Detailed landslide hazard zones, 1/1000 annual probability
Detailed NVE landslide hazard zones with a nominal annual probability of 1/1000 (the TEK17 safety class S2 limit) near the address, with landslide type and report reference. Only this probability class is read.
Status right now
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
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
API warnings
The API returns these notes in warnings.
- Only NVE's 1/1000 class is read (nominal annual probability 1/1000, the TEK17 §7-3 safety class S2 limit); the 1/100 and 1/5000 zones are the sections landslide_hazard_zones_100 and 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. Complements the aktsomhet-based hazard_zones section.
- 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. 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.
| Field | Type | Role | Demo |
|---|---|---|---|
| feature_id | string | null | context | open |
| label | string | null | context | open |
| municipality_code | string | null | context | open |
| updated_at | string | null | context | open |
| landslide_type | string | null | context | open |
| annual_probability | string | null | context | open |
| report_number | string | null | context | open |
| report_date | string | null | context | open |
| municipality_name | string | null | context | open |
| straight_line_distance_m | integer | null (m) | value | open |
| contains_address | boolean | null | value | open |
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_detailed'
# 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_detailed?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.