Sharing Operations Data Among Agencies (2014) / Chapter Skim
Currently Skimming:
Pages 48-61
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 48... ...
48 RITIS planning began in 2002 with a grant from the federal government issued to the Metropolitan Washington Council of Governments (MWCOG)
|
From page 49... ...
49 Table A1 provides a list of these and other expected RITIS users in each established category. Use cases for each of these user groups were created to help justify account requests and stakeholder needs.
|
From page 50... ...
50 Early Data Provider Analysis Within RITIS, all participating systems can exist as providers and/or users of particular classes of information. Any single system can be a data provider, a data consumer, or both.
|
From page 53... ...
53 RITIS Capabilities RITIS was designed for two primary capabilities: the exchange of real-time transportation-related information, and the archiving of regional transportation-related data. Real-time Information Exchange RITIS information is available to participating agencies through electronic data feeds and a web interface.
|
From page 54... ...
54 FIGURE A3 A high level screenshot of the real-time RITIS user interface showing several layers of data visualization from comparative traffic flow, to weather, incidents, and even CCTV. FIGURE A4 Road weather stations (RWIS)
|
From page 55... ...
55 FIGURE A5 Evacuation data within RITIS is shared between agencies to help understand how to manage traffic control points, visualize hospital beds, routes, and even equipment staging areas. FIGURE A6 Information on real-time train, subway, and bus AVL and schedule data are visualized.
|
From page 56... ...
56 to derive vehicle hours of delay, user costs, and fuel consumption based on the coupling of probe data readings with volume measurements. When this new functionality was completed, these features were shared with other RITIS participating agencies that are providing probe data.
|
From page 57... ...
57 FIGURE A8 Incident timelines show the relationship between agency notification data, arrival times, lane closures, and traffic queues. FIGURE A9 Most RITIS visualization tools provide an overview of the data; allowing the user to zoom to selected performance measures, and then bringing up specific details upon demand.
|
From page 58... ...
58 FIGURE A10 The RITIS Incident Cluster Explorer allows agencies to analyze trends in accident data, generate histograms and other charts, graphs, and statistical functions. FIGURE A11 Local and regional incident, construction, or special event heatmaps for user-specified date ranges.
|
From page 59... ...
59 FIGURE A12 Incident cluster diagrams give users a better idea of exactly how many events are occurring in specific regions. FIGURE A13 Charts and graphs allow users to analyze incident response times, clearance times, or event types by roadways.
|
From page 60... ...
60 FIGURE A14 An RWIS data explorer allows an agency to see how localized weather, visibility, surface temps, etc., can affect traffic speeds, volumes, and accidents near RWIS stations. FIGURE A15 User Delay Cost analytics in RITIS help agencies understand the financial and environmental impact of congestion.
|
From page 61... ...
61 previously, is a common operating platform that shows fused data in a central viewer. Because some agencies have not been successful in fully integrating data feeds in a meaningful way into their own systems, many operators rely heavily on the RITIS website for viewing real-time data more so than they rely on their own native systems.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.