WG SXL Standardization 2024-09-12

[emiltin]

Participants

Toni, Matti, David, Emil

VMS

Different use-cases have slightly different needs, eg. pixel errors on highway panels can be used for closing the road if the panel is deemed unreadable.
Let's us invite a VMS producer to a feedback session where we review our current technical concept.
Matti can provide info about existing protocols being used in Finland for VMS'es.

Sensors

We previously discussed use cases, what data types to cover, classification, etc.
Are we ready to move to designing concrete messages?

Sometimes it can be useful to get more raw data e,.g. for fixing errors in equipment. Perhaps we can think of a way to get raw data, but with normalized values.

Video and LIDAR detectors can provide new types of data. But what kind of generic data types can be define that is technology agnostic, and makes sense for traffic management or traffic analysis. A video can be used to analyse behaviour.

Behaviour is often related to safety; near-miss situations, use of helmets, red-crossings, etc.

Current TLC control strategies typically assume (for historical reasons) that detectors are loops. Never technologies often emulate a loop to provide just on/off values, even though they could provide more data, like queue lengths.

Data types

Existing data types:

• volume /count
• speed
• presence/occupancy
• classification

Possible new types:

• Queue length
• Estimated time of arrival to intersection
• Turn movements
• Accelleration
• Vehicle length/height
• Hot map (pedestrians crossing outside designated crossings)
• Vehicle density

Next steps

Emil will contact VisuaLED
Matti will get info about VMS protocols used in Finland