TransXChange

Examples 2.5 - 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 after midnight on Saturday but should be shifted to be shown as starting on the Monday to Friday service i.e. be  shifted to a different bed and marked with a note that they are in a different day. (TXC v2.4)
  • Partial Traversal of Route / Journey Pattern.
  • Dead runs, Positioning links (Including TXC v2.4 duty crew).
  • 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

Journeys

Bus Station - High Street - Hospital - Bus Station.

    Based on Ref to JP1 JP1 JP1 VJ2 VJ2 JP1 JP1 JP1 JP1 JP1 JP1
    Links based on ->JP1 JP1 + start
dead
run		 ->JP1 ->VJ2 ->VJ2 P1 + end
dead
run		 ->JP1 ->JP1 ->JP1 ->JP1 ->JP1
    Operational Profile Override ->JP1 Override ->VJ2 Override ->JP1 Override Override Override Override Override
VJ #A #1 #2 #3 #4 #5 #6 #7 #8 #B #C
Line 1 Night 1 1 1 1 ++ 1 1 Night 1 Night 1 Night 1 Night 1 Night
Days

Of Week

 Service MTWTFSS MTWTFSS MTWTFSS  -- MTWTFSS MTWTFSS MTWTFSS MTWTFSS MTWTFSS MTWTFSS MTWTFSS
Vehicle Journey MTWTF--

"

 MTWTF--

(MTWTF--)

 c

"

 MTWTF-- MTWTF-- -----SS -TWTFS- -----F-
    DayShift -1 0 0 0 0 0 0 0 0 +1 +1
    Actual Days MTWT--S MTWTFSS MTWTF-- MTWTF-- MTW-FSS MTWTFSS MTWTF-- MTWTF-- -----SS -TWTFS- ------S-
    Beds MF MF, SS MF MF MF, SS MF, SS MF MF SS MF MF
    Dep (23:55) (10:29) (11:00) (12:00) (13:00) (14:00) (22:30) (23:30) (23:33) (00:00) (00:10)
xL1   Bus Station 23:55** - 11:00 12:00 13:00 14:00 22:30 23:30 23:33 00:10* 00:20*
xL2 High St 23:58** - 11:03 12:03 13:03 14:03 22:33 23:33 23:37 00:13* 00:23*
xL3 Market St 00:02 - 11:07 12:07 13:07 14:07 22:37 23:37 23:50 00:17* 00:27*
xL4 School 00:15 - 11:20 12:20 13:20 14:20 22:50 23:50 23:59 00:30* 00:40*
xL5 Hospital 00:24 10:29 11:29 12:29 13:29 14:29 22:59 23:59 00:18* 00:39* 00:49*
xL6 Library 00:43 10:48 11:48 12:48 13:48 - 23:18 00:18* 00:30* 00:58* 01:08*
  Bus Station 00:55 11:00 12:00 13:00 14:00 - 23:30 00:30* 00:42:* 01:10* 01:20*
  Sunday to Friday Everyday Monday to Friday Monday to Friday Not Thursday Everyday Monday to Friday Monday to Friday Saturday & Sunday Only Tuesday to Saturday Fridays Only

* Next Day

 

Timetable - Clockwise, Monday to Friday

Bus Station - High Street - Hospital - Bus Station.

VJ #A #1 #2 #3 #4 #5 #6 #7 #B #C
Line 1 Night 1 1 1 1 ++ 1 1 Night 1 Night 1 Night 1 Night
Days

Of Week

 Actual Days MTWT--S

MTWTFSS

 MTWTF--

MTWTF--

 MTW-FSS

MTWTFSS

 MTWTF-- MTWTF-- -TWTFS- ------S-
Days of week MTWTF-- MTWTFSS MTWTF-- MTWTF-- MTW-FSS MTWTFSS MTWTF-- MTWTF-- MTWTF-- -----F-
DayShift -1 0 0 0 0 0 0 0 +1 +1
    Dep (23:55)) (10:29) (11:00) (12:00) (13:00) (14:00) (22:30) (23:30) (00:00) (00:10)
xL1   Bus Station 23:55** - 11:00 12:00 13:00 14:00 22:30 23:30 00:10* 00:20*
xL2 High St 23:58** - 11:03 12:03 13:03 14:03 22:33 23:33 00:13* 00:23*
xL3 Market St 00:02 - 11:07 12:07 13:07 14:07 22:37 23:37 00:17* 00:27*
xL4 School 00:15 - 11:20 12:20 13:20 14:20 22:50 23:50 00:30* 00:40*
xL5 Hospital 00:24 10:29 11:29 12:29 13:29 14:29 22:59 23:59 00:39* 00:49*
xL6 Library 00:43 10:48 11:48 12:48 13:48 - 23:18 00:18* 00:58* 01:08*
  Bus Station 00:55 11:00 12:00 13:00 14:00 - 23:30 00:30* 01:10* 01:20*
    Sunday to Friday     Not Thursday       Tuesday to Saturday Fridays Only

Footnotes

Service runs Monday To Friday

** Previous Day

* Next Day

++ Not Thursday

Timetable Clockwise, Saturday & Sunday

Bus Station - High Street - Hospital - Bus Station

VJ #1 #4 #5 #8
Line 1 1 1 1 Night
Days
Of
Week		 Actual Days

MTWTFSS

 MTW-FSS

MTWTFSS

 -----SS
Days of Week MTWTFSS MTW-FSS MTWTFSS -----SS
DayShift 0 0 0 0
xL1   Dep (10:29) (13:00) (14:00) (23:30)
xL2 High St - 13:03 14:03 23:33
xL3 Market St - 13:07 14:07 23:37
xL4 School - 13:20 14:20 23:50
xL5 Hospital 10:29 13:29 14:29 23:59
xL6 Library 10:48 13:48 - 00:18*
  Bus Station 11:00 14:00 - 00:30*
        Not Thursday   * next day


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 only.
  • Three of the  VehicleJourney instances, are day shifted  in a different bed,  so that a journey that actually takes place on saturday morning appears as part of the Monday to Friday service (with a footnote) and a journey that actually takes place late on sunday night is grouped as a Monday to Friday service. 
    1. VJ_A follows all six links of JP1 for all its timing links starting at Bus Station at 00:10, .
      • It has an OperationalProfile that says it runs Tuesday, Wednesday, Thursday, Friday and Saturday.
      •  A negative Day shift causes it to placed in the MondayToFriday  bed as the first journey of the day.
    2. VJ_B follows all six links of JP1 for all its timing links starting at Bus Station at 00:20, .
      • It has an OperationalProfile that says it runs only on Saturday.
      •  A negative Day shift causes it to placed in the MondayToFriday  bed at the beginning of the day.
    3. VJ_C follows all six links of JP1 for all its timing links starting at Bus Station at 23:55, .
      • It has an OperationalProfile that says it runs Sunday, Monday, T uesday, Wednesday, , and Thursday.
      •  A negative Day shift causes it to placed in the MondayToFriday  bed as the first journey of the day.

Operational Profile
  • On the JourneyPattern, OperationalProfile / RegularDayType/ DaysOfWeek / MondayToSunday states that by default that the service runs everyday of the week.
  • Some  VehicleJourney instances, override this as described above

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: 2013/04/13