Mapped NVE hazard-zone matches at the address point
hazard_zones14 fields9 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.
- The canonical hazard answer: hazards, safety_and_regulations and ground_integrity answer from the same zones and the same rule. Point-in-polygon against locally ingested NVE zones. True reports a match in a mapped zone. False reports no match, and only where the address's kommune is in the layer's coverage (/coverage) — that proves we hold zones there, not complete municipal surveying. Outside coverage the answer is null and the matching *_status is unknown_not_covered. Missing matches never establish absence of hazard. Null must never be read as clearance. Source freshness is unverified unless a retrieval timestamp is supplied.
- flood_min_return_period is the lowest present-climate recurrence whose zone covers the point (e.g. 20 = inside the 20-year flood zone); flood_climate_adjusted is true when the point lies in NVE's climate-adjusted (year-2100) zone, so in_flood_zone true with a null flood_min_return_period means the 2100 zone only. Quick clay reports the most severe NVE grade at the point, whether that zone is the release area (where a slide starts) or the run-out area (where the masses end up), and NVE's risk class 1-5. landslide_hazard_type 'combined' is NVE's joint zone for every slide type in steep terrain. Not an engineering assessment.
Fields
10 of 14 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_status | string | null | value | — |
| flood_min_return_period | integer | null (år) | value | open |
| flood_climate_adjusted | boolean | null | context | open |
| in_quick_clay_zone | boolean | null | value | open |
| quick_clay_status | string | null | value | — |
| quick_clay_hazard_level | string | null | value | open |
| quick_clay_zone_type | string | null | value | — |
| quick_clay_consequence_class | string | null | context | open |
| quick_clay_risk_class | integer | null | context | — |
| in_landslide_zone | boolean | null | value | open |
| landslide_status | string | null | value | — |
| landslide_hazard_type | string | null | value | open |
| landslide_safety_class | string | null | context | open |
Fetch this section
curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643?include=hazard_zones" # paginated, one section at a time curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643/sections/hazard_zones?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.