Climate and natural hazard exposure index
hazard_exposure38 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.
- 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.
Fields
3 of 38 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 |
| 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 --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643?include=hazard_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/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.