The contents of a feed message.
A feed is a continuous stream of feed messages. Each message in the stream is
obtained as a response to an appropriate HTTP GET request.
A realtime feed is always defined with relation to an existing GTFS feed.
All the entity ids are resolved with respect to the GTFS feed.
Note that “required” and “optional” as stated in this file refer to Protocol
Buffer cardinality, not semantic cardinality. See reference.md at
https://github.com/google/transit/tree/master/gtfs-realtime for field
semantic cardinality.
Describes the physical path that a vehicle takes when it’s not part of the (CSV) GTFS,
such as for a detour. Shapes belong to Trips, and consist of a sequence of shape points.
Tracing the points in order provides the path of the vehicle. Shapes do not need to intercept
the location of Stops exactly, but all Stops on a trip should lie within a small distance of
the shape for that trip, i.e. close to straight line segments connecting the shape points
NOTE: This message is still experimental, and subject to change. It may be formally adopted in the future.
Describes a stop which is served by trips. All fields are as described in the GTFS-Static specification.
NOTE: This message is still experimental, and subject to change. It may be formally adopted in the future.
NOTE: This field is still experimental, and subject to change. It may be formally adopted in the future.
Select a stop by stop sequence or by stop_id. At least one of the two values must be provided.
An internationalized image containing per-language versions of a URL linking to an image
along with meta information
Only one of the images from a message will be retained by consumers. The resolution proceeds
as follows:
An internationalized message containing per-language versions of a snippet of
text or a URL.
One of the strings from a message will be picked up. The resolution proceeds
as follows: