Skip to content

Add fare_media_type=1#385

Merged
tzujenchanmbd merged 1 commit intogoogle:masterfrom
tzujenchanmbd:fare_media_type=1
Aug 2, 2023
Merged

Add fare_media_type=1#385
tzujenchanmbd merged 1 commit intogoogle:masterfrom
tzujenchanmbd:fare_media_type=1

Conversation

@tzujenchanmbd
Copy link
Collaborator

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=1 for physical paper ticket has not been adopted yet. In PR#355, fare_media_type=1 was reserved primarily because no producers were providing data at the time.

Change in this PR

Add fare_media_type=1 description in fare_media.txt

Value of this change

  • Showing the price for fares that are purchased on a paper ticket
  • Showing what needs to be used to validate the ride (the paper ticket)

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.

Added fare_media_type=1 in description
@tzujenchanmbd tzujenchanmbd added GTFS Schedule Issues and Pull Requests that focus on GTFS Schedule GTFS-Fares Issues and Pull Requests that focus on GTFS-Fares Extension labels Jun 28, 2023
@tzujenchanmbd
Copy link
Collaborator Author

@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.

@isabelle-dr isabelle-dr linked an issue Jul 18, 2023 that may be closed by this pull request
@tzujenchanmbd
Copy link
Collaborator Author

According to @npaun comment in issue#384,

On behalf of Transit, I can confirm that the changes made by PVTA and MBTA are in production in our system.

Both PVTA and MBTA's changes are in production on Transit App.

We are opening a vote for adding fare_media_type=1, which is a part of GTFS-fares v2 proposal.
Please vote with a +1 (for) or -1 (against) in the comments. Voting ends on 2023-08-01 at 23:59:59 UTC.

PVTA

MBTA

@emmambd emmambd added the Vote to Test Community votes to determine whether the proposal is ready for testing. label Jul 25, 2023
@npaun
Copy link
Contributor

npaun commented Jul 25, 2023

+1 Transit

@doconnoronca
Copy link
Contributor

+1 TransSee

@westontrillium
Copy link
Contributor

+1 Trillium

@drewda
Copy link

drewda commented Jul 26, 2023

+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 fare_media_type=1 in the Bay Area Regional Feed in the near future.

@isabelle-dr isabelle-dr mentioned this pull request Jul 27, 2023
4 tasks
@lhynes607
Copy link

+1 PVTA

@jfabi
Copy link
Contributor

jfabi commented Jul 27, 2023

+1 from the @mbta.

@bdferris-v2
Copy link
Contributor

+1 from Google

@tzujenchanmbd tzujenchanmbd removed the Vote to Test Community votes to determine whether the proposal is ready for testing. label Aug 2, 2023
@tzujenchanmbd
Copy link
Collaborator Author

The vote passed on 2023-08-01 at 23:59:59 UTC.

7 votes in favour and no votes against.

The votes came from:
Transit (@npaun)
TransSee (@doconnoronca)
Trillium (@westontrillium)
Interline-io (@drewda)
PVTA (@lhynes607)
MBTA (@jfabi)
Google (@bdferris-v2)

Thanks to everyone who contributed and voted! We are in the process of updating the GTFS Schedule Reference page on gtfs.org.

@tzujenchanmbd tzujenchanmbd merged commit 4dcefae into google:master Aug 2, 2023
gcamp pushed a commit to TransitApp/transit that referenced this pull request Sep 25, 2023
Added fare_media_type=1 in description
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

GTFS Schedule Issues and Pull Requests that focus on GTFS Schedule GTFS-Fares Issues and Pull Requests that focus on GTFS-Fares Extension

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add fare_media_type=1 to fare_media.txt

9 participants