I have been looking at the current set of Working and Temporary CUF timetable files with a view to extracting the currently applicable timetables at any given point and have encountered some issues.
Firstly some points regardnig Zip file naming, location and structure:
- Zip file names for timetables < 100 may or may not contain leading zeros, e.g BN023/BN029/BN040 but BN68/BN85
- The contents may or may not be contained in a subfolder, e.g BN023/BN029/BN040/BN136 do not have a subfolder, the remaining Bakerloo Temporarys do, e.g BN111.zip/BN111/*.csv
- There is a misplaced (duplicate) copy of WT7.zip in CUF/Working Timetables/, as well as the one in CUF/Working Timetables/Waterloo & City Line/
- Despite the documentation, only files VN127/151/159 contain CHK files
- The folder structure has ‘CUF/Working Timetables/Waterloo & City Line/’ but ‘CUF/Temporary Timetable Notices/Waterloo & City/’
Secondly, there is the issue of what is current. Using https://tfl.gov.uk/corporate/publications-and-reports/working-timetables as a reference, we get the following:
Bakerloo, Central, Hammersmith & City (& Circle), Jubilee, Piccadilly, Victoria
- all good, the latest set of WTT files is the expected one
District: the reference says 150 - presumably we need 150 SUN and 149 MTF and SAT
Metropolitan: fine for 341 MTH and FRI, but there are no SAT or SUN WTTs at all
Northern: reference has 132/19, the latest WTTs are 57 (Feb 2018). There is a set of Interim TTs for 132 in the Temporary Timetables which I take to be current
Waterloo & City: MTF fine, no SAT timetable
Thirdly, there is the problem of knowing when Temporary Timetables apply. This is fairly straightforward for all the clock change and bank holiday ones but not for engineering works and for any general (like 132 in Northern) entries in the Temporary section.
Here is the paragraph from the documentation that describes the usage of Operational Date in the ID files:
Although the table below shows provision for six date records (and the sample file format shows five dates), only the first is mandatory. The number of other (Operational) date records will be determined by the number of dates on which the timetable is scheduled to operate at the time when the file is created. Files related to a Working Timetable (and other timetables that may temporarily supersede a Working Timetable) will only have one date record. However, the absence of more than one date does not necessarily indicate that a timetable will supersede the Working Timetable on anything other than the date specified.
On the face of it, this would imply that a Temporary timetable is only in operation on the date(s) specified and this will be mostly true ( bank holidays, clock change, specific engineering work). The killer is in the last sentence, the intention of which I do not fully understand. What happens in the cases of ongoing engineering work or, like the Northern line, where a temporary timetable supersedes the WTT? How do we know when such an event stops?