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.

Sign up for GitHub

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

Jump to bottom

It is not possible to provide both scheduled time and delay for an ADDED / REPLACEMENT trip in GTFS-RT. #6009

Open
miklcct opened this issue Aug 14, 2024 · 2 comments · May be fixed by #6028
Open

It is not possible to provide both scheduled time and delay for an ADDED / REPLACEMENT trip in GTFS-RT. #6009

miklcct opened this issue Aug 14, 2024 · 2 comments · May be fixed by #6028
Labels
New Feature

Comments

@miklcct
Copy link
Contributor

miklcct commented Aug 14, 2024

Is your feature request related to a problem? Please describe.
It is currently not possible to make OpenTripPlanner return a delay for an ADDED or REPLACEMENT trip in GTFS-RT. If both a time and a delay is specified in the StopTimeEvent in GTFS-RT, the latter is ignored as per GTFS-RT spec, in line with SCHEDULED trips.

Goal / high level use-case
A transport provider wants to add last-minute event special which does not exist in the GTFS static timetable, and the bus may be delayed.

Describe the solution you'd like
OpenTripPlanner should handle both time and delay in an StopTimeEvent for added or replacement trips (where the behaviour is not specified in the official GTFS-RT specification).

Describe alternatives you've considered
Implement the GTFS-ScheduleChanges v3.1 proposal for an official way to add or modify trips.
@miklcct miklcct linked a pull request Aug 28, 2024 that will close this issue
Draft
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days

@github-actions github-actions bot added the Stale This issue is stale, no activity for 90 days. Remove stale label or comment within 30 days. label Nov 13, 2024
@miklcct
Copy link
Contributor Author

miklcct commented Nov 13, 2024

Keep open. Waiting for progress on the proposal.

@github-actions github-actions bot removed the Stale This issue is stale, no activity for 90 days. Remove stale label or comment within 30 days. label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
New Feature
Projects
None yet
Milestone
No milestone
1 participant
@miklcct