Sea-level and storm-surge scenarios at the address (present, 2100, 2150)
sea_level_projection14 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.
- One row per published scenario: mean high water, 20-, 200- and 1000-year storm surge and the upper estimate, in the present climate and, where Kartverket publishes it, for 2100 and 2150. Together they show how far the sea can reach with the projected rise: compare the same hazard across climate_year. water_level_cm_nn2000 is the level of the nearest modelled area (within 2 km) and distance_to_zone_m is 0 when the address is inside it.
- Static maps of the area that the stated water level would cover (aktsomhetskart): waves, wind set-up, rain and groundwater are not included, and Kartverket says the modelled areas are not suited for detailed studies or decisions at plot level. The 2100 and 2150 scenarios follow DSB's 2024 guide and the report Sea-Level Rise and Extremes in Norway (2024); the 2050 horizon is not published in this dataset. in_zone false means no modelled flooding at this scenario inside the model's coverage; null means the scenario is not loaded or the address is outside the coverage.
- Water levels are whole centimetres above NN2000, as the source publishes them (vannstandOverNN2000). The older storm_surge_zones_current and storm_surge_zones_2100 sections serve the same property under the name water_level_nn2000_m, which is also centimetres, not metres.
- station_level_cm_nn2000 is the return level at the nearest permanent tide gauge in the present climate (Kartverket Se havnivå, locationlevels API); the gauge can be far away and on another side of a fjord or island. For 2100 and 2150 there is no gauge figure.
- Licence: NLOD (Norsk lisens for offentlige data) for the Stormflo og havnivå polygons (Kartverket, metadata on kartkatalog.geonorge.no); the tide-station return levels come from Kartverket's Se havnivå API, licensed CC BY 4.0. Attribution: Kartverket.
Fields
4 of 14 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 |
|---|---|---|
| scenario | string | null | context |
| label | string | null | context |
| hazard | string | null | context |
| return_period_years | integer | null | context |
| climate_year | string | null (årstall) | context |
| in_zone | boolean | null | value |
| water_level_cm_nn2000 | number | null | value |
| distance_to_zone_m | integer | null | value |
| model_covers_address | boolean | null | context |
| nearest_station_name | string | null | context |
| nearest_station_distance_m | integer | null (m) | context |
| station_level_cm_nn2000 | number | null | value |
| station_level_code | string | null | context |
| updated_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=sea_level_projection' # 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/sea_level_projection?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.