Incorrect data

Not checking your data before you upload it to Passenger Cloud can result in undesired results, see “Manual Validation” above.

Invalid XML

Invalid XML cannot be imported, your timetabling software should produce valid XML.

This most commonly occurs from making manual edits to TransXChange XML files, which is highly discouraged and not supported, your timetabling software supplier should not require you to make manual edits. 

Invalid TransXChange

Sometimes timetabling software can produce valid XML, but invalid TransXChange, see “Automatic Validation” above. 

Incorrect/Inconsistent TransXChange Identifiers 

Incorrect or inconsistent TransXChange identifiers can lead to duplication of data, or mismatching of data between systems, see “External Identifiers” above.

Poor Content Quality

Some timetabling software can produce poor defaults for free text fields, such as:

  • Stop names
  • Destination display
  • Descriptions
  • Locations
  • and more... 

We encourage you to check the content quality of such data within your timetabling software and Passenger Cloud on a regular basis.

Incorrect Journey Calendars

Sometimes your TransXChange can incorrectly define journey calendars, causing timetables and/or journey planning to show data for services that aren’t running.

We encourage you to double-check calendars within your timetabling software before importing TransXChange into Passenger Cloud.

Once imported into Passenger Cloud, you should check the timetable and/or journey planning previews to confirm that no data is presented for days the service is not running, and data is presented for days it is. For further information see the “Operating profiles” section of the “Managing journey data” folder.

Continue to the next article on TransXChange: Managing TransXChange Datasets