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
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
Start OTP with some GTFS containing loop lines, and some vehicles running on those loops.
The text was updated successfully, but these errors were encountered:
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 hasstop
andstatus
, but not thestopTime
or thestopPosition
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
The text was updated successfully, but these errors were encountered: