Breaking change: TripUpdate.delay in GTFS Realtime trip updates feed

[nat...@omnimodal.io]

When using the GTFS realtime feeds generated by TheTransitClock for integration with Google Transit, we initially received Google's INVALID_TRIP_UPDATE_DELAY_USAGE warning, in the context of the GTFS Realtime trip updates feed. If both TripUpdate.delay and StopTimeUpdate arrival/departure times are specified, this warning from Google will occur, and they will drop the StopTimeUpdate predictions in favor of TripUpdate.delay.

Because of this, we made including TripUpdate delay optional, and false by default. However, other GTFS Realtime consumers may prefer having TripUpdate.delay available in the trip updates feed. If this describes you, this is a breaking change. To keep including delay, set transitclock.api.includeTripUpdateDelay to true.

Documented in this issue and PR, which has been merged into develop:

https://github.com/TheTransitClock/transitime/issues/92

https://github.com/TheTransitClock/transitime/pull/95#event-1778376551

-Nathan