Notes
Slide Show
Outline
1
Use Case #5: Enhanced Road Weather Content Enabled by Clarus
Sept. 8, 2011
Leon F. Osborne
leono@meridian-enviro.com
2
Clarus Use Case #5 Overview
  • Goal:
  • Use Clarus data to develop enhanced road weather information for travelers.


  • Methods:
  • by leveraging the multi-state nature of Clarus to create a multi-state traveler information platform


  • by applying Clarus data to develop enhanced road / weather forecasts that can alert drivers of conditions before they occur
3
Use Case #5 Design
4
Message Generation Engine
5
Message Generation Engine
  • For a given information ‘segment’:


  • Identify which data are available
    • DOT, Clarus ESS, road/weather analyses/forecasts


  • Separately analyze data streams to determine if a problematic condition is indicated


  • Progress through appropriate path in a decision tree
    • Based on data availability and consistency (or lack thereof)


  • Generate a message and GIS attributes appropriate for the ending point in the decision tree


6
Multi-State Web Portal
7
ATIS Web Portal
8
ATIS Web Portal Text Content
9
ATIS Web Portal Text Content
10
Multi-State Travel Weather
11
Findings
  • Algorithms for making sense of incomplete and/or conflicting data are vital


  • Need to provide actionable information without providing too much information
    • Overstating what is known can lead to distrust in the system and heightened liability concerns.
    • Conditions vary over both time and space – how do you convey the threat without overwhelming the user?
12
Findings
  • There may be more value in multi-state and forecast information via a web portal relative to telephony systems
    • “a picture is worth a thousand words”


  • With current data availability, the system holds more promise for alerting travelers to imminent travel problems than for predicting the return of good travel conditions
    • Early sensor- or model-based detection
    • Forecast conditions
13
DOT Perspectives
  • The concepts have been well-received by both the participating DOTs and public evaluators


  • Reducing liability, rather than increasing it, is a major consideration in deciding whether or not to implement


  • The system would potentially benefit from more detailed agency data (e.g., IT-equipped snowplows)


  • Agreement on conditions and color schemes elusive
14
Research Needs/Gaps
  • There could be considerable benefit to closing more of the ‘loops’ in the system
    • Assimilate DOT road condition reports into pavement model
    • Track and apply data on maintenance activities


  • The concept may be more amenable to smartphone applications than to telephony-based traveler information


15
Contact Information
  • John Mewes  -  Meridian Environmental Technology, Inc.
  •     jmewes@meridian-enviro.com
  • Leon Osborne  -  Meridian Environmental Technology, Inc.
  •     leono@meridian-enviro.com
  • Julie Theisen  -  Meridian Environmental Technology, Inc.
  •     theisen@meridian-enviro.com