SIST-TS CEN/TS 16614-4:2020
(Main)Public transport - Network and Timetable Exchange (NeTEx) - Part 4: Passenger Information European Profile
Public transport - Network and Timetable Exchange (NeTEx) - Part 4: Passenger Information European Profile
This technical specification is a profile of CEN/TS 16614 series. It focuses on information relevant to feed passenger information services and excludes operational and fares information.
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V6 (EN 12986) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3) and supports information exchange of relevance to public transport services for passenger information and AVMS systems.
As for most data exchange standards, defining subsets of data and dedicated rules for some specific use case is of great help for implementers and for the overall interoperability. This subset is usually called profile and this profile targets passenger information as only use case.
Öffentlicher Verkehr - Netzwerk- und Fahrplan-Austausch (NeTEx) - Teil 4: Europäisches Profil für Reisenden Informationen
Transport public - Échange des données réseau et horaires (NeTex) - Partie 4 : Profil Européen pour l'Information Voyageur
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 4. del: Evropski profil za potovalne informacije
General Information
- Status
- Published
- Publication Date
- 29-Apr-2020
- Technical Committee
- ITC - Information technology
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 23-Apr-2020
- Due Date
- 28-Jun-2020
- Completion Date
- 30-Apr-2020
Relations
- Effective Date
- 19-Jun-2024
Overview
CEN/TS 16614-4:2020 - Public transport: NeTEx Part 4 (Passenger Information European Profile) is a CEN technical specification that defines a focused profile of the NeTEx (Network and Timetable Exchange) series for exchanging the data needed by passenger information systems. NeTEx is a data exchange model for scheduled public transport information based on Transmodel and SIRI. This Part 4 profile narrows the NeTEx model to the subset relevant to passenger-facing services and AVMS (Audio-Visual and Messaging Systems), explicitly excluding operational and fares information to improve interoperability and simplify implementations for passenger information use cases.
Key topics and technical requirements
The specification provides precise rules and structures implementers must follow, including:
- Profile scope and presentation conventions - how NeTEx elements are presented and which subsets apply to passenger information.
- Framework and data governance - concepts such as DataManagedObject, Versioning, Codespace, ValidityCondition and ResponsibilitySet that control identity, provenance and lifecycle of data.
- Relationships and integrity - entity references, VersionOfObjectRef, and XML integrity checking rules to ensure consistent, interoperable data exchange.
- Frames and defaults - use of Version Frames, TypeOfFrame and FrameDefaults to package data snapshots and manage versions.
- Stop profile and place model - stop places, quays, entrances, stop place hierarchies, site elements and address models that underpin passenger-facing location information.
- Network and timetable constructs - lines, routes, destination displays, via points and network topology elements relevant to creating public timetable information.
- Accessibility and facility descriptions - AccessibilityAssessment, facility sets and accommodation descriptors to support accessible travel information and traveler needs.
- Presentation and locale - presentation components, locales and contact details to format passenger information appropriately.
Applications and who uses it
CEN/TS 16614-4:2020 is targeted at organizations building or integrating passenger information systems and services, including:
- Public transport authorities and operators preparing feeds for journey planners and passenger displays
- ITS integrators and software vendors implementing NeTEx-based data feeds
- AVMS and real-time passenger information providers that require consistent, standardized network and timetable data
- Mobility platforms and MaaS integrators that consume scheduled public transport data for end-user apps
By adopting this European profile, implementers reduce complexity, improve cross-border interoperability and accelerate deployment of consistent passenger information services.
Related standards
- NeTEx family: CEN/TS 16614 series (this profile is Part 4)
- Transmodel V6 (referenced in the document)
- SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3)
Keywords: NeTEx, CEN/TS 16614-4, Passenger Information European Profile, public transport data exchange, timetable exchange, Transmodel, SIRI, stop place, accessibility, network topology, versioning.
Frequently Asked Questions
SIST-TS CEN/TS 16614-4:2020 is a technical specification published by the Slovenian Institute for Standardization (SIST). Its full title is "Public transport - Network and Timetable Exchange (NeTEx) - Part 4: Passenger Information European Profile". This standard covers: This technical specification is a profile of CEN/TS 16614 series. It focuses on information relevant to feed passenger information services and excludes operational and fares information. NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V6 (EN 12986) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3) and supports information exchange of relevance to public transport services for passenger information and AVMS systems. As for most data exchange standards, defining subsets of data and dedicated rules for some specific use case is of great help for implementers and for the overall interoperability. This subset is usually called profile and this profile targets passenger information as only use case.
This technical specification is a profile of CEN/TS 16614 series. It focuses on information relevant to feed passenger information services and excludes operational and fares information. NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V6 (EN 12986) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3) and supports information exchange of relevance to public transport services for passenger information and AVMS systems. As for most data exchange standards, defining subsets of data and dedicated rules for some specific use case is of great help for implementers and for the overall interoperability. This subset is usually called profile and this profile targets passenger information as only use case.
SIST-TS CEN/TS 16614-4:2020 is classified under the following ICS (International Classification for Standards) categories: 03.220.01 - Transport in general; 35.240.60 - IT applications in transport. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST-TS CEN/TS 16614-4:2020 has the following relationships with other standards: It is inter standard links to kSIST-TS FprCEN/TS 16614-4:2025. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
SIST-TS CEN/TS 16614-4:2020 is associated with the following European legislation: EU Directives/Regulations: 2010/40/EU. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
You can purchase SIST-TS CEN/TS 16614-4:2020 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of SIST standards.
Standards Content (Sample)
SLOVENSKI STANDARD
01-junij-2020
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 4. del:
Evropski profil za potovalne informacije
Public transport - Network and Timetable Exchange (NeTEx) - Part 4: Passenger
Information European Profile
Öffentlicher Verkehr - Netzwerk- und Fahrplan-Austausch (NeTEx) - Teil 4: Europäisches
Profil für Reisenden Informationen
Transport public - Échange des données réseau et horaires (NeTex) - Partie 4 : Profil
Européen pour l'Information Voyageur
Ta slovenski standard je istoveten z: CEN/TS 16614-4:2020
ICS:
03.220.01 Transport na splošno Transport in general
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
CEN/TS 16614-4
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
April 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.60
English Version
Public transport - Network and Timetable Exchange
(NeTEx) - Part 4: Passenger Information European Profile
Transport public - Échange des données réseau et Öffentlicher Verkehr - Netzwerk- und Fahrplan-
horaires (NeTex) - Partie 4 : Profil Européen pour Austausch (NeTEx) - Teil 4: Europäisches Profil für
l'Information Voyageur Reisenden Informationen
This Technical Specification (CEN/TS) was approved by CEN on 2 March 2020 for provisional application.
The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.
CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, 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: Rue de la Science 23, B-1040 Brussels
© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16614-4:2020 E
worldwide for CEN national Members.
Contents Page
European foreword . 8
Introduction . 9
1 Scope . 13
2 Normative references . 13
3 Terms and definitions . 13
4 Presentation conventions . 16
4.1 Recap of NeTEx presentation conventions . 16
4.2 Additional EPIP presentation conventions . 17
4.3 Transmodel definitions and EPIP . 18
5 Framework . 19
5.1 Introduction . 19
5.2 DataManagedObject, Version and Codespace . 19
5.2.1 Overview . 19
5.2.2 Entity (Abstract) . 21
5.2.3 EntityInVersion (Abstract) . 21
5.2.4 DataManagedObject (Abstract) . 22
5.2.5 AlternativeText (Subcomponent of DataManagedObject) . 23
5.2.6 KeyValue (Subcomponent of DataManagedObject) . 23
5.2.7 Version . 24
5.2.8 Codespace . 24
5.2.9 ValidityCondition . 26
5.2.10 ValidBetween . 27
5.2.11 ResponsibilitySet . 27
5.2.12 ResponsibilityRoleAssignment (Subcomponent of ResponsibilitySet) . 27
5.2.13 DataSource . 28
5.3 Relationships and entity references . 29
5.3.1 General rules . 29
5.3.2 VersionOfObjectRef . 30
5.3.3 Integrity Checking of XML Documents . 31
5.3.4 Identity uniqueness scope . 32
5.4 Frames . 33
5.4.1 Overview . 33
5.4.2 Version Frame (Abstract) . 34
5.4.3 TypeOfFrame . 35
5.4.4 Specific frames and General Frames . 36
5.4.5 Composite Frame . 37
5.4.6 FrameDefaults . 37
5.5 Generic elements . 38
5.5.1 Introduction . 38
5.5.2 TypeOfValue (Abstract) . 38
5.5.3 ValueSet . 39
5.5.4 GroupOfEntities (Abstract) . 40
5.5.5 Point (Abstract) . 40
5.5.6 Location (Subcomponent of Point) . 41
5.5.7 Link (Abstract) . 41
5.5.8 LinkSequence (Abstract) . 42
5.5.9 PointInLinkSequence (Abstract) . 43
5.5.10 Zone (Abstract) . 43
5.5.11 Transport Mode and Submode . 43
5.5.12 Assignment (Abstract) . 44
5.5.13 Presentation (Subcomponent – Multipurpose) . 45
5.5.14 Locale (Subcomponent – Multipurpose) . 46
5.5.15 Booking Arrangements (Subcomponent – Multipurpose) . 46
5.5.16 ContactDetails (Subcomponent – Multipurpose) . 47
5.6 Accessibility . 47
5.6.1 Overview . 47
5.6.2 AccessibilityAssessment (Subcomponent – Multipurpose) . 48
5.6.3 AccessibilityLimitation (Subcomponent of AccessibilityAssessment) . 49
5.7 Facility sets . 50
5.7.1 Overview . 50
5.7.2 FacilitySet (Abstract) . 51
5.7.3 ServiceFacilitySet . 51
5.7.4 Accommodation – (Subcomponent of ServiceFacilitySet) . 51
5.7.5 SiteFacilitySet . 52
6 Stop Profile . 52
6.1 Overview . 52
6.2 Stop Place hierarchies . 54
6.3 Other types of Place . 57
6.3.1 Introduction. 57
6.3.2 Place (Abstract) . 58
6.3.3 AddressablePlace (Abstract) . 58
6.3.4 SiteElement (Abstract) . 59
6.3.5 Site (Abstract) . 60
6.3.6 Address (Abstract) . 61
6.3.7 PostalAddress (Subcomponent of SITE in EPIP) . 62
6.3.8 RoadAddress (Subcomponent of SITE in EPIP). 62
6.3.9 Topographic Place . 63
6.3.10 TopographicPlaceDescriptor (Subcomponent) . 64
6.3.11 Point of Interest. 64
6.4 Stop Places. 65
6.4.1 StopPlace . 65
6.4.2 SiteComponent (Abstract) . 67
6.4.3 StopPlaceSpace (Abstract) . 67
6.4.4 Quay (Subcomponent of Quay) . 67
6.4.5 Entrance (Abstract). 68
6.4.6 StopPlaceEntrance . 69
6.5 GroupOfStopPlaces . 69
6.6 TariffZone . 69
7 Network and Timetables . 70
7.1 General . 70
7.2 Basic network topology . 70
7.2.1 Overview . 70
7.2.2 Line . 71
7.2.3 AllowedLineDirection (Subcomponent of Line) . 73
7.2.4 GroupOfLines . 73
7.2.5 Network . 74
7.2.6 DestinationDisplay . 74
7.2.7 Via . 75
7.2.8 DestinationDisplayVariant . 75
7.2.9 Organisation (Abstract) . 76
7.2.10 Operator . 77
7.2.11 Authority . 77
7.3 Routes . 77
7.3.1 Overview . 77
7.3.2 RoutePoint . 78
7.3.3 RouteLink . 78
7.3.4 Route . 79
7.3.5 PointOnRoute (Subcomponent of Route) . 79
7.4 Service patterns . 80
7.4.1 Overview . 80
7.4.2 JourneyPattern (Abstract in EPIP) . 81
7.4.3 ServicePattern . 82
7.4.4 PointInJourneyPattern (Abstract in EPIP). 82
7.4.5 StopPointInJourneyPattern (Subcomponent of JourneyPattern) . 83
7.4.6 Direction . 84
7.4.7 TimingPoint (Abstract in EPIP) . 85
7.4.8 ScheduledStopPoint . 85
7.4.9 Service Link . 86
7.5 Assigning Stops . 87
7.5.1 Overview . 87
7.5.2 StopAssignment (Abstract) . 87
7.5.3 PassengerStopAssignment . 88
7.5.4 DynamicStopAssignment . 88
7.5.5 TrainStopAssignment (Subcomponent of Passenger Stop Assignment) . 89
7.6 Connections, transfers and interchanging . 90
7.6.1 Overview . 90
7.6.2 Transfer (Abstract) . 90
7.6.3 Transfer Duration (Subcomponent of Transfer) . 91
7.6.4 Connection . 91
7.6.5 ConnectionEnd (Subcomponent of Connection) . 92
7.6.6 SiteConnection . 92
7.6.7 SiteConnectionEnd (Subcomponent of SiteConnection) . 93
7.6.8 DefaultConnection . 93
7.6.9 DefaultConnectionEnd (Subcomponent of DefaultConnection) . 94
7.7 Vehicle journeys and passing times . 94
7.7.1 Overview . 94
7.7.2 Journey (Abstract) . 96
7.7.3 ServiceJourney . 96
7.7.4 PassingTime . 97
7.7.5 PassingTime (Abstract) . 98
7.7.6 TimetabledPassingTime (Subcomponent – Service Journey) . 98
7.7.7 GroupOfServices . 98
7.7.8 GroupOfServicesMember (Subcomponent of GroupOfServices) . 99
7.8 Very frequent journeys . 100
7.8.1 Introduction . 100
7.8.2 TemplateVehicleJourney. 100
7.8.3 JourneyFrequencyGroup (Abstract) . 101
7.8.4 HeadwayJourneyGroup (Subcomponent of TemplateJourney) . 101
7.9 Transferring between services . 102
7.9.1 Introduction . 102
7.9.2 Interchange (Abstract) . 102
7.9.3 ServiceJourneyInterchange . 103
7.10 Trains and train coupling . 103
7.10.1 Overview . 103
7.10.2 TrainNumber . 104
7.10.3 JourneyPart (Subcomponent of ServiceJourney) . 105
7.10.4 JourneyPartCouple . 105
7.10.5 JourneyPartPosition (Subcomponent of JourneyPartCouple) . 106
7.11 Vehicles and Trains . 107
7.11.1 Overview . 107
7.11.2 VehicleType . 107
7.11.3 Train . 108
7.11.4 TrainElement (Subcomponent of Train) . 109
7.11.5 TrainComponent (Subcomponent of Train) . 109
7.12 Notices . 110
7.12.1 Introduction. 110
7.12.2 Notice (Subcomponent - Multipurpose) . 110
7.12.3 NoticeAssigment (Subcomponent - Multipurpose) . 111
7.13 Calendars . 112
7.13.1 Overview . 112
7.13.2 DayType . 112
7.13.3 PropertyOfDay (Subcomponent of DayType) . 113
7.13.4 Timeband (Subcomponent of DayType) . 114
7.13.5 ServiceCalendar . 115
7.13.6 OperatingDay (Subcomponent of ServiceCalendar) . 115
7.13.7 DayTypeAssignment (Subcomponent of ServiceCalendar) . 116
7.13.8 Operating Period (Abstract in EPIP) . 117
7.13.9 UicOperatingPeriod (Subcomponent of ServiceCalendar) . 117
7.14 Flexible services . 118
7.14.1 Introduction. 118
7.14.2 FlexibleLine . 118
7.14.3 FlexiblePointProperties (Subcomponent – Multipurpose) . 118
7.14.4 FlexibleServiceProperties (Subcomponent of SERVICE JOURNEY) . 119
8 Common rules . 120
8.1 Version management of data . 120
8.2 Use of validity conditions in EPIP . 121
8.3 Populating creation and change dates . 121
8.4 Codespaces and the structure of identifiers . 122
8.4.1 Introduction. 122
8.4.2 Use of codespaces in EPIP . 123
8.4.3 Identifier structure for EPIP data objects. . 123
8.4.4 Identifier structure for EPIP version frames . 124
8.5 Versions of the EPIP . 129
8.6 Dependencies between frames . 129
8.7 Organisation and nesting of elements within an EPIP document . 130
8.8 Responsibility for data. 130
8.9 Handling large data sets . 131
8.10 Available types of frame . 132
8.10.1 Type of Frame list . 132
8.10.2 Classes for SPECIFIC FRAMEs . 133
8.10.3 Classes for COMPOSITE FRAMEs . 137
8.10.4 Classes for EPIP Metadata FRAMEs . 138
8.11 Completeness of data . 139
8.11.1 Introduction . 139
8.11.2 Empty values . 139
8.12 Data exchange . 140
8.13 PublicationDelivery . 140
8.13.1 Introduction . 140
8.13.2 Publication Request (Subcomponent of PublicationDelivery) . 141
8.13.3 NetworkFrameTopic (Subcomponent of PublicationDelivery) . 141
8.13.4 NetworkFilterByValue (Subcomponent of PublicationDelivery) . 142
8.13.5 PublicationDelivery example . 142
8.14 Names of files for EPIP documents . 144
8.15 Extending the profile . 145
9 Profile compliance and data quality checking . 146
9.1 Introduction . 146
9.2 Methods of checking the quality of data . 146
9.3 Quality issue resolution . 147
9.4 Profile validator rules . 147
9.5 Metadata for profiles . 148
9.6 Summary of data quality rules for EPIP . 149
9.7 Referential integrity (automatic) . 155
Annex A (normative) Data Dictionary . 156
Annex B (normative) Facility code list . 166
B.1 AccessFacilityList . 166
B.2 AccessibilityInfoFacilityList . 166
B.3 AccessibilityToolList . 166
B.4 AccommodationAccessList . 167
B.5 AccommodationFacilityList . 167
B.6 AssistanceFacilityList . 167
B.7 BoardingPermisssion . 167
B.8 BookingProcessFacilityList . 168
B.9 CarServiceFacilityList . 168
B.10 CateringFacilityList . 168
B.11 CouchetteFacilityList . 169
B.12 FamilyFacilityList . 169
B.13 FareClasses . 169
B.14 GenderLimitation . 169
B.15 GroupBookingFacility . 170
B.16 LuggageCarriageFacilityList . 170
B.17 MealFacilityList. 170
B.18 MedicalFacilityList . 170
B.19 MobilityFacilityList . 171
B.20 NuisanceFacilityList . 171
B.21 PassengerCommsFacilityList . 171
B.22 PassengerInformationEquipmentList . 172
B.23 PassengerInformationFacilityList . 172
B.24 RetailFacilityList . 172
B.25 SafetyFacilityList . 172
B.26 SanitaryFacilityList . 173
B.27 ServiceReservationFacilityList . 173
B.28 TicketingFacilityList . 173
B.29 TicketingServiceFacilityList . 174
B.30 UicProductCharacteristicList . 174
B.31 UicTrainRate . 174
B.32 VehicleFacilityList . 174
Annex C (informative) Related EU Directive . 175
Bibliography . 177
European foreword
This document (CEN/TS 16614-4:2020) 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 shall not be held responsible for identifying any or all such patent rights.
This document presents a Passenger Information European Profile of the European Technical
Specification known as “NeTEx”. NeTEx provides a framework for specifying communications and data
exchange protocols for organizations wishing to exchange scheduled Information relating to public
transport operations.
NeTEx is made up of three parts defining a single European Standard, which provides a complete
e
...
SLOVENSKI STANDARD
01-junij-2020
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 4. del:
Evropski profil za informacije o potnikih
Public transport - Network and Timetable Exchange (NeTEx) - Part 4: Passenger
Information European Profile
Öffentlicher Verkehr - Netzwerk- und Fahrplan-Austausch (NeTEx) - Teil 4: Europäisches
Profil für Reisenden Informationen
Transport public - Échange des données réseau et horaires (NeTex) - Partie 4 : Profil
Européen pour l'Information Voyageur
Ta slovenski standard je istoveten z: CEN/TS 16614-4:2020
ICS:
03.220.01 Transport na splošno Transport in general
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
CEN/TS 16614-4
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
April 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.60
English Version
Public transport - Network and Timetable Exchange
(NeTEx) - Part 4: Passenger Information European Profile
Transport public - Échange des données réseau et Öffentlicher Verkehr - Netzwerk- und Fahrplan-
horaires (NeTex) - Partie 4 : Profil Européen pour Austausch (NeTEx) - Teil 4: Europäisches Profil für
l'Information Voyageur Reisenden Informationen
This Technical Specification (CEN/TS) was approved by CEN on 2 March 2020 for provisional application.
The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.
CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, 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: Rue de la Science 23, B-1040 Brussels
© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16614-4:2020 E
worldwide for CEN national Members.
Contents Page
European foreword . 8
Introduction . 9
1 Scope . 13
2 Normative references . 13
3 Terms and definitions . 13
4 Presentation conventions . 16
4.1 Recap of NeTEx presentation conventions . 16
4.2 Additional EPIP presentation conventions . 17
4.3 Transmodel definitions and EPIP . 18
5 Framework . 19
5.1 Introduction . 19
5.2 DataManagedObject, Version and Codespace . 19
5.2.1 Overview . 19
5.2.2 Entity (Abstract) . 21
5.2.3 EntityInVersion (Abstract) . 21
5.2.4 DataManagedObject (Abstract) . 22
5.2.5 AlternativeText (Subcomponent of DataManagedObject) . 23
5.2.6 KeyValue (Subcomponent of DataManagedObject) . 23
5.2.7 Version . 24
5.2.8 Codespace . 24
5.2.9 ValidityCondition . 26
5.2.10 ValidBetween . 27
5.2.11 ResponsibilitySet . 27
5.2.12 ResponsibilityRoleAssignment (Subcomponent of ResponsibilitySet) . 27
5.2.13 DataSource . 28
5.3 Relationships and entity references . 29
5.3.1 General rules . 29
5.3.2 VersionOfObjectRef . 30
5.3.3 Integrity Checking of XML Documents . 31
5.3.4 Identity uniqueness scope . 32
5.4 Frames . 33
5.4.1 Overview . 33
5.4.2 Version Frame (Abstract) . 34
5.4.3 TypeOfFrame . 35
5.4.4 Specific frames and General Frames . 36
5.4.5 Composite Frame . 37
5.4.6 FrameDefaults . 37
5.5 Generic elements . 38
5.5.1 Introduction . 38
5.5.2 TypeOfValue (Abstract) . 38
5.5.3 ValueSet . 39
5.5.4 GroupOfEntities (Abstract) . 40
5.5.5 Point (Abstract) . 40
5.5.6 Location (Subcomponent of Point) . 41
5.5.7 Link (Abstract) . 41
5.5.8 LinkSequence (Abstract) . 42
5.5.9 PointInLinkSequence (Abstract) . 43
5.5.10 Zone (Abstract) . 43
5.5.11 Transport Mode and Submode . 43
5.5.12 Assignment (Abstract) . 44
5.5.13 Presentation (Subcomponent – Multipurpose) . 45
5.5.14 Locale (Subcomponent – Multipurpose) . 46
5.5.15 Booking Arrangements (Subcomponent – Multipurpose) . 46
5.5.16 ContactDetails (Subcomponent – Multipurpose) . 47
5.6 Accessibility . 47
5.6.1 Overview . 47
5.6.2 AccessibilityAssessment (Subcomponent – Multipurpose) . 48
5.6.3 AccessibilityLimitation (Subcomponent of AccessibilityAssessment) . 49
5.7 Facility sets . 50
5.7.1 Overview . 50
5.7.2 FacilitySet (Abstract) . 51
5.7.3 ServiceFacilitySet . 51
5.7.4 Accommodation – (Subcomponent of ServiceFacilitySet) . 51
5.7.5 SiteFacilitySet . 52
6 Stop Profile . 52
6.1 Overview . 52
6.2 Stop Place hierarchies . 54
6.3 Other types of Place . 57
6.3.1 Introduction. 57
6.3.2 Place (Abstract) . 58
6.3.3 AddressablePlace (Abstract) . 58
6.3.4 SiteElement (Abstract) . 59
6.3.5 Site (Abstract) . 60
6.3.6 Address (Abstract) . 61
6.3.7 PostalAddress (Subcomponent of SITE in EPIP) . 62
6.3.8 RoadAddress (Subcomponent of SITE in EPIP). 62
6.3.9 Topographic Place . 63
6.3.10 TopographicPlaceDescriptor (Subcomponent) . 64
6.3.11 Point of Interest. 64
6.4 Stop Places. 65
6.4.1 StopPlace . 65
6.4.2 SiteComponent (Abstract) . 67
6.4.3 StopPlaceSpace (Abstract) . 67
6.4.4 Quay (Subcomponent of Quay) . 67
6.4.5 Entrance (Abstract). 68
6.4.6 StopPlaceEntrance . 69
6.5 GroupOfStopPlaces . 69
6.6 TariffZone . 69
7 Network and Timetables . 70
7.1 General . 70
7.2 Basic network topology . 70
7.2.1 Overview . 70
7.2.2 Line . 71
7.2.3 AllowedLineDirection (Subcomponent of Line) . 73
7.2.4 GroupOfLines . 73
7.2.5 Network . 74
7.2.6 DestinationDisplay . 74
7.2.7 Via . 75
7.2.8 DestinationDisplayVariant . 75
7.2.9 Organisation (Abstract) . 76
7.2.10 Operator . 77
7.2.11 Authority . 77
7.3 Routes . 77
7.3.1 Overview . 77
7.3.2 RoutePoint . 78
7.3.3 RouteLink . 78
7.3.4 Route . 79
7.3.5 PointOnRoute (Subcomponent of Route) . 79
7.4 Service patterns . 80
7.4.1 Overview . 80
7.4.2 JourneyPattern (Abstract in EPIP) . 81
7.4.3 ServicePattern . 82
7.4.4 PointInJourneyPattern (Abstract in EPIP). 82
7.4.5 StopPointInJourneyPattern (Subcomponent of JourneyPattern) . 83
7.4.6 Direction . 84
7.4.7 TimingPoint (Abstract in EPIP) . 85
7.4.8 ScheduledStopPoint . 85
7.4.9 Service Link . 86
7.5 Assigning Stops . 87
7.5.1 Overview . 87
7.5.2 StopAssignment (Abstract) . 87
7.5.3 PassengerStopAssignment . 88
7.5.4 DynamicStopAssignment . 88
7.5.5 TrainStopAssignment (Subcomponent of Passenger Stop Assignment) . 89
7.6 Connections, transfers and interchanging . 90
7.6.1 Overview . 90
7.6.2 Transfer (Abstract) . 90
7.6.3 Transfer Duration (Subcomponent of Transfer) . 91
7.6.4 Connection . 91
7.6.5 ConnectionEnd (Subcomponent of Connection) . 92
7.6.6 SiteConnection . 92
7.6.7 SiteConnectionEnd (Subcomponent of SiteConnection) . 93
7.6.8 DefaultConnection . 93
7.6.9 DefaultConnectionEnd (Subcomponent of DefaultConnection) . 94
7.7 Vehicle journeys and passing times . 94
7.7.1 Overview . 94
7.7.2 Journey (Abstract) . 96
7.7.3 ServiceJourney . 96
7.7.4 PassingTime . 97
7.7.5 PassingTime (Abstract) . 98
7.7.6 TimetabledPassingTime (Subcomponent – Service Journey) . 98
7.7.7 GroupOfServices . 98
7.7.8 GroupOfServicesMember (Subcomponent of GroupOfServices) . 99
7.8 Very frequent journeys . 100
7.8.1 Introduction . 100
7.8.2 TemplateVehicleJourney. 100
7.8.3 JourneyFrequencyGroup (Abstract) . 101
7.8.4 HeadwayJourneyGroup (Subcomponent of TemplateJourney) . 101
7.9 Transferring between services . 102
7.9.1 Introduction . 102
7.9.2 Interchange (Abstract) . 102
7.9.3 ServiceJourneyInterchange . 103
7.10 Trains and train coupling . 103
7.10.1 Overview . 103
7.10.2 TrainNumber . 104
7.10.3 JourneyPart (Subcomponent of ServiceJourney) . 105
7.10.4 JourneyPartCouple . 105
7.10.5 JourneyPartPosition (Subcomponent of JourneyPartCouple) . 106
7.11 Vehicles and Trains . 107
7.11.1 Overview . 107
7.11.2 VehicleType . 107
7.11.3 Train . 108
7.11.4 TrainElement (Subcomponent of Train) . 109
7.11.5 TrainComponent (Subcomponent of Train) . 109
7.12 Notices . 110
7.12.1 Introduction. 110
7.12.2 Notice (Subcomponent - Multipurpose) . 110
7.12.3 NoticeAssigment (Subcomponent - Multipurpose) . 111
7.13 Calendars . 112
7.13.1 Overview . 112
7.13.2 DayType . 112
7.13.3 PropertyOfDay (Subcomponent of DayType) . 113
7.13.4 Timeband (Subcomponent of DayType) . 114
7.13.5 ServiceCalendar . 115
7.13.6 OperatingDay (Subcomponent of ServiceCalendar) . 115
7.13.7 DayTypeAssignment (Subcomponent of ServiceCalendar) . 116
7.13.8 Operating Period (Abstract in EPIP) . 117
7.13.9 UicOperatingPeriod (Subcomponent of ServiceCalendar) . 117
7.14 Flexible services . 118
7.14.1 Introduction. 118
7.14.2 FlexibleLine . 118
7.14.3 FlexiblePointProperties (Subcomponent – Multipurpose) . 118
7.14.4 FlexibleServiceProperties (Subcomponent of SERVICE JOURNEY) . 119
8 Common rules . 120
8.1 Version management of data . 120
8.2 Use of validity conditions in EPIP . 121
8.3 Populating creation and change dates . 121
8.4 Codespaces and the structure of identifiers . 122
8.4.1 Introduction. 122
8.4.2 Use of codespaces in EPIP . 123
8.4.3 Identifier structure for EPIP data objects. . 123
8.4.4 Identifier structure for EPIP version frames . 124
8.5 Versions of the EPIP . 129
8.6 Dependencies between frames . 129
8.7 Organisation and nesting of elements within an EPIP document . 130
8.8 Responsibility for data. 130
8.9 Handling large data sets . 131
8.10 Available types of frame . 132
8.10.1 Type of Frame list . 132
8.10.2 Classes for SPECIFIC FRAMEs . 133
8.10.3 Classes for COMPOSITE FRAMEs . 137
8.10.4 Classes for EPIP Metadata FRAMEs . 138
8.11 Completeness of data . 139
8.11.1 Introduction . 139
8.11.2 Empty values . 139
8.12 Data exchange . 140
8.13 PublicationDelivery . 140
8.13.1 Introduction . 140
8.13.2 Publication Request (Subcomponent of PublicationDelivery) . 141
8.13.3 NetworkFrameTopic (Subcomponent of PublicationDelivery) . 141
8.13.4 NetworkFilterByValue (Subcomponent of PublicationDelivery) . 142
8.13.5 PublicationDelivery example . 142
8.14 Names of files for EPIP documents . 144
8.15 Extending the profile . 145
9 Profile compliance and data quality checking . 146
9.1 Introduction . 146
9.2 Methods of checking the quality of data . 146
9.3 Quality issue resolution . 147
9.4 Profile validator rules . 147
9.5 Metadata for profiles . 148
9.6 Summary of data quality rules for EPIP . 149
9.7 Referential integrity (automatic) . 155
Annex A (normative) Data Dictionary . 156
Annex B (normative) Facility code list . 166
B.1 AccessFacilityList . 166
B.2 AccessibilityInfoFacilityList . 166
B.3 AccessibilityToolList . 166
B.4 AccommodationAccessList . 167
B.5 AccommodationFacilityList . 167
B.6 AssistanceFacilityList . 167
B.7 BoardingPermisssion . 167
B.8 BookingProcessFacilityList . 168
B.9 CarServiceFacilityList . 168
B.10 CateringFacilityList . 168
B.11 CouchetteFacilityList . 169
B.12 FamilyFacilityList . 169
B.13 FareClasses . 169
B.14 GenderLimitation . 169
B.15 GroupBookingFacility . 170
B.16 LuggageCarriageFacilityList . 170
B.17 MealFacilityList. 170
B.18 MedicalFacilityList . 170
B.19 MobilityFacilityList . 171
B.20 NuisanceFacilityList . 171
B.21 PassengerCommsFacilityList . 171
B.22 PassengerInformationEquipmentList . 172
B.23 PassengerInformationFacilityList . 172
B.24 RetailFacilityList . 172
B.25 SafetyFacilityList . 172
B.26 SanitaryFacilityList . 173
B.27 ServiceReservationFacilityList . 173
B.28 TicketingFacilityList . 173
B.29 TicketingServiceFacilityList . 174
B.30 UicProductCharacteristicList . 174
B.31 UicTrainRate . 174
B.32 VehicleFacilityList . 174
Annex C (informative) Related EU Directive . 175
Bibliography . 177
European foreword
This document (CEN/TS 16614-4:2020) 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 shall not be held responsible for identifying any or all such patent rights.
This document presents a Passenger Information European Profile of the European Technical
Specification known as “NeTEx”. NeTEx provides a framework for specifying communications and data
exchange protocols for organizations wishing to exchange scheduled Information relating to public
transport operations.
NeTEx is made up of three parts defining a single European Standard, which provides a complete
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...