You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to move forward with the trip detour use case specifically. We saw the need for a more focused specification tailored to consistent and accurate representation of detours.
For these reasons, we came up with GTFS-TripModifications. Indeed, GTFS-TripModifications allow us to give more specific details and to be more efficient when a detour affects multiple trips, compared to a complete replacement of each affected trip, as is currently provided for in GTFS-ServiceChanges v3.1.
We just released today our first implementation of our detour feature that uses data formatted in this proposition. Swiftly is also already interested in producing this data.
We welcome your feedback either here, or directly in the Google doc! Note that GTFS-TripModifications builds on GTFS-ServiceChanges v3.1 and uses some parts of it. This proposal doesn’t prevent the remaining features in that specification from being adopted in the future.
The text was updated successfully, but these errors were encountered:
Hi everyone,
GTFS-ServiceChanges v3.1 has been in the proposal stage for a long time and spans very wide.
We want to move forward with the trip detour use case specifically. We saw the need for a more focused specification tailored to consistent and accurate representation of detours.
For these reasons, we came up with GTFS-TripModifications. Indeed, GTFS-TripModifications allow us to give more specific details and to be more efficient when a detour affects multiple trips, compared to a complete replacement of each affected trip, as is currently provided for in GTFS-ServiceChanges v3.1.
We just released today our first implementation of our detour feature that uses data formatted in this proposition. Swiftly is also already interested in producing this data.
We welcome your feedback either here, or directly in the Google doc! Note that GTFS-TripModifications builds on GTFS-ServiceChanges v3.1 and uses some parts of it. This proposal doesn’t prevent the remaining features in that specification from being adopted in the future.
The text was updated successfully, but these errors were encountered: