Skip to main content

UC 12: Road works warning

Operation use case​

In this use case, warnings are made for static roadworks that cause disruption to traffic. The road is partially or completely closed. Fixed location, so not including the crash absorber accompanied mobile road works.

The warning message is issued for upstream traffic, and is present during the duration of the roadworks.

Road users will get a warning message for upcoming roadworks. Determination if an alternative route to be taken, and which one, is not part of this use case and up the road user (and possible navigationsystem). The eventual speed limitation in the relevance zone is included in the message if it is known at the source.

Operational Road Environment​

  • Territory: Flanders
  • Border passing cases: Road works usually stop around the border, if they continue, these will often be 2 separate sites
  • Road class: all roads
  • Time restrictions: none
  • Weather restrictions: none
  • Special restrictions: none

Data sources​

  • the DATEX II feed of the Flemish Traffic Centre (VVC): covering the road network of then Flemish regional road authorities. From this feed, the planned mobile road works zones are filtered out. Information on mobile roadworks is covered in Mobildata in use case 6 – active service vehicle location: crash absorbers, mowers, …
  • GIPOD: the Generic Information Platform Public Domain: covering the road network of local road authorities. This database contains the longer term planning of all activities causing hindrance to the public domain. Local Road authorities and all active in the public domain are obliged to enter their planned activities in this database. Some of these (many) plannings are entered precise and accurate, others are less precise. Criteria were defined to filter out events/roadworks without impact on traffic, and also filter out insufficiently precisely timed events. This to avoid an overload of false positive roadworks notifications.
  • Event Sourcing from RUF: new reports of road works by connected road users.

MI & Historical archive​

DENM information​

  • Default time to live 24 hours: If the roadwork is over a longer period, the detectionTime and referenceTime values are adjusted to the new value (detectionTime + duration) and the DENM is updated. Only in the first instance of the roadworks DENM, the detectionTime and referenceTime can therefor be different, in all updated DENM's they are the same.
  • Lat/Long position of event: The position of the reference point can be updated if a better data source is available, or RUF information is indicating.
  • Awareness zone(s) defined, upstream the lat/long position
  • History (relevance) zone(s) are optional, depending on quality of source information. The history zone is representative for the length of the roadworks area along the route. (The definition of history zone is the route that the perceptive vehicle has laid down.)
  • Speed limit of actual road works zone can be included. !: gradual speed limit reductions before the road works zone is not available in the DENM message. Only the speed for the history zone is provided.

Cause and subcause codes are:

CausecodeDescriptionSubcausecodeDesctiption
3roadworks0details unavailable
1major roadworks, road closure
2, 3not used
4short-Term Stationary Roadworks, Lane closure
5, 6not used

MI Headers​

Capability descriptor:

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

Historical archive​

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

RUF and sourcing​

RUF messages with reference to the actionID in the originating DENM message will be aggregated and anomynously sent to AWV in order to correct the source data if possible. See RUF page in Messages section.

Risk and remarks​

/

Alert cancelling​

Alerts are kept alive as long as they are available at the source for DATEX and GIPOD.

Alerts generated by RUF/Event sourcing by road users have a time to live of 24 hours. Every upvoting/confirming resets the 24-hour timer to restart the 24h count-down.

Message example​

UC 12 Message Example
{
  "shardId": "1",
  "latitude": "51.035872",
  "quadTree": ",120202122031210330,1202021220312,",
  "causeCode": "3",
  "longitude": "3.106774",
  "shardCount": "1",
  "messageType": "DENM",
  "publisherId": "BE00004",
  "subCauseCode": "0",
  "publicationId": "BE00004:DENM_ROADWORKS_02",
  "baselineVersion": "2.1.0",
  "protocolVersion": "DENM:1.3.1",
  "originatingCountry": "BE",
  "custom-mobilidata-useCase": ",12,",
  "custom-mobilidata-timestamp": "1737369958958",
  "custom-mobilidata-alertCCodes": "702,401",
  "custom-mobilidata-publisherType": "PIP",
  "custom-mobilidata-baselineVersion": "1.0.0",
  "custom-mobilidata-dtapEnvironment": "production"
}
Tags:
Last updated on by taeyma41