The MSI data service

The MSI data service

Introduction

The data service MSI makes information available from traffic signs that have a variable picture. A typical example of such a sign is the MSI as they are used in the signaling of the Dutch national road network. Another example is a tilting roller board with which traffic signs can be presented. Currently only MSIs are supported.

Response structure

The response body contains the XML message variable_message_sign_events. The scheme of the message can be found in the TODO, Variable Message Sign interface scheme. This message contains the following elements:

meta element

This element contains information about the response message and the request that formed the basis for it. The following parts are included.

element meaning type example
msg_id UUID of the message, for the purpose of tracebility. UUID 12345678-1234-1234-1234-123456789012

The event element

The Event element contains the (new) information from a measurement point about one of the aspects that the measurement point has. These aspects are:

  • lanelocation indicates the location of the sign with a road, track, strip and kilometer indication.
  • display indicates which image is shown by the board.

Below is described what information can be given in the variable_message_sign event.

element aspect at meaning type example
ts_event all   The time at which the event is registered. On this basis, the event is counted as a time window. [ISO8601] 2014-09-09T15:02:13Z
ts_state all   The time at which the condition reported in the event arose. [ISO8601] 2014-09-09T15:02:12Z
sign_id all   The identity of the board or MSI UUID 12345678-1234-1234-1234-123456789012
road lanelocation   Indication of the road where the sign is placed. string A15
carriageway lanelocation   Indication of the roadway where the sign is placed. string L
lane lanelocation   Indication of the lane where the sign is placed counted from the WOL (Road Orientation Line). int 2
km lanelocation   The kilometer position along the road, calculated from the start of the hectometering. decimal 12.369
blank display f The image shown is blank. n/a  
speedlimit display fr The image shown is the maximum speed indicated. int 90
lane_open display f With a green arrow is indicated that the strip may be used n/a  
lane_closed_ahead display f The strip is closed down in the traffic flow. Traffic must be inserted in the indicated direction (left or right). element
merge_right
merge_left
lane_closed display f The strip is closed for traffic n/a  
restriction_end display f End of restrictions. n/a  
unknown * display f The image shown can not be determined with certainty. n/a  
discontinued n/a   The traffic sign has been removed. No events are reported anymore n/a  

A number of images have extra attributes. This is indicated in the table above in the column “at”. The letters in the column have the following meaning:

  • f The image has the flashing attribute. With a boolean value is indicated whether the displayed image requires extra attention by means of flashing lights, the so-called “flashers”. With true these are enabled, with false not.
  • r The image has the attribute red_ring. This indicates with a boolean value whether the red border of a prohibition sign is displayed or not. With true, it is present, with false not.

*unknown The unknown status can be given in the data feed in one of the 7 situations below:

  1. Lamp status is “lampfout” (lamp fault), “aansturing_fout” (control error) or “defect” (defective); Image is not displayed in MTM. In MTM the MSI is then on BL (Blank).
  2. “MSI fataal status” (fatal status) is true; No image can be displayed on the MSI. In MTM the MSI is then on BL (Blank).
  3. “OS fatale fout” (OS fatal error) is true; No image can be displayed by the OS on the MSI. In MTM the MSI is then on BL (Blank).
  4. “OS koud startend” (OS cold starting) is true; The Os has just been rebooted by an Engineer. In MTM the MSI is then on BL (Blank).
  5. “Verkeerscentrale in sync” (Traffic center in sync) is not true; This occurs e.g. if the messages from MTM to the ESB no longer come through or if the ESBXML is not correctly loaded after a database change. All images from that center will then show Unknown while in MTM you can see images.
  6. “OS mode is “local”; In MTM, images are shown in this OS mode in the ESB. Depending on the situation where an OS local has fallen, these images are more or less reliable, which is why ESB is here the design choice made to put the images on Unknown.
  7. “OS mode” is “Idle”; No images in MTM are shown in this mode.