TransXChange as a standard can represent the same data in many different ways. The schema often has loose descriptions and definitions, resulting in different interpretations between different suppliers' implementations.

In order to ensure data accuracy, we require that you validate your TransXChange before uploading it to Passenger Cloud. Although this may take longer, it greatly reduces the chances of your TransXChange producing undesired results.

Automatic Validation

The TransXChange schema provides some constraints which can be automatically checked for compliance with that version of the schema.

There are three main ways this automatic validation can be performed: 

  1. By enabling the option when exporting from your timetabling software
  2. By producing PDF’s using the Department for Transport’s TransXChange Publisher with validation enabled
  3. By using generic 3rd party tools to perform XML Schema Definition (XSD) validation on your files before uploading them

If you need further advice on this please contact

Manual Validation

Whilst your TransXChange files may be compliant with the schema, that does not guarantee the final results will match your expectations if the schedule data provided was incorrect.

As such, we recommend running your TransXChange through multiple distinct systems to compare the results before uploading to Passenger Cloud, e.g.: 

  1. PDF exports from your timetabling software.
  2. PDF exports from the Department for Transport’s TransXChange Publisher

Once you’ve confirmed you get the desired results from other systems, you can import your dataset into Passenger Cloud for further testing and comparison to the PDF’s previously produced - by previewing timetables and journey planning for the draft dataset.

If inconsistent results are produced, this manual validation can help narrow down the issue for a quick resolution. If Passenger Cloud produces inconsistent results, please raise a support ticket with a copy of the TransXChange and a link to the relevant dataset.

Continue to the next article on TransXChange: Common TransXChange Pitfalls