[GTFS Fares v2] Area Set matching predicates. #483
Conversation
eliasmbd
added
GTFS Schedule
gtfs/spec/en/reference.md
Outdated
| @@ -477,12 +479,16 @@ To process the cost of a leg: | |||
|
|
|||
| <br/> | |||
|
|
|||
| For area set predicates in `fare_leg_rules.txt` specified below, a leg “travels through an area” if any of the stops or parent stations (if the area is not defined at the stop-level) of the leg; including departure, arrival, and intermediate stops; belongs to the specified area as defined by [stop_areas.txt](#stopareastxt). | |||
There was a problem hiding this comment.
For the intermediate stops, it seems they must be stops defined in stop_times rather than "geographical pass-through" stops. Could the current description cause misunderstandings? Would it be clearer to state this explicitly?
There was a problem hiding this comment.
I attempted to add explicit language. Let me know what you think.
There was a problem hiding this comment.
Looks good to me!
Just to confirm:
and intermediate stops as referenced by the trip's stop-time entries; belongs to the specified area as defined by [stop_areas.txt]
This means that entries will be included regardless of their pickup_type and drop_off_type values (e.g., value=1 - No pickup/drop_off available). Is this correct?
There was a problem hiding this comment.
Yes, I suppose that's correct.
I think we discussed this briefly in the last meeting, yes? I think it's reasonable to make the default the simple case (passes through a stop).
There was a problem hiding this comment.
Yes, got it. Just want to confirm if I correctly understand the semantics here (i.e. regardless of the pickup_type and drop_off_type values).
|
Here is a dataset that has already been implemented by Ito, which is part of a private feed. |
Add support for matching "sets" of areas in
fare_leg_rules.txtper this proposal.