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

Changelog

Last Updated: 28/04/2022


Known Issues

Publisher issues:

  • Timetables DQ: Previously published routes being shown in DQ report. A minority of publishers have reported that they are shown out of date routes, or routes from an earlier dataset in their DQ reports.
  • Where AVL feeds which fail due to invalid data are terminated, no publicly available validation report is supplied to enable the supplier to resolve the issue.
  • Feedback messages from consumers are in some specific cases not being sent to the data set owners.
  • Notifications from BODS of issues with datasets are in some cases not being sent to the admin users of an organisation.
  • Fixed Timetables PTI: a minority of users reported end Date PTI validation error encountered when start and end date are the same.
  • Timetables DQ: users have reported for some files DQ reports were not being generated and instead shown that the DQ service is unavailable.
  • Fixed Timetables PTI: a minority of users reported Having <OtherPublicHoliday> tags within the <DaysOfOperation> AND <DaysOfNonOperation> tags produces an incorrect PTI error
  • Fixed Timetables PTI: a minority of users reporting having the name of the xml file being changed after upload.
  • Fixed Account Management: 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 Timetables: a minority of users reported timetables data with empty <Licence /> tags cause pipeline to fail.
  • Fixed Account Management: a minority of users reported receiving no email confirmations of their password changes for BODS.
  • Fixed Timetables DQ: Some of the Data Quality reports (DQ) erroneously mentions ‘expire lines’ which should not be there.
  • Timetables DQ: a minority of publishers have reported that they are shown unknown routes, or routes from different operators in their DQ reports.
  • Fixed Timetables DQ: 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.
  • Fixed Timetables DQ: 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.
  • Fixed Timetables PTI: TxC files within a zip that have not been amended are being validated for version control unexpectedly due to other files within the zip being amended, causing files to be non-compliant
  • Timetables PTI: A minority of users have reported unexpected the PTI validation check failures when updating timetable datasets. We are aware of this minor discrepancy and are working on a fix soon.
  • Timetables: A minority of users have reported small issues with datasets in draft. We are aware of this minor discrepancy and are working on a fix soon.
  • AVL: a minority of publishers have reported AVL feeds which are not updating properly.
  • AVL: A minority of users have reported that they are getting inappropriate text in AVL notification for a dormant feed. We are aware of this minor discrepancy and are working on a fix soon.
  • Fixed PTI validator: a minority of users reported getting erroneous errors when it comes to run time and zero run-times.

Consumer issues:

  • Filtering by Start Date on the browse section can filter results unexpectedly. The system is incorrectly using the earliest start date of a file in a dataset, rather than all start dates in a file.
  • Download all: A minority of users have reported some duplicate download links that are showing 500 errors. This shouldn’t be the case. We are aware of this minor discrepancy and are working on a fix soon.
  • Timetables data API: A minority of users have reported that the 'dqRag' parameter for the API provides unexpected results. We are aware of this minor discrepancy and are working on a fix soon.
  • Fares consumer: A minority of users have reported that published fares files on BODS which have a previous draft shows up as two different links on the Find Bus Open Data side. This shouldn’t be the case. We are aware of this minor discrepancy and are working on a fix soon.
  • Bus location data API: A minority of users have reported some missing data in the AVL API intermittently throughout the day. We are aware of this minor discrepancy and are working on a fix soon.
  • Bus location data API: A minority of users have reported that in the API, the VehicleRef cannot limit results to the specified vehicleRef. We are aware of this minor discrepancy and are working on a fix soon.
  • Fixed Producer Ref supplies a incorrect default value for all AVL responses. This will not be fixed as ProducerRef can only have one value with AVL.
  • 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.

High-level roadmap

Spring 2022 - Enhanced service usability and navigation as well as monitoring and compliance data statistics, with a focus on compliance with the OTC registration


Release notes

April 2022 (1.17.0)

  • Admin portal pages for DfT have been updated on BODS with functionality including searchable text boxes and sorting functions across organisation management, agent management and consumer management. This will enable easier and more convenient navigation on the admin portal for DfT.
  • The team has also worked on updating the download metrics on the platform. This will enable the DfT to truly track the utilisation of BODS and work with consumers to ensure higher adoption/usage of the platform.
  • A bulk of technical debts accrued over the past year have now been improved. This means the code base on BODS is cleaned up which will enable a better functioning overall platform.
  • Updates have been made to the developer documentation on Find BODS pages which adds more details on GTFS formats available on the platform. The documentation for data quality is now also updated to reflect the accurate description of how data quality is measured on BODS. Both these changes will enable more guidance and transparency on the features available on the platform.

February 2022 (1.16.0)

  • Enhancements to the Find Bus Open Data portal have been added to provide an improved consumer experience, including a new capability of viewing operator profiles and updated dataset detail pages with more relevant information, guidance and links.
  • 'Download All' data zip file has an updated nested folder structure, where datasets are placed into individualised operator folders. Consumers would be able to select individual operators files as requested.
  • Data Catalogue files have been improved with additional information including improved the 'Guide Me' pages.

December 2021 (1.15.0)

  • SIRI-VM Validator will provide users with reports on schema validation checks, with a status of compliant, partially compliant or non-compliant.
  • Updates to the BODS PTI validation has been added to check that lines consist of journeys with at least one matching locality (where localities are provided).
  • Updates to the validation of BODS PTI StopPoints will look if no OperatingProfile elements are at the VehicleJourney level then use the Service > OperatingPeriod > EndDate to check if non-NaPTAN stops are used for more than 2 months.

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.