TransXChange

Examples 2.1 - 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 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
Partial Traversal of Route / Journey Pattern
Dead runs (positioning links)
Operator Garage
Dynamic Destination Displays
Fare Stages
Vehicle Type, Ticket Machine, Duty crew

Route Map

Circular route image

Timetable - Clockwise, Monday to Friday

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

++ Not Thursday

Bus Station - High Street - Hospital - Bus Station

Clockwise, Saturday & Sunday

Based on Ref to

JP1

VJ2

JP1

VJ8

Links based on

JP1 + start
dead
run

->VJ2

JP1 + end
dead
run

->JP1

->VJ2

Operational Profile

->JP1

Override

->JP1

Override

Line

1 Night

xL1

Bus Station

13:00

14:00

22:45

23:45

xL2

High St

13:03

14:03

22:48

23:48

xL3

Market St

13:07

14:07

22:53

23:52

xL4

School

13:20

14:20

23:05

00:05

xL5

Hospital

10:29

13:29

14:29

23:14

00:14

xL6

Library

10:48

13:48

23:33

00:33

Bus Station

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 Serviceinstance 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 JourneyPatternTimingLinkinstances, 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 eight 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

Operational Profile

On the JourneyPattern, OperationalProfile / RegularDayType/ DaysOfWeek / MondayToSunday states that by default that the service runs everyday of the week.
Some eight VehicleJourneyinstances, override this
- VJ2, VJ6 & VJ7 run only Monday to Frida
- VJ3 inherits its profile from VJ2 Monday to Friday
- VJ4 overides the V2 profile does not run on Thursday
- VJ7, VJ8 run only Saturday & Sunday

Operational Details

The Operator has a Garagedefined
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 specifie
- A default RunningBoard is specifie
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'.

Circular route image

Page last updated: 2013/04/13