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

  1. Bus Open Data Service
  2. Service Changelog

Service changelog

Last Updated: 13/07/2022


Known Issues

Publisher issues:

  • Fares: a minority of publishers have reported that some fares files have been stuck in processing with the automatic update through URL. We are aware of the minor discrepancy and are working to fix the issue.
  • 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:

  • AVL API: Some newly published feeds are not being displayed on the AVL API. We are aware of the minor discrepancy and are working on fixing it.
  • Fixed 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.
  • Fixed 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.
  • Fixed 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.
  • 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.
  • 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

Summer 2022 - Enhanced metrics for publishers, updated feedback form and bug fixes relating to data quality reporting


Release notes

August 2022 (1.19.0)

The team has worked on a number of high-value updates that will be available to everyone including:

  • An addition of a feedback page wherein any user can give a rating and a feedback on the user experience of the web pages on BODS. The feedback in turn can be accessed readily by DfT admin users. This will enable our team to continuously improve the BODS website experience. (Note that this is different from the feedback function on specific data sets/feeds on BODS).
  • A small update to the PTI logic of BODS where the as is functionality is: Review all files in new zip with same service code that have changed (hash of file changes) → Identify highest revision number from previous zip for that service code → Fail any amended files in new zip that do not have a higher revision number than highest from previous zip. This will be changed to the new updated PTI logic which will be: Review all files in new zip with same service code/line combination that have changed (hash of file changes) → Identify highest revision number from previous zip for that service code/line combination → Fail all new or amended files in new zip (with that service code/line combination) that do not have a higher revision number than highest from previous zip.
  • Some generic content updates to the entire website (in particular the guidance section) along with a few other high priority bugs (and some back-end updates) to improve the overall performance of the service.

June 2022 (1.18.0)

The team has worked on a number of high-value feature updates that will be available to all publishers including:

  • A new 'Guide Me' section for all publishers which simplifies and puts a step by step guide to how to go about publishing and maintaining data on BODS.
  • A new Publisher dashboard. All publishers once logged-in will now be able to view all the different feature options they have on BODS and select their relevant flow. A simplified ‘Review my published data’ dashboard is also now available for Publisher and Agent users, where they can review the status of the different operators that they are agents for.
  • A new ‘Data requiring attention’ section for all publishers and agents which highlights to all operators the service codes which are available on the OTC (Office of the Traffic Commissioner) database but have not been found in the BODS data that has been uploaded by publishers. This includes a downloadable CSV.
  • A new ‘Data consumer activity’ section showcasing the total consumer interactions with the data for a given operator’s data. This is intended to give the publishers a more granular idea about how their data is being utilized by consumers (e.g. passenger app developers, researchers) on BODS. This section includes two downloadable CSVs: one related to granular data interactions with the operator’s data, and the other relates to the direct feedback that has been received by operators on their published data.
  • An additional summarised version of the PTI validation report. This simplifies and gives an overview of the major errors in the data as it passes through our PTI TransXChange validator.

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.