Intelligent transport systems - ITS spatial data - Data exchange on changes in road attributes

This document defines the content specification for the exchange of road-related spatial data, and especially updates thereof. Based on the content specification, this document defines also a physical exchange format (structure and encoding) for the actual data exchange. In addition, it defines web services that are needed to make the coded data on updates available. Exchange of dynamic information is not in the scope of this document.
Although the focus of this document is on providing information on updates, the technology described in this document in principle also enables the exchange of full datasets, either concerning the whole road network in a coverage area, including all geometry and all attributes, or a subset, concerning for instance all instances of one or more specific attributes.
NOTE   This specification does not support the provision of updates concerning geometry. The provision of geometry associated with attribution change is supported, in the context of providing the location of attribute change.

Intelligente Verkehrssysteme - Räumliche ITS-Daten - Datenaustausch zu Änderungen von Straßenattributen

Systèmes de transport intelligents - Données spatiales STI - Échange de données sur les modifications d'attributs routiers

Inteligentni transportni sistemi - Prostorski podatki ITS - Izmenjava podatkov o spremembah atributov cest

Ta dokument določa specifikacijo vsebine za izmenjavo prostorskih podatkov, povezanih s cestami, in še zlasti njihove posodobitve. Na podlagi specifikacije vsebine ta dokument določa tudi fizični format izmenjave (strukturo in kodiranje) za dejansko izmenjavo podatkov. Poleg tega določa spletne storitve, ki so potrebne za razpoložljivost kodiranih podatkov o posodobitvah. Izmenjava dinamičnih informacij ne spada na področje uporabe tega dokumenta.
Čeprav je bistvo tega dokumenta zagotavljanje informacij o posodobitvah, tehnologija, ki je opisana v tem dokumentu, načeloma omogoča tudi izmenjavo celotnih naborov podatkov v povezavi s celotnim cestnim omrežjem na območju pokritosti, vključno z vso geometrijo in atributi, ali podskupino, na primer za vse primere enega ali več posebnih atributov.
OPOMBA: Ta specifikacija ne podpira zagotavljanja posodobitev o geometriji. Zagotavljanje geometrije v povezavi s spremembo atributa je podprto v okviru zagotavljanja lokacije spremembe atributov.

General Information

Status
Published
Publication Date
11-Dec-2018
Current Stage
6060 - Definitive text made available (DAV) - Publishing
Due Date
12-Dec-2018
Completion Date
12-Dec-2018

Buy Standard

Technical specification
-TS CEN/TS 17268:2019
English language
171 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TS CEN/TS 17268:2019
01-februar-2019
Inteligentni transportni sistemi - Prostorski podatki ITS - Izmenjava podatkov o
spremembah atributov cest

Intelligent transport systems - ITS spatial data - Data exchange on changes in road

attributes

Intelligente Verkehrssysteme - Räumliche ITS-Daten - Datenaustausch zu Änderungen

von Straßenattributen

Systèmes de transport intelligents - Données spatiales STI - Échange de données sur

les modifications d'attributs routiers
Ta slovenski standard je istoveten z: CEN/TS 17268:2018
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST-TS CEN/TS 17268:2019 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST-TS CEN/TS 17268:2019
---------------------- Page: 2 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
December 2018
TECHNISCHE SPEZIFIKATION
ICS 35.240.60
English Version
Intelligent transport systems - ITS spatial data - Data
exchange on changes in road attributes

Systèmes de transport intelligents - Données spatiales Intelligente Verkehrssysteme - Räumliche ITS-Daten -

STI - Échange de données sur les modifications Datenaustausch zu Änderungen von Straßenattributen

d'attributs routiers

This Technical Specification (CEN/TS) was approved by CEN on 29 July 2018 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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,

Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, 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

© 2018 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 17268:2018 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268:2018 (E)
Contents Page

European foreword ....................................................................................................................................................... 4

Introduction .................................................................................................................................................................... 5

1 Scope .................................................................................................................................................................... 7

2 Normative references .................................................................................................................................... 7

3 Terms and definitions ................................................................................................................................... 8

4 Symbols and abbreviated terms ................................................................................................................ 9

5 Conformance ..................................................................................................................................................... 9

6 Data content specification ........................................................................................................................ 10

6.1 Introduction ................................................................................................................................................... 10

6.2 Package overview ........................................................................................................................................ 10

6.3 Package Road features ............................................................................................................................... 12

6.3.1 Overview ......................................................................................................................................................... 12

6.3.2 Class definitions ............................................................................................................................................ 14

6.3.3 Sub package Conditions ............................................................................................................................. 20

6.4 Package location referencing .................................................................................................................. 43

6.5 Package Updates ........................................................................................................................................... 56

6.5.1 Overview ......................................................................................................................................................... 56

6.5.2 Class definitions ............................................................................................................................................ 57

6.6 Package Metadata ........................................................................................................................................ 57

6.7 Package Feedback ........................................................................................................................................ 59

6.8 Package Data set ........................................................................................................................................... 65

7 Physical exchange format - structure and encoding ....................................................................... 69

7.1 Introduction ................................................................................................................................................... 69

7.2 GML schemas for TN-ITS ............................................................................................................................ 70

8 Service specification ................................................................................................................................... 72

8.1 Introduction ................................................................................................................................................... 72

8.1.1 Context ............................................................................................................................................................. 72

8.1.2 Discovery service scope ............................................................................................................................. 72

8.1.3 Download service scope ............................................................................................................................ 73

8.1.4 Download service decisions ..................................................................................................................... 73

8.1.5 Approach 1: Server defined update intervals .................................................................................... 73

8.1.6 Approach 2: Client defined update intervals ..................................................................................... 74

8.1.7 Server/Client defined update intervals - conclusion ...................................................................... 74

8.1.8 Versioning scheme ....................................................................................................................................... 75

8.2 Interface specification ................................................................................................................................ 75

8.2.1 Context ............................................................................................................................................................. 75

8.2.2 Server-side interfaces ................................................................................................................................. 75

8.2.3 Server-side classes and datatypes ......................................................................................................... 77

8.2.4 Server-side responsibilities ..................................................................................................................... 78

8.3 Interface implementation specification .............................................................................................. 81

Annex A (normative) Enumerations and CodeLists ...................................................................................... 82

A.1 Explanation of Structure ............................................................................................................................ 82

---------------------- Page: 4 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268:2018 (E)

A.2 Enumerations ................................................................................................................................................. 82

A.3 Codelists ........................................................................................................................................................... 86

Annex B (normative) TN-ITS XSD schemas .................................................................................................... 124

B.1 General .......................................................................................................................................................... 124

B.2 XML schemas ............................................................................................................................................... 124

B.2.1 TN-ITS.xsd .................................................................................................................................................... 124

B.2.2 Dataset.xsd ................................................................................................................................................... 124

B.2.3 RoadFeatures.xsd ...................................................................................................................................... 126

B.2.4 Conditions.xsd............................................................................................................................................. 129

B.2.5 LocationReferencing.xsd ......................................................................................................................... 137

B.2.6 Update.xsd .................................................................................................................................................... 142

B.2.7 Feedback.xsd ............................................................................................................................................... 143

B.2.8 Metadata.xsd ............................................................................................................................................... 146

B.2.9 OpenLR.xsd .................................................................................................................................................. 146

B.3 Linear referencing methods .................................................................................................................. 159

Annex C (informative) Examples of GML files ............................................................................................... 160

Annex D (informative) Alignment with EC Delegated Regulation 2015/962 and INSPIRE.......... 161

D.1 Context ........................................................................................................................................................... 161

D.2 Alignment with the Delegated Regulation 2015/962 supplementing the European ITS

Directive (2010/40/EU) .......................................................................................................................... 161

D.3 Alignment with INSPIRE Directive (2007/2/EU) and INSPIRE Implementing Rules ........ 164

D.3.1 Connection to INSPIRE Road Network data sets ............................................................................. 164

D.3.2 Use of INSPIRE Administrative Units .................................................................................................. 164

D.3.3 Alignment in regard to INSPIRE Metadata Implementing Rules .............................................. 164

Annex E (informative) Link to EN ISO 19148 ................................................................................................ 168

Bibliography .............................................................................................................................................................. 170

---------------------- Page: 5 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268:2018 (E)
European foreword

This document (CEN/TS 17268:2018) 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.

According to the CEN/CENELEC Internal Regulations, the national standards organisations of the

following countries are bound to announce this Technical Specification: 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, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,

Turkey and the United Kingdom
---------------------- Page: 6 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268:2018 (E)
Introduction

ITS digital maps (digital maps for ITS applications) were initially developed for in-vehicle navigation

systems. Over time, these maps evolved, and their use extended beyond mere navigation, as a range of

other in-vehicle driving support systems were developed, many of which need ITS digital maps as an

important component for processing, interpreting and relating sensor data. This evolution from

navigation via ADAS (advanced driver assistance systems) and then C-ITS (cooperative ITS systems) to

automated driving generates increasing requirements for the digital map, in terms of content

specification, detail, accuracy and timeliness. The latter characteristic signifies whether the map data are

up to date with respect to changes in the real world.

ITS digital maps represent the physical road network infrastructure and its attributes, as well as other

relevant geographic information. The related data has a more or less permanent character, and is

sometimes referred to as static road data; road data that do not often change [9]. Besides for the

abovementioned applications, accurate and up to date digital maps have also high significance for the

provision of real-time road status and traffic information. This concerns dynamic road-related data, with

a highly volatile and temporary character. Typically data that will not be included in a digital map, but

generally need digital map data for processing, representation and display.

Although the road infrastructure has a rather permanent character, changes of the road network and

related attributes do actually occur at a significant scale. There is a need for timely and comprehensive

propagation of information on such changes to digital maps used in ITS applications. Providers of such

maps use a multitude of data sources to maintain their map databases, in order to keep these accurate

and up to date. These sources include visual inspection (by driving the roads), and the use of vehicle

probe data (big data that need processing, interpretation and verification).

The specification in this document aims to enable another mechanism for provision of static road data,

with a focus on changes, directly from the source of the changes: the public road authorities and/or

(public/private) road operators, who build and maintain the roads, and decide on and implement the

day-to-day changes that are relevant for inclusion in ITS digital maps. If road authorities and road

operators maintain a digital road database of their network, and have good procedures for keeping such

database fully up to date in a timely manner with respect to these changes, this would constitute a highly

efficient and potentially timely source for information on such changes for ITS map providers, but also

for other users of such data.

Based on good procedures, intense cooperation between the two sides of this data chain, and experience

gained over time, the data flow will achieve a high level of reliability, with known and guaranteed quality.

The data constitutes well-defined discrete data elements that do not need any big-data type of processing,

permitting swift implementation for any potential users. Dependent on the timeliness of the processes

deployed at, respectively, road authorities, road operators, ITS map providers and map-update-provision

services, the TN-ITS concept permits future transfer of information on road network changes to in-vehicle

systems with minimal delays. This document defines the TN-ITS specification.

The exchanged data elements are termed road features in this document. Each road feature is required

to have a location reference, identifying its location in the road network. The specification within this

document is flexible and supports the introduction of new data types by permitting the use of external

code lists.

The “Commission Delegated Regulation (EU) 2015/962 of 18 December 2014 supplementing

Directive 2010/40/EU of the European Parliament and of the Council with regard to the provision of EU-

wide real-time traffic information services” [9] sets out the requirements, for road authorities, road

operators and service providers, for the accessibility, exchange, re-use and provision of updates of static

road data, road status data and traffic data. Road authorities and road operators provide the static road

data they collect and update in a standardized format, if available, or in any other machine-readable

format, on a non-discriminatory basis, and digital map providers collaborate with the data providers to

ensure that any inaccuracies related to static road data are signalled without delay to the road authorities

---------------------- Page: 7 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268:2018 (E)

and road operators from which the data originates. For dynamic road status data and traffic data the

Delegated Regulation in Articles 5 and 6 mandates the use of DATEX II (CEN/TS 16157 series and

subsequently upgraded versions) format or any machine-readable format fully compatible and

interoperable with DATEX II. The Delegated Regulation provides a list of types of static road data to be

addressed. This document takes full account of the part of the Regulation concerning static road data, and

supports and facilitates road authorities, road operators and digital map providers to implement and

fulfil the requirements of the Regulation with respect to the provision and use of such data.

The document’s specification is well aligned with Directive 2007/2/EU establishing an Infrastructure for

Spatial Information in the European Community (INSPIRE). Under this directive, public authorities

provide road network geospatial data sets in an INSPIRE-compliant way. Linear location referencing

enabled by this document’s specification establishes a direct (and INSPIRE-compliant) connection

between the exchanged road features and the originating geospatial data set of the public authority. This

will provide users with easy access to the specific location of the road feature in the originating database

for inspection, in case decoding of the dynamic location reference, used for automated processing of the

data, fails.

The idea for the TN-ITS concept for data exchange developed during the EU-funded projects

PReVENT/MAPS&ADAS (2004/2007) and SpeedAlert (2004/2005), and was further elaborated and

tested in the EU-funded ROSATTE project (Road Safety Attributes Exchange Infrastructure in Europe;

2008-2010), in which the basis for this specification was laid. This work led in 2013 to the foundation of

the TN-ITS Platform for deployment of the concept. In the past years, implementation in several European

countries took place, and a further roll-out in Europe with support from the EU CEF Programme

(Connecting Europe Facility) is ongoing.

The European Committee for Standardization (CEN) draws attention to the fact that it is claimed that

compliance with some stipulations of this document may involve the use of one or more patents when

using AGORA-C location referencing, standardized in ISO 17572-3, and/or OpenLR location referencing,

both described in 6.4 and Annex B. EN ISO 19148 for linear referencing has not identified any patents.

CEN takes no position concerning the evidence, validity and scope of these patent rights.

---------------------- Page: 8 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268:2018 (E)
1 Scope

This document defines the content specification for the exchange of road-related spatial data, and

especially updates thereof. Based on the content specification, this document defines also a physical

exchange format (structure and encoding) for the actual data exchange. In addition, it defines web

services that are needed to make the coded data on updates available. Exchange of dynamic information

is not in the scope of this document.

Although the focus of this document is on providing information on updates, the technology described in

this document in principle also enables the exchange of full data sets, either concerning the whole road

network in a coverage area, including all geometry and all attributes, or a subset, concerning for instance

all instances of one or more specific attributes.

NOTE This document does not support the provision of updates concerning geometry. The provision of

geometry associated with attribution change is supported, in the context of providing the location of attribute

change.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

EN ISO 14823, Intelligent transport systems - Graphic data dictionary (ISO 14823)

EN ISO 14825, Intelligent transport systems - Geographic Data Files (GDF) - GDF5.0 (ISO 14825)

EN ISO 19107, Geographic information - Spatial schema (ISO 19107)
EN ISO 19108, Geographic information - Temporal schema (ISO 19108)
EN ISO 19109, Geographic information - Rules for application schema (ISO 19109)

EN ISO 19111, Geographic information - Spatial referencing by coordinates (ISO 19111)

EN ISO 19115-1:2014, Geographic information – Metadata – Part 1: Fundamentals (ISO 19115-1:2014)

EN ISO 19115-2, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data

(ISO 19115-2)

EN ISO 19136, Geographic information - Geography Markup Language (GML) (ISO 19136)

EN ISO 19148, Geographic information - Linear referencing (ISO 19148)

ISO 17572-3, Intelligent transport systems (ITS) - Location referencing for geographic databases - Part 3:

Dynamic location references (dynamic profile)
ISO 19103, Geographic information - Conceptual schema language

ISO/TS 19115-3, Geographic information – Metadata – Part 3: XML schema implementation for

fundamental concepts
---------------------- Page: 9 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268:2018 (E)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1
location reference
code which provides a reference to a simple or compound geographic object

Note 1 to entry: With a single Location Referencing Method, one reference shall define unambiguously and

exactly one location in the location referencing system. The reference is the set of data which is passed between

different implementations of a location referencing system to identify the location.

Note 2 to entry: A location reference code is created from information in the road database that represents the

road network, either based on a location referencing system that is reflected in the road database (including linear

referencing systems), or on coordinates and attributes extracted from the road database. A location reference may

address a point location, a linear location or an area location.
3.2
digital map database

structured set of digital and alphanumeric data portraying geographic locations and relationships of

spatial features

Note 1 to entry: Typically, such structures represent, but are not limited to, the digital form of hard copy maps.

For example, drawings can be imported into a Geographic Information System (GIS) and considered as a form of

digital map.
[SOURCE: ISO 17572-1:2013]
3.3
road database

structured set of digital and alphanumeric data representing characteristics of a road network, possibly

including spatial representation
3.4
road feature

distinctive road-related attribute or object including its location that defines a real-world phenonemon

Note 1 to entry: The location may be a point, a linear location or an area location, and is expressed by a location

reference.
3.5
road sign

physical traffic control device intended to communicate specific information to road users through a

word, symbol, and/or arrow legend

Note 1 to entry: Road signs do not include highway traffic signals, pavement markings, delineators, or

channelization devices.
[SOURCE: CEN ISO/TS 19091:2017]
---------------------- Page: 10 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268:2018 (E)

Note 2 to entry: Road signs are by their nature associated with a point location.

Note 3 to entry: Road signs may be permanent or temporary fixed plates (with or without temporal limitations),

signs displayed on variable message signs or changeable boards, or other means of displaying signs.

3.6
traffic regulation

rule or directive, made and maintained by an authority, related to the road network and its use

Note 1 to entry: A traffic regulation may cover a point along a road, a linear stretch of a road or an area (which

can be a complete national territory (e.g. “generic speed limits”)), and may be expressed by one or more road signs,

road markings or traffic signals. Not all traffic regulations are expressed by road signs.

4 Symbols and abbreviated terms

ADR European Agreement concerning the International Carriage of Dangerous Goods by Road

GDF Geographic Data Files
GML Geographic Markup Language
ID Identifier
INSPIRE Infrastructure for Spatial Information in Europe
ITS Intelligent Transport Systems
OCL Object Constraint Language
OGC Open Geospatial Consortium
REST Representational state transfer
ROSATTE ROad Safety ATTributes in Europe
TN-ITS Transport Network – Intelligent Transport Systems
UML Unified Modelling Language
UTC Coordinated Universal Time
UUID Universally Unique Identifier
WADL Web Application Description Language
XML Extensible Markup Language
XSD XML Schema Definition
5 Conformance
Conformance is achieved by ensuring conformance to:
1. the requirements of the data content specification (Clause 6);

2. the requirements of structure and encoding of the physical exchange format (Clause 7);

3. The requirements of the service specification (Clause 8).
---------------------- Page: 11 ----------------------
SIST-TS CEN/TS 17268:2019
CEN/TS 17268:2018 (E)
6 Data content specification
6.1 Introduction

To comply with the requirements of the INSPIRE Directive and its technical specifications and the

ISO 19100 series of standards, the conceptual data content specification has been specified in

conformance with EN ISO 19109 – Rules for application schema. The data content specification specifies

the various classes of information that are being used within TN-ITS without mandating a particular

technology for implementation. The data content specification uses UML constructs such as packages,

classes, attributes, associations and OCL constraints, and assumes that the reader is f

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.