Skip to main content

UC 13: Wrong way driving warning

Operation use case​

Definition​

Wrong-way driving/ ghost driving: Vehicle(s) traveling on the wrong side of a divided carriageway against the oncoming traffic.

Operational Road Environment​

  • Territory: Flanders
  • Border passing cases:
  • Road class: Highways and high-speed roads with median/centre divider.
  • Time restrictions: none
  • Weather restrictions: none
  • Special restrictions: none

MI & historical archive​

DENM information​

The data is presented as DENM message, main characteristics:

CausecodeDescriptionSubcausecodeDescription
14wrong way driver0unavailable
1Vehicle driving in wrong lane
2Vehicle driving in wrong driving direction
  • Time to live:
    • Default DENM time to live 600 seconds or 10 minutes.
    • Based on RUF it is 300 seconds or 5 minutes.
  • Lat/Long position of original WWD situation detection.
  • Relevance zone defined, upstream the lat/long position: zone until next highway entry location, with a minimum distance of 5 min isochrone starting at that next entry location (e.g., 10 km upstream @ 120km/h).
  • Number of WWD vehicles: not specified.
  • Type of WWD vehicle (motorcycle/car/truck): not specified.

MI Headers​

Capability descriptor:

{
  "messageType": "DENM",
  "originatingCountry": "BE",
  "protocolVersion": "DENM:1.3.1",
  "publisherId": "BE00004",
  "publicationId": "BE00004:DENM_GHOST_DRIVER_01",
  "custom-mobilidata-publisherType": "PIP",
  "custom-mobilidata-dtapEnvironment": "production",
  "custom-mobilidata-useCase": [13],
  "quadTree": []
}

Historical archive​

The data is tranformed to NGSI-LD data classes and stored in the historical database, in the date of creation based hierarchy.

Data processing (PIP)​

Event creation​

Events are issued by flemmish traffic center, Bosch or Ruf where the data is converted in a DEN message. The location container traces in the message are upstream towards the first junction/highway entrance or the length calculated for 5 minutes at the maximum speed for that road section. Wrong way driver events are only generated for highways and high-speed roads with median/centre divider.

Event handling and ending​

Depending on the automated source of the data, messages are automatically ended due to time-to-live value, or ended manualy. the RUF

Quality check​

Due to the volatile character and the difficulty in checking the information, the PIO is not performing additional verifications.

Data sources​

  1. Flanders traffic center notifications: own and trusted 3rd party observations and manually generated alerts (typically validated by Road Police before official distribution): DATEX point notification of location of observation (any position on highway)
  2. Bosch Wrong way driving notification: automated detections of WWD coming from all Bosch-WWD-service connected applications and apps. The Mobilidata connected app’s Flitsmeister and KartaGPS are part of that community. Bosch notices WWD situation on the off-ramps of all highways in the EU and notifies the WWdriver + the community. If the WWD responds to his notification stops/turns back the notification is NOT cancelled in current version Bosch WWD. The standard TTL for the notification of 5 min is overruled for the Mobilidata message and set to 15 minutes.
  3. RUF (road user feedback/new notifications) coming from Mobilidata connected Road users, currently Flitsmeister and KartaGPS. Under unspecified validation processes before transmission towards Mobilidata (e.g., required trust level user? number of notifications required? location bundling process?) The user trust system of the C-ITS service provider is not questioned.

Risk and remarks​

None

Alert cancelling​

Only alerts directly managed by the Flanders traffic center can be cancelled before the Mobilidata standard of 10-minute time to live cycle of wrong way driving alerts. For all others (Bosch and RUF), and even with positive end of situation knowledge from authorities, there is no process of cancelling or warning for ‘end of situation’ sent.

Use case implementation recommendations in applications and apps​

disclaimer

Mobilidata does not warrant an optimal safe usage system with recommendations below. It fully remains the responsibility of the information provider to know the usage situation and needs of their users and provide a safety enhancing service based on Mobilidata information.

Message​

The message to the wrong way driver himself is not treated here since it is not part of the Mobilidata enabled use case via the message on the Mobilidata Interchange. We do encourage new information providers to become part of the Bosch WWD ecosystem and enable the WWD detection service for drivers. Contact us for more information.

The alert for road users entering a zone with possible encounter of a wrong way driver:

Notification:

ICON based notifications are always to be preferred over textual messages. There is no road sign equivalent for the wwd situation, and no standard icons exist to our knowledge. Some application developers use ‘ghost’-image based icons, but that has its’ limitations in regions where wrong way driving is not known as ghost-driving. Alternatively the more common way of alerting is the general ‘attention danger’ symbol as used on road-signs, but that does need extra text and reading before interpretation is possible. More direct icon examples like these we consider also to be good examples, but are not to be used/copied without permission: Coyote and Bosch (copyrighted) examples:

notification notification

Basic alert message:* Wrong way driver alerted zone: * Use the lanes on the right * Slow down

Additional info:

Remaining distance before entering the zone – when approaching zone.
Remaining length of zone – when in the wrong way driving zone.

Voice alert:

Basic alert, messages if possible repeated 1X.

Map information:

highlight WWD zone on the map.

Message example​

UC 13 Message Example
{
    "shardId": "1",
    "latitude": "49.704205",
    "quadTree": ",120203220020020231,1202032200200,",
    "causeCode": "14",
    "longitude": "5.629905",
    "shardCount": "1",
    "messageType": "DENM",
    "publisherId": "BE00004",
    "serviceType": ",HLN-AWWD,",
    "subCauseCode": "2",
    "publicationId": "BE00004:DENM_GHOST_DRIVER_02",
    "baselineVersion": "2.1.0",
    "protocolVersion": "DENM:1.3.1",
    "originatingCountry": "BE",
    "custom-mobilidata-useCase": ",13,",
    "custom-mobilidata-timestamp": "1737723048511",
    "custom-mobilidata-alertCCodes": "1701",
    "custom-mobilidata-publisherType": "PIP",
    "custom-mobilidata-baselineVersion": "1.0.0",
    "custom-mobilidata-dtapEnvironment": "production"
}
Tags:
Last updated on by taeyma41