Skip to content

← All sections

Sensor proximity

Identity and straight-line distance of the traffic sensors within 5 km of the address. The sensors' own observations are in the traffic section.

traffic_sensor_links3 fields3 of these fields open in the demo
Source
Approach geometric matching
Geography
The address point
Reported stale after
30 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
22 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured
Municipalities with data
329

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.

  • Straight-line EPSG:25833 distances to traffic sensors within 5 km. No driving distance and no road-relevance guarantee.
  • This is the identity-and-distance list; the sensors' own observations are in the traffic section, computed from the same match.

Provider-contract fields

2 of 3 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
sensor_idstring | nullcontextopen
sensor_namestring | nullvalueopen
straight_line_distance_minteger | null (m)valueopen

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_sensor_links'

# 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_sensor_links?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.