TransXChange

Examples 2.4

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

Registration Schema.

A single straight route run by a single operator. All vehicle journeys have the same timings.
  • Linear route.
  • Registration details.
  • Route Track Map.
  • Local Track data, including instructions and Mapping System Reference.
  • Frequent Service, with Frequency based journey times, specified as an interval.
  • Inbound and outbound service.
  • Operator Details including Parent Operator (TXC v2.4) & Licence details.
  • Reversing manouevre.

XML

Matrix PDF

Map PDF

Express

General Schema.

 

 

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 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, including SMS codes for TXC V2.4 rules, e.g. London.
  • Journey Footnote.
  • Local stop area definition.
  • Variable Bay Allocation.
  • Supporting document.
  • Marketing Name (TXC v2.4).

XML

Matrix PDF

Map PDF

 

Cancellation

Registration Schema.

Minimal details needed to identify a registration for cancellation. (TXC

C v2.4)

Cancellation of a registration.

XML

Matrix PDF

Complex

Interchange

Registration Schema.

Two routes run by two different operators. All vehicle journeys have the same timings.

  • Inbound and Outbound timetable.
  • An Interchange.
  • 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 dates, including Classification (TXC v2.4).
  • More than one operation.
  • Use of Stop Sequence Numbers.
  • Timetable Note.
  • Line Colours (TXC v2.4).

XML Matrix PDF

Circular

General Schema.

A circular route.
  • Circular route.
  • Reuse of route section.
  • Dead runs, Positioning links (Including TXC v2.4 duty crew).
  • Late night services that cross midnight till next day.
  • Different weekday and Weekend variants.
  • Journey Times past midnight for a given day type (TXC v2.4).
  • Partial traversal of Journey pattern.
  • Operator Garage.
  • AVL data - Vehicle Type Ticket Machine, Duty crew.
  • Multiple Variants of data per journey (TXC v2.4).
  • Reusable Day Types (TXC v2.4).
  • Vehicle Type Equipment for Accessibility (TXC v2.4)
  • Weekend service.
  • WGS8.
  • Service Level Vias.
  • Running Board / Dynamic Destinations.
XML Matrix PDF

Cloverleaf

General Schema.

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 display.
  • Recommended End date on Period (v2.4).
XML Matrix PDF

Lollipop

General Schema.

lollipop shaped route, with two parallel branches.
  • Circular and parallel section.
  • Reuse of journey pattern section.
  • Reuse of VehicleJourney Links.
  • Stop Sequence Number to control row order.
  • 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 Point.
  • Service Classification combinations including for '&' in code (TXC v2,4)
  • Two services run by two different operator.
  • Connecting service.
  • Express stopping pattern for some journeys.
  • Use of Stop Sequence Number.
  • Use of Dynamic Destination headings.
  • Partial Frequency Based service (TXC v2.4).
XML Matrix PDF

Eye

Registration Schema.

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 to control row order.
  • Local stop point definition.
  • New Stops required.
  • Bilingual stop names & schedule (Cymraeg).
  • Dynamic Destinations & Vias (Running Board) (TXC v2.4).
  • Multiple classifications (including TXC v2.4 relaxation of combinations).

XML en
XML cy

PDF en


PDF cy

 

Map PDF

 

FlexibleRegistration Schema.

Use of flexible zones
  • Flexible zone.
  • Flexible time band.
XML Matrix PDF
 

GroupingRegistration Schema.

Use of Journey Grouping (TXC v2.4).

  • Built in Journey Bed labels. (TXC v2.4).
  • Custom Journey Beds. (TXC v2.4).

XML

Matrix PDFMap PDF

 

Hail & RideRegistration Schema.

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.
  • Scottish Bank Holidays including St Andrews Day & January 2 Displacement (TXC v2.4).
  • Workflow Attributes (TXC v2.4).

XML

Matrix PDFMap PDF

 

Large Route Registration Schema.

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.

XML

Matrix PDF

Map PDF

 

Merge Frequent JourneysRegistration Schema.

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 point.
  • Default Operating Profile.

XML

Matrix PDF Map PDF

 

Footnotes Registration Schema.

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 Registration.
  • Stop Sequence Numbers to control row order.
  • Operational data: Block, Vehicle type, layover point etc.

XML

Matrix PDF Map PDF

Other
Data Exchange

Operators General Schema.

Exchange of just operators.
  • Multiple operators, no timetable
XML  

RoutesGeneral Schema.

Exchange of just routes. XML  

Delta General Schema.

Exchange of just changes to a vehicle journey. XML  


Page last updated: 2013/03/30