Skip to content

Define valid GTFS-realtime version numbers#130

Merged
barbeau merged 2 commits intogoogle:masterfrom
MobilityData:versions
Jan 17, 2019
Merged

Define valid GTFS-realtime version numbers#130
barbeau merged 2 commits intogoogle:masterfrom
MobilityData:versions

Conversation

@barbeau
Copy link
Contributor

@barbeau barbeau commented Dec 20, 2018

gtfs_realtime_version is a string in the Protocol Buffer gtfs-realtime.proto file, and therefore producers can populate this field with a number of different possible values. Previously, the exact allowed GTFS-realtime version format hasn't been explicitly defined in a single location, and as a result producers have published a variety of interpretations (e.g., 1.0, 1).

This proposal strictly defines what the allowed GTFS-realtime version numbers are so that consumers can do exact string matching to determine which GTFS-realtime version the producer is publishing and producers have better guidance for the values they should be using.

Valid versions are defined as 2.0 and 1.0. The .proto file currently lists 2.0 as the version, and prior to that 1.0 was defined. Based on our analysis, 37 feeds are using 1.0, 4 are using 2.0 and 4 agencies are using other values, so this aligns with the majority of values currently in use.

Announced on the GTFS-realtime Google Group at https://groups.google.com/forum/#!topic/gtfs-realtime/7g8inwuIpKA.

* gtfs_realtime_version is a string in the Protocol Buffer gtfs-realtime.proto file, and therefore producers can populate this field with a number of different possible values.  Previously, the exact GTFS-realtime version format hasn't been explicitly defined anywhere, and as a result producers have published a variety of interpretations (e.g., 1.0, 1)
* This proposal strictly defines what the allowed GTFS-realtime version numbers are so that consumers can do exact string matching to determine which GTFS-realtime version the producer is publishing
@barbeau barbeau added the GTFS Realtime Issues and Pull Requests that focus on GTFS Realtime label Dec 20, 2018
Copy link

@TomGoBravo TomGoBravo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you Sean.

@barbeau
Copy link
Contributor Author

barbeau commented Jan 7, 2019

This pull request has been open for more than one week, so per the Official Process I'm calling for a vote.

Vote will be closed on Tuesday January 15th at 23:59:59 UTC.

@git-rearden
Copy link

+1

7 similar comments
@TomGoBravo
Copy link

+1

@gcamp
Copy link
Contributor

gcamp commented Jan 7, 2019

+1

@paulswartz
Copy link
Contributor

+1

@geopamplona
Copy link

+1

@abyrd
Copy link

abyrd commented Jan 8, 2019

+1

@ghost
Copy link

ghost commented Jan 8, 2019

+1

@prhod
Copy link

prhod commented Jan 8, 2019

+1

@barbeau
Copy link
Contributor Author

barbeau commented Jan 17, 2019

Voting is closed on this proposal and the results are:

  • Yes - 8

So it passes! Thanks all!

@barbeau barbeau merged commit 97381d3 into google:master Jan 17, 2019
@barbeau barbeau deleted the versions branch January 17, 2019 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

GTFS Realtime Issues and Pull Requests that focus on GTFS Realtime

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants