Very frequent journeys

When journeys run at short or regular intervals, rather than list all the journeys, passenger information systems often show multiple journeys as a single column in the timetable. For example “And then every 20 minutes until 6 pm”. Note that this is a convention to simplify the presentation of schedules; the operational timetable implementing the schedule will still require separate DATED SERVICE JOURNEYS for each journey to be run.

The Journey Frequency model (see diagram for SERVICE JOURNEYs) allows multiple journeys to be aggregated using a TEMPLATE JOURNEY and an overall frequency to be specified for them, using for example a HEADWAY JOURNEY GROUP (e.g. ‘every 10 minutes’).

Using an aggregated schedule can also significantly reduce the amount of data that needs to be exchanged.

TemplateVehicleJourney

A TEMPLATE VEHICLE JOURNEY is a repeating VEHICLE JOURNEY for which a frequency is specified as a JOURNEY FREQUENCY GROUP. It may thus represent multiple journeys.

The frequency of the journey is defined by a JOURNEY FREQUENCY GROUP. Two types of JOURNEY FREQUENCY GROUP are possible, ‘headway’ (interval based), and ‘rhythmic’ (minutes past the hour). The EPIP is restricted to using only ‘Headway’JOURNEY FREQUENCY GROUPs.

TemplateVehicleJourney – XML Element

Classification

Name

Type

Cardinality

Description

::>

::>

Journey

::>

TEMPLATE VEHICLE JOURNEY inherits from JOURNEY.

«PK»

id

TemplateVehicleJourney­IdType

0:1

Identifier of TEMPLATE VEHICLE JOURNEY.

«enum»

TemplateVehicle­JourneyType

TemplateVehicleJourney­TypeEnum

0:1

Type of TEMPLATE VEHICLE JOURNEY.

·        headway

·rhythmic

·other

«cntd»

frequencyGroups

JourneyFrequencyGroup

0:*

FREQUENCY GROUPs defining TEMPLATE VEHICLE JOURNEY.

Currently this XML Element is not in use in the Austrian NeTEx Profile

JourneyFrequencyGroup (Abstract)

A JOURNEY FREQUENCY GROUP defines a set of JOURNEYs and a start and end time during which the frequency-based services will run. It is further specialised in order to describe specific frequency behaviour such as headway-based services or rhythmical services.

All the journeys in a JOURNEY FREQUENCY GROUP should follow the same JOURNEY PATTERN. When publishing a TEMPLATE JOURNEY, the JOURNEY PATTERN of the first journey in the group will be used to determine the stops visits for the group as a whole, i.e. at which to show the indicated frequency). EPIP requires at least one Journey to be specified in a JOURNEY FREQUENCY GROUP.

JourneyFrequencyGroup – XML Element

Classification

Name

Type

Cardinality

Description

::>

::>

GroupOfEntities

::>

JOURNEY FREQUENCY GROUP inherits from GROUP OF ENTITies.

«PK»

id

FrequencyGroupIdType

0:1

Identifier of FREQUENCY GROUP.

 

FirstDepartureTime

xsd:time

0:1

Time of the first departure in FREQUENCY GROUP.

 

LastDepartureTime

xsd:time

0:1

Time of last departure in FREQUENCY GROUP.

 

DayOffset

xsd:integer

0:1

Offset of the end-time day from the start time.

«cntd»

timeDemandTypes

TimeDemandRef

0:1

TIME DEMAND TYPEs for which this FREQUENCY GROUP applies.

«cntd»

journeys

VehicleJourneyRef

1:*

Journeys belonging to FREQUENCY GROUP.

Currently this XML Element is not in use in the Austrian NeTEx Profile

HeadwayJourneyGroup (Subcomponent of TemplateJourney)

A HEADWAY JOURNEY GROUP is a group of VEHICLE JOURNEYs following the same JOURNEY PATTERN and having the same headway interval between a specified start and end time (for example, ‘every 10 minutes’).

HeadwayJourneyGroup – XML Element

Classification

Name

Type

Cardinality

Description

::>

::>

JourneyFrequencyGroup

::>

HEADWAY JOURNEY GROUP inherits from JOURNEY FREQUENCY GROUP.

«PK»

id

HeadwayJourneyGroupIdType

0:1

Identifier of HEADWAY JOURNEY GROUP.

 

ScheduledHeadway­Interval

xsd:duration

0:1

Scheduled normal HEADWAY INTERVAL.

 

MinimumHeadway­Interval

xsd:duration

0:1

Minimum HEADWAY INTERVAL.

 

MaximumHeadwa­yInterval

xsd:duration

0:1

Maximum HEADWAY INTERVAL.

 

HeadwayDisplay

HeadwayUseEnum

0:1

How headway is to be displayed to passengers.

 

Description

MultilingualString

0:1

Description of Headway Journey Groups.

Currently this XML Element is not in use in the Austrian NeTEx Profile