Elevation, slope, aspect and relief of the ground at the address
terrain13 fields13 of these fields open in the demo
What this does not say
Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.
- Read off the national 10 m terrain model, so slope is over a 20 m baseline and a cut-in driveway, a retaining wall or a filled plot is invisible to it; not a survey. aspect_name is the downhill compass direction (flatt below 1°). relief_100m_m and relief_250m_m are the height difference within that radius; tpi_100m_m is the elevation minus the mean within 100 m, and position_class reads it as rygg (ridge, +5 m or more), søkk (hollow, -5 m or less), skråning (6° or steeper) or flate. height_above_low_250m_m is how far the address sits above the lowest ground within 250 m: near zero means water collects here before anywhere else nearby. steep_share_100m is the share of ground within 100 m steeper than 25°. No record until terrain-enrichment has reached the tile.
Fields
11 of 13 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” return values to anonymous callers; the rest require a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| elevation_m | number | null (m) | value | open |
| slope_deg | number | null (grader) | value | open |
| slope_pct | number | null (%) | value | open |
| aspect_deg | number | null (grader) | value | open |
| aspect_name | string | null | value | open |
| relief_100m_m | number | null | value | open |
| relief_250m_m | number | null | value | open |
| tpi_100m_m | number | null | value | open |
| position_class | string | null | value | open |
| height_above_low_250m_m | number | null (m) | value | open |
| steep_share_100m | number | null (andel) | value | open |
| dtm_resolution_m | number | null (m) | context | open |
| computed_at | string | null | context | open |
Fetch this section
curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643?include=terrain" # paginated, one section at a time curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643/sections/terrain?limit=25"
Try it now
This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.