Examples 2.1

The following development examples demonstrate the use of TransXChange to encode simple and complex bus schedules. For each example, both the XML document in TransXChange format, and the PDF file output from the TransXChange Publisher are provided.

See also the TransXChange Samples which provide further examples of using TransXChange from live systems.

Group Name Description & Features XML Output
Basic Linear A single straight route run by a single operator. All vehicle journeys have the same timings.
  • Linear route
  • Registration detail
  • Route Track Map (Enhanced Publisher only
  • Local Track data, including instructions and Mapping System Reference
  • Frequent Service, with Frequency based journey times, specified as an interval
  • Inbound and outbound service
  • Registration Schema
Express A linear route with express journey patterns running over it that omit stops.
  • Express servic
  • Reuse of Vehicle journey timing link in multiple journeys
  • Overriding of Journey Pattern Timing Link Run Times with different values on the Vehicle Journey Timing links for some journey
  • Use of Wait Time
  • Holiday Day Type Exclusion
  • Local stop point definitions for an off-street Bus Station: BCQ, BCE and BCS stop type
  • Journey Footnote
  • Local stop area definition
  • Variable Bay Allocation
  • Supporting documen
  • General Schem
Complex Interchange Two routes run by two different operators. All vehicle journeys have the same timings.
  • Inbound and Outbound timetable
  • An Interchang
  • Linear route, with different stop visiting pattern at one end
  • Express stop
  • Frequent Service journey times, specified as an interval, but not a Frequent Service
  • Combining operating days from service, journey pattern and vehicle journey level
  • Serviced Organisation & School date
  • More than one operaton
  • Timetable Note
  • Registration Schema
Circular A circular route.
  • Circular rout
  • Reuse of route section
  • Dead runs (positioning links
  • Late night servcies that cross midnight till next da
  • Different weekday and Weekend variant
  • Partial traversal of Journey patter
  • Operator Garag
  • AVL data - Vehicle Type Ticket Machine, duty cre
  • Weekend servic
  • WGS8
  • Running Boar
  • General Schem
Cloverleaf A cloverleaf route shape with three petals.
  • Multiple routes composed of common route section
  • Multiple journey patterns composed of common. journey pattern section
  • Dynamic destination displa
  • General Schem
Lollipop lollipop shaped route, with two parallel branches.
  • Circular and parallel section
  • Reuse of journey pattern section
  • Reuse of VehicleJourney Links
  • Stop Sequence Number
  • Timing status on stop usage other than 'Principle Timing Point' (PTP)
  • Complex day types for regular and bank holiday operation
  • Use of TXC publisher option
  • Layover Poin
  • Two services run by two different operato
  • Connecting service
  • General Schem
  • Express stopping pattern for some journeys
  • Use of Stop Sequence Number
  • Use of Dynamic Destination headings
Eye An eye shaped route, with two alternative branches.
  • Multiple routes composed of common route section
  • Multiple journey patterns composed of common. journey pattern section
  • Stop Sequence Number
  • Local stop point definition
  • Bilingual stop names & schedule (Cymraeg)
  • Registration Schema
  • Running Boar
XML en
XML cy
PDF en
PDF cy
  Flexible Use of flexible zones
  • Flexible zone
  • Flexible time band
  • Registration Schema
  Hail & Ride Use of hail and ride stops.
  • Hail and ride section
  • Local stop point definition
  • Full lollipop topology
  • Frequency based journey times, specified as minutes past the hour, but not a frequent service
  • Short notice registration detail
  • Registration Schema
  Large Route Very large timetable.
  • More stops than fit down a page
  • More journeys than fit across a page
  • Basing of vehicle journeys on other vehicle journey
  • Timing links with zero duration
  • Multiple Frequency based services, specified as intervals, but not a frequent service
  Merge Frequent Journeys Individually coded frequent services that are to be merged as a single column.
  • Frequent service with, Frequent journeys coded individually. Merging by publishe
  • Page overflo
  • Non PTP point
  Footnotes Service with complex conditions requiring footnotes frequent services that are to be merged as a single column.
  • Large number of services (144)
  • Frequent journeys
  • Footnote
  • Page overflow
  • Garage detail
  • Short Notice Registratio
  • Operational data: Block, Vehicle type, layover point etc
Data Exchange
Operators Exchange of just operators.
  • General Schema
Routes Exchange of just routes.
  • General Schema
Service Changes Exchange of just changes to a vehicle journey.
  • General Schema

Page last updated: 2013/03/30