Skip to main content

6.3

6.3​

Resolved Issues - Sept 20, 2018​

  • Lane blockage pattern could generate 'OPEN BLOCKED' or 'CLOSED BLOCKED'
  • Traffic event comments don't store when comment exceeds 256 characters
  • Repeated planned events terminate when deactivated before deactivation time
  • API response code [OPT: TO {inc road2} BEFORE/BEYOND/AT downstream inc loc] failing to generate message
  • McCain Data Pump does not connect (or reconnect) to RMP if started before RMP
  • VDS property window does not include lane data when zone 0 corresponds to lane 2
  • Scheduled Messages could not add/remove signs
  • Apostrophes in message schedules create errors in error log
  • Verified station volume and station occupancy against on paper calculation. Traf Segments having only McCain source, only RTMS source and combination of RTMS + McCain as source were tested.

Additions/Improvements - Sept 20, 2018​

  • Added API response message character count and warning message based on configurable message length
  • New CMS template variable: [MULTI-LINE LANE/SHOULDER BLOCKED/CLOSED]
  • New CMS template variable [amber alert license long state] and [amber alert license short state] replacing [amber alert license state]
  • CMS templates for Amber Alerts will need to be configured to use the new variables
  • New config key in ApplicationSettings.json (WarningLengthOfApiResponse) for configuring API response message length warning
  • Accept button for response will be disabled if users have unsaved changes
  • Drakewell and TomTom history now logged to respective tables
  • TomTom Service logs error "Empty TomTom Data Error" if the live feed has no data
  • Improve memory performance of McCain data pump
  • Improve GuiAgent stability when handling DMS status updates
  • Added stability to DMS to better handle bad responses coming from faulty signs
  • Added configuration to hide manual refresh/refresh time for images
  • Modified code to append date on log file also avoid overwriting existing log file.