Network Exchange (NeTEx)  CEN TC 278 WG9

 

List of Examples

Group Name Description & Features XML Provider
Tactical Simple Network Example of Simple  Line 66 : two branches, five stop places, links in two directions
             - D
A - B - C <
             - E 
  • Scheduled Stop Points:
    •  Aa, (Ba, Bb), (Ca, Cb), D, E
      • SSP0001A, SSP0002Ba, SSP0002Bb, SSP0003Ca, SSP0003Cb, SSP0004D, SSP0005E
  • Stop Places A, B, C , D, E
    • Quays
      • A: Q_SP001A_1,
      • B: Q_SP002B_1, Q_SP002B_2
      • C: Q_SP003C_1, Q_SP003C_2,
      • D: Q_SP004D_1,
      • E: Q_SP003E_1
  • Routes in each Direction: : route points are centreline of road.
    • A - Ba - Ca - D
    •   /  D - Cb - Bb- A
      • RT001o seven points A - [rp21 - Ba - rp22 -rp2 5 - Ca - D
      • RT001i seven points D - Cb - rp25 - rp22 Bb - rp21 - A
    • A - Ba- Ca - E  /  E - Cb - Bb - A
      • RT001o seven points: A - rp21 - Ba - rp22 -rp2 5 - Ca - E
      • RT001i seven points: E - Cb - 25 - rp22 - Bb - rp21 - A
  • Service pattern in each direction
    • A - Ba - Ca - D
    • /  D - Cb - Bb- A
      • SvP001o: A - Ba - Ca - D Points A, Ba, C, D Links A-Ba, Ba-Ca, Ca-D
      • SvP001i: D - Cb - Bb -A : Ba, Links D - Cb, Cb-Bb, Bb - A
    • A - Ba- Ca - E  /  E - Cb - Bb - A
      • SvP002o: A - Ba - Ca - E Points A, Ba, C, D Links A-Ba, Ba-Ca, Ca-E
      • SvP002i: E - Cb - Bb -A : Ba, Links E -Cb, Cb-Bb, Bb - A
  • Timing Pattern in each direction
    • A - Ba - Ca - D
    • /  D - Cb - Bb- A
      • TP001o : A - Ba - TP51 - Ca - D
      • TP001i  : D - Cb - Bb - A
    • A - Ba- Ca - E  /  E - Cb - Bb - A
      • TP002o A - Ba - TP51 - Ca - E
      • TP002i E - Cb - Bb - A
  • Journey Pattern in each direction
    • A - Ba - Ca - D
    • /  D - Cb - Bb- A
      • JP001:o A - Ba - C - D
      • JP001i: D C - Bb - A
    • A - Ba- Ca - E  /  E - Cb - Bb - A
      • JP002o A - Ba - C - E
      • JP002i E- C -Bb -A
  • Timing Demand : TP001 peak
  • Two different Responsibilities
    • Stop Places
      • myBus:RS_10,
    • Service Patterns
      • hde:RS_22
  • Infrastructure elements
    • Road
      • 1 FooSt , 2 BarLane,  3 FumAv 4
      • A ..20mB.. ..30mC
  • Infrastructure restrictions
XML nk
Tactical Service & Journey Patterns Example of Service journey with projections between layers

Based on Paris Route example

  • Different Responsibilities & namespaces
    • ssp:RS_02 ; Service pattern owner
    • tim:RS_03, Timing pattern owner
    • spq::RS_01 Stop Places and route owner
  • Scheduled Stop Points
    • SSP1,-SSP2, SSP3,SSA4, SSP5, SSP6, SSP7, SSPY, SSP9
  • Service pattern: outbound
    • SvP001o: SSP1 - SSP2 - SSP3 - SSA4 - SSP5 - SSP6 - SSP7 - SSPY - SSP9
  • Timing Pattern: outbound
    • TP001o: TP1 - TP2=SSP1 - TP£ - TP4 - TP5 - TP6=SSP9 TL_1to2, TL_2to3, Tl_3to4, TL_4to5, TL5to6,
  • Routes in each Direction: : route points are centreline of road.
    • points: PoR1 - PoR2 - PoR3 - PoR4 - PoR5 - PoR6 - PoR7 - PoR8 - PoR9 - PoR10
    • RT001o: points: rpA - [rp21 - rpBa - rp22 -rp2 5 - rpCa - rpD
    • RT001o: links: RL_1to2 - RL_2to3 - RL_3to4 - RL_5to6, RL_6to7, RL_ 7to8, Rl_8to9, Rl_9to10
  • Journey Pattern outbound
    • JP001o TP1, TP2=SSP1 - SSP2 - SSP3 - TP3 - SSA4 - SSP5 - SSP6 - TP4 - TP5 - SSP7 - SSP8 - TP6=SSP9
  • Projections
    • Timing Pattern to Route

      Timing Points Projected onto Route Points

      • TP1 :: PoR1,
      • TP2 ::> Por2 ,
      • TP3 ::> Por5
      • TP4 ::> Por8,
      • TP5 ::> [RL_8to9, d1] ,
      • TP6 ::> Por10 TL_1to2
    • Timing Links Projected onto Route Links

      • TL_1to2 :::> [RL_1to2, 0,0 ]
      • TL_2to3 ::> [RL_2to3, 0,0 ], [RL_3to4, 0,0 ], [RL_4to5, 0,0 ],
      • TL_3to4 ::> [RL_5to6, 0,0 ], [RL_6to7, 0.0 ], [RL_7to8, 0.0 ],
      • TL_4to5 ::>, [RL_7to8, 0.0 ], [RL_8to9, 0.d1 ],
      • TL_5to6 ::> [RL_8to9, d1,.0 ], [RL_9to10]

       

    • Service Pattern to Route

      Service Links Projected onto Route Links

      • SSP1 ::> PoR1,
      • SSP2 ::>[RL_1to2, d1] ,
      • SSP3 ::> [RL_3to5, d1]
      • SSP4 ::> [RL_5to6, d1] ,
      • SSP5 ::> [RL_7to8, d1] ,
      • SSP6 ::> [RL_8to9, d1] ,
      • SSP7 ::> [RL_9to10, d1] ,
      • SSP8 ::> [RL_9to10, d2] ,
      • SSP9::> Por10
    • Service Links Projected onto Route Links

      • sL_1to2:::> [RL_2to3, 0,d1 ]
      • SL_2to3 ::> [RL_2to3, d1,0 ], [RL_3to4, 0,0 ], [RL_4to5, 0,d2 ],
      • Sl_3to4 ::> [RL_4to5, d2 , 0 ], [RL_5to6, 0,d3 ],
      • SL_4to5 ::> [RL_5to6, d3,0], [RL_6to7, 0.0 ],RL_7to8, 0, d4 ],
      • SL5to6::>[RL_7to8, d4., 0 ], [RL_8to9, 0,.d5 ], [
      • SL6to7::> [RL_8to9, d5,.0 ], [RL_9to10, 0,d6 ]
      • SL7to8::> [RL_9to10, d6,d7]
      • SL8to9::> [RL_9to10, d7,0]
  • Features
    • Road elements / Road Junctions
      • Rue de Paris - Rue de L'est, Route De La Reine - Rue Thiery... etc etc
  • Stop Places
      • SP1, SP2 , SP3 ,SP4, SP5, SSP6, - SP7, -SP8 SP9
    • Quays
      • SSP1, SSP2, SSP3, SSA4, SSP5, SSP6, SSP7, SSP8, SSP9
  • Stop Assignments ssp:SSP1=spq:SSP1 etc
    • Scheduled Stop Points to Quays
    XML NK based on KB paper
    IFOPT Stop Place Urban Station (UK)   This example provides an IFOPT representation of Wimbledon Station based on a UK DfT paper . This is a busy urban station with several transport modes. The example includes detailed accessibility data.

    See plan and Navigation path summaries  to, from and between entrances and platforms.

    • Stop Places
      • Rail Station
      • Metro Station
      • Tram Station
      • Bus  Stops
      • Taxi Rank
    • Quays
      • 4 Metro platforms in two pairs (pl 1-4)
      • 4 Bus stops (P, C, D , L)
      • 6 Rail Platforms in three pairs (pl 5-10)
      • Lower concourse for Metro
      • Taxi Rank
      • Set down point
    • Navigation Paths
      • 1 lift and 1 stair to each Rail pair
      • 1 lift and 1 stair to shared concourse for Metro
      • 1 Tram Platform (Shared with Rail (10)
    • Entrances
      • Entrance to Main Ticket Hall
      • entrance to Side Ticket Hall from Centre court
    • Access Spaces
      • Main Ticket Hall
      • Side Ticket Hall
      • Upper concourse
      • Upper Concourse Lift Corridor
      • Bicycle storage area
    • Equipment
      • Barriers to entrance
    • Responsibilities
      • Rail & Tram data is responsibility of DfT
      • Bus data is responsibility of London
      • Ids corresponding to existing data are shown in namespace napt:
      • Ids corresponding to additional data are shown in namespace tbd:
     
    XML DftT UK (nk)
    Part 1 IFOPT
    Stop Place Urban Station (SE)

    Representation of Tekniska Högskolan which is used for Bus and Metro in Stockholm (reduced)

    • Quays
      • 2 Metro platforms in two pairs (pl 1-4)
      • 2 Bus stops (P, C, D , L)
      •  
    • Navigation Paths
      • 1 lift and 1 stair to each Rail pair
      • 1 lift and 1 stair to shared concourse for Metro
      • 1 Tram Platform (Shared with Rail (10)
    • Entrances
      • Entrance to Main Ticket Hall
      • entrance to Side Ticket Hall from Centre court
    •  
    • Responsibilities
      • Rail & Tram data is responsibility of Dft
      • Bus data is responsibillity of London
      • Ids corresponding to existing data are shown in namespace napt:
      • Ids corresponding to additional data are shown in namespace tbd:
     
    XML Hogia (ub)

     

    logo

    © Copyright CEN NeTEx 2009
    Page last updated: 2010/07/05