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

GTFS GraphQL StopRelationship does not have stopTime #6306

Open
miklcct opened this issue Dec 5, 2024 · 0 comments
Open

GTFS GraphQL StopRelationship does not have stopTime #6306

miklcct opened this issue Dec 5, 2024 · 0 comments

Comments

@miklcct
Copy link
Contributor

miklcct commented Dec 5, 2024

Expected behavior

I know which stopTime the vehicle is arriving.

Observed behavior

There is no way to know which stopTime the vehicle is arriving.

The StopRelationship only has stop and status, but not the stopTime or the stopPosition which I can look it up from the journey. Therefore, if the trip makes a loop with repeated stops, it is impossible for me to know which part of the trip it is on.

Version of OTP used (exact commit hash or JAR name)

2.7.0-SNAPSHOT

Data sets in use (links to GTFS and OSM PBF files)

Any GTFS with vehicle position update

Command line used to start OTP

irrelevant

Router config and graph build config JSON

large irrelevant, just need a vehicle position updater

Steps to reproduce the problem

  1. Start OTP with some GTFS containing loop lines, and some vehicles running on those loops.
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