-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fare_media and transaction_type overlap #23
Comments
Also, see issue #22, "ODX - transfers / multiple vehicle trips": If GTFS-ride is intended to include linked trips (ODX), it may be useful to include these fields in rider_trip_segment.txt so that they could be associated with alightings (necessary in the case of transfers). |
I agree that there is overlap here and perhaps some consolidation/clarification may be warranted to disentangle the intent and use of the two fields. The field values you suggested for the example would be correct. I will work on a pull request for this. |
Clarification and updates to the transaction_type and fare_media fields of rider_trip.txt in response to issue ODOT-PTS#23 at ODOT-PTS#23
Why are RFID, smartphone apps, and open payment are listed across these definitions for
|
There is overlap in the rider_trip.transaction_type and rider_trip.fare_media fields. i.e. both list cash, transfer options (though slightly differently). If a traveler used a mobile payment "software flash pass" to make a transfer, then would transaction_type = 2 and fare_media = 4? It seems as though options 0, 1, 2 might be removed from transaction_type.
Quoting draft:
The text was updated successfully, but these errors were encountered: