Skip to main content

Currently Skimming:


Pages 11-14

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 11...
... These requirements should be factored into the development of a data standard. • Transit ITS data is often aggregated or integrated with other data sets to maximize transit ITS value to transit agencies.
From page 12...
... The primary intended use of the data structure is for internal use by transit agency staff to manage and analyze their historic ITS data. If transit agencies choose to share any of this data publicly, they should consider potential privacy concerns with some of these data types, particularly fare transaction data that pertains to an individual fare medium (e.g., card)
From page 13...
... Section 5.5.1 indicates which fields are required to evaluate each KPI and which files contain these fields. Some fields that are necessary to evaluate KPIs are optional fields in the data structure so that the data structure is flexible enough to accommodate transit agencies with different needs and data availability.
From page 14...
... The data structure also does not require coverage across all three ITS data types or across all vehicles or modes. Depending on data availability, transit agencies also could use the entire data structure or portions of it, either using some but not all files in the structure or only using the structure for specific modes.


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.