TransXChange Examples 2.1
The following 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.   
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 details.
  • Route Track Map (Enhanced Publisher only)
  • Local Track data, including instructions and Mapping System References.
  • Frequent Service, with Frequency based journey times, specified as an interval.
  • Inbound and outbound services.
  • Registration Schema.
 XML PDF
Express A linear route with express journey patterns running over it that omit stops.
  • Express service.
  • 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 journeys.
  • Use of Wait Times.
  • Holiday Day Type Exclusions.
  • Local stop point definitions for an off-street Bus Station: BCQ, BCE and  BCS stop types.
  • Journey Footnotes.
  • Local stop area definitions.
  • Variable Bay Allocation.
  • Supporting document.
  • General Schema.
 XML PDF
 
Complex  Interchange Two routes run by two different operators. All vehicle journeys have the same timings.
  • Inbound and Outbound timetables.
  • An Interchange.
  • Linear route, with different stop visiting pattern at one end.
  • Express stops.
  • 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 dates.
  • More than one operator.
  • Timetable Notes.
  • Registration Schema.
 XML PDF  
Circular A circular route.
  • Circular route.
  • Reuse of route sections.
  • Dead runs (positioning links).
  • Late night servcies that cross midnight till next day.
  • Different weekday and Weekend variants.
  • Partial traversal of Journey pattern.
  • Operator Garage.
  • AVL data - Vehicle Type Ticket Machine, duty crew.
  • Weekend service.
  • WGS84.
  • Running Board.
  • General Schema.
 XML PDF  
Cloverleaf A cloverleaf route. shape with three petals.
  • Multiple routes composed of common route sections.
  • Multiple journey patterns composed of common. journey pattern sections.
  • Dynamic destination display.
  • General Schema.
 XML PDF  
Lollipop lollipop shaped route, with two parallel branches.
  • Circular and parallel sections.
  • Reuse of journey pattern sections.
  • Reuse of VehicleJourney Links.
  • Stop Sequence Numbers.
  • Timing status on stop usage other than  'Principle Timing Point' (PTP).
  • Complex day types for regular and bank holiday operation.
  • Use of TXC publisher options.
  • Layover Point.
  • Two services run by two different operators
  • Connecting services.
  • General Schema.
  • Express stopping pattern for some journeys.
  • Use of Stop Sequence Numbers
  • Use of Dynamic Destination headings.
XML PDF  
Eye An eye shaped route, with two alternative branches.
  • Multiple routes composed of common route sections.
  • Multiple journey patterns composed of common. journey pattern sections.
  • Stop Sequence Numbers.
  • Local stop point definitions.
  • Bilingual stop names & schedule (Cymraeg).
  • Registration Schema.
  • Running Board.
 XML enXML cy PDF
en PDF
cy
  Flexible Use of flexible zones
  • Flexible zones.
  • Flexible time bands.
  • Registration Schema.
 XML PDF
  Hail & Ride Use of hail and ride stops.
  • Hail and ride sections.
  • Local stop point definitions.
  • Full lollipop topology.
  • Frequency based journey times, specified as minutes past the hour, but not a frequent service.
  • Short notice registration details.
  • Registration Schema.
 XML PDF
  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 journeys.
  • Timing links with zero duration.
  • Multiple Frequency based services, specified as intervals, but not a frequent service.
 XML PDF  
  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 publisher.
  • Page overflow.
  • Non PTP points.
 XML PDF  
  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. 
  • Footnotes.
  • Page overflow.
  • Garage details.
  • Short Notice Registration.
  • Operational data: Block, Vehicle type, layover point etc.
 XML PDF  
Other
Data Exchange		 Operators Exchange of just operators.
  • General Schema.
 XML  
Routes Exchange of just routes.
  • General Schema.
 XML  
Service Changes Exchange of just changes to a vehicle journey.
  • General Schema.
 XML  
GovTalk logo