Flood, landslide and avalanche warning days in the kommune since each warning service began
natural_hazard_warnings18 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.
- Lived hazard, not mapped hazard: the number of days NVE's Varsom has warned the address's kommune, one record per hazard. A warning covers a region or a group of kommuner and says nothing about whether the address itself was exposed; hazard_zones and the awareness maps answer that. hazard_warnings answers what is in force now.
- Levels: flood and landslide use Varsom's 1-4 awareness scale (2 yellow, 3 orange, 4 red); avalanche uses the 1-5 European avalanche danger scale, and level 2 (moderate) is the normal winter state, so threshold_level is 3 (considerable) for avalanche and 2 (yellow) for the others. mean_threshold_days_per_full_year averages the days at or above threshold_level over years in which the service issued on at least 360 days (flood, landslide) or 150 days (avalanche).
- History starts where the service does: flood and landslide warnings from 2013, avalanche from the 2017-18 season (earlier seasons used other region ids). days_covered counts the days the service issued; warning_status not_collected means the history has not been fetched and every count is null, and not_in_avalanche_forecast_region means no avalanche forecast region covers the kommune. An avalanche day for a kommune is the highest level of any forecast region that covers it.
Fields
7 of 18 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 |
|---|---|---|
| hazard | string | null | context |
| municipality_code | string | null | context |
| warning_status | string | null | context |
| level_scale | string | null | context |
| threshold_level | integer | null | context |
| first_year | integer | null (årstall) | context |
| covered_through | date | null | context |
| days_covered | integer | null | context |
| days_level_2 | integer | null | value |
| days_level_3 | integer | null | value |
| days_level_4 | integer | null | value |
| days_level_5 | integer | null | value |
| full_years | integer | null | context |
| mean_threshold_days_per_full_year | number | null (årstall) | value |
| by_year | object | null | value |
| latest_warning_date | date | null | value |
| latest_warning_level | integer | null | context |
| 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=natural_hazard_warnings' # 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/natural_hazard_warnings?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.