Ad-hoc trips in GTFS-RT TripUpdates feed use of trip_id not found in GTFS-Static

[mpaine-act]

Introduce yourself

IT Supervisor for AC Transit working on new GTFS-Realtime feed.

Ask a question

I am trying to tune a new GTFS-RT TripUpdates feed and would like to know which scenario is better for data consumers regarding adding trips not found in GTFS-Static:

1. Set a negative (fake) trip_id to a specific trip inside TripDescriptor. This negative (fake) trip_id is not found inside GTFS-Static but is provided for backwards compatibility for older data consumers which assume a trip_id exists.

2. Instead of providing a fake trip_id, it will be omitted. We assume a fake trip_id is not necessary for modern GTFS-RT data consumers.

Note that alongside the route_id, direction_id, start_time and start_date will be set. Note that the additional properties may or may not coincide with a specific trip inside GTFS-Static trips.txt

[miklcct]

Please refer to #504 , it is a proposal of formalising the ability to add trips not found in GTFS-static, which is under voting.

I would like to hear your opinion about this.