Skip to content

← All sections

Hazard screening (compatibility view of hazard_zones)

Legacy hazard screening: whether the address point lies in a mapped NVE flood, quick-clay or landslide zone, with flood return periods. Kept for existing integrations; hazard_zones carries the reasons behind unknowns.

hazards15 fields15 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

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.

  • 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.

Provider-contract 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” 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_return_periodinteger | null (år)valueopen
in_quick_clay_zoneboolean | nullvalueopen
quick_clay_hazard_levelstring | nullvalueopen
in_landslide_zoneboolean | nullvalueopen
landslide_hazard_typestring | nullvalueopen
in_flood_20yrboolean | nullvalueopen
in_flood_50yrboolean | nullvalueopen
in_flood_100yrboolean | nullvalueopen
in_flood_200yrboolean | nullvalueopen
in_flood_500yrboolean | nullvalueopen
in_flood_1000yrboolean | nullvalueopen
flood_zone_countinteger | null (count)valueopen
flood_max_return_periodinteger | null (år)valueopen
computed_atstring | nullcontextopen

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=hazards'

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