All datasets should be XML files with the root node "PublicationDelivery
" (see description of the exchange format), which is the message format defined in NeTEx to contain relevant components.
The following examples are simplified snippets of semi-fictitious data to illustrate how the components and their contents should be modelled.
Entur has an official repository at GitHub, which contains XML-files for all our examples below: https://github.com/entur/profile-examples/tree/master/netex
The catalogue is intended to cover the most common use cases, but we welcome any ideas for creating additional examples.
Skeleton (can be used as a template for datasets)
Complete delivery (contains all relevant elements for datasets)
All the various example categories are described on individual pages with a detailed description of file structure and data content, as well as links to the corresponding XML file on GitHub.
Sample | Profile | XML | Description | Comments |
---|---|---|---|---|
network/timetable | Line 61A, Oslo: | See TimetableFrame (the file contains a full dataset for network and service) | ||
network/timetable | Line 109, Oslo: | See TimetableFrame (the file also contains geographical projections and a full dataset for Network, Service and Timetable.) | ||
network/timetable | Line 109, Oslo: | |||
network/timetable | 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 |
| Linje 316 contains examples of Interchange | |
network/timetable | 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 | Projection (for Line 109, Oslo): | See serviceLinks in ServiceFrame (the file contains a full dataset for network and service.) | |
Calendar (ServiceCalendar with dayTypes) | network/timetable | Theoretical example showing how to use different calendar types. | ||
network/timetable | Show custom company information (overriding Authority/Operator). | Also, see Authorities (below) | ||
network/timetable | 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. | ||
Blystadlia, Rælingen. | ||||
"Bryn skole": | ||||
Complex stop area (multiple transport types) | Oslo S - Jernbanetorget: | Contains deviations from actual implementation in live solutions. The examples here will be adjusted when a revised implementation is ready for publication. | ||
network/timetable | Specification of TariffZone per Line and/or departure. |
fares examples will be added at a later time. |
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.
Create a fork (your local copy) of the catalogue.
Create a branch (your local branch of the code) and make your changes to the code there.
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.)
Make a pull request into the repository to "save" the changes.
Further information about the use of pull request in GitHub is located at https://help.github.com/articles/using-pull-requests/.
It is recommended to use tools which support automatic validation of the data structure while working with XML files, eg. Notepad++ with XML Tools plugin (free, the XML-plugin could be installed automatically in Notepad++ or downloaded separate) or licensed tools like Oxygen or XMLspy.