Skip to content

← All sections

200-year storm-surge zones, present climate

Areas that a 200-year storm surge would flood in today's climate, with the water level in centimetres above NN2000 and a safety class. Static inundation from sea level, without waves or wind set-up.

storm_surge_zones_current10 fields10 of these fields open in the demo
Source
Kartverket Stormflo via Geonorge
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
11 Oct 2026
Data freshness evidence
Late
Newest stored data record 11 Oct 2026
Newest record
11 Oct 2026
Municipalities with data
229

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
Creative Commons Attribution 4.0
Declared redistribution
Allowed with attribution
Catalogue basis
Publisher terms
Read the publisher terms →
Attribution and note

Shown from the contract in its original language.

© Kartverket Stormflo via Geonorge, CC BY 4.0

API warnings

The API returns these notes in warnings.

  • Static inundation from the 200-year sea level; waves and wind set-up are not included.
  • Unit: water_level_nn2000_cm is whole centimetres above NN2000 as Kartverket publishes it (vannstandOverNN2000): 110 means 1.10 m. water_level_nn2000_m is a deprecated alias of the same field and its value is centimetres too, despite the suffix; read _cm, the _m name is removed in a later version. The sea_level_projection section names the same value water_level_cm_nn2000.
  • 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 10 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
water_level_nn2000_cmnumber | null (cm)contextopen
water_level_nn2000_mnumber | nullcontextopen
safety_classstring | nullcontextopen
source_updated_atstring | 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=storm_surge_zones_current'

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