CEN/TS 16157-5:2014

SLOVENSKI STANDARD
01-september-2014
Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri
upravljanju prometa in informiranju - 5. del: Merjeni in obdelani podatki za objavo
Intelligent transport systems - DATEX II data exchange specifications for traffic
management and information - Part 5: Measured and elaborated data publications
Intelligente Transportsysteme - DATEX II Datenaustausch Spezifikationen für
Verkehrsmanagement und Informationen - Teil 5: Gemessene und ausgearbeitete
Datenveröffentlichungen
Systèmes de transport intelligents - Spécifications Datex II d'échange de données pour
la gestion du trafic et l'information routière - Partie 5 : Publication de données mesurées
et de données calculées
Ta slovenski standard je istoveten z: CEN/TS 16157-5:2014
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

TECHNICAL SPECIFICATION
CEN/TS 16157-5
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
April 2014
ICS 35.240.60
English Version
Intelligent transport systems - DATEX II data exchange
specifications for traffic management and information - Part 5:
Measured and elaborated data publications
Systèmes de transport intelligents - Spécifications Datex II Intelligente Transportsysteme - DATEX II Datenaustausch
d'échange de données pour la gestion du trafic et Spezifikationen für Verkehrsmanagement und
l'information routière - Partie 5 : Publication de données Informationen - Teil 5: Gemessene und ausgearbeitete
mesurées et de données calculées Datenveröffentlichungen
This Technical Specification (CEN/TS) was approved by CEN on 27 January 2014 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, 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
© 2014 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16157-5:2014 E
worldwide for CEN national Members.

Contents Page
Foreword .4
Introduction .5
1 Scope .6
1.1 Conformance .6
2 Normative references .7
3 Terms and definitions .7
4 Symbols and abbreviated terms .8
5 UML notation .8
6 The Measurement Site Table Publication model .8
6.1 Overview of the Measurement Site Table Publication model .8
6.2 The “MeasurementSiteTablePublication” Package .8
7 The Measured Data Publication model . 11
7.1 Overview of the Measured Data Publication model . 11
7.2 The “MeasuredDataPublication” Package . 11
7.3 The “BasicData” Package . 14
7.4 The “TrafficStatus” Package . 16
7.5 The “TravelTimeData” Package . 18
7.6 The “TrafficData” Package . 19
7.7 The “TrafficHeadway” Package . 21
7.8 The “TrafficFlow” Package . 23
7.9 The “TrafficSpeed” Package . 24
7.10 The “TrafficConcentration” Package . 26
7.11 The “IndividualDataValues” Package . 27
7.12 The “WeatherData” Package . 29
7.13 The “Humidity” Package . 32
7.14 The “Visibility” Package . 33
7.15 The “Pollution” Package . 34
7.16 The “PrecipitationDetail” Package. 35
7.17 The “RoadsurfaceConditionMeasurements” Package . 36
7.18 The “Temperature” Package . 38
7.19 The “Wind” Package . 39
8 The Elaborated Data Publication model . 41
8.1 Overview of the Elaborated Data Publication model . 41
8.2 The “ElaboratedDataPublication” Package . 41
8.3 The “ElaboratedData” Package . 43
8.4 The “Validity” Package . 45
8.5 The “BasicData” Package . 45
Annex A (normative) Data Dictionary. 46
A.2 Data Dictionary for “Measurement Site Table Publication” . 47
A.3 Data Dictionary of < < datatypes > > for “Measurement Site Table Publication” . 49
A.4 Data Dictionary of < < enumerations > > for “Measurement Site Table Publication” . 49
A.5 Data Dictionary for “Measured Data Publication” . 51
A.6 Data Dictionary of < < datatypes > > for “Measured Data Publication” . 66
A.7 Data Dictionary of < < enumerations > > for “Measured Data Publication” . 66
A.8 Data Dictionary for “Elaborated Data Publication” . 71
A.9 Data Dictionary of < < datatypes > > for “Elaborated Data Publication” . 74
Annex B (normative) Referenced XML Schema for “MeasurementSiteTablePublication” . 75
B.1 Overview . 75
B.2 Schema . 75
Annex C (normative) Referenced XML Schema for “MeasuredDataPublication” . 88
C.1 Overview . 88
C.2 Schema . 88
Annex D (normative) Referenced XML Schema for “ElaboratedDataPublication” . 118
D.1 Overview . 118
D.2 Schema . 118
Annex E (informative) Examples of Measurement Site Table Publications, Measured Data

Publications and Elaborated Data Publications in XML . 151
E.1 Example of Measurement Site Table Publication . 151
E.2 Example of Measured Data Publication . 154
E.3 Example of Elaborated Data Publication . 159
Bibliography . 161

Foreword
This document (CEN/TS 16157-5:2014) 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.
The CEN/TS 16157 series consists of the following parts, under the general title “Intelligent transport systems
— DATEX II data exchange specifications for traffic management and information”:
- Part 1: Context and framework
- Part 2: Location referencing
- Part 3: Situation publication
- Part 4: VMS publication
- Part 5: Measured and Elaborated Data Publications
Other parts may be developed in the future.
As a user of the standard, attention is drawn to the resources of www.datex2.eu < http://www.datex2.eu/ > .
This website contains related software tools and software resources that aid the implementation of the
CEN/TS 16157 series DATEX II.
According to the CEN-CENELEC Internal Regulations, the national standards organizations 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, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.

Introduction
This Technical Specification defines a common set of data exchange specifications to support the vision of a
seamless interoperable exchange of traffic and travel information across boundaries, including national,
urban, interurban, road administrations, infrastructure providers and service providers. Standardization in this
context is a vital constituent to ensure that interoperability, reduction of risk, reduction of the cost base and
promotion of open marketplace objectives are achieved that will lead to many social, economic and
community benefits as a result of more informed travellers, network managers and transport operators.
Delivering European Transport Policy in line with the White Paper issued by the European Commission
requires co-ordination of traffic management and the development of seamless pan European services. With
the aim to support sustainable mobility in Europe, the European Commission has been supporting the
development of information exchange mainly between the actors of the road traffic management domain for a
number of years. In the road sector, DATEX II has been long in fruition, with the European Commission being
fundamental to its development through an initial contract and subsequent co-funding through the Euro-
Regional projects. With this standardization of DATEX II there is a real basis for common exchange between
the actors of the traffic and travel information sector.
This Technical Specification includes the framework and context for exchanges, the modelling approach, data
content, data structure and relationships and communications specification.
This Technical Specification supports a methodology that is extensible.
The fifth part of this Technical Specification deals with the one or more publication sub-model(s) within the
DATEX II model that support the exchange of measured and elaborated information. These publications are
intended to support the exchange of information from the organization having the measures and creating
elaborated data to other organizations providing ITS services or onward information exchange. It also includes
the exchange of static information about measurement sites.
The European Committee for Standardization (CEN) draws attention to the fact that it is claimed that
compliance with this document may involve the use of a patent concerning procedures, methods and/or
formats given in this document.
CEN takes no position concerning the evidence, validity and scope of patent rights.
1 Scope
This Technical Specification (CEN/TS 16157-5) specifies and defines component facets supporting the
exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, the data
content, the data structure and relationships and the communications specification.
This Technical Specification is applicable to:
— Traffic and travel information which is of relevance to road networks (non urban and urban);
— Public transport information that is of direct relevance to the use of a road network (e.g. road link via train
or ferry service).
This Technical Specification establishes specifications for data exchange between any two instances of the
following actors:
— Traffic Information Centres (TICs);
— Traffic Control Centres (TCCs);
— Service Providers (SPs).
Use of this Technical Specification may be applicable for use by other actors.
This Technical Specification includes the following types of information content:
— Road traffic event information – planned and unplanned occurrences both on the road network and in the
surrounding environment;
— Operator initiated actions;
— Road traffic measurement data, status data and travel time data;
— Travel information relevant to road users, including weather and environmental information;
— Road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 series specifies the informational structures, relationships, roles, attributes and
associated data types required for publishing measured and elaborated data within the Datex II framework.
This is specified in three submodels, a DATEX II Measurement Site Table Publication submodel, a DATEX II
Measured Data Publication submodel and a DATEX II Elaborated Data Publication submodel.
1.1 Conformance
The platform independent sub-models defined by this Part specify a DATEX II Measurement Site
Table Publication, a DATEX II Measured Data Publication and a DATEX II Elaborated Data Publication except
for those elements that relate to location information which are specified in CEN/TS 16157-2. The DATEX II
platform independent data model these three publication sub-models are a part of which, corresponds to the
Level A model as defined in CEN/TS 16157-1.
Conformance with this Part shall require platform independent models from which platform specific models are
generated to comply with the UML modelling rules defined in CEN/TS 16157-1 and with the following
requirements of the sub-models which are expressed in this Part:
— comply with all stipulated minimum and maximum multiplicity requirements for UML elements and
relationships;
— comply with all definitions, types and ordering;
— employ optional elements as specified;
— comply with all expressed constraints.
It should be noted that conformance of a publication service with all the structural requirements stated above
does not necessarily ensure that the informational content of that service will be semantically comprehensible.
2 Normative references
The following referenced documents are indispensable for the application 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.
CEN/TS 16157-1:2011, Intelligent transport systems - DATEX II data exchange specifications for traffic
management and information - Part 1: Context and framework
CEN/TS 16157-2:2011, Intelligent transport systems - DATEX II data exchange specifications for traffic
management and information - Part 2: Location referencing
CEN/TS 16157-3:2011, Intelligent transport systems - DATEX II data exchange specifications for traffic
management and information - Part 3: Situation Publication
ISO/IEC 19501:2005, Information technology — Open Distributed Processing — Unified Modeling Language
(UML) Version 1.4.2
3 Terms and definitions
For the purposes of this document, the terms and definitions given in CEN/TS 16157-1, CEN/TS 16157-2,
CEN/TS 16157-3 and in the following list shall apply.
3.1
elaborated data
data which is derived/computed from one or more measurements over a period of time
Note 1 to entry: It may be a current value or a forecast value predicted from historical measurements.
3.2
measured data
quantitative data measured against a quantified scale (possibly using standard units of measure)
Note 1 to entry: In comparison to Elaborated Data, measured data can be considered to represent presentation of
more directly observed measurements
3.3
measurement
collection of quantitative data
Note 1 to entry: A measurement is made by comparing a quantity with a standard unit. Since this comparison cannot
be perfect, measurements inherently include error.
3.4
measurement site
location from where a stream of measured data may be derived
Note 1 to entry: It can be a point, a linear road section or an area. Linear sections may even be specified as itineraries
or predefined location sets, e.g. for travel time routes which comprise one or more different roads.
3.5
Site Measurements
A measurement data set derived from a specific measurement site
4 Symbols and abbreviated terms
For the purposes of this document, the abbreviation of terms given in CEN/TS 16157-1, CEN/TS 16157-2,
CEN/TS 16157-3 and in the following list shall apply.
PCU Passenger Car Unit
5 UML notation
The UML notation used in these Technical Specifications shall be as described in ISO/IEC 19501. A short
summary explaining the notation used in this part of the CEN/TS 16157 series is provided in Annex A of
CEN/TS 16157-1.
6 The Measurement Site Table Publication model
6.1 Overview of the Measurement Site Table Publication model
The Measurement Site Table Publication model comprises a top-level package,
“MeasurementSiteTablePublication” which utilizes some classes from the “ReusableClasses” package and the
“GroupOfLocations” package. This package is one of a number which are immediately subordinate to the
“PayloadPublication” package and hence forms the top of the hierarchy in the Measurement Site
Table Publication sub-model.
The “MeasurementSiteTablePublication” package models Measurement Site Tables comprising a number of
sets of data, each describing the location from where a stream of measured data may be derived. Each
location is known as a “measurement site” which can be a point, a linear road section or an area.
Each “MeasurementSiteTablePublication” instance shall contain one or more instances of a
“MeasurementSiteTable”, each table containing a number of “MeasurementSiteRecords”. Each
“MeasurementSiteRecord” shall be described by a location and specific characteristics.
Each “MeasurementSite” instance contains zero or more “Measurements” that have different characteristics
like e.g. traffic flow, speed,…
6.2 The “MeasurementSiteTablePublication” Package
6.2.1 Overview of the “MeasurementSiteTablePublication” Package
The “MeasurementSiteTablePublication” package shall comprise a sub-model for defining publishable
measurement site tables which comprise records defining the measurement sites (see Figure 1). Each
publication may contain one or more tables, allowing logical partitioning of measurement sites information as
deemed most appropriate for recipients of measured data information by the supplier (e.g. by road designation
or other geographic criteria or by type of measurement site, etc.)
Figure 1 — The “MeasurementSiteTablePublication” package class model
6.2.2 Semantics of the “MeasurementSiteTablePublication” Package
6.2.2.1 “MeasurementSiteTablePublication” package semantics - general
The “MeasurementSiteTablePublication” class is a specific realizable case of a “PayloadPublication”. Each “MeasurementSiteTablePublication” may
contain any number of separate measurement site tables.
6.2.2.2 “MeasurementSiteTablePublication” Class
The “MeasurementSiteTablePublication” class is the base class for containing the published measurement site tables.
6.2.2.3 “HeaderInformation” Class
Each instance of a “MeasurementSiteTablePublication” shall have associated metadata contained in an instance of the “HeaderInformation” class which
allows the supplier of the “MeasurementSiteTablePublication” to specify how the recipient should treat the information contained in it. This class is already
defined in CEN/TS 16157-3.
6.2.2.4 “MeasurementSiteTable” Class
An identifiable versioned instance of the “MeasurementSiteTable” class shall contain any logical collection of “MeasurementSiteRecords”.
6.2.2.5 “MeasurementSiteRecord” Class
An identifiable versioned instance of the “MeasurementSiteRecord” class shall contain the characteristics information relating to a specific Measurement
Site.
Each record shall be located by a “GroupOfLocations” class. This class belongs to the “GroupOfLocations” package already described in CEN/TS 16157-2.
Each record shall have one indexed “MeasurementSpecificCharacteristics” sub-record for containing the characteristics of each individual measure. The
index provides the means for a measured value (in the MeasuredDataPublication) to be referenced to the relevant MeasurementSpecificCharacteristics at
the measurement site. Each measure can concern specific vehicles which are described by a “VehicleCharacteristics” class.
6.2.2.6 “MeasurementSpecificCharacteristics” Class
An instance of the “MeasurementSpecificCharacteristics” class contains characteristics which are specific to an individual measurement type (specified in a
known order) at the given measurement site.
6.2.2.7 “VehicleCharacteristics” Class
The characteristics of a vehicle, e.g. lorry of gross weight greater than 30 tonnes.
The “VehicleCharacteristics” class is defined in the “VehicleCharacteristics” package which is already described in CEN/TS 16157-3.
7 The Measured Data Publication model
7.1 Overview of the Measured Data Publication model
The Measured Data Publication model shall comprise a top-level package, “MeasuredDataPublication” and one sub-package “BasicData” from the
“ReusableClasses” package. The “MeasuredDataPublication” top-level package shall be one of a number which shall be immediately subordinate to the
“PayloadPublication” package and hence shall form the top of the hierarchy in the Measured Data Publication model.
7.2 The “MeasuredDataPublication” Package
7.2.1 Overview of the “MeasuredDataPublication” Package
The “MeasuredDataPublication” package shall comprise the sub-model for defining a publication containing one or more measurement data sets, each set
being composed of a number of measure values measured at a single measurement site.
Figure 2 — The “MeasuredDataPublication” package class model
7.2.2 Semantics of the “MeasuredDataPublication” Package
7.2.2.1 “MeasuredDataPublication” package semantics - general
The “MeasuredDataPublication” class shall be the only entry point of the package and shall be a specific realizable case of a “PayloadPublication”. Each
“MeasuredDataPublication” shall contain one or more measurement data sets, each set being measured at a single measurement site.
7.2.2.2 “MeasuredDataPublication” Class
The “MeasuredDataPublication” class shall be the base class for containing the published measured data.
7.2.2.3 “HeaderInformation” Class
Each instance of a “MeasuredDataPublication” shall have associated metadata contained in an instance of the “HeaderInformation” class which shall allow
the supplier of the publication to specify how the recipient of the “MeasuredDataPublication” should treat the information contained in it. This class is
already defined in CEN/TS 16157-3.
7.2.2.4 “SiteMeasurements” Class
The “SiteMeasurements” class shall contain a measurement data set derived from a specific measurement site.
Each measurement site, at a given time, has an indexed “MeasurementValue”. The “index” qualifier provides a reference to the specific
MeasurementCharacteristics that are relevant for the MeasuredValue at the referenced measurement site.
7.2.2.5 “MeasuredValue” Class
The “MeasuredValue” class contains optional characteristics for the specific measured value (indexed to correspond with the defined characteristics of the
measurement at the referenced measurement site) which override the static characteristics defined in the MeasurementSiteTable.
7.2.2.6 “LocationCharacteristicsOverride” Class
The “LocationCharacteristicsOverride” class may contain location characteristics which override values set in the referenced measurement point.
7.2.2.7 “MeasurementEquipmentFault” Class
The “MeasurementEquipmentFault” class contains details of a fault which is being reported for the related measurement equipment.
7.2.2.8 “BasicData” Class
The “BasicData” class contains generic data that is either measured or calculated (elaborated) at the same time or over the same time period. These values
are expressed using basic classes included in the DataValue package which is already defined in CEN/TS 16157-3.
7.3 The “BasicData” Package
7.3.1 Overview of the “BasicData” Package
This package describes data that is either measured or calculated (elaborated).
Basic Data values are of one of the following types:
— traffic status;
— travel time data;
— traffic data;
— weather data.
Figure 3 — The “BasicData” package class model
7.3.2 Semantics of the “BasicData” Package
7.3.2.1 “BasicData” package semantics – general
The “BasicData” class is an abstract class i.e. shall be specialized in one of the possible type given above. Each Basic Data value may have a pertinent
location, which is a location or a group of locations (e.g. a stretch of road or an area) relevant for the data value(s). This may be different from the location
of the measurement equipment (i.e. the measurement site location).
Each basic data type is described in a specific package.
7.3.2.2 “BasicData” Class
It is an abstract class. Generic data that is either measured or calculated (elaborated) at the same time or over the same time period.
7.3.2.3 “GroupOfLocations” class
The package is defined in reference document “CEN/TS 16157-2 (Part 2: Location referencing)”.
The “GroupOfLocations” class contains the location (e.g. the stretch of road or area) to which the data value(s) is or are pertinent/relevant. Generally, this
group of locations is identified by reference.
7.4 The “TrafficStatus” Package
7.4.1 Overview of the “TrafficStatus” Package
Derived/computed traffic status information.
Figure 4 — The “TrafficStatus” package class model
7.4.2 Semantics of the “TrafficStatus” Package
7.4.2.1 “TrafficStatus” package semantics – general
The “TrafficStatus” class can be associated with a “TrafficStatusValue” class if the value differs from the reference value given for the publication.
7.4.2.2 “TrafficStatus” Class
The status of traffic conditions on a specific section or at a specific point on the road network.
7.4.2.3 “TrafficStatusValue” Class
This class is already defined in CEN/TS 16157-3.
7.5 The “TravelTimeData” Package
7.5.1 Overview of the “TravelTimeData” Package
Measured or derived travel time information relating to a defined linear stretch of the road network.

Figure 5 — The “TravelTimeData” package class model
7.5.2 Semantics of the “TravelTimeData” Package
7.5.2.1 “TravelTimeData” package semantics – general
The “TravelTimeData” class may be associated with the “DurationValue” class through three possible relationships:
— travel time (in seconds);
— free flow travel time;
— normally expected travel time;
— as well as with a “SpeedValue” class through the Free flow speed relationship.
7.5.2.2 “TravelTimeData” Class
Derived/computed travel time information relating to a linear section of the road network.
7.6 The “TrafficData” Package
7.6.1 Overview of the “TrafficData” Package
This package represents a collection of information associated with measured or derived values relating to vehicle movements at a specified location.
Traffic data are usually sent as Measured Data, but can also be sent as Elaborated Data.
Traffic values can be classified on the basis of vehicle characteristics.
There are 5 kinds of traffic values:
— traffic headway;
— traffic flow;
— traffic speed;
— traffic concentration;
— individual vehicle measurements (not applicable for elaborated data).
Figure 6 — The “TrafficData” package class model
7.6.2 Semantics of the “TrafficData” Package
7.6.2.1 “TrafficData” package semantics – general
The “TrafficData” abstract class shall be the only entry point of the package.
The “VehicleCharacteristics” class from “VehicleCharacteristics” package within “ReusableClasses” is used to define the vehicle characteristics to which the
TrafficData are applicable, primarily in Elaborated Data Publications, but may also be used in Measured Data Publications to override vehicle
characteristics defined for the measurement site.
Each kind of traffic value is defined in a specific package.
7.6.2.2 “TrafficData” Class
It is an abstract class without any attribute.
7.6.2.3 “VehicleCharacteristics” Class
The characteristics of a vehicle, e.g. lorry of gross weight greater than 30 tonnes.
The “VehicleCharacteristics” class is the entry class of the “VehicleCharacteristics” package which is already described in CEN/TS 16157-3.
7.7 The “TrafficHeadway” Package
7.7.1 Overview of the “TrafficHeadway” Package
Averaged measurements or calculations of traffic headway, i.e. the distance or time interval between vehicles (measured between the front of a vehicle and
the front of the vehicle immediately following it). The headway can be expressed as an average distance or an average time.
Figure 7 — The “TrafficHeadway” package class model
7.7.2 Semantics of the “TrafficHeadway” Package
7.7.2.1 “TrafficHeadway” package semantics – general
Each type of headway (i.e. in terms of distance or time) shall be associated with a separate class.
7.7.2.2 “TrafficHeadway” Class
Averaged measurements or calculations of traffic headway, i.e. the distance or time interval between vehicles.
7.8 The “TrafficFlow” Package
7.8.1 Overview of the “TrafficFlow” Package
Averaged measurements of traffic flow rates. They can be expressed in four different ways:
— axle flow;
— PCU flow;
— percentage value;
— vehicle flow.
Figure 8 — The “TrafficFlow” package class model
7.8.2 Semantics of the “TrafficFlow” Package
7.8.2.1 “TrafficFlow” package semantics – general
The “TrafficFlow” class may be accompanied with the possible kind of flow which is expressed with one specific class.
7.8.2.2 “TrafficFlow” Class
The generic class of the package.
7.8.2.3 “AxleFlowValue” Class
This class is already defined in CEN/TS 16157-3.
7.8.2.4 “PcuFlowValue” Class
This class is already defined in CEN/TS 16157-3.
7.8.2.5 “VehicleFlowValue” Class
This class is already defined CEN/TS 16157-3.
7.9 The “TrafficSpeed” Package
7.9.1 Overview of the “TrafficSpeed” Package
Averaged measurements or calculations of traffic speed.
Figure 9 — The “TrafficSpeed” package class model
7.9.2 Semantics of the “TrafficSpeed” Package
7.9.2.1 “TrafficSpeed” package semantics – general
Averaged measurements or calculations of traffic speed.
7.9.2.2 “SpeedPercentile” Class
Details of percentage (from an observation set) of vehicles whose speeds fall below a stated value. The speed value and the percentage value shall both
be given.
7.10 The “TrafficConcentration” Package
7.10.1 Overview of the “TrafficConcentration” Package
Averaged measurements or calculations of traffic concentration. The concentration is expressed with a number of vehicles per kilometre or with a
percentage.
Figure 10 — The “TrafficConcentration” package class model
7.10.2 Semantics of the “TrafficConcentration” Package
7.10.2.1 “TrafficConcentration” package semantics – general
The “TrafficConcentration” class provides averaged measurements or calculations of traffic concentration. This class has no specific attribute. Each kind of
concentration value (in vehicles per kilometre or percentage) is provided in a separate class.
7.10.2.2 “ConcentrationOfVehiclesValue” Class
This class is already defined in CEN/TS 16157-3.
7.11 The “IndividualDataValues” Package
7.11.1 Overview of the “IndividualDataValues” Package
Measured or calculated data values relating to individual vehicles derived from detectors at the specified measurement site.
There are four different kinds of values:
— date times;
— speeds;
— durations;
— distances.
Nine values can be given:
— individual vehicle speed;
— arrival time;
— exit time;
— passage duration time;
— presence duration time;
— time gap;
— time headway;
— distance gap;
— distance headway.
Figure 11 — The “IndividualVehicleDataValues” package class model
7.11.2 Semantics of the “IndividualDataValues” Package
7.11.2.1 “IndividualDataValues” package semantics – general
The “IndividualDataValues” class shall be the only entry point of the package. Each value is expressed with a class depending on its type.
7.11.2.2 “IndividualDataValues” Class
Measured or calculated data values relating to individual vehicles derived from detectors at the specified measurement site.
7.12 The “WeatherData” Package
7.12.1 Overview of the “WeatherData” Package
This package contains measured or derived values relating to the weather at a specific location or locations.
There are 7 types of weather values:
— humidity information;
— visibility information;
— pollution information;
— precipitation information;
— road surface condition information;
— temperature information;
— wind information.
NOTE However the following point is of note for its use in the Elaborated Data publication: Traffic values and weather values are normally provided as Measured data,
but may be provided as Elaborated data if appropriate (e.g. because values are provided by calculation).
Figure 12 — The “WeatherData” package class model
7.12.2 Semantics of the “WeatherData” Package
7.12.2.1 “WeatherData” package semantics – general
The “WeatherData” abstract class shall be the only entry point of the package. Each type of weather value is expressed with a specific class being part of a
specific package within “WeatherRelated” package within “ReusableClasses” package:
— “Humidity” package
— “Visibility” package
— “Pollution” package
— “PrecipitationDetail” package
— “RoadsurfaceConditionMeasurementsDetail” package
— “Temperature” package
— “Wind” package
7.12.2.2 “WeatherData” Class
It is an abstract class for measured or derived values relating to the weather at a specific location or locations.
7.12.2.3 “HumidityInformation” Class
Measurements of atmospheric humidity.
7.12.2.4 “VisibilityInformation” Class
Measurements of atmospheric visibility.
7.12.2.5 “PolutionInformation” Class
Measurements of atmospheric pollution.
7.12.2.6 “PrecipitationInformation” Class
Measurements of precipitation.
7.12.2.7 “RoadSurfaceConditionInformation” Class
Measurements of road surface conditions which are related to the weather.
7.12.2.8 “TemperatureInformation” Class
Measurements of atmospheric temperature.
7.12.2.9 “WindInformation” Class
Measurements of wind conditions.
7.13 The “Humidity” Package
7.13.1 Overview of the “Humidity” Package
Humidity is a relative humidity expressed with a percentage value.

Figure 13 — The “Humidity” package class model
7.13.2 Semantics of the “Humidity” Package
7.13.2.1 “Humidity” package semantics – general
Humidity is a relative humidity expressed with a “PercentageValue” class from “DataValue” package within “ReusableClasses” package.
7.13.2.2 “Humidity” Class
Details of atmospheric humidity
7.14 The “Visibility” Package
7.14.1 Overview of the “Visibility” Package
Visibility is a minimum visibility distance expressed in metres.

Figure 14 — The “Visibility” package class model
7.14.2 Semantics of the “Visibility” Package
7.14.2.1 “Visibility” package semantics – general
VIsibility is a minimum visibility distance expressed with an “IntegerMetreDistanceValue” class from “DataValue” package within “ReusableClasses”
package.
7.14.2.2 “Visibility” Class
Details of atmospheric visibility.
7.15 The “Pollution” Package
7.15.1 Overview of the “Pollution” Package
Details of atmospheric pollution.

Figure 15 — The “Pollution” package class model
7.15.2 Semantics of the “Pollution” Package
7.15.2.1 “Pollution” package semantics – general
The pollutant type shall be given in the “Pollution” class. The pollutant concentration may be given in a separate class.
7.15.2.2 “Pollution” Class
Contains the pollutant type.
7.16 The “PrecipitationDetail” Package
7.16.1 Overview of the “Pr
...