Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Message Format

...

Sample

Profile

XML

Description

Comments

Simple route - Bus with rhythm-based departures

network/timetable

GitHub

Line 61A, Oslo:
Circular feeder route at Tveita. Operates every day except Sunday. 

See TimetableFrame (the file contains a full dataset for network and service)

Simple route - Bus with explicit ServiceJourney(s)

network/timetable

GitHub

Line 109, Oslo:
Morning bus route with three departures (times differ between weekdays, Saturdays and Sundays).

See TimetableFrame (the file also contains geographical projections and a full dataset for Network, Service and Timetable.) 

Simple route - Bus

network/timetable

GitHub

Line 109, Oslo:
Morning bus route between Helsfyr T and Holtet. Operates every day except Sunday. 


Simple route - Bus with pre-booked stops

network/timetable

GitHub

Express bus Sørlandsekspressen. Some stops are on-demand only: passengers must book in advance for the bus to stop.


On-demand transport (FlexibleLines)

network/timetable

  1. GitHub

  2. GitHub

  3. GitHub

  1. Line 316, Lørenskog: On-demand transport on weekdays.

  2. On-demand transport without a predefined journey pattern within a defined area.

  3. Line 507, Drøbak: A scheduled route which allows alighting and boarding outside the fixed stop places along segments of a journey (Hail & Ride).

Linje 316 contains examples of Interchange

Multimodal interchange

network/timetable

GitHub

On-demand transport line which links up with train- and bus lines at a specific stop.

Modelled as on-demand transport with planned interchanges for train and bus. 

Projection (geographical positions)

network/timetable

GitHub

Projection (for Line 109, Oslo):
Specification of journey pattern through positional data

See serviceLinks in ServiceFrame (the file contains a full dataset for network and service.)

Calendar (ServiceCalendar with dayTypes)

network/timetable

GitHub

Theoretical example showing how to use different calendar types.


Branding

network/timetable

GitHub

Show custom company information (overriding Authority/Operator).

Also, see Authorities (below)

Authorities

network/timetable

GitHub

Description of multiple Authorities in the same data set.

Used when submitting data for a service provider different from your own (on behalf of), also see Branding. 

Stop place with a minimum of required information

stops

GitHub

Blystadlia, Rælingen.
Monomodal stop place for bus with one Quay.


Normal stop place for bus

stops

GitHub

"Bryn skole":
Monomodal stop place for bus with one Quay in each direction.


Complex stop area  (multiple transport types)

stops

GitHub

Oslo S - Jernbanetorget:
Stop place area which with several multi- and monomodal stop places.

Contains deviations from actual implementation in live solutions. The examples here will be adjusted when a revised implementation is ready for publication.

Tariff code

network/timetable

GitHub

Specification of TariffZone per Line and/or departure.


...

If you want to expand the samples or add new ones in GitHub, eg. the need for modelling special cases not already covered follow these guidelines. 

  1. Create a fork (your local copy) of the catalogue.

  2. Create a branch (your local branch of the code) and make your changes to the code there.

  3. Test all changes/new files.
    (XML-documents must validate against the NeTEx official Schema, see https://github.com/NeTEx-CEN/NeTEx for the last version of XSD's.)

  4. Make a pull request into the repository to "save" the changes.

...