Content

...

Content

This document contains additional information for the Nordic NeTEx profile, including overall data models and conceptual descriptions of how the elements from NeTEx will be used.

...

...

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):

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. 

...

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 DayTypes 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

...

When describing a deviation from the common departure pattern, the OperatingDay, can be described in inverse by When the nature of the service requires a permanent ID per service, e.g. with tickets associated to a specific departure on a specific day, rather than having a loose coupling to a ServiceJourney with multiple associated DayTypes these should be defined as individual DatedServiceJourneys with an associate ServiceJourney specifying the nature of the service and an  OperatingDay defining on which date it is serviced. Should such a DatedServiceJourney be replanned or replaced, (a) new DatedServiceJourney(s) referencing the originally planned DatedServiceJourney should be specified.

NeTEx conceptual model for DatedServiceJourney

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.

...