Organisation responsible (for example owner) for the network.

An explicit listing of lines included in the group (if appropriate)

Note that reference should link from Line up to Network through a RepresentedByGroupRef

The transport mode of the group.

See Transport Modes for possible values

See Mode in Transport Modes for valid values

See Submodes in Transport Modes for valid values (must be a TransportSubmode belonging to the selected TransportMode)

The publicly advertised line number, or code of the line.

Usually a number, or a number combined with a letter (eg L2, 31, 30E etc.).

The Name field normally contains more information than the PublicCode, and is often the combination of PublicCode + Name.

Reference (ID) to a related Line (for example, the regular line for which this is a replacement).

1: 1

Reference to the main operator (may be omitted in exceptional cases, such as a different operator for every departure).

Reference to additional operators of the line

Reference to the line type. Classification, (e.g. replacement line)

Specifies whether real-time information normally is available for this line (set to true when real-time data exists for the line).

Reference to a listing of all routes (Route) which are part of the line.

The references can normally be deduced from Line references in Routes. Therefore this field is only relevant in exceptional cases).

RepresentedByGroupRef

Graphical representation information (colour, text, etc.)

Six digit hexadecimal representation of the lines' RGB colour values.

Six digit hexadecimal representation of the lines' RGB colour values.

Font identifier (font). Normally not specified.

The direction of the route:

• inbound (towards the city centre or transport hub)
• outbound (from the city centre or transport hub) 
• clockwise (circular route in the clockwise direction)
• anticlockwise (circular route in the anticlockwise direction)

To be able to identify full- or partial circular routes clockwise/anticlockwise must be specified.

Specifies whether the point is on the border between two countries.

Type of TimingPoint:

• timingPoint
• notTimingPoint (may indicate the expected passing time)

Reference to LinkSequence to which the point belongs.

RouteRef should be used, since Route inherits from LinkSequence.

Note that the field should not be used if PointOnRoute is defined inline in Route.

Projection on a point (RoutePoint, TimingPoint, SchedueledStopPoint) or a GML-coordinate projection .

Reference to Point

RoutePointRef should be used to point to the corresponding RoutePoint.

Distance in meters for ServiceLink, i.e. driving distance between FromPoint and ToPoint.

ScheduledStopPointRef

Reference to StopPlace which is related to ScheduledStopPoint

Should be included as far as possible, but the StopPlace can also be derived from the referenced Quay (QuayRef) when the StopPlaceRef is missing

References to a detailed position on platform (TrainStopAssignment)

Used only for trains

The "order" attribute is inherited from the more generic type Assignment, but in the case of a PassengerStopAssignment its business meaning is undefined. It is however mandatory due to an XML schema validation constraint.
Examples of valid implementations:

• an incremented sequence number ("1", "2", "3", ...)
• a constant value ("0")

Reference to a FlexibleQuay.

Can be added in a supplementary role if a FlexibleQuay is used.

Reference to an actual FlexibleArea

Can be added in a supplementary role if a FlexibleArea is defined for the FlexibleStopPlace.

Reference to an actual HailAndRideArea

Can be added in a supplementary role if a HailAndRideArea is defined for the FlexibleStopPlace.

Internal (non-public) identifier for the JourneyPattern.

Description of RunTimes for the JourneyPattern.

Only used when describing frequency-based departures.

Description of WaitTime for JourneyPattern

Normally used only when describing frequency-based departures.

Description of JourneyHeadway for JourneyPattern

Only used when describing frequency-based departures.

Specifies whether alighting is allowed.

Should be explicitly indicated (normally "false") for the first StopPointInJourneyPattern

Specifies whether boarding is allowed.

Should be explicitly indicated (normally "false") for last StopPointInJourneyPattern

Reference to DestinationDisplay

The required minimum for linear routes is for the first StopPointInJourneyPattern to have a DestinationDisplayRef. For circular routes, the minimum is two.

A new DestinationDisplayRef should be set at any StopPointInJourneyPattern along the route where it is relevant to update the destination text. This is particularly relevant for circular routes.

Possible values for hailing or arranging a stop:

• handSignal
• phoneCall
• sms
• stopButton
• turnOnLight

Rules for booking.

Please note that BookingArrangements specified at the StopPointInJourneyPattern level will always override equivalent specifications at the Line- or ServiceJourney level.

Contact information for booking

Note that the field is mandatory if this is not already on FlexibleLine or overridden in FlexibleServiceProperties

Possible ways to book (must match info found in BookingContact):

• callDriver
• callOffice
• online
• phoneAtStop
• text (text message/SMS)

Note that the field is mandatory if this is not already on FlexibleLine or overridden in FlexibleServiceProperties

Who may place an order (book):

• public
• authorisedPublic (eg TT-transport - special services for mobility restricted travellers )
• staff

Time constraints for booking:

• timeOfTravelOnly
• dayOfTravelOnly
• untilPreviousDay
• advanceAndDayOfTravel

Note that the field is mandatory if this is not already on FlexibleLine or overridden in FlexibleServiceProperties

Time constraints for payment:

• onReservation
• beforeBoarding
• afterBoarding
• onCheckOut

The minimum period prior to the departure the booking has to be placed.

The text displayed on the side of the vehicle body

The text displayed on the front of the vehicle, commonly above the front window.

An intermediary destination which the vehicle will pass before reaching its final destination.

Eg. Oslo tram line 11: "Majorstuen - Kjelsås via Torshov"

Variations of DestinationDisplay adapted for particular media types

Note that for composite DestinationDisplay text, e.g. line number and destination name. The minimum requirement is to provide a DestinationDisplay for web sites, with a destination name.

Supported media types:

• Printed
• TextToSpeech
• Web
• Mobile
• other (e.g. real-time display)

Front page text for DestinationDisplay

Reference to the DestinationDisplay object describing the stop place/area the vehicle is headed towards.

Possible values:

• stopPoint
• name

Flexible line types:

• corridorService
• mainRouteWithFlexibleEnds
• flexibleAreasOnly
• hailAndRideSections
• fixedStopAreaWide
• mixedFlexible
• mixedFlexibleAndFixed
• fixed

Contact information for booking.

0: 1

Possible booking methods:

• callDriver
• callOffice
• online
• phoneAtStop
• text (text message/SMS)

Who may place an order (book):

• public
• authorisedPublic
• staff

Time constraints for booking:

• timeOfTravelOnly
• dayOfTravelOnly
• untilPreviousDay
• advanceAndDayOfTravel

Time constraints for payment:

• onReservation
• beforeBoarding
• afterBoarding
• onCheckOut

The minimum period prior to the departure the booking has to be placed.

Detailed description for duration transfer

The time it will take a person with local knowledge to complete the transfer (commuter)

The time it will take a person unfamiliar with the place to complete the transfer (tourist etc.)

The time it will take a person with special needs to complete the transfer