Notes
Slide Show
Outline
1
Integrating Clarus Data with the 511 New York Traveler Information System
  • Road Weather Management Stakeholder Meeting
  • September 8th, 2011
2
Agenda
  • Project Background & Goals
  • Inputs into Road Segment Alerting
    • Why is Clarus Data Important?
  • About 511NY
  • Demonstration Scenarios
  • Observations and Results
  • Next Steps
  • Questions?
3
Project Background
  • Project part of the Federal Highway Administration (FHWA) Broad Agency Announcement
    • Research on Clarus  System Data
    • Winter/Spring 2010
    • Solicitation Number DTFH61-10-R-00015

  • “…develop new or improved road weather management/operations procedures, create innovative user interfaces, and develop new applications including weather-responsive traffic management tools.”
4
Project Background
5
Project Goals
  • Collect and integrate Clarus observations and disseminate road-segment alerts for use in the New York 511 system and Connected Vehicle Program



6
Road Segment Alerting Inputs
7
NYSDOT Road Network
  • Project coverage – Two New York transportation corridors
8
Road Segment Alerting Inputs
9
Road Segment Alerting Inputs
10
Why is Clarus data valuable for Road Segment Alerting?
  • Alerting on observations from Airports…
    • Typically 1-3 miles (or more) from a major roadway
    • Report atmospheric (non-roadway) variables only
      • Air Temperature, Wind Speed & Direction…
11
Why is Clarus data valuable for Road Segment Alerting?
12
Clarus Stations Used
13
Clarus RWIS versus Roadway
  • Radius of influence around the RWIS selected from Clarus
    • 8 miles
14
Road Segment Alerting Inputs
15
Road Segment Alerting Inputs
16
Road Segment Alerting Inputs
17
Road Segment Alerting Inputs
18
Road Segment Alerting Inputs
19
Architecture & End Users
20
About 511NY
21
About 511NY
22
About 511NY
23
Two Demonstration Scenarios
  • March 7th, 2011
    • Snow storm
  • April 28th, 2011
    • Severe weather outbreak
24
Scenario #1 – March 7th, 2011
25
Scenario #1 – March 7th, 2011
26
Scenario #1 – March 7th, 2011
27
Scenario #2 – April 28th, 2011
28
Scenario #2 – April 28th, 2011
29
Scenario #2 – April 28th, 2011
30
From the Traveler’s Perspective



31
From the Traveler’s Perspective



32
 Observations & Results
  • Both NYSDOT and FHWA evaluated the pre-production 511NY system over a 3-month time period.
    • Alert Prioritization
      • Standardize order of alerts to display (radar versus warnings, etc.)
    • Data Quality
      • RWIS data quality is key to ensure data can be utilized for alerting
    • Information Clarity
      • Keep public perception/interpretation in mind…keep it simple
      • Provide additional information on alert types
      • Standardize the colorization and terminology
      • Cease use of Flood Warnings…keep Flash Flood Warnings
    • Thank you NYSDOT & FHWA!
33
Next Steps
  • Simplify and clarify the alert results
34
Next Steps
  • Simplify and clarify the alert results
  • Explore integration of road segment alerts into 511NY production system
35
Next Steps
  • Simplify and clarify the alert results
  • Explore integration of road segment alerts into 511NY production system
  • Integrate road segment alerts into the NY Connected Vehicle program
36
Other Uses for Road Segment Alerting
  • XML feed can be integrated into many different applications
    • Connected vehicle initiatives
    • 511 programs
    • Traffic Management Centers
    • Traffic modeling input
    • Signal timing
37
Thank You