-
Notifications
You must be signed in to change notification settings - Fork 9
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
What is the use of addLateNightServices? #86
Comments
Yes, it does. Trains in the DTD system start their day at 4am, which is different to GTFS (and any sane person). I believe that code will look at trains after midnight the previous day and add them in the correct day. I believe they may end up being duplicated at 24:00+ departure trains (e.g. departing 25:30) which is completely valid in GTFS. It's been many years since I looked at some of this so the details might be off but I believe that's it. |
The effect of the code is to add a copy of a train departing Monday 00:30 to depart at Sunday 24:30. I believe it may result in departure boards showing duplicate trains, however I haven't verified it yet in my deployment. Btw are you the maintainer of gtfs.pro ? |
No that's not me. I'm not actually involved with any rail stuff any more. Most of this stuff is just on life support. |
I just re-read the code and it came back to me. Please ignore my first reply. This was a hack I put in so that when you searched for journeys at the end of the day (e.g. 23:30) it would make connections with services after midnight without having to look for them on the next day. I suggest we add a flag to disable this behaviour. |
Upon studying the code,
addLateNightServices
add a copy of the service to the previous day. Won't it produce duplicated service entries?The text was updated successfully, but these errors were encountered: