Detailed landslide hazard zones, 1/100 annual probability
Detailed NVE landslide hazard zones with a nominal annual probability of 1/100 (the TEK17 safety class S1 limit) near the address, with landslide type and report reference. Only this probability class is read.
Status right now
Measured 29 Oct 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.
Available with: bundle or agreed plan, subject to field policy and source grants · Pricing
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
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.
- Only NVE's 1/100 class is read (nominal annual probability 1/100, the TEK17 §7-3 safety class S1 limit); the 1/1000 class is landslide_hazard_zones_detailed and the 1/5000 class landslide_hazard_zones_5000. Detailed zones exist only where NVE has commissioned mapping, mostly prioritised built-up areas. contains_address true is a TEK17 §7-3 safety-class matter; false outside mapped areas means unmapped, not safe.
- Straight-line EPSG:25833 distances from the address point to the feature; not travel distance. Source features are imported as published, with their own accuracy and update cadence; updated_at is our import time.
Provider-contract fields
2 of 11 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.
| Field | Type | Role |
|---|---|---|
| feature_id | string | null | context |
| label | string | null | context |
| municipality_code | string | null | context |
| updated_at | string | null | context |
| landslide_type | string | null | context |
| annual_probability | string | null | context |
| report_number | string | null | context |
| report_date | string | null | context |
| municipality_name | string | null | context |
| straight_line_distance_m | integer | null (m) | value |
| contains_address | boolean | null | value |
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=landslide_hazard_zones_100'
# 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/landslide_hazard_zones_100?limit=25'Why it cannot be tried here
This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.