General information: The data set includes traffic data from all locations in Hamburg where motor vehicle traffic (vehicle traffic) is recorded using infrared detectors 24 hours a day and every day of the year. The data contain real-time traffic volumes and are made available at counting points summarized for the road cross-section at 15-minute, 60-minute, daily and weekly intervals. The data from the counting points is also visualized in the corresponding geoportals of the FHH, e.g. Geo-Online and Verkehrsportal.

In addition to the real-time data, historical data is also available to the following extent: all data for the last two weeks in 15 -minute intervals, all data for the last two months for the 60-minute intervals, all data for the current and last year in daily intervals, all data since the beginning of the collection in weekly intervals.

Technical information: The infrared detectors are usually installed on traffic lights, but to a lesser extent also on other masts. The detectors record and count the traffic via the heat radiation of the individual road users. Since only infrared images are evaluated, data protection is guaranteed at all times.

Notes on data quality: The data is transmitted in real time to the FHH Urban Data Platform. In this way, they are available promptly to all users and interested parties. Due to the real-time component, however, various framework conditions must be observed: The data is not comprehensively quality-assured. Unusual deviations from the expected data and data gaps are automatically recognized by the system, but cannot be corrected in real time. Gaps that occur, e.g. due to a break in data transmission, can be supplied later. Under certain circumstances and in the case of longer failures, changes in the historical data can still occur after a few days.

The data is therefore updated daily for the following periods: Previous day: 15-minute intervals Six days ago : 15 min intervals and daily intervals day 28 days ago: daily intervals

The weekly values are updated weekly for the values of the previous week and the week four weeks ago.

The data published here is not officially verified data from the FHH. If such data is required, e.g. the data set "Traffic volume Hamburg" can be used. be used, which contains the "average (work)day traffic" in the development of the last few years. As with any traffic count, whether automated or manual, there are certain tolerances in the measurement accuracy. The requirements for the system used here are accuracies of +/- 5% when recording vehicle traffic volumes.

Further information about the real-time service:

The real-time data service contains the locations of the counting points for the Vehicle volume recorded with infrared detectors. The data is provided in JSON format via the SensorThings API (STA). For each counting place in the SensorThings API (STA), an object was created in the "Thing" entity. created. There is an object in the "Datastreams" entity for each temporal resolution level at the counting points or each traffic reference value. The real-time data on the number of vehicles per counting point and time interval is stored in the STA in the "Observations" entity. published.

The following spatial and temporal levels are differentiated:

-Counting point 15 minutes, 1 hour, 1 day, 1 week: number of vehicles

< p>All times are given in Coordinated Universal Time (UTC).

In the Datastreams entity, there is a JSON object under the "key" "properties" more "key-value-pairs". Based on the service and layer structure in GIS, we have defined service and layer as additional "key-value pairs" introduced under the JSON object properties. Here is an example:

{ "properties":{ "serviceName": "HHSTAAutomated traffic volume acquisition", "layerName": "NumberKfz< /em>Zaehlstelle_15-Min", "key":"value"} }

Available layers in the layerName are: * NumberKfzZehlstelle15-Min * Numbercarscounting station1-hour * Numbercarscounting station1-day * Numbercarscounting station1 -Week

Using these "key-value pairs" filters can then be defined for the REST request, e.g. #39; and properties/layerName eq 'NumberKfzZaehlstelle_15-Min'

The real-time data can also be obtained via an MQTT broker. The IDs required for this can be set via a REST request and then used to subscribe to a data stream:

MQTT broker: iot.hamburg.de Topic: v1.1/Datastream({id})/Observations

Activity Stream