Skip to main content

UC 10: Spilled load warning

Use case specifics​

Definition​

In Flanders, there is little-detailed information on types of ‘foreign’ object(s) that is/are present on the road. It has been defined as ‘Spilled load’ as common denominator. A more correct definition would be abnormal material(s) on the road that can cause damage to passing vehicles, can hinder traffic flow and/or can cause unsafe maneuvers by anyone passing by. It can be entire truckloads of materials, or a single brick fallen from a trailer, tire parts, parts of vehicles, fallen branches or trees etc….

Opposite direction for event: If there is no hard deviation between the opposite lanes, the event is always duplicated (in PIP) for the opposite direction. This guarantes that all possible involved road users will get the warning message. On roads with separate tracks, there is no duplication. Except for weather oriented messages. If there is a road separation is based on the road geometry in OSM.

Operational Road Environment​

  • Territory: Flanders
  • Border passing cases: All of Flanders roads. The quality of coverage of the government information sources is best on highest levels road classes.
  • Road class: N/A
  • Time restrictions: none
  • Weather restrictions: none
  • Special restrictions:none
  • Vehicle classes: N/A

MI & Historical archive​

DENM information​

The data is presented as a DENM message, with main characteristics: Cause and sub cause codes are:

CausecodeDescriptionSubcausecodeDescription
10Hazardous location - Obstacle on the road0unavailable
1Shed load
2Fallen trees
3Parts of vehicle
4Large objects
  • Default time to live 600 seconds -10 minutes. However, Mobilidata will recreate new DENM’s to cover a time period upto 1 hour after initial notification of a spilled load based on road user feedback alerts. Also: this 1-hour timer is reset after receiving an ‘upvote’ on an existing Mobilidata DENM via RUF. Spilled load notifications coming from the Flanders Traffic center are kept alive as long as the traffic center keeps them alive.
  • Lat/Long position of original situation detection

MI headers​

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

Historical archive​

As well the original messages as the RUF messages ar stored in the historial database.

Data sources​

  1. Flanders traffic center notifications: own and trusted 3rd party observations and manually generated alerts DATEX point notification of location of observation (any position on highway/and larger secondary roads)

  2. 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.

Alert cancelling​

  1. Flanders traffic center cancels the alert on their DATEX channel.

  2. RUF (road user feedback – upvoting/downvoting) 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.

RUF/ES Cooperative information options​

For this use case, it is (strongly) recommended to participate in the Mobilidata feedback channel.

  • ES (event sourcing – creating new information points) is possible in the form of ‘a new event’ information. The user can indicate that at the location of creation of his/her ES a new event is applicable.
  • Feedback only (Road user feedback - upvoting/downvoting of existing notifications).

Message example​

UC 10 Message Example
{
  "shardId": "1",
  "latitude": "51.244293",
  "quadTree": ",120202130230230311,1202021302302,",
  "causeCode": "10",
  "longitude": "4.426349",
  "shardCount": "1",
  "messageType": "DENM",
  "publisherId": "BE00004",
  "serviceType": ",HLN-OR,",
  "subCauseCode": "4",
  "publicationId": "BE00004:DENM_OBJECTS_ON_THE_ROAD_02",
  "baselineVersion": "2.1.0",
  "protocolVersion": "DENM:1.3.1",
  "originatingCountry": "BE",
  "custom-mobilidata-useCase": ",10,",
  "custom-mobilidata-timestamp": "1737369931786",
  "custom-mobilidata-alertCCodes": "61",
  "custom-mobilidata-publisherType": "PIP",
  "custom-mobilidata-baselineVersion": "1.0.0",
  "custom-mobilidata-dtapEnvironment": "production"
}
Tags:
Last updated on by taeyma41