Proto commits in google/transit

These 56 commits are when the Protocol Buffers files have changed:

2025-04-14

deprecate active_period and add the two fields to the proto file

2024-12-05

Add GTFS Feed Version to the GTFS real time FeedHeader (#434) * Add feed_version and GTFS_url to FeedHeader. * attributes should be lowercase Co-authored-by: Antoine Augusti <antoine.augusti@gmail.com> * Remove gtfs_url Remove the addition of gtfs_url because it wasn't clear if it should the current or upcoming file and it hasn't been implemented. * Add feed_version description to referance.md * Add backticks to key word. Co-authored-by: Tzu-Jen Chan <126435471+tzujenchanmbd@users.noreply.github.com> --------- Co-authored-by: Antoine Augusti <antoine.augusti@gmail.com> Co-authored-by: Tzu-Jen Chan <126435471+tzujenchanmbd@users.noreply.github.com>

The documentation is generated from this commit.

2024-10-22

Adjust trip modifications (#497) - Addition of start_time and start_date to `ModifiedTripSelector` for frequency service support - Adding missing extensions fields for ModifiedTripSelector - Explicitly allow use of `schedule_relationship` in `TripDescriptor` when using a `ModifiedTripSelector`. - Add missing documentation in reference.md (it was only specified in the .proto) Revert whitespace change Co-authored-by: Stefan de Konink <stefan@konink.de> Revert white space change

2024-10-21

fix whitespace in .proto file (#489)

2024-05-09

Remove spanish translations from GTFS Realtime (#446) * Update README.md * Delete gtfs-realtime/spec/es directory * Update README.md * Update README.md * Update README.md

2024-03-11

GTFS Trip-Modifications (#403) * Add Trip-Modification, make shape non-experimental Fix typo Add images Update image width Add newlines Add newlines Update images Italic for image description Update SLO travel_time_to_stop is optional Proto : all feild optional Add references to GTFS-Static * Create a page for TripModifications entities for consistency with TU and VP * Clarify providing TUs for modified trips and ReplacementStop time interpolation Less strong requirement to interpolate * Fix first_stop_reference.png not having the right image + optimize image size. * Fix optional/require for Stop message * Clarify behaviour and linkage to TripUpdates * Apply Modification clarification proposed changes Co-authored-by: Paul Swartz <paul@paulswartz.net> * Use ModifiedTripSelector instead of concatenation of IDs Update langage Update namign * Add details on behavior when is provided * Remove modifications_id * Fix after comments from @bdferris-v2 * Add note about producer needed the two versions of trip updates * Fix bad relationship mentionned, + force no other entity when using ModifiedTripSelector * Changes after Jan 10 call * Add experimental notices * Remove mention of stop pattern * Use stop selector instead of stop sequence only * Update to end_stop_selector * Update proto with start/end stop selector * Add selected trips * Update reference with SelectedTrips * Update trip modif doc * Add last_modified_time * Add missing start_times in pb * Fix typos, fix description of selected trips * Fix typos Co-authored-by: Nicholas Paun <np@icebergsystems.ca> * Update reference for clarity * Clarify and remove duplicated information * Consistancy * Revert correctly shape experimental * Editorial, formatting clarifications * Apply suggestions from @sam-hickey-ibigroup Co-authored-by: Sam Hickey <sam.hickey@ibigroup.com> * Update documentation images with new fields, add source files * Clarifies behavior of propagated_modification_delay when no stop_time is cancelled * Remove extra word * Sync .proto and reference files --------- Co-authored-by: Nicholas Paun <nicholas@transit.app> Co-authored-by: Paul Swartz <paul@paulswartz.net> Co-authored-by: Nicholas Paun <np@icebergsystems.ca> Co-authored-by: Joshua Fabian <jfabian@mbta.com> Co-authored-by: Sam Hickey <sam.hickey@ibigroup.com>

2022-11-30

Proposal: Support DELETED trips in GTFS-RT (#352)

2022-07-26

addition of cause_detail and effect_detail to the spec (#332)

2022-07-25

Add WheelchairAccessible documentation (#340)

2021-11-26

Feature/image in alerts (#283) * Add image_url to alert * Add details about essential information in the image * Add notice about mainly text * Update discouraged image list * Support list of images * Fix typo Co-authored-by: Stefan de Konink <stefan@konink.de> * Fix typo Co-authored-by: Stefan de Konink <stefan@konink.de> * Revert table of content * Add media type, alt text * Fix URL writing Co-authored-by: Paul Swartz <paul@paulswartz.net> * Fix text reference in TranlatedImage Co-authored-by: Paul Swartz <paul@paulswartz.net> * Fix copy/paste error Co-authored-by: Paul Swartz <paul@paulswartz.net> * Clarify langage about image selection Co-authored-by: Sean Barbeau <sjbarbeau@gmail.com> * Clarify alt text description Co-authored-by: Sean Barbeau <sjbarbeau@gmail.com> * Update gtfs-realtime/proto/gtfs-realtime.proto Co-authored-by: Sean Barbeau <sjbarbeau@gmail.com> * Use RFC 2119 definition for requirement description Co-authored-by: Sean Barbeau <sjbarbeau@gmail.com> * Add missing extension attribute in TranslatedImage * Revert editorial changes * Revert editorial changes * Max size to 2MB * Add note about URL needing changing if the image changes * Use MUST for the size limit * Move alternative_text into the parent alert * Add missing experimenal note for image_alternative_text * Add note about image orderign * Only allow one image * Fix image text * Add mention of URL escaping, mirroring the one in GTFS static Co-authored-by: Stefan de Konink <stefan@konink.de> Co-authored-by: Paul Swartz <paul@paulswartz.net> Co-authored-by: Sean Barbeau <sjbarbeau@gmail.com>

2021-08-30

Proposal: Add GTFS-NewShapes as experimental (#272)

2021-04-14

Add departure_occupancy_status to TripUpdate (#260)

2021-04-09

Clarification of TripUpdate.timestamp (#263)

2021-02-01

Clarification of GTFS Realtime occupancy descriptions (#259)

2020-11-12

Proposal: Support stop assignments in GTFS-RT (#219)

2020-09-10

Proposal: Support multi-car crowding in GTFS-RT (#237)

2020-08-10

fix: Add extensions to TripProperties, remove extra comment (#238) This is an editorial follow-up to https://github.com/google/transit/pull/221 to fix two items: * New messages should have the extensions fields to allow 3rd party and internal extensions - this commit adds these fields * An erroneous comment was added that labeled schedule_relationship as experimental - this commit removes it

2020-07-29

Proposal: Support DUPLICATED trips in GTFS-RT (#221) * Support DUPLICATED trips in GTFS-RT * Revert deprecation of ADDED * Remove auto-format change * Better explanation of "forbidden" * Add experimental labels for message/fields * Add experimental labels for field * Add experimental label for message * Clarify DUPLICATED use with VehiclePosition * Clarify that true frequency-based trips can't be duplicated * Explicitly define how the duplicated trip schedule and RT values are calculated * docs: Add migration guide for transition from ADDED to DUPLICATED trips * docs: Normalize comments in code * docs: Allow trip.trip_id->trip_properties.trip_id link in migration guide

2020-07-23

feat: Alert `tts_header_text`, `tts_description_text` no longer experimental (#229)

2020-07-15

feat: Label GTFS-RT ADDED trips as not fully specified (#230)

2020-04-28

Mark severity level as final (#214)

Add occupancy_percentage (#213)

2020-04-27

feat: `direction_id` no longer experimental (#210)

2019-09-04

Reserve extension IDs range 9000-9999 for internal use by any organization (#178)

2019-08-07

Fix #102 - Add StopTimeUpdate.ScheduleRelationship UNSCHEDULED value (#173)

2019-05-09

Add accessibility issue alert effect (#164)

2019-05-05

Clarify TripDescriptor as referencing a single trip instance (#163) * Clarify TripDescriptor as referencing a single trip instance In the past, it was unclear whether TripDescriptor could reference more than one trip at a time when used within Alert EntitySelector. This change clarifies TripDescriptor use as follows: * TripDescriptor always refers to a single trip instances - it cannot be used to identify sets of trips. State that if a TripDescriptor doesn't resolve to a single trip instance, it's an error and consumers can drop the data. * List examples of known cases where additional fields other than trip_id are required to resolve TripDescriptor to a single trip instance * TripDescriptor.route_id cannot be used within an Alert EntitySelector - use EntitySelector.route_id instead * ScheduleRelationship field is ignored by consumers if set within an EntitySelector.TripDescriptor Basic descriptions for the fields in Alert EntitySelector are also added. This change also adds EntitySelector.direction_id for selecting one direction of route

2019-02-18

Remove some trailing whitespace from files (#142) * Remove trailing whitespace from Markdown files * Remove trailing whitespace from .proto file

2019-02-15

Comment formatting - Add period for consistency

2019-02-14

Add deprecated TripDescriptor.ScheduleRelationship=REPLACEMENT to .proto * TRANSLink in Queensland (https://gtfsrt.api.translink.com.au/) is publishing TripDescriptor.ScheduleRelationship=REPLACEMENT, which was deprecated in 2014 (https://groups.google.com/forum/#!topic/gtfs-realtime/77c3WZrGBnI) * When it was deprecated, the REPLACEMENT field value was removed from .proto entirely, which is causing consumers to crash when trying to read feed using the current .proto file (via gtfs-realtime-bindings library) (https://groups.google.com/forum/#!topic/gtfs-realtime/wbPfMIpXsJE) * This patch adds the REPLACEMENT field value back into the .proto file to support backwards-compatibility, but marks it as deprecated to discourage use until behavior surrounding this value is better defined.

2019-02-08

Update MobilityData fork (#20) Brings this fork in line with google/transit

2019-02-06

Add NO_EFFECT effect option for GTFS-realtime service alert (#137) * 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)

2019-02-01

Add optional field SeverityLevel to Service Alerts feed (#136)

Add optional fields for Text-to-Speech in Service Alerts feed (#135)

2019-01-17

Define valid GTFS-realtime version numbers (#130) * 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

2017-12-12

Revision of the Spanish translation of GTFS-realtime docs (#57) * Revision of the Spanish translation of GTFS-realtime docs Fix a number of translation inaccuracies. Add Occupancy status (missing in the Spanish version of vehicle-positions.md).

2017-10-25

fix gtfs_realtime_version in FeedHeader (#82) gtfs_realtime_version was set = to 2 (the version number) instead of 1 (the field number)

2017-08-09

Define semantic cardinality for GTFS-realtime fields (#64) * Define semantic cardinality for GTFS-realtime fields * As originally discussed in https://github.com/google/transit/pull/19 and https://groups.google.com/forum/#!msg/gtfs-realtime/wm3W7QIEZ9Y/DLyWKkknJyoJ, the current GTFS-realtime spec documentation describes field Protocol Buffer cardinality, not semantic cardinality. This has created confusion for consumers and producers where fields have been omitted based on them being labeled as "optional" in the GTFS-realtime spec, even if they were required under certain logical transit conditions (e.g., stop_sequence must be provided if a trip contains a loop). * This patch changes the "Cardinality" documentation to define the semantic cardinality for each data element as "required", "conditionally required", and "optional". It also bumps the gtfs_realtime_version in the .proto file to 2.0 so validators can strictly enforce semantic cardinality based on the gtfs_realtime_version. * Make trip.stop_time_update conditionally required based on trip.schedule_relationship Addresses https://github.com/google/transit/pull/64#pullrequestreview-46986350 * Fix conditional states for stop_time_update.arrival/departure ...based on stop_time_update.schedule_relationship. See https://github.com/google/transit/blob/master/gtfs-realtime/spec/en/reference.md#enum-schedulerelationship * Separate "Required" and "Cardinality" into different columns * A new "Required" field holds the information as to whether a particular field is Required, Optional, or Conditionally required * The existing "Cardinality" field is changed to a semantic version of cardinality instead of using Protobuf cardinality * Change FeedMessage.entity to "Conditionally required" * This field can't be "Required", because there are legitimate scenarios where a feed may not have any real-time information about the system (e.g., if it's 3am, and the agency doesn't offer any service at 3am). So, change to "Conditionally required" with description.

2017-07-17

Clarify that single-carriage vehicles (e.g. a standard bus) should have only 1 CarriageDescriptor.

Add carriage_sequence to explicitly define the carriage ordering.

2017-07-11

cleanup.

Add extensions and fix documentation for CarriageDescriptor.

Add CarriageDescriptor.

whatevs

2015-08-17

Merge pull request #7 from google/egorich239-multifeeds Allow multiple feed entity types in a single feed

2015-07-30

Remove REPLACEMENTS, format to 80 chars.

2015-07-29

Merge branch 'master' into egorich239-multifeeds

Remove paragraph about external configuration. It is clear from the previous sentences that GTFS RT refers to a GTFS feed. Polling frequency is one of trivial implementation details, not worth mentioning.

Initial commit for Spanish translation.

Refer to the gtfs-realtime directory.

Make the Github repository the authoritative source for gtfs-realtime.proto.

Do not require same entity types across a feed.

s/GTFS-realtime/GTFS Realtime/g

2015-07-15

Delete extra empty line.

2015-07-14

Change GTFS Realtime Specification to Apache 2.0

2015-07-10

Create Markdown mirror of devsite content.