Skip to content

← All sections

Mapped NVE hazard-zone matches at the address point

Whether the address point lies inside mapped NVE flood, quick-clay and landslide zones, with return period, hazard level and class, and the status behind each answer. Where zones are not mapped, NVE awareness (aktsomhet) maps give a coarser second answer.

hazard_zones20 fields12 of these fields open in the demo
Source
NVE flood/quick-clay/landslide zones
Geography
The address point
Reported stale after
120 days
Access
Requires an API key granted this section
Contract version
1
In packages
safety, core, hazard_screen, fire_and_damage

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
1 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured
Municipalities with data
0

Measured 22 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: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing

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

API warnings

The API returns these notes in warnings.

  • 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.
  • Second tier where the zone maps are missing: flood_aktsomhet, quick_clay_aktsomhet and landslide_aktsomhet answer from NVE's national awareness (aktsomhet) maps — flood, quick clay, and debris flow/flood slide plus rockfall run-out. in_area means the address lies in an area where the hazard must be assessed before building; it is a screening map, not a hazard zone, and never sets in_<hazard>_zone. outside_area means the point is outside every awareness area of a loaded national map, which narrows the question but does not clear the address. Null means the map is not loaded; the matching *_aktsomhet_coverage says national or not_loaded.

Provider-contract fields

13 of 20 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” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.

FieldTypeRoleDemo
in_flood_zoneboolean | nullvalueopen
flood_statusstring | nullvalueopen
flood_min_return_periodinteger | null (år)valueopen
flood_climate_adjustedboolean | nullcontextopen
in_quick_clay_zoneboolean | nullvalueopen
quick_clay_statusstring | nullvalueopen
quick_clay_hazard_levelstring | nullvalueopen
quick_clay_zone_typestring | nullvalue—
quick_clay_consequence_classstring | nullcontextopen
quick_clay_risk_classinteger | nullcontext—
in_landslide_zoneboolean | nullvalueopen
landslide_statusstring | nullvalueopen
landslide_hazard_typestring | nullvalueopen
landslide_safety_classstring | nullcontextopen
flood_aktsomhetstring | nullvalue—
flood_aktsomhet_coveragestring | nullcontext—
quick_clay_aktsomhetstring | nullvalue—
quick_clay_aktsomhet_coveragestring | nullcontext—
landslide_aktsomhetstring | nullvalue—
landslide_aktsomhet_coveragestring | nullcontext—

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_zones'

# 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_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.