Skip to main content

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

2. Research Findings, Objectives, and Approach
Pages 11-15

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 11...
... • Standards require ongoing advocacy and education to be widely adopted. • Data standard development should consider the cost and effort of implementation, including how a standard will integrate with transit agency operational procedures.
Read the entire page →
From page 12...
... The primary intended use of the data structure is for internal use by transit agency staff to manage and analyze their historic ITS data. If transit agencies choose to share any of this data publicly, they should consider potential privacy concerns with some of these data types, particularly fare transaction data that pertains to an individual fare medium (e.g., card)
Read the entire page →
From page 13...
... Feature Definition Outcome-oriented • Data fields included and data table organization support calculation of KPIs. • Documentation specifies which data fields are required for various types of downstream analyses.
Read the entire page →
From page 14...
... Additional explanatory information related to best practices that may vary across agency contexts is included separately for reference. 2.3.3 Flexible As described above, the proposed data structure is designed to function for both transit agencies that desire access to the most detailed records from their AVL, APC, and AFC systems, such as individual boardings, and ramp deployment times, as well as for transit agencies that collect data only at a stop visit, station, or trip level.
Read the entire page →
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)
Read the entire page →

Key Terms

  • transit agencies
  • data standard
  • public transit
  • transit agency
  • data availability

  • data standards
  • key performance
  • optional fields
  • tool requirements
  • data fields

  • data structures
  • data types
  • proposed data
  • agencies collect
  • key findings

  • desired features
  • fields included
  • support calculation
  • agency data
  • manage data

  • effective data
  • data quality
  • time data
  • data processing
  • transaction data

  • data table
  • successful data
  • data applications
  • ensure data
  • meet 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.