RevisionNumbers not matching in BODS timetable data

Timetables for a service exported from Ticketer can be made up of more than one file per period of operation. For example, Monday to Friday, Saturday and School Trips may be published to BODS as separate files. Each file should have the same RevisionNumber in the header so that consumers can display the whole timetable for the week correctly, or present them correctly in journey plans.

There is an issue where the RevisionNumbers for such files are not the same, where they should be. This has been ongoing for several months and affects hundreds of services. Ticketer is rolling out a fix to its customers, which is in test.

Seems it’s still an ongoing issue and regularly affects Diamond West Midlands services. Some other ops too but I see it a lot on Diamond.

We understand that Ticketer has fixed this in their TXC export but like you we’re still seeing this issue for many data publishers

1 Like