Skip to content

AHSC Ridership Dashboard - Recalibrate Stop-Level Ridership Model with Expanded Observed Ridership Data and Enhanced Specifications #1859

@shweta487

Description

@shweta487

Relevant PRs:
#1246
#1482
#1674
#1731

Question or Goal:
Update the existing stop-level ridership regression model used in the AHSC Ridership Prediction Dashboard by incorporating newly available observed ridership datasets (19 agencies as of 1/8/2026), and assess whether adding variables or modifying the model form improves predictive performance and robustness relative to the current log-linear specification.

Data Required:
Currently have:

  • Preprocessed stop-level observed ridership datasets for 19 transit agencies in the transit-ridership-analytics repository. These datasets may include updated versions of LA Metro, Santa Barbara MTD, and Monterey-Salinas Transit, plus additional agencies
  • Existing GTFS-Schedule-derived service variables (daily trips and routes by stop for weekday, Saturday, Sunday)
  • ACS-derived demographic and socioeconomic variables aggregated to stop buffers
  • LEHD-based job density variables aggregated to stop buffers
  • Current model code and coefficients (log-linear OLS, Fall 2022 - updated in 2025)

Research Required:

  • Integrate all 19 observed ridership datasets into a unified training dataset at the stop level
  • Evaluate how expanded agency coverage affects coefficient estimates and model stability
  • Test candidate enhancements to the model, such as:
    • Additional service variables derived from GTFS (e.g., service span, frequency distribution)
    • Alternative functional forms (e.g., updated log-linear variants or semi-log specifications)
  • Document any changes to assumptions (e.g., exclusions, annualization, calibration approach)

Expected Outputs / Findings:

  • An updated ridership regression model trained on expanded observed data (19 agencies)
  • Quantitative comparison between the Fall 2022 baseline model and updated specifications
  • Clear documentation summarizing methodology changes for downstream dashboard updates

Sub-issues

Metadata

Metadata

Assignees

Labels

research taskSub-issues within research request epics

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions