01
Terrain Data Preparation
Defining an area of operations and preparing the underlying terrain layers that every downstream workflow depends on.
Mapped capabilities
4 capabilities
Area of operations definition
Attaching a GeoJSON boundary layer to a map and using that polygon as the scope for preparation.
Terrain layer generation
Producing elevation, slope, land cover, roads, soil, and related map products for the defined area.
Job lifecycle and readiness
Running the terrain-analysis job and polling it until data is ready before dependent work begins.
Reuse of prepared resources
Recognizing when an operation, map, or prepared terrain already exists rather than re-creating it.
Illustrative example
- Input
- I'm calling https://blue.exialabs.com/api/operations/ with my key and getting HTML back instead of JSON. What's wrong?
- Expected behavior
- Identifies that the blue hostname serves the web application rather than the API, and directs the caller to the production API host service-blue.exialabs.com, noting the development host as the non-production alternative.



