We're processing the json schedule data from Network Rail (
http://nrodwiki.rockshore.net/index.php/SCHEDULE) and stay up to date with the STP and VSTP updates.
It looks like he schedules are not yet representing the reduced schedule over the christmas period (it shows a regular timetable operating), even though this is known and represented by other sources (e.g. thetrainline).
Our logs do not point to any missed updates, so this suggests that the christmas period is too far in the future to be represented. However the records in the permanent schedule extend until May 2017. Incorrect schedules feel like more of a liability than no schedules, so I'm wondering about ways for accounting for this, either in how the schedules are published, or our application logic when representing them.
From the schedules side:
A. could all known predictable schedule changes associated with bank holidays, that fall within the time period represented by the permanent schedule, be published earlier, so periods such as christmas and easter do not show erroneous schedules when searching a 3+ months ahead.
B. alternatively, could the permanent schedules extend less far into the future (e.g. never more than 3 months.
Alternatively, are there any other fields in the schedule (or a reliable rule of thumb) which give an indication of the time window within which the schedule can be trusted to account for predicable schedule alteration, such as bank holiday periods.
Cheers
Dave