-
Notifications
You must be signed in to change notification settings - Fork 2
Upstream merge 2024-09-20 #225
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
Upstream merge 2024-09-20 #225
Conversation
also added line break to improve page formatting
…TimeToScheduledTripTimesMapper.java Co-authored-by: Thomas Gran <t2gran@gmail.com>
also updated descriptions to reflect recent changes to realtime system
arrows now point at correct hierarchical level, but stop short of the specific individual objects when they are referring to instances that are elided from the diagrams
…/npm-vite-vulnerability Update dependency vite to v5.4.6 [SECURITY]
…/debug-ui-dependencies-(non-major) Update Debug UI dependencies (non-major)
…/major-geotools.version Update geotools.version to v32 (major)
…times-colors Add full ISO times and colours to debug UI
…-leg Extra leg when transferring at the same stop
For the new "transfer" leg am I right in seeing that it's generating a WALK type leg? Am I supposed to compare the from/to to identify that it's a transfer leg instead of a walking leg? |
All transfer legs are walk legs. For anything else we would need a new schema, which is a super breaking change. |
The distance is also 0. |
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.
Great thank you!
This adds the ability to insert an extra leg when transferring at the exact same stop: opentripplanner#5984
You need to enable the feature flag
ExtraTransferLegOnSameStop
.It also fixes the parsing of safe_duration_offset but that is likely to change again: opentripplanner#5984
The arrive by fix for Hopelink is not merge upstream yet, so please don't deploy this merge there. Use #223 instead.