Destination names come from the destination name provided by the SIRI-SM feed, with a fallback to the name defined within your TransXChange.
In order of preference, the following fields are used:
TransXChange JourneyPattern → DestinationDisplay
Last stop’s locality name
Last stop’s common name
Truncated destination names
Some legacy systems do not support destination names beyond a certain number of characters.
To prevent breaking these legacy systems, some TransXChange exporter suppliers truncate the destination names by default.
Passenger does not require truncated destination names - you should change your export settings to ensure the full destination names are provided.
Departure board with a truncated destination name (Bournemouth Hosp)
For example, from the screenshot of OmniTimes below, set the “Shorten (Dynamic)DestinationDisplay text” option to No.
When uploading new TransXChange to suppliers, full destination names should start to be displayed to passengers.
Continue to the next article on Managing Departure Boards: Cancellations