Skip to content

← All sections

Elevation, slope, aspect and relief of the ground at the address

Elevation, slope, aspect and relief of the ground at the address, computed from Kartverket's 10 m terrain model, with a position class such as hilltop or hollow. A modelled reading, not a survey.

terrain13 fields13 of these fields open in the demo
Source
Kartverket NHM terrain WCS, sampled at 10 m by Approach
Geography
The address point
Reported stale after
400 days
Access
Requires an API key granted this section
Contract version
1
In packages
construction, plot_and_zoning, calculations

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
22 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 22 Nov 2026
Newest record
22 Nov 2026
Municipalities with data
357

Measured 22 Nov 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.

Available with: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing

Model and method

What is the terrain at the address: height, slope, aspect and position?

This is model metadata from the contract. Results are estimates, not observed source facts. Declared maturity and reference comparison do not establish that the current model release is approved or available to the customer.

Result type
Calculation
Method
Geometric calculation
Declared maturity
Marked stable in the catalogue
Reference comparison
No qualified comparison declared
Contract version
1
Model artifact and runtime version
Not established by this catalogue description
Inputs, headline fields and comparison basis

Declared inputs

  • DTM10 (Kartverket)

Headline output fields

elevation_m, slope_deg, slope_pct, aspect_deg, aspect_name, relief_100m_m, relief_250m_m, tpi_100m_m, position_class, height_above_low_250m_m, steep_share_100m

Declared comparison basis

none: derived directly from the terrain model

Input names are not a complete training dataset or revision-pinned lineage. Read the caveats and response metadata for what a particular result is based on.

Source terms and reuse

These are declarations from the catalogue contract, not a new rights approval. Customer access, source agreements and privacy need separate assessment. A licence label does not establish coverage or reviewed content.

Declared licence or terms
unverified
Declared redistribution
Not established
Catalogue basis
Unverified
Attribution and note

Shown from the contract in its original language.

Computed by Approach; the terms of its inputs named in source apply and have not been reviewed together.

API warnings

The API returns these notes in warnings.

  • Computed from Kartverket NHM terrain WCS sampled by Approach on a 10 m output grid; this does not identify the separate legacy DTM10 product or establish 10 m vertical accuracy. Slope uses a 20 m baseline and may miss a cut-in driveway, retaining wall or filled plot; it is not a survey or the actual access-road gradient. 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: a value near zero describes relative terrain position only, not a flow path or a prediction that water will collect there. Vertical datum, datum realization and source capture date are not carried in these rows; computed_at is the processing time. Verify compatible source height references before comparing elevation_m with flood, storm-surge or design levels. steep_share_100m is the share of ground within 100 m steeper than 25°. No record until terrain-enrichment has reached the tile.

Provider-contract 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” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.

FieldTypeRoleDemo
elevation_mnumber | null (m)valueopen
slope_degnumber | null (grader)valueopen
slope_pctnumber | null (%)valueopen
aspect_degnumber | null (grader)valueopen
aspect_namestring | nullvalueopen
relief_100m_mnumber | nullvalueopen
relief_250m_mnumber | nullvalueopen
tpi_100m_mnumber | nullvalueopen
position_classstring | nullvalueopen
height_above_low_250m_mnumber | null (m)valueopen
steep_share_100mnumber | null (andel)valueopen
dtm_resolution_mnumber | null (m)contextopen
computed_atstring | nullcontextopen

Fetch this section

Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.

curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/285717643?include=terrain'

# paginated, one section at a time
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  '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.