Skip to main content

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


Pages 38-45

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 38...
... In that case, the Data Transfer Tool is used to transform Event Data Files to Summary Data Files and the Format Validation Tool and Data Quality Tool are applied to both the Event Data Files and the Summary Data Files. Figure 7 shows the entire data flow in the case that a transit agency is using only the Summary Data Files, rendering the Data Transfer Tool unnecessary.
Read the entire page →
From page 39...
... REQ. ID REQUIREMENT TEXT 1 The data files, fields, and types shall conform to the proposed data structure.
Read the entire page →
From page 40...
... best practices discussed in Chapter 6 provide guidance for how to address errors flagged by the Format Validation Tool. 5.3 Data Quality Tool There are many different types of data quality checks, some of which may require customization based on features of the agency's vehicles, route structure, and other variables.
Read the entire page →
From page 41...
... Passenger_events, Stop_visits 8.0 The tool shall conduct the following validations for fare transactions: 8.1 • The value of each fare transaction shall be within a user-configured range, which may vary based on the transaction type, fare media type, or another characteristic. Fare_transactions, Stop_visits, Station_activities 8.2 • The number of fare transactions for a stop visit or at a station shall be within a user-configured percentage range of boardings for that stop visit or entrances at that station.
Read the entire page →
From page 42...
... 2 The tool shall process the Event Data input files and generate the three Summary Data Files (Stop_visits, Trips_performed, and Station_activities) in conformance with the data structure.
Read the entire page →
From page 43...
... 1.1 • Schedule deviation for an individual vehicle trip at an individual location, such as a stop, is defined as the difference between the time at which a trip was scheduled to arrive at and depart from the location and the time that it actually arrived at or departed from the location. Schedule deviation may be within, before or after user-defined thresholds, indicating the trip is on time, early or late at that location.
Read the entire page →
From page 44...
... 1.2 • Average load for a trip is defined as the weighted average load by distance (i.e., the sum of the departure loads of the vehicle trip at each stop, each multiplied by the distance traveled to the vehicle trip's next stop, divided by the total distance traveled by the vehicle trips)
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 →

Key Terms

  • transit agencies
  • data structure
  • event data
  • summary data
  • fare transactions

  • data quality
  • vary based
  • requirement text
  • tool requirements
  • field name

  • transit agency
  • format validation
  • quality tool
  • vehicle trip
  • fare media

  • individual vehicle
  • route type
  • individual location
  • distance traveled
  • data transfer

  • fields required
  • data flow
  • validation tool
  • scheduled trip
  • transfer tool

  • data fields
  • proposed data
  • priority data
  • data issue
  • core data


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