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
Allow multiple FlexibleAreas in a FlexibleStopPlace #4922
Allow multiple FlexibleAreas in a FlexibleStopPlace #4922
Conversation
src/main/java/org/opentripplanner/netex/mapping/FlexStopsMapper.java
Outdated
Show resolved
Hide resolved
src/main/java/org/opentripplanner/netex/mapping/FlexStopsMapper.java
Outdated
Show resolved
Hide resolved
src/main/java/org/opentripplanner/netex/mapping/FlexStopsMapper.java
Outdated
Show resolved
Hide resolved
c460a05
to
f70524f
Compare
I addressed most of the comments. There is an open question about the location of the type key (see comment). |
Could you please fix the tests? |
src/main/java/org/opentripplanner/netex/mapping/FlexStopsMapper.java
Outdated
Show resolved
Hide resolved
No, as the tests should fail with the current behaviour and data. We need to clarify the #4922 (comment) above |
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.
As suggested by @testower, the key/value pairs should be looked up both at the FlexibleStopPlace level and FlexibleArea level, with precedence at the FlexibleArea level.
f70524f
to
9c6c2c7
Compare
…ea instead of the stop
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## dev-2.x #4922 +/- ##
=============================================
+ Coverage 65.34% 65.41% +0.06%
- Complexity 14455 14494 +39
=============================================
Files 1755 1754 -1
Lines 67978 68029 +51
Branches 7231 7243 +12
=============================================
+ Hits 44420 44500 +80
+ Misses 21091 21063 -28
+ Partials 2467 2466 -1
☔ View full report in Codecov by Sentry. |
@testower Can you please click "re-request review" when you think that it's time for it? |
Yep will do, there's a couple of outstanding issues that I'm trying to resolve first. |
I believe I have adressed all outstanding issues. I will create a test dataset based on real data and verify manually before asking for a re-review. |
I have verified this locally with a semi-fictitious dataset (I have excluded the regular stops from this zip, otherwise GitHub won't let me upload it): The dataset contains a flexible service that uses a single flexible stop place, with two areas. One of the areas is of the type UnrestrictedPublicTransportArea. Here is screenshot from the debug client, show an itinerary from a regular stop within one area to a street edge in the other area: |
Should be good to go now @leonardehrenfried (I mean, good to go for another review :) ) |
Ok, I see that you've already have reviewers (of which I'm not one, because I don't use Netex :)). |
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.
@testower Do you have merge permission?
Summary
Currently only the first FlexibleArea in a NeTEX FlexibleStopPlace is parsed. Modify the code to create a GrupStop if multiple areas exist.