-
Notifications
You must be signed in to change notification settings - Fork 6
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
Hqta collinearity #1323
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ng buffer 50-->35m
…and trolleybus in bus scripts
…improved accuracy)
nbviewer URLs for impacted notebooks: |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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):
New Major Stops: