Service changelog

Last Updated: 21/11/2022


Known Issues

Publisher issues:

  • AVL: A minority of users have reported that they are getting inappropriate text in AVL notification for a dormant feed
  • Dataset feedback email: feedback is sent to the user who published the data, where this is no longer the correct user, feedback from consumers about a dataset is not received by email. Operators can still find a copy of all their consumer feedback on the dataset dashboards under consumer interactions.
  • AVL feed termination: when suppliers send data that isn't 'schema valid SIRI-VM data', BODS will set the feed to inactive, and terminate it. Operators will need to work with their suppliers to enhance their data to prevent this occurring and re-publish their feed credentials in BODS. No publicly available 'schema validation' reports are available, please request these from bodshelpdesk@kpmg.co.uk
  • Fixed Fares: operators have reported that fares files have occasionally been stuck in processing with the automatic update through URL
  • 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: 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

Consumer issues:

  • Fixed AVL: API queries for all BODS AVL data will be disabled from 21/11/2022, as they have a negative impact the BODS infrastructure. At least one AVL query parameter must be used, and multiple API calls made to get a full AVL response.
  • AVL API: A small number of newly published AVL feeds are not being correctly exposed through the AVL API
  • We are aware of issues with the API to access BODS data, with queries either taking a long time or responding with a 504 error. We are working to resolve the issue and resume normal response times as quickly as possible.
  • Dataset feedback email: feedback is sent to the user who published the data, where this is no longer the correct user, feedback from consumers about a dataset is not received by email. Operators can still find a copy of all their consumer feedback on the dataset dashboards.
  • Fixed Timetables data API: A minority of users reported the 'dqRag' parameter for the timetables API provided unexpected results. This has now been fixed.

High-level roadmap

Winter 2022 // Service code level completion reports will enable operators, local authorities and consumers to measure how completely an operators services are published to BODS. // AVL quality reports will enable operators and their suppliers to address issues relating to the AVL feed and how will this joins up with the timetable data for those journeys.


Release notes

October 2022 (1.20.0)

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

  • A list of your services which are marked as exempt by the BODS admin team so that they do not appear in the 'Service codes requiring attention' section. A publisher can notify the service desk if there are unexpected services so that they are removed from this report.
  • Functionality within the DfT Admin Portal has been updated to maintain the service code exemption list.
  • The data catalogues have been updated to ensure service codes that are out of scope will not show as missing.
  • A fix to the publish process for Fares which were impacting some users and their ability to publish fares data.
  • A fix to the publish process for Timetables which were impacting the ability to upload some circular services.

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.