TransXChange Examples 2.0e - Circular Route
 

Summary

A circular route served in a clockwise direction by a single operator. All vehicle journeys have the same timings.

Published as: PDF

Route Map

 

Timetable

Bus Station - High Street - Hospital - Bus Station

    #1 #2 #3 #4 #5

 Line

1

1

1

1

1
xL1  

Bus Station

-

11:00

12:00

13:00

14:00
xL2

High St

-

11:03

12:03

13:03

14:03
xL3

Market St

-

11:07

12:07

13:07

14:07
xL4

School

-

11:20

12:20

13:20

14:20
xL5

Hospital

10:29

11:29

12:29

13:29

14:29
xL6

Library

10:48

11:48

12:48

13:48

 -
 

Bus Station

11:00

12:00

13:00

14:00

 -

The XML Representation

XML Document

Service Registration

  • The service is not registered.
  • There is a single Operator.

Service Structure

  • The schema uses WGS84 coordinates, specified by LocationSystem.
  • There is a single Service instance SV1, with one Line - '1'.
  • There is a single RouteSection, RS1, connecting the six stops. It has six RouteLinks between the six stops;
    • (RL1) Bus Station to High Street,
    • (RL2) High Street to School,
    • (RL3) School to Market Street,
    • (RL4) Market Street to Hospital,
    • (RL5) Hospital to Library, and
    • (RL6) Library to Bus Station.
  • There is a single Route R1, with the one RouteSection, RS1.
  • There is a single JourneyPattern, JP1, with a single JourneyPatternSection instance JS1; corresponding to the route section RS1, and containing six JourneyPatternTimingLink instances, JPTL1 - JPTL6, which project onto the respective RouteLink instances RL1-RL6.
    • JPTL1 has a DynamicDestination heading of Hospital. This will be in effect until the next heading is encountered.
    • The JPTL4-To usage has a DynamicDestination heading of BusStation: from this point a different destination will be shown.,
  • There are five VehicleJourney instances, one for each column:
    1. VJ1 has an initial StartDeadRun run to position the bus at the Hospital stop from the Operator's Garage. It has just two vehicle journey timing links, VJTL5 & VJTL6, corresponding to the last two sequential links of the journey pattern, JPTL5 & JPTL6, to visit the last three stops of the route.
    2. VJ2 has six vehicle journey timing links, corresponding to all six journey pattern links, starting at Bus Station at 11:00.
    3. VJ3, VJ4 reference VJ2 for all their timing links, specifying only a different start time. (12:00 and 13:00).
    4. VJ5 has just three vehicle journey timing links to complete the journey, corresponding to the first three journey pattern timing links, and a final EndDeadRun to return the bus to the Garage. It has an override RunningBoard showing the short running.

Operational Details

  • The Operator has a Garage defined.
  • A default Service / TicketMachineServiceCode is specified.:
  • On the JourneyPattern, Operational details are specified:
    • A default TicketMachine /JourneyCode is specified. The TicketMachine / Direction is different from that of the service
    • A VehicleType is specified
    • A default RunningBoard is specified
  • DutyCrew CRW1 runs the first four journeys. A second DutyCrew CRW2 takes over at 'Bus Station' to run the final journey #5.

Fare Stages

  • There are FareStage instances at 'Bus Station', 'Market Street', and 'Hospital'.