Elevation
Understand terrain heights, coordinate ordering, vertical reference, and missing samples.
Sample the landscape
Elevation returns terrain samples at the coordinates you supply. Ordering matters: keep the original point sequence to relate each sample to a location along your path.
Start with contract examples
curl -X POST 'https://api.uat.audisory.com/v1/elevation' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"coordinates": [
[
30.0619,
-1.9441
],
[
30.09,
-1.937
],
[
30.122,
-1.942
]
]
}'Units and vertical reference
Values use metres relative to the documented EGM2008 vertical reference from Copernicus DEM GLO-30. They are not ellipsoidal GPS altitude and should not be compared directly without considering the reference system.
Surface height is not surveyed road height
The surface model can include buildings and vegetation. Missing samples are possible; preserve gaps rather than replacing them with zero. Interpolating a chart can improve presentation but does not create observed terrain data.
Model limitations
Elevation samples and derived slopes are useful planning inputs. They do not establish survey-grade accuracy, a legal gradient classification, or a calibrated travel-time guarantee.
Explore the request schema
| Field | Type | Description |
|---|---|---|
coordinatesrequired | array | Points to sample, in order.Nested fields{
"type": "array",
"description": "A WGS84 position as `[longitude, latitude]`, in that order.",
"minItems": 2,
"maxItems": 2,
"prefixItems": [
{
"type": "number",
"format": "double",
"description": "Longitude in decimal degrees.",
"minimum": -180,
"maximum": 180
},
{
"type": "number",
"format": "double",
"description": "Latitude in decimal degrees.",
"minimum": -90,
"maximum": 90
}
],
"x-go-type": "[]float64",
"examples": [
[
30.0619,
-1.9441
]
]
} |
Read the generated elevation reference and preserve the required data attribution.