Skip to content

← All sections

Modelled surface-water indicators

Modelled surface-water indicators from the 10 m terrain model: depressions, height above nearest drainage, flow accumulation and slope at the address. It is an estimate of where water goes, not a flood map.

water_risk14 fields14 of these fields open in the demo
Source
Approach terrain analysis
Geography
The address point
Reported stale after
1 year
Access
Requires an API key granted this section
Contract version
1
In packages
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
22 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 22 Nov 2026
Newest record
22 Nov 2026
Municipalities with data
357

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

Model and method

Where does surface water collect and run at the address?

This is model metadata from the contract. Results are estimates, not observed source facts. Declared maturity and reference comparison do not establish that the current model release is approved or available to the customer.

Result type
Calculation
Method
Geometric calculation
Declared maturity
Experimental
Reference comparison
No qualified comparison declared
Contract version
1
Model artifact and runtime version
Not established by this catalogue description
Inputs, headline fields and comparison basis

Declared inputs

  • DTM10 (Kartverket)

Headline output fields

depression_score, hand_score, flow_accumulation_score, slope_score, overall_water_risk, depression_depth_m, hand_value_m, flow_accumulation_cells, slope_degrees, elevation_m, nearest_drainage_distance_m, dtm_resolution_m

Declared comparison basis

none yet: not a flood model

Input names are not a complete training dataset or revision-pinned lineage. Read the caveats and response metadata for what a particular result is based on.

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
Attribution and note

Shown from the contract in its original language.

Computed by Approach; the terms of its inputs named in source apply and have not been reviewed together.

API warnings

The API returns these notes in warnings.

  • Estimate, not a flood map: a screening of where water goes when the ground alone decides, from the national 10 m terrain model: depression_depth_m is how deep water would stand at the point before it drains (a blue spot), hand_value_m the height above the nearest drainage line, flow_accumulation_cells how many 10 m cells drain through the point, slope_degrees the local slope. The 0-100 scores weight these 30/25/20/15 with 10 for the position in the tile's elevation range. A 10 m grid sees neither kerbs, culverts nor drains: not a flood model, not an engineering assessment or an insurance rating.
  • Computed nightly in rotation through the kommuner, one 2 km DTM tile at a time (from 6 Oct 2026; a national pass takes about four nights, after which rows older than a year are recomputed in turn). Until an address has been computed the section is not_found with reason not_yet_computed: unknown, never low risk. Addresses where Kartverket's DTM has no ground under the point (sea, lakes, survey holes) stay not computed. Flood zones and quick clay are in hazard_zones.

Provider-contract fields

12 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” 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
depression_scoreinteger | null (score 0-100)valueopen
hand_scoreinteger | null (score 0-100)valueopen
flow_accumulation_scoreinteger | null (score 0-100)valueopen
slope_scoreinteger | null (score 0-100)valueopen
overall_water_riskinteger | null (score 0-100)valueopen
depression_depth_mnumber | null (m)valueopen
hand_value_mnumber | null (m)valueopen
flow_accumulation_cellsinteger | null (count)valueopen
slope_degreesnumber | null (degrees)valueopen
elevation_mnumber | null (m)valueopen
nearest_drainage_distance_mnumber | null (m)valueopen
dtm_resolution_minteger | null (m)valueopen
analysis_datestring | nullcontextopen
updated_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=water_risk'

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