Skip to content

← All sections

Rockslide and tsunami hazard zones

NVE hazard zones for rockslide and the resulting tsunami near the address, with landslide type, annual probability and zone type. Only mapped high-risk objects are covered, so no zone is not proof of no exposure.

rockslide_tsunami_zones11 fields11 of these fields open in the demo
Source
NVE Fjellskred faresoner
Geography
Around the address
Reported stale after
47 days
Access
Requires an API key granted this section
Contract version
1
In packages
hazard_screen

Read about this data source →

Status right now

State
Late
The combined section or collection clock is near or past its limit. Check the data timestamp separately.
Last loaded
17 Oct 2026
Data freshness evidence
Late
Newest stored data record 17 Oct 2026
Newest record
17 Oct 2026
Municipalities with data
19

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 the mapped high-risk rockslide objects and their run-up zones are covered; no zone within the radius is not proof of no exposure.
  • 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.

FieldTypeRoleDemo
feature_idstring | nullcontextopen
labelstring | nullcontextopen
municipality_codestring | nullcontextopen
updated_atstring | nullcontextopen
landslide_typestring | nullcontextopen
annual_probabilitystring | nullcontextopen
zone_typestring | nullcontextopen
report_urlstring | nullcontextopen
project_urlstring | nullcontextopen
straight_line_distance_minteger | null (m)valueopen
contains_addressboolean | nullvalueopen

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=rockslide_tsunami_zones'

# 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/rockslide_tsunami_zones?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.