Bus operator requirements
What you need to know to get started. Find guidance and support material tailored to your needs.
|Data required||Data format required||Method|
|Timetable||TransXChange Version 2.4 profile v1.1||
Validation against PTI 1.1 profile
Data Quality report
|Bus location||SIRI-VM Version 2.0||Validation against schema|
|Basic fares||UK NeTEx 1.10||Validation against schema|
|Complex fares||UK NeTEx 1.10||Validation against schema|
Data quality checks are provided on the data supplied to the service to provide feedback on the data to help operators identify and understand issues within their data. The issues identified may prevent a data consumer using and sharing their data with passengers. High data quality is expected for all data published on the service. It reduces the barriers to entry for innovators and consumers when using bus open data. High quality data enables trust to be created between passengers and the public transport network.
TransXChange data undergoes two sets of checks. In the first validation stage, it is checked that it adheres to the TxC 2.4 schema and the PTI profile v1.1. The TxC 2.4 schema is the basic data standard mandated by DfT, and the PTI profile v1.1 is an additional mandate for the TransxChange data that will be expected from operators. The PTI profile 1.1 clarifies the standards even further, making the industry unified with a common, unambiguous data standard. More information on the differences between the TxC 2.4 schema and the PTI profile v1.1 can be found here.
From Friday 1st October 2021, files non-compliant to the PTI profile 1.1 will be rejected upon submission.
The feedback as a result of the validation check in the first step of upload is provided to the user which is to be shared with their respective software suppliers to enable them to provide robust data that fits the profile. In the second review step, a further data quality check is conducted which produces a report for operators. The report provides observations about operator’s data, highlighting common errors. Some observations are critical, meaning there is definitely an error within the data and the operator is expected to rectify the issue. Other observations are advisory as they may be false positives, as a result of the data structure. Operators should use these reports as suggested improvements in their timetables data.
Bus location data
SIRI-VM data is taken into a central AVL system, where it harmonised to produce a consistent SIRI-VM 2.4 output of bus location data for open data consumers.
NeTEx data is validated against their respective schemas, to check if it is in the expected format. As this format is new to the UK, more data quality checks may be enabled over time.