Conversation
Added fare_media_type=1 in description
|
@npaun @timMillet Would you be able to share a screenshot of Transit app using this type? For example displaying the ticket name and/or if you use it to display the price. |
|
According to @npaun comment in issue#384,
Both PVTA and MBTA's changes are in production on Transit App. We are opening a vote for adding |
|
+1 Transit |
|
+1 TransSee |
|
+1 Trillium |
|
+1 from @interline-io Our team is currently reviewing to look for the handful of situations like this in the SF Bay Area, and will tag those as |
|
+1 PVTA |
|
+1 from the @mbta. |
|
+1 from Google |
|
The vote passed on 2023-08-01 at 23:59:59 UTC. 7 votes in favour and no votes against. The votes came from: Thanks to everyone who contributed and voted! We are in the process of updating the GTFS Schedule Reference page on gtfs.org. |
Added fare_media_type=1 in description


Context
Currently the valid options of fare_media_type enum are: 0-None, 2-Physical transit card, 3-cEMV, 4-Mobile app.
fare_media_type=1for physical paper ticket has not been adopted yet. In PR#355,fare_media_type=1was reserved primarily because no producers were providing data at the time.Change in this PR
Add
fare_media_type=1description infare_media.txtValue of this change
Data consumer: Transit
Data producer: MBTA, PVTA
For previous discussions, please see issue#384, PR#355, and working group meeting minutes.
Please go through the change and share your thoughts here.