Skip to main content

Currently Skimming:


Pages 45-58

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 45...
... 45 This chapter examines proprietary data acquisition in greater detail by looking at the policies and practices of four state DOTs and one MPO. The study team collected information by interviewing agency staff and reviewing agency procurement documents.
From page 46...
... 46 Practices on Acquiring Proprietary Data for Transportation Applications • Guarantee data accuracy of ± 4 mph; • Provide access to the analytics tools, including region explorer, massive raw data downloader, congestion scan, trend maps, performance charts, performance summaries, bottleneck rankings, and user delay cost analysis; • Provide data in XML format and at an interval that would let Ohio DOT's traffic information systems produce accurate and timely traffic information; and • Make real-time speed data available to the agency's central control system through a vendor's server. The RFP stated that Ohio DOT intended to use real-time data for transportation purposes, including the operation of freeway management systems, the OHGO app and BuckeyeTraffic.org (both for color-coded speed range maps)
From page 47...
... Case Examples 47 Use Cases Speed data The main use cases for the real-time speed data are DMS, 511 services, and incident recovery monitoring. The historical speed data set has been used in a wide range of applications, such as before-and-after studies and calibration and validation of statewide and MPO travel-demand models.
From page 48...
... 48 Practices on Acquiring Proprietary Data for Transportation Applications too narrow of a time period. This feature potentially mitigates concerns about particular firms being targeted.
From page 49...
... Case Examples 49 all data received from the selected vendor would be post-processed by the agency's STOC. Once processed, it would be used to alert the public of traffic conditions via DMSs and the agency's 511 website.
From page 50...
... 50 Practices on Acquiring Proprietary Data for Transportation Applications from its disclosure or use. Under Wisconsin Statute § 19.36(5)
From page 51...
... Case Examples 51 Peer Advice Obtaining probe data to monitor traffic conditions is a much less-expensive option than installing sensors on roadways in areas under travel advisory during freeway construction. Agencies can modify their probe data coverage in the future if needs change; whereas, permanent sensor installations do not afford this flexibility.
From page 52...
... 52 Practices on Acquiring Proprietary Data for Transportation Applications Planned uses of the data included providing traveler information to the public, obtaining and archiving historical traffic data to inform agency planning, tracking historical changes in traffic volumes, and using traffic data to report performance and support the operation of freeways and the arterial system. In addition to describing the Arizona DOT's data needs, the RFP stipulated that the winning contractors shall be available to all jurisdictions within the state of Arizona that request trafficdata services and that utilize federal, state, city, county, or any other jurisdictional funding for such requests.
From page 53...
... Case Examples 53 both the agency and taxpayers would benefit from making data acquisition more efficient and giving multiple jurisdictions access to data. Strong partnerships between the Arizona DOT and MPOs and other local agencies have also facilitated adoption of the on-call contracting strategy.
From page 54...
... 54 Practices on Acquiring Proprietary Data for Transportation Applications reflect traffic congestion better than traditional measures such as volume-to-service flow ratio. Analysis of probe-speed data by the KTC–KYTC team is being used to develop comprehensive sets of congestion measures for statewide network screening and project selection.
From page 55...
... Case Examples 55 • internal crowdsourced activities throughout the state, and • DMS. KYTC aggregates data from these sources and harmonizes them based on location and time.
From page 56...
... 56 Practices on Acquiring Proprietary Data for Transportation Applications contributed to its occurrence. This information facilitates after-action reviews and strengthens KYTC's incident management program, helping the agency improve its responses to future incidents.
From page 57...
... Case Examples 57 Atlanta Regional Commission Experience The Atlanta Regional Commission (ARC) is a federally designated MPO that collaborates with state and local transportation agencies and governments to produce and manage the Regional Transportation Plan.
From page 58...
... 58 Practices on Acquiring Proprietary Data for Transportation Applications around the Atlanta metropolitan area and the seven Transportation Management Association territories. Staff in the Mobility Services Division developed the data specification and worked with the budget office to complete the acquisition.

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.