Skip to content

← All sections

Latest water level and discharge at nearby NVE stations

Latest water level and discharge at up to ten NVE hydrological stations within 15 km of the address. A station reports the water at the station, not at the address, and distance does not say whether it is upstream or downstream.

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

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
19 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured

Measured 19 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: 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
Norsk lisens for offentlige data 2.0
Declared redistribution
Allowed with attribution
Catalogue basis
Stated in catalogue evidence
Read the publisher terms →
Attribution and note

Shown from the contract in its original language.

Inneholder data under norsk lisens for offentlige data (NLOD) tilgjengeliggjort av NVE HydAPI (saved copy; requires an NVE API key to be filled)

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

Provider-contract 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.

FieldTypeRole
station_idstring | nullcontext
station_namestring | nullcontext
river_namestring | nullcontext
regine_nostring | nullcontext
council_namestring | nullcontext
station_height_maslinteger | nullcontext
drainage_basin_area_km2number | null (km2)context
straight_line_distance_minteger | null (m)value
latest_stage_mnumber | nullvalue
latest_stage_attimestamp | nullcontext
latest_stage_qualityinteger | nullcontext
latest_discharge_m3snumber | nullvalue
latest_discharge_attimestamp | nullcontext
latest_discharge_qualityinteger | nullcontext
updated_attimestamp | nullcontext

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

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