Exporting
When exporting TransXChange, ensure that the resulting files are valid TXC, this can be done within the export options of the timetabling software, or via DfT’s TXC Publisher.
Validation
Use the dataset preview features in Passenger Cloud to ensure the data uploaded is correct and complete.
If you encounter any unexpected results, use DfT’s TXC Publisher to generate a PDF timetable, if this PDF produces the expected result but Passenger Cloud does not, please raise a support ticket with a copy of the TXC, and a link to the relevant dataset.
Please use valid ATCO codes when defining stops, if these stops are not currently in Naptan should be added. Where required stops can be defined in your TXC that are not in Naptan however we encourage ensuring naptan is complete.
Following the TransXChange schema, please ensure all unique key constraints are followed, unique keys should not appear more than once. E.g. Service codes / service private codes.
Export Options
Ensure your TransXChange does not contain “Dead Runs” https://help.discoverpassenger.com/support/solutions/articles/60000313082-why-are-timetables-sometimes-different-to-what-s-shown-in-txc-
You should export TransXChange 2.4 where possible, otherwise TransXChange 2.1 is also currently supported. We do not support mixing 2.4 and 2.1 files within the same dataset.
File Structure
Passenger Cloud supports uploading of TransXChange as a single .zip file containing multiple .xml files. Although Passenger Cloud also currently supports uploading a single .xml file, this option will soon be removed. It is preferable to always upload a .zip file, even if it only contains one .xml file.
Note that you should not upload zip files containing other zip files.
Note that Bus Open Data publishing requires that zip files are uploaded.
Note that you should avoid having multiple files with overlapping data (e.g. 1 line across 2 files within the same timeframe), unless you have confirmed these are merged correctly within the dataset preview.
Files are merged in the order they are presented within the zip file (alphabetically).
Generally we'd recommend a single TransXChange file per line within the zip file.