TransXChange

Examples 2.4 - Grouping route (TXC v2.4)

Summary

A linear route with Custom Grouping of journeys to create additional bed.

  • Custom Grouping of service journeys (TXC v2.4).
  • Override labels for Journey groupings (TXC v2.4).
  • Suppression of a Built-in journey Grouping /  Matrix bed (TXC v2.4).
  • Short working.
  • Vehicle journey timing link reuse.
  • Overriding of Journey Pattern Timing Link Run Times with different values on the Vehicle Journey Timing links for some journeys.
  • Additional Wait times at stop; on arrival, on departure, on first or intermediate stops.
  • Monday to Sunday Service. Day Type Restrictions on certain journeys
  • Holiday Day Type Exclusions.
  • Vehicle Journey Footnote.
  • Operational Calendar (TXC v2.4). Day Assignments
  • Data Rights.  (TXC v2.4)
  • Registration Schema.
TransXChange XML Document Particulars and Matrix output PDF Route Map Output
Grouping.xml
(One direction only)		 Particulars and Matrix PDF Route Map PDF
Route Map PDF (no background)


Route Map

Grouping route image

Timetable

This example segregates the journeys in the following table into four  beds (as coloured white, green , orange, yellow)

Saffron Crossroads to Weldon Road
    #1 #2 #3 #4 #5 #6 #7
    E23 E23 E23 E23 E23 E23 E23
Saffron Crossroads

 

 dep 10:00 11:00 12:00 - 14:10 15:10 18:00
Glenhills Boulevard

 

 arr 10:03 11:03 - - 14:18 15:18 18:03
dep 10:03 11:03 - - 14:28 15:28 18:03
Roehampton Drive

 

 dep 10:07 - 12:07 13:07 14:37 15:37 18:07
Carleton Drive

 

 arr 10:20 11:20 - 13:20 - - 18:20
dep 10:20 11:20 - 13:30 - - 18:20
Weldon Road 

 

 dep 10:29 11:29 12:29 13:39 - - 18:29



  • Service operates from 01/01/2004 until 13/06/2004
  • Service operates Monday to Sunday

 

 

1. Built-in Bed: Saffron Crossroads to Weldon Road  E23 Regular Service

The first three journeys and the last  one are added to the built in beds for Monday to Friday, and Saturday  (which are then merged into a single bed because they are the same  T

Outbound, Monday to Saturday
    #1 #2 #4 #7
    E23 E23 E23 E23
Saffron Crossroads

 

 dep 10:00 11:00 - 18:00
Glenhills Boulevard

 

 arr 10:03 11:03 - 18:03
dep 10:03 11:03 - 18:03
Roehampton Drive

 

 dep 10:07 - 13:07 18:07
Carleton Drive

 

 arr 10:20 11:20 13:20 18:20
dep 10:20 11:20 13:30 18:20
Weldon Road 

 

 dep 10:29 11:29 13:39 18:29

 

 

2. Custom  Bed #1 :Saffron Crossroads to Weldon Road  Express

The express Journey is shown in a custom bed

Outbound, Express

    #3
    E23
Saffron Crossroads dep 12:00
Roehampton Drive dep 12:07
Weldon Road dep 12:29


3. Custom Bed #2.: Saffron Crossroads to Weldon Road , Tuesday & Thursday only

The two short working Journeys #5 #6 are shown in a another custom bed

    #5 #6
    E23 E23
Saffron Crossroads dep 14:10 15:10
Glenhills Boulevard arr 14:18 15:18
dep 14:28 15:28
Tweeham, Roehampton Drive dep 14:37 15:37


 Service runs Tuesdays and Thursdays only


4. Suppressed Bed

The Sunday built in journey grouping , is suppressed completely: this means that the last Journey, #7, which is in both the Monday to Friday, Saturday and the Sunday bed, appears as a Monday to Saturday journey but that there is no Sunday bed.

 

    #7
    E23
Saffron Crossroads, Bay Area dep 18:00
Glenhills Boulevard arr 18:03
dep 18:03
Roehampton Drive dep 18:07
Carlton Drive arr 18:20
dep 18:20
Weldon Road dep 18:29



 

In this example the last journey overrides the default run times . In additional wait times are specified for some stops. The following table shows the timetable additionally annotated with the vehicle journey run times ( default values inherited from the journey pattern shown in brackets) and the wait times (additional wait times prefixed by a +).

  JP Run
Time (Mins)		   VJ run & Wait #1 VJ run & Wait #2 VJ run & Wait #3 VJ run & Wait #4 VJ run & Wait #5 #6 VJ run & Wait #7
        E23   E23   E23   E23   E23 E23   E23
    start   10:00   11:00   12:00       14:00 15:00   18:00
                               
Saffron Crossroads   dep   10:00   11:00   12:00     +w10 14:10 15:10   18:00
  r3   (r3)   (r3)   (r3)   sr   +r8     (r3)  
Glenhills Boulevard   arr   10:03   11:03 pass       +w10 14:08 15:08   18:03
  dep   10:03   11:03 pass   sr     14:28 15:28   18:03
  r4   (r4)   (r4)   (r4)       +r9     (r4)  
Roehampton Drive   dep   10:07 pass     12:07   13:07   14:37 15:37   18:07
  r13   (r13)       (r13)   (r13)   sr     (r13)  
Carlton Drive   arr   10:20   11:20 pass     13:20   - -   18:20
  dep   10:20   11:20 pass   +w10 13:30   - -   18:20
  r9   (r9)   (r9)   (r9)   (r9)   sr     (r9)  
Weldon Road   dep   10:29   11:29   12:29   13:39         18:29



The XML Representation

One way encoding this example would be to have a separate route and journey pattern for each column, thus there would be five routes and five journey patterns, each with a single section. Since however the vehicle travels over the same route in the same order, but just passes by certain stops it is possible also to encode it in a less verbose manner by having a single journey pattern with an stop activity of pass at certain stops.

XML Document

Service Registration

  • The service is not registered
  • There is a single Operator. code "Op_02", with id 01.

Service Structure

  • There is a single Service instance SV1, with one Line - '1'.
  • There are six  on-street StopPoint , all references to existing NaPTAN stops.
  • There is a single RouteSection rs_1 with four RouteLink instances rl_1-rl_4 connecting the stops.
  • There is a single JourneyPatternSection JPS1 made up of four JourneyPatternTimingLink instances, JPTL1-4, with RunTime values of 3, 4, 13, and9 minutes respectively.
  • There is a single JourneyPattern instances;
    • JP_1, section: JS_1
  • There are six VehicleJourney instances, all for Ln_1 - 'E23', and using JP1. The instances all use the same set of JourneyPatternTimingLink instances, but define different stop activities (e.g. pass) to specify the different express stopping patterns:
    • VJ_1, with a departure time of 10:00, stopping at all stops. VJ_1 appears in column #1.
      • There is a variable stop allocation the bay in the Saffron Crossroads, specified on the From part of the first VehicleJourneyTimingLink - see below.
    • VJ_2, with a departure time of 11:00 (column #2), which has a timing links annotated with a VehicleJourneyStopUsage / Activity of 'pass' for the Roehampton Drive stop to indicate that the bus does not stop there.
    • VJ_3, with a departure time of 12:00 (column #3), which has a VehicleJourneyStopUsage / Activity of 'pass' for Glenhills Boulevard. and for Carlton Drive.
    • VJ_4, with a departure time of 13:07 (column #4), which has a short working: a dummy StartDeadRun is used to indicate that the service starts at Roehampton Drive.
      • There is an extra WaitTime of 10 Minutes on departure from the Carlton Drive stop, specified on the From usage of VehicleJourneyTimingLink VJ4_TL4.
    • VJ_5, with a departure time of 14:00 (column #5), which has a short working: a dummy EndDeadRun is used to indicate that the service ends at Roehampton Drive.
      • A DynamicDestinationDisplay of Roehampton Drive. is used to override the default destination of Weldon Road .
      • Both links of this journey takes longer so has a explicit override values of 8.00 and 9.00 minutes for the RunTime on the VehicleJourneyTimingLink instances of the Journey.
      • There is an extra WaitTime of 10 Minutes on arrival at the Glenhills Boulevard stop, specified on the To usage of VehicleJourneyTimingLink VJ5_TL1.
    • VJ_6, with a departure time of 15:00 (column #6), Reuses the links from VJ_5.

The Operating Days

  • The Service operating period for SV_1 starts on 02/01/2002 for all vehicle journeys and continues indefinitely
  • The OperatingProfile for the Service SV_1 states values that apply to all journeys unless overridden on a journey pattern or individual vehicle journey.
    • The RegularDayType specifies journeys of the service run Monday to Sunday every week of the year
    • The BankHolidayOperation / DaysOfNonOperation states journeys of the service do not run LateSummerBankHolidayNotScotland, MayDay, EasterMonday, ChristmasDayHoliday, NewYearsDayHoliday,
      ChristmasEve, NewYearsEve.
    • The SpecialDaysOperation / DaysOfOperation states that journeys of the service are will run on 01/06/2004 regardless.
    • The SpecialDaysOperation / DaysOfNonOperation states that all services will not run on 02/06/2004.
    •  VJ_5, VJ_6, Have an override profile that say they run only on Tuesdays & Thursdays

The Journey Groupings

  • Three Outbound Built in Journey Groupings are included
    • MondayToFridayJourneyGrouping with description  "E232 Regular" and Vias "Glenhills Boulevard", "Market" and "Carlton Drive".
    • SaturdayJourneyGrouping with description  "E232 Saturday Short Service" and Vias "Glenhills Boulevard" only.
    • SundayJourneyGrouping with Contents / None to suppress the matrix.

     

  • Two CustomJourneyGroupings are added for
    • cusgrp_01 with description  "E232 Express" and Vias / None. It includes VehicleJourneys Vj5 and Vj6.
    • cusgrp_02 with description  "E232 Sunday Short" and  Vias "Glenhills Boulevard". It includes VehicleJourney Vj3 only.

The Data Rights

  • Two sets of DataRights are specified
    • For the Operator.   01. (Speedy buses) there is is a single right dr_01 permitting unrestricted use under the given  terms and conditions
    • For the Contributor.   02 (Rival buses) there is is a single right dr_02 requiring a  commercial licences for use of tagged items and use under separate  terms and conditions.
  • The DataRights are referenced as follows
    • The document references dr_01, indicating all of the contents except where specifically excluded are available under the associated terms.
    • VehicleJourney Vj3 reference dr_02 indicating it is owned by  Rival buses and subject to different rights.

The Calendar

  • A Calendar specifies the DayAssignments for Christmas 2010 
    • Three separate  DayAssignments specify the service for  well known bank holidays ChristmasEve, ChristmasDay and BoxingDay to use the day types  day_01, day_02, Day_02 respectively.
    • Four  DayAssignments specify the service for a special holiday "Slevin Day" as type Day_03. 

 


Page last updated: 2013/03/30.

>