More concretely: it looks like the schedules for Night Tube and Night Buses are shifted forwards by one day. Not sure how this has happened, but this is the case.
For Night Tube, they are shifted between Thursday and Saturday:
Thursday has the Friday schedule - trips start 4am ish + late at night trips (for overnight Tube) - INCORRECT
Friday has the Friday schedule - trips start 4am ish + late at night trips (for overnight Tube) - CORRECT
Saturday has something that looks like a Sunday schedule - early am trips + end around midnight INCORRECT
Sunday: also has a Sunday schedule (as expected) - but fewer trips than on Saturday - early am trips + end around midnight CORRECT
For Night buses, they are shifted entirely between Thursday and Sunday:
The way that post-midnight services display in TxC 2.4 has now changed. In 2.1, this was allocated to the exact day that the service runs. i.e. a service at 00:30 on a Friday night would show as being on Saturday. In 2.4, there is a DepartureDayShift field that when present will show the post-midnight journey as being in the early hours of the following day. In this case, the Saturday will now show as Friday with the
Examples of the same journey on the Victoria line are shown below:
This field can apply to any TxC file produced as most services across the modes have journeys that occur at the end of a day after midnight.
In the case of night tube, services that start before 03:00 will appear on the previous day with <DepartureDayShift>1</DepartureDayShift> and those after 03:00 will not have DepartureDayShift set.
Hi @jamesevans , thank you. Yes this would explain why we are seeing this ‘shift’. Has anything else of the sorts changed?
e.g. service exception, service periods, holiday v standard schedule, overnight schedules
I took a look at the schema for 2.4, but it’s 290 pages long so it’s difficult to understand what is new in comparison with 2.1
Cheers,
Nick