From 9668516934ca4c8659fe897be907e500e5ecc1e1 Mon Sep 17 00:00:00 2001 From: Kyler Chin Date: Sat, 21 Sep 2024 15:08:54 -0400 Subject: [PATCH] CHange to recommended to keep past events. --- gtfs-realtime/spec/en/trip-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gtfs-realtime/spec/en/trip-updates.md b/gtfs-realtime/spec/en/trip-updates.md index b6c6894b..406ea3c9 100644 --- a/gtfs-realtime/spec/en/trip-updates.md +++ b/gtfs-realtime/spec/en/trip-updates.md @@ -10,7 +10,7 @@ If a vehicle is serving multiple trips within the same block (for more informati ## StopTimeUpdate -A trip update consists of one or more updates to vehicle stop times, which are referred to as [StopTimeUpdates](reference.md#message-stoptimeupdate). These can be supplied for past and future stop times. You are allowed, but not required, to drop past stop times. Producers should not drop a past `StopTimeUpdate` if it refers to a stop with a scheduled arrival time in the future for the given trip (i.e. the vehicle has passed the stop ahead of schedule), as otherwise it will be concluded that there is no update for this stop. +A trip update consists of one or more updates to vehicle stop times, which are referred to as [StopTimeUpdates](reference.md#message-stoptimeupdate). These can be supplied for past and future stop times. Producers are recommended but not required to keep past events. Producers should not drop a past `StopTimeUpdate` if it refers to a stop with a scheduled arrival time in the future for the given trip (i.e. the vehicle has passed the stop ahead of schedule), as otherwise it will be concluded that there is no update for this stop. For example, if the following data appears in the GTFS-rt feed: