Skip to main content

Currently Skimming:


Pages 15-17

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 15...
... The level of aggregation and format of this data varies. The data structure and related tools 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)
From page 16...
... Before the transfer, the data flow includes the application of the Format Validation Tool and Data Quality Tool 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 time-based event data or do not want to transform their Vendor Outputs into the Event Data Files.
From page 17...
... with many doors, such as platform crowding analysis in rail stations, a mid-level of aggregation is needed. These transit agencies have the option of creating a file that summarizes passenger events by stop visit and by individual train car rather than for the entire train consist.


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.