Skip to content

← All sections

Climate and natural hazard exposure index

Screening index of climate and natural-hazard exposure at the address, combining flood, storm-surge, sea-level and other mapped components, with the dominant hazard and which components were loaded. Not an insurance price or a geotechnical assessment.

hazard_exposure39 fieldsNot in the demo
Source
Approach hazard model over NVE, NGU, Kartverket and Klimaservicesenteret layers
Geography
The address point
Reported stale after
120 days
Access
Requires an API key granted this section
Contract version
1
In packages
hazard_screen, fire_and_damage, calculations

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
16 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 16 Nov 2026
Newest record
16 Nov 2026
Municipalities with data
20

Measured 16 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: bundle or agreed plan, subject to field policy and source grants · Pricing

Model and method

How exposed is the address to climate and natural hazards overall, and which hazard drives it?

This is model metadata from the contract. Results are estimates, not observed source facts. Declared maturity and reference comparison do not establish that the current model release is approved or available to the customer.

Result type
Calculation
Method
Index
Declared maturity
Marked stable in the catalogue
Reference comparison
No qualified comparison declared
Contract version
1
Model artifact and runtime version
Not established by this catalogue description
Inputs, headline fields and comparison basis

Declared inputs

  • NVE hazard zones
  • NGU
  • Kartverket storm surge and sea level
  • Klimaservicesenteret projections

Headline output fields

hazard_index, hazard_level, dominant_hazard

Declared comparison basis

none: the worst component plus documented adjustments

Input names are not a complete training dataset or revision-pinned lineage. Read the caveats and response metadata for what a particular result is based on.

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
Attribution and note

Shown from the contract in its original language.

Computed by Approach; the terms of its inputs named in source apply and have not been reviewed together.

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.

  • A screening indicator built from mapped hazard zones and projections, not an insurance price or a geotechnical assessment. The index is the worst component plus a bounded share of the others; a component whose source does not cover the address is reported as missing and left out, so the index is then a lower bound.
  • 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

3 of 39 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.

FieldTypeRole
feature_idstring | nullcontext
labelstring | nullcontext
municipality_codestring | nullcontext
updated_atstring | nullcontext
uncertaintyobject | nullcontext
hazard_indexinteger | nullvalue
hazard_levelstring | nullvalue
dominant_hazardstring | nullvalue
statusstring | nullcontext
abstain_reasonstring | nullcontext
components_loadedinteger | nullcontext
components_missingarray<string> | nullcontext
flood_scoreinteger | nullcontext
flood_levelstring | nullcontext
flood_coveragestring | nullcontext
storm_surge_scoreinteger | nullcontext
storm_surge_levelstring | nullcontext
storm_surge_coveragestring | nullcontext
sea_level_scoreinteger | nullcontext
sea_level_levelstring | nullcontext
sea_level_coveragestring | nullcontext
quick_clay_scoreinteger | nullcontext
quick_clay_levelstring | nullcontext
quick_clay_coveragestring | nullcontext
landslide_scoreinteger | nullcontext
landslide_levelstring | nullcontext
landslide_coveragestring | nullcontext
ground_motion_scoreinteger | nullcontext
ground_motion_levelstring | nullcontext
ground_motion_coveragestring | nullcontext
extreme_precipitation_scoreinteger | nullcontext
extreme_precipitation_levelstring | nullcontext
extreme_precipitation_coveragestring | nullcontext
componentsarray<object> | nullcontext
model_warningsarray<string> | nullcontext
methodstring | nullcontext
model_versionstring | nullcontext
inputs_digeststring | nullcontext
computed_atstring | nullcontext

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

# 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/hazard_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.