Skip to main content

Improving Access and Management of Public Transit ITS Data (2022) / Chapter Skim
Currently Skimming:

3. Roadmap
Pages 16-19

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 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.
Read the entire page →
From page 17...
... Note on Implementation: Transit agencies may process Vendor Outputs into the Event or Summary Data Files themselves, or they may request that vendors do the processing. Third parties may also develop tools for this processing; however, Vendor Outputs typically are specific to each agency, which may limit the potential for shared tools.
Read the entire page →
From page 18...
... In addition, if an agency desires to use the Event Data Files to store data on vehicle locations, passenger events, and fare transactions, they would use these files to populate the required files. Therefore, they are designated as conditionally required.
Read the entire page →
From page 19...
... Summary Station_activities Conditionally required Summarized transactions, entries, and exits by stop or station and time period for each service date (for events not associated with a trip)
Read the entire page →

Key Terms

  • event data
  • summary data
  • data structure
  • vendor outputs
  • service date

  • entire train
  • gtfs identifiers
  • record boardings
  • train consist
  • blue arrow

  • data quality
  • share data
  • proposed data
  • data formats
  • data flow

  • data transfer
  • files themselves
  • using event
  • individual train
  • files allow

  • timestamped event
  • allow transit
  • files consist
  • analysis comparing
  • events associated

  • unique identifiers
  • historical consistency
  • scheduled trips
  • transfer tool
  • date uniquely


    • 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.