Hi! I am struggling to understand how OperatingPeriod and SpecialDaysofOperation work for Night buses, and as a result how two files representing the schedule of one Night bus route connect.
Example: route N89 in TxC from 12/06
There are two files to represent the N89 schedules.
File 1 - ending in 76 - states that operating period is 10/06 - 23/06, and contains the schedules for that period. There are no SpecialDaysOperation around 23/06 or 24/06 in that file.
File 2 - ending in 77 - states that operating period is 24/06 to Dec 2023. It contains the schedules for that period. However, it has lots of SpecialDaysOperation around 24/06 that I don’t understand .
Lots of DaysOfNonOperation for 24/06 for Saturday
One DaysOfOperation for 24/06 for Sunday
However, Saturday is 23/06.
I am struggling to understand how the two files connect around 23-24/06. Could someone clarify? Thank you
The main problem with Night Buses/Tubes (rather than 24/7/365 services) is the 4am thing isn’t helpful as the “night” buses often run past 4am.
Anyway, the thing I got to work was using the Iso8601 day of the week AND the bitmap returned from the above function.
The data appears to use a 00:00 to 23:59:59 day allocation (for the start time if there’s an ofset then this can roll over into the next day: use Unix dates…)
Thank you @briantist! This is helpful, I do have to look a bit more into this to fully get my head around this. I will let you know if I have any further questions
I don’t think it’s quite the same as applying a Sunday schedule. Rather, some of the journeys that usually take place on a Saturday don’t take place, and one of the journeys from the Sunday schedule takes place on the Saturday. Therefore the actual schedule for that date is unique.
Section 3.18.5 “General Principles for Using Operational Days” on Page 133 of the schema guide provides quite a useful explanation of how operational days can be overridden.