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||Data quality|
|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 a data quality check and 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.
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.