https://docs.google.com/document/d/1zF5i03BFQi1kVBfN17aR7N1KRrpsHs3B9YjCzE8apJE/edit

Author: Transit

Adopted Files Affected: fare_leg_rules.txt, fare_products.txt

Problem

It is currently ambiguous in the spec if the same fare_product must be used on both legs of a fare_transfer_rule in order for the transfer to be accepted.

Solution proposed

Add 1 field to clearly define if the transfer requires the same fare_product or not.

Universally agreed IDs for fare information enable trip planners to process transfer costs between routes run by different agencies even if the information is not provided in the same GTFS dataset.

Specific Proposals:

Cross Dataset Namespaces

Author: Ito World

Currently Adopted Files Affected: None specific to proposal — impacts concepts outside of fares in GTFS

Solution Proposed: Add namespaces.txt to define what external datasets are referred to within the feed.

GTFS-References

Author: Cal-ITP

Adopted Files Affected: fare_transfer_rules.txt, transfers.txt, stop_times.txt, pathways.txt, stops.txt

Solution Proposed: Use references to identify when an entity (like stop, pathway, transfer, fare_transfer_rule) is shared across datasets.

MobilityData Member's Score: 0

Distinguish between certain trips within a network.

Specific Proposals:

Trip groups

Author: Ito World

Adopted Files Affected: fare_leg_rules.txt

Problem:

• Peak trains: Some systems have trains that are designated peak trains without simple time-based rules to describe them. In this case, the peak trips can be assigned to a ‘peak’ trip group that can then be matched in the fare leg rules.

• Direction-specific transfers: On networks where transfer rules involve the direction of the two trips, trips can be assigned to ‘inbound’ and ‘outbound’ groups.

Solution proposed: a definition along the lines of areas.txt and stop_areas.txt mechanism, but with “area” replaced by “trip_group” and “stop” replaced by “trip”.

Provide information on the transit agency's fare system and instructions on how to use it (in free form text).

https://bit.ly/gtfs-fares-v2-fare-leg-rules-scope-proposal

Author: Google

Adopted Files Affected: fare_leg_rules.txt

Problem

Empty values in fare_leg_rules create unintuitive overrides when networks with differing area boundaries are listed together.

Solution proposed

Add a scope field to specify the network that the leg rule applies to, so the duplicative work across networks is removed.

https://docs.google.com/document/d/18yWhwR89pQp48VuBNPXK0djLXOtdjWhgC2h6jCC8WPM/edit?usp=sharing

Author:  Transit

Adopted Files Affected: fare_leg_rules.txt

Problem

It’s not possible to model rules that only apply when there’s a transfer between agencies.

Solution proposed

Adding a transfer_only field to fare_leg_rules.txt which indicates that a rule applies only when transferring.

https://docs.google.com/document/d/1O0M0z4bZ1LKaB0l6qizq3G3isBom2__EJaisfA5om70/edit?usp=sharing

Author: Ito World

Adopted Files Affected: fare_leg_rules.txt

Problem

A transfer can be modelled so it appears to be free forever, if a passenger transfers back and forth across modes.

Solution proposed

Add an attribute to the rule that “stores” the enacted transfer and must be used as the from_leg_group_id for further matching.

It’s difficult to model complex fare systems without a way to track a passenger’s transitions through a trip, especially in fare systems with multiple transfers.

Specific Proposals:

Finite State Machines

Author: Google

Adopted Files Affected: fare_leg_rules.txt

Solution proposed: Use leg_group_id to model state and then use fare transfer rules, in combination with transfer_leg_group_id, to model transitions through the state machine.

Transfers -with-output_leg_group

Author: Ito World

Adopted Files Affected: fare_leg_rules.txt

Problem: A transfer can be modelled so it appears to be free forever, if a passenger transfers back and forth across modes.

Solution proposed: Add an attribute to the rule that “stores” the enacted transfer and must be used as the from_leg_group_id for further matching.

Resources

• Full Proposal: GTFS-Fares

• Adoption Matrix: GTFS-Fares v2 Adoptable Files and Fields List