Latest water level and discharge at nearby NVE stations

nearby_water_level15 fieldsNot in the demo

Source: NVE HydAPI (saved copy; requires an NVE API key to be filled)
Geography: Around the address
Reported stale after: 6 hours
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.

Up to ten of the nearest active NVE hydrological stations within 15 km that have a stage or discharge reading from the last three days. latest_stage_m is water level in metres at the station's own gauge zero, not above sea level and not comparable between stations; latest_discharge_m3s is discharge. quality 0 unknown, 1 uncontrolled, 2 primary controlled, 3 secondary controlled.
A station reports the water at the station, not at the address. Straight-line distance says nothing about whether the station is upstream or downstream of the address, on the same river or in the same catchment; compare river_name, regine_no and station_height_masl with the address before drawing a conclusion. Readings are recent, provisional values (quality 1 = uncontrolled) and are not a flood warning: NVE's Varsom is the warning service.
This section is filled only when the owner has configured an NVE HydAPI key (NVE_HYDAPI_KEY): hydapi.nve.no answers 401 without one. Until then it is empty for every address and an empty section means nothing about the water nearby.
Licence: NLOD, stated on https://hydapi.nve.no/UserDocumentation/. NVE gives the data as is and says it can contain erroneous or missing data. Attribution: Norwegian Water Resources and Energy Directorate (NVE).

Fields

3 of 15 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
station_id	string \| null	context
station_name	string \| null	context
river_name	string \| null	context
regine_no	string \| null	context
council_name	string \| null	context
station_height_masl	integer \| null	context
drainage_basin_area_km2	number \| null (km2)	context
straight_line_distance_m	integer \| null (m)	value
latest_stage_m	number \| null	value
latest_stage_at	timestamp \| null	context
latest_stage_quality	integer \| null	context
latest_discharge_m3s	number \| null	value
latest_discharge_at	timestamp \| null	context
latest_discharge_quality	integer \| 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=nearby_water_level'

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