Traffic Lights Data Hamburg

Description

LSA process data The dataset currently includes the LSA process data for about half of all nodes connected to the traffic computer network in Hamburg and contains current signal characteristics in real time. In addition, data on detectors such as bicycle, pedestrian and vehicle requirements as well as bus messages are transmitted. The following points should be taken into account when using the data: Due to maintenance work, there may be occasional short failures in signal transmission for several road trains. In a few cases, there are also incorrect timestamps from the LSA ECUs (phenomenonTime), which are responsible for implausible latency values. For a better understanding of the data, a user manual is linked in the References and Downloads section. More information about the real-time service: The OGC SensorThings API compliant real-time data service contains data streams and positions of lane relationships at intersections with light signal systems for cyclists, pedestrians and motor vehicles in Hamburg’s urban area. When provided on the light signal system, the following data streams are delivered as JSON objects: Primary signals, secondary signals, auxiliary signals, acoustic signals, automotive signal requirements, cyclist signal requirements, pedestrian signal requirements, acoustic signal requirement, public transport pre-registration, public transport registration, public transport deregistration, signal program and wave seconds. In the OGC SensorThings API, the information on the lane relationships is stored in the entity Thing. For the data streams listed above, which are available at a specific thing, an entry in the entity Datastreams is created that references the corresponding thing. All dates are given in Coordinated Universal Time (UTC). In the entity Datastreams there are further “key value pairs” in the JSON object under the “key” “properties”. Based on the service and layer structure in the GIS, we introduced Service and Layers as additional “key-value pairs” under the JSON object properties. Here is an example: { “properties”: { “service name”: “HH_STA_traffic_lights”, “layer name”: “primay_signal”, “key”: “value” } } All possible values for “Layername”: * primay_signal (primary signal), * secondeary_signal (secondary signal), * auxiliary_signal (auxiliary signal), * acoustic_signal (acoustic signal), * detector_car (Automotive Signal Requirement), * detector_cyclist (cyclist signal requirement), * detector_pedestrian (Pedestrian signal requirement), * detector_acoustic_traffic_request, * bus_pre-request_point (public transport pre-registration), * bus_request_point (public transport registration), * bus_checkout (public transport deregistration), * signal_program (signal program number), * cycle_second (wave-second) These “key-value pairs” can then be used to define filters for the REST request, e.g. https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName eq ‘HH_STA_traffic_lights’ and properties/Layername eq ‘primary_signal’ The real-time data can also be obtained via 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: tld.iot.hamburg.de Topic: v1.1/Datastreams({id})/Observations Furthermore, the MAP files (.xml- and.kml) of all previously published nodes can be accessed via the following link: https://daten-hamburg.de/tlf_public/

Resources

Name Format Description Link
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27bus_checkout%27&$expand=Observations($orderby=phenomenonTime%20desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27cycle_second%27&$expand=Observations($orderby=phenomenonTime%20desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27detector_acoustic_traffic_request%27&$expand=Observations($orderby=phenomenonTime%20desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27bus_request_point%27&$expand=Observations($orderby=phenomenonTime%20desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.0/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27primary_signal%27&$expand=Observations($orderby=phenomenonTime%20desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27acoustic_signal%27&$expand=Observations($orderby=phenomenonTime%20desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName+eq+%27HH_STA_traffic_lights%27+and+properties/layerName%20eq%27detector_car%27&$expand=Observations($select=phenomenonTime,result;$orderby=phenomenonTime+desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.1/Things?$filter=Datastreams/properties/serviceName%20eq%20%27HH_STA_traffic_lights%27&$orderby=id&$expand=Locations&$top=100
0 https://tld.iot.hamburg.de/v1.1/Things?$filter=Datastreams/properties/serviceName%20eq%20%27HH_STA_traffic_lights%27&$expand=Locations,Datastreams($expand=Observations($orderby=phenomenonTime%20desc;$top=3),Sensor,ObservedProperty)&$top=100
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27bus_pre-request_point%27&$expand=Observations($select=phenomenonTime,result;$orderby=phenomenonTime%20desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27secondary_signal%27&$expand=Observations($orderby=phenomenonTime%20desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27detector_pedestrian%27&$expand=Observations($orderby=phenomenonTime%20desc;$top=10)&$orderby=id&$top=100
0 https://tld.iot.hamburg.de/v1.1/Datastreams?$filter=properties/serviceName%20eq%20%27HH_STA_traffic_lights%27%20and%20properties/layerName%20eq%20%27signal_program%27&$expand=Observations($orderby=phenomenonTime%20desc;$top=10)

Tags

  • tlf
  • ampeldaten
  • lichtsignalanlagen
  • hmbtg
  • geodaten
  • opendata
  • sensordaten
  • ampeln
  • knotentopologie
  • sensorthings-api
  • lsa-prozessdaten
  • echtzeitdaten
  • frost-server
  • lsa
  • tran
  • mqtt

Topics

  • TRAN

Categories