Hi everyone,

We (MobilityData) are opening this issue in regards to fare information in GTFS.

Currently, fares in GTFS are described using fare_attributes.txt and fare_rules.txt. We noticed 2 main issues regarding this current specification:

1. It falls short of detailed payment descriptions, discoverability of fares, points of sale, rider eligibility criteria, transfer rules, and travel conditions (e.g., timeframes, distance).
2. It has not been widely produced or consumed by the GTFS community, perhaps in part because this specification does not reach its full potential for describing fare information.

Therefore, we would like to know your thoughts on describing fares with the current GTFS:

1. Are fare_attributes.txt and fare_rules.txt enough to describe fares? Do they allow accurate fare representation?
2. What are your needs for fare descriptions that are not handled or are badly handled by the current specification?
3. What is your interest in having a new way to describe fares in GTFS?

As you may know, MobilityData has drafted GTFS-Fares v2 to allow for broader descriptions of simple or complex fare structures. But before going further with this project, we would like the input of the GTFS community to know if we are capturing all needs as much and as accurately as possible.

Don’t hesitate to voice your concerns, needs, or general feedback in this issue!

Thanks!

Edits
2021-08-18: Issue renamed from "Fares in GTFS" to "GTFS Fares v2"