Traveline (TIL) challenges with BODS version control

BODS TXC Version Control
1

TIL has developed a BODS TXC import tool, and using the BODS ‘download all’ data is using the Elydium BODS Healthcheck tool to assess the useability of the data. The following document records some report results focussing on version control. TILFocusOnBODSVersionControl

TIL has found that the BODS validator is not using the TXC 2.4 PTI rules, and that some published data can’t be interpretted correctly/accurately for live service.

Are other BODS data consumers experiencing similar challenges?

2 Likes
2

I know of issues happening a lot with Stagecoach data where revision numbers are often a bit messy. Especially around School Holidays and on routes which operate between multiple depots. It’s been really affecting timetable information shown on bustimes.org.

1 Like
3

Yes. There appear to be a few challenges involving different technology suppliers:

  1. The Ticketer issue. As a data consumer, a dubious workaround I’ve found, and am using on bustimes.org, is appending part of the filename – e.g. 38M from DAGC_38M_DAGCPC109023112938_20250331_-_2091379.xml – to the ServiceCode.

  2. Services operated by multiple depots, where one depot’s journeys appear in a separate file with a different revision number. I’m told that operators who use Optibus can prevent this by choosing the “timeplan” (as opposed to “schedule”) option when exporting their data.

  3. Others?

There are workarounds that consumers can try, but they risk causing further problems by misinterpreting correct data.

2 Likes