Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Current version for timetable is:   v1.5   (last changed 27 Apr

Content

Table of Contents
excludeContent

...

Info

An abstract type which describes a departure/journey.

See definition under General information

Examples in the GitHub-repository (replacement transport)

Journey < LinkSequence < DataManagedObject

Name

Type

Cardinality

Description

Description

MultilingualString

0: 1

Description of the departure

TransportMode

AllVehicleModesOfTransportEnumeration

0: 1

Transport mode, see Mode in Transport Modes for possible values (with accompanying submodes).

Note that when overriding the mode for a Journey, both TransportMode and TransportSubmode must be specified.

TransportSubmode

TransportSubmode

0: 1

Transport submode

See Submode in Transport Modes for possible values (must be a submode of specified TransportMode)

Note that when overriding the mode for a Journey, both TransportMode and TransportSubmode must be specified.

ExternalVehicleJourneyRef

ExternalObjectRef

0: 1

Reference (ID) to original ServiceJourney when specifying replacement traffic.

Note that replaced ServiceJourneys (if ID is referred to by ExternalVehicleJourneyRef) must also be part of the dataset (even in cases of partial delivery) to ensure the validity of the reference.

Monitored

xsd:boolean

0: 1

Specifies whether real-time information is available for the departure.

...

Info

A planned journey from starting point to a destination, according to a JourneyPattern.

See definition under General information

VehicleJourney < Journey < LinkSequence  < DataManagedObject 

Name

Type

Cardinality

Description

PrivateCode

xsd:normalizedString

0: 1

Internal code (non-public identifier) for the journey (e.g. train- or trip number from the planners' tool)

DepartureTime

xsd:time

0: 1

Time of departure for the journey.

Frequency

Frequency

0: 1

Frequency or interval for departures.

Used only for frequency-based departures.

JourneyDuration

xsd:duration

0: 1

The total duration of the journey.

RouteRef

RouteRef

0: 1

Reference to Route (not mandatory for ServiceJourney, as this can be derived from JourneyPatternRef)

PublicCode

xsd:normalizedString

0: 1

Public code or identifier for the journey

Used only when for example the line number is changed per trip or has extraordinary overrides.


waitTimes

VehicleJourneyWaitTime

0: *

Description of wait times at TimingPoints

Normally used only when describing frequency-based departures.

runTimes

VehicleJourneyRunTime

0: *

Description of run times between TimingPoints

Normally used only when describing frequency-based departures.

passingTimes

TimetabledPassingTime

1: *

Description of planned passing times at StopPoints or TimingPoints

parts

JourneyPart

0: *

List of the parts of the journey. Used in special cases such as combined journeys.

...

Info

A part of a journey, used for example when creating compound train journeys. 

See definition under General information

JourneyPart < DataManagedObject 

Name

Type

Cardinality

Description

Description

MultilingualString  

0: 1

Description

MainPartRef

JourneyPartCoupleRef

1: 1

Reference to the main part of the journey

JourneyPartCoupleRef

JourneyPartCoupleRef

0: 1

Reference to CoupledJourney to which this journey part belongs.

TrainNumberRef

TrainNumberRef

0: 1

Reference to TrainNumber for the journey part

FromStopPointRef

ScheduledStopPointRef

0: 1

The starting point for the journey part (ScheduledStopPoint)

ToStopPointRef

ScheduledStopPointRef

0: 1

The destination for the journey part (ScheduledStopPoint)

StartTime

xsd:time

1: 1

Start-time

EndTime

xsd:time

1: 1

End-time

...

Info

The frequency for a journey, i.e. the time interval between each departure in frequency based traffic.

See definition under General information

Frequency < DataManagedObject 

Name

Type

Cardinality

Description

ScheduledHeadwayInterval

xsd:duration

1: 1

Planned departure interval

MinimumHeadwayInterval

xsd:duration

0: 1

Minimum departure interval

MaximumHeadwayInterval

xsd:duration

0: 1

Maximum departure interval

Description

MultilingualString  

0: 1

Description, for example, "every 15 minutes"

...

Info

Waiting time at TimingPoint for a VehicleJourney.

See definition under General information

VehicleJourneyWaitTime < JourneyWaitTime < JourneyTiming < VersionedChild  < EntityInVersion  < Entity 

Name

Type

Cardinality

Description

VehicleJourneyRef

VehicleJourneyRef

0: 1

Reference to VehicleJourney

...

Info

Run time between TimingPoints for a VehicleJourney.

See definition under General information

VehicleJourneyRunTime < JourneyRuntime < JourneyTiming  < VersionedChild  < EntityInVersion  < Entity 

Name

Type

Cardinality

Description

VehicleJourneyRef

VehicleJourneyRef

0: 1

Reference to VehicleJourney

...

Info

The interval between two VehicleJourneys.

Used for frequency-based traffic.

See definition under General information

VehicleJourneyHeadway < JourneyHeadway < JourneyTiming  < VersionedChild  < EntityInVersion  < Entity 

Name

Type

Cardinality

Description

VehicleJourneyRef

VehicleJourneyRef

0: 1

Reference to VehicleJourney

...

ALTERNATIVE 1: Ordinary timetable for planned journeys

TimetabledPassingTime < PassingTime < VersionedChild  < EntityInVersion  < Entity 

Name

Type

Cardinality

Description

attr

id

ObjectIdType

1: 1

Unique id for the object

Mandatory attribute

attr

version

VersionIdType

1: 1

Version number

Mandatory attribute

elem

PointInJourneyPatternRef

PointInJourneyPatternRef

1: 1

Reference to PointInJourneyPattern (the point being served/passed by the vehicle)

elem (choice)

ArrivalTime

ArrivalDayOffset

xsd:time

DayOffsetType (xsd:integer)

1: 1

0: 1

Planned arrival time (if relevant, both ArrivalTime and DepartureTime may be specified)

ArrivalOffset relative to the OperatingDay / Date for the affected VehicleJourney(s), e.g. "-1" (previous day) or "1" (next day)

DepartureTime

DepartureDayOffset

xsd:time

DayOffsetType (xsd:integer)

1: 1

0: 1

Planned departure time (if relevant, both ArrivalTime and DepartureTime may be specified)

DepartureOffset relative to the OperatingDay / Date for the affected VehicleJourney(s), e.g. "-1" (previous day) or "1" (next day)

elem

WaitingTime

xsd:duration

0: 1

Planned waiting time at a Point

ALTERNATIVE 2: On demand transport/FlexibleLines including hail and ride

TimetabledPassingTime < PassingTime < VersionedChild  < EntityInVersion  < Entity 

Name

Type

Cardinality

Description

attr

id

ObjectIdType

1: 1

Unique id for the object

Mandatory attribute

attr

version

VersionIdType

1: 1

Version number

Mandatory attribute

elem

PointInJourneyPatternRef

PointInJourneyPatternRef

1: 1

Reference to PointInJourneyPattern (the point being served/passed by the vehicle)

elem

WaitingTime

xsd:duration

0: 1

Planned waiting time at a Point

elem

LatestArrivalTime

xsd:time

1: 1

Latest possible (planned) arrival time (if relevant, both LatestArrivalTime and EarliestDepartureTime may be specified)

elem

LatestArrivalDayOffset

DayOffsetType (xsd:integer)

0: 1

Number of days of arrival relative to the journey start day (only used when journey spans more than one calendar day)

ArrivalOffset relative to the OperatingDay/Date for the affected VehicleJourney(s), e.g. "-1" (previous day) or "1" (next day)

elem

EarliestDepartureTime

xsd:time

1: 1

Earliest possible departure time (if relevant, both LatestArrivalTime and EarliestDepartureTime may be specified)

elem

EarliestDepartureDayOffset

DayOffsetType (xsd:integer)

0: 1

Number of days of arrival relative to the journey start day (only used when journey spans more than one calendar day)

DepartureOffset relative to the OperatingDay/Date for the affected VehicleJourney(s), e.g. "-1" (previous day) or "1" (next day)

...

Info

VehicleJourney with passengers. This is usually an ordinary departure according to the planned time table.

See definition under General information

Defined in TimetableFrame

Examples in the GitHub-repository

ServiceJourney < VehicleJourney  < Journey < LinkSequence < DataManagedObject 

Name

Type

Cardinality

Description

ServiceAlteration

ServiceAlterationEnumeration

0: 1

Journey type:

  • extraJourney

  • cancellation

  • planned

  • replaced (by another new ServiceJourneys)

DepartureTime

xsd:time

0: 1

Departure time

Frequency 

Frequency

0: 1

Frequency or interval for departures.

Used only for frequency-based departures.

JourneyDuration

xsd:duration

0: 1

Duration of the journey

dayTypes

DayTypeRef

1: *

References to DayTypes

JourneyPatternRef

JourneyPatternRef

1: 1

Reference to JourneyPattern

JourneyFrequencyGroupRef

JourneyFrequencyGroupRef

0: 1

Reference to JourneyFrequencyGroup

VehicleTypeRef

VehicleTypeRef

0: 1

Reference to VehicleType

OperatorRef

OperatorRef

0: 1

Reference to Operator

trainNumbers

TrainNumberRef

0: *

References to TrainNumber

passingTimes

TimetabledPassingTime

1: *

Planned passing times

parts

JourneyPart

0: *

List of parts of the journey (used in special cases, such as combined journeys)

To make re-use of journey parts possible, these must be defined separately (as independent objects, referred to from here).

checkConstraints

CheckConstraint

0: *

Information about security checks, barriers etc. which may cause delays.

TrainSize

TrainSize

0: 1

Information about the size and structure of a train

FlexibleServiceProperties

FlexibleServiceProperties

0: 1

Properties for flexible (on demand) transport.

It is possible to define properties here if they deviate from the flexible service properties set at the Line-level.

...

FlexibleServiceProperties < DataManagedObject

Name

Type

Cardinality

Description

FlexibleServiceType

FlexibleServiceTypeEnumeration

0: 1

Type of flexible transport:

  • dynamicPassingTimes

  • fixedHeadwayFrequency

  • fixedPassingTimes

  • notFlexible

CancellationPossible

xsd:boolean

0: 1

Specifies whether a service may be cancelled by the operator

ChangeOfTimePossible

xsd:boolean

0: 1

Specifies whether times may be changed by the operator

BookingContact

ContactStructure

0: 1

Contact information to book the on-demand service

BookingMethods

BookingMethodListOfEnumerations

0: 1

Possible methods for booking the on-demand service:

  • callDriver

  • callOffice

  • online

  • phoneAtStop

  • text (text message/SMS)

  • other

BookingAccess

BookingAccessEnumeration

0: 1

Who may place an order (book the on-demand service):

  • public

  • authorisedPublic (e.g. TT-transport - special services for mobility restricted travelers)

  • staff

BookWhen

PurchaseWhenEnumeration

0: 1

Time constraints for booking:

  • timeOfTravelOnly

  • dayOfTravelOnly (requires LatestBookingTime to be set)

  • untilPreviousDay (requires LatestBookingTime to be set)

  • advanceAndDayOfTravel (requires LatestBookingTime to be set)

It is recommended to set this field if MinimumBookingPeriod is not specified

BuyWhen

PurchaseMomentListOfEnumerations

0: 1

Time constraints for payment:

  • onReservation

  • beforeBoarding

  • afterBoarding

  • onCheckOut

LatestBookingTime

xsd:time

0: 1

Latest possible time for booking

Do not set if BookWhen is undefined or defined as “timeOfTravelOnly” (would be invalid)

MinimumBookingPeriod

xsd:duration

0: 1

The minimum time ahead of journey departure the booking must be completed

Can only be set (optionally) if BookWhen is undefined

BookingNote

xsd:normalizedString

0: 1

Additional information about the booking

...

Info

VehicleJourney without passengers.

See definition under General information

Defined in TimetableFrame

DeadRun VehicleJourney < Journey < LinkSequence < DataManagedObject

Name

Type

Cardinality

Description

Frequency 

Frequency

0: 1

Frequency/interval for departures

Used only for frequency-based departures.

dayTypes

DayTypeRef

1: *

References to DayTypes

JourneyPatternRef

JourneyPatternRef

1: 1

References to JourneyPattern

Note, that for JourneyPatterns used exclusively by DeadRuns, it is permitted to define ScheduledStopPoints which are not linked to a Place (i.e. StopAssignment is not defined), when these ScheduledStopPoints do not exist in the stop place registry (e.g. vehicle garages, workshops, rest areas)

JourneyFrequencyGroupRef

JourneyFrequencyGroupRef

0: 1

Reference to JourneyFrequencyGroup

VehicleTypeRef

VehicleTypeRef

0: 1

Reference to VehicleType

passingTimes

TimetabledPassingTime

0: *

Planned passing times

OperatorRef

OperatorRef

0: 1

Reference to Operator

DeadRunType

DeadRunTypeEnumeration

0: 1

Classification of DeadRun (if relevant):

  • garageRunOut

  • garageRunIn

...

Info

Template to describe recurring ServiceJourney, used together with HeadwayJourneyGroup (to describe frequency-based departures) or with RhythmicalJourneyGroup (to describe departures at the same time of day in a set period).

See definition under General information

Defined in TimetableFrame

TemplateServiceJourney < TemplateVehicleJourney < ServiceJourney < Journey  < LinkSequence < DataManagedObject 

Name

Type

Cardinality

Description

frequencyGroups

(choice) RhytmicalJourneyGroup

(choice) HeadwayJourneyGroup

(choice) RhytmicalJourneyGroupRef

(choice) HeadwayJourneyGroupRef

1: *

RhythmicalJourneyGroup or HeadwayJourneyGroup, or reference to a template which applies to this pattern.

...

Info

Template to describe recurring ServiceJourney, used either with HeadwayJourneyGroup (to describe frequency-based departures) or with RhytmicalJourneyGroup (to describe departures at the same time of day in a set period).

See definition under General information

Defined in TimetableFrame

Examples in the GitHub-repository 

TemplateServiceJourney < TemplateVehicleJourney < ServiceJourney < Journey  < LinkSequence < DataManagedObject 

Name

Type

Cardinality

Description

TemplateServiceJourney inherits from TemplateVehicleJourney and does not introduce new elements or attributes.

...

Info

Abstract type which describes recurring (for example: "departures at xx05, xx15, xx25, xx35, xx45, xx55") or frequency based departures ("departures with X minutes spacing").

See definition under General information

JourneyFrequencyGroup < GroupOfEntities < DataManagedObject 

Name

Type

Cardinality

Description

FirstDepartureTime

xsd:time

1: 1

Departure time for the first stop in the first departure in the frequency group.

LastDepartureTime

xsd:time

1: 1

Departure time for the first stop in the last departure in the frequency group.

DayOffset

xsd:integer

0: 1

Number of days from the starting point (when service period spans more than one calendar day)

Offset is relative to the OperatingDay / Date for the affected VehicleJourney(s), e.g. "-1" (previous day) or "1" (next day)

journeys

VehicleJourneyRef

0: *

List of journeys in a JourneyFrequencyGroup.

Lists only ServiceJourneyRef objects.

...

Info

Description of service where departure(s) start at the same time (minutes over a whole hour) in a set period.

See definition under General information

Defined in TimetableFrame

Examples in the GitHub-repository 

RhythmicalJourneyGroup < JourneyFrequencyGroup < GroupOfEntities   < DataManagedObject 

Name

Type

Cardinality

Description

timebands

TimebandRef

1: *

Reference to a Timeband-object which describes the departure time for ServiceJourney as minutes over a full hour.

In the context of RhythmicalJourneyGroup, Timeband must have identical StartTime and EndTime and show the departure time as minutes over a full hour. Use "00:..." for generic time representation.

...

Info

Description of service which has the same time interval between departures (frequency-based departures).

See definition under General information

Defined in TimetableFrame

HeadwayJourneyGroup < JourneyFrequencyGroup < GroupOfEntities   < DataManagedObject 

Name

Type

Cardinality

Description

ScheduledHeadwayInterval

xsd:duration

1: 1

The planned interval between departures

MinimumHeadwayInterval

xsd:duration

0: 1

The minimum interval between departures

MaximumHeadwayInterval

xsd:duration

0: 1

The maximum interval between departures

Description

MultilingualString

0: 1

Description (for example: "every 15 minutes")

...

Info

A combined/coupled journey comprised of different VehicleJourneys, where the operating vehicle is a combination of two or more single vehicles (normally used for linking trains).

See definition under General information

Defined in TimetableFrame

CoupledJourney < DataManagedObject 

Name

Type

Cardinality

Description

Description

MultilingualString

0: 1

Description

journeys

VehicleJourneyRef

0: *

List of VehicleJourneys in the coupled journey.

...

Info

Two or more JourneyParts from different VehicleJourneys which are served simultaneously (i.e. operating together / coupled) (normally used for linking trains). As such it represents a “joined” train that has two SERVICE JOURNEYs coupled together for a section of their journey.

See definition under General information

Defined in TimetableFrame

JourneyPartCouple < DataManagedObject 

Name

Type

Cardinality

Description

Description

MultilingualString

0: 1

Description of journey part coupling

StartTime

xsd:time

1: 1

Starting time for the coupled journey part(s)

EndTime

xsd:time

1: 1

End time for the coupled journey part(s)

FromStopPointRef

ScheduledStopPointRef

1: 1

Planned first stop for the journey part coupling (ScheduledStopPoint)

ToStopPointRef

ScheduledStopPointRef

1: 1

Planned last stop for the journey part coupling (ScheduledStopPoint)

MainPartRef

JourneyPartRef

1: 1

The main part of the coupled journey (relevant for travel information to the public)

journeyParts

JourneyPartRef

0: 1

Remaining parts of a coupled journey (excl. MainPartRef)

TrainNumberRef

TrainNumberRef

0: 1

Reference to TrainNumber for the coupled journey part(s)

...

Info

A logical container for a grouping of calendar-related elements with identical validity criteria, and/or identical start-end dates.

Please note that unlinked calendar objects with validity criteria identical to the current ServiceCalendarFrame should be added directly below it, rather than unnecessarily grouping it in a ServiceCalendar.

See definition under General information

Defined in ServiceCalendarFrame

Examples in the GitHub-repository.

ServiceCalendar < DataManagedObject 

Name

Type

Cardinality

Description

Name

MultilingualString

0: 1

Name of calendar

FromDate

xsd:date

1: 1

Calendar start date

ToDate

xsd:date

1: 1

Calendar end date

EarliestTime

xsd:time

0: 1

Start time for the day can be defined in cases where it differs from the normal 00:00:00.

DayLength

xsd:duration

0: 1

Length of the day can be defined in cases where it differs from the normal 24 hours.

dayTypes

DayType

0: *

DayTypes used in a calendar

May be defined directly in ServiceCalendarFrame

timebands

Timeband

0: *

Timebands used in a calendar

May be defined directly in ServiceCalendarFrame

operatingDays

OperatingDay

0: *

OperatingDays used in a calendar

May be defined directly in ServiceCalendarFrame

operatingPeriods

OperatingPeriod

0: *

OperatingPeriods used in a calendar

May be defined directly in ServiceCalendarFrame

dayTypeAssignments

DayTypeAssignment

0: *

Linking of DayTypes to OperatingDays

May be defined directly in ServiceCalendarFrame

...

Info

An abstract type which describes planned possibilities for passengers to transfer betweenServiceJourneys on the same or (usually) nearby stops, with a description of when/if a vehicle will wait for another arriving vehicle.

See definition under General information

Interchange < DataManagedObject 

Name

Type

Cardinality

Description

Priority

xsd:integer

0: 1

Weighted prioritization of transfers, e.g. when there are multiple possible interchange locations along a journey, or when there is a need to mark a location as inappropriate for interchanges:

  • -1 (interchanges not allowed. Corresponds to: noInterchange)

  • 0 (null, standard interchange value. Corresponds to: interchangeAllowed

  • 1 (recommended interchange, to be weighted high by journey planners. [timed according to stated MaximumWaitTime]. Corresponds to: recommendedInterchange)

  • 2 (preferred interchange, to be weighted with maximum preference by journey planners. Corresponds to: preferredInterchange) (value recommended to be deprecated)

Corresponds to Weighting (InterchangeWeightingEnumeration) for StopPlace

StaySeated

xsd:boolean

0: 1

Specifies that the traveller can remain seated in the vehicle, as it will be re-used for the next part of the journey.

Useful when describing Lines that operate in a circular pattern (prevents fictitious interchanges), and also implies that the interchange is de facto guaranteed (i.e. does not require Guaranteed = “true” to be set).

Guaranteed

xsd:boolean

0: 1

Specifies whether the interchange is guaranteed (the passenger is guaranteed the transfer between the two journeys).

MaximumWaitTime

xsd:duration

0: 1

Maximum time (after normal departure time) the connecting transport allows for delays.

If this value is not set for an Interchange with Guaranteed ‘true’, it should be assumed that the consumer service will wait for the feeder service regardless of delay.

...

ServiceJourneyInterchange < Interchange < DataManagedObject 

Name

Type

Cardinality

Description

FromPointRef

ScheduledStopPointRef

1: 1

Reference to stop where passenger begins transfer/interchange (arriving vehicle location)

Stop point for the interchange feeder journey

ToPointRef

ScheduledStopPointRef

1: 1

Reference to stop where passenger continues the journey from (departing vehicle location)

Stop point for the interchange consumer/distributor journey

FromJourneyRef

VehicleJourneyRef

1: 1

Reference to the journey the passenger transfers from (VehicleJourney)

Interchange feeder journey

ToJourneyRef

VehicleJourneyRef

1: 1

Reference to the journey the passenger transfers to (VehicleJourney)

Interchange consumer/distributor journey

...