Nearest traffic sensors
nearest_traffic_sensors17 fields17 of these fields open in the demo
What this does not say
Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.
- Ten nearest sensors geometrically; not guaranteed to monitor the property's road. Observation interval is not retained; updated_at is import time, not measurement time.
- Routes follow the car profile, from the address to the feature; ranking remains straight-line. Static modelled travel time excludes live traffic and emergency response. Road snapping is limited to 250 m at each end. Ferries may be included without timetable/wait guarantees. Graph source date is unverified unless supplied. © OpenStreetMap contributors, ODbL: https://www.openstreetmap.org/copyright
- walk_route and cycle_route follow OSRM's foot and bicycle profiles on the same OpenStreetMap data: paths and stairs allowed on foot, road rules for bicycles; modelled times at profile default speeds, not measured.
Fields
7 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” return values to anonymous callers; the rest require a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| sensor_id | string | null | context | open |
| road | string | null | context | open |
| road_category | string | null | context | open |
| lat | number | null | context | open |
| lon | number | null | context | open |
| straight_line_distance_m | number | null (m) | value | open |
| vehicles_per_hour | integer | null | value | open |
| heavy_vehicle_pct | number | null (%) | value | open |
| coverage_pct | number | null (%) | value | open |
| avg_daily_volume | integer | null | value | open |
| peak_hour | integer | null | context | open |
| peak_hour_volume | integer | null | value | open |
| road_speed_limit | integer | null | value | open |
| updated_at | string | null | context | open |
| route | object | context | open |
| walk_route | object | context | open |
| cycle_route | object | context | open |
Fetch this section
curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643?include=nearest_traffic_sensors" # paginated, one section at a time curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643/sections/nearest_traffic_sensors?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.