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
Trips throughout the day may start from the first stop 24h ++ past midnight. This is common for "night-buses" witch is designed to run together with the services of the previous day. If the service for the next day start up early, before the last departure of the previous day, then OTP does not handle this correct.
Example
Departure times from Majorstua(first stop):
Uh oh!
There was an error while loading. Please reload this page.
Expected behavior
Trips throughout the day may start from the first stop 24h ++ past midnight. This is common for "night-buses" witch is designed to run together with the services of the previous day. If the service for the next day start up early, before the last departure of the previous day, then OTP does not handle this correct.
Example
Departure times from Majorstua(first stop):
The 27:35 departure is AFTER the first departure 02:35 on Tuesday.
When doing trip searches we expect all departures to be available, but the Tuesday 02:35 does not show up - it is skipped in the timetable view:
Version of OTP used (exact commit hash or JAR name)
dev-2.x
Data sets in use (links to GTFS and OSM PBF files)
https://developer.entur.org/stops-and-timetable-data
Only the NBU dataset is required to reproduce the problem.
The text was updated successfully, but these errors were encountered: