TransXChange
Examples 2.0 - Hail & ride route
Summary
- Use of Hail and Ride sections
- Route with Hail and Ride only sections, Non-Hail and Ride stops and mixed stops
- Full lollipop
- Short Notice Registration
- Some locally defined stops
- FrequentService, specified as minutes past the hour
Published as: Hail & ride PDF
Route Map
| Journeys | ||||
|---|---|---|---|---|
| Stops | #1 | |||
| Seaview Road | 10:10 | And then at 10 and 42 minutes past the hour until 1642 | 19:00 | |
| South Heighton | 10:30 | 9:30 | ||
| Newhaven Centre | 10:40 | 20:10 | ||
| Northdown Road | Hail & Ride section | 10:50 | 19:40 | |
| Gibbon Road | Hail & Ride section | 11:00 | 19:50 | |
| Fortis Road | Hail & Ride section | 11:10 | 20:00 | |
| Newhaven Centre | 11:20 | 20:10 | ||
| South Heighton | 11:30 | 20:20 | ||
| Seaview Road | 11:50 | 20:40 | ||
The XML Representation
Service Registration
- The Registration is for a single Operator.
- The Registration is circulated to three authorities.
- It has ShortNoticeRegistration details specified as well.
Service Structure
- Here is a single Service instance SV1, with one Line - 'L1', with LineName 'H145'.
- There are six StopPoint instances:
- Three fixed stops: Seaview Road, South Heighton, Newhaven Centre
- Three HailAndRide section stops: Northdown Road, Gibbon Road Fortis Road. Gibbon Road also has a fixed stop.
- There are three RouteSection instances:
- rs_b1 connecting the outward handle of the lollipop.
- There are two RouteLink instances rl_b5, rl_b6, running Seaview Road - South Heighton - NewHaven Centre
- rs_b2 connecting the hail and ride stops in the lollipop ring.
- There are four RouteLink instances rl_b1 - rl_b4 , running NewHaven Centre - South Heighton - Seaview Road
- rs_b3 connecting the return handle of the lollipop.
- There are two RouteLink instances rl_b7 rl_b8, running NewHaven Centre - South Heighton - Seaview Road
- rs_b1 connecting the outward handle of the lollipop.
- There is a single Route r_b1 containing the route sections rs_b1, rs_b2, rs_b3.
- There are three JourneyPatternSections:
- js_b1 covering the outbound traversal of rs_2.
- There are two JourneyPatternTimingLink instances, jptl_b5 , jptl_b6, each referencing the corresponding route link.
- js_b2 connecting the hail and ride stops in the lollipop ring.
- There are four JourneyPatternTimingLink instances, jptl_b1 -j ptl_b4, each referencing the corresponding route link. The links are marked as Hail And Ride links.
- js_b3 covering the return traversal of rs_2.
- There are two JourneyPatternTimingLink instances, jptl_b7 , jptl_b8, each referencing the corresponding route link.
- js_b1 covering the outbound traversal of rs_2.
- There is a single JourneyPattern, jp_b1, that follows route r_b1.
- There are two VehicleJourney instance,s based on JourneyPattern jp_b1:
- VJ_1, follows JP1 without any changes to the timings on the JourneyPatternTimingLink instances. It has a start time of 10.00. It has a frequent service of every 10 and 42 minutes past the hour, and an end time of 16:42. Journeys will be created that start at 10 and 42 minutes past the hour up to a last departure of 16:42.
- VJ_2, follows JP1 without any changes to the timings on the JourneyPatternTimingLink instances. It has a start time of 19.40.
The Operating Days
- The service OperatingProfile says it runs Monday to Friday every day of the year.
Hail And Ride
Page last updated: 2005/11/01
