Skip to main content

Currently Skimming:

Summary
Pages 1-6

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 1...
... This report proposes a data structure for storing data from bus and rail ITS, including vehicle locations, passenger counts, and fare collection information. It also describes how the data structure can facilitate a process in which transit agencies receive ITS data from vendors, organize and validate it, and use it to calculate key performance indicators (KPIs)
From page 2...
... The FTA allows multiple methods for APC certification. While adoption by a transit agency of the proposed data structure would not directly result in FTA-compliant NTD ridership reporting, this report does provide a draft specification for APC data storage.
From page 3...
... The data structure and related tool requirements are intended to support the management of data both for transit agencies that receive very detailed data (for example, heartbeat vehicle location data, individual timestamped boarding records) as well as agencies that receive more processed data (such as data assigned to a trip and stop or summarized at a station by time period)
From page 4...
... Before the transfer, the data flow includes the application of the Format Validation and Data Quality Tools to ensure that the data provided is in the correct format and that unique identifiers across internal and external reference files match. • Path if using only Summary Data Files: The second path, shown with the dotted blue arrow, can be used by transit agencies that do not receive detailed time-based event data or do not want to transform their Vendor Outputs into the Event Data Files.
From page 5...
... Processes to Minimize Costs There is an upfront cost to transit agencies to convert their existing Vendor Outputs or internally defined data structures to the proposed structure. Unlike the standard tools discussed in the prior section, this effort is likely to require customized support for individual transit agencies, as each transit agency currently has an individualized method for storing data.
From page 6...
... to develop a governance group and to provide a forum for communication about the data structure.


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.