[GTFS-Fares v2] Add fare_leg_join_rules.txt (first iteration) #439
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.
This PR is based on Google's fare_leg_join_rules.txt proposal. At the workgroup meeting on February 27th, the following consensus was reached:
from_network_id
andto_network_id
will be added first, followed by the addition of other predicates such asfrom_stop_id
andto_stop_id
.from_network_id
andto_network_id
are required fields, and initially will be restricted to the same network_id. We will consider relaxing this for differentnetwork_id
later.Changes in this PR
fare_leg_join_rules.txt
network_id
,from_area_id
,to_area_id
,from_timeframe_group_id
,to_timeframe_group_id
infare_leg_rules.txt
for effective fare legFor previous discussions please see the working group meeting note and issue#346
Please go through the changes and feel free to share your thoughts/questions here.