TransXchange (TXC)

TransXchange builds on the Transmodel data standard and is XML based. It is suitable for transferring bus timetable data to real time systems, local authorities and for Electronic Bus Registration. In TransXchange the route as a series of journeys is the main unit for the transfer of data.

Documentation

latest specifications are for version 2.1.
Transmodel On line Glossary
Wikipedia entry for Transmodel

Transmodel

breaks public transport routes down into the following:

Line: (a service with a single service number - 13, X3, 200 etc)
Route: A physical path through the network (on tarmac or rails normally)
Service Pattern: A sequence of Stop Points called at in turn with an associated Route (a line will normally have 2 or more Service Patterns)
Timing Pattern: A set of timing for a particular Service Pattern (service patterns can have multiple timing patterns)
Vehicle Journey: A departure time and set of dates/days with an assoicated Timing Pattern (A timing pattern can have mulutiple Vehicle Journeys).

There is also a way of grouping Service Patterns into Directions and methods to deal with trains that divide and join (ie the front and back are eventually heading for different places). Many other tedious exceptions can also be modeled.

XML

If you find alternatives which are good, and perhaps cheaper, please

Publisher

Publisher will help you can see the TransXchange data as a conventional registration and timetable. The latest version of publisher is 2.2a_10

Timetable Software that will import and export TXC

Software	Company	Capability
Diadem	JourneyPlan	Version 3.0.71 and upwards will import and export files in TXC2.1 format. Exports can be in TXC2 or TXC2(registration) formats.
Diva	MDV	The latest versions will import and export files in TXC2.1 format.
OmniTimes	Omnibus	Import and Export in TXC2.1 format is available in a chargeable TransXchange module that works with the latest version of the OmniTimes software. To create an Electronic Bus Registration there is an EBSR module which requires OmniTimes, OmniMap and the TransXchange module.
Trackbuilder	Trapeze	Subject to the appropriate licence, TrackBuilder version 7.0 and upwards is capable of importing and exporting TXC2.1 files that satisfy journey planning requirements.
Routewise	Trapeze	Subject to the appropriate licence, Routewise version 10.0 and upwards supports TXC2.1 both import and export of both Registration and General documents.

Companies with TransXchange2 systems available and in use now are:

(please notify any other companies)

Support Groups

ATCO/suppliers database group and the RTIG data working group are merging. Their first joint meeting is to be on 27 November 2008.

Read a TransXchange edition of the RTIG newsletter