Skip to content

Update MobilityData fork#20

Merged
giocorti merged 7 commits intoMobilityData:masterfrom
google:master
Feb 8, 2019
Merged

Update MobilityData fork#20
giocorti merged 7 commits intoMobilityData:masterfrom
google:master

Conversation

@giocorti
Copy link

@giocorti giocorti commented Feb 8, 2019

No description provided.

barbeau and others added 7 commits January 17, 2019 11:53
* 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
* Some transit agencies are publishing service alerts that don't actually impact the transit network. Examples include advertising public meetings, and soliciting feedback via surveys.
* This proposal adds a new Effect enumeration NO_EFFECT so that transit agency can clearly label these types of alerts as not impacting the transit network.  Consumers can then make a choice if they want to surface these types of alerts in their UI.
* Put example of holiday schedule under "Modified service" (following discussion in #137)
@giocorti giocorti merged commit 2150941 into MobilityData:master Feb 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants