Hazard screening (compatibility view of hazard_zones)
hazards15 fields15 of these fields open in the demo
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.
- Deprecated: kept for existing integrations, answered live from the same mapped zones and the same coverage rule as hazard_zones, which carries the reason for every unknown (flood_status, quick_clay_status, landslide_status) and should be used instead. True is a match in a mapped zone. False is no match in a kommune whose zones we hold (see /coverage). Null is unknown — the kommune is not covered — and never clearance; missing matches never establish absence of hazard.
- Flood figures count present-climate zones only: flood_return_period is the lowest and flood_max_return_period the highest return period whose zone covers the point. in_flood_<n>yr is null inside a zone of another period, because NVE does not map every period everywhere. quick_clay_hazard_level is the most severe NVE grade at the point.
Fields
14 of 15 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” return values to anonymous callers; the rest require a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| in_flood_zone | boolean | null | value | open |
| flood_return_period | integer | null (år) | value | open |
| in_quick_clay_zone | boolean | null | value | open |
| quick_clay_hazard_level | string | null | value | open |
| in_landslide_zone | boolean | null | value | open |
| landslide_hazard_type | string | null | value | open |
| in_flood_20yr | boolean | null | value | open |
| in_flood_50yr | boolean | null | value | open |
| in_flood_100yr | boolean | null | value | open |
| in_flood_200yr | boolean | null | value | open |
| in_flood_500yr | boolean | null | value | open |
| in_flood_1000yr | boolean | null | value | open |
| flood_zone_count | integer | null (count) | value | open |
| flood_max_return_period | integer | null (år) | value | open |
| computed_at | string | null | context | open |
Fetch this section
curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643?include=hazards" # paginated, one section at a time curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643/sections/hazards?limit=25"
Try it now
This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.