Rivers and streams near the address (NVE ELVIS)
Rivers and streams near the address from NVE's river network: nearest river, nearest named and main river, Strahler order, catchment, and number of river segments within 500 m. Distances are straight-line.
Status right now
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
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
API warnings
The API returns these notes in warnings.
- Distances are straight-line from the address point to the river line (not to a segment centroid); a null name means the nearest water is an unnamed brook. Strahler order 1 is a headwater stream, 6 or more a large river; nearest_main_river is the hovedelv of a catchment. river_length_m_500m sums the segments inside a 500 m circle. Nearness to a stream is not a flood finding — hazard_zones carries NVE's mapped flood zones; this says how close, and how big, the water is. No record until nve-rivers has loaded the network.
Provider-contract fields
10 of 17 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.
| Field | Type | Role | Demo |
|---|---|---|---|
| nearest_river_name | string | null | value | open |
| nearest_river_strahler_order | integer | null | value | open |
| nearest_river_distance_m | integer | null (m) | value | open |
| nearest_river_watershed | string | null | context | open |
| nearest_river_vassdragsnr | string | null | context | — |
| nearest_river_catchment_area | string | null | context | — |
| nearest_named_river_name | string | null | value | open |
| nearest_named_river_strahler_order | integer | null | context | open |
| nearest_named_river_distance_m | integer | null (m) | value | open |
| nearest_main_river_name | string | null | value | open |
| nearest_main_river_distance_m | integer | null (m) | value | open |
| segments_500m | integer | null | value | open |
| river_length_m_500m | integer | null (m) | value | open |
| max_strahler_500m | integer | null | context | open |
| river_within_100m | boolean | null | value | open |
| river_within_20m | boolean | null | context | open |
| updated_at | string | null | context | open |
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=rivers'
# 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/rivers?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.