TransXChange

Examples 2.4 - Circular route

Summary

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

  • Circular route.
  • Reuse of route sections.
  • Multiple Line.
  • Operational Profile for different Weekend service, with fewer journeys and different evening journey times. Overriding of a default profile.
  • Journeys that run past end of day/midnight boundary.
  • Journeys that start or end in a different day from the Journey profile day type marked with Day Shift. (TXC v2.4)
  • Partial Traversal of Route / Journey Pattern.
  • Dead runs, Positioning links (Including TXC v2.4 duty crew).
  • Late night services that cross midnight till next day.
  • Operator Garage.
  • Service level Vias
  • Dynamic Destination Displays.
  • Fare Stages.
  • Operational data: Vehicle Type, Ticket Machine, Duty crew.
  • Operational data Variants for different days (TXC v2.4).
  • Reusable Day Types (TXC v2.4).
  • Vehicle Type Equipment for Accessibility (TXC v2.4)
  • WGS8 coordinates
  • General Schema.

 

Published as: PDF PDF Timetable only

Route Map

Circular route image

Timetable - Clockwise, Monday to Friday

Bus Station - High Street - Hospital - Bus Station.
    Based on Ref to JP1 JP1 JP1 VJ2 VJ2 JP1 JP1 JP1 JP1
    Links based on JP1 + start
dead
run		 JP1 + start
dead
run		 ->JP1 ->VJ2 ->VJ2 P1 + end
dead
run		 ->JP1 ->JP1 ->JP1
    Operational Profile ->JP1 ->JP1 ->JP1 ->VJ2 Override ->JP1 Override Override Override
VJ #10 #1 #2 #3 #4 #5 #6 #7 #10
Line 1 1 1 1 1 ++ 1 1 Night 1 Night 1 Night
    Day Shift -1 0 0 0 0 0 0 0 1
xL1   Bus Station 23:30* - 11:00 12:00 13:00 14:00 22:30 23:30 00:10**
xL2 High St 23:33* - 11:03 12:03 13:03 14:03 22:33 23:33 00:13**
xL3 Market St 23:37* - 11:07 12:07 13:07 14:07 22:37 23:37 00:17**
xL4 School 23:50* - 11:20 12:20 13:20 14:20 22:50 23:50 00:30**
xL5 Hospital 23:59* 10:29 11:29 12:29 13:29 14:29 22:59 23:59 00:39**
xL6 Library 00:18 10:48 11:48 12:48 13:48 - 23:18 00:18 00:58**
  Bus Station 00:00 11:00 12:00 13:00 14:00 - 23:30 00:30 01:10**


* Previous Day

** Next Day

++ Not Thursday

Bus Station - High Street - Hospital - Bus Station

Clockwise, Saturday & Sunday
    Based on Ref to JP1 JP1 VJ2 JP1 JP1 VJ8
    Links based on VJ10 JP1 + start
dead
run		 ->VJ2 JP1 + end
dead
run		 ->JP1 ->VJ2
    Operational Profile Override ->JP1 Override ->JP1 Override Override
VJ #11 #1 #4 #5 #8 #9
Line 1 Night 1 1 1 1 Night 1 Night
    Day Shift -1 0 0 0 0 0
xL1   Bus Station 23:30 - 13:00 14:00 22:45 23:45
xL2 High St 23:33 - 13:03 14:03 22:48 23:48
xL3 Market St 23:37 - 13:07 14:07 22:53 23:52
xL4 School 23:50 - 13:20 14:20 23:05 00:05
xL5 Hospital 23:59 10:29 13:29 14:29 23:14 00:14
xL6 Library 00:18 10:48 13:48 - 23:33 00:33
  Bus Station 00:00 11:00 14:00 - 23:45 00:45


The XML Representation

XML Document

Service Registration

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

Service Structure

  • There is a single Service instance SV1, with two Lines - '1'. and '1 Night'.
  • 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 ten VehicleJourney instances, with different day profile conditions, so different journeys get selected for Monday to Friday and for Saturday and Sunday:
    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.
      • It inherits an OperationalProfile from JP1 that says it runs MondayToFriday.
    2. VJ2 has six vehicle journey timing links, corresponding to all six journey pattern links, starting at Bus Station at 11:00.
      • It has an override OperationalProfile that says it runs MondayToFriday
    3. VJ3, VJ4 reference VJ2 for all their timing links, specifying only a different start time. (12:00 and 13:00).
      • VJ3 inherits an OperationalProfile from VJ2 that says it runs MondayToFriday
      • VJ4 has an override OperationalProfile that says it does not run on Thursday, but otherwise runs Monday to Sunday.
    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
    5. VJ6 follows all six links of JP1 starting at Bus Station at 22:30.
      • It has an OperationalProfile that says it runs MondayToFriday
    6. VJ7 follows all six links of JP1, starting at Bus Station at 23:30, so its later stages will take place in the next calendar day.
      • It has an OperationalProfile that says it runs MondayToFriday
    7. VJ8 follows all six links of JP1 starting at Bus Station at 22:30.
      • It has an OperationalProfile that says it runs Saturday and Sunday
    8. VJ9 references VJ8 for all its timing links starting at Bus Station at 23:45, so its later stages will take place in the next calendar day.
      • It also inherits its OperationalProfile that says it runs Saturday and Sunday
  • Two of the vehicle journeys VehicleJourney instance, have a day shift.
  • that is although they with different day profile conditions, so different journeys get selected for Monday to Friday and for Saturday and Sunday:
    1. VJ10 Starts after midnight, Monday to Friday, at 00:10 so its stages will take place in the next calendar day, though it is part of the MondayToFriday Timetable
      • It has an OperationalProfile that says it runs MondayToFriday, and a DayShift=+1
    2. VJ11 Starts before midnight, Saturday and Sunday, at 00:10  so some of its  stages will take place in the previous calendar day, though it is part o thef Saturday and Sunday Timetable
      • It has an OperationalProfile that says it runs Saturday and Sunday, and a DayShift=-1

Operational Profile
  • On the JourneyPattern, OperationalProfile / RegularDayType/ DaysOfWeek / MondayToSunday states that by default that the service runs everyday of the week.
  • Some eight VehicleJourney instances, override this:
    • VJ2, VJ6 & VJ7, VJ10 run only Monday to Friday.
    • VJ3 inherits its profile from VJ2 Monday to Friday.
    • VJ4 overrides the V2 profile does not run on Thursday.
    • VJ7, VJ8, VJ11 run only Saturday & Sunday.

Operational Details
  • The Operator has a Garaged 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.
  • There are different variants for different days of the week.

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

Circular route image


Page last updated: 2010/03/04

UKGovTalk logo