Most feeds remove data from trip past stops:
You are allowed, but not required, to drop past stop times, unless the trip is a new or replacement trip not found in the GTFS static. 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 past the stop ahead of schedule), as otherwise it will be concluded that there is no update for this stop.
https://gtfs.org/documentation/realtime/feed-entities/trip-updates/#stoptimeupdate
If a trip has real-time info in the Trip Update feed, we should not keep past stop times once past (when no real-time data is available) else the app will show the static past stop time (which might be wrong).
Example: TTC bus has a -1 minute past stop time (from static data) which might be wrong and should not be displayed since we know from GTFS-RT data that the bus has past this stop.
Most feeds remove data from trip past stops:
If a trip has real-time info in the Trip Update feed, we should not keep past stop times once past (when no real-time data is available) else the app will show the static past stop time (which might be wrong).
Example: TTC bus has a
-1 minutepast stop time (from static data) which might be wrong and should not be displayed since we know from GTFS-RT data that the bus has past this stop.