Ecological and chemical status of the nearest river, lake and coastal water within 500 m

water_body_status17 fieldsNot in the demo

Source: Miljødirektoratet Vann-Nett water bodies (vannforekomster, NLOD)
Geography: Around the address
Reported stale after: 120 days
Access: Requires an API key granted this section
Contract version: 1

Available with: bought bundle or agreed plan (all fields) · Pricing

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 water bodies the Water Framework Directive work classifies, as published in Vann-Nett: for the nearest river, lake and coastal water within 500 m of the address point, the ecological status (or potential, for heavily modified water) and the chemical status with the precision the classification has, and whether the body is at risk of missing its environmental objective. A status describes the whole water body, often kilometres of river or a whole fjord, not the water at the address, and is not a bathing-water or drinking-water test.
Status values are Vann-Nett's own codes, passed on unchanged: svaertGod, god, moderat, daarlig, svaertDaarlig, or ikkeKlassifisert where the body has not been classified; precision is hoey, middels, lav or ingenInformasjon. Distances are straight-line to the body's line or area; contains_address is true when the address point lies in a lake or coastal polygon.
No record for a type means no water body of that type is classified within 500 m. Small streams and ponds are not separate water bodies in Vann-Nett.

Fields

5 of 17 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.

Field	Type	Role
water_body_type	string \| null	context
water_body_id	string \| null	context
name	string \| null	value
ecological_status	string \| null	value
ecological_status_precision	string \| null	context
chemical_status	string \| null	value
chemical_status_precision	string \| null	context
risk_assessment	string \| null	value
natural_or_heavily_modified	string \| null	context
ecological_objective	string \| null	context
chemical_objective	string \| null	context
river_basin_district	string \| null	context
water_management_area	string \| null	context
factsheet_url	string \| null	context
straight_line_distance_m	integer \| null (m)	value
contains_address	boolean \| null	context
updated_at	timestamp \| null	context

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 --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643?include=water_body_status'

# paginated, one section at a time
curl --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643/sections/water_body_status?limit=25'

Why it cannot be tried here

This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.