Skip to content

← All sections

Road and transport context

Legacy section: speed limit on the nearest road and straight-line distances from the address to NVDB road objects such as bus stops, parking, tunnels, bridges, toll stations and traffic signals. Kept for existing integrations.

roads19 fields18 of these fields open in the demo
Source
NVDB proximity enrichment
Geography
The address point
Reported stale after
120 days
Access
Requires an API key granted this section
Contract version
1
In packages
traffic_and_sensors

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

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
Norsk lisens for offentlige data 2.0
Declared redistribution
Allowed with attribution
Catalogue basis
Publisher terms
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 NVDB proximity enrichment

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 and refreshed for about 10 000 of 2.6 million addresses a night, so most distances are months old and nvdb_enriched_at must be read per address. Stops answering on 15 Jan 2027 (the Sunset header carries the date). Use road_infrastructure instead (the nearest bridges, tunnels, ferry quays, toll stations, level crossings and park-and-ride, answered live from the loaded NVDB objects); traffic_volume, cycle_routes and road_building_limits answer the traffic, cycling and building-limit questions from the same live network.
  • Straight-line metres from the address point to the nearest NVDB object geometry, not travel distance. When nvdb_enriched_at is set, a null distance means nothing of that kind within the search radius (0.5–50 km by type); when it is null the address has not been checked yet.

Provider-contract fields

18 of 19 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.

FieldTypeRoleDemo
nearest_road_speed_limitinteger | null (km/h)valueopen
high_speed_road_distance_mnumber | null (m)valueopen
nearest_bus_stop_distance_mnumber | null (m)valueopen
nearest_transit_hub_distance_mnumber | null (m)valueopen
nearest_noise_barrier_distance_mnumber | null (m)valueopen
nearest_speed_bump_distance_mnumber | null (m)valueopen
nearest_traffic_signal_distance_mnumber | null (m)valueopen
nearest_tunnel_distance_mnumber | null (m)valueopen
nearest_bridge_distance_mnumber | null (m)valueopen
nearest_toll_station_distance_mnumber | null (m)valueopen
nearest_parking_distance_mnumber | null (m)valueopen
nearest_railway_crossing_distance_mnumber | null (m)valueopen
has_sidewalk_nearbyboolean | nullvalueopen
has_street_lightingboolean | nullvalueopen
nearest_intersection_distance_mnumber | null (m)valueopen
nearest_roundabout_distance_mnumber | null (m)valueopen
nearest_rest_area_distance_mnumber | null (m)valueopen
nearest_ferry_dock_distance_mnumber | null (m)valueopen
nvdb_enriched_atstring | 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=roads'

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