Traffic data Automotive (infrared detectors) Hamburg

General information: The data set includes traffic data from all locations in Hamburg where motor vehicle traffic (vehicle traffic) is recorded by means of infrared detectors 24 hours a day and all days of the year. The data contains traffic volumes in real time and is made available at counting points summarised for the road cross-section in 15 minutes, 60 minutes, daily and weekly intervals. The data of the counting points are also visualized in the corresponding geoportals of the FHH, e.g. in Geo-Online and the traffic portal. In addition to 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 the last year in daily intervals, and all data since the beginning of the collection in weekly intervals. Information on technology: The infrared detectors are usually installed on light signal systems, but to a small extent also on other masts. The detectors record and count the traffic via the heat radiation of the individual traffic participants. 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 Urban Data Platform of the FHH. This means that they are available to all users and interested parties in a timely manner. Due to the real-time component, however, various framework conditions must be observed: The data is not fully quality-assured. Unusual deviations from the expected data and data gaps are automatically detected by the system, but cannot be corrected in real time. Gaps, which occur e.g. due to a demolition of the data transmission, can still be delivered afterwards. Under certain circumstances and in the case of longer outages, changes in the historical data can therefore still take place after a few days. The data are therefore updated daily for the following periods: The day before: 15-minute intervals Six days ago: 15-minute intervals and daily intervals 28 days ago: Daily intervals Weekly values are updated weekly for the previous week and the week before four weeks. The data published here are not officially verified data of the FHH. If such data are required, the data set "Verkehrsstärken Hamburg" can be used, for example, which contains the "average (working) daily traffic" in the development of recent years. As with any traffic count, whether automated or manual, there are certain tolerances in measurement accuracy. The system used here requires accuracies of +/- 5% for the recording of vehicle traffic strengths. More information about the real-time service: The real-time data service contains the locations of the counting points for vehicle traffic, which is recorded with infrared detectors. The data is provided in JSON format via the SensorThings API (STA). For each counting point in the SensorThings API (STA), an object has been created in the entity "Thing". For each temporal resolution level at the counting points or each traffic reference value, there is an object in the entity "Datastreams". The real-time data on the number of vehicles per counting point and time interval is published in the STA in the entity "Observations". The following spatial and temporal levels are differentiated: -Counting point 15-min, 1-hour, 1-day, 1-week: Number of vehicles All times are given in Coordinated Universal Time (UTC). In the Datastreams entity, there are additional key-value pairs under the "key" "properties" in the JSON object. Following the service and layer structure in GIS, we have introduced service and layer as additional "key-value pairs" under the JSON property. Here is an example: { "properties":{ "serviceName": "HH_STA_Automated traffic quantity recording", "layerName": "Number_Kfz_Zaehlstelle_15-Min", "key":"value"} } Available layers in the layerName are: * Number_car_description_15-min * Number_car_recent_1 hour * Number_Kfz_Zaehlstelle_1-Tag * Number_car_destination_1 week With the help of these "key-value pairs", filters can then be defined for the REST request, e.g. https://iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName eq 'HH_STA_AutomatierteVerkehrsmengeerfassung' and properties/layerName eq 'Number_Kfz_Zaehlstelle_15-Min' The real-time data can also be obtained through an MQTT broker. The necessary IDs can be obtained via a REST request and then used for the subscription to a data stream: MQTT broker: iot.hamburg.de Topic: v1.1/Datastream({id})/Observations