This is a new service – your feedback will help us to improve it.

Changelog

Last Updated: 04/10/2021


Known Issues

Publisher issues:

  • Erroneous NAPTAN stop observation: a minority of publishers have reported erroneously receiving the following observation: 'Synthetic stop(s) (naptanID) not found in NaPTAN'. However, their stops are registered to the NAPTAN database. We are aware of this minor discrepancy and are working on a fix soon.
  • Zip file upload: a minority of publishers have reported that at times the zip uploads for timetables to BODS are failing to pass validation. We are aware of this minor discrepancy and are working on a fix soon.
  • PTI validation end-date: there is a minor issue reported in regards to end dates which are erroneously flagged up for users when it is similar to the start date. We are aware of this minor discrepancy and are working on a fix soon.
  • AVL data feeds not updating: a minority of publishers have reported AVL feeds which are not updating properly. We are aware of this minor discrepancy and are working on a fix soon.
  • Inconsistent DQ reports: a minority of publishers have reported that the outputs of the DQ reports are sometimes inconsistent for the same file. In some cases some advisory observations are also not shown correctly. We are aware of this minor discrepancy and are working on a fix soon.
  • Different routes being shown in DQ report: a minority of publishers have reported that they are shown unknown routes, or routes from different operators in their DQ reports. We are aware of this minor discrepancy and are working on a fix soon.
  • Missing block reference in DQ: Some of the users have reported that the ‘missing block number’ feature on DQ report is not fully working for them. We are aware of this minor discrepancy and are working on a fix soon.
  • Large files not loading in DQ: Some of the Data Quality reports (DQ) are not being generated correctly in particular for files which are of large sizes. We are aware of this minor discrepancy and are working on a fix soon.
  • Expired lines: Some of the Data Quality reports (DQ) erroneously mentions ‘expire lines’ which should not be there. We are aware of this minor discrepancy and are working on a fix soon.
  • Fixed Password rest: a minority of users reported receiving no email confirmations of their password changes for BODS.
  • Fixed Timetables publishing: a minority of users reported timetables data with empty <Licence /> tags cause pipeline to fail.
  • Fixed Timetables and Fares map: the map feature on BODS wasn’t working properly with some timetables and fares data routes not being generated correctly on maps
  • Fixed Inviting new user: a minority of users reported getting error messages when inviting a new email ID to join BODS multiple times. Some of them also reported invalid errors in the form to invite itself.
  • Fixed PTI valid but DQ not working: a minority of users reported having PTI valid files but however were unable to publish because the DQ reporting service was unavailable.
  • Fixed PTI validator: a minority of users reporting having the name of the xml file being changed after upload.
  • Fixed PTI validator: a minority of users reported Having <OtherPublicHoliday> tags within the <DaysOfOperation> AND <DaysOfNonOperation> tags produces an incorrect PTI error
  • Fixed PTI validator: a minority of users reported end Date PTI validation error encountered when start and end date are the same.
  • Fixed PTI validator: a minority of users reported getting erroneous errors when it comes to run time and zero run-times.
  • Fixed DQ report generation problem: for some files DQ reports were not being generated and instead shown that the DQ service is unavailable.
  • Fixed Email updates: erroneous emails were sent even when the correct PTI valid files were uploaded.
  • Fixed DQ report internal server error: for some files DQ reports were not being generated instead shown an internal server error.

Consumer issues:

  • Fixed Browse data: the pagination on the browse bus open data page were missing/not working properly.
  • Fixed API: When adding a random parameter after the API key, all results still come back as a 200 response which should not be the case.
  • Fixed Data set feedback email: a minority of publishers reported receiving no emails after a feedback have been left on their data sets by consumers.
  • Download all button: Repeated clicking (every 5 seconds) of the download all button erroneously gives the user a smaller file to download instead of the actual correct large file. We are aware of this minor discrepancy and are working on a fix soon.

High-level roadmap

Late Autumn 2021(1.15.0) - SIRI -VM validator to be added to check SIRI-VM feeds


Release notes

September 2021 (1.14.0)

  • TransXChange files that are not PTI compliant will no longer be allowed to be published in BODS.
  • Users of the service can now keep track of known issues, upcoming changes and release notes through the new Changelog page.