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.
Status right now
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.
| Field | Type | Role |
|---|---|---|
| feature_id | string | null | context |
| label | string | null | context |
| municipality_code | string | null | context |
| updated_at | string | null | context |
| uncertainty | object | null | context |
| hazard_index | integer | null | value |
| hazard_level | string | null | value |
| dominant_hazard | string | null | value |
| status | string | null | context |
| abstain_reason | string | null | context |
| components_loaded | integer | null | context |
| components_missing | array<string> | null | context |
| flood_score | integer | null | context |
| flood_level | string | null | context |
| flood_coverage | string | null | context |
| storm_surge_score | integer | null | context |
| storm_surge_level | string | null | context |
| storm_surge_coverage | string | null | context |
| sea_level_score | integer | null | context |
| sea_level_level | string | null | context |
| sea_level_coverage | string | null | context |
| quick_clay_score | integer | null | context |
| quick_clay_level | string | null | context |
| quick_clay_coverage | string | null | context |
| landslide_score | integer | null | context |
| landslide_level | string | null | context |
| landslide_coverage | string | null | context |
| ground_motion_score | integer | null | context |
| ground_motion_level | string | null | context |
| ground_motion_coverage | string | null | context |
| extreme_precipitation_score | integer | null | context |
| extreme_precipitation_level | string | null | context |
| extreme_precipitation_coverage | string | null | context |
| components | array<object> | null | context |
| model_warnings | array<string> | null | context |
| method | string | null | context |
| model_version | string | null | context |
| inputs_digest | string | null | context |
| computed_at | string | 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 --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.