TransXChange Examples 2.1 - Large Route
 

Summary 

Registration for a set of long routes 

  • Many stops, requiring page breaking vertically to publish.
  • Many vehicle  journeys, requiring page breaking horizontally  to publish.
  • Some operational date rules.
  • Sharing of Sections & Journeys.
  • Timing links with zero values.
  • Multiple Frequency based services,breaking horizontally  to publish.

Published as:  PDF 

Route Map

 

Timetable

The XML Representation

XML Document 

  • There is a single Service instance SV1, with one Line - 'A1'.
  • The service has more stops than will fit on a single  page and more journeys than will fit on a single page.

Service Registration

  • The service is  Registered.
  • There is a single Operator.

Service Structure

  • There is a single Service instance SV1, with one Line - 'A1'.
  • There are 31 StopPoint instances, more  than will fit vertically on a single  page
  • There are two RouteSection rs_1 and rs_2 with RouteLink instances  connecting the stops.
  • There are two JourneyPatternSection jp_s1 and jp_s2 made up of five and 25  JourneyPatternTimingLink instances respectively.
  • There is a single JourneyPattern instance JP_1, with two sections: JS_1 and js_2.
  • There are 27 VehicleJourney instances, all for Ln_1, more than will fit horizontally on a single page . The first journey vj_1 is based on JP1, all the others are based on VJ_1, with different times.  The journeys fall into two groups.
    • Vj_1-20 which are single services and demonstrate page overflow for simple columns.
    • Vj_2127 which are marked as frequent service and demonstrate page overflow for frequency based service column groups.