Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft proposal : GTFS-TripModifications #5

Open
gcamp opened this issue Oct 27, 2022 · 0 comments
Open

Draft proposal : GTFS-TripModifications #5

gcamp opened this issue Oct 27, 2022 · 0 comments

Comments

@gcamp
Copy link
Member

gcamp commented Oct 27, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant