Sharing Operations Data Among Agencies (2014) / Chapter Skim
Currently Skimming:
Pages 35-40
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 35... ...
35 Not all data sharing initiatives are implemented in the same manner. Governance structures, personalities, implementation details, and other factors can heavily influence whether operations data sharing ever takes place, and if it does take place, how successful might it be in producing meaningful, quantifiable benefits.
|
From page 36... ...
36 • Rights to share the data with operational partners including: – Other government agencies that help the procuring agency in its mission, – Consultants working on behalf of the procuring agency, – University researchers working on studies on behalf of the procuring agency, and – To do all of the above even for partner agencies outside of the geography of the procuring agency. • Rights to summarize the data for use in: – Variable message signs, – Websites that are sponsored by the procuring agency, – Social media postings (such as Facebook, Twitter, etc.)
|
From page 37... ...
37 Maintenance of sensor systems can be problematic because of funding or other issues. Significant effort has gone into various strategies for the analysis of data quality, including imputation algorithms for accounting for poor quality data or missing data (50–53)
|
From page 38... ...
38 shared between agencies. Additional work is always necessary to enable a mechanism for data sharing regardless of what type of connection is made between the agencies.
|
From page 39... ...
39 this report, many vendor-provided ATMS have historically utilized proprietary protocols or data formats that limited the amount of data that could be shared. As transportation operations data sharing becomes more common, agencies have revised their requirements generation process to include data feeds to third parties.
|
From page 40... ...
40 – Reintegrating data into native systems that are not standards compliant can be cumbersome; and – Costs associated with creating data feeds or ingesting data feeds. Any one of these issues, if not properly dealt with, can be enough to slow or halt a data sharing initiative; however, all agencies interviewed commented that none of the issues should be a reason to avoid data sharing.
|
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.