Skip to content

← All sections

Road traffic around the address in 100 m, 500 m and 1 km discs

Road traffic around the address in 100 m, 500 m and 1 km discs, with traffic sensors shown separately. Also eight 45-degree compass sectors, the road nearest the address point, a distance-weighted figure, the count year behind each figure and observed transit departures within walking distance. Not live traffic.

traffic_exposure63 fields45 of these fields open in the demo
Source
Statens vegvesen NVDB (ÅDT), Statens vegvesen traffic sensors and Entur (observed departures)
Geography
The address point
Reported stale after
120 days
Access
Requires an API key granted this section
Contract version
1
In packages
environment_nuisance, noise_and_nearby_projects, calculations

Read about this data source →

Status right now

State
Not measured yet
There is no age measurement for this section yet, or it is measured when requested.
Last loaded
not measured
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured
Municipalities with data
357

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

Model and method

How much traffic passes within 100 m, 500 m and 1 km?

This is model metadata from the contract. Results are estimates, not observed source facts. Declared maturity and reference comparison do not establish that the current model release is approved or available to the customer.

Result type
Calculation
Method
Geometric calculation
Declared maturity
Marked stable in the catalogue
Reference comparison
No qualified comparison declared
Contract version
1
Model artifact and runtime version
Not established by this catalogue description
Inputs, headline fields and comparison basis

Declared inputs

  • NVDB ÅDT
  • Trafikkdata sensors

Headline output fields

max_adt_100m, traffic_load_100m, adt_segments_over_5000_100m, adt_segments_over_15000_100m, sensor_combined_adt_100m, max_adt_500m, traffic_load_500m, adt_segments_over_5000_500m, adt_segments_over_15000_500m, sensor_combined_adt_500m, max_adt_1000m, traffic_load_1000m, adt_segments_over_5000_1000m, adt_segments_over_15000_1000m, sensor_combined_adt_1000m, nearest_adt_road_distance_m

Declared comparison basis

none: an exposure measure, not a prediction

Input names are not a complete training dataset or revision-pinned lineage. Read the caveats and response metadata for what a particular result is based on.

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.

  • ÅDT is Statens vegvesen's annual average daily traffic for a road stretch in the year adt_year (from counting or estimation, see basis and adt_counted), not live traffic. Discs are straight-line distance from the address point (_100m, _500m, _1000m; each disc includes the smaller ones) and say nothing about whether a road is reachable, audible or screened from the address.
  • traffic_load_<r> is Σ(ÅDT × metres of the stretch inside the disc) / 1000 / disc area in km², in vehicle-km per km² per day. Each NVDB stretch counts once; separate carriageways and one-way streets are separate stretches carrying their own traffic. NVDB leaves ÅDT off many municipal and private roads, so the load is a lower bound: those roads are unknown, not zero. A disc with no ÅDT stretch has adt_segments 0 and null ÅDT figures (adt_status no_adt_road_in_ring); no_adt_data_within_20km means we hold no ÅDT stretch within 20 km of the address (NVDB has none there, or the area is not loaded), and every ÅDT figure is null.
  • busiest_road_<r>.adt_applies_to is one_carriageway_of_divided_road when NVDB records the ÅDT for one carriageway only; the road's two-way traffic is then roughly the sum of both carriageways. heavy_vehicle_share_pct is NVDB's share of long vehicles (5.6 m and over). NVDB carries no street name for ÅDT stretches; road_number (EV18, FV24, KV1234) identifies the road.
  • Sensor figures are never summed across sensors: sensors on one road count the same vehicles. sensor_combined_adt_<r> is the sum over distinct road numbers of the busiest sensor on each road (sensor_combination_method), with the roads listed in sensor_roads_<r>. Sensors are sparse, so sensor_count_<r> is mainly a data-quality indicator and a disc without sensors (sensor_status no_sensor_in_ring) is not measured, not free of traffic. busiest_sensor_<r>.vehicles_per_hour is the latest stored hourly volume. Its measurement interval is not retained in this projection; updated_at is import time, not observation time. This is not a live congestion measure.
  • Every figure carries the year of the count behind it (adt_year, adt_years_<r>, adt_year_oldest, adt_year_newest). NVDB years run from 1982 to 2025 and counts older than five years are flagged, not hidden: an old count says what the road carried then. traffic_exposure_method serves the rules below in machine-readable form.
  • traffic_sectors_<r> are eight 45-degree compass sectors (N is 337.5 to 22.5 degrees) of the 500 m and 1 km discs, azimuth clockwise from grid north. Each carries the ÅDT figures clipped to that sector; a stretch that crosses several sectors counts in each. A sector with no ÅDT stretch is unknown (adt_segments 0, null figures), not free of traffic. No stretch ids or per-stretch positions are served for sectors.
  • frontage_road is the ÅDT stretch nearest the address point within 150 m, ties by higher ÅDT. The platform holds no entrance point for addresses, so this is the road nearest the address point, not a verified entrance or facade road; nearer_stretch_without_adt_m says when a nearer road has no ÅDT (unknown traffic). frontage_cone_500m is a 90-degree cone centred on the bearing from the address point to that stretch; the bearing is an address-point bearing, not an entrance direction.
  • weighted_adt_exposure_<r> is the sum over ÅDT stretches of ÅDT × length in km × w(d), w(d) = min(1, 25 m / d), d the distance from the address point to the midpoint of each 10 m piece, in vehicle-km per day weighted. Nearer traffic counts more; it is an index of closeness to traffic, not a noise level and not traffic at the facade. Like traffic_load it is a lower bound where NVDB has no ÅDT.
  • transit_<r>m counts departures that Entur's national real-time feed (SIRI-ET, monitored journeys only) reported at stops within <r> m straight-line of the address point, over the window transit_window_from to transit_window_to (observed_departures; departures_per_hour is the window average). It is observed service rolled up per stop, not a timetable; a stop served only by unmonitored journeys reads low. transit_status says why the figures are missing: transit_activity_not_loaded, transit_activity_stale (refreshed more than three days ago), no_stop_in_walking_distance or transit_window_unknown. transport.gtfs_routes is empty in production and is not used.

Provider-contract fields

16 of 63 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
adt_status_100mstring | nullcontextopen
adt_segments_100minteger | nullcontextopen
max_adt_100minteger | nullvalueopen
busiest_road_100mobject | nullcontextopen
traffic_load_100mnumber | nullvalueopen
adt_segments_over_5000_100minteger | nullvalueopen
adt_segments_over_15000_100minteger | nullvalueopen
sensor_status_100mstring | nullcontextopen
sensor_count_100minteger | nullcontextopen
sensor_combined_adt_100minteger | nullvalueopen
sensor_roads_100marray<object> | nullcontextopen
busiest_sensor_100mobject | nullcontextopen
sensors_in_ring_100marray<object> | nullcontextopen
adt_status_500mstring | nullcontextopen
adt_segments_500minteger | nullcontextopen
max_adt_500minteger | nullvalueopen
busiest_road_500mobject | nullcontextopen
traffic_load_500mnumber | nullvalueopen
adt_segments_over_5000_500minteger | nullvalueopen
adt_segments_over_15000_500minteger | nullvalueopen
sensor_status_500mstring | nullcontextopen
sensor_count_500minteger | nullcontextopen
sensor_combined_adt_500minteger | nullvalueopen
sensor_roads_500marray<object> | nullcontextopen
busiest_sensor_500mobject | nullcontextopen
sensors_in_ring_500marray<object> | nullcontextopen
adt_status_1000mstring | nullcontextopen
adt_segments_1000minteger | nullcontextopen
max_adt_1000minteger | nullvalueopen
busiest_road_1000mobject | nullcontextopen
traffic_load_1000mnumber | nullvalueopen
adt_segments_over_5000_1000minteger | nullvalueopen
adt_segments_over_15000_1000minteger | nullvalueopen
sensor_status_1000mstring | nullcontextopen
sensor_count_1000minteger | nullcontextopen
sensor_combined_adt_1000minteger | nullvalueopen
sensor_roads_1000marray<object> | nullcontextopen
busiest_sensor_1000mobject | nullcontextopen
sensors_in_ring_1000marray<object> | nullcontextopen
sensor_combination_methodstring | nullcontextopen
nearest_adt_roadobject | nullcontextopen
nearest_adt_road_distance_minteger | null (m)valueopen
nearest_adt_road_statusstring | nullcontextopen
adt_fetched_attimestamp | nullcontextopen
sensors_updated_attimestamp | nullcontextopen
traffic_exposure_methodobject | nullcontext—
adt_years_100mobject | nullcontext—
adt_years_500mobject | nullcontext—
adt_years_1000mobject | nullcontext—
weighted_adt_exposure_500mobject | nullcontext—
weighted_adt_exposure_1000mobject | nullcontext—
traffic_sectors_500marray<object> | nullcontext—
traffic_sectors_1000marray<object> | nullcontext—
frontage_road_statusstring | nullcontext—
frontage_roadobject | nullcontext—
frontage_cone_500mobject | nullcontext—
transit_statusstring | nullcontext—
transit_sourcestring | nullcontext—
transit_window_fromtimestamp | nullcontext—
transit_window_totimestamp | nullcontext—
transit_refreshed_attimestamp | nullcontext—
transit_400mobject | nullcontext—
transit_800mobject | 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=traffic_exposure'

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