Buildings, roads and land below storm-surge levels in the kommune, today and with sea-level rise
storm_surge_municipal_exposure20 fieldsNot in the demo
Available with: bought bundle or agreed plan (all fields) · Pricing
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.
- Kommune statistics from Kartverket's storm-surge consequence analysis: how many buildings, metres of road and square metres of land lie below each extreme water level, at today's sea level (2025) and with the sea-level rise expected by 2100 or 2150. A benchmark for the kommune, not an answer for any one address: storm_surge_zones and sea_level_projection answer whether the address itself is inside a zone.
- Kartverket notes that the dataset is not suited to detailed studies or decisions at plot level. Counts are of objects whose footprint intersects the flooded area; waves, wind set-up and local protection are not modelled. Only coastal kommuner are in the source; an inland kommune has no rows, which is not the same as zero exposure being computed.
Fields
5 of 20 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 |
|---|---|---|
| municipality_code | string | null | context |
| scenario | string | null | context |
| scenario_description | string | null | context |
| return_period_years | integer | null | context |
| sea_level_year | integer | null (årstall) | context |
| buildings_total | integer | null | value |
| public_buildings | integer | null | context |
| commercial_buildings | integer | null | context |
| private_buildings | integer | null | value |
| critical_buildings | integer | null | value |
| other_buildings | integer | null | context |
| private_road_m | integer | null | context |
| public_road_m | integer | null | context |
| road_total_m | integer | null | value |
| built_up_area_m2 | integer | null (m2) | context |
| nature_area_m2 | integer | null (m2) | context |
| public_facilities_area_m2 | integer | null (m2) | context |
| primary_industry_area_m2 | integer | null (m2) | context |
| area_total_m2 | integer | null (m2) | value |
| fetched_at | timestamp | null | context |
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 --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643?include=storm_surge_municipal_exposure' # paginated, one section at a time curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643/sections/storm_surge_municipal_exposure?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.