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 collinearity #1323

Merged
merged 22 commits into from
Dec 17, 2024
Merged

Hqta collinearity #1323

merged 22 commits into from
Dec 17, 2024

Conversation

edasmalchi
Copy link
Member

resolves #1292 and greatly increases HQTA accuracy by ensuring we only aggregate frequency across routes where those routes are collinear. Use those results to filter down segments, reducing the chance of infrequent route segments getting matched to nearby frequent stops that aren't actually on that route, which creates a cleaner dataset with, importantly, far fewer erroneous major stops.

Also, don't consider looping segments for intersections, and ensure process for generating hq corridors and intersection-based major stops is filtered to bus only (rail major stops already captured in separate process)

see https://github.com/cal-itp/data-analyses/blob/e8b3c7f55bd5ba8dcf6838d1b4c086689475297a/high_quality_transit_areas/technical_notes.md for details on collinearity check

HQ Corridor Examples (old is blue):
octa_old
octa_new

New Major Stops:
mts_socal
mts_norcal

Copy link

@edasmalchi edasmalchi merged commit 6aa1172 into main Dec 17, 2024
2 checks passed
@edasmalchi edasmalchi deleted the hqta-collinearity branch December 17, 2024 20:30
@edasmalchi edasmalchi mentioned this pull request Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

HQTA Methodology follow-up: enforce partial collinearity and check branching
1 participant