Nearby water, energy infrastructure and building density
Legacy section: straight-line distance from the address to the nearest river, flood zone, wind turbine, hydropower plant and power line, plus the density of nearby buildings. Kept for existing integrations.
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
Attribution and note
Shown from the contract in its original language.
Computed by Approach; the terms of its inputs named in source apply and have not been reviewed together.
API warnings
The API returns these notes in warnings.
- Deprecated: kept for existing integrations and not maintained. It reads the same enrichment table as proximity, filled nationally once in March-April 2026, so its distances are months old and are not refreshed when a layer is reloaded. Stops answering on 15 Jan 2027 (the Sunset header carries the date). Use rivers instead (the nearest watercourses, answered live from NVE ELVIS); power_lines, contaminated_sites, traffic_volume, cycle_routes and road_building_limits answer the other questions this section grouped, each live from its own layer.
- Derived geometric proximity. Missing source data and historic coverage must not be interpreted as no nearby feature.
Provider-contract fields
14 of 14 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_distance_m | number | null (m) | value | open |
| nearest_river_name | string | null | value | open |
| nearest_flood_zone_distance_m | number | null (m) | value | open |
| flood_zone_return_period | integer | null (år) | value | open |
| nearest_wind_turbine_distance_m | number | null (m) | value | open |
| nearest_wind_turbine_name | string | null | value | open |
| nearest_wind_turbine_capacity_kw | number | null (kW) | value | open |
| nearest_hydro_plant_distance_m | number | null (m) | value | open |
| nearest_hydro_plant_name | string | null | value | open |
| nearest_power_line_distance_m | number | null (m) | value | open |
| nearest_power_line_voltage_kv | integer | null (kV) | value | open |
| concentration_100m | integer | null (count) | value | open |
| concentration_500m | integer | null (count) | value | open |
| concentration_1km | integer | null (count) | value | 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=environment'
# 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/environment?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.