Nearest registered dams

dams16 fields16 of these fields open in the demo

Source: NVE Damdatabasen
Geography: Around the address
Reported stale after: 120 days
Access: Requires an API key granted this section
Contract version: 2
In packages: hazard_screen

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.

Proximity only. Dam-break consequence class (bruddkonsekvensklasse) and downstream inundation are not in this layer, so this is not a downstream-of-dam assessment.
Straight-line EPSG:25833 distances from the address point to the feature; not travel distance. Source features are imported as published, with their own accuracy and update cadence; updated_at is our import time.
Routes follow the car profile, from the address to the feature; ranking remains straight-line. Static modelled travel time excludes live traffic and emergency response. Road snapping is limited to 250 m at each end. Ferries may be included without timetable/wait guarantees. Graph source date is unverified unless supplied. © OpenStreetMap contributors, ODbL: https://www.openstreetmap.org/copyright
walk_route and cycle_route follow OSRM's foot and bicycle profiles on the same OpenStreetMap data: paths and stairs allowed on foot, road rules for bicycles; modelled times at profile default speeds, not measured.

Fields

2 of 16 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
feature_id	string \| null	context	open
label	string \| null	value	open
municipality_code	string \| null	context	open
updated_at	string \| null	context	open
dam_function	integer \| null	context	open
licence_status	integer \| null	context	open
status	string \| null	context	open
commissioned_year	integer \| null (årstall)	context	open
reservoir_name	string \| null	context	open
municipality_name	string \| null	context	open
straight_line_distance_m	integer \| null (m)	value	open
lon	number \| null	context	open
lat	number \| null	context	open
route	object	context	open
walk_route	object	context	open
cycle_route	object	context	open

Fetch this section

curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643?include=dams"

# paginated, one section at a time
curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643/sections/dams?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.