SIST-TP CEN/TR 16959:2016
(Main)Public transport - Network and Timetable Exchange (NeTEx) - Examples, guidelines and explanatory materials
Public transport - Network and Timetable Exchange (NeTEx) - Examples, guidelines and explanatory materials
This Technical Report provides a set of examples, white papers and explanatory material that makes it easy to understand how to use and deploy all parts of NeTEx. This will help EPTIS system providers and acquirers, providing functional scope, guidelines and terminology explanations needed to implement a system. It will also ease formalizing the requirements for the context of a procurement process.
Öffentlicher Verkehr - Netzwerk- und Fahrplan Austausch (NeTEx) - Beispiele, Vorgaben und erläuterndes Material
Transport Public - Échange des données de réseau et d'horaires (NeTEx)
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - Primeri, smernice in pojasnjevalno gradivo
To tehnično poročilo navaja primere, uradne dokumente in pojasnjevalno gradivo za lažje razumevanje uporabe in izvedbe vseh delov NeTEx. To bo v pomoč ponudnikom in odjemalcem sistema EPTIS, saj zagotavlja funkcionalni obseg, smernice in terminološka pojasnila, ki so potrebni za uvedbo sistema. S tem bo enostavnejša tudi formalizacija zahtev za postopke javnih naročil.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST-TP CEN/TR 16959:2016
01-september-2016
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - Primeri,
smernice in pojasnjevalno gradivo
Public transport - Network and Timetable Exchange (NeTEx) - Examples, guidelines and
explanatory materials
Öffentlicher Verkehr - Netzwerk- und Fahrplan Austausch (NeTEx) - Beispiele, Vorgaben
und erläuterndes Material
Transport Public - Échange des données de réseau et d'horaires (NeTEx)
Ta slovenski standard je istoveten z: CEN/TR 16959:2016
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST-TP CEN/TR 16959:2016 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST-TP CEN/TR 16959:2016
---------------------- Page: 2 ----------------------
SIST-TP CEN/TR 16959:2016
CEN/TR 16959
TECHNICAL REPORT
RAPPORT TECHNIQUE
May 2016
TECHNISCHER BERICHT
ICS 35.240.60
English Version
Public transport - Network and Timetable Exchange
(NeTEx) - Examples, guidelines and explanatory materials
Transport Public - Échange des données de réseau et Öffentlicher Verkehr - Netzwerk- und Fahrplan
d'horaires (NeTEx) Austausch (NeTEx) - Beispiele, Vorgaben und
erläuterndes Material
This Technical Report was approved by CEN on 4 April 2016. It has been drawn up by the Technical Committee CEN/TC 278.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2016 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TR 16959:2016 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TP CEN/TR 16959:2016
CEN/TR 16959:2016 (E)
Contents Page
European foreword . 6
Introduction . 7
1 Scope . 13
2 Frequently Asked Questions (FAQ) . 13
2.1 Introduction . 13
2.2 Basic Commercial questions . 13
2.2.1 Do I have to pay for using NeTEx? . 13
2.2.2 What skills do I need to deploy NeTEx? . 13
2.2.3 What tools are available to support NeTEx? . 13
2.2.4 How do I get new features added to NeTEx?. 14
2.2.5 What is a profile? . 14
2.2.6 What if I find a bug in NeTEx? . 14
2.2.7 How do I get support for my NeTEx development? . 14
2.3 Basic scope questions . 15
2.3.1 Is NeTEx a GIS standard? . 15
2.3.2 Is NeTEx a database? . 15
2.3.3 Is NeTEx for real-time applications? . 15
2.3.4 Can I use NeTEx for Rail? . 15
2.3.5 Does NeTEx provide web services?. 15
2.3.6 Does NeTEx cover ticket sales? . 16
2.3.7 Can I use NeTEx for mobile applications? . 16
2.4 Pros and Cons questions . 16
2.4.1 What are the advantages of using NeTEx?. 16
2.4.2 How can NeTEx reduce development costs? . 16
2.4.3 How can NeTEx increase capability and improve design quality? . 17
2.4.4 How can NeTEx simplify my software application development?. 17
2.4.5 How can NeTEx protect my investment? . 17
2.4.6 What are the disadvantages of using NeTEx?. 18
2.4.7 Is NeTEx hard to understand? . 18
2.4.8 Does increased generality make NeTEx is harder to work with? . 18
2.4.9 Does NeTEx require more computing resources that other standards? . 18
2.4.10 Are there missing validity checks in NeTEx ? . 19
2.4.11 Is it quick to add new features in NeTEx? . 19
2.5 Further Specific questions of Scope . 19
2.5.1 Can NeTEx describe journey connection times? . 19
2.5.2 Does NeTEx support accessibility? . 19
2.5.3 Can NeTEx handle frequency based services? . 19
2.5.4 Can I have different journey timings for different times of day? . 20
2.5.5 Can NeTEx describe zone based fares? . 20
2.5.6 Can I restrict certain products to certain classes of user? . 20
2.5.7 Can I specify time based constraints on travel? . 20
2.5.8 Can I integrate data from different countries with NeTEx? . 20
2.5.9 Does NeTEx support dynamic/ yield managed pricing? . 20
2.5.10 Can NeTEx define products for modern e-card based ticketing? . 21
2.5.11 Does NeTEx support Flexible and Demand Responsive Travel? . 21
2.5.12 Can I create applications to run in different national Languages? . 21
2
---------------------- Page: 4 ----------------------
SIST-TP CEN/TR 16959:2016
CEN/TR 16959:2016 (E)
2.5.13 Can I have different version of data for the same element extant at the same time? . 21
2.5.14 Can I create Network maps with NeTEx? . 21
2.5.15 I have my own classification for Stops/ Lines / etc. Can NeTEx handle this? . 22
2.6 Comparison with other documents . 22
2.6.1 How does NeTEx relate to Transmodel?. 22
2.6.2 How does NeTEx relate to IFOPT?. 22
2.6.3 How does NeTEx compare with VDV? . 22
2.6.4 How does NeTEx compare with TransXChange? . 22
2.6.5 How does NeTEx compare with NEPTUNE? . 23
2.6.6 How does NeTEx compare with NOPTIS? . 23
2.6.7 How does NeTEx compare with IFM? . 23
2.6.8 How does NeTEx compare with BISON ? . 23
2.6.9 How does NeTEx compare with the Taap/TSI standards? . 24
2.6.10 How does NeTEx compare with GTFS? . 24
3 NeTEx covered areas description . 25
3.1 Introduction. 25
3.2 General areas . 25
3.3 Specific functional areas . 25
Annex A (informative) Getting Started . 26
A.1 Introduction. 26
A.2 Three common use cases . 26
A.3 Basic Steps . 27
A.4 Implementing a NeTEx System . 29
A.5 Resources . 31
A.6 NeTEx CEN Technical specifications, . 31
A.7 NeTEx UML Models . 31
A.8 NeTEx XML Schema . 32
A.9 NeTEx WSDL Bindings . 32
A.10 Tools and Technology . 32
Annex B (informative) Design Methodology . 33
B.1 Introduction. 33
B.2 Model driven design . 33
B.3 Consistent Terminology . 34
B.4 UML Notation . 35
B.5 XML schema . 35
B.6 Tools and Technology . 37
B.7 Modularisation of the framework . 37
Annex C (informative) Framework. 39
C.1 Introduction. 39
C.2 The NeTEx Frameworks . 39
C.3 NeTEx framework features . 40
3
---------------------- Page: 5 ----------------------
SIST-TP CEN/TR 16959:2016
CEN/TR 16959:2016 (E)
Annex D (informative) Reusable Components . 45
D.1 Introduction . 45
D.2 The NeTEx Reusable Components . 45
D.3 Summary of Reusable Components . 45
D.4 Summary of Reusable Data types . 47
Annex E (informative) Representing Public Transport Networks in NeTEx . 48
E.1 Introduction . 48
E.2 NeTEx Methodology . 48
E.3 Scope . 48
E.4 Corresponding NeTEx documentation . 48
E.5 Approach . 49
E.6 Basic spatial network aspects. 51
Annex F (informative) Representing Flexible Networks and Multimodality in NeTEx . 56
F.1 Introduction . 56
F.2 Scope . 56
F.3 Corresponding NeTEx documentation . 56
F.4 NeTEx Methodology . 57
F.5 Flexible networks . 57
F.6 Multimodality . 60
Annex G (informative) Support for Accessibility in NeTEx . 63
G.1 Introduction . 63
G.2 Scope . 63
G.3 Corresponding NeTEx documentation . 63
G.4 NeTEx Methodology . 64
G.5 Approach . 64
G.6 Accessibility of sites . 64
G.7 Accessibility and connections . 65
G.8 Accessibility of navigation paths . 66
G.9 Accessibility of journeys . 66
Annex H (informative) Representing Timetables in NeTEx . 67
H.1 Introduction . 67
H.2 Corresponding NeTEx documentation . 67
H.3 Approach to Timetables in NeTEx . 68
H.4 The representation of a timetable . 69
H.5 Example of a simple timetable in NeTEx . 71
Annex I (informative) Representing Fares in NeTEx . 74
4
---------------------- Page: 6 ----------------------
SIST-TP CEN/TR 16959:2016
CEN/TR 16959:2016 (E)
I.1 Introduction. 74
I.2 Scope . 74
I.3 Functional areas . 74
I.4 Provision of information on fares . 75
I.5 Approach . 77
I.6 Selecting a Fare . 81
Bibliography . 83
5
---------------------- Page: 7 ----------------------
SIST-TP CEN/TR 16959:2016
CEN/TR 16959:2016 (E)
European foreword
This document (CEN/TR 16959:2016) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent
rights.
6
---------------------- Page: 8 ----------------------
SIST-TP CEN/TR 16959:2016
CEN/TR 16959:2016 (E)
Introduction
0.1 General information
NeTEx is a series of CEN Technical Specifications dedicated to the exchange of Public Transport
scheduled data (network, timetable and fare information) based on:
— Transmodel V5.1 (see [T1], [T1] and [T3]);
— IFOPT (see [I1]);
— SIRI (see [S1], [S2], [S3], [S4], [S5]);
It supports information exchange of relevance to public transport services for passenger information
and AVMS (Automated Vehicle Monitoring Systems). Many NeTEx concepts are taken directly from
Transmodel and IFOPT; the definitions and explanation of these concepts are extracted directly from
the respective documents and reused in NeTEx, sometimes with further adaptions in order to fit the
NeTEx context.
The data exchanges targeted by NeTEx are predominantly oriented towards passenger information and
also for data exchange between transit scheduling systems and AVMS. However it is not restricted to
these purposes, and it can provide an effective solution to many other use cases for transport data
exchange
The NeTEx series of documents is divided into three parts, each covering a functional subset of the CEN
Transmodel for Public Transport Information:
— Part 1 describes the Public Transport Network topology (see [N1]);
— Part 2 describes Scheduled Timetables (see [N2]);
— Part 3 covers Fare information (see [N3]).
NeTEX is intended to be a general purpose XML format designed for the efficient, updateable exchange
of complex transport data among distributed systems. This allows the data to be used in modern web
services based architectures and to support a wide range of passenger information and operational
applications.
Most public transport modes are taken into account by NeTEx, including train, bus, coach, metro,
tramway, ferry, and their submodes. Moreover, it is possible to describe airports and air journeys, but
there has not been any specific consideration of any additional provisions that apply especially to air
transport.
While there are a number of existing documents available for Timetables, NeTEx is the first
systematically engineered document that also covers multimodal Fares.
0.2 Compatibility with existing standards and recommendations
The concepts covered in NeTEx that relate in particular to long-distance train travel include:
— rail operators and related organizations;
— stations and related equipment's;
— journey coupling and journey parts;
— train composition and facilities;
7
---------------------- Page: 9 ----------------------
SIST-TP CEN/TR 16959:2016
CEN/TR 16959:2016 (E)
— planned passing times;
— timetable versions and validity conditions.
In the case of long distance train, the NeTEx takes into account the requirements formulated by the ERA
(European Rail Agency) – TAP/TSI (Telematics Applications for Passenger/ Technical Specification for
Interoperability), entered into force on 13 May 2011 as the Commission Regulation (EU No 454/2011),
based on UIC directives.
As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK),
VDV 452 (Germany), NEPTUNE (France), UIC Leaflet, BISON (Netherland) and NOPTIS (Nordic Public
Transport Interface Standard).
The data exchange is possible either through dedicated web services, through data file exchanges, or
using the SIRI exchange protocol as described in Part 2 of the SIRI documentation (see [S2]).
This Technical report is to be used in conjunction with the following documents:
— EN 15531-1, Public transport - Service interface for real-time information relating to public
transport operations - Part 1: Context and framework (see [S1]);
— EN 15531-2, Public transport - Service interface for real-time information relating to public
transport operations - Part 2: Communications infrastructure (see [S2]);
— EN 15531-3, Public transport - Service interface for real-time information relating to public
transport operations - Part 3: Functional service interfaces (see [S3]);
— CEN/TS 15531-4, Public transport - Service interface for real-time information relating to public
transport operations - Part 4: Functional service interfaces: Facility Monitoring (see [S4]);
— CEN/TS 15531-5, Public transport - Service interface for real-time information relating to public
transport operations - Part 5: Functional service interfaces - Situation Exchange (see [S5]);
— EN 12896, Road transport and traffic telematics - Public transport - Reference data model (see
[T1]);
— EN 28701, Intelligent transport systems - Public transport - Identification of Fixed Objects in Public
Transport (see [I1]).
0.3 NeTEx exchanged information
NeTEx provides a means to exchange data for passenger information such as stops, routes timetables
and fares, among different computer systems, together with related operational data. It can be used to
collect and integrate date from many different stakeholders, and to reintegrate it as it evolves through
successive versions.
All three parts covered by NeTEx use the same framework of reusable components, versioning
mechanisms, validity conditions, global identification mechanisms, etc., defined in a NeTEx framework
in Part 1. NeTEx also includes, container elements called “version frames” to group data into coherent
sets for efficient exchange.
NeTEx schema can thus be used to exchange:
— public Transport schedules including stops, routes, departures times / frequencies, operational
notes, and map coordinates;
8
---------------------- Page: 10 ----------------------
SIST-TP CEN/TR 16959:2016
CEN/TR 16959:2016 (E)
— routes with complex topologies such as circular routes, cloverleaf and lollipops, and complex
workings such as short working and express patterns. Connections with other services can also be
described;
— the days on which the services run, including availability on public holidays and other exceptions;
— composite journeys such as train journeys that merge or split trains;
— information about the Operators providing the service;
— additional operational information, including, positioning runs, garages, layovers, duty crews,
useful for AVL and on-board ticketing systems;
— data about the Accessibility of services to passengers with restricted mobility;
— data are versioned with management metadata allowing updates across distributed systems;
— fare structures, (flat fares, point to point fares, zonal fares);
— fare products (Single tickets, return tickets, day, and season passses etc);
— fare prices that apply at specific dates.
0.4 NeTEx exchanging data modality
Data in NeTEx format is encoded as XML documents that should conform exactly to the defined schema,
and conformance can be checked automatically by standard XML validator tools. The schema can also
be used to create bindings to different programming languages to assist automating part of the
implementation process for creating software that supports NeTEx formats.
In this perspective, a NeTEx service need only to implement those elements of relevance to its business
objectives – extraneous elements present in the binding can be ignored. Parties using NeTEx for a
particular purpose will typically define
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.