TransXChange Examples 2.1 - Interchange Route

Information: TransXChange

• Overview
• Data & Process
• Downloads & Schema
• Documentation
• Examples
• Linear
• Express
• Interchange
• Circular
• Cloverleaf
• Lollipop
• Eye
• Flexible
• Hail & Ride
• Large
• Merged
• Footnotes
• Publisher
• Versioning
• Implementations
• History
• Terms of Use
• Contact

Related UK Standards

• NaPTAN
• National PT Gazetteer
• JourneyWeb 2.1
• JourneyWeb 3.0
• TransXChange
• RtigXml
• GovTalk & e-Gif

Summary 

Two linear routes, connected with an interchange to make a single service.

• Linear route, with different stop visiting pattern at one end.
• An Interchange.
• Express stops, i.e. "Pass" activity where the bus does not stop
• Frequency Based journey times, specified as an interval, but not a frequent service.
• Combining operating days from service, journey pattern and vehicle journey level.
• Timetable Notes.
• More than one operator.
• Return Journeys: Outbound and Inbound Timetables
• Serviced Organisation & School dates.
• Registration Schema.

Published as  PDF

Route Map

Timetable

Line I (Outbound) - Grub Street to Howard's End or Barchester

Timetable Notes

Line I (Inbound) - Barchester or Howard's End to Grub Street

The XML Representation

XML Document 

Service Registration

• The service is not registered.
• There are two Operator instances;
  • O1 - 'Smooth Buses', who register and provide the main service,
  • O2 - 'Smart Buses'  who provide just the journey in column #5 on behalf of 'Smooth Buses'.

Service Structure

• There is a single Service instance SV1, with two Line instances Ln_1 ? ?I1?. and Ln_2 - ?I2?.
• There are seven StopPoint instances, all references to existing NaPTAN stops.
• There are two Route instances s (R_1, R_2), each with a single RouteSection (RS_1, RS_2)
  • RS_1 has four RouteLink instances (RL_1, RL_2, RL_3, RL_4), running 'Grub Street - Tin Pan Alley - Sinister Street - Swann's Way - Howard's End'. Each link has two stop references (RL_1a, RL1b, etc).
  • RS_2 has two RouteLink instances  (RL_5, RL_6) links respectively. running 'Swann's Way - Yellow Brick Road - Howard's End'.

Outbound Journeys

• There are two outbound JourneyPatternSection instances JS_1 and JS_2;  corresponding to the two RouteSection instances, with corresponding journey pattern timing links.
• The outbound service is made up of two JourneyPattern instances;
  • JP_1, section: JS_1,  JourneyPatternTimingLink  instances (JL_1{Rl_1}, JL_2{RL_2}, JL_3{RL_3}, JL_4{RL_4}),  Each journey pattern timing link has two stop usages (JL_1a, JL1b, etc).
  • JP_2, section: JS_2,  JourneyPatternTimingLink  instances JL_5{RL_5}, and JL_6{RL_6}.
• There are four outbound VehicleJourney instances:
  • VJ_1,   for line: Ln_1 over  JP_1,  with a departure time of 8:02.  This appears in column #1.
  • VJ_2,  also for line: Ln_1   with a departure time of 9:02, which references VJ_1 for its links, and so also follows JP_1. 
    • The  Frequency element specifies that is a Frequency Based service with a  ScheduledFrequency  of every 15 minutes  which generates both column #2 and column #3.  However The service is not a statutory Frequent Service (and the interval is greater than 10 minutes), so   FrequentService is false.
  • VJ_3, also for line: Ln_1 ,  with a departure time of 12:02, which references VJ_1 for its links, and so also follows JP_1. This appears in column #4.
  • VJ_4, for line:  Ln_2 -?I1?, over  JP_2. with a departure time of 12:45. This appears in column #5.  It has a different operator of O2.

Inbound Journeys

• There are two inbound JourneyPatternSection instances JS_X1 and JS_X2;  corresponding to the two RouteSection instances, with corresponding journey pattern timing links, specified in reverse order .
• The outbound service is made up of two JourneyPattern instances;
  • JP_Z1, section: JS_X1,  JourneyPatternTimingLink  instances (JL_X1 {RL_4}, JL_X2 {Rl_3}, JL_X3 {Rl_2}, JL_X4 {RL_1}),  Each journey pattern timing link has two stop usages (JL_1a, JL1b, etc).
  • JP_2, section: JS_2,  JourneyPatternTimingLink  instances JL_5{RL_6}, and JL_6{RL_5}.
• There are four outbound VehicleJourney instances:
  • VJ_X1,   for line: Ln_1  ('ln1') over  JP_X1,  with a departure time of 9:00.  This appears in column #1.
  • VJ_X2,  also for line: Ln_1   ('ln1') with a departure time of 10:00,  which references VJ_X1 for its links, and so also follows JP_X1.
    •  The Frequency element specifies that is a Frequency Based service with a  ScheduledFrequency  of every 15 minutes - for which teh publisher generates both column #2 and column #3.  The service is not a statutory Frequent Service, so   FrequentService is false.
  • VJ_X3, also for line: Ln_1,  ('ln1') with a departure time of 13:00, which references also VJ_X1 for its links, and so also follows JP_X1. This appears in column #4.
  • VJ_X4, for line:  Ln_2  ('ln2'), over  JP_X2. with a departure time of 12:45. This appears in column #5.  It has a different operator of O2.

Interchanges

Outbound Journey Interchange

• The service has an outbound JourneyPatternInterchange (JI_1) that connects the two journey patterns (JP_1, JP_2) at specific journey pattern timing link stop usages
  • inbound:  JP_1 : JL_3b,
  • outbound:  JP_2: JL_5a.
• The connection of the two journeys is modelled by two an outbound  VehicleJourneyInterchange instances, one for each of the two vehicle journeys that connect; both reference the journey pattern interchange JI_1.
   
• interchange: VJI_3:  for journey VJ_3  has inbound: VJ_3,: outbound: VJ_4,
• interchange VJI_4:  for journey VJ_4 has inbound: VJ_3,: outbound: VJ_4). 

Inbound Journey Interchange

• The service has an inbound JourneyPatternInterchange (JI_X1) that connects the two journey patterns (JP_X2, JP_X1) at specific journey pattern timing link stop usages
  • inbound:   JP_X2 : JL_X6b,
  • outbound:  JP_X1 : JL_X2a.
• The connection of the two journeys is modelled by two inbound VehicleJourneyInterchange instances, one for each of the two vehicle journeys that connect; both reference the journey pattern interchange JI_X1.
   
• interchange: VJI_X3:  for journey VJ_X3  has inbound: VJ_X3,: outbound: VJ_X4,
• interchange VJI_X4:  for journey VJ_X4 has inbound: VJ_X3,: outbound: VJ_X4). 

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 of SV_1 specifies journeys of the service run Monday to Friday every week of the year.
  • The BankHolidayOperation / DaysOfNonOperation of SV_1 states journeys of the service do not run Christmas (i.e. Christmas Day & Boxing Day) New Year's Day, and Good Friday, but that they do run on all Bank Holiday Mondays.
  • The SpecialDaysOperation / DaysOfOperation  of SV_1 states that  journeys of the service are will run on 02/06/2004 regardless.
  • The SpecialDaysOperation / DaysOfNonOperation states that all services will not run between 09/12/2004 and 15/12/2004 regardless, and also will not run on  01/06/2004.
• There is an override instance of the OperatingProfile for journey pattern JP_1, which applies to all its  VehicleJourney instances: -  VJ1_2, VJ_2, & VJ_3,
  • The SpecialDaysOperation / DaysOfOperation  of JP_1 states that  journeys of the service are will run on 12/16/2004 regardless.
  • The SpecialDaysOperation / DaysOfNonOperation states that all services will not run between 01/11/2004 and 1111/2004 regardless.
• There are override instances of the OperatingProfile for the vehicle journeys VJ_1, VJ_2, & VJ_4, but not for VJ_3, which has the same values as the general service defaults for SV_1.
  • VJ1: OperatingProfile
    • The RegularDayType  states that VJ_1 runs Monday to Friday  in the term time of serviced organisation SO_2 (Dotheboy's).
    • The BankHolidayOperation / DaysOfNonOperation states that VJ_1 does not run on Mayday, differing from the general defaults. VJ_1 still does not run on Christmas (i.e. Christmas Day & Boxing Day) New Year's Day, and Good Friday and Good Friday
  • VJ2:  OperatingProfile
    • The RegularDayType of states that VJ_2 runs Monday to Saturday.
    • The BankHolidayOperation / DaysOfOperation  states that VJ_2 does   run on Boxing Day and New Year's Day.
  • VJ3: OperatingProfile
    • As for Service
  • VJ4: OperatingProfile
    • The RegularDayType states that VJ_4 runs on Wednesday
    • The PeriodicDayType states that VJ_4 furthermore only runs on the first and third weeks of the month.
    • The SpecialDaysOperation / DaysOfOperation VJ_4 states that VJ_4 does run on 5/08/2004.
    • The SpecialDaysOperation / DaysOfNonOperation  states that VJ_4 is does not  run on 05/02/2004, and between 4/08/2004 and 0908/2004 and also not between 508/2005 to 10/08/2005.
• The VehicleJourneyInterchange instances VI_3 & VI_4 which connect VJ_3 and VJ_4 have a validity period from 02/01/2004 to 17/10/2004.

The Service Organisation Days

• VehicleJourney  VJ1 states on its OperatingProfile  that the
  • The service only runs in the  term time of serviced organisation SO2_1 (Dotheboy's).
• There are two ServicedOrganisation   Definitions.
  • A local authority  'Bleakshire LEA' , SO_1
  • Dotheboys, SO_2 which has Bleakshire LEA as its parent.
• The ServicedOrganisation  definition for 'Bleakshire LEA' , SO_1 defines the terms of the school year using working days.
  • Michaelmas Term StartDate 2004-09-01, EndDate 2004-12-23 , exception 2004-11-11
  • Easter Term StartDate 2005-01-01, EndDate 2005-04-30
  • Summer Term StartDate 2005-04-02, EndDate 2005-07-29
• The ServicedOrganisation  definition for Dotheboy's overrides the summer term working days.
  • Summer Term StartDate 2005-04-01 EndDate 2005-07-30

Notes

This example was refined for in the 2.1 Enhanced publisher to  not be a Frequent Service

© Crown copyright 2006.
Page last updated: 2006/12/28