Not allowed transfers and support for GTFS transfer points - #3792
Merged
t2gran merged 26 commits intoJan 26, 2022
Conversation
t2gran
force-pushed
the
otp2_not_allowed_transfers
branch
from
December 20, 2021 08:50
9d64941 to
ca028ac
Compare
Use a constant, REGULAR_TRANSFER instead of null to represent transfer constraint in boarding events. This enable the constrained transfer search to return a regular transfer and avoid null checking.
One of the test is disabled, because it fails. I will fix the bug and enable the test in a later commit.
When TripTimes are added to the trip, it trip times are also added to the "local list of trips" - witch is a aggregated temporary list, this has of cause no effect.
When TripTimes are added to the trip, it trip times are also added to the "local list of trips" - witch is a aggregated temporary list, this has of cause no effect.
t2gran
force-pushed
the
otp2_not_allowed_transfers
branch
from
December 20, 2021 14:35
ca028ac to
02e1dcb
Compare
t2gran
marked this pull request as ready for review
December 20, 2021 14:36
leonardehrenfried
requested changes
Dec 21, 2021
leonardehrenfried
left a comment
Member
There was a problem hiding this comment.
I've made a few comments about names.
Member
|
I ran this with the GTFS Flex example feed and there I saw a NPE when starting up OTP: So it seems that you can have a stop with which doesn't have a pattern. |
The StopPattern improve the memory footprint allowing multiple TripPatterns using the same sequence of stops to ref the same StopPattern. review: Get approval for API change in DigitransitStopPropertyMapper
- The Transfer report is improved - OTP serialization version id incremented
t2gran
force-pushed
the
otp2_not_allowed_transfers
branch
from
January 11, 2022 14:01
a956fcf to
1390922
Compare
t2gran
marked this pull request as ready for review
January 11, 2022 14:02
Co-authored-by: Leonard Ehrenfried <mail@leonard.io>
- refactor: Remove unused code in TransferMapper - refactor: Rename applyToAllTrips to appliesToAllTrips
Member
|
I'm going to turn off the codecov bot. |
Member
|
I've committed the configuration file directly to dev-2.x. If you merge again, the codecov bot will disappear. |
Member
leonardehrenfried
previously approved these changes
Jan 24, 2022
hannesj
reviewed
Jan 25, 2022
…ferPoint.java Co-authored-by: Hannes Junnila <hannes.junnila@gmail.com>
t2gran
force-pushed
the
otp2_not_allowed_transfers
branch
from
January 26, 2022 14:18
5ccb134 to
1e82238
Compare
…sfers # Conflicts: # src/main/java/org/opentripplanner/routing/stoptimes/StopTimesHelper.java # src/test/java/org/opentripplanner/routing/algorithm/mapping/__snapshots__/TransitSnapshotTest.snap
hannesj
approved these changes
Jan 26, 2022
leonardehrenfried
approved these changes
Jan 26, 2022
This file contains hidden or 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
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.


Summary
Explain in one or two sentences what this PR achieves.
Issue
Link to or create an issue that describes the relevant feature or bug.
You need not create an issue for small bugfixes and code cleanups, but in that case do describe the problem clearly and completely in the "summary" section above.
In the linked issue (or summary section for smaller PRs) please describe:
Remember that the PR will be reviewed by another developer who may not be familiar with your use cases or the code you're modifying. It generally takes much less effort for the author of a PR to explain the background and technical details than for a reviewer to infer or deduce them. PRs may be closed if they or their linked issues do not contain sufficient information for a reviewer to proceed.
Add GitHub keywords to this PR's description, for example:
closes #45Unit tests
Write a few words on how the new code is tested.
Code style
Have you followed the suggested code style?
Documentation
Changelog
The changelog file
is generated from the pull-request title, make sure the title describe the feature or issue fixed.
To exclude the PR from the changelog add
[changelog skip]in the title.