Measured hourly traffic near the address
traffic_hourly_history19 fieldsNot in the demo
Available with: bought bundle or agreed plan (all fields) · Pricing
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.
- Measured hourly buckets at sensors within 5 km, not estimated traffic at the address. The window is the last seven days; use section pagination for all available sensor/hour keys. No farther sensor is substituted. Stations may count the same vehicles and their volumes must not be summed.
- measured_from/to are source measurement times; imported_at is retrieval/storage time. Missing hours are absent, not zero; a null volume is not zero. Low or unknown coverage remains visible with quality_status. A quality-gated bucket is not proof of a complete station series or complete source coverage.
- Local dates/hours use Europe/Oslo. The autumn repeated hour retains two distinct UTC measured_from keys; the spring skipped hour is not fabricated. This is rolling current-source history, not a frozen point-in-time historical dataset.
- 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
2 of 19 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.
| Field | Type | Role |
|---|---|---|
| sensor_id | string | context |
| road | string | null | context |
| lat | number | null (degrees) | context |
| lon | number | null (degrees) | context |
| straight_line_distance_m | integer (m) | context |
| measured_from | string | context |
| measured_to | string | context |
| volume | integer | null (vehicles) | value |
| coverage_pct | number | null (percent) | context |
| heavy_vehicle_pct | number | null (percent) | value |
| imported_at | string | context |
| time_basis | string | context |
| local_timezone | string | context |
| local_date | string | context |
| local_hour | integer | context |
| quality_status | string | context |
| route | object | context |
| walk_route | object | context |
| cycle_route | object | context |
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 --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643?include=traffic_hourly_history' # paginated, one section at a time curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643/sections/traffic_hourly_history?limit=25'
Why it cannot be tried here
This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.