Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HQTA Methodology follow-up: enforce partial collinearity and check branching #1292

Open
edasmalchi opened this issue Nov 14, 2024 · 0 comments
Assignees
Labels
data Work related to the management of data open-data Work related to publishing, ingesting open data research task Sub-issues within research request epics

Comments

@edasmalchi
Copy link
Member

edasmalchi commented Nov 14, 2024

Research Task

Per ongoing discussion with stakeholders, build on #1230 to further improve dataset accuracy.

  • While combining frequencies from multiple routes in a corridor often makes sense, it can lead to inaccurate results where routes are only briefly collinear -- especially in suburban areas or at transit centers. Implement a threshold distance (TBD, 1-4mi) to require routes to be collinear along a corridor for a certain distance before allowing aggregation, ensuring transit riders actually experience those frequencies for a meaningful trip distance.
  • Where a route branches from a trunk, ensure we only create a major stop if both the branch and the trunk meet the frequency standard
  • Research Required:
  • What should the threshold distance be? Look at empirical results and bus transit trip distance research/statistics.
  • Test cases: Woodland, Elk Grove, Woodman/Saticoy (San Fernando Valley), Wardlow corridor (Long Beach)
  • Expected Outputs / Findings: what do you hope to have created when this is complete?
  • Revised HQTA data incorporating these changes.
@edasmalchi edasmalchi added data Work related to the management of data open-data Work related to publishing, ingesting open data research task Sub-issues within research request epics labels Nov 14, 2024
@edasmalchi edasmalchi self-assigned this Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Work related to the management of data open-data Work related to publishing, ingesting open data research task Sub-issues within research request epics
Projects
None yet
Development

No branches or pull requests

1 participant