JourneyPattern (Abstract in EPIP), ServicePattern

The JOURNEY PATTERN model is concerned with the spatial description of services, i.e. spatial aspects of the work of the vehicles. The concerns of this model are different from those of describing the ROUTEs and LINEs. The latter are describing schematic paths of vehicles through the road network, whereas JOURNEY PATTERNs describe how the work of vehicles is performed. These work patterns describe the sequence of points where vehicles stop with specific points being attributed with timing information.

This means that a JOURNEY PATTERN consists of:

An ordered sequence of SCHEDULED STOP POINTs to be served;

An ordered sequence of TIMING POINTs at which timing information is scheduled. These TIMING POINTs may  also be SCHEDULED STOP POINTs or other POINTs. In the EPIP there are no TIMING POINTs that are not SCHEDULED STOP POINTs.

Note: NeTEx allows timing information to be held separately (for example the duration in minutes need to traverse a SERVICE LINK, or the time to wait at a SCHEDULED STOP POINT; this separate data can be used to calculate the actual passing times for many different journeys. In the EPIP only the calculated results are exchanged – as PASSING TIMEs.

The working pattern described by a JOURNEY PATTERN is usually related to a ROUTE it covers. Several JOURNEY PATTERNs may use the same ROUTE (e.g. an express service skipping many stops and a ‘slow’ service stopping at all stops may both follow the same route).

JourneyPattern – XML Element (Abstract in EPIP)

Example from Austrian NeTEx Profile

ServicePattern

A SERVICE PATTERN is made up of an ordered sequence of STOP POINTs IN JOURNEY PATTERN, with a SERVICE LINK between each pair of consecutive SCHEDULED STOP POINTs. As the same SCHEDULED STOP POINT may occur more than once in the same SERVICE PATTERN, a STOP POINT IN JOURNEY PATTERN is identified by that SERVICE PATTERN together with an ‘order’ attribute.

Each STOP POINT IN JOURNEY PATTERN references a specific SCHEDULED STOP POINT.

NOTE           it should be noted that in the terminology of many existing systems and organisations,  the sequence of such points is often called a “line”. However, the objective of Transmodel is the separation of concerns: LINEs are groupings of ROUTEs, i.e. schematic views of physical paths through the network, determined through ROUTE POINTs, whereas SERVICE PATTERNs are sequences of points of another type. Thus, a Transmodel LINE is conceptually different from a grouping of SERVICE PATTERNs even if a link exists (a LINE is a group of ROUTEs and each ROUTE is linked to one or more SERVICE PATTERNs). Of course, from the point of view of the precise physical path (along the road network) both types of points (ROUTE POINTs and SCHEDULED STOP POINTs) are on the INFRASTRUCTURE LINKs taken by the vehicle - but the ROUTE and the SERVICE PATTERN are not the same LINK SEQUENCEs.

ServiceJourneyPattern – XML Element

Example from the Austrian NeTEx Profile