Skip to main content

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

5. Tool Requirements
Pages 41-49

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 41...
... REQ. ID REQUIREMENT TEXT APPLICABLE FILES 5.2 • All stop_sequence values for a distinct trip_id shall be in ascending order when ordered by actual arrival and departure times.
Read the entire page →
From page 42...
... to flag devices that require maintenance; or • Analyze discrepancies in AVL arrival/departures compared to APC arrival/departures across vehicles/devices to flag issues. 5.4 Data Transfer Tool The Data Transfer Tool is used to generate the Summary Data Files from the Event Data Files and the Supporting Data Files (Table 18)
Read the entire page →
From page 43...
... , which shall be the duration between consecutive trips, aggregated by location or route, and across time periods. 1.1 • The headway at a location for all routes at that location is calculated as the difference between a trip's arrival or departure time at the location and the previous trip's arrival or departure time regardless of route.
Read the entire page →
From page 44...
... , which shall be boardings, alightings, and load for each location, trip, and route aggregated across daily time periods. 1.1 • Average load on a route at a specific location, which may be a stop, is defined as the total departure load for all vehicle trips on that route departing that location in the time period divided by the total number of vehicle trips on that route departing that location in the time period.
Read the entire page →
From page 45...
... Field Name File date Stop_visits trip_id_performed Stop_visits trip_id_scheduled Trips_performed stop_id Stop_visits stop_sequence Stop_visits distance Stop_visits route_id Trips_performed actual_arrival_time Stop_visits actual_departure_time Stop_visits Table 26. Speed/runtime.
Read the entire page →
From page 46...
... . As these tools also integrate GTFS and Supporting Data Files, agencies should ensure that the GTFS and supporting files correspond to the same time period as the ITS data.
Read the entire page →
From page 47...
... Use distinct tools to process each set of Vendor Outputs into either the Event or Summary Data Files; or 2. Bind Vendor Outputs prior to using a tool to process the combined Vendor Outputs into either the Event Data Files or Summary Data Files.
Read the entire page →
From page 48...
... or similar. For example, if in using the data quality tool, unrealistic bus speeds of 60 mph on a trip are found, the fields used to derive the speed would be set to NA, as if the data had been missing.
Read the entire page →
From page 49...
... Agencies will need to convert scheduled times from GTFS from the HH:MM:SS format to POSIX time for integration in the data structure. If desired, agencies can maintain additional time fields using the HH:MM:SS format for readability.
Read the entire page →

Key Terms

  • event data
  • data quality
  • validation tool
  • tool requirements
  • format validation

  • data transfer
  • vehicle trip
  • requirement text
  • vary based
  • quality tool

  • transfer tool
  • fields required
  • data fields
  • data structure
  • analysis tool

  • individual vehicle
  • vehicle trips
  • route type
  • individual location
  • distance traveled

  • priority data
  • core data
  • data issue
  • vehicle type
  • transit agency

  • field name
  • following validations
  • route departing
  • name file
  • text applicable


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