Parse NeTEx fare zones from a FareFrame#4563
Merged
Merged
Conversation
| .withIgnoreFareFrame( | ||
| config | ||
| .of("ignoreFareFrame") | ||
| .since(V2_2) |
Member
There was a problem hiding this comment.
Since 2.2 has been released we need a new enum value for 2.3
hannesj
force-pushed
the
otp2_netex_fare_zones
branch
from
November 3, 2022 09:03
9dbd09c to
1bd7edc
Compare
vpaturet
approved these changes
Nov 8, 2022
leonardehrenfried
approved these changes
Nov 8, 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
It is possible to define TariffZones in two ways, in a
SiteFrameasTariffZones or in aFareFrameas its superclass,FareZone. Currently only the first way is implemented in OTP. This adds a parser for theFareFrameto readFareZones