Content
| Table of Contents | ||
|---|---|---|
|
...
Connection between Route and JourneyPattern
As shown in earlier example RoutePoint vs PointOnRoute a Route is defined as a set of RoutePoints in a given order, here illustrated by two routes (red and pink respectively):
| Gliffy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
How this route is operated is further defined by the JourneyPattern which consists of a set of ScheduledStopPoints in a given order, and these again refer to each respective Route.
| Gliffy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
It is also possible to describe rhytm based departures (for example repeating departures every 10 minutes over whole hours), or interval based departures (for example departures every 15 minutes), for a defined period of the day using JourneyFrequencyGroup which TemplateServiceJourney can refer to. Alternatively a list of stop places for a ServiceJourney can be created by using PassingTime objects refering to stops through a ScheduledStopPoint.
NeTEx data model for Vehicle Journey
...
This means each departure is defined as a ServiceJourney (usually connected to a Line), used by a JourneyPattern with one or more DayType (describing dates or periods). The ServiceJourney describes the times of arrival and departure along the journey by use of StopPointInJourneyPattern for stop, with a PassingTime defining the exact times.
NeTEx conceptual model for ServiceJourney
...
NeTEx conceptual model for DatedServiceJourney
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Deviations
When describing a deviation from the common departure pattern, the OperatingDay, can be described in inverse by define the particular day(s) as unavailable.
Data enrichment
As mentioned above, a trip can be specified on several levels in NeTEx, ranging from the parent Route via detailed JourneyPattern down to the individual ServiceJourney.
...