As discussed at the 2017 TRB Annual Meeting
Examples of recent headaches with Data Management:
Addresses workforce issues. A Data Officer could go into a public agency similar to how Code for America works
A lot of time is wasted having to deal with different variable names and terminology. Zephyr sets standard variable names and units [ i.e. commuter_rail vs CommuterRail ]
There should be a periodic update of standards so that they do not become stale or forked. The Zephyr board could decide each year whether or not to revisit each standard. We also need a technicals standing body to monitor data standards to inform the board.
A standard protocol for managing data projects or developing data resources.
Could include:
Zephyr can help come up with example contract and licensing language to facilitate data sharing with researchers and other stakeholders while protecting privacy.
Similar to survey methods manual, but for other data sources.
How to grade a dataset: -Completion -Sample size -Representation
A dataset grade would have to depend on the specific application.
Potential actions:
For data sets that are unique to transportation, Zephyr can set standards but need to talk to public agencies and groups that collect data.
Private data providers.
After relationship, both groups work together to get the right data. Prevent each public agency from having to determine independently examine each private companies’ data.