-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Make flex linking work together with boarding locations #6311
base: dev-2.x
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev-2.x #6311 +/- ##
===========================================
Coverage 69.79% 69.79%
- Complexity 17798 17821 +23
===========================================
Files 2019 2020 +1
Lines 76126 76234 +108
Branches 7786 7800 +14
===========================================
+ Hits 53132 53210 +78
- Misses 20288 20309 +21
- Partials 2706 2715 +9 ☔ View full report in Codecov by Sentry. |
Will it cause #5498 to appear again? If not, what's the difference? |
No, it will not reappear. The difference is that linking to both walk and drive edges is ensured in all cases, even the stop has previously been linked to a boarding location. This is ensured by unit tests. |
@vesameskanen Can I ask you to review this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Logic seems fine, but could you clarify the link order and fix a typo please?
Summary
It links flex stops also to the drivable street network even when they are already linked to an OSM boarding location.
Issue
Closes #6299
Unit tests
Added.
Documentation
Javadoc.