image

image INSPIRE Infrastructure for Spatial Information in Europe

D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines

Title

D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines

Creator

Temporary MIWP 2021-2024 sub-group 2.3.1

Date of publication

2024-01-31

Subject

INSPIRE Data Specification for the spatial data theme Transport Networks

Publisher

INSPIRE Maintenance and Implementation Group (MIG)

Type

Text

Description

This document describes the INSPIRE Data Specification for the spatial data theme Transport Networks

Format

AsciiDoc

Licence

Creative Commons Attribution (cc-by) 4.0

Rights

Public

Identifier

D2.8.I.7_v3.3.0

Changelog

https://github.com/INSPIRE-MIF/technical-guidelines/releases/tag/v2024.1

Language

en

Relation

Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE)

Foreword

How to read the document?

This document describes the "INSPIRE data specification on Transport Networks – Technical Guidelines" version 3.2rc1 as developed by the Thematic Working Group (TWG) Transport Networks using both natural and a conceptual schema language.

The data specification is based on a common template[1] used for all data specifications, which has been harmonised using the experience from the development of the Annex I, II and III data specifications.

This document provides guidelines for the implementation of the provisions laid down in the Implementing Rule for spatial data sets and services of the INSPIRE Directive. It also includes additional requirements and recommendations that, although not included in the Implementing Rule, are relevant to guarantee or to increase data interoperability.

Two executive summaries provide a quick overview of the INSPIRE data specification process in general, and the content of the data specification on Transport Networks in particular. We highly recommend that managers, decision makers, and all those new to the INSPIRE process and/or information modelling should read these executive summaries first.

The UML diagrams (in Chapter 5) offer a rapid way to see the main elements of the specifications and their relationships. The definition of the spatial object types, attributes, and relationships are included in the Feature Catalogue (also in Chapter 5). People having thematic expertise but not familiar with UML can fully understand the content of the data model focusing on the Feature Catalogue. Users might also find the Feature Catalogue especially useful to check if it contains the data necessary for the applications that they run. The technical details are expected to be of prime interest to those organisations that are responsible for implementing INSPIRE within the field of Transport Networks, but also to other stakeholders and users of the spatial data infrastructure.

The technical provisions and the underlying concepts are often illustrated by examples. Smaller examples are within the text of the specification, while longer explanatory examples and descriptions of selected use cases are attached in the annexes.

In order to distinguish the INSPIRE spatial data themes from the spatial object types, the INSPIRE spatial data themes are written in italics.

The document will be publicly available as a 'non-paper'. It does not represent an official position of the European Commission, and as such cannot be invoked in the context of legal procedures.

Legal Notice

Neither the European Commission nor any person acting on behalf of the Commission is responsible for the use which might be made of this publication.

Interoperability of Spatial Data Sets and Services – General Executive Summary

The challenges regarding the lack of availability, quality, organisation, accessibility, and sharing of spatial information are common to a large number of policies and activities and are experienced across the various levels of public authority in Europe. In order to solve these problems it is necessary to take measures of coordination between the users and providers of spatial information. The Directive 2007/2/EC of the European Parliament and of the Council adopted on 14 March 2007 aims at establishing an Infrastructure for Spatial Information in the European Community (INSPIRE) for environmental policies, or policies and activities that have an impact on the environment.

INSPIRE is based on the infrastructures for spatial information that are created and maintained by the Member States. To support the establishment of a European infrastructure, Implementing Rules addressing the following components of the infrastructure have been specified: metadata, interoperability of spatial data sets (as described in Annexes I, II, III of the Directive) and spatial data services, network services, data and service sharing, and monitoring and reporting procedures.

INSPIRE does not require collection of new data. However, after the period specified in the Directive[2] Member States have to make their data available according to the Implementing Rules.

Interoperability in INSPIRE means the possibility to combine spatial data and services from different sources across the European Community in a consistent way without involving specific efforts of humans or machines. It is important to note that "interoperability" is understood as providing access to spatial data sets through network services, typically via Internet. Interoperability may be achieved by either changing (harmonising) and storing existing data sets or transforming them via services for publication in the INSPIRE infrastructure. It is expected that users will spend less time and efforts on understanding and integrating data when they build their applications based on data delivered in accordance with INSPIRE.

In order to benefit from the endeavours of international standardisation bodies and organisations established under international law their standards and technical means have been utilised and referenced, whenever possible.

To facilitate the implementation of INSPIRE, it is important that all stakeholders have the opportunity to participate in specification and development. For this reason, the Commission has put in place a consensus building process involving data users, and providers together with representatives of industry, research and government. These stakeholders, organised through Spatial Data Interest Communities (SDIC) and Legally Mandated Organisations (LMO)[3], have provided reference materials, participated in the user requirement and technical[4] surveys, proposed experts for the Data Specification Drafting Team[5], the Thematic Working Groups[6] and other ad-hoc cross-thematic technical groups and participated in the public stakeholder consultations on draft versions of the data specifications. These consultations covered expert reviews as well as feasibility and fitness-for-purpose testing of the data specifications[7].

This open and participatory approach was successfully used during the development of the data specifications on Annex I, II and III data themes as well as during the preparation of the Implementing Rule on Interoperability of Spatial Data Sets and Services[8] for Annex I spatial data themes and of its amendment regarding the themes of Annex II and III.

The development framework elaborated by the Data Specification Drafting Team aims at keeping the data specifications of the different themes coherent. It summarises the methodology to be used for the development of the data specifications, providing a coherent set of requirements and recommendations to achieve interoperability. The pillars of the framework are the following technical documents[9]:

The structure of the data specifications is based on the "ISO 19131 Geographic information - Data product specifications" standard. They include the technical documentation of the application schema, the spatial object types with their properties, and other specifics of the spatial data themes using natural language as well as a formal conceptual schema language[10].

A consolidated model repository, feature concept dictionary, and glossary are being maintained to support the consistent specification development and potential further reuse of specification elements. The consolidated model consists of the harmonised models of the relevant standards from the ISO 19100 series, the INSPIRE Generic Conceptual Model, and the application schemas[11] developed for each spatial data theme. The multilingual INSPIRE Feature Concept Dictionary contains the definition and description of the INSPIRE themes together with the definition of the spatial object types present in the specification. The INSPIRE Glossary defines all the terms (beyond the spatial object types) necessary for understanding the INSPIRE documentation including the terminology of other components (metadata, network services, data sharing, and monitoring).

By listing a number of requirements and making the necessary recommendations, the data specifications enable full system interoperability across the Member States, within the scope of the application areas targeted by the Directive. The data specifications (in their version 3.0) are published as technical guidelines and provide the basis for the content of the Implementing Rule on Interoperability of Spatial Data Sets and Services[12]. The content of the Implementing Rule is extracted from the data specifications, considering short- and medium-term feasibility as well as cost-benefit considerations. The requirements included in the Implementing Rule are legally binding for the Member States according to the timeline specified in the INSPIRE Directive.

In addition to providing a basis for the interoperability of spatial data in INSPIRE, the data specification development framework and the thematic data specifications can be reused in other environments at local, regional, national and global level contributing to improvements in the coherence and interoperability of data in spatial data infrastructures.

Transport Networks – Executive Summary

Purpose

INSPIRE Directive (2007/2/EC, 14.03.2007) defines the spatial data theme ("theme") Transport Networks as: "Road, rail, air and water transport networks and related infrastructure. Includes links between different networks. Also includes the trans-European transport network as defined in Decision 1692/96/EC of the European Parliament and of the Council of 23 July 1996 on Community guidelines for the development of the trans-European transport network ([13]) and future revisions of that Decision."

This version (3.2) of the data specification on Transport networks provides:

The data specification has been prepared by the INSPIRE Thematic Working Group Transport Networks (TWG-TN), a multinational team of experts in the field drawn from different parts of the European Union ([multiblock footnote omitted]), in the frame of the common and transparent development process.

This version of the INSPIRE data specification for Transport networks has been compiled from reference material submitted by the Spatial Data Interest Communities (SDICs) and Legally Mandated Organisation (LMOs) of INSPIRE, plus the responses to the User Requirements Survey and a set of agreed use cases - some of which have been specifically prepared by the TWG-TN based on their knowledge and experience, like environmental impact assessment, noise mapping, speed limits (related to the in-car information systems) and journey planning.

A large amount of submitted reference material was available for the road networks, largely from the mapping agencies and less input from road authorities. For the other sub-themes Rail, Water and Air transport networks the TWG-TN has had to undertake additional research, building on existing material and documentation. Research has included supporting material regarding trans-European networks and the objects required to support them, such as TEN-T, as well as other initiatives for example: specific documentation from Eurocontrol for air documentation.

Scope and description

The transport component should comprise of an integrated transport network, and related features, that are seamless within each national border. In accordance with Article 10(2) of the INSPIRE Directive, national transport networks may also be seamless at European level, i.e. connected at national borders. Transportation data includes topographic features that are related to transport by road, rail, water, and air. It is important that the features form networks where appropriate, and that links between different networks are established, i.e. multi-modal nodes, especially at the local level, in order to satisfy the requirements for intelligent transport systems such as location based services (LBS) and telematics. The transport network should also support the referencing of transport flows to enable the navigation services.

The data specification is extensive, covering major transport networks types that are defined in the five distinct transport themes (sub-themes): Road, Rail, Water, Air transport and Cableways[14], including the connections between those types. The sub-themes are defined in a way that they can be used together to support an integrated approach to transport and they may be used with other spatial data themes. It is evident that there are a very large number of applications that can potentially use the Transport networks.

Taking into account the variety of responsibilities in collecting, managing and using the data and different approaches in the data base management practice, from simple models to complex data arrangements, this data specification is provided as basic framework and with the purpose to maximize the reuse and sharing of the data about a network. It is mainly focused on the "widely reused – widely referenced" segments of spatial objects, supporting the loose linkage between the diverse organizational data with these spatial objects and allowing the extensibility to fit into div erse applications and users needs.

This approach provides a framework for users to configure and associate their own information (from surface condition surveys, to journey planning, to trans-European transport policy making etc.) using existing transport networks information in each Member State.

The datasets in scope are used extensively at the "local level" and extended to regional, national and European levels. This data specification provides a coherent approach to the forms of the representation (physical topographic area objects or centreline representations) and consistency between data sets, the latest as different types of coherence (between spatial objects of the same theme at different levels of detail, between different spatial objects within a same area or coherence at state boundaries).

All the spatial data sub-themes are based on the INSPIRE Generic Conceptual Model (GCM)([multiblock footnote omitted]) that relies on several ISO 19100([15]) series of geographic information standards to provide the foundations for specific aspects of interoperability.

Within the GCM, the Generic Network Model (GNM)([16]) is defined to be shared by any network spatial data theme (e.g. Hydrography) to ensure a consistent approach across all network themes.

Specific mechanisms, used in the data specification and defined in the GNM, include:

The elements in the network are handled as nodes, links, aggregated links, areas and points. In addition, the individual transport links can be combined to form transport link sequences or further – the combination of both can be used to form the transport link sets.

The data specification includes three types of geometry: (a) (topographic) area objects, (b) centreline objects and (c) point objects. The types (a) and (b) may be alternative representations of the same real world phenomena about which the user can associate their own information (objects). The type (c) is, apart from network nodes, only included in the specification for marker posts. The basic spatial representation type is 2D vector.

Topology is handled in the data specification implicitly rather than explicitly, with the main reason to keep the model simple as possible but expecting that most applications will use the network data within a topological environment.There is therefore a prerequisite for "implicit topology", where the data provided must be sufficiently clean and capable of automated topological construction within a user’s application. This concept is framed with the specific requirements, including the data quality information.

There are relationships with other spatial data themes, in particular with:

Next steps in the development

It is intended that this data specification will be maintained in accordance with the future development of the INSPIRE data specification framework documents, new identified user requirements or policy requirements, development of the standards (used as a basis for data specification) and based on the best practices and on the input from the implementation of the INSPIRE Implementing Rules.

The data specification – guidelines will be are published on INSPIRE web site([18]).

Acknowledgements

Many individuals and organisations have contributed to the development of these Guidelines.

The Thematic Working Group Transport Networks (TWG-TN) included:

Keith Murray (TWG Facilitator), Jordi Escriu Paradell (TWG Co-editor), Ward Verlinden (TWG Co-editor), Lars Wikström (TWG Co-editor), Alain Chaumet, Mark Lepage, Dave Russell, Ulf Sandgren, Darja Lihteneger (European Commission contact point).

Other contributors to the INSPIRE data specifications are the Drafting Team Data Specifications, the JRC Data Specifications Team and the INSPIRE stakeholders - Spatial Data Interested Communities (SDICs) and Legally Mandated Organisations (LMOs).

Contact information

Maria Vanda Nunes de Lima & Michael Lutz
European Commission Joint Research Centre (JRC)
Institute for Environment and Sustainability
Unit H06: Digital Earth and Reference Data
http://inspire.ec.europa.eu/index.cfm/pageid/2

Table of Contents

1. Scope

This document specifies a harmonised data specification for the spatial data theme Transport Networks as defined in Annex I of the INSPIRE Directive.

This data specification provides the basis for the drafting of Implementing Rules according to Article 7 (1) of the INSPIRE Directive [Directive 2007/2/EC]. The entire data specification is published as implementation guidelines accompanying these Implementing Rules.

2. Overview

2.1. Name

INSPIRE data specification for the theme Transport Networks.

2.2. Informal description

Definition:

The Transport Networks theme is defined within the INSPIRE Directive as:

"Road, rail, air and water transport networks and related infrastructure. Includes links between different networks. Also includes the trans-European transport network as defined in Decision No 1692/96/EC of the European Parliament and of the Council of 23 July 1996 on Community Guidelines for the development of the trans-European transport network (1) and future revisions of that Decision.

  1. OJ L 228, 9.9.1996, p. 1. Decision as last amended by Coun cil Regulation (EC) No 1791/2006 (OJ L 363, 20.12.2006, p. 1)"

[Directive 2007/2/EC]

Description:

It is further described in the INSPIRE Feature Concept Dictionary as follows:

"The transport component should comprise an integrated transport network, and related features, that are seamless within each national border. In accordance with article 10.2 of the Directive, national transport networks may also be seamless at European level, i.e. connected at national borders. Transportation data includes topographic features related to transport by road, rail, water, and air. It is important that the features form networks where appropriate, and that links between different networks are established, i.e. multi-modal nodes, especially at the local level, in order to satisfy the requirements for intelligent transport systems such as location based services (LBS) and telematics. The transport network should also support the referencing of transport flow to enable our navigation services."

[INSPIRE Feature Concept Dictionary]

The INSPIRE Directive sets out the key requirements in the following Articles of the Directive.

"Article 4

  1. This Directive shall cover spatial data sets which fulfil the following conditions:

    1. they relate to an area where a Member State has and/or exercises jurisdictional rights;

    2. they are in electronic format;

    3. they are held by or on behalf of any of the following:

      1. a public authority, having been produced or received by a public authority, or being managed or updated by that authority and falling within the scope of its public tasks;

      2. a third party to whom the network has been made available in accordance with Article 12;

    4. they relate to one or more of the themes listed in Annex I, II or III."

  1. "In cases where multiple identical copies of the same spatial data set are held by or on behalf of various public authorities, this Directive shall apply only to the reference version from which the various copies are derived."

  1. "This Directive does not require collection of new spatial data."

"Article 7

  1. Implementing rules laying down technical arrangements for the interoperability and, where practicable, harmonisation of spatial data sets and services, designed to amend non-essential elements of this Directive by supplementing it, shall be adopted in accordance with the regulatory procedure with scrutiny referred to in Article 22(3). Relevant user requirements, existing initiatives and international standards for the harmonisation of spatial data sets, as well as feasibility and cost-benefit considerations shall be taken into account in the development of the implementing rules."

  1. "Implementing rules referred to in paragraph 1 shall cover the definition and classification of spatial objects relevant to spatial data sets related to the themes listed in Annex I, II or III and the way in which those spatial data are geo-referenced."

"Article 8

  1. In the case of spatial data sets corresponding to one or more of the themes listed in Annex I or II, the implementing rules provided for in Article 7(1) shall meet the conditions laid down in paragraphs 2, 3 and 4 of this Article.

  2. The implementing rules shall address the following aspects of spatial data:

    1. a common framework for the unique identification of spatial objects, to which identifiers under national systems can be mapped in order to ensure interoperability between them;

    2. the relationship between spatial objects;

    3. the key attributes and the corresponding multilingual thesauri commonly required for policies which may have an impact on the environment;

    4. information on the temporal dimension of the data;

    5. updates of the data.

  3. The implementing rules shall be designed to ensure consistency between items of information which refer to the same location or between items of information which refer to the same object represented at different scales.

  4. The implementing rules shall be designed to ensure that information derived from different spatial data sets is comparable as regards the aspects referred to in Article 7(4) and in paragraph 2 of this Article"

To support a consistent approach to all themes the European Commission, through the Data Specifications Drafting Team, developed the "Generic Conceptual Model" [GCM] which was reviewed and published prior to the commencement of work on the Annex I themes. This is the foundation model for every theme – with the intention that any theme may be combined in future and used in a way that is predicable.

The scope of the INSPIRE Transport Networks Data Product Specification incorporates five distinct transport themes:

  • Road transport

  • Rail transport

  • Water transport

  • Air transport

  • Cableways

This is summarised in the diagram below which shows how the Directive guides the Generic Conceptual Model [D2.5] which contains a basic framework for any kind of network model (the Generic Network Model [GNM]). From the GNM a Common Transport application schema is adapted and this then is used as the basis for all five application schema. Collectively these are drawn together in this document as the Transport Networks Data Product Specification [D2.8.1.7].

image

Figure 1 – Document framework for this data product specification [key documents only]

These themes can be used together to support an integrated approach to transport but as noted above - they may be used with other themes developed to the same standard (e.g. response to an emergency where a fuel tanker over turns on a highway and discharges into an adjacent river network). It is evident that there are a very large number of applications that can potentially use the Transport Networks theme.

Understanding of the Generic Conceptual Model is essential and the GCM/GNM should be read in conjunction with this document. The GCM which describes the basic form of real world abstraction through to a comprehensive set of data interoperability. The GNM adapts this and describes the basic concepts that underpin and define the Common Transport Application Schema upon which all five themes are based. The GCM relies on ISO standards and the 19xxx series in particular.

The purpose of this document is to specify a harmonised data specification for the spatial data theme Transport Networks as defined in Annex I of the INSPIRE Directive.

However each organisation will have different responsibilities from the next and this will influence the kind of data they collect and manage and use. In turn some organisations may use simple models; others by necessity will have complex data arrangements. This data specification is provided as basic framework which users can adopt and if required – extend for themselves.

The model is structured to maximise reuse and the sharing of organisational data about a network. The specification is concerned only with the core spatial objects required by Transport Networks (while acknowledging that the boundary of any object grouping is never black and white).

Figure 2 below outlines the scope of the specification and how it relates to associated spatial objects which are less generically used.

image

Figure 2 – Scope of Transport Network data

Spatial Objects (core – application specific)

This specification is mainly focussed on the "widely reused – widely referenced" segment of spatial objects (ie network centrelines etc.). It does not attempt to try and incorporate every spatial object that might be used by any application. In Figure 2 – Scope of Transport Network data above such objects maybe lighting columns, gantries, signals, sensors etc. These are all of the type "application specific "– and will be used/referenced by at least one organisation.

Associated "non-Geographic" data

Any "non geographic data" (the majority of the data holdings in any organisation) – is also out of scope of this specification – such records maybe "an asset condition report", "traffic flow records", "images of assets", "statistics", "timetables", "noise data" and so on. Therefore much of the data used in the telematics industry is classed application specific. While associated with the network all these examples are closer to the application end of the spectrum than generic use by a wide community whether they represent a geographic entity or non-geographic data.

To maximise reuse the linkage of such organisational data with the spatial objects should be "loose" in the sense that these are ideally defined as different data objects in a database. Configured correctly such data may then reused in several different applications and any associated information shared and exchanged as desired.

User defined views and flexibility

The model itself is flexible and will permit a cross organisational approach where different users may collect and use different kinds of information about a network. By referencing they can relate one "view" e.g. a highway name, classification, route, condition survey and so on – simply by using references against a common geographic framework. Methods that will be found within the GNM that support this are the "linkset" and "link sequence". Any third party may further add their own "views", thereby enabling greater reuse and easier exchange of information around a common standard set of information components.

This approach enables several organisations to contribute and easily combine several views of the transport network. For a road example the combinations and contributors might be:

Underlying link and node geometry: mapping agency (national or state level)
Highway name: municipality
National highway classification: national highway authority
European highway classification: European highway authority

Many of these contributors may also collect and maintain application objects and business data which can be linked to the same infrastructure.

Extensibility
Users can extend the schema and add their own spatial objects to support an application. Data architects should use the GCM as the basis for any such extension. To illustrate this a small number of objects that are primarily of an application need (than generic) are included in this specification. Examples of these are:

  • Linear – speed limits in the Roads theme

  • Point – kilometer posts on the Roads and Rail

  • Area* - Port area, Railway station area, etc.

*In practice these areas may be defined by aggregations of some other area object types using objects from other themes e.g. buildings.

Applications and use cases

While INSPIRE is primarily an environmental directive, Transport Networks data enjoys a wide variety of applications as recognised in the footnote to the theme statement in Annex I of the Directive. The following use cases are highlighted to demonstrate the width and breadth of applications (the list is not exhaustive).

  • Asset Management

  • Capacity Planning

  • Construction

  • Design & Planning

  • Disaster management

  • Emergency response

  • Environmental Impact Assessments (incl. Noise)

  • Estate management

  • Flow modelling

  • In car information systems

  • Incident management

  • Journey Planning

  • Maintenance

  • Navigation

  • Network operation

  • Rerouting & diversions

  • Routing

  • Traffic Control

  • Traffic management

The applications in bold above were used as use cases in the preparation of this specification. These represent applications at the European, national, local public sector levels and in the private sector. It is evident that the scope of the specific does not attempt to support all these applications. User extensibility is supported and encouraged. Future revisions may incorporate further object types if it is felt that further standardisation is necessary.

Characteristics of the specification

The key characteristics of the Transport Networks datasets are:

  • They contain information of specific interest for the public sector in its role to support economic growth through efficient transportation, passenger safety, environ­mental impacts and social planning, etc.

  • The information is applicable from local to European levels of operation.

  • The data represents a structure or methods of operation that is stable over time (even if parts of the data content frequently changes).

  • Supports cross border (pan-European) applications.

  • Being a part of the European Spatial Data Infrastructure the data may be more easily used with other kinds of data themes, such as geographical names, administrative units, and addresses etc.

  • Private sector applications are extensive.

Local to European level capability

From the use case list above it is evident that the specification has wide application and at several levels. Many applications would like to move seamlessly from the macro to micro view but this is rarely possible today for many reasons – chiefly today’s datasets were not designed to operate in that way.

Local, Regional, National and European relevance of the specification

The datasets in scope are used extensively at the "local level" and extend to regional, national and European levels. Usage can change with levels of operation or within an organisation. The specification is mainly focussed on establishing a more coherent approach to those datasets that universally used, probably held at national or regional level and at the highest resolution within this context. This section describes the context within this respect.

Area and link types of representation at the higher resolution level

Some applications require a centreline network approach, some require the extent of carriageway or other form of transport, and some applications use both forms of representation. These are alternative forms of representation of a real world entity. The specification therefore supports alternative forms of representation and these may be cross referenced to support easy data exchange between the two. Only the centreline (link) can be formed into network (e.g. using the linkset).

Seamless resolution representations at the local and regional level

In these and other domains lower resolution representations may be preferred e.g. to view traffic flows in a region or capacity of the network. A user may wish to zoom from city level to a specific street seamlessly. Such an approach is recognised in D2.5 and outlined in D2.6. However such data management processes and methodologies remain immature. Ideally the lower resolution datasets would be derived from the local/high resolution data - outlined in the previous paragraph – and referenced (no geographic) data could then be aggregated and disaggregated as desired.

Multiple representations at regional, national and European levels.

Ideally the same data would be scalable dynamically from local to European level seamlessly. Since the current datasets and methods are insufficiently mature to support this - several "levels of detail" will usually be stored to represent the network at different operational levels.

Unfortunately today there is very little correspondence between each level. Ideally it would be easy to seamlessly move from the highest to the lowest resolution with corresponding scaling and aggregation and disaggregation of the associated organisational information (as we do on statistical datasets) e.g. for reporting purposes or trans European analysis, real time management, planning and policy making.

Such a "multiple resolution" approach is discussed in D2.6 Annex A.19 and Annex B.1 of this document. Transport networks lend themselves to such an approach.

In the meantime this specification applies to all levels of detail. Further proving of the approach is required to support truly seamless integration of the levels of detail*. In the meantime data providers are encouraged to introduce this specification at the local level as a priority.

*It is reported that some organisations are currently investigating such an approach but it is not yet formally adopted to such a level to document it in this version of the Transport networks specification (TN specification). This is an area that requires further research to improve both the capability and automation potential.

Overview Structure of the Transport Networks data product specification and commentary on specific issues within the specification

Structure

The structure follows the ISO standard for data specifications (ISO 19xxx). Sections 1-3 are prepared to a defined pattern for all themes. Section 5 contains a combination of the outputs from the UML model (application schemas) for the Common Transport Model and each of the five themes. This is supplemented by a descriptive narrative. Sections 6 – 11 are largely harmonised across all themes with variations that are essential to support aspects of this theme. The Annexes are informative and include the Abstract Test Suite and further background information and examples.

Linear Referencing

Linear referencing is incorporated in the specification. This uses an approach aligned with the ISO 19148:2012; which establishes linear referencing within a spatial environment (rather than a traditional standalone approach). The aim of this is to better support data sharing across referencing mechanisms, and to offer coordinates for any object referenced linearly, in the same national coordinate system.

Logical networks

Logical networks (see Annex B.1) can be used within the model but their spatial value is very limited or in some cases may be non-existent. Therefore caution is required. Where these are in operation alongside the above forms of representation it is suggested that any corresponding nodes are reused or at least cross referenced to provide a relationship between the systems to preserve the potential for data sharing and exchange where that is both relevant and appropriate.

Network Interconnections

There are several cases where networks need to be joined up. For example at national, regional or dataset boundaries and at intermodal points within networks. This is provided by the Network Connection component which is defined in the Generic Network Model.

Relationships with other themes

There are linkages to other themes. In particular:

Hydrography [HY] – the water transport theme reuses the INSPIRE river network model, for inland transportation purposes. To avoid undue interference with the river network - connections link inland ports with the nearest node on the river network. In marine waters the model is influenced by specifications from the International Hydrographic Office [IHO].

Addresses [AD] – the majority of addresses are linked to transport links (roads, some rivers etc) and thoroughfares are not part of the transport network defined in this specifications (e.g. pedestrian ways). However there is no link shown in the TN model – this is more logically made from the address to the transport object to which it is associated. The primary purpose for such a link would be to ensure consistency of geographic highway/thoroughfare name and to support address to address navigation via transport networks.

Source material

The Transport Networks data product specification (TN DPS) has been developed using the reference material, expertise and dialogue with LMO and SDIC. Other material submitted by LMO/SDIC has been supplemented by research to fill in the gaps in evidence. The TN specification is extensive and has therefore been broken into five interoperable transport themes: Road, Rail, Water, Air transport and Cableway networks.

Topology

Topology is handled implicitly rather than explicitly in the entire transport schema. This is to keep the model simple as possible. Generally systems will build topology in a form that best meets the user’s application. It is expected that most applications will use the network data within a topological environment.

There is therefore a prerequisite for "implicit topology". This means that the data provided must be sufficiently clean and capable of automated topological construction within a user’s application. There are therefore specific data capture requirements and these are described in Chapter 7 on Data Quality and in Chapter 10 on Data Capture.

Future Updates of this specification

It is intended that this specification will be maintained in accordance with current proposals outlined by the Data Specifications Drafting Team. It is not possible to state at this time when the next update will occur.

2.3. Normative References

[Directive 2007/2/EC] Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE)

[ISO 19107] EN ISO 19107:2005, Geographic Information – Spatial Schema

[ISO 19113] EN ISO 19113:2005, Geographic Information – Quality principles

[ISO 19115] EN ISO 19115:2005, Geographic information – Metadata (ISO 19115:2003)

[ISO 19118] EN ISO 19118:2006, Geographic information – Encoding (ISO 19118:2005)

[ISO 19125-1] EN ISO 19125-1:2004, Geographic Information – Simple feature access – Part 1: Common architecture

[ISO 19135] EN ISO 19135:2007 Geographic information – Procedures for item registration (ISO 19135:2005)

[ISO 19138] ISO/TS 19138:2006, Geographic Information – Data quality measures

[ISO 19139] ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation

[ISO 19157] ISO/DIS 19157, Geographic information – Data quality

[OGC 06-103r4] Implementation Specification for Geographic Information - Simple feature access – Part 1: Common Architecture v1.2.1

NOTE This is an updated version of "EN ISO 19125-1:2004, Geographic information – Simple feature access – Part 1: Common architecture".

[Regulation 1205/2008/EC] Regulation 1205/2008/EC implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata

ISO/AWI 19148:2012 Geographic information — Location based services — Linear referencing system

Regulation L228, 09/09/1996 Community Guidelines for the development of the trans-European transport network.

Decision No 884/2004/EC OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 29 April 2004 amending Decision No 1692/96/EC on Community guidelines for the development of the

Trans-European transport network

Directive of 27 June 1985 on the assessment of the effects of certain public and private projects on the environment (85/337/EEC) (OJ L 175, 5.7.1985, p. 40)

2.4. Terms and definitions

General terms and definitions helpful for understanding the INSPIRE data specification documents are defined in the INSPIRE Glossary[19].

Specifically, for the theme Transport Networks, the following terms are defined: (delete if no additional terms are defined)

There are no new terms defined in this specification.

2.5. Symbols and abbreviations

AICM/AIXM

Aeronautical Information Exchange

ARP

Airport Reference Point

ATS

ATS Route as described in ICAO Annex 11

ATZ

Airport Traffic Zone

CEDR

Conference of European Directors of Roads

CEMT

European Conference of Ministers of Transport.

CTA

Control Area

CTR

Control Zone

D

Danger Area

DME

Distance Measuring Equipment

Eurocontrol

Eurocontrol is the European Organisation for the Safety of Air Navigation.

EuroRoadS

An EC funded project (2003-2006) with the aim of producing a specification framework to support interoperable road information

FATO

Final Approach and Take Off Area for Helicopters

FIR

Flight Information Region

GCM

Generic Conceptual Model

GDF

Geographic Data Files

GNM

Generic Network Model

IAF

Initial Approach Fix Point

IAP

Instrument Approach Procedure

IATA

International Air Transport Association

ICAO

International Civil Aviation Organization

IFR

Instrument Flight Rules

IHO

International Hydrographic Organization

ILS

Instrument Landing System

ILS-DME

ILS with collocated DME

IMO

International Maritime Organization

ISO

International Organization for Standardization

LOC

Localizer

LOC-DME

LOC and DME collocated

MKR

Marker Beacon

MLS

Microwave Landing System

MLS-DME

MLS with collocated DME

NAT

North Atlantic Track (part of Organized Track System)

NDB

Non-Directional Radio Beacon

NDB-DME

NDB and DME collocated

NDB-MKR

Non-Directional Radio Beacon and Marker Beacon

NVDB

Swedish National Road Database

P

Prohibited Area

R

Restricted Area

RADEF

Road Administration Data Exchange Format

RNAV

Area Navigation Route

S-100

IHO Hydrographic Geospatial Standard for Marine Data and Information

S-32

IHO International Hydrographic Dictionary

SID

Standard Instrument Departure

STAR

Standard Instrument Arrival

TACAN

Tactical Air Navigation Beacon; Tactical Air Navigation Route

TEN-T

Trans-European Network - Transport

TLS

Transponder Landing System

TMA

Terminal Control Area

TN

Transport Networks

TSS

Traffic Separation Scheme

TWG

Thematic Working Group

UIR

Upper Flight Information Region

VFR

Visual Flight Rules

VOR

VHF Omnidirectional Radio Range

VOR-DME

VOR and DME collocated

VORTAC

VOR and TACAN collocated

2.6. How the Technical Guidelines map to the Implementing Rules

The schematic diagram in Figure 3 gives an overview of the relationships between the INSPIRE legal acts (the INSPIRE Directive and Implementing Rules) and the INSPIRE Technical Guidelines. The INSPIRE Directive and Implementing Rules include legally binding requirements that describe, usually on an abstract level, what Member States must implement.

In contrast, the Technical Guidelines define how Member States might implement the requirements included in the INSPIRE Implementing Rules. As such, they may include non-binding technical requirements that must be satisfied if a Member State data provider chooses to conform to the Technical Guidelines. Implementing these Technical Guidelines will maximise the interoperability of INSPIRE spatial data sets.

image

Figure 3 - Relationship between INSPIRE Implementing Rules and Technical Guidelines

2.6.1. Requirements

The purpose of these Technical Guidelines (Data specifications on Transport Networks) is to provide practical guidance for implementation that is guided by, and satisfies, the (legally binding) requirements included for the spatial data theme Transport Networks in the Regulation (Implementing Rules) on interoperability of spatial data sets and services. These requirements are highlighted in this document as follows:

📕

IR Requirement
Article / Annex / Section no.
Title / Heading

This style is used for requirements contained in the Implementing Rules on interoperability of spatial data sets and services (Commission Regulation (EU) No 1089/2010).

For each of these IR requirements, these Technical Guidelines contain additional explanations and examples.

NOTE The Abstract Test Suite (ATS) in Annex A contains conformance tests that directly check conformance with these IR requirements.

Furthermore, these Technical Guidelines may propose a specific technical implementation for satisfying an IR requirement. In such cases, these Technical Guidelines may contain additional technical requirements that need to be met in order to be conformant with the corresponding IR requirement when using this proposed implementation. These technical requirements are highlighted as follows:

📒

TG Requirement X

This style is used for requirements for a specific technical solution proposed in these Technical Guidelines for an IR requirement.

NOTE 1 Conformance of a data set with the TG requirement(s) included in the ATS implies conformance with the corresponding IR requirement(s).

NOTE 2 In addition to the requirements included in the Implementing Rules on interoperability of spatial data sets and services, the INSPIRE Directive includes further legally binding obligations that put additional requirements on data providers. For example, Art. 10(2) requires that Member States shall, where appropriate, decide by mutual consent on the depiction and position of geographical features whose location spans the frontier between two or more Member States. General guidance for how to meet these obligations is provided in the INSPIRE framework documents.

2.6.2. Recommendations

In addition to IR and TG requirements, these Technical Guidelines may also include a number of recommendations for facilitating implementation or for further and coherent development of an interoperable infrastructure.

📘

Recommendation X

Recommendations are shown using this style.

NOTE The implementation of recommendations is not mandatory. Compliance with these Technical Guidelines or the legal obligation does not depend on the fulfilment of the recommendations.

2.6.3. Conformance

Annex A includes the abstract test suite for checking conformance with the requirements included in these Technical Guidelines and the corresponding parts of the Implementing Rules (Commission Regulation (EU) No 1089/2010).

3. Specification scopes

This data specification does not distinguish different specification scopes, but just considers one general scope.

NOTE For more information on specification scopes, see [ISO 19131:2007], clause 8 and Annex D.

4. Identification information

These Technical Guidelines are identified by the following URI:

http://inspire.ec.europa.eu/tg/tn/3.2rc1

NOTE ISO 19131 suggests further identification information to be included in this section, e.g. the title, abstract or spatial representation type. The proposed items are already described in the document metadata, executive summary, overview description (section 2) and descriptions of the application schemas (section 5). In order to avoid redundancy, they are not repeated here.

5. Data content and structure

5.1. Application schemas – Overview

5.1.1. Application schemas included in the IRs

Articles 3, 4 and 5 of the Implementing Rules lay down the requirements for the content and structure of the data sets related to the INSPIRE Annex themes.

📕

IR Requirement
Article 4
Types for the Exchange and Classification of Spatial Objects

  1. For the exchange and classification of spatial objects from data sets meeting the conditions laid down in Article 4 of Directive 2007/2/EC, Member States shall use the spatial object types and associated data types and code lists that are defined in Annexes II, III and IV for the themes the data sets relate to.

  2. When exchanging spatial objects, Member States shall comply with the definitions and constraints set out in the Annexes and provide values for all attributes and association roles set out for the relevant spatial object types and data types in the Annexes. For voidable attributes and association roles for which no value exists, Member States may omit the value.

The types to be used for the exchange and classification of spatial objects from data sets related to the spatial data theme Transport Networks are defined in the following application schemas (see sections 5.3, 5.4, 5.5, 5.6, 5.7, 5.8):

  • Common Transport Elements application schema

  • Air Transport Network application schema

  • Cable Transport Network application schema

  • Railway Transport Network application schema

  • Road Transport Network application schema

  • Water Transport Network application schema

image

Figure 4 – UML class diagram: Overview of the Transport Networks UML structure and dependencies

The dependencies between the different Transport Networks application schemas are illustrated in Figure 4. All five of the Transport Networks (Road, Rail, Cable, Water and Air) application schemas depend on the Common Transport Elements application schema which defines a number of common transport classes. In turn, Common Transport Elements depends on the Generic Network Model on which it is based.

The application schemas specify requirements on the properties of each spatial object including its multiplicity, domain of valid values, constraints, etc.

NOTE The application schemas presented in this section contain some additional information that is not included in the Implementing Rules, in particular multiplicities of attributes and association roles.

📒

TG Requirement 1

Spatial object types and data types shall comply with the multiplicities defined for the attributes and association roles in this section.

An application schema may include references (e.g. in attributes or inheritance relationships) to common types or types defined in other spatial data themes. These types can be found in a sub-section called "Imported Types" at the end of each application schema section. The common types referred to from application schemas included in the IRs are addressed in Article 3.

📕

IR Requirement
Article 3
Common Types

Types that are common to several of the themes listed in Annexes I, II and III to Directive 2007/2/EC shall conform to the definitions and constraints and include the attributes and association roles set out in Annex I.

NOTE Since the IRs contain the types for all INSPIRE spatial data themes in one document, Article 3 does not explicitly refer to types defined in other spatial data themes, but only to types defined in external data models.

Common types are described in detail in the Generic Conceptual Model [DS-D2.7], in the relevant international standards (e.g. of the ISO 19100 series) or in the documents on the common INSPIRE models [DS-D2.10.x]. For detailed descriptions of types defined in other spatial data themes, see the corresponding Data Specification TG document [DS-D2.8.x].

5.2. Basic notions

This section explains some of the basic notions used in the INSPIRE application schemas. These explanations are based on the GCM [DS-D2.5].

5.2.1. Notation

5.2.1.1. Unified Modeling Language (UML)

The application schemas included in this section are specified in UML, version 2.1. The spatial object types, their properties and associated types are shown in UML class diagrams.

NOTE For an overview of the UML notation, see Annex D in [ISO 19103].

The use of a common conceptual schema language (i.e. UML) allows for an automated processing of application schemas and the encoding, querying and updating of data based on the application schema – across different themes and different levels of detail.

The following important rules related to class inheritance and abstract classes are included in the IRs.

📕

IR Requirement
Article 5
Types

(…​)

  1. Types that are a sub-type of another type shall also include all this type’s attributes and association roles.

  2. Abstract types shall not be instantiated.

The use of UML conforms to ISO 19109 8.3 and ISO/TS 19103 with the exception that UML 2.1 instead of ISO/IEC 19501 is being used. The use of UML also conforms to ISO 19136 E.2.1.1.1-E.2.1.1.4.

NOTE ISO/TS 19103 and ISO 19109 specify a profile of UML to be used in conjunction with the ISO 19100 series. This includes in particular a list of stereotypes and basic types to be used in application schemas. ISO 19136 specifies a more restricted UML profile that allows for a direct encoding in XML Schema for data transfer purposes.

To model constraints on the spatial object types and their properties, in particular to express data/data set consistency rules, OCL (Object Constraint Language) is used as described in ISO/TS 19103, whenever possible. In addition, all constraints are described in the feature catalogue in English, too.

NOTE Since "void" is not a concept supported by OCL, OCL constraints cannot include expressions to test whether a value is a void value. Such constraints may only be expressed in natural language.

5.2.1.2. Stereotypes

In the application schemas in this section several stereotypes are used that have been defined as part of a UML profile for use in INSPIRE [DS-D2.5]. These are explained in Table 1 below.

Table 1 – Stereotypes (adapted from [DS-D2.5])

Stereotype Model element Description

applicationSchema

Package

An INSPIRE application schema according to ISO 19109 and the Generic Conceptual Model.

leaf

Package

A package that is not an application schema and contains no packages.

featureType

Class

A spatial object type.

type

Class

A type that is not directly instantiable, but is used as an abstract collection of operation, attribute and relation signatures. This stereotype should usually not be used in INSPIRE application schemas as these are on a different conceptual level than classifiers with this stereotype.

dataType

Class

A structured data type without identity.

union

Class

A structured data type without identity where exactly one of the properties of the type is present in any instance.

codeList

Class

A code list.

import

Dependency

The model elements of the supplier package are imported.

voidable

Attribute, association role

A voidable attribute or association role (see section 5.2.2).

lifeCycleInfo

Attribute, association role

If in an application schema a property is considered to be part of the life-cycle information of a spatial object type, the property shall receive this stereotype.

version

Association role

If in an application schema an association role ends at a spatial object type, this stereotype denotes that the value of the property is meant to be a specific version of the spatial object, not the spatial object in general.

5.2.2. Voidable characteristics

The «voidable» stereotype is used to characterise those properties of a spatial object that may not be present in some spatial data sets, even though they may be present or applicable in the real world. This does not mean that it is optional to provide a value for those properties.

For all properties defined for a spatial object, a value has to be provided – either the corresponding value (if available in the data set maintained by the data provider) or the value of void. A void value shall imply that no corresponding value is contained in the source spatial data set maintained by the data provider or no corresponding value can be derived from existing values at reasonable costs.

📘

Recomendation 1

The reason for a void value should be provided where possible using a listed value from the VoidReasonValue code list to indicate the reason for the missing value.

The VoidReasonValue type is a code list, which includes the following pre-defined values:

  • Unpopulated: The property is not part of the dataset maintained by the data provider. However, the characteristic may exist in the real world. For example when the "elevation of the water body above the sea level" has not been included in a dataset containing lake spatial objects, then the reason for a void value of this property would be 'Unpopulated'. The property receives this value for all spatial objects in the spatial data set.

  • Unknown: The correct value for the specific spatial object is not known to, and not computable by the data provider. However, a correct value may exist. For example when the "elevation of the water body above the sea level" of a certain lake has not been measured, then the reason for a void value of this property would be 'Unknown'. This value is applied only to those spatial objects where the property in question is not known.

  • Withheld: The characteristic may exist, but is confidential and not divulged by the data provider.

NOTE It is possible that additional reasons will be identified in the future, in particular to support reasons / special values in coverage ranges.

The «voidable» stereotype does not give any information on whether or not a characteristic exists in the real world. This is expressed using the multiplicity:

  • If a characteristic may or may not exist in the real world, its minimum cardinality shall be defined as 0. For example, if an Address may or may not have a house number, the multiplicity of the corresponding property shall be 0..1.

  • If at least one value for a certain characteristic exists in the real world, the minimum cardinality shall be defined as 1. For example, if an Administrative Unit always has at least one name, the multiplicity of the corresponding property shall be 1..*.

In both cases, the «voidable» stereotype can be applied. In cases where the minimum multiplicity is 0, the absence of a value indicates that it is known that no value exists, whereas a value of void indicates that it is not known whether a value exists or not.

EXAMPLE If an address does not have a house number, the corresponding Address object should not have any value for the «voidable» attribute house number. If the house number is simply not known or not populated in the data set, the Address object should receive a value of void (with the corresponding void reason) for the house number attribute.

5.2.3. Code lists

Code lists are modelled as classes in the application schemas. Their values, however, are managed outside of the application schema.

5.2.3.1. Code list types

The IRs distinguish the following types of code lists.

📕

IR Requirement
Article 6
Code Lists for Spatial Data Sets

  1. The code lists included in this Regulation set out the multilingual thesauri to be used for the key attributes, in accordance with Article 8(2), point (c), of Directive 2007/2/EC.

  2. The Commission shall establish and operate an INSPIRE code list register at Union level for managing and making publicly available the values that are included in the code lists referred to in paragraph 1.

  3. The Commission shall be assisted by the INSPIRE Commission expert group in the maintenance and update of the code list values.

  4. Code lists shall be one of the following types:

    1. code lists whose values comprise only the values specified in the INSPIRE code list register;

    2. code lists whose values comprise the values specified in the INSPIRE code list register and narrower values defined by data providers;

    3. code lists whose values comprise the values specified in the INSPIRE code list register and additional values at any level defined by data providers;

    4. code lists, whose values comprise any values defined by data providers.

  5. Code lists may be hierarchical. Values of hierarchical code lists may have a more general parent value.

  6. Where, for an attribute whose type is a code list as referred to in paragraph 4, points (b), (c) or (d), a data provider provides a value that is not specified in the INSPIRE code list register, that value and its definition and label shall be made available in another register.

The type of code list is represented in the UML model through the tagged value extensibility, which can take the following values:

  • none, representing code lists whose allowed values comprise only the values specified in the IRs (type a);

  • narrower, representing code lists whose allowed values comprise the values specified in the IRs and narrower values defined by data providers (type b);

  • open, representing code lists whose allowed values comprise the values specified in the IRs and additional values at any level defined by data providers (type c); and

  • any, representing code lists, for which the IRs do not specify any allowed values, i.e. whose allowed values comprise any values defined by data providers (type d).

📘

Recomendation 2

Additional values defined by data providers should not replace or redefine any value already specified in the IRs.

NOTE This data specification may specify recommended values for some of the code lists of type (b), (c) and (d) (see section 5.2.4.3). These recommended values are specified in a dedicated Annex.

In addition, code lists can be hierarchical, as explained in Article 6(5) of the IRs.

📕

IR Requirement
Article 6
Code Lists for Spatial Data Sets

(…​)

  1. Code lists may be hierarchical. Values of hierarchical code lists may have a more general parent value.

The type of code list and whether it is hierarchical or not is also indicated in the feature catalogues.

5.2.3.2. Obligations on data providers
📕

IR Requirement
Article 6
Code Lists for Spatial Data Sets

(…​.)

  1. Where, for an attribute whose type is a code list as referred to in paragraph 4, points (b), (c) or (d), a data provider provides a value that is not specified in the INSPIRE code list register, that value and its definition and label shall be made available in another register.

Article 6(6) obliges data providers to use only values that are allowed according to the specification of the code list. The "allowed values according to the specification of the code list" are the values explicitly defined in the IRs plus (in the case of code lists of type (b), (c) and (d)) additional values defined by data providers.

For attributes whose type is a code list of type (b), (c) or (d) data providers may use additional values that are not defined in the IRs. Article 6(6) requires that such additional values and their definition be made available in a register. This enables users of the data to look up the meaning of the additional values used in a data set, and also facilitates the re-use of additional values by other data providers (potentially across Member States).

NOTE Guidelines for setting up registers for additional values and how to register additional values in these registers is still an open discussion point between Member States and the Commission.

5.2.3.3. Recommended code list values

For code lists of type (b), (c) and (d), this data specification may propose additional values as a recommendation (in a dedicated Annex). These values will be included in the INSPIRE code list register. This will facilitate and encourage the usage of the recommended values by data providers since the obligation to make additional values defined by data providers available in a register (see section 5.2.4.2) is already met.

📘

Recomendation 3

Where these Technical Guidelines recommend values for a code list in addition to those specified in the IRs, these values should be used.

NOTE For some code lists of type (d), no values may be specified in these Technical Guidelines. In these cases, any additional value defined by data providers may be used.

5.2.3.4. Governance

The following two types of code lists are distinguished in INSPIRE:

  • Code lists that are governed by INSPIRE (INSPIRE-governed code lists). These code lists will be managed centrally in the INSPIRE code list register. Change requests to these code lists (e.g. to add, deprecate or supersede values) are processed and decided upon using the INSPIRE code list register’s maintenance workflows.

    INSPIRE-governed code lists will be made available in the INSPIRE code list register at http://inspire.ec.europa.eu/codelist/<CodeListName>. They will be available in SKOS/RDF, XML and HTML. The maintenance will follow the procedures defined in ISO 19135. This means that the only allowed changes to a code list are the addition, deprecation or supersession of values, i.e. no value will ever be deleted, but only receive different statuses (valid, deprecated, superseded). Identifiers for values of INSPIRE-governed code lists are constructed using the pattern http://inspire.ec.europa.eu/codelist/<CodeListName>/<value>.

  • Code lists that are governed by an organisation outside of INSPIRE (externally governed code lists). These code lists are managed by an organisation outside of INSPIRE, e.g. the World Meteorological Organization (WMO) or the World Health Organization (WHO). Change requests to these code lists follow the maintenance workflows defined by the maintaining organisations. Note that in some cases, no such workflows may be formally defined.

    Since the updates of externally governed code lists is outside the control of INSPIRE, the IRs and these Technical Guidelines reference a specific version for such code lists.

    The tables describing externally governed code lists in this section contain the following columns:

    • The Governance column describes the external organisation that is responsible for maintaining the code list.

    • The Source column specifies a citation for the authoritative source for the values of the code list. For code lists, whose values are mandated in the IRs, this citation should include the version of the code list used in INSPIRE. The version can be specified using a version number or the publication date. For code list values recommended in these Technical Guidelines, the citation may refer to the "latest available version".

    • In some cases, for INSPIRE only a subset of an externally governed code list is relevant. The subset is specified using the Subset column.

    • The Availability column specifies from where (e.g. URL) the values of the externally governed code list are available, and in which formats. Formats can include machine-readable (e.g. SKOS/RDF, XML) or human-readable (e.g. HTML, PDF) ones.

    Code list values are encoded using http URIs and labels. Rules for generating these URIs and labels are specified in a separate table.

📘

Recomendation 4

The http URIs and labels used for encoding code list values should be taken from the INSPIRE code list registry for INSPIRE-governed code lists and generated according to the relevant rules specified for externally governed code lists.

NOTE Where practicable, the INSPIRE code list register could also provide http URIs and labels for externally governed code lists.

5.2.3.5. Vocabulary

For each code list, a tagged value called "vocabulary" is specified to define a URI identifying the values of the code list. For INSPIRE-governed code lists and externally governed code lists that do not have a persistent identifier, the URI is constructed following the pattern http://inspire.ec.europa.eu/codelist/<UpperCamelCaseName>;.

If the value is missing or empty, this indicates an empty code list. If no sub-classes are defined for this empty code list, this means that any code list may be used that meets the given definition.

An empty code list may also be used as a super-class for a number of specific code lists whose values may be used to specify the attribute value. If the sub-classes specified in the model represent all valid extensions to the empty code list, the subtyping relationship is qualified with the standard UML constraint "\{complete,disjoint}".

5.2.4. Identifier management

📕

IR Requirement
Article 9
Identifier Management

  1. The data type Identifier defined in Section 2.1 of Annex I shall be used as a type for the external object identifier of a spatial object.

  2. The external object identifier for the unique identification of spatial objects shall not be changed during the life-cycle of a spatial object.

NOTE 1 An external object identifier is a unique object identifier which is published by the responsible body, which may be used by external applications to reference the spatial object. [DS-D2.5]

NOTE 2 Article 9(1) is implemented in each application schema by including the attribute inspireId of type Identifier.

NOTE 3 Article 9(2) is ensured if the namespace and localId attributes of the Identifier remains the same for different versions of a spatial object; the version attribute can of course change.

5.2.5. Geometry representation

📕

IR Requirement
Article 12
Other Requirements & Rules

  1. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.

NOTE 1 The specification restricts the spatial schema to 0-, 1-, 2-, and 2.5-dimensional geometries where all curve interpolations are linear and surface interpolations are performed by triangles.

NOTE 2 The topological relations of two spatial objects based on their specific geometry and topology properties can in principle be investigated by invoking the operations of the types defined in ISO 19107 (or the methods specified in EN ISO 19125-1).

5.2.6. Temporality representation

The application schema(s) use(s) the derived attributes "beginLifespanVersion" and "endLifespanVersion" to record the lifespan of a spatial object.

The attributes "beginLifespanVersion" specifies the date and time at which this version of the spatial object was inserted or changed in the spatial data set. The attribute "endLifespanVersion" specifies the date and time at which this version of the spatial object was superseded or retired in the spatial data set.

NOTE 1 The attributes specify the beginning of the lifespan of the version in the spatial data set itself, which is different from the temporal characteristics of the real-world phenomenon described by the spatial object. This lifespan information, if available, supports mainly two requirements: First, knowledge about the spatial data set content at a specific time; second, knowledge about changes to a data set in a specific time frame. The lifespan information should be as detailed as in the data set (i.e., if the lifespan information in the data set includes seconds, the seconds should be represented in data published in INSPIRE) and include time zone information.

NOTE 2 Changes to the attribute "endLifespanVersion" does not trigger a change in the attribute "beginLifespanVersion".

📕

IR Requirement
Article 10
Life-cycle of Spatial Objects

(…​)

  1. Where the attributes beginLifespanVersion and endLifespanVersion are used, the value of endLifespanVersion shall not be before the value of beginLifespanVersion.

NOTE The requirement expressed in the IR Requirement above will be included as constraints in the UML data models of all themes.

📘

Recomendation 5

If life-cycle information is not maintained as part of the spatial data set, all spatial objects belonging to this data set should provide a void value with a reason of "unpopulated".
5.2.6.1. Validity of the real-world phenomena

The application schema(s) use(s) the attributes "validFrom" and "validTo" to record the validity of the real-world phenomenon represented by a spatial object.

The attributes "validFrom" specifies the date and time at which the real-world phenomenon became valid in the real world. The attribute "validTo" specifies the date and time at which the real-world phenomenon is no longer valid in the real world.

Specific application schemas may give examples what "being valid" means for a specific real-world phenomenon represented by a spatial object.

📕

IR Requirement
Article 12
Other Requirements & Rules

(…​)

  1. Where the attributes validFrom and validTo are used, the value of validTo shall not be before the value of validFrom.

NOTE The requirement expressed in the IR Requirement above will be included as constraints in the UML data models of all themes.

5.3. Application schema Common Transport Elements

5.3.1. Description

5.3.1.1. Narrative description

The Common Transport Elements application schema covers elements that are shared by subthemes Road, Rail, Cable, Water and Air. These subthemes have been modelled as separate application schemas within the Transport Networks theme.

Many of the common transport elements are specializations of common definitions for networks and network elements available in the GNM. Elements in networks are handled as nodes, links, aggregated links, areas and points.

Cross-border connectivity (connections between networks across national and regional borders) is also included. It uses a mechanism provided by the GNM and inherited by the specific transport network classes. Using the same mechanism from the GNM, intermodal connectivity (connections between elements in networks which use a different mode of transport) may also be included.

The Common Transport Elements application schema also defines a number of common transport property classes (as specializations of the generic Network Property class in the GNM). These classes are used to describe properties of transport network elements and they can apply to the whole of the network element they are associated with or - for linear features - be described using linear referencing.

The primary aspects modelled for transport network elements are:

  • Spatial. Geometric (point, line and surface (i.e. areas (topographic areas)) representation of various elements that are parts of a network. Typically, the network is handled as a network of connected linear elements (links) with optional points (nodes) at the ends of the lines (at junctions, road ends etc). Also, points (other than nodes) and areas with a function in a network may be represented in the dataset.

  • Temporal. All elements in a network may have a temporal validity (i.e. description of when the network element exists in the real world) and also information on when data was entered, modified or deleted in the dataset.

  • Thematic. Depending on subtheme, the specializations for nodes, links and areas can be further characterized through various types of attributes and/or links to common or subtheme-specific property types.

5.3.1.2. UML Overview

As illustrated by Figure 5, many of the important mechanisms that are used to properly describe a transport network are defined by the GNM, and inherited by components of the transport network application schemas. Although these classes and relationships only appear in the informative paragraphs about imported types in the Transport Networks specification, they are very important for a correct implementation of this specification.

They include:

  • The relationships between Nodes, Links, Link Sequences and Link Sets,

  • Network Properties and the different ways of linking them to an element of a (transport) network,

  • The mechanism for cross-border and intermodal connections,

  • Grade separated crossings.

NOTE In Figure 5, only the most important relationships between the Common Transport Networks application schema and the GNM are shown. Not all classes are present in the diagram and most of the attributes are removed in the intrest of clarity.

In the following paragraphs, the use of these mechanisms will be further explained.

image

Figure 5 – UML class diagram: Overview of the Transport Networks application schema and its relationships with the GNM

image

Figure 6 – UML class diagram: Spatial object types – Transport Link, Node and Area

image

Figure 7 – UML class diagram: Spatial object types – Transport Point

image

Figure 8 – UML class diagram: Spatial object types – Transport Network

image

Figure 9 – UML class diagram: Spatial object types – Transport Properties

image

Figure 10 – UML class diagram: code lists

5.3.1.3. Consistency between spatial data sets

As described in D2.6 A.18 there are three topic areas regarding consistency between spatial data sets, these are:

  1. Coherence between spatial objects of the same theme at different levels of detail

  2. Coherence between different spatial objects within a same area

  3. Coherence at state boundaries.

[a] For Transport networks the specification incorporates two alternative forms of representation:

  • Physical topographic area objects (usually surveyed to a high accuracy)

  • Centreline representations (often an approximation of the centreline)

At any level of detail data integrity demands that these two forms need to be consistent with each other both positionally and logically. For example, where both exist, a road centreline will always fall within the limits of the corresponding road area object. Similarly, nodes in the road centreline representation will always fall inside the road area object that corresponds to the topographic junction where the node occurs.

📕

IR Requirement
Annex II, Section 7.9.1
Theme-specific Requirements – Consistency between spatial data sets

  1. Transport Networks centreline representations and nodes shall always be located within the extent of the area representation of the same object

[b] Both forms of representation will often be combined with other themes in a wide variety of applications. Again data integrity demands that these should be positionally consistent to ensure both a faithful representation of the real world and a professional appearance that will fill the user with confidence. For example buildings, rivers and forests with the transportation system.

📘

Recomendation 6

The objects in the Transport Networks theme should be positionally consistent with spatial objects from other themes (e.g. with buildings and rivers, forestry extents)

[c] It is essential that continuity of transport network information is preserved positionally, logically and semantically across state borders and – where applicable – also across regional borders within member states. This is vital to interoperable pan-European spatial information. The methods to support this are outlined in D2.6 Annex B.

The GNM provides a simple cross-referencing system to establish cross-border connections between Transport Networks. In practice, this is done by linking a transport network element in a data set on one side of the border and the connected or corresponding network element in a data set on the other side of the border to a Network Connection object which has been qualified as cross-border connected (when the linked network elements connect to each other) or as cross-border identical (when the linked network elements are representations in each data set of the same real world object). The Network Connection class is defined in the GNM.

CrossBorderConnections

Figure 11 – Examples of cross-border connections between Transport Networks

For Transport Networks the use of a Network Connection to establish cross-border connectivity is mandatory. Furthermore, it is recommended that the respective authorities seek to fully resolve the positional alignment of cross-border connected elements of Transport Networks in accordance to the rules for network connectivity outlined in section 10.2 (Ensuring Network Connectivity).

📕

IR Requirement
Annex II, Section 7.9.1
Theme-specific Requirements – Consistency between spatial data sets

  1. Connectivity between Transport Networks across state borders and – where applicable – also across regional borders (and data sets) within Member States shall be established and maintained by the respective authorities, using the cross-border connectivity mechanisms provided by the NetworkConnection type.
📘

Recomendation 7

In considering reconciliation across borders the respective authorities should seek to fully resolve the positional alignment that minimises positional deficiencies that would require repeated manual interval in updates or detract from the use of the data in applications.
5.3.1.4. Identifier management

As is required by the GCM, all spatial objects must have a unique identifier. This must be persistent and will usually be supported by a defined lifecycle to ensure that users understand the conditions that the identifier may be created, modified (in terms of its relationship with the spatial object) and deleted.

The unique object identifier will be modelled on the form described in D2.5 9.8.2 and 9.7 and D2.7 Chapter 7 where a country code and namespace is applied as a prefix to the existing local identifier used by the authority responsible for the data. This will both ensure that the identifier is:

  • Unique in the European spatial data infrastructure

  • The object is traceable in that infrastructure

All spatial objects in the Transport networks will have a unique object identifier – this includes those spatial objects that contain geometry and those that may not (e.g. Associated objects, AggregatedLink objects and those defined by linear referencing etc).

All spatial objects in the Transport Networks themes have a persistent unique identifier as defined in the INSPIRE documents D2.5 and D2.7.

NOTE All spatial object classes in the Transport Networks application schemas inherit their unique identifier from the GNM where it is defined with a cardinality of "0..1". In the transport networks classes the unique identifier is mandatory for all objects, which corresponds to a cardinality of "1".

Ideally all objects should be supported by a defined lifecycle model and a method of versioning (see D2.5 9.7) that assists the user in distinguishing between current objects and previous versions.

📘

Recomendation 8

The spatial object unique identifier should be supported by a documented lifecycle to provide users with a defined behaviour pattern as conditions which affect the object change over time.
📘

Recomendation 9

The spatial object unique identifier should be supported by a defined form of versioning to ensure that users refer to the correct version in applications.
5.3.1.5. Modelling of object references

The INSPIRE Directive promotes the reuse of information. Object referencing is designed to support that aim whereby an existing object e.g. a transport link is used by several other objects, which may be collected by different organisations (e.g. surface condition survey, speed limit/restrictions etc). Such objects would normally inherit geometry from underlying referenced objects.

Data Association

As described in D2.5 Chapter 13 an associated object would reference the base network (data association). The link is physically achieved by cross referencing one object with another – using the unique identifiers provided (and ideally the version information),

This is common practice in several existing transport networks and the Transport networks specification supports this approach.

📘

Recomendation 10

All associated spatial objects in the Transport Networks theme should use object referencing to an existing set of transport links rather than duplicate the geometry.
📘

Recomendation 11

All centreline spatial objects in the Transport Networks theme should use object referencing to the topographic area objects to support both data sharing of application data and the support synchronisation of the two representations over time.

Transport properties and linear referencing

Many of the thematic properties of the Transport Networks objects are defined as Transport Properties. All Transport Property classes are subtypes of the GNM Network Property class. As such, they inherit the mechanisms that are defined in the GNM to link them to transport network elements (such as Transport links, Transport Link Sequences, Transport Link Sets, Transport Nodes and Transport Areas) using object referencing.

Transport Properties also offer a way the easily extend the Transport Networks specification. For different applications, additional Transport Property classes can be defined and linked to the appropriate Network Elements.

A Transport Property can be linked to an entire transport element or, when the target is a Transport Link or – more typically – a Transport Link Sequence, to part of it using linear referencing.

Linear referencing is included in the GNM (ISO 19148:2012) (see also Chapter 10.2) and a simple approach is included until the standard is more widely used. This can be of value in many applications where a consistent approach to data capture and referencing is absent today for example speed limit extents as shown in Figure 12 below.

LinearReferencingExample

Figure 12 – example of linear referencing to locate the start and end of a speed restriction zone.

📘

Recomendation 12

Linear referencing should be adopted to support the location of changes in condition or other phenomena along a link or link sequence where there is no requirement to disturb the link and node structure

Linear referencing is used to position phenomena along a linear object, using a distance from the beginning of the linear object. Some systems disconnect the linear reference from the geometry of the linear object in the dataset, adding a calibrated linear coordinate to the object, corresponding to the distance measured along the real world object or interpolated between fixed marker posts (which themselves may not be exactly located at the distance they indicate).

For Transport Networks, all supplied linear references will use the distance along the geometry of the linear object in the database.

📕

IR Requirement
Annex II, Section 7.9.2
Theme-specific Requirements – Modelling of object references

  1. When linear referencing is used in Transport Networks data, the position of referenced properties on links and link sequences shall be expressed as distances measured along the supplied geometry of the underlying link object(s).

Intermodal connections

The Transport Networks specification inherits a simple approach to intermodal connections from the GNM that has been adopted in the absence of any commonly adopted standards. Spatial objects within the Transport Networks specification can be linked (cross-referenced) to support connectivity between any two transport networks that use different modes of transport. This is to support journey planning, navigation etc.

In practice, intermodal connections can be established by linking two transport network elements (from different transport networks which use a different mode of transport) to a Network Connection object which is qualified as an intermodal connection. The Network Connection class is defined in the GNM.

Several types of transport network elements, including links, link sequences, link sets, areas and nodes can participate in intermodal connections. The use of nodes is recommended since this allows for a more accurate positioning of the connection in the two networks.

Figure 13 demonstrates the concept of the intermodal connection. In this example, a node in a road transport network is connected to a node in the railway network. These nodes may, but do not have to, share the same location.

Intermodal

Figure 13 – The intermodal connection linking two different Transport networks themes Rail and Road

📕

IR Requirement
Annex II, Section 7.9.2
Theme-specific Requirements – Modelling of object references

  1. An inter-modal connection shall always reference two elements which belong to different networks.
📘

Recomendation 13

An inter-modal connection should be established between transport nodes.
5.3.1.6. Geometry representation

There are three types of geometry in this specification:

  1. (Topographic) Area objects in Transport Networks

  2. Centreline objects in Transport Networks

  3. Point objects in Transport Networks

Types (a) and (b) may be alternative representations of the same real world phenomena about which the user can associate their own information (objects) – See Annex B1 for more background.

Type (c) is, apart from network nodes, only included in the specification for marker posts. However users may wish to collect such data and associate it with the network (e.g. the location of network infrastructure components e.g. traffic lights, lighting columns, beacons, navigation lights etc).

The geometric basis of a transport network consists of a number of connected linear elements (Transport Links) with optional point elements (Transport Nodes) at the ends of the lines (at junctions, terminals, etc).

Section 10.2 (Ensuring Network Connectivity) contains the necessary rules for ensuring connectivity within Transport Networks. Connections between Transport Networks are established by using the cross-border and intermodal connection mechanisms present in the GNM and further explained in sections 5.3.1.3 (Consistency between spatial data sets) and 5.3.1.5 (Modelling of object references) respectively.

📕

IR Requirement
Annex II, Section 7.9.3
Theme-specific Requirements – Geometry representation

  1. Transport link ends shall be connected wherever an intersection exists between the real world phenomena they represent. No connections shall be created at crossing network elements when it is not possible to pass from one element to another.

NOTE Grade separated crossings can be modeled using the GradeSeparatedCrossing class from the GNM. This class enables the ordered linking of two (Transport) Links. In this ordered relationship, the first Link is always the lower of the two.

📘

Recomendation 14

In Transport Networks data, Transport Nodes should be present wherever Transport Links connect or end

If a Transport Networks data set contains nodes, they can only occur where a connection exists between two Transport Links or where a Transport Link ends (end or dangle node). Nodes shall not occur where two links cross but not intersect, for instance at grade separated crossings.
NOTE An AirNode is not necessarily placed at the end or start of a Transport Link when it is not used for navigation/ATS purposes.
Example: an AerodromeNode could either simply represent the aerodrome location (significantPoint = false) or act as transport node for connectivity (significantPoint = true).

📕

IR Requirement
Annex II, Section 7.9.3
Theme-specific Requirements – Geometry representation

  1. In a Transport Networks data set which contains nodes, these nodes shall only be present where Transport Links connect or end.

An AirNode is not required to be present where Transport Links connect or end when it is not intended for navigation/ATS purposes i.e., when its significantPoint attribute is set to 'false'.

The individual Transport Links can be combined to form Transport Link Sequences, using the mechanism provided by the GNM. As an ordered sequence of Transport Links, Transport Link Sequences have no geometry of their own. Their position is defined by the composing Transport Links.

Transport Link Sequences and/or Transport Links can be further combined to form Transport Link Sets. This way, looped and forked elements of a transport network can be represented. Like Transport Link Sequences, Transport Link Sets have no geometry of their own.

LinkSequenceSet

Figure 14 –Example of the use of Link, Node, Link Sequence and Link Set

Levels of detail: The specification addresses the highest resolution of data capture in Transport Networks and is also applicable to any derived lower resolution levels of detail where the number of coordinates is reduced and the geometry simplified to support viewing and reporting at regional, national and European levels. See also Chapter D10.4 and Annex B.1

This specification cannot advise on the form of representation at the highest resolution nor the accuracy since this will be driven by member state needs. Ideally derived lower resolution datasets will use the approach outlined in D2.6 A.19 where all the objects are related from lowest to highest resolution and any user information collected about the network can be simply aggregated at the lower resolution level or disaggregated as the user increases the resolution.

📘

Recomendation 15

All Transport Networks spatial objects should be provided at the source resolution (and accuracy) where possible.
📘

Recomendation 16

Lower order resolutions should be derived from the highest order representation of the transport network, and any user information captured once and referenced to each geometrical representation

NOTE The topological relations of two spatial objects based on their specific geometry and topology properties can in principle be investigated by invoking the operations of the types defined in ISO 19107 (or the methods specified in OGC 06-103r3).

5.3.1.7. Temporality representation
📘

Recomendation 17

If information about the actual start and end of the existence of transport network elements is not maintained as part of the spatial data set, all spatial objects belonging to this data set should provide a void value with a reason of "unknown".
5.3.1.8. Notes on constraints for transport properties

NOTE 1 The application schemas in this section specify constraints on transport properties restricting the transport objects the transport property can be associated with. In some cases, these constraints allow the transport property to be associated only with very specific types, while in other cases they refer only very generally to spatial objects that are part of a specific (e.g. road or rail) transport network. In some cases, the more specific restriction is already indicated in the name of the constraint (e.g. "Applies to WaterwayLink and WaterwayNode only"), while the natural language description is less specific (e.g. "This property can only be associated with a spatial object that is part of a water transport network."). Ideally, these mismatches should be removed, while following the general rule that the constraints should be as specific as possible. This will be proposed in a future update of the Regulation on spatial data sets and services as well as this guidelines document.

NOTE 2 In cases where there is a mismatch between the name of the constraint and its natural language description, the OCL constraint already reflects the more specific restriction. In these cases, while the natural language description is consistent with the Regulation on spatial data sets and services, the OCL constraint already reflects the intended update of the (natural language descriptions of the) constraint.

5.3.2. Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Common Transport Elements

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

AccessRestriction

Common Transport Elements

«featureType»

AccessRestrictionValue

Common Transport Elements

«codeList»

ConditionOfFacility

Common Transport Elements

«featureType»

MaintenanceAuthority

Common Transport Elements

«featureType»

MarkerPost

Common Transport Elements

«featureType»

OwnerAuthority

Common Transport Elements

«featureType»

RestrictionForVehicles

Common Transport Elements

«featureType»

RestrictionTypeValue

Common Transport Elements

«codeList»

TrafficFlowDirection

Common Transport Elements

«featureType»

TransportArea

Common Transport Elements

«featureType»

TransportLink

Common Transport Elements

«featureType»

TransportLinkSequence

Common Transport Elements

«featureType»

TransportLinkSet

Common Transport Elements

«featureType»

TransportNetwork

Common Transport Elements

«featureType»

TransportNode

Common Transport Elements

«featureType»

TransportObject

Common Transport Elements

«featureType»

TransportPoint

Common Transport Elements

«featureType»

TransportProperty

Common Transport Elements

«featureType»

VerticalPosition

Common Transport Elements

«featureType»
5.3.2.1. Spatial object types
5.3.2.1.1. AccessRestriction
AccessRestriction

Subtype of:

TransportProperty

Definition:

A restriction on the access to a transport element.

Stereotypes:

«featureType»

Attribute: restriction

Value type:

AccessRestrictionValue

Definition:

Nature of the access restriction.

Multiplicity:

1
5.3.2.1.2. ConditionOfFacility
ConditionOfFacility

Subtype of:

TransportProperty

Definition:

State of a transport network element with regards to its completion and use.

Stereotypes:

«featureType»

Attribute: currentStatus

Value type:

ConditionOfFacilityValue

Definition:

Current status value of a transport network element with regards to its completion and use.

Multiplicity:

1
5.3.2.1.3. MaintenanceAuthority
MaintenanceAuthority

Subtype of:

TransportProperty

Definition:

The authority responsible for maintenance of the transport element.

Stereotypes:

«featureType»

Attribute: authority

Value type:

CI_Citation

Definition:

Identification of the maintenance authority.

Multiplicity:

1
5.3.2.1.4. MarkerPost
MarkerPost

Subtype of:

TransportPoint

Definition:

Reference marker placed along a route in a transport network, mostly at regular intervals, indicating the distance from the beginning of the route, or some other reference point, to the point where the marker is located.

Description:

EXAMPLE Examples of routes along which marker posts can be found are roads, railway lines and navigable waterways.

Stereotypes:

«featureType»

Attribute: location

Value type:

Distance

Definition:

Distance from the beginning of the route, or some other reference point, to the point where a marker post is located.

Multiplicity:

1

Association role: route

Value type:

TransportLinkSet

Definition:

Route in a transport network along which the marker post is placed.

Multiplicity:

1

Stereotypes:

«voidable»
5.3.2.1.5. OwnerAuthority
OwnerAuthority

Subtype of:

TransportProperty

Definition:

The authority owning the transport element.

Stereotypes:

«featureType»

Attribute: authority

Value type:

CI_Citation

Definition:

Identification of the owning authority.

Multiplicity:

1
5.3.2.1.6. RestrictionForVehicles
RestrictionForVehicles

Subtype of:

TransportProperty

Definition:

Restriction on vehicles on a transport element.

Stereotypes:

«featureType»

Attribute: measure

Value type:

Measure

Definition:

The measure for the restriction .

Description:

SOURCE [Euroroads].

Multiplicity:

1

Attribute: restrictionType

Value type:

RestrictionTypeValue

Definition:

The type of restriction .

Description:

SOURCE [Euroroads].

Multiplicity:

1
5.3.2.1.7. TrafficFlowDirection
TrafficFlowDirection

Subtype of:

TransportProperty

Definition:

Indicates the direction of the flow of traffic in relation to the direction of the transport link vector.

Stereotypes:

«featureType»

Attribute: direction

Value type:

LinkDirectionValue

Definition:

Indicates the direction of the flow of traffic.

Multiplicity:

1

Constraint: Applies to Link and LinkSequence only

Natural language:

This property can only be associated with a spatial object of the type Link or LinkSequence.

OCL:

inv: networkRef.element.oclIsKindOf(LinkReference)
5.3.2.1.8. TransportArea
TransportArea (abstract)

Subtype of:

TransportObjectNetworkArea

Definition:

Surface that represents the spatial extent of an element of a transport network.

Stereotypes:

«featureType»

Attribute: validFrom

Value type:

DateTime

Definition:

The time when the transport area started to exist in the real world.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

DateTime

Definition:

The time from which the transport area no longer exists in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Constraint: All objects have inspireId

Natural language:

All transport areas have an external object identifier.

OCL:

inv:inspireId→notEmpty()
5.3.2.1.9. TransportLink
TransportLink (abstract)

Subtype of:

TransportObjectLink

Definition:

A linear spatial object that describes the geometry and connectivity of a transport network between two points in the network.

Stereotypes:

«featureType»

Attribute: validFrom

Value type:

DateTime

Definition:

The time when the transport link started to exist in the real world.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

DateTime

Definition:

The time from which the transport link no longer exists in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Constraint: All objects have inspireId

Natural language:

All transport links have an external object identifier.

OCL:

inv:inspireId→notEmpty()
5.3.2.1.10. TransportLinkSequence
TransportLinkSequence (abstract)

Subtype of:

TransportObjectLinkSequence

Definition:

A linear spatial object, composed of an ordered collection of transport links, which represents a continuous path in the transport network without any branches. The element has a defined beginning and end and every position on the transport link sequence is identifiable with one single parameter such as length. It describes an element of the transport network, characterized by one or more thematical identifiers and/or properties.

Stereotypes:

«featureType»

Attribute: validFrom

Value type:

DateTime

Definition:

The time when the transport link sequence started to exist in the real world.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

DateTime

Definition:

The time from which the transport link sequence no longer exists in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Constraint: All components belong to same transport network

Natural language:

A transport link sequence must be composed of transport links that all belong to the same transport network.

OCL:

inv: link→forAll(l | l.link.inNetwork = self.inNetwork)

Constraint: All objects have inspireId

Natural language:

All transport link sequences have an external object identifier.

OCL:

inv: inspireId→notEmpty()
5.3.2.1.11. TransportLinkSet
TransportLinkSet (abstract)

Subtype of:

TransportObjectLinkSet

Definition:

A collection of transport link sequences and or individual transport links that has a specific function or significance in a transport network.

Description:

NOTE
This spatial object type supports the aggregation of links to form objects with branches, loops, parallel sequences of links, gaps, etc.

EXAMPLE
A dual carriageway road, as a collection of the two link sequences that represent each carriageway.

Stereotypes:

«featureType»

Attribute: validFrom

Value type:

DateTime

Definition:

The time when the transport link set started to exist in the real world.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

DateTime

Definition:

The time from which the transport link set no longer exists in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Association role: post

Value type:

MarkerPost

Definition:

Marker post along a route in a transport network.

Multiplicity:

0..*

Stereotypes:

«voidable»

Constraint: All components belong to same transport network

Natural language:

A transport link set must be composed of transport links and or transport link sequences that all belong to the same transport network.

OCL:

inv: link→forAll(l

l.inNetwork = self.inNetwork)
!===

Constraint: All objects have inspireId

Natural language:

All transport link sets have an external object identifier.

OCL:

inv:inspireId→notEmpty()
5.3.2.1.12. TransportNetwork
TransportNetwork

Subtype of:

Network

Definition:

Collection of network elements that belong to a single mode of transport.

Description:

NOTE Road, rail, water and air transport are always considered separate transport modes. Even within these four categories, multiple modes of transport can be defined, based on infrastructure, vehicle types, propulsion system, operation and/or other defining characteristics.

EXAMPLE All road transport can be considered one mode of transport for some applications. For other applications, it might be necessary to distinguish between different public road transport networks. Within water transport, marine and inland water transport can be considered to be separate modes of transport for some applications, as they use different types of ships.

Stereotypes:

«featureType»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the spatial object.

Multiplicity:

1

Attribute: typeOfTransport

Value type:

TransportTypeValue

Definition:

Type of transport network, based on the type of infrastructure the network uses.

Multiplicity:

1
5.3.2.1.13. TransportNode
TransportNode (abstract)

Subtype of:

TransportObjectNode

Definition:

A point spatial object which is used for connectivity.

Description:

Nodes are found at either end of the TransportLink.

Stereotypes:

«featureType»

Attribute: validFrom

Value type:

DateTime

Definition:

The time when the transport node started to exist in the real world.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

DateTime

Definition:

The time from which the transport node no longer exists in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Constraint: All objects have inspireId

Natural language:

All transport nodes have an external object identifier.

OCL:

inv:inspireId→notEmpty()
5.3.2.1.14. TransportObject
TransportObject (abstract)

Definition:

An identity base for transport network objects in the real world.

Description:

NOTE Derived 'views' of real-world transport objects are represented through specialisations in other application schemas; all representations of the same real-world object share a common geographic name.

Stereotypes:

«featureType»

Attribute: geographicalName

Value type:

GeographicalName

Definition:

A geographical name that is used to identify the transport network object in the real world. It provides a 'key' for implicitly associating different representations of the object.

Multiplicity:

0..1

Stereotypes:

«voidable»
5.3.2.1.15. TransportPoint
TransportPoint (abstract)

Subtype of:

TransportObjectNetworkElement

Definition:

A point spatial object - which is not a node - that represents the position of an element of a transport network.

Stereotypes:

«featureType»

Attribute: geometry

Value type:

GM_Point

Definition:

The location of the transport point.

Multiplicity:

1

Attribute: validFrom

Value type:

DateTime

Definition:

The time when the transport point started to exist in the real world.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

DateTime

Definition:

The time from which the transport point no longer exists in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Constraint: All objects have inspireId

Natural language:

All transport points have an external object identfier.

OCL:

inv:inspireId→notEmpty()
5.3.2.1.16. TransportProperty
TransportProperty (abstract)

Subtype of:

NetworkProperty

Definition:

A reference to a property that falls upon the network. This property can apply to the whole of the network element it is associated with or - for linear spatial objects - be described using linear referencing.

Stereotypes:

«featureType»

Attribute: validFrom

Value type:

DateTime

Definition:

The time when the transport property started to exist in the real world.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

DateTime

Definition:

The time from which the transport property no longer exists in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Constraint: All objects have inspireId

Natural language:

All transport properties have an external object identifier.

OCL:

inv:inspireId→notEmpty()
5.3.2.1.17. VerticalPosition
VerticalPosition

Subtype of:

TransportProperty

Definition:

Vertical level relative to other transport network elements.

Stereotypes:

«featureType»

Attribute: verticalPosition

Value type:

VerticalPositionValue

Definition:

Relative vertical position of the transport element.

Multiplicity:

1
5.3.2.2. Code lists
5.3.2.2.1. RestrictionTypeValue
RestrictionTypeValue

Definition:

Possible restrictions on vehicles that can access a transport element.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RestrictionTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.3.2.2.2. AccessRestrictionValue
AccessRestrictionValue

Definition:

Types of access restrictions for a transport element.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AccessRestrictionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.3.2.2.3. TransportTypeValue
TransportTypeValue

Definition:

Possible types on transport networks.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/TransportTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.3.2.3. Imported types (informative)

This section lists definitions for feature types, data types and code lists that are defined in other application schemas. The section is purely informative and should help the reader understand the feature catalogue presented in the previous sections. For the normative documentation of these types, see the given references.

5.3.2.3.1. CI_Citation
CI_Citation

Package:

Citation and responsible party information

Reference:

Geographic information — Metadata [ISO 19115:2003/Cor 1:2006]
5.3.2.3.2. ConditionOfFacilityValue
ConditionOfFacilityValue

Package:

Base Types

Reference:

INSPIRE Generic Conceptual Model, version 3.4 [DS-D2.5]

Definition:

The status of a facility with regards to its completion and use.
5.3.2.3.3. DateTime
DateTime

Package:

Date and Time

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.3.2.3.4. Distance
Distance

Package:

Units of Measure

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.3.2.3.5. GM_Point
GM_Point

Package:

Geometric primitive

Reference:

Geographic information — Spatial schema [ISO 19107:2003]
5.3.2.3.6. GeographicalName
GeographicalName

Package:

Geographical Names

Reference:

INSPIRE Data specification on Geographical Names [DS-D2.8.I.3]

Definition:

Proper noun applied to a real world entity.
5.3.2.3.7. Identifier
Identifier

Package:

Base Types

Reference:

INSPIRE Generic Conceptual Model, version 3.4 [DS-D2.5]

Definition:

External unique object identifier published by the responsible body, which may be used by external applications to reference the spatial object.

Description:

NOTE1 External object identifiers are distinct from thematic object identifiers.

NOTE 2 The voidable version identifier attribute is not part of the unique identifier of a spatial object and may be used to distinguish two versions of the same spatial object.

NOTE 3 The unique identifier will not change during the life-time of a spatial object.
5.3.2.3.8. Link
Link (abstract)

Package:

Network

Reference:

INSPIRE Data Specifications – Base Models – Generic Network Model, version 1.0 [DS-D2.10.1]

Definition:

Curvilinear network element that connects two positions and represents a homogeneous path in the network. The connected positions may be represented as nodes.
5.3.2.3.9. LinkDirectionValue
LinkDirectionValue

Package:

Network

Reference:

INSPIRE Data Specifications – Base Models – Generic Network Model, version 1.0 [DS-D2.10.1]

Definition:

List of values for directions relative to a link
5.3.2.3.10. LinkSequence
LinkSequence (abstract)

Package:

Network

Reference:

INSPIRE Data Specifications – Base Models – Generic Network Model, version 1.0 [DS-D2.10.1]

Definition:

A network element which represents a continuous path in the network without any branches. The element has a defined beginning and end and every position on the link sequence is identifiable with one single parameter such as length.

Description:

EXAMPLE A link sequence may represent a route.
5.3.2.3.11. LinkSet
LinkSet (abstract)

Package:

Network

Reference:

INSPIRE Data Specifications – Base Models – Generic Network Model, version 1.0 [DS-D2.10.1]

Definition:

A collection of link sequences and/or individual links that has a specific function or significance in a network.

Description:

NOTE This spatial object type supports the aggregation of links to form objects with branches, loops, parallel sequences of links, gaps, etc.

EXAMPLE A dual carriageway road, as a collection of the two link sequences that represent each carriageway.
5.3.2.3.12. Measure
Measure

Package:

ProductionAndIndustrialFacilitiesExtension

Reference:

INSPIRE Data specification on Production and Industrial Facilities [DS-D2.8.III.8]

Definition:

Declared or measured quantity of any kind of physical entity.
5.3.2.3.13. Network
Network

Package:

Assessment Methods

Reference:

INSPIRE Data specification on Area Management Restriction Regulation Zones and Reporting units [DS-D2.8.III.11]
5.3.2.3.14. NetworkArea
NetworkArea (abstract)

Package:

Network

Reference:

INSPIRE Data Specifications – Base Models – Generic Network Model, version 1.0 [DS-D2.10.1]

Definition:

A 2-dimensional element in a network.
5.3.2.3.15. NetworkElement
NetworkElement (abstract)

Package:

Network

Reference:

INSPIRE Data Specifications – Base Models – Generic Network Model, version 1.0 [DS-D2.10.1]

Definition:

Abstract base type representing an element in a network. Every element in a network provides some function that is of interest in the network.
5.3.2.3.16. NetworkProperty
NetworkProperty (abstract)

Package:

Network

Reference:

INSPIRE Data Specifications – Base Models – Generic Network Model, version 1.0 [DS-D2.10.1]

Definition:

Abstract base type representing phenomena located at or along a network element. This base type provides general properties to associate the network-related phenomena (network properties) with the network elements.

Description:

In the simplest case (NetworkReference), the network property applies to the whole network element. In the case of a Link, the spatial reference may be restricted to part of the Link by using a linear reference. ISO/TC 211 is currently in the early stages of developing a standard for Linear Referencing (ISO 19148). A simple mechanism to express linear references is provided in this version of the network model; it is expected that the model will be extended once ISO 19148 is stable. The current simple model requires for all linear references two expressions representing a distance from the start of the Link along its curve geometry. The network property applies to the part of the Link between fromPosition and toPosition.
5.3.2.3.17. Node
Node (abstract)

Package:

Network

Reference:

INSPIRE Data Specifications – Base Models – Generic Network Model, version 1.0 [DS-D2.10.1]

Definition:

Represents a significant position in the network that always occurs at the beginning or the end of a link.

Description:

NOTE if a topological representation of the network is used the road node is either a topological connection between two or more links or the termination of a ink. If a geometric representation of the network is used road nodes are represented by points or alternatively another geometric shape. [EuroRoadS]
5.3.2.3.18. VerticalPositionValue
VerticalPositionValue

Package:

Base Types

Reference:

INSPIRE Generic Conceptual Model, version 3.4 [DS-D2.5]

Definition:

The relative vertical position of a spatial object.

5.4. Application schema Road Transport Networks

5.4.1. Description

5.4.1.1. Narrative description

The Road Transport Networks application schema (Roads Schema) employs a link and node structure to represent a road system used for the transportation of vehicles in the form of a linear network. The Roads Schema inherits classes from the Common Transport Schema and also creates its own classes to describe properties of the road network such as Ownership and traffic direction that can apply to whole sections of the network element or subsections that can be described using linear referencing.

The primary aspects modelled for road network elements are:

  • Spatial. Geometric (point, line and area (topographic)) representation of various elements that are parts of a network. Typically, the network is handled as a network of connected linear elements (links) with points (nodes) at the ends of the lines (at junctions, road ends etc). Also real objects with a function in a network may be represented in the dataset. Network connectivity within the roads network is essential but between elements in the other networks is an optional spatial aspect.

  • Temporal. All elements in a network may have a temporal validity (i.e. description of when the network element exists in the real world) and also optional information on when data was entered, modified or deleted in the dataset.

  • Thematic. The road schema can be thematically displayed via several of the attributes defined within the specification such as ownerAuthority or speedLimits.

5.4.1.2. UML Overview
image

Figure 15 – UML class diagram: Overview of the Road Transport Networks

image

Figure 16 – UML class diagram: Road Transport Networks Spatial object types – Links, Nodes and Areas

image

Figure 17 – UML class diagram: Road Transport Networks Spatial object types – Transport Properties

RoadTransportNetwork

Figure 18 – Overview of the main Road Transport Networks objects

image

Figure 19 – UML class diagram: Road Transport Networks code lists

5.4.1.3. Consistency between spatial data sets

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.3) apply to the corresponding specialized elements/classes in the Road transport networks.

5.4.1.4. Identifier management

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.4) apply to the corresponding specialized elements/classes in the Road transport networks.

5.4.1.5. Modelling of object references

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.5) apply to the corresponding specialized elements/classes in the Road transport networks.

5.4.1.6. Geometry representation

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.6) apply to the corresponding specialized elements/classes in the Road transport networks.

5.4.1.7. Temporality representation

All attributes describing the lifespan of spatial objects or the phenomena in the real world they describe are inherited from the Common Transport Elements application schema. Refer to section 5.3.1.7 for more information.

5.4.2. Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Road Transport Network

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

AreaConditionValue

Road Transport Network

«codeList»

ERoad

Road Transport Network

«featureType»

FormOfRoadNodeValue

Road Transport Network

«codeList»

FormOfWay

Road Transport Network

«featureType»

FormOfWayValue

Road Transport Network

«codeList»

FunctionalRoadClass

Road Transport Network

«featureType»

NumberOfLanes

Road Transport Network

«featureType»

Road

Road Transport Network

«featureType»

RoadArea

Road Transport Network

«featureType»

RoadLink

Road Transport Network

«featureType»

RoadLinkSequence

Road Transport Network

«featureType»

RoadName

Road Transport Network

«featureType»

RoadNode

Road Transport Network

«featureType»

RoadPartValue

Road Transport Network

«codeList»

RoadServiceArea

Road Transport Network

«featureType»

RoadServiceType

Road Transport Network

«featureType»

RoadServiceTypeValue

Road Transport Network

«codeList»

RoadSurfaceCategory

Road Transport Network

«featureType»

RoadSurfaceCategoryValue

Road Transport Network

«codeList»

RoadWidth

Road Transport Network

«featureType»

ServiceFacilityValue

Road Transport Network

«codeList»

SpeedLimit

Road Transport Network

«featureType»

SpeedLimitSourceValue

Road Transport Network

«codeList»

VehicleTrafficArea

Road Transport Network

«featureType»

VehicleTypeValue

Road Transport Network

«codeList»

WeatherConditionValue

Road Transport Network

«codeList»
5.4.2.1. Spatial object types
5.4.2.1.1. ERoad
ERoad

Subtype of:

TransportLinkSet

Definition:

A collection of road link sequences and or individual road links that represents a route that is part of the international E-road network, characterized by its European route number.

Description:

EXAMPLE E40.

Stereotypes:

«featureType»

Attribute: europeanRouteNumber

Value type:

CharacterString

Definition:

Code, identifying the route in the international E-road network. The code always starts with a letter 'E', followed by a one-, two- or three-digit number.

Multiplicity:

1

Stereotypes:

«voidable»
5.4.2.1.2. FormOfWay
FormOfWay

Subtype of:

TransportProperty

Definition:

A classification based on the physical properties of the Road Link.

Description:

SOURCE Based on [EuroRoadS].

Stereotypes:

«featureType»

Attribute: formOfWay

Value type:

FormOfWayValue

Definition:

Physical form of the way.

Multiplicity:

1

Constraint: Applies to road transport elements only

Natural language:

This property can only be associated with a spatial object that is part of a road transport network.

OCL:

inv: networkRef.element.oclIsKindOf(Road) or networkRef.element.oclIsKindOf(ERoad) or networkRef.element.oclIsKindOf(RoadLink) or networkRef.element.oclIsKindOf(RoadLinkSequence) or networkRef.element.oclIsKindOf(RoadNode) or networkRef.element.oclIsKindOf(RoadArea) or networkRef.element.oclIsKindOf(RoadServiceArea) or networkRef.element.oclIsKindOf(VehicleTrafficArea)
5.4.2.1.3. FunctionalRoadClass
FunctionalRoadClass

Subtype of:

TransportProperty

Definition:

A classification based on the importance of the role that the road performs in the road network.

Description:

SOURCE Adapted from [GDF, EuroRoadS].

Stereotypes:

«featureType»

Attribute: functionalClass

Value type:

FunctionalRoadClassValue

Definition:

Functional rank of the road link in the road network.

Description:

NOTE Where functional classification systems are used that have fewer classes/ranks than the number provided by FunctionalRoadClassValues, classes with codes 1 to n will be used, where n corresponds to the number of classes that are used in the classification system.

Multiplicity:

1

Constraint: Applies to road transport elements only

Natural language:

This property can only be associated with a spatial object that is part of a road transport network.

OCL:

inv: networkRef.element.oclIsKindOf(Road) or networkRef.element.oclIsKindOf(ERoad) or networkRef.element.oclIsKindOf(RoadLink) or networkRef.element.oclIsKindOf(RoadLinkSequence) or networkRef.element.oclIsKindOf(RoadNode) or networkRef.element.oclIsKindOf(RoadArea) or networkRef.element.oclIsKindOf(RoadServiceArea) or networkRef.element.oclIsKindOf(VehicleTrafficArea)
5.4.2.1.4. NumberOfLanes
NumberOfLanes

Subtype of:

TransportProperty

Definition:

The number of lanes of a road element.

Description:

SOURCE Adapated from [Euroroads].

Stereotypes:

«featureType»

Attribute: direction

Value type:

LinkDirectionValue

Definition:

Indicates which direction the number of lanes is valid for.

Description:

SOURCE [Euroroads].
NOTE When the value for this attribute is 'both', numberOfLanes contains the sum of the number of lanes in both directions of travel.
NOTE This attribute only applies when the property is associated with a road link or road link sequence.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: minMaxNumberOfLanes

Value type:

MinMaxLaneValue

Definition:

Indicates if the number of lanes is counted as minimum or maximum value.

Description:

SOURCE [Euroroads].

NOTE This attribute only applies when the value in numberOfLanes is not an exact value.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: numberOfLanes

Value type:

Integer

Definition:

Number of lanes.

Description:

SOURCE [Euroroads].

Multiplicity:

1

Constraint: Applies to road transport elements only

Natural language:

This property can only be associated with a spatial object that is part of a road transport network.

OCL:

inv: networkRef.element.oclIsKindOf(Road) or networkRef.element.oclIsKindOf(ERoad) or networkRef.element.oclIsKindOf(RoadLink) or networkRef.element.oclIsKindOf(RoadLinkSequence) or networkRef.element.oclIsKindOf(RoadNode) or networkRef.element.oclIsKindOf(RoadArea) or networkRef.element.oclIsKindOf(RoadServiceArea) or networkRef.element.oclIsKindOf(VehicleTrafficArea)
5.4.2.1.5. RoadLinkSequence
RoadLinkSequence

Subtype of:

TransportLinkSequence

Definition:

A linear spatial object, composed of an ordered collection of road links, which represents a continuous path in a road network without any branches. The element has a defined beginning and end and every position on the road link sequence is identifiable with one single parameter such as length. It describes an element of the road network, characterized by one or more thematic identifiers and/or properties.

Stereotypes:

«featureType»
5.4.2.1.6. RoadName
RoadName

Subtype of:

TransportProperty

Definition:

Name of a road, as assigned by the responsible authority.

Stereotypes:

«featureType»

Attribute: name

Value type:

GeographicalName

Definition:

Name of the road.

Multiplicity:

1

Constraint: Applies to road transport elements only

Natural language:

This property can only be associated with a spatial object that is part of a road transport network.

OCL:

inv: networkRef.element.oclIsKindOf(Road) or networkRef.element.oclIsKindOf(ERoad) or networkRef.element.oclIsKindOf(RoadLink) or networkRef.element.oclIsKindOf(RoadLinkSequence) or networkRef.element.oclIsKindOf(RoadNode) or networkRef.element.oclIsKindOf(RoadArea) or networkRef.element.oclIsKindOf(RoadServiceArea) or networkRef.element.oclIsKindOf(VehicleTrafficArea)
5.4.2.1.7. RoadServiceArea
RoadServiceArea

Subtype of:

TransportArea

Definition:

Surface annexed to a road and devoted to offer particular services for it.

Description:

EXAMPLES Gas station, rest area, toll area.

Stereotypes:

«featureType»
5.4.2.1.8. RoadServiceType
RoadServiceType

Subtype of:

TransportProperty

Definition:

Description of the type of road service area and the available facilities.

Stereotypes:

«featureType»

Attribute: availableFacility

Value type:

ServiceFacilityValue

Definition:

Facility that is available for a given road service area.

Multiplicity:

0..*

Attribute: type

Value type:

RoadServiceTypeValue

Definition:

Type of road service area.

Multiplicity:

1

Constraint: Applies to road service areas only

Natural language:

This property can only be associated with a spatial object of the type RoadServiceArea or RoadNode (when formOfRoadNode=roadServiceArea).

OCL:

inv: networkRef.element.oclIsKindOf(RoadServiceArea) or (networkRef.element.oclIsKindOf(RoadNode) and networkRef.element. formOfRoadNode = FormOfRoadNodeValue::roadServiceArea)
5.4.2.1.9. RoadSurfaceCategory
RoadSurfaceCategory

Subtype of:

TransportProperty

Definition:

Specification of the state of the surface of the associated Road Element. Indicates whether a road is paved or unpaved.

Description:

SOURCE [GDF3, Euroroads].

Stereotypes:

«featureType»

Attribute: surfaceCategory

Value type:

RoadSurfaceCategoryValue

Definition:

Type of road surface.

Multiplicity:

1

Constraint: Applies to road transport elements only

Natural language:

This property can only be associated with a spatial object that is part of a road transport network.

OCL:

inv: networkRef.element.oclIsKindOf(Road) or networkRef.element.oclIsKindOf(ERoad) or networkRef.element.oclIsKindOf(RoadLink) or networkRef.element.oclIsKindOf(RoadLinkSequence) or networkRef.element.oclIsKindOf(RoadNode) or networkRef.element.oclIsKindOf(RoadArea) or networkRef.element.oclIsKindOf(RoadServiceArea) or networkRef.element.oclIsKindOf(VehicleTrafficArea)
5.4.2.1.10. RoadWidth
RoadWidth

Subtype of:

TransportProperty

Definition:

The width of the road, measured as an average value.

Description:

SOURCE [Euroroads].

Stereotypes:

«featureType»

Attribute: measuredRoadPart

Value type:

RoadPartValue

Definition:

Indicates to which part of a road the value for the attribute 'width' applies.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: width

Value type:

Measure

Definition:

Road width value.

Multiplicity:

1

Constraint: Applies to road transport elements only

Natural language:

This property can only be associated with a spatial object that is part of a road transport network.

OCL:

inv: networkRef.element.oclIsKindOf(Road) or networkRef.element.oclIsKindOf(ERoad) or networkRef.element.oclIsKindOf(RoadLink) or networkRef.element.oclIsKindOf(RoadLinkSequence) or networkRef.element.oclIsKindOf(RoadNode) or networkRef.element.oclIsKindOf(RoadArea) or networkRef.element.oclIsKindOf(RoadServiceArea) or networkRef.element.oclIsKindOf(VehicleTrafficArea)
5.4.2.1.11. SpeedLimit
SpeedLimit

Subtype of:

TransportProperty

Definition:

Limit for the speed of a vehicle on a road..

Description:

SOURCE [Euroroads].

Stereotypes:

«featureType»

Attribute: areaCondition

Value type:

AreaConditionValue

Definition:

Speed limit is dependent on environmental circumstances.

Description:

SOURCE [Euroroads].

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: direction

Value type:

LinkDirectionValue

Definition:

Indicates which direction the speed limit is valid for.

Description:

SOURCE [Euroroads].
NOTE This attribute only applies when the property is associated with a road link or road link sequence.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: laneExtension

Value type:

Integer

Definition:

Number of lanes including the start lane counted from the right hand side for which the speed limit applies.

Description:

SOURCE [Euroroads].
NOTE This attribute only applies when the property is associated with a road link or road link sequence.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: speedLimitMinMaxType

Value type:

SpeedLimitMinMaxValue

Definition:

Indicates if the speed limit is maximum or minimum and if it is recommended.

Description:

SOURCE [Euroroads].

Multiplicity:

1

Attribute: speedLimitSource

Value type:

SpeedLimitSourceValue

Definition:

Source for speed limit.

Description:

SOURCE [Euroroads].

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: speedLimitValue

Value type:

Velocity

Definition:

Value for speed limit.

Description:

SOURCE [Euroroads].

Multiplicity:

1

Attribute: startLane

Value type:

Integer

Definition:

Start lane counted from the right side for which speed limit applies.

Description:

SOURCE [Euroroads].
NOTE This attribute only applies when the property is associated with a road link or road link sequence.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: validityPeriod

Value type:

TM_Period

Definition:

Period during which the speed limit is valid.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: vehicleType

Value type:

VehicleTypeValue

Definition:

Vehicle type the speed limit is restricted to.

Description:

SOURCE Adapted from [Euroroads].

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: weatherCondition

Value type:

WeatherConditionValue

Definition:

Weather condition the speed limit is dependent on.

Description:

SOURCE Adapted from [Euroroads].

Multiplicity:

0..1

Stereotypes:

«voidable»

Constraint: Applies to road transport elements only

Natural language:

This property can only be associated with a spatial object that is part of a road transport network.

OCL:

inv: networkRef.element.oclIsKindOf(Road) or networkRef.element.oclIsKindOf(ERoad) or networkRef.element.oclIsKindOf(RoadLink) or networkRef.element.oclIsKindOf(RoadLinkSequence) or networkRef.element.oclIsKindOf(RoadNode) or networkRef.element.oclIsKindOf(RoadArea) or networkRef.element.oclIsKindOf(RoadServiceArea) or networkRef.element.oclIsKindOf(VehicleTrafficArea)
5.4.2.1.12. VehicleTrafficArea
VehicleTrafficArea

Subtype of:

TransportArea

Definition:

Surface that represents the part of a road which is used for the normal traffic of vehicles.

Stereotypes:

«featureType»
5.4.2.1.13. Road
Road

Subtype of:

TransportLinkSet

Definition:

A collection of road link sequences and/or individual road links that are characterized by one or more thematic identifiers and/or properties.

Description:

EXAMPLE Examples are roads characterized by a specific identification code, used by road management authorities or tourist routes, identified by a specific name.

Stereotypes:

«featureType»

Attribute: localRoadCode

Value type:

CharacterString

Definition:

Identification code assigned to the road by the local road authority.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: nationalRoadCode

Value type:

CharacterString

Definition:

The national number of the road.

Description:

SOURCE [Euroroads].

Multiplicity:

0..1

Stereotypes:

«voidable»
5.4.2.1.14. RoadArea
RoadArea

Subtype of:

TransportArea

Definition:

Surface which extends to the limits of a road, including vehicular areas and other parts of it.

Description:

EAXMPLE Pedestrian areas.

Stereotypes:

«featureType»
5.4.2.1.15. RoadLink
RoadLink

Subtype of:

TransportLink

Definition:

A linear spatial object that describes the geometry and connectivity of a road network between two points in the network. Road links can represent paths, bicycle roads, single carriageways, multiple carriageway roads and even fictitious trajectories across traffic squares.

Stereotypes:

«featureType»
5.4.2.1.16. RoadNode
RoadNode

Subtype of:

TransportNode

Definition:

A point spatial object that is used to either represent connectivity between two road links or to represent a significant spatial object such as a services station or roundabout.

Stereotypes:

«featureType»

Attribute: formOfRoadNode

Value type:

FormOfRoadNodeValue

Definition:

Description of the function of a road node in the road transport network.

Multiplicity:

1

Stereotypes:

«voidable»
5.4.2.2. Code lists
5.4.2.2.1. AreaConditionValue
AreaConditionValue

Definition:

Speed limit restriction depending on the area.

Description:

SOURCE [Euroroads].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AreaConditionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.2. RoadPartValue
RoadPartValue

Definition:

Indication to which part of a road the value of a measurement applies.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FormOfRoadNodeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.3. RoadSurfaceCategoryValue
RoadSurfaceCategoryValue

Definition:

Values to indicate whether a road is paved or not paved.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RoadSurfaceCategoryValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.4. SpeedLimitSourceValue
SpeedLimitSourceValue

Definition:

Possible sources for speed limits.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/SpeedLimitSourceValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.5. VehicleTypeValue
VehicleTypeValue

Definition:

Possible types of vehicles.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/VehicleTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.6. WeatherConditionValue
WeatherConditionValue

Definition:

Values to indicate weather conditions that affect speed limits.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/WeatherConditionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.7. FormOfRoadNodeValue
FormOfRoadNodeValue

Definition:

Functions of road nodes within Euroroads.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FormOfRoadNodeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.8. FormOfWayValue
FormOfWayValue

Definition:

Classification based on the physical properties of the road link.

Description:

SOURCE Based on [Euroroads].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FormOfWayValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.9. RoadServiceTypeValue
RoadServiceTypeValue

Definition:

Types of road service areas.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RoadServiceTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.10. ServiceFacilityValue
ServiceFacilityValue

Definition:

Possible service facilities available at a road service area.

Extensibility:

none

Identifier:

https://inspire.ec.europa.eu/codelist/ServiceFacilityValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.11. MinMaxLaneValue
MinMaxLaneValue

Definition:

Values to indicate whether number of lanes are counted as the maximum, minimum or average number.

Description:

SOURCE Adapted from [Euroroads].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/MinMaxLaneValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.12. SpeedLimitMinMaxValue
SpeedLimitMinMaxValue

Definition:

Possible values to indicate the nature of a speed limit.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/SpeedLimitMinMaxValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.2.13. FunctionalRoadClassValue
FunctionalRoadClassValue

Definition:

Values for the functional road classification. This classification is based on the importance of the role that the road performs in the road network.

Description:

SOURCE Adapted from [GDF, EuroRoadS].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FunctionalRoadClassValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.4.2.3. Imported types (informative)

This section lists definitions for feature types, data types and code lists that are defined in other application schemas. The section is purely informative and should help the reader understand the feature catalogue presented in the previous sections. For the normative documentation of these types, see the given references.

5.4.2.3.1. CharacterString
CharacterString

Package:

Text

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.4.2.3.2. GeographicalName
GeographicalName

Package:

Geographical Names

Reference:

INSPIRE Data specification on Geographical Names [DS-D2.8.I.3]

Definition:

Proper noun applied to a real world entity.
5.4.2.3.3. Integer
Integer

Package:

Numerics

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.4.2.3.4. LinkDirectionValue
LinkDirectionValue

Package:

Network

Reference:

INSPIRE Data Specifications – Base Models – Generic Network Model, version 1.0 [DS-D2.10.1]

Definition:

List of values for directions relative to a link
5.4.2.3.5. Measure
Measure

Package:

ProductionAndIndustrialFacilitiesExtension

Reference:

INSPIRE Data specification on Production and Industrial Facilities [DS-D2.8.III.8]

Definition:

Declared or measured quantity of any kind of physical entity.
5.4.2.3.6. TM_Period
TM_Period

Package:

Temporal Objects

Reference:

Geographic information — Temporal schema [ISO 19108:2002/Cor 1:2006]
5.4.2.3.7. TransportArea
TransportArea (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

Surface that represents the spatial extent of an element of a transport network.
5.4.2.3.8. TransportLink
TransportLink (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object that describes the geometry and connectivity of a transport network between two points in the network.
5.4.2.3.9. TransportLinkSequence
TransportLinkSequence (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object, composed of an ordered collection of transport links, which represents a continuous path in the transport network without any branches. The element has a defined beginning and end and every position on the transport link sequence is identifiable with one single parameter such as length. It describes an element of the transport network, characterized by one or more thematical identifiers and/or properties.
5.4.2.3.10. TransportLinkSet
TransportLinkSet (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A collection of transport link sequences and or individual transport links that has a specific function or significance in a transport network.

Description:

NOTE
This spatial object type supports the aggregation of links to form objects with branches, loops, parallel sequences of links, gaps, etc.

EXAMPLE
A dual carriageway road, as a collection of the two link sequences that represent each carriageway.
5.4.2.3.11. TransportNode
TransportNode (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A point spatial object which is used for connectivity.

Description:

Nodes are found at either end of the TransportLink.
5.4.2.3.12. TransportProperty
TransportProperty (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A reference to a property that falls upon the network. This property can apply to the whole of the network element it is associated with or - for linear spatial objects - be described using linear referencing.
5.4.2.3.13. Velocity
Velocity

Package:

Units of Measure

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]

5.5. Application schema Rail Transport Networks

5.5.1. Description

5.5.1.1. Narrative description

The Rail Transport Networks application schema (Rail Schema) employs a link and node structure to represent the rail tracks used for transportation in the form of a linear network. The Rail Schema inherits classes from the Common Transport Schema and also creates its own classes to describe properties of the rail network such as Ownership and restrictions that can apply to whole sections of the network element or subsections that can be described using linear referencing.

The primary aspects modelled for rail network elements are:

  • Spatial. Geometric (point, line and area (topographic)) representation of various elements that are parts of a network. Typically, the network is handled as a network of connected linear elements (links) with points (nodes) at the ends of the lines (at junctions, rail ends etc). Also real objects with a function in a network may be represented in the dataset. Network connectivity within the rail network is essential but between elements in the other networks is an optional spatial aspect.

  • Temporal. All elements in a network may have a temporal validity (i.e. description of when the network element exists in the real world) and also optional information on when data was entered, modified or deleted in the dataset.

  • Thematic. The Rail Schema can be thematically displayed via several of the attributes defined within the specification such as railwayGauge or owningAuthority.

5.5.1.2. UML Overview
image

Figure 20 – UML class diagram: Overview of the Rail Transport Networks application schema

image

Figure 21 – UML class diagram: Railway Transport Networks Spatial object types – Links, Nodes and Areas

image

Figure 22 – UML class diagram: Railway Transport Networks Spatial object types – Transport Properties

RailTransportNetwork

Figure 23 – Overview of the main Rail Transport Networks objects

image

Figure 24 – UML class diagram: Railway Transport Networks Code lists

5.5.1.3. Consistency between spatial data sets

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.3) apply to the corresponding specialized elements/classes in the Rail transport networks.

5.5.1.4. Identifier management

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.4) apply to the corresponding specialized elements/classes in the Rail transport networks.

5.5.1.5. Modelling of object references

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.5) apply to the corresponding specialized elements/classes in the Rail transport networks.

5.5.1.6. Geometry representation

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.6) apply to the corresponding specialized elements/classes in the Rail transport networks.

5.5.1.7. Temporality representation

All attributes describing the lifespan of spatial objects or the phenomena in the real world they describe are inherited from the Common Transport Elements application schema. Refer to section 5.3.1.7 for more information.

5.5.2. Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Railway Transport Network

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

DesignSpeed

Railway Transport Network

«featureType»

FormOfRailwayNodeValue

Railway Transport Network

«codeList»

NominalTrackGauge

Railway Transport Network

«featureType»

NumberOfTracks

Railway Transport Network

«featureType»

RailwayArea

Railway Transport Network

«featureType»

RailwayElectrification

Railway Transport Network

«featureType»

RailwayLine

Railway Transport Network

«featureType»

RailwayLink

Railway Transport Network

«featureType»

RailwayLinkSequence

Railway Transport Network

«featureType»

RailwayNode

Railway Transport Network

«featureType»

RailwayStationArea

Railway Transport Network

«featureType»

RailwayStationCode

Railway Transport Network

«featureType»

RailwayStationNode

Railway Transport Network

«featureType»

RailwayType

Railway Transport Network

«featureType»

RailwayTypeValue

Railway Transport Network

«codeList»

RailwayUse

Railway Transport Network

«featureType»

RailwayUseValue

Railway Transport Network

«codeList»

RailwayYardArea

Railway Transport Network

«featureType»

RailwayYardNode

Railway Transport Network

«featureType»
5.5.2.1. Spatial object types
5.5.2.1.1. DesignSpeed
DesignSpeed

Subtype of:

TransportProperty

Definition:

The specification of the maximum speed to which a railway line is designed for.

Stereotypes:

«featureType»

Attribute: speed

Value type:

Velocity

Definition:

The specification of the maximum speed to which a railway line is designed for.

Multiplicity:

1

Constraint: Applies to railway transport classes only

Natural language:

This property can only be associated with a spatial object that is part of a railway transport network.

OCL:

inv: networkRef.element.oclIsKindOf(RailwayArea) or networkRef.element.oclIsKindOf(RailwayYardArea) or networkRef.element.oclIsKindOf(RailwayStationArea) or networkRef.element.oclIsKindOf(RailwayLine) or networkRef.element.oclIsKindOf(RailwayLinkSequence) or networkRef.element.oclIsKindOf(RailwayLink) or networkRef.element.oclIsKindOf(RailwayNode)
5.5.2.1.2. NominalTrackGauge
NominalTrackGauge

Subtype of:

TransportProperty

Definition:

The nominal distance between the two outer rails (gauge) of a railway track.

Stereotypes:

«featureType»

Attribute: nominalGauge

Value type:

Measure

Definition:

A single value that identifies the track gauge.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: nominalGaugeCategory

Value type:

TrackGaugeCategoryValue

Definition:

Provision of the gauge of a railway track as a fuzzy category with respect to the European standard nominal gauge.

Multiplicity:

0..1

Stereotypes:

«voidable»

Constraint: Applies to railway transport classes only

Natural language:

This property can only be associated with a spatial object that is part of a railway transport network.

OCL:

inv: networkRef.element.oclIsKindOf(RailwayArea) or networkRef.element.oclIsKindOf(RailwayYardArea) or networkRef.element.oclIsKindOf(RailwayStationArea) or networkRef.element.oclIsKindOf(RailwayLine) or networkRef.element.oclIsKindOf(RailwayLinkSequence) or networkRef.element.oclIsKindOf(RailwayLink) or networkRef.element.oclIsKindOf(RailwayNode)
5.5.2.1.3. NumberOfTracks
NumberOfTracks

Subtype of:

TransportProperty

Definition:

The number of tracks for a railway stretch.

Description:

This is dependent on the resolution of the data.

Stereotypes:

«featureType»

Attribute: minMaxNumberOfTracks

Value type:

MinMaxTrackValue

Definition:

Indicates whether the number of tracks are counted as minimum or maximum value.

Description:

NOTE This attribute only applies when the value in numberOfTracks is not an exact value.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: numberOfTracks

Value type:

Integer

Definition:

The number of tracks present.

Multiplicity:

1

Constraint: Applies to railway transport classes only

Natural language:

This property can only be associated with a spatial object that is part of a railway transport network.

OCL:

inv: networkRef.element.oclIsKindOf(RailwayArea) or networkRef.element.oclIsKindOf(RailwayYardArea) or networkRef.element.oclIsKindOf(RailwayStationArea) or networkRef.element.oclIsKindOf(RailwayLine) or networkRef.element.oclIsKindOf(RailwayLinkSequence) or networkRef.element.oclIsKindOf(RailwayLink) or networkRef.element.oclIsKindOf(RailwayNode)
5.5.2.1.4. RailwayArea
RailwayArea

Subtype of:

TransportArea

Definition:

Surface occupied by a railway track, including ballast.

Stereotypes:

«featureType»
5.5.2.1.5. RailwayElectrification
RailwayElectrification

Subtype of:

TransportProperty

Definition:

Indication whether the railway is provided with an electric system to power vehicles moving along it.

Stereotypes:

«featureType»

Attribute: electrified

Value type:

Boolean

Definition:

Inidicates whether the railway is provided with an electric system to power vehicles moving along it.

Multiplicity:

1

Constraint: Applies to railway transport classes only

Natural language:

This property can only be associated with a spatial object that is part of a railway transport network.

OCL:

inv: networkRef.element.oclIsKindOf(RailwayArea) or networkRef.element.oclIsKindOf(RailwayYardArea) or networkRef.element.oclIsKindOf(RailwayStationArea) or networkRef.element.oclIsKindOf(RailwayLine) or networkRef.element.oclIsKindOf(RailwayLinkSequence) or networkRef.element.oclIsKindOf(RailwayLink) or networkRef.element.oclIsKindOf(RailwayNode)
5.5.2.1.6. RailwayLine
RailwayLine

Subtype of:

TransportLinkSet

Definition:

A collection of railway link sequences and or individual railway links that are characterized by one or more thematical identifiers and/or properties.

Description:

EXAMPLE Railway lines characterized by a specific identification code, used by railroad companies or tourist railways, identified by a specific name.

Stereotypes:

«featureType»

Attribute: railwayLineCode

Value type:

CharacterString

Definition:

A code assigned to a railway line which is unique within a Member State.

Multiplicity:

1

Stereotypes:

«voidable»
5.5.2.1.7. RailwayLink
RailwayLink

Subtype of:

TransportLink

Definition:

A linear spatial object that describes the geometry and connectivity of a railway network between two points in the network.

Description:

NOTE Railway links can be used to represent stretches of railway with one or multiple tracks.

Stereotypes:

«featureType»
5.5.2.1.8. RailwayLinkSequence
RailwayLinkSequence

Subtype of:

TransportLinkSequence

Definition:

A linear spatial object, composed of an ordered collection of railway links, which represents a continuous path in a railway network without any branches. The element has a defined beginning and end and every position on the railway link sequence is identifiable with one single parameter such as length. It describes an element of the railway network, characterized by one or more thematical identifiers and/or properties.

Stereotypes:

«featureType»
5.5.2.1.9. RailwayNode
RailwayNode

Subtype of:

TransportNode

Definition:

A point spatial object which represents a significant point along the railway network or defines an intersection of railway tracks used to describe its connectivity.

Stereotypes:

«featureType»

Attribute: formOfNode

Value type:

FormOfRailwayNodeValue

Definition:

The function of a railway node within the railway network.

Multiplicity:

1

Stereotypes:

«voidable»
5.5.2.1.10. RailwayStationArea
RailwayStationArea

Subtype of:

TransportArea

Definition:

An area spatial object which is used to represent the topographical limits of the facilities of a railway station (buildings, railway yards, installations and equipment) devoted to carry out railway station operations.

Stereotypes:

«featureType»
5.5.2.1.11. RailwayStationCode
RailwayStationCode

Subtype of:

TransportProperty

Definition:

The unique code assigned to a railway station.

Stereotypes:

«featureType»

Attribute: stationCode

Value type:

CharacterString

Definition:

A unique code assigned to a railway station.

Multiplicity:

1

Constraint: Applies to Railway Transport classes only

Natural language:

This property can only be associated with a spatial object that is part of a railway transport network.

OCL:

inv: networkRef.element.oclIsKindOf(RailwayArea) or networkRef.element.oclIsKindOf(RailwayYardArea) or networkRef.element.oclIsKindOf(RailwayStationArea) or networkRef.element.oclIsKindOf(RailwayLine) or networkRef.element.oclIsKindOf(RailwayLinkSequence) or networkRef.element.oclIsKindOf(RailwayLink) or networkRef.element.oclIsKindOf(RailwayNode)
5.5.2.1.12. RailwayStationNode
RailwayStationNode

Subtype of:

RailwayNode

Definition:

A railway node which represents the location of a railway station along the railway network.

Stereotypes:

«featureType»

Attribute: numberOfPlatforms

Value type:

Integer

Definition:

A value indicating the number of platforms available at a railway station.

Multiplicity:

1

Stereotypes:

«voidable»

Constraint: formOfNode is always RailwayStop

Natural language:

For a railway station node, the value for the "formOfNode" attribute shall always be "RailwayStop".

OCL:

formOfNode = FormOfRailwayNodeValue::railwayStop
5.5.2.1.13. RailwayType
RailwayType

Subtype of:

TransportProperty

Definition:

The type of railway transport the line is designed for.

Stereotypes:

«featureType»

Attribute: type

Value type:

RailwayTypeValue

Definition:

The type of railway transport to which the line is designed for.

Multiplicity:

1

Constraint: Applies to railway transport classes only

Natural language:

This property can only be associated with a spatial object that is part of a railway transport network.

OCL:

inv: networkRef.element.oclIsKindOf(RailwayArea) or networkRef.element.oclIsKindOf(RailwayYardArea) or networkRef.element.oclIsKindOf(RailwayStationArea) or networkRef.element.oclIsKindOf(RailwayLine) or networkRef.element.oclIsKindOf(RailwayLinkSequence) or networkRef.element.oclIsKindOf(RailwayLink) or networkRef.element.oclIsKindOf(RailwayNode)
5.5.2.1.14. RailwayUse
RailwayUse

Subtype of:

TransportProperty

Definition:

The current use of the railway.

Stereotypes:

«featureType»

Attribute: use

Value type:

RailwayUseValue

Definition:

The current use of the railway.

Multiplicity:

1

Constraint: Applies to Railway Transport classes only

Natural language:

This property can only be associated with a spatial object that is part of a railway transport network.

OCL:

inv: networkRef.element.oclIsKindOf(RailwayArea) or networkRef.element.oclIsKindOf(RailwayYardArea) or networkRef.element.oclIsKindOf(RailwayStationArea) or networkRef.element.oclIsKindOf(RailwayLine) or networkRef.element.oclIsKindOf(RailwayLinkSequence) or networkRef.element.oclIsKindOf(RailwayLink) or networkRef.element.oclIsKindOf(RailwayNode)
5.5.2.1.15. RailwayYardArea
RailwayYardArea

Subtype of:

TransportArea

Definition:

An area spatial object which is used to represent the topographical limits of a railway yard. DEFINITION Railway yard: An area crossed by a number of parallel railway tracks (usually more than two) interconnected between them, which are used to stop trains in order to load / unload freight without interrupting the traffic of a main railway line.

Stereotypes:

«featureType»
5.5.2.1.16. RailwayYardNode
RailwayYardNode

Subtype of:

RailwayNode

Definition:

A railway node which occurs within a railway yard area. DEFINTION Railway yard: An area crossed by a number of parallel railway tracks (usually more than two) interconnected between them, which are used to stop trains in order to load / unload freight without interrupting the traffic of a main railway line.

Stereotypes:

«featureType»

Constraint: formOfNode is always RailwayStop

Natural language:

For a railway yard node, the value for the "formOfNode" attribute shall always be "RailwayStop".

OCL:

formOfNode = FormOfRailwayNodeValue::railwayStop
5.5.2.2. Code lists
5.5.2.2.1. FormOfRailwayNodeValue
FormOfRailwayNodeValue

Definition:

The possible functions of a railway node within the railway network.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FormOfRailwayNodeValue

Values:

The allowed values for this code list comprise only the values specified in Annex C .
5.5.2.2.2. RailwayTypeValue
RailwayTypeValue

Definition:

The possible types of railway transport.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RailwayTypeValue

Values:

The allowed values for this code list comprise only the values specified in Annex C .
5.5.2.2.3. RailwayUseValue
RailwayUseValue

Definition:

The possible uses of railways.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RailwayUseValue

Values:

The allowed values for this code list comprise only the values specified in Annex C .
5.5.2.2.4. MinMaxTrackValue
MinMaxTrackValue

Definition:

Values to indicate whether number of tracks are counted as the maximum, minimum or average number.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/MinMaxTrackValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.5.2.2.5. TrackGaugeCategoryValue
TrackGaugeCategoryValue

Definition:

The possible categories of railways concerning its nominal track gauge.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/TrackGaugeCategoryValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.5.2.3. Imported types (informative)

This section lists definitions for feature types, data types and code lists that are defined in other application schemas. The section is purely informative and should help the reader understand the feature catalogue presented in the previous sections. For the normative documentation of these types, see the given references.

5.5.2.3.1. Boolean
Boolean

Package:

Truth

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.5.2.3.2. CharacterString
CharacterString

Package:

Text

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.5.2.3.3. Integer
Integer

Package:

Numerics

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.5.2.3.4. Measure
Measure

Package:

ProductionAndIndustrialFacilitiesExtension

Reference:

INSPIRE Data specification on Production and Industrial Facilities [DS-D2.8.III.8]

Definition:

Declared or measured quantity of any kind of physical entity.
5.5.2.3.5. TransportArea
TransportArea (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

Surface that represents the spatial extent of an element of a transport network.
5.5.2.3.6. TransportLink
TransportLink (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object that describes the geometry and connectivity of a transport network between two points in the network.
5.5.2.3.7. TransportLinkSequence
TransportLinkSequence (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object, composed of an ordered collection of transport links, which represents a continuous path in the transport network without any branches. The element has a defined beginning and end and every position on the transport link sequence is identifiable with one single parameter such as length. It describes an element of the transport network, characterized by one or more thematical identifiers and/or properties.
5.5.2.3.8. TransportLinkSet
TransportLinkSet (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A collection of transport link sequences and or individual transport links that has a specific function or significance in a transport network.

Description:

NOTE
This spatial object type supports the aggregation of links to form objects with branches, loops, parallel sequences of links, gaps, etc.

EXAMPLE
A dual carriageway road, as a collection of the two link sequences that represent each carriageway.
5.5.2.3.9. TransportNode
TransportNode (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A point spatial object which is used for connectivity.

Description:

Nodes are found at either end of the TransportLink.
5.5.2.3.10. TransportProperty
TransportProperty (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A reference to a property that falls upon the network. This property can apply to the whole of the network element it is associated with or - for linear spatial objects - be described using linear referencing.
5.5.2.3.11. Velocity
Velocity

Package:

Units of Measure

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]

5.6. Application schema Cable Transport Networks

5.6.1. Description

5.6.1.1. Narrative description

The Cable Transport Networks application schema (Cable Schema) employs a link and node structure to represent the cableways used for transportation of hung vehicles in the form of a linear network. It can play an important role especially in isolated areas having none or difficult access by means of other types of transport (e.g. mountain areas). The Cable Schema inherits classes from the Common Transport Elements application schema, including the possibility to create classes to describe properties of the cableway network and restrictions that can apply to whole sections of the network element or subsections that can be described using linear referencing. This type of network is modelled in a basic way in the specifications.

The primary aspects modelled for cableway network elements are:

  • Spatial. Geometric (point and line) representation of various elements that are parts of a network. Typically, the network is handled as a network of connected linear elements (links) with points (nodes) at the ends of the lines (at junctions, cable ends etc). Also real objects with a function in a network may be represented in the dataset. Network connectivity within the cable network is essential but between elements in the other networks is an optional spatial aspect.

  • Temporal. All elements in a network may have a temporal validity (i.e. description of when the network element exists in the real world) and also optional information on when data was entered, modified or deleted in the dataset.

  • Thematic. The Cable Schema can be thematically enriched through the use of Transport Properties as defined in the Common Transport Elements application schema.

5.6.1.2. UML Overview
image

Figure 25 – UML class diagram: Overview of the Cableway Transport Networks application schema

image

Figure 26 – UML class diagram: Cable Transport Networks Spatial object types

CableTransportNetwork

Figure 27 – Overview of the main Cable Transport Networks objects

image

Figure 28 – UML class diagram: Cable Transport Networks code lists

5.6.1.3. Consistency between spatial data sets

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.3) apply to the corresponding specialized elements/classes in the Cable transport networks.

5.6.1.4. Identifier management

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section5.3.1.4) apply to the corresponding specialized elements/classes in the Cable transport networks.

5.6.1.5. Modelling of object references

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.5) apply to the corresponding specialized elements/classes in the Cable transport networks.

5.6.1.6. Geometry representation

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.6) apply to the corresponding specialized elements/classes in the Cable transport networks.

5.6.1.7. Temporality representation

All attributes describing the lifespan of spatial objects or the phenomena in the real world they describe are inherited from the Common Transport Elements application schema. Refer to section 5.3.1.7 for more information.

5.6.2. Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Cable Transport Network

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

CablewayLink

Cable Transport Network

«featureType»

CablewayLinkSequence

Cable Transport Network

«featureType»

CablewayLinkSet

Cable Transport Network

«featureType»

CablewayNode

Cable Transport Network

«featureType»

CablewayTypeValue

Cable Transport Network

«codeList»
5.6.2.1. Spatial object types
5.6.2.1.1. CablewayLink
CablewayLink

Subtype of:

TransportLink

Definition:

Linear spatial object that describes the geometry and connectivity of a cable network between two points in a cableway transport network.

Description:

NOTE Cableway transport is a form of transport based on a cable suspended normally from a set of consecutive towers.

Stereotypes:

«featureType»

Attribute: cablewayType

Value type:

CablewayTypeValue

Definition:

The type of a cableway transport.

Multiplicity:

1

Stereotypes:

«voidable»
5.6.2.1.2. CablewayLinkSequence
CablewayLinkSequence

Subtype of:

TransportLinkSequence

Definition:

An ordered collection of cableway links that are characterized by one or more thematic identifiers and/or properties.

Stereotypes:

«featureType»
5.6.2.1.3. CablewayLinkSet
CablewayLinkSet

Subtype of:

TransportLinkSet

Definition:

A collection of cableway link sequences and or individual cableway links that has a specific function or significance in a cable transport network.

Stereotypes:

«featureType»
5.6.2.1.4. CablewayNode
CablewayNode

Subtype of:

TransportNode

Definition:

A point spatial object that is used to represent connectivity between two consecutive cableway links.

Stereotypes:

«featureType»
5.6.2.2. Code lists
5.6.2.2.1. CablewayTypeValue
CablewayTypeValue

Definition:

The possible types of cableway transport.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/CablewayTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.6.2.3. Imported types (informative)

This section lists definitions for feature types, data types and code lists that are defined in other application schemas. The section is purely informative and should help the reader understand the feature catalogue presented in the previous sections. For the normative documentation of these types, see the given references.

5.6.2.3.1. TransportLink
TransportLink (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object that describes the geometry and connectivity of a transport network between two points in the network.
5.6.2.3.2. TransportLinkSequence
TransportLinkSequence (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object, composed of an ordered collection of transport links, which represents a continuous path in the transport network without any branches. The element has a defined beginning and end and every position on the transport link sequence is identifiable with one single parameter such as length. It describes an element of the transport network, characterized by one or more thematical identifiers and/or properties.
5.6.2.3.3. TransportLinkSet
TransportLinkSet (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A collection of transport link sequences and or individual transport links that has a specific function or significance in a transport network.

Description:

NOTE
This spatial object type supports the aggregation of links to form objects with branches, loops, parallel sequences of links, gaps, etc.

EXAMPLE
A dual carriageway road, as a collection of the two link sequences that represent each carriageway.
5.6.2.3.4. TransportNode
TransportNode (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A point spatial object which is used for connectivity.

Description:

Nodes are found at either end of the TransportLink.

5.7. Application schema Water Transport Networks

5.7.1. Description

5.7.1.1. Narrative description

The Water transport network schema employs a link and node structure to represent navigable waterways and ports within water bodies (main marine waterways and ships routeing systems - traffic separation schemes - at the sea, and inland waterways defined across rivers and canals) allowing transportation in the form of a linear network. The water transport network reuse the centreline geometry of the Hydrography theme’s network (hydrographic network) of rivers and canals as the basis for most inland water transport. However, when this is not enough to describe it properly, specific water transport network’s centrelines can also be used (waterway links), in combination to the previous ones, in order to complete the network. The water schema also inherits classes from the Common Transport Schema and also creates its own classes to describe properties of the water network such as water traffic flow direction and any restrictions that can apply to whole sections of the network element or subsections that can be described using linear referencing.

The primary aspects modelled for water network elements are:

  • Spatial. Geometric (point, line and area (topographic)) representation of various elements that are parts of a network. Typically, the network is handled as a network of connected linear elements (links) with points (nodes) at the ends of the lines (at junctions, ports etc). Also real objects with a function in a network may be represented in the dataset. Network connectivity within the water network is essential but between elements in the other networks is an optional spatial aspect.

  • Temporal. All elements in a network may have a temporal validity (i.e. description of when the network element exists in the real world) and also optional information on when data was entered, modified or deleted in the dataset.

  • Thematic. The water schema can be thematically displayed via several of the attributes defined within the specification such as CEMTClass.

5.7.1.2. UML Overview
image

Figure 29 – UML class diagram: Overview of the Water Transport Networks application schema

image

Figure 30 – UML class diagram: Water Transport Networks Spatial object types – Links and Areas

image

Figure 31 – UML class diagram: Water Transport Networks Spatial object types – Nodes

image

Figure 32 – UML class diagram: Water Transport Networks Spatial object types – Transport Points

image

Figure 33 – UML class diagram: Water Transport Networks Spatial object types – Transport Properties

WaterTransportNetwork_1
WaterTransportNetwork_2

Figure 34 – Overview of the main Water Transport Networks objects

image

Figure 35 – UML class diagram: Water Transport Networks code lists

5.7.1.3. Consistency between spatial data sets

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.3) apply to the corresponding specialized elements/classes in the Water transport networks.

5.7.1.4. Identifier management

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.4) apply to the corresponding specialized elements/classes in the Water transport networks.

5.7.1.5. Modelling of object references

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.5) apply to the corresponding specialized elements/classes in the Water transport networks.

In particular the Water transport networks theme reuses the existing water network in the Hydrography theme for the majority of the inland Water transport networks geometry. This is a case of object referencing.

📕

IR Requirement
Annex II, Section 7.9.4
Theme-specific Requirements – Modelling of object references

The Water transport networks shall re-use, where it exists and is practicable, the water network centreline geometry of the Hydrography theme. Therefore, object referencing shall be used to link the water transport course with the existing water network geometry in the Hydrography theme.
5.7.1.6. Geometry representation

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.6) apply to the corresponding specialized elements/classes in the Water transport networks.

5.7.1.7. Temporality representation

All attributes describing the lifespan of spatial objects or the phenomena in the real world they describe are inherited from the Common Transport Elements application schema. Refer to section 5.3.1.7 for more information.

5.7.2. Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Water Transport Network

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

Beacon

Water Transport Network

«featureType»

Buoy

Water Transport Network

«featureType»

CEMTClass

Water Transport Network

«featureType»

ConditionOfWaterFacility

Water Transport Network

«featureType»

FairwayArea

Water Transport Network

«featureType»

FerryCrossing

Water Transport Network

«featureType»

FerryUse

Water Transport Network

«featureType»

FerryUseValue

Water Transport Network

«codeList»

FormOfWaterwayNodeValue

Water Transport Network

«codeList»

InlandWaterway

Water Transport Network

«featureType»

MarineWaterway

Water Transport Network

«featureType»

PortArea

Water Transport Network

«featureType»

PortNode

Water Transport Network

«featureType»

RestrictionForWaterVehicles

Water Transport Network

«featureType»

TrafficSeparationScheme

Water Transport Network

«featureType»

TrafficSeparationSchemeArea

Water Transport Network

«featureType»

TrafficSeparationSchemeCrossing

Water Transport Network

«featureType»

TrafficSeparationSchemeLane

Water Transport Network

«featureType»

TrafficSeparationSchemeRoundabout

Water Transport Network

«featureType»

TrafficSeparationSchemeSeparator

Water Transport Network

«featureType»

WaterLinkSequence

Water Transport Network

«featureType»

WaterNode

Water Transport Network

«featureType»

WaterTrafficFlowDirection

Water Transport Network

«featureType»

Waterway

Water Transport Network

«featureType»

WaterwayLink

Water Transport Network

«featureType»

WaterwayNode

Water Transport Network

«featureType»
5.7.2.1. Spatial object types
5.7.2.1.1. Beacon
Beacon

Subtype of:

TransportPoint

Definition:

A prominent specially constructed object forming a conspicuous mark as a fixed aid to navigation, or for use in hydrographic survey.

Description:

SOURCE [S-32 - IHO International Hydrographic Dictionary].

Stereotypes:

«featureType»
5.7.2.1.2. Buoy
Buoy

Subtype of:

TransportPoint

Definition:

A floating object moored to the bottom in a particular (charted) place, as an aid to navigation or for other specific purposes.

Description:

SOURCE [S-32 - IHO International Hydrographic Dictionary]

NOTE Navigational buoys may be classified according to: (a) their shape, appearance, or construction, such as barrel, can, cask, conical, cylindrical, dan, keg, nun, pillar, spar, spherical, or topmark buoy; (b) their colour, such as black, chequered, green, red buoy; (c) their location, such as bifurcation, fairway, junction, mid-channel, middle-ground, or turning buoy; (d) the various kinds of hazards or dangers to navigation which they mark, such as bar, isolated danger, fish trap, obstruction, spoil ground, telegraph or wreck buoy; (e) their particular purpose or use, such as anchor, anchorage, compass adjustment, dredging, farewell (or landfall), marker, quarantine, station (or watch), or warping buoy. [S-32 - IHO International Hydrographic Dictionary].

Stereotypes:

«featureType»
5.7.2.1.3. CEMTClass
CEMTClass

Subtype of:

TransportProperty

Definition:

Classification of an inland waterway according to CEMT (European Conference of Ministers of Transport).

Stereotypes:

«featureType»

Attribute: CEMTClass

Value type:

CEMTClassValue

Definition:

Value indicating the classification of an Inland waterway according to CEMT (European Conference of Ministers of Transport).

Multiplicity:

1

Constraint: Applies to InlandWaterway only

Natural language:

This property can only be associated with a spatial object that is part of a water transport network.

OCL:

inv: networkRef.element.oclIsKindOf(InlandWaterway)
5.7.2.1.4. ConditionOfWaterFacility
ConditionOfWaterFacility

Subtype of:

ConditionOfFacility

Definition:

State of a water transport network element with regards to its completion and use.

Stereotypes:

«featureType»

Constraint: Applies to PortNode and PortArea only

Natural language:

This property can only be associated with a spatial object that is part of a water transport network.

OCL:

inv: networkRef.element.oclIsKindOf(PortArea) or networkRef.element.oclIsKindOf(PortNode)
5.7.2.1.5. FairwayArea
FairwayArea

Subtype of:

TransportArea

Definition:

The main travelled part of a waterway.

Description:

SOURCE [International Hydrographic Dictionary].

NOTE That part of a river, harbour and so on, where the main navigable channel for vessels of larger size lies. It is also the usual course followed by vessels entering or leaving harbours, called 'ship channel' [IHO Hidrographic Registry].

Stereotypes:

«featureType»
5.7.2.1.6. FerryCrossing
FerryCrossing

Subtype of:

Waterway

Definition:

A special waterway aimed at supporting the transport of passengers, vehicles or other cargo/freight across a water body, and which is normally used as a connection linking two or more nodes of a land based transport network.

Stereotypes:

«featureType»
5.7.2.1.7. FerryUse
FerryUse

Subtype of:

TransportProperty

Definition:

The type of transport carried out by a ferry crossing.

Stereotypes:

«featureType»

Attribute: ferryUse

Value type:

FerryUseValue

Definition:

Value indicating the type of transport carried out by a ferry crossing.

Multiplicity:

1..*

Constraint: Applies to FerryCrossing only

Natural language:

This property can only be associated with a spatial object that is part of a water transport network.

OCL:

inv: networkRef.element.oclIsKindOf(FerryCrossing)
5.7.2.1.8. InlandWaterway
InlandWaterway

Subtype of:

Waterway

Definition:

Waterway which is defined at inland continental waters.

Description:

EXAMPLE The inland waterways classified by the CEMT (European Conference of Ministers of Transport).

Stereotypes:

«featureType»
5.7.2.1.9. MarineWaterway
MarineWaterway

Subtype of:

Waterway

Definition:

Waterway which is defined at sea waters.

Stereotypes:

«featureType»

Attribute: deepWaterRoute

Value type:

Boolean

Definition:

Attribute which indicates if the maritime waterway is a deep water route. DEFINITION Deep water route: A route in a designated area within defined limits which has been accurately surveyed for clearance of sea bottom and submerged obstacles to a minimum indicated depth of water [S-32 - IHO International Hydrographic Dictionary].

Multiplicity:

1

Stereotypes:

«voidable»
5.7.2.1.10. PortArea
PortArea

Subtype of:

TransportArea

Definition:

An area spatial object which is used to represent the physical limits of all the facilities which constitute the terrestrial zone of a sea or inland port.

Stereotypes:

«featureType»
5.7.2.1.11. PortNode
PortNode

Subtype of:

WaterNode

Definition:

A point spatial object which is used to represent a sea or inland port in a simplified way, aproximately located at the bank of the waterbody where the port is placed.

Description:

NOTE It is used to connect the port with the rest of the water transport network, by means of the different waterway links which arrive to / depart from it.

Stereotypes:

«featureType»
5.7.2.1.12. RestrictionForWaterVehicles
RestrictionForWaterVehicles

Subtype of:

RestrictionForVehicles

Definition:

Restriction on vehicles on a water transport element.

Stereotypes:

«featureType»

Constraint: Applies to WaterwayLink and WaterwayNode only

Natural language:

This property can only be associated with a spatial object that is part of a water transport network.

OCL:

inv: networkRef.element.oclIsKindOf(WaterwayLink) or networkRef.element.oclIsKindOf(WaterwayNode)
5.7.2.1.13. TrafficSeparationScheme
TrafficSeparationScheme

Definition:

A scheme which aims at reducing the risk of collision in congested and/or converging areas by separating traffic moving in opposite, or nearly opposite, directions.

Description:

SOURCE [S-32 - IHO International Hydrographic Dictionary]

NOTE 1 Acronym: TSS.

NOTE 2 TSSs constitute main components of maritime routing measures for hydrographic transport.

Stereotypes:

«featureType»

Association role: component

Value type:

TrafficSeparationSchemeArea

Definition:

A component of a traffic separation scheme.

Multiplicity:

1..*

Association role: markerBuoy

Value type:

Buoy

Definition:

A marker forming part of a traffic separation scheme.

Multiplicity:

0..*

Association role: marineWaterRoute

Value type:

MarineWaterway

Definition:

The collection of marine waterways associated with a traffic separation scheme.

Multiplicity:

0..*

Association role: markerBeacon

Value type:

Beacon

Definition:

A marker forming part of a traffic separation scheme.

Multiplicity:

0..*
5.7.2.1.14. TrafficSeparationSchemeArea
TrafficSeparationSchemeArea (abstract)

Subtype of:

TransportArea

Definition:

An area spatial object forming part of a traffic separation scheme.

Stereotypes:

«featureType»
5.7.2.1.15. TrafficSeparationSchemeCrossing
TrafficSeparationSchemeCrossing

Subtype of:

TrafficSeparationSchemeArea

Definition:

A defined area where traffic lanes cross.

Description:

SOURCE [IHO Hydrographic Registry].

Stereotypes:

«featureType»
5.7.2.1.16. TrafficSeparationSchemeLane
TrafficSeparationSchemeLane

Subtype of:

TrafficSeparationSchemeArea

Definition:

An area within defined limits in which one-way traffic flow is established.

Description:

SOURCE [IMO Ships Routeing, 6th Edition], [IHO Hydrographic Registry].

Stereotypes:

«featureType»
5.7.2.1.17. TrafficSeparationSchemeRoundabout
TrafficSeparationSchemeRoundabout

Subtype of:

TrafficSeparationSchemeArea

Definition:

A traffic separation scheme in which traffic moves in a counter-clockwise direction around a specified point or zone.

Description:

SOURCE [IHO Hydrographic Registry].

Stereotypes:

«featureType»
5.7.2.1.18. TrafficSeparationSchemeSeparator
TrafficSeparationSchemeSeparator

Subtype of:

TrafficSeparationSchemeArea

Definition:

A zone separating the lanes in which ships are proceeding in opposite or nearly opposite directions; or separating traffic lanes designated for particular classes of ships proceeding in the same direction.

Description:

SOURCE [IHO Hydrographic Registry].

Stereotypes:

«featureType»
5.7.2.1.19. WaterLinkSequence
WaterLinkSequence

Subtype of:

TransportLinkSequence

Definition:

A linear spatial object, composed of an ordered collection of waterway and/or watercourse links (as necessary), which represents a continuous path in the water network without any branches.

Description:

NOTE The element has a defined beginning and end and every position on the water link sequence is identifiable with one single parameter such as length. It describes a element of the water network, which is a navigable path within a water body (oceans, seas, rivers, lakes, channels or canals) and could be characterized by one or more thematical identifiers and/or properties.

Stereotypes:

«featureType»
5.7.2.1.20. WaterNode
WaterNode (abstract)

Subtype of:

TransportNode

Definition:

A point spatial object which is used to represent the connectivity between two different waterway links, or between a waterway link and a watercourse link, in the water transport network.

Description:

NOTE It is also used to represent a significant feature in the network, such as a port.

Stereotypes:

«featureType»
5.7.2.1.21. WaterTrafficFlowDirection
WaterTrafficFlowDirection

Subtype of:

TrafficFlowDirection

Definition:

Indicates the direction of the flow of water transport traffic in relation to the direction of the water transport link vector.

Stereotypes:

«featureType»

Constraint: Applies to WaterwayLink and WaterLinkSequence only

Natural language:

This property can only be associated with a spatial object that is part of a water transport network.

OCL:

inv: networkRef.element.oclIsKindOf(WaterLinkSequence) or networkRef.element.oclIsKindOf(WaterwayLink)
5.7.2.1.22. Waterway
Waterway (abstract)

Subtype of:

TransportLinkSet

Definition:

A collection of water link sequences and or individual waterway and/or watercourse links (as necessary) that are characterized by one or more thematical identifiers and/or properties, which perform a navigable route within a water body (oceans, seas, rivers, lakes, channels or canals).

Stereotypes:

«featureType»
5.7.2.1.23. WaterwayLink
WaterwayLink

Subtype of:

TransportLink

Definition:

A linear spatial object that describes the geometry or connectivity of the water transport network between two consecutive waterway or watercourse nodes. It represents a linear section across a body of water which is used for shipping.

Description:

NOTE Water Transport Networks will use the WatercourseLink class - provided by the INSPIRE Hydrography Data Specification - wherever possible.

Stereotypes:

«featureType»
5.7.2.1.24. WaterwayNode
WaterwayNode

Subtype of:

WaterNode

Definition:

A point spatial object which is used to represent the connectivity between two different waterway links, or between a waterway link and a watercourse link, in the water transport network.

Stereotypes:

«featureType»

Attribute: formOfWaterwayNode

Value type:

FormOfWaterwayNodeValue

Definition:

Description of the function of a waterway node in the water transport network.

Multiplicity:

1

Stereotypes:

«voidable»
5.7.2.2. Code lists
5.7.2.2.1. FerryUseValue
FerryUseValue

Definition:

Types of transport carried out by a ferry.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FerryUseValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.7.2.2.2. FormOfWaterwayNodeValue
FormOfWaterwayNodeValue

Definition:

Function of a WaterwayNode in the water transport network.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FormOfWaterwayNodeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.7.2.2.3. CEMTClassValue
CEMTClassValue

Definition:

Inland waterway classification according to CEMT (European Conference of Ministers of Transport) Resolution No.92/2.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/CEMTClassValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.7.2.3. Imported types (informative)

This section lists definitions for feature types, data types and code lists that are defined in other application schemas. The section is purely informative and should help the reader understand the feature catalogue presented in the previous sections. For the normative documentation of these types, see the given references.

5.7.2.4. Boolean
Boolean

Package:

Truth

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.7.2.5. ConditionOfFacility
ConditionOfFacility

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

State of a transport network element with regards to its completion and use.
5.7.2.6. RestrictionForVehicles
RestrictionForVehicles

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

Restriction on vehicles on a transport element.
5.7.2.7. TrafficFlowDirection
TrafficFlowDirection

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

Indicates the direction of the flow of traffic in relation to the direction of the transport link vector.
5.7.2.8. TransportArea
TransportArea (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

Surface that represents the spatial extent of an element of a transport network.
5.7.2.9. TransportLink
TransportLink (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object that describes the geometry and connectivity of a transport network between two points in the network.
5.7.2.10. TransportLinkSequence
TransportLinkSequence (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object, composed of an ordered collection of transport links, which represents a continuous path in the transport network without any branches. The element has a defined beginning and end and every position on the transport link sequence is identifiable with one single parameter such as length. It describes an element of the transport network, characterized by one or more thematical identifiers and/or properties.
5.7.2.11. TransportLinkSet
TransportLinkSet (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A collection of transport link sequences and or individual transport links that has a specific function or significance in a transport network.

Description:

NOTE
This spatial object type supports the aggregation of links to form objects with branches, loops, parallel sequences of links, gaps, etc.

EXAMPLE
A dual carriageway road, as a collection of the two link sequences that represent each carriageway.
5.7.2.12. TransportNode
TransportNode (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A point spatial object which is used for connectivity.

Description:

Nodes are found at either end of the TransportLink.
5.7.2.13. TransportPoint
TransportPoint (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A point spatial object - which is not a node - that represents the position of an element of a transport network.
5.7.2.14. TransportProperty
TransportProperty (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A reference to a property that falls upon the network. This property can apply to the whole of the network element it is associated with or - for linear spatial objects - be described using linear referencing.

5.8. Application schema Air Transport Networks

5.8.1. Description

5.8.1.1. Narrative description

The Air Transport Networks application schema (Air Schema) employs a link and node structure to represent the Air routes used for transportation in the form of a linear network. The Air Schema inherits classes from the Common Transport Schema and also creates its own classes to describe properties of the air network such as air route type and restrictions that can apply to whole sections of the network element or subsections that can be described using linear referencing.

The primary aspects modelled for air network elements are:

  • Spatial. Geometric (point, line and area (topographic)) representation of various elements that are parts of a network. Typically, the network is handled as a network of connected linear elements (links) with points (nodes) at the air route junctions (usually over the position of significant points, such as navigation aids and designated points) or at the ends of the lines (at aerodromes – airports or heliports). Also real objects with a function in a network may be represented in the dataset. Network connectivity within the roads and rail networks (where this exists) is essential but between elements in the other networks is an optional spatial aspect.

  • Temporal. All elements in a network may have a temporal validity (i.e. description of when the network element exists in the real world) and also optional information on when data was entered, modified or deleted in the dataset.

  • Thematic. The air schema can be thematically displayed via several of the attributes defined within the specification such as altitude.

5.8.1.2. UML Overview
image

Figure 36 – UML class diagram: Overview of the Air Transport Networks application schema

image

Figure 37 – UML class diagram: Air Transport Networks Spatial object types – Links and Areas

image

Figure 38 – UML class diagram: Air Transport Networks Spatial object types - Nodes

image

Figure 39 – UML class diagram: Air Transport Networks Spatial object types – Transport Properties

AirTransportNetwork

Figure 40 – Overview of the main Air Transport Networks objects

image

Figure 41 – UML class diagram: Air Transport Networks code lists

5.8.1.3. Consistency between spatial data sets

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.3) apply to the corresponding specialized elements/classes in the Air transport networks.

5.8.1.4. Identifier management

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.4) apply to the corresponding specialized elements/classes in the Air transport networks.

5.8.1.5. Modelling of object references

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.5) apply to the corresponding specialized elements/classes in the Air transport networks.

5.8.1.6. Geometry representation

All requirements and recommendations on transport networks, defined in the Common Transport Elements application schema (see section 5.3.1.6) apply to the corresponding specialized elements/classes in the Air transport networks.

5.8.1.7. Temporality representation

All attributes describing the lifespan of spatial objects or the phenomena in the real world they describe are inherited from the Common Transport Elements application schema. Refer to section 5.3.1.7 for more information.

5.8.2. Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Air Transport Network

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

AerodromeArea

Air Transport Network

«featureType»

AerodromeCategory

Air Transport Network

«featureType»

AerodromeCategoryValue

Air Transport Network

«codeList»

AerodromeNode

Air Transport Network

«featureType»

AerodromeType

Air Transport Network

«featureType»

AerodromeTypeValue

Air Transport Network

«codeList»

AirLink

Air Transport Network

«featureType»

AirLinkSequence

Air Transport Network

«featureType»

AirNode

Air Transport Network

«featureType»

AirRoute

Air Transport Network

«featureType»

AirRouteLink

Air Transport Network

«featureType»

AirRouteLinkClassValue

Air Transport Network

«codeList»

AirRouteTypeValue

Air Transport Network

«codeList»

AirUseRestrictionValue

Air Transport Network

«codeList»

AirspaceArea

Air Transport Network

«featureType»

AirspaceAreaTypeValue

Air Transport Network

«codeList»

ApronArea

Air Transport Network

«featureType»

ConditionOfAirFacility

Air Transport Network

«featureType»

DesignatedPoint

Air Transport Network

«featureType»

ElementLength

Air Transport Network

«featureType»

ElementWidth

Air Transport Network

«featureType»

FieldElevation

Air Transport Network

«featureType»

InstrumentApproachProcedure

Air Transport Network

«featureType»

LowerAltitudeLimit

Air Transport Network

«featureType»

Navaid

Air Transport Network

«featureType»

NavaidTypeValue

Air Transport Network

«codeList»

PointRoleValue

Air Transport Network

«codeList»

ProcedureLink

Air Transport Network

«featureType»

RunwayArea

Air Transport Network

«featureType»

RunwayCentrelinePoint

Air Transport Network

«featureType»

RunwayTypeValue

Air Transport Network

«codeList»

StandardInstrumentArrival

Air Transport Network

«featureType»

StandardInstrumentDeparture

Air Transport Network

«featureType»

SurfaceComposition

Air Transport Network

«featureType»

SurfaceCompositionValue

Air Transport Network

«codeList»

TaxiwayArea

Air Transport Network

«featureType»

TouchDownLiftOff

Air Transport Network

«featureType»

UpperAltitudeLimit

Air Transport Network

«featureType»

UseRestriction

Air Transport Network

«featureType»
5.8.2.1. Spatial object types
5.8.2.1.1. AerodromeArea
AerodromeArea

Subtype of:

TransportArea

Definition:

A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft and/or helicopters.

Description:

SOURCE [AIXM5.0].

NOTE An area spatial object which is used to represent the physical limits of all the facilities which form part of an inland aerodrome.

Stereotypes:

«featureType»
5.8.2.1.2. AerodromeCategory
AerodromeCategory

Subtype of:

TransportProperty

Definition:

Aerodrome category concerning the scope and importance of the air traffic services offered from and to it.

Stereotypes:

«featureType»

Attribute: aerodromeCategory

Value type:

AerodromeCategoryValue

Definition:

Value which indicates the category of an aerodrome.

Multiplicity:

1

Constraint: Applies to AerodromeNode and AerodromeArea only

Natural language:

This property can only be associated with a spatial object that is an Aerodrome Node or an Aerodrome Area.

OCL:

inv: networkRef.element.oclIsKindOf(AerodromeNode) or networkRef.element.oclIsKindOf(AerodromeArea)
5.8.2.1.3. AerodromeNode
AerodromeNode

Subtype of:

AirNode

Definition:

Node located at the aerodrome reference point of an airport/heliport, which is used to represent it in a simplified way. DEFINITION Aerodrome Reference Point (ARP): The designated geographical location of an aerodrome, located near the initial or planned geometric centre of the aerodrome and normally remaining where originally established [AIXM3.3]. DEFINITION Airport/heliport: A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft/helicopters [AIXM5.0].

Description:

SOURCE [AIXM5.0].

Stereotypes:

«featureType»

Attribute: designatorIATA

Value type:

CharacterString

Definition:

The three letter IATA designator of the aerodrome (airport/heliport).

Description:

SOURCE [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: locationIndicatorICAO

Value type:

CharacterString

Definition:

The four letter ICAO location indicator of the aerodrome (airport/heliport), as listed in ICAO DOC 7910.

Description:

SOURCE [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»

Association role: controlTowers

Value type:

Building of the Buildings Base package

Definition:

The set of control towers belonging to an aerodrome (airport/heliport).

Description:

Multiplicity:

0..*

Stereotypes:

«voidable»
5.8.2.1.4. AerodromeType
AerodromeType

Subtype of:

TransportProperty

Definition:

A code specifying the type of aerodrome.

Description:

SOURCE [AIXM5.0].

EXAMPLE Aerodrome only, combined aerodrome/heliport or simple landing site.

Stereotypes:

«featureType»

Attribute: aerodromeType

Value type:

AerodromeTypeValue

Definition:

The type of aerodrome.

Multiplicity:

1

Constraint: Applies to AerodromeNode and AerodromeArea only

Natural language:

This property can only be associated with a spatial object that is an Aerodrome Node or Aerodrome Area.

OCL:

inv: networkRef.element.oclIsKindOf(AerodromeNode) or networkRef.element.oclIsKindOf(AerodromeArea)
5.8.2.1.5. AirLink
AirLink (abstract)

Subtype of:

TransportLink

Definition:

A linear spatial object that describes the geometry and connectivity of the air network between two points in the network.

Stereotypes:

«featureType»
5.8.2.1.6. AirLinkSequence
AirLinkSequence

Subtype of:

TransportLinkSequence

Definition:

A linear spatial object, composed of an ordered collection of air links, which represents a continuous path in the air network without any branches.

Description:

NOTE 1 The element has a defined beginning and end and every position on the air link sequence is identifiable with one single parameter such as length. It describes an element of the air network, which could be characterized by one or more thematical identifiers and/or properties.

NOTE 2 This collection of air links is equivalent to RoutePortion feature in AIXM5.0. RoutePortion: A group of two or more consecutive segments of the same route, which have the usage and/or the same flight restrictions [AIXM5.0].

Stereotypes:

«featureType»
5.8.2.1.7. AirNode
AirNode (abstract)

Subtype of:

TransportNode

Definition:

A node which occurs in a air network.

Stereotypes:

«featureType»

Attribute: significantPoint

Value type:

Boolean

Definition:

Attribute which indicates whether the air node is or is not a significant point. DEFINITION Significant point: A specified geographical location used to define an ATS route, the flight path of an aircraft or for other navigation/ATS purposes [AIXM5.0].

Description:

NOTE Significant Points are specific air nodes which normally define air routes.

Multiplicity:

1
5.8.2.1.8. AirRoute
AirRoute

Subtype of:

TransportLinkSet

Definition:

A specified route designed for channelling the flow of traffic as necessary for the provision of air traffic services, from the end of the take-off and initial climb phase to the commencement of the approach and landing phase.

Description:

SOURCE [Route - AIXM5.0].

NOTE A collection of air link sequences and or individual air links that are characterized by one or more thematic identifiers and /or properties, which perform a Route.

Stereotypes:

«featureType»

Attribute: airRouteType

Value type:

AirRouteTypeValue

Definition:

Route classification.

Description:

SOURCE [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: designator

Value type:

CharacterString

Definition:

Code or designator that identifies an Air Route.

Multiplicity:

1

Stereotypes:

«voidable»
5.8.2.1.9. AirRouteLink
AirRouteLink

Subtype of:

AirLink

Definition:

A portion of a route to be flown usually without an intermediate stop, as defined by two consecutive significant points.

Description:

SOURCE [AirRouteSegment - AIXM5.0].

NOTE The presence of air nodes (normally defining Significant Points) is not mandated.

Stereotypes:

«featureType»

Attribute: airRouteLinkClass

Value type:

AirRouteLinkClassValue

Definition:

The class or type of an air route link.

Multiplicity:

1

Stereotypes:

«voidable»
5.8.2.1.10. AirspaceArea
AirspaceArea

Subtype of:

TransportArea

Definition:

A defined volume in the air, described as horizontal projection with vertical limits.

Description:

SOURCE [AirspaceVolume - AIXM5.0].

NOTE 1 Definition of Airspace: A defined three dimensional region of space relevant to air traffic [AIXM5.0].

NOTE 2 Airspace regions are managed by air traffic control systems to provide a safe IFR (Instrument Flight Rules) navigation for air traffic services and aircrafts.

Stereotypes:

«featureType»

Attribute: AirspaceAreaType

Value type:

AirspaceAreaTypeValue

Definition:

A code indicating the general structure or characteristics of a particular airspace.

Description:

SOURCE [Airspace.type - AIXM5.0].

Multiplicity:

1
5.8.2.1.11. ApronArea
ApronArea

Subtype of:

TransportArea

Definition:

A defined area, on a land aerodrome/heliport, intended to accommodate aircraft/helicopters for purposes of loading and unloading passengers, mail or cargo, and for fuelling, parking or maintenance.

Description:

SOURCE [Apron - AIXM5.0].

Stereotypes:

«featureType»
5.8.2.1.12. ConditionOfAirFacility
ConditionOfAirFacility

Subtype of:

ConditionOfFacility

Definition:

State of an air transport network element with regards to its completion and use.

Stereotypes:

«featureType»

Constraint: Applies only to AerodromeNode, AerodromeArea and RunwayArea

Natural language:

This property can only be associated with a spatial object that is an Aerodrome Node, an Aerodrome Area or a Runway Area.

OCL:

inv: networkRef.element.oclIsKindOf(AerodromeNode) or networkRef.element.oclIsKindOf(AerodromeArea) or networkRef.element.oclIsKindOf(RunwayArea)
5.8.2.1.13. DesignatedPoint
DesignatedPoint

Subtype of:

AirNode

Definition:

A geographical location not marked by the site of a radio navigation aid, used in defining an ATS route, the flight path of an aircraft or for other navigation or ATS purposes.

Description:

SOURCE [AIXM5.0].

NOTE Examples of Designated points are compulsory and non-compulsory reporting points.

Stereotypes:

«featureType»

Attribute: designator

Value type:

CharacterString

Definition:

The coded designator of the point.

Description:

SOURCE [AIXM5.0].

EXAMPLE The five-letter ICAO name of the point.

Multiplicity:

1

Stereotypes:

«voidable»
5.8.2.1.14. ElementLength
ElementLength

Subtype of:

TransportProperty

Definition:

The physical length of the element.

Stereotypes:

«featureType»

Attribute: length

Value type:

Measure

Definition:

The physical length of the element.

Description:

NOTE 1 The value of the physical length of the runway [AIXM5.0], when applied to RunwayArea.

NOTE 2 Value for the length of the taxiway [AIXM5.0], when applied to TaxiwayArea.

NOTE 3 The value of the physical length of the touchdown and lift-off area [AIXM5.0], when applied to TouchDownLiftOff.

Multiplicity:

1

Constraint: Applies to RunwayArea, TaxiwayArea and TouchDownLiftOff only

Natural language:

This property can only be associated with a spatial object that is a Runway Area, Taxiway Area or Touch Down Lift Off.

OCL:

inv: networkRef.element.oclIsKindOf(RunwayArea) or networkRef.element.oclIsKindOf(TaxiwayArea) or networkRef.element.oclIsKindOf(TouchDownLiftOff)
5.8.2.1.15. ElementWidth
ElementWidth

Subtype of:

TransportProperty

Definition:

The physical width of the element.

Stereotypes:

«featureType»

Attribute: width

Value type:

Measure

Definition:

The physical width of the element.

Description:

NOTE 1 The value of the physical width of the runway [AIXM5.0], when applied to RunwayArea.

NOTE 2 The value of the physical width of the taxiway [AIXM5.0], when applied to TaxiwayArea.

NOTE 3 The value of the physical width of the touchdown and lift-off area [AIXM5.0], when applied to TouchDownLiftOff.

Multiplicity:

1

Constraint: Applies to RunwayArea, TaxiwayArea and TouchDownLiftOff only

Natural language:

This property can only be associated with a spatial object that is a Runway Area, Taxiway Area or Touch Down Lift Off.

OCL:

inv: networkRef.element.oclIsKindOf(RunwayArea) or networkRef.element.oclIsKindOf(TaxiwayArea) or networkRef.element.oclIsKindOf(TouchDownLiftOff)
5.8.2.1.16. FieldElevation
FieldElevation

Subtype of:

TransportProperty

Definition:

The aerodrome elevation as the vertical distance between the highest point of the landing area of an aerodrome and mean sea level.

Description:

SOURCE [AIXM5.0].

NOTE This might be different from the elevation of the Aerodrome Reference Point.

Stereotypes:

«featureType»

Attribute: altitude

Value type:

Measure

Definition:

Value of the field altitude.

Multiplicity:

1

Constraint: Applies to AerodromeNode and AerodromeArea only

Natural language:

This property can only be associated with a spatial object that is an Aerodrome Node or Aerodrome Area.

OCL:

inv: networkRef.element.oclIsKindOf(AerodromeNode) or networkRef.element.oclIsKindOf(AerodromeArea)
5.8.2.1.17. InstrumentApproachProcedure
InstrumentApproachProcedure

Subtype of:

ProcedureLink

Definition:

A series of predetermined manoeuvres by reference to flight instruments with specified protection from obstacles from the initial approach fix, or where applicable, from the beginning of a defined arrival route to a point from which a landing can be completed and thereafter, if a landing is not completed, to a position at which holding or en route obstacle clearance criteria apply.

Description:

SOURCE [AIXM5.0].

NOTE 1 Acronym: IAP.

NOTE 2 It corresponds to the final approach and arrival during the landing phase.

NOTE 3 A specific runway of an airport/heliport usually has more than one IAP, depending on the landing direction on it.

Stereotypes:

«featureType»
5.8.2.1.18. LowerAltitudeLimit
LowerAltitudeLimit

Subtype of:

TransportProperty

Definition:

Altitude that defines the lower limit of an air transport network object.

Description:

NOTE When applied to an AirRouteLink it corresponds to the Lowest Safe Altitude, which is defined in order to provide safety for navigation.

Stereotypes:

«featureType»

Attribute: altitude

Value type:

Measure

Definition:

Value of the altitude limit.

Multiplicity:

1

Constraint: Applies to AirRouteLink and AirspaceArea only

Natural language:

This property can only be associated with a spatial object that is an Air Route Link or Airspace Area.

OCL:

inv: networkRef.element.oclIsKindOf(AirRouteLink) or networkRef.element.oclIsKindOf(AirspaceArea)
5.8.2.1.19. Navaid
Navaid

Subtype of:

AirNode

Definition:

One or more Navaid Equipments providing navigation services. DEFINITION Navaid equipment: A physical navaid equipment like VOR, DME, localizer, TACAN or etc.

Description:

SOURCE [AIXM5.0].

NOTE 1
The Navaid Equipment share business rules like paired frequencies [AIXM5.0].

Stereotypes:

«featureType»

Attribute: navaidType

Value type:

NavaidTypeValue

Definition:

Type of the navaid service.

Description:

SOURCE [AIXM5.0].

EXAMPLES ILS, MLS, VORTAC, VOR/DME.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: designator

Value type:

CharacterString

Definition:

The coded identifier given to the navaid system.

Description:

SOURCE [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»
5.8.2.1.20. ProcedureLink
ProcedureLink

Subtype of:

AirLink

Definition:

A series of predetermined manoeuvres with specified protection from obstacles.

Description:

SOURCE [Procedure - AIXM5.0].

NOTE 1 A defined airway connector designed for channelling the flow of traffic as necessary for the provision of air traffic services during the take-off or landing phase, which links an airport/heliport to a significant point, usually connected to one or more air routes.

NOTE 2 When a airport/heliport is not connected with a standardized airway connector to the rest of the air network, this object can be used as a fictitious connector between the airport/heliport and a significant point on one or more ATS routes - for example for VFR (Visual Flight Rules) flights.

NOTE 3 Nevertheless, three main types of standardized Procedures are usually defined for IFR (Instrument Flight Rules) flights:
- Standard Instrument Departure (SID), corresponding to the take-off phase.
- Standard Instrument Arrival (STAR), corresponding to the initial approach during the landing phase.
- Instrument Approach Procedure (IAP), corresponding to the final approach and arrival during the landing phase.

Stereotypes:

«featureType»
5.8.2.1.21. RunwayArea
RunwayArea

Subtype of:

TransportArea

Definition:

A defined rectangular area on a land aerodrome/heliport prepared for the landing and take-off of aircraft.

Description:

SOURCE [Runway - AIXM5.0].

NOTE 1 This includes the concept of Final Approach and Take-Off Area (FATO) for helicopters [Runway - AIXM5.0].

NOTE 2 The runway strip is a defined area including the runway and stopway, if provided, intended : a) to reduce the risk of damage to aircraft running off a runway; and b) to protect aircraft flying over it during take-off or landing operations [ICAO].

Stereotypes:

«featureType»

Attribute: designator

Value type:

CharacterString

Definition:

The full textual designator of the runway, used to uniquely identify it at an aerodrome/heliport which has more than one.

Description:

SOURCE [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: runwayType

Value type:

RunwayTypeValue

Definition:

The type of runway, either runway for airplanes or final approach and take off area (FATO) for helicopters.

Description:

SOURCE Adapted from [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»
5.8.2.1.22. RunwayCentrelinePoint
RunwayCentrelinePoint

Subtype of:

AirNode

Definition:

An operationally significant position on the center line of a runway direction.

Description:

SOURCE [AIXM5.0].

NOTE 1 The role of the point along the runway direction centreline is indicated within the pointRole attribute.

NOTE 2 Runway centreline points are used to connect the Procedure Links that connect an airport/heliport to the rest of the air network.

EXAMPLE A typical example is the runway threshold [AIXM5.0].

Stereotypes:

«featureType»

Attribute: pointRole

Value type:

PointRoleValue

Definition:

The role of the point along the runway direction centreline.

Description:

SOURCE [AIXM5.0].

Multiplicity:

1
5.8.2.1.23. StandardInstrumentArrival
StandardInstrumentArrival

Subtype of:

ProcedureLink

Definition:

A designated instrument flight rule (IFR) arrival route linking a significant point, normally on an ATS route, with a point from which a published instrument approach procedure can be commenced.

Description:

SOURCE [AIXM5.0].

NOTE 1 Acronym: STAR.

NOTE 2 It corresponds to the initial approach during the landing phase. Each airport/heliport could have various STAR linking significant points (usually connected to air routes) to the points designated to start the landing on a specific runway.

Stereotypes:

«featureType»

Attribute: designator

Value type:

CharacterString

Definition:

The textual designator of the Standard Instrument Arrival.

Description:

SOURCE [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»
5.8.2.1.24. StandardInstrumentDeparture
StandardInstrumentDeparture

Subtype of:

ProcedureLink

Definition:

A designated instrument flight rule (IFR) departure route linking the aerodrome or a specific runway of the aerodrome with a specified significant point, normally on a designated ATS route, at which the en-route phase of a flight commences.

Description:

SOURCE [AIXM5.0].

NOTE 1 Acronym: SID.

NOTE 2 It corresponds to the take-off phase. Each airport/heliport could have various SID linking the different runways to one or various significant points, usually connected to air routes.

Stereotypes:

«featureType»

Attribute: designator

Value type:

CharacterString

Definition:

The full textual designator of the Standard Instrument Departure.

Description:

SOURCE [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»
5.8.2.1.25. SurfaceComposition
SurfaceComposition

Subtype of:

TransportProperty

Definition:

The composition of an aerodrome/heliport related surface.

Stereotypes:

«featureType»

Attribute: surfaceComposition

Value type:

SurfaceCompositionValue

Definition:

A code indicating the composition of an aerodrome/heliport related surface.

Description:

SOURCE [SurfaceCharacteristics.composition - AIXM5.0].

EXAMPLES Asphalt, concrete.

Multiplicity:

1

Constraint: Applies to RunwayArea, TaxiwayArea, ApronArea and TouchDownLiftOff only

Natural language:

This property can only be associated with a spatial object that is a Runway Area, Taxiway Area, Apron Area or Touch Down Lift Off.

OCL:

inv: networkRef.element.oclIsKindOf(RunwayArea) or networkRef.element.oclIsKindOf(TaxiwayArea) or networkRef.element.oclIsKindOf(ApronArea) or networkRef.element.oclIsKindOf(TouchDownLiftOff)
5.8.2.1.26. TaxiwayArea
TaxiwayArea

Subtype of:

TransportArea

Definition:

A defined path at an aerodrome/heliport established for the taxiing of aircraft/helicopters and intended to provide a link between one part of the aerodrome and another.

Description:

SOURCE [Taxiway - AIXM5.0].

NOTE This includes aircraft/helicopter stand taxilines, apron taxiways, rapid exit taxiways, air taxiways etc.

Stereotypes:

«featureType»

Attribute: designator

Value type:

CharacterString

Definition:

The textual designator of the taxiway.

Description:

SOURCE [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»
5.8.2.1.27. TouchDownLiftOff
TouchDownLiftOff

Subtype of:

AirNode

Definition:

A load bearing area on which a helicopter may touch down or lift-off.

Description:

SOURCE [AIXM5.0].

Stereotypes:

«featureType»

Attribute: designator

Value type:

CharacterString

Definition:

The textual designator of the touch down and lift-off area.

Description:

SOURCE [AIXM5.0].

Multiplicity:

1

Stereotypes:

«voidable»
5.8.2.1.28. UpperAltitudeLimit
UpperAltitudeLimit

Subtype of:

TransportProperty

Definition:

Altitude that defines the upper limit of an air transport network object.

Stereotypes:

«featureType»

Attribute: altitude

Value type:

Measure

Definition:

Value of the altitude limit.

Multiplicity:

1

Constraint: Applies to AirRouteLink and AirspaceArea only

Natural language:

This property can only be associated with a spatial object that is an Air Route Link or Airspace Area.

OCL:

inv: networkRef.element.oclIsKindOf(AirRouteLink) or networkRef.element.oclIsKindOf(AirspaceArea)
5.8.2.1.29. UseRestriction
UseRestriction

Subtype of:

TransportProperty

Definition:

The restrictions to the use of an air network object.

Stereotypes:

«featureType»

Attribute: restriction

Value type:

AirUseRestrictionValue

Definition:

The type of use restriction for the air network object.

Multiplicity:

1

Constraint: Applies to AirRoute, AirLinks, AirNodes and AerodromeArea only

Natural language:

This property can only be associated with a spatial object that is an Air Route, Air Link (or specialized Air Link), Air Node (or specialized Air Node) or Aerodrome Area.

OCL:

inv: networkRef.element.oclIsKindOf(AirRoute) or networkRef.element.oclIsKindOf(AirLink) or networkRef.element.oclIsKindOf(AirNode) or networkRef.element.oclIsKindOf(AerodromeArea)
5.8.2.2. Code lists
5.8.2.2.1. AerodromeCategoryValue
AerodromeCategoryValue

Definition:

Aerodrome possible categories concerning the scope and importance of the air traffic services offered from and to it.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AerodromeCategoryValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.2.2. AerodromeTypeValue
AerodromeTypeValue

Definition:

A code specifying whether a particular entity occurrence is an Aerodrome or a Heliport.

Description:

SOURCE [CodeAirportHeliportType - AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AerodromeTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.2.3. AirRouteLinkClassValue
AirRouteLinkClassValue

Definition:

The type of the route from the navigation point of view.

Description:

SOURCE [CodeRouteNavigationType - AIXM5.0].

NOTE These values enumerate the possible usages of a AirRouteLink.

EXAMPLES Conventional, RNAV.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AirRouteLinkClassValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.2.4. AirRouteTypeValue
AirRouteTypeValue

Definition:

The route classification as ATS route or North Atlantic Tracks.

Description:

SOURCE [CodeRouteType - AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AirRouteTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.2.5. AirspaceAreaTypeValue
AirspaceAreaTypeValue

Definition:

Recognised types of Airspace.

Description:

SOURCE [CodeAirspaceType - AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AirspaceAreaTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.2.6. AirUseRestrictionValue
AirUseRestrictionValue

Definition:

The use restrictions for an air network object.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AirUseRestrictionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.2.7. NavaidTypeValue
NavaidTypeValue

Definition:

Types of Navaid Services.

Description:

SOURCE [AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/NavaidTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.2.8. PointRoleValue
PointRoleValue

Definition:

Role of the Runway Centreline Point.

Description:

SOURCE [AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/PointRoleValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.2.9. RunwayTypeValue
RunwayTypeValue

Definition:

A code that makes a distinction between runways for airplanes and FATO for helicopters.

Description:

SOURCE [CodeRunwayType - AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RunwayTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.2.10. SurfaceCompositionValue
SurfaceCompositionValue

Definition:

A code indicating the composition of a surface.

Description:

SOURCE [CodeSurfaceCompositionType - AIXM5.0].

EXAMPLES Asphalt, concrete.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/SurfaceCompositionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.8.2.3. Imported types (informative)

This section lists definitions for feature types, data types and code lists that are defined in other application schemas. The section is purely informative and should help the reader understand the feature catalogue presented in the previous sections. For the normative documentation of these types, see the given references.

Boolean

Boolean

Package:

Truth

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.8.2.4. CharacterString
CharacterString

Package:

Text

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.8.2.5. ConditionOfFacility
ConditionOfFacility

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

State of a transport network element with regards to its completion and use.
5.8.2.6. Measure
Measure

Package:

ProductionAndIndustrialFacilitiesExtension

Reference:

INSPIRE Data specification on Production and Industrial Facilities [DS-D2.8.III.8]

Definition:

Declared or measured quantity of any kind of physical entity.
5.8.2.7. TransportArea
TransportArea (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

Surface that represents the spatial extent of an element of a transport network.
5.8.2.8. TransportLink
TransportLink (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object that describes the geometry and connectivity of a transport network between two points in the network.
5.8.2.9. TransportLinkSequence
TransportLinkSequence (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A linear spatial object, composed of an ordered collection of transport links, which represents a continuous path in the transport network without any branches. The element has a defined beginning and end and every position on the transport link sequence is identifiable with one single parameter such as length. It describes an element of the transport network, characterized by one or more thematical identifiers and/or properties.
5.8.2.10. TransportLinkSet
TransportLinkSet (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A collection of transport link sequences and or individual transport links that has a specific function or significance in a transport network.

Description:

NOTE
This spatial object type supports the aggregation of links to form objects with branches, loops, parallel sequences of links, gaps, etc.

EXAMPLE
A dual carriageway road, as a collection of the two link sequences that represent each carriageway.
5.8.2.11. TransportNode
TransportNode (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A point spatial object which is used for connectivity.

Description:

Nodes are found at either end of the TransportLink.
5.8.2.12. TransportProperty
TransportProperty (abstract)

Package:

Common Transport Elements

Reference:

INSPIRE Data specification on Transport Networks [DS-D2.8.I.7]

Definition:

A reference to a property that falls upon the network. This property can apply to the whole of the network element it is associated with or - for linear spatial objects - be described using linear referencing.

6. Reference systems, units of measure and grids

6.1. Default reference systems, units of measure and grid

The reference systems, units of measure and geographic grid systems included in this sub-section are the defaults to be used for all INSPIRE data sets, unless theme-specific exceptions and/or additional requirements are defined in section 6.2.

6.1.1. Coordinate reference systems

6.1.1.1. Datum
📕

IR Requirement
Annex II, Section 1.2
Datum for three-dimensional and two-dimensional coordinate reference systems

For the three-dimensional and two-dimensional coordinate reference systems and the horizontal component of compound coordinate reference systems used for making spatial data sets available, the datum shall be the datum of the European Terrestrial Reference System 1989 (ETRS89) in areas within its geographical scope, or the datum of the International Terrestrial Reference System (ITRS) or other geodetic coordinate reference systems compliant with ITRS in areas that are outside the geographical scope of ETRS89. Compliant with the ITRS means that the system definition is based on the definition of the ITRS and there is a well documented relationship between both systems, according to EN ISO 19111.
6.1.1.2. Coordinate reference systems
📕

IR Requirement
Annex II, Section 1.3
Coordinate Reference Systems

Spatial data sets shall be made available using at least one of the coordinate reference systems specified in sections 1.3.1, 1.3.2 and 1.3.3, unless one of the conditions specified in section 1.3.4 holds.

1.3.1. Three-dimensional Coordinate Reference Systems

  • Three-dimensional Cartesian coordinates based on a datum specified in 1.2 and using the parameters of the Geodetic Reference System 1980 (GRS80) ellipsoid.

  • Three-dimensional geodetic coordinates (latitude, longitude and ellipsoidal height) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.

1.3.2. Two-dimensional Coordinate Reference Systems

  • Two-dimensional geodetic coordinates (latitude and longitude) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.

  • Plane coordinates using the ETRS89 Lambert Azimuthal Equal Area coordinate reference system.

  • Plane coordinates using the ETRS89 Lambert Conformal Conic coordinate reference system.

  • Plane coordinates using the ETRS89 Transverse Mercator coordinate reference system.

1.3.3. Compound Coordinate Reference Systems

  1. For the horizontal component of the compound coordinate reference system, one of the coordinate reference systems specified in section 1.3.2 shall be used.

  2. For the vertical component, one of the following coordinate reference systems shall be used:

  • For the vertical component on land, the European Vertical Reference System (EVRS) shall be used to express gravity-related heights within its geographical scope. Other vertical reference systems related to the Earth gravity field shall be used to express gravity-related heights in areas that are outside the geographical scope of EVRS.

  • For the vertical component in the free atmosphere, barometric pressure, converted to height using ISO 2533:1975 International Standard Atmosphere, or other linear or parametric reference systems shall be used. Where other parametric reference systems are used, these shall be described in an accessible reference using EN ISO 19111-2:2012.

  • For the vertical component in marine areas where there is an appreciable tidal range (tidal waters), the Lowest Astronomical Tide (LAT) shall be used as the reference surface.

  • For the vertical component in marine areas without an appreciable tidal range, in open oceans and effectively in waters that are deeper than 200 meters, the Mean Sea Level (MSL) or a well-defined reference level close to the MSL shall be used as the reference surface.

1.3.4. Other Coordinate Reference Systems

Exceptions, where other coordinate reference systems than those listed in 1.3.1, 1.3.2 or 1.3.3 may be used, are:
. Other coordinate reference systems may be specified for specific spatial data themes.

  1. For regions outside of continental Europe, Member States may define suitable coordinate reference systems.

The geodetic codes and parameters needed to describe these other coordinate reference systems and to allow conversion and transformation operations shall be documented and an identifier shall be created in a coordinate systems register established and operated by the Commission, according to EN ISO 19111 and ISO 19127.
The Commission shall be assisted by the INSPIRE Commission expert group in the maintenance and update of the coordinate systems register.
6.1.1.3. Display
📕

IR Requirement
Annex II, Section 1.4
Coordinate Reference Systems used in the View Network Service

For the display of spatial data sets with the view network service as specified in Regulation No 976/2009, at least the coordinate reference systems for two-dimensional geodetic coordinates (latitude, longitude) shall be available.
6.1.1.4. Identifiers for coordinate reference systems
📕

IR Requirement
Annex II, Section 1.5
Coordinate Reference System Identifiers

  1. Coordinate reference system parameters and identifiers shall be managed in one or several common registers for coordinate reference systems.

  2. Only identifiers contained in a common register shall be used for referring to the coordinate reference systems listed in this Section.

These Technical Guidelines propose to use the http URIs provided by the Open Geospatial Consortium as coordinate reference system identifiers (see identifiers for the default CRSs in the INSPIRE coordinate reference systems register). These are based on and redirect to the definition in the EPSG Geodetic Parameter Registry (http://www.epsg-registry.org/).

📒

TG Requirement 2

The identifiers listed in the INSPIRE coordinate reference systems register (https://inspire.ec.europa.eu/crs) shall be used for referring to the coordinate reference systems used in a data set.

NOTE CRS identifiers may be used e.g. in:

  • data encoding,

  • data set and service metadata, and

  • requests to INSPIRE network services.

6.1.2. Temporal reference system

📕

IR Requirement
Article 11
Temporal Reference Systems

  1. The default temporal reference system referred to in point 5 of part B of the Annex to Commission Regulation (EC) No 1205/2008 ([20]) shall be used, unless other temporal reference systems are specified for a specific spatial data theme in Annex II.

NOTE 1 Point 5 of part B of the Annex to Commission Regulation (EC) No 1205/2008 (the INSPIRE Metadata IRs) states that the default reference system shall be the Gregorian calendar, with dates expressed in accordance with ISO 8601.

NOTE 2 ISO 8601 Data elements and interchange formats – Information interchange – Representation of dates and times is an international standard covering the exchange of date and time-related data. The purpose of this standard is to provide an unambiguous and well-defined method of representing dates and times, so as to avoid misinterpretation of numeric representations of dates and times, particularly when data is transferred between countries with different conventions for writing numeric dates and times. The standard organizes the data so the largest temporal term (the year) appears first in the data string and progresses to the smallest term (the second). It also provides for a standardized method of communicating time-based information across time zones by attaching an offset to Coordinated Universal Time (UTC).

EXAMPLE 1997 (the year 1997), 1997-07-16 (16th July 1997), 1997-07-16T19:20:3001:00 (16th July 1997, 19h 20' 30'', time zone: UTC1)

6.1.3. Units of measure

📕

IR Requirement
Article 12
Other Requirements & Rules

(…​)

  1. All measurement values shall be expressed using SI units or non-SI units accepted for use with the International System of Units, unless specified otherwise for a specific spatial data theme or type.

6.2. Theme-specific requirements and recommendations

There are no theme-specific requirements or recommendations on reference systems and grids.

7. Data quality

This chapter includes a description of the data quality elements and sub-elements as well as the corresponding data quality measures that should be used to evaluate and document data quality for data sets related to the spatial data theme Transport Networks (section 7.1).

It may also define requirements or recommendations about the targeted data quality results applicable for data sets related to the spatial data theme Transport Networks (sections 7.2 and 7.3).

In particular, the data quality elements, sub-elements and measures specified in section 7.1 should be used for

  • evaluating and documenting data quality properties and constraints of spatial objects, where such properties or constraints are defined as part of the application schema(s) (see section 5);

  • evaluating and documenting data quality metadata elements of spatial data sets (see section 8); and/or

  • specifying requirements or recommendations about the targeted data quality results applicable for data sets related to the spatial data theme Transport Networks (see sections 7.2 and 7.3).

The descriptions of the elements and measures are based on Annex D of ISO/DIS 19157 Geographic information – Data quality.

7.1. Data quality elements

Table 3 lists all data quality elements and sub-elements that are being used in this specification. Data quality information can be evaluated at level of spatial object, spatial object type, dataset or dataset series. The level at which the evaluation is performed is given in the "Evaluation Scope" column.

The measures to be used for each of the listed data quality sub-elements are defined in the following sub-sections.

Table 3 – Data quality elements used in the spatial data theme Transport Networks

Section

Data quality element

Data quality sub-element

Definition

Evaluation Scope

Quality purpose

7.1.1

Completeness

Commission

excess data present in the dataset, as described by the scope

dataset

evaluation

7.1.2

Completeness

Omission

data absent from the dataset, as described by the scope

dataset

evaluation

7.1.3

Logical consistency

Conceptual consistency

adherence to rules of the conceptual schema

spatial object type; spatial object

evaluation

7.1.4

Logical consistency

Domain consistency

adherence of values to the value domains

spatial object type; spatial object

evaluation

7.1.5

Logical consistency

Format consistency

degree to which data is stored in accordance with the physical structure of the dataset, as described by the scope

dataset

evaluation

7.1.6

Logical consistency

Topological consistency

correctness of the explicitly encoded topological characteristics of the dataset, as described by the scope

dataset

network

7.1.7

Positional accuracy

Absolute or external accuracy

closeness of reported coordinate values to values accepted as or being true

dataset

evaluation

7.1.8

Thematic accuracy

Classification correctness

comparison of the classes assigned to features or their attributes to a universe of discourse

dataset

evaluation
📘

Recomendation 18

Where it is impossible to express the evaluation of a data quality element in a quantitative way, the evaluation of the element should be expressed with a textual statement as a data quality descriptive result.

7.1.1. Completeness – Commission

📘

Recomendation 19

Commission should be evaluated and documented using Rate of excess items and Number of duplicate feature instances as specified in the tables below.

Name

Rate of excess items

Alternative name

-

Data quality element

Completeness

Data quality sub-element

Commission

Data quality basic measure

Error rate

Definition

Number of excess items in the dataset in relation to the number of items that should have been present.

Description

-

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

-

Data quality value type

Real, percentage, ratio

Data quality value structure

-

Source reference

-

Example

-

Measure identifier

3

Name

Number of duplicate feature instances

Alternative name

-

Data quality element

Completeness

Data quality subelement

Commission

Data quality basic measure

Error count

Definition

Total number of exact duplications of feature instances within the data

Description

Count of all items in the data that are incorrectly extracted with duplicate geometries.

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

-

Data quality value type

Integer

Data quality value structure

-

Source reference

-

Example

Features with identical attribution and identical coordinates:

  • two (or more) points collected on top of each other;

  • two (or more) curves collected on top of each other;

  • two (or more) surfaces collected on top of each other.

Measure identifier

4

7.1.2. Completeness – Omission

📘

Recomendation 20

Omission should be evaluated and documented using Rate of missing items as specified in the table below.

Name

Rate of missing items

Alternative name

-

Data quality element

Completeness

Data quality subelement

Omission

Data quality basic measure

Error rate

Definition

Number of items missing from the data.

Description

-

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

-

Data quality value type

Real, percentage, ratio

Data quality value structure

-

Source reference

-

Example

-

Measure identifier

5

7.1.3. Logical consistency – Conceptual consistency

The Application Schema conformance class of the Abstract Test Suite in Annex I defines a number of tests to evaluate the conceptual consistency (tests A.1.1-A.1.9) of a data set.

📘

Recomendation 21

For the tests on conceptual consistency, it is recommended to use the Logical consistency – Conceptual consistency data quality sub-element and the measure Number of items not compliant with the rules of the conceptual schema as specified in the table below.

Name

Number of items not compliant with the rules of the conceptual schema

Alternative name

-

Data quality element

logical consistency

Data quality sub-element

conceptual consistency

Data quality basic measure

error count

Definition

count of all items in the dataset that are not compliant with the rules of the conceptual schema

Description

If the conceptual schema explicitly or implicitly describes rules, these rules shall be followed. Violations against such rules can be, for example, invalid placement of features within a defined tolerance, duplication of features and invalid overlap of features.

Evaluation scope

spatial object / spatial object type

Reporting scope

data set

Parameter

-

Data quality value type

integer

Data quality value structure

-

Source reference

ISO/DIS 19157 Geographic information – Data quality

Example

Measure identifier

10

NOTE in the previous version of the document (v3.1), the "conceptual schema compliance" was proposed as the measure for "Logical consistency – Conceptual consistency". This measure has been harmonised according to the new template.

7.1.4. Logical consistency – Domain consistency

The Application Schema conformance class of the Abstract Test Suite in Annex I defines a number of tests to evaluate the domain consistency (tests A1.10-A.1.12) of a data set.

📘

Recomendation 22

For the tests on domain consistency, it is recommended to use the Logical consistency – Domain consistency data quality sub-element and the measure Number of items not in conformance with their value domain as specified in the table below.

Name

Number of items not in conformance with their value domain

Alternative name

-

Data quality element

logical consistency

Data quality sub-element

domain consistency

Data quality basic measure

error count

Definition

count of all items in the dataset that are not in conformance with their value domain

Description

Example: number of incorrect or missing national identifiers in the data set in relation to the number of items in the data set.

Evaluation scope

spatial object / spatial object type

Reporting scope

data set

Parameter

-

Data quality value type

integer

NOTE in the previous version of the document (v3.1), the "value domain non conformance rate" was proposed as the measure for "Logical consistency – Domain consistency". This measure has been harmonised according to the new template.

7.1.5. Logical Consistency – Format consistency

📘

Recomendation 23

Format consistency should be evaluated and documented using Physical structure conflict rate as specified in the table below.

Name

Physical structure conflict rate

Alternative name

-

Data quality element

Logical consistency

Data quality subelement

Format consistency

Data quality basic measure

Error rate

Definition

Number of items in the dataset that are stored in conflict with the physical structure of the dataset divided by the total number of items

Description

-

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

-

Data quality value type

Real, percentage, ratio

Data quality value structure

-

Source reference

-

Example

-

Measure identifier

20

7.1.6. Logical Consistency – Topological consistency

📘

Recomendation 24

Topological consistency should be evaluated and documented using Number of invalid overlaps of surfaces, Number of missing connections due to undershoots, Number of missing connections due to overshoots, Number of invalid slivers, Number of invalid self-intersect errors, Number of invalid self-overlap errors as specified in the tables below.

Name

Number of invalid overlaps of surfaces

Alternative name

Overlapping surfaces

Data quality element

Logical consistency

Data quality subelement

Conceptual consistency

Data quality basic measure

Error count

Definition

Total number of erroneous overlaps within the data.

Description

Which surfaces may overlap and which shall not is application dependent. Not all overlapping surfaces are necessarily erroneous.

When reporting this data quality measure, the types of feature classes corresponding to the illegal overlapping surfaces shall be reported as well.

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

-

Data quality value type

Integer

Data quality value structure

-

Source reference

-

Example:
image

Key

  1. Surface 1

  2. Surface 2

  3. Overlapping Area

Note: Some types of area features related to air transport (e.g. AirspaceArea types FIR and CTR) represent the horizontal projections of 3D volumes in the air space which may overlap.

Measure identifier

11

Name

Number of missing connections due to undershoots

Alternative name

Undershoots

Data quality element

Logical consistency

Data quality subelement

Topological consistency

Data quality basic measure

Error count

Definition

Count of items in the dataset that are mismatched due to undershoots, given the parameter Connectivity tolerance.

Description

Lacks of connectivity exceeding the Connectivity tolerance are considered as errors if the real features are connected in the transport network.

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

  • Name: Connectivity tolerance

  • Definition: Search distance from the end of a dangling line.

  • Description:

This parameter is specific for each data provider’s dataset and must be reported as metadata in order to ensure automatic and unambiguous creation of centreline topology – connectivity - for the transport network (See Section 10.2 Ensuring Network Connectivity).

Connectivity tolerance must be specified by the data provider using the following elements of the DQ_TopologicalConsistency metadata element for the current measure:

  • 102. measureDescription (type: free text):

    Defined as "Description of the measure".

  • 107. Result (type DQ_Result):

    Defined as "Value (or set of values) obtained from applying a data quality measure or the outcome of evaluating the obtained value (or set of values) against a specified acceptable conformance quality level".

    Specifically, the tolerance must be defined within the two elements:

    • 130. specification

    • 131. explanation

from DQ_Result class.

Note: Metadata elements defined in ISO 19115.

Data quality value type

Integer

Data quality value structure

-

Source reference

-

Example
image

Key

  1. Connectivity tolerance = 3 m

Measure identifier

23

Name

Number of missing connections due to overshoots

Alternative name

Overshoots

Data quality element

Logical consistency

Data quality subelement

Topological consistency

Data quality basic measure

Error count

Definition

Count of items in the dataset that are mismatched due to overshoots, given the parameter Connectivity tolerance.

Description

Lacks of connectivity exceeding the Connectivity tolerance are considered as errors if the real features are connected in the transport network.

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

  • Name: Connectivity tolerance

  • Definition: Search distance from the end of a dangling line.

  • Description:

This parameter is specific for each data provider’s dataset and must be reported as metadata in order to ensure automatic and unambiguous creation of centreline topology – connectivity - for the transport network (See Section 10.2 Ensuring Network Connectivity).

Connectivity tolerance must be specified by the data provider using the following elements of the DQ_TopologicalConsistency metadata element for the current measure:

  • 102. measureDescription (type: free text):

    Defined as "Description of the measure".

  • 107. Result (type DQ_Result):

    Defined as "Value (or set of values) obtained from applying a data quality measure or the outcome of evaluating the obtained value (or set of values) against a specified acceptable conformance quality level".

Specifically, the tolerance must be defined within the two elements:

  • 130. specification

  • 131. explanation

from DQ_Result class.

Note: Metadata elements defined in ISO 19115.

Data quality value type

Integer

Data quality value structure

-

Source reference

-

Example
image

Key

  1. Connectivity tolerance = 3 m

Measure identifier

24

Name

Number of invalid slivers

Alternative name

Slivers

Data quality element

Logical consistency

Data quality subelement

Topological consistency

Data quality basic measure

Error count

Definition

Count of all items in the dataset that are invalid sliver surfaces.

Description

A sliver is an unintended area that occurs when adjacent surfaces are not digitized properly. The borders of the adjacent surfaces may unintentionally gap or overlap by small amounts to cause a topological error.

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

This data quality measure has 2 parameters:

  • maximum sliver area size

  • thickness quotient

The thickness quotient shall be a real number between 0 and 1. This quotient is determined by the following formula:

T is the thickness quotient

T = 4 π [area]/2

T = 1 value corresponds to a circle that has the largest area/perimeter2 value.

T = 0 value corresponds to a line that has the smallest area/perimeter2 value.

The thickness quotient is independent of the size of the surface, and the closer the value is to 0, the thinner the selected sliver surfaces shall be.

The maximum area determines the upper limit of a sliver. This is to prevent surfaces with sinuous perimeters and large areas from being mistaken as slivers.

Data quality value type

Integer

Data quality value structure

-

Source reference

Environmental Systems Research Institute, Inc. (ESRI)

GIS Data ReViewer 4.2 User Guide

Example
image

Key

  1. Single line rail

  2. Double line rail

    1. Maximum area parameter prevents correct double line rail portrayal from being flagged as an error

image

Key

  1. Railway station area

  2. Sliver

  3. Railway yard area

    1. Sliver is less than the maximum parameter and is flagged for evaluation of possible error

Measure identifier

25

Name

Number of invalid self-intersect errors

Alternative name

Loops

Data quality element

Logical consistency

Data quality subelement

Topological consistency

Data quality basic measure

Error count

Definition

Count of all items in the data that illegally intersect with themselves.

Description

-

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

-

Data quality value type

Integer

Data quality value structure

-

Source reference

-

Example
image

Key

  1. Enclosed Traffic Area

  2. Illegal intersection (loop)

Measure identifier

26

Name

Number of invalid self-overlap errors

Alternative name

Kickbacks

Data quality element

Logical consistency

Data quality subelement

Topological consistency

Data quality basic measure

Error count

Definition

Count of all items in the data that illegally self overlap.

Description

-

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

-

Data quality value type

Integer

Data quality value structure

-

Source reference

-

Example
ZigZag

a Vertices.

Measure identifier

27

7.1.7. Positional accuracy – Absolute or external accuracy

📘

Recomendation 25

Absolute or external accuracy should be evaluated and documented using Mean value of positional uncertainties as specified in the table below.

Name

Mean value of positional uncertainties

Alternative name

Mean value of positional uncertainties (1D, 2D and 3D)

Data quality element

Positional accuracy

Data quality subelement

Absolute or external accuracy

Data quality basic measure

Not applicable

Definition

Mean value of the positional uncertainties for a set of positions where the positional uncertainties are defined as the distance between a measured position and what is considered as the corresponding true position.

Description

For a number of points (N), the measured positions are given as xmi, ymi and zmi coordinates depending on the dimension in which the position of the point is measured. A corresponding set of coordinates, xti, yti and zti, are considered to represent the true positions. The errors are calculated as 1D:

image

2D:

image

3D:

image

The mean positional uncertainties of the horizontal absolute or external positions are then calculated as

image

A criterion for the establishing of correspondence should also be stated (e.g. allowing for correspondence to the closest position, correspondence on vertices or along lines). The criterion/criteria for finding the corresponding points shall be reported with the data quality evaluation result.

This data quality measure is different from the standard deviation.

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

-

Data quality value type

Measure

Data quality value structure

-

Source reference

-

Example

-

Measure identifier

28

7.1.8. Thematic accuracy – Classification correctness

📘

Recomendation 26

Classification correctness should be evaluated and documented using Misclassification rate as specified in the tables below.

Name

Misclassification rate

Alternative name

-

Data quality element

Thematic accuracy

Data quality subelement

Classification correctness

Data quality basic measure

Error rate

Definition

Average number of incorrectly classified features in relation to the number of features that are supposed to be within the dataset.

Description

To be provided globally as an average value for the whole dataset.

Evaluation scope

data set

Reporting scope

data set; spatial object type

Parameter

­-

Data quality value type

Real, percentage, ratio

Data quality value structure

-

Source reference

-

Example

-

Measure identifier

61
📘

Recomendation 27

Where metadata is not supplied at the object level data providers should supply the dataset metadata described in section 7.

7.2. Minimum data quality requirements

No minimum data quality requirements are defined for the spatial data theme Transport Networks.

7.3. Recommendation on data quality

No minimum data quality recommendations are defined.

8. Dataset-level metadata

This section specifies dataset-level metadata elements, which should be used for documenting metadata for a complete dataset or dataset series.

NOTE Metadata can also be reported for each individual spatial object (spatial object-level metadata). Spatial object-level metadata is fully described in the application schema(s) (section 5).

For some dataset-level metadata elements, in particular those for reporting data quality and maintenance, a more specific scope can be specified. This allows the definition of metadata at sub-dataset level, e.g. separately for each spatial object type (see instructions for the relevant metadata element).

8.1. Metadata elements defined in INSPIRE Metadata Regulation

Table 4 gives an overview of the metadata elements specified in Regulation 1205/2008/EC (implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata).

The table contains the following information:

  • The first column provides a reference to the relevant section in the Metadata Regulation, which contains a more detailed description.

  • The second column specifies the name of the metadata element.

  • The third column specifies the multiplicity.

  • The fourth column specifies the condition, under which the given element becomes mandatory.

Table 4 – Metadata for spatial datasets and spatial dataset series specified in Regulation 1205/2008/EC

Metadata Regulation Section

Metadata element

Multiplicity

Condition

1.1

Resource title

1

1.2

Resource abstract

1

1.3

Resource type

1

1.4

Resource locator

0..*

Mandatory if a URL is available to obtain more information on the resource, and/or access related services.

1.5

Unique resource identifier

1..*

1.7

Resource language

0..*

Mandatory if the resource includes textual information.

2.1

Topic category

1..*

3

Keyword

1..*

4.1

Geographic bounding box

1..*

5

Temporal reference

1..*

6.1

Lineage

1

6.2

Spatial resolution

0..*

Mandatory for data sets and data set series if an equivalent scale or a resolution distance can be specified.

7

Conformity

1..*

8.1

Conditions for access and use

1..*

8.2

Limitations on public access

1..*

9

Responsible organisation

1..*

10.1

Metadata point of contact

1..*

10.2

Metadata date

1

10.3

Metadata language

1

Generic guidelines for implementing these elements using ISO 19115 and 19119 are available at https://knowledge-base.inspire.ec.europa.eu/publications/technical-guidance-implementation-inspire-dataset-and-service-metadata-based-isots-191392007_en. The following sections describe additional theme-specific recommendations and requirements for implementing these elements.

8.1.1. Conformity

The Conformity metadata element defined in Regulation 1205/2008/EC requires to report the conformance with the Implementing Rule for interoperability of spatial data sets and services. In addition, it may be used also to document the conformance to another specification.

📘

Recomendation 28

Dataset metadata should include a statement on the overall conformance of the dataset with this data specification (i.e. conformance with all requirements).
📘

Recomendation 29

The Conformity metadata element should be used to document conformance with this data specification (as a whole), with a specific conformance class defined in the Abstract Test Suite in Annex A and/or with another specification.

The Conformity element includes two sub-elements, the Specification (a citation of the Implementing Rule for interoperability of spatial data sets and services or other specification), and the Degree of conformity. The Degree can be Conformant (if the dataset is fully conformant with the cited specification), Not Conformant (if the dataset does not conform to the cited specification) or Not Evaluated (if the conformance has not been evaluated).

📘

Recomendation 30

If a dataset is not yet conformant with all requirements of this data specification, it is recommended to include information on the conformance with the individual conformance classes specified in the Abstract Test Suite in Annex A.
📘

Recomendation 31

If a dataset is produced or transformed according to an external specification that includes specific quality assurance procedures, the conformity with this specification should be documented using the Conformity metadata element.
📘

Recomendation 32

If minimum data quality recommendations are defined then the statement on the conformity with these requirements should be included using the Conformity metadata element and referring to the relevant data quality conformance class in the Abstract Test Suite.

NOTE Currently no minimum data quality requirements are included in the IRs. The recommendation above should be included as a requirement in the IRs if minimum data quality requirements are defined at some point in the future.

📘

Recomendation 33

When documenting conformance with this data specification or one of the conformance classes defined in the Abstract Test Suite, the Specification sub-element should be given using the http URI identifier of the conformance class or using a citation including the following elements:

  • title: "INSPIRE Data Specification on Transport Networks – Draft Guidelines – <name of the conformance class>"

  • date:

    • dateType: publication

    • date: yyyy-mm-dd

EXAMPLE 1: The XML snippets below show how to fill the Specification sub-element for documenting conformance with the whole data specification on Addresses v3.0.1.

<gmd:DQ_ConformanceResult>
	<gmd:specification href="http://inspire.ec.europa.eu/conformanceClass/ad/3.0.1/tg" />
	<gmd:explanation> (...) </gmd:explanation>
	<gmd:pass> (...) </gmd:pass>
</gmd:DQ_ConformanceResult>

or (using a citation):

<gmd:DQ_ConformanceResult>
	<gmd:specification>
		<gmd:CI_Citation>
			<gmd:title>
				<gco:CharacterString>INSPIRE Data Specification on Transport Networks – Draft Guidelines</gco:CharacterString>
			</gmd:title>
			<gmd:date>
				<gmd:date>
					<gco:Date>yyyy-mm-dd</gco:Date>
				</gmd:date>
				<gmd:dateType>
					<gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resou
rces/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
				</gmd:dateType>
			</gmd:date>
		</gmd:CI_Citation>
	</gmd:specification>
	<gmd:explanation> (...) </gmd:explanation>
	<gmd:pass> (...) </gmd:pass>
</gmd:DQ_ConformanceResult>

EXAMPLE 2: The XML snippets below show how to fill the Specification sub-element for documenting conformance with the CRS conformance class of the data specification on Addresses v3.0.1.

<gmd:DQ_ConformanceResult>
	<gmd:specification href="http://inspire.ec.europa.eu/conformanceClass/ad/3.0.1/crs" />
	<gmd:explanation> (...) </gmd:explanation>
	<gmd:pass> (...) </gmd:pass>
</gmd:DQ_ConformanceResult>

or (using a citation):

<gmd:DQ_ConformanceResult>
	<gmd:specification>
		<gmd:CI_Citation>
			<gmd:title>
				<gco:CharacterString>INSPIRE Data Specification on Transport Networks – Draft Guidelines – CRS</gco:CharacterString>
			</gmd:title>
			<gmd:date>
				<gmd:date>
					<gco:Date>yyyy-mm-dd</gco:Date>
				</gmd:date>
				<gmd:dateType>
					<gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resou
rces/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
				</gmd:dateType>
			</gmd:date>
		</gmd:CI_Citation>
	</gmd:specification>
	<gmd:explanation> (...) </gmd:explanation>
	<gmd:pass> (...) </gmd:pass>
</gmd:DQ_ConformanceResult>

8.1.2. Lineage

📘

Recomendation 34

Following the ISO/DIS 19157 Quality principles, if a data provider has a procedure for the quality management of their spatial data sets then the appropriate data quality elements and measures defined in ISO/DIS 19157 should be used to evaluate and report (in the metadata) the results. If not, the Lineage metadata element (defined in Regulation 1205/2008/EC) should be used to describe the overall quality of a spatial data set.

According to Regulation 1205/2008/EC, lineage "is a statement on process history and/or overall quality of the spatial data set. Where appropriate it may include a statement whether the data set has been validated or quality assured, whether it is the official version (if multiple versions exist), and whether it has legal validity. The value domain of this metadata element is free text".

The Metadata Technical Guidelines based on EN ISO 19115 and EN ISO 19119 specifies that the statement sub-element of LI_Lineage (EN ISO 19115) should be used to implement the lineage metadata element.

📘

Recomendation 35

To describe the transformation steps and related source data, it is recommended to use the following sub-elements of LI_Lineage:

  • For the description of the transformation process of the local to the common INSPIRE data structures, the LI_ProcessStep sub-element should be used.

+ For the description of the source data the LI_Source sub-element should be used.

NOTE 1 In order to improve the interoperability, domain templates and instructions for using these free text elements (descriptive statements) may be specified here and/or in an Annex of this data specification.

8.1.3. Temporal reference

According to Regulation 1205/2008/EC, at least one of the following temporal reference metadata sub-elements shall be provided: temporal extent, date of publication, date of last revision, date of creation.

📘

Recomendation 36

It is recommended that at least the date of the last revision of a spatial data set should be reported using the Date of last revision metadata sub-element.

8.1.4. MD Element from MD Regulation

8.2. Metadata elements for interoperability

📕

IR Requirement
Article 13
Metadata required for Interoperability

The metadata describing a spatial data set shall include the following metadata elements required for interoperability:

  1. Coordinate Reference System: Description of the coordinate reference system(s) used in the data set.

  2. Temporal Reference System: ion of the temporal reference system(s) used in the data set.

    This element is mandatory only if the spatial data set contains temporal information that does not refer to the default temporal reference system.

  3. Encoding: Description of the computer language construct(s) specifying the representation of data objects in a record, file, message, storage device or transmission channel.

  4. Topological Consistency: Correctness of the explicitly encoded topological characteristics of the data set as described by the scope.

    This element is mandatory only if the data set includes types from the Generic Network Model and does not assure centreline topology (connectivity of centrelines) for the network.

  5. Character Encoding: The character encoding used in the data set.

    This element is mandatory only if an encoding is used that is not based on UTF-8.

  6. Spatial Representation Type: The method used to spatially represent geographic information.

These Technical Guidelines propose to implement the required metadata elements based on ISO 19115 and ISO/TS 19139.

The following TG requirements need to be met in order to be conformant with the proposed encoding.

📒

TG Requirement 3

Metadata instance (XML) documents shall validate without error against the used ISO 19139 XML schema.

NOTE Section 2.1.2 of the Metadata Technical Guidelines discusses the different ISO 19139 XML schemas that are currently available.

📒

TG Requirement 4

Metadata instance (XML) documents shall contain the elements and meet the INSPIRE multiplicity specified in the sections below.
📒

TG Requirement 5

The elements specified below shall be available in the specified ISO/TS 19139 path.
📘

Recomendation 37

The metadata elements for interoperability should be made available together with the metadata elements defined in the Metadata Regulation through an INSPIRE discovery service.

NOTE While this not explicitly required by any of the INSPIRE Implementing Rules, making all metadata of a data set available together and through one service simplifies implementation and usability.

8.2.1. Coordinate Reference System

Metadata element name Coordinate Reference System

Definition

Description of the coordinate reference system used in the dataset.

ISO 19115 number and name

  1. referenceSystemInfo

ISO/TS 19139 path

referenceSystemInfo

INSPIRE obligation / condition

mandatory

INSPIRE multiplicity

1..*

Data type(and ISO 19115 no.)

  1. MD_ReferenceSystem

Domain

To identify the reference system, the referenceSystemIdentifier (RS_Identifier) shall be provided.

NOTE More specific instructions, in particular on pre-defined values for filling the referenceSystemIdentifier attribute should be agreed among Member States during the implementation phase to support interoperability.

Implementing instructions

Example

referenceSystemIdentifier:
code: ETRS_89
codeSpace: INSPIRE RS registry

Example XML encoding

 
<gmd:referenceSystemInfo>
		<gmd:MD_ReferenceSystem>
			<gmd:referenceSystemIdentifier>
				<gmd:RS_Identifier>
					<gmd:code>
						<gco:CharacterString>ETRS89 </gco:CharacterString>
					</gmd:code>
					<gmd:codeSpace>
						<gco:CharacterString>INSPIRE RS registry</gco:CharacterString>
					</gmd:codeSpace>
				</gmd:RS_Identifier>
			</gmd:referenceSystemIdentifier>
		</gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>

Comments

8.2.2. Temporal Reference System

Metadata element name Temporal Reference System

Definition

Description of the temporal reference systems used in the dataset.

ISO 19115 number and name

  1. referenceSystemInfo

ISO/TS 19139 path

referenceSystemInfo

INSPIRE obligation / condition

Mandatory, if the spatial data set or one of its feature types contains temporal information that does not refer to the Gregorian Calendar or the Coordinated Universal Time.

INSPIRE multiplicity

0..*

Data type(and ISO 19115 no.)

  1. MD_ReferenceSystem

Domain

No specific type is defined in ISO 19115 for temporal reference systems. Thus, the generic MD_ReferenceSystem element and its reference SystemIdentifier (RS_Identifier) property shall be provided.

NOTE More specific instructions, in particular on pre-defined values for filling the referenceSystemIdentifier attribute should be agreed among Member States during the implementation phase to support interoperability.

Implementing instructions

Example

referenceSystemIdentifier:
code: GregorianCalendar
codeSpace: INSPIRE RS registry

Example XML encoding

 
<gmd:referenceSystemInfo>
	<gmd:MD_ReferenceSystem>
		<gmd:referenceSystemIdentifier>
			<gmd:RS_Identifier>
				<gmd:code>
			<gco:CharacterString>GregorianCalendar </gco:CharacterString>
				</gmd:code>
				<gmd:codeSpace>
					<gco:CharacterString>INSPIRE RS registry</gco:CharacterString>
				</gmd:codeSpace>
			</gmd:RS_Identifier>
		</gmd:referenceSystemIdentifier>
	</gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>

Comments

8.2.3. Encoding

Metadata element name Encoding

Definition

Description of the computer language construct that specifies the representation of data objects in a record, file, message, storage device or transmission channel

ISO 19115 number and name

  1. distributionFormat

ISO/TS 19139 path

distributionInfo/MD_Distribution/distributionFormat

INSPIRE obligation / condition

mandatory

INSPIRE multiplicity

1..*

Data type (and ISO 19115 no.)

  1. MD_Format

Domain

See B.2.10.4. The property values (name, version, specification) specified in section 5 shall be used to document the default and alternative encodings.

Implementing instructions

Example

name: <Application schema name> GML application schema
version: 5.0
specification: D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines

Example XML encoding

 
<gmd:MD_Format>
	<gmd:name>
		<gco:CharacterString>SomeApplicationSchema GML application schema</gco:CharacterString>
	</gmd:name>
	<gmd:version>
		<gco:CharacterString>5.0</gco:CharacterString>
	</gmd:version>
	<gmd:specification>
		<gco:CharacterString>D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines</gco:CharacterString>
	</gmd:specification>
</gmd:MD_Format>

Comments

8.2.4. Character Encoding

Metadata element name Character Encoding

Definition

The character encoding used in the data set.

ISO 19115 number and name

ISO/TS 19139 path

INSPIRE obligation / condition

Mandatory, if an encoding is used that is not based on UTF-8.

INSPIRE multiplicity

0..*

Data type (and ISO 19115 no.)

Domain

Implementing instructions

Example

-

Example XML encoding

 
Example XML encoding	<gmd:characterSet>
	<gmd:MD_CharacterSetCode codeListValue="8859part2" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CharacterSetCode">8859-2</gmd:MD_CharacterSetCode>
</gmd:characterSet>

Comments

8.2.5. Spatial representation type

Metadata element name Spatial representation type

Definition

The method used to spatially represent geographic information.

ISO 19115 number and name

  1. spatialRepresentationType

ISO/TS 19139 path

INSPIRE obligation / condition

Mandatory

INSPIRE multiplicity

1..*

Data type (and ISO 19115 no.)

B.5.26 MD_SpatialRepresentationTypeCode

Domain

Implementing instructions

Of the values included in the code list in ISO 19115 (vector, grid, textTable, tin, stereoModel, video), only vector, grid and tin should be used.

NOTE Additional code list values may be defined based on feedback from implementation.

Example

-

Example XML encoding

Comments

8.2.6. Data Quality – Logical Consistency – Topological Consistency

See section 8.3.2 for instructions on how to implement metadata elements for reporting data quality.

8.3. Recommended theme-specific metadata elements

📘

Recomendation 38

The metadata describing a spatial data set or a spatial data set series related to the theme Transport Networks should comprise the theme-specific metadata elements specified in Table 5.

The table contains the following information:

  • The first column provides a reference to a more detailed description.

  • The second column specifies the name of the metadata element.

  • The third column specifies the multiplicity.

Table 5 – Optional theme-specific metadata elements for the theme Transport Networks

Section

Metadata element

Multiplicity

8.3.1

Maintenance Information

0..1

8.3.2

Logical Consistency – Conceptual Consistency

0..*

8.3.2

Logical Consistency – Domain Consistency

0..*

8.3.2

Completeness – Commission

0..*

8.3.2

Completeness – Omission

0..*

8.3.2

Logical Consistency – Topological Consistency

0..*

8.3.2

Positional Accuracy – Absolute or external accuracy

0..*

8.3.2

Logical Consistency - Format Consistency

0..*

8.3.2

Thematic Accuracy – Thematic Classification Correctness

0..*

8.3.2

Thematic accuracy – Non-quantitative correctness

0..*
📘

Recomendation 39

For implementing the metadata elements included in this section using ISO 19115, ISO/DIS 19157 and ISO/TS 19139, the instructions included in the relevant sub-sections should be followed.

8.3.1. Maintenance Information

Metadata element name Maintenance information

Definition

Information about the scope and frequency of updating

ISO 19115 number and name

30. resourceMaintenance

ISO/TS 19139 path

identificationInfo/MD_Identification/resourceMaintenance

INSPIRE obligation / condition

optional

INSPIRE multiplicity

0..1

Data type(and ISO 19115 no.)

  1. MD_MaintenanceInformation

Domain

This is a complex type (lines 143-148 from ISO 19115).

At least the following elements should be used (the multiplicity according to ISO 19115 is shown in parentheses):

  • maintenanceAndUpdateFrequency [1]: frequency with which changes and additions are made to the resource after the initial resource is completed / domain value: MD_MaintenanceFrequencyCode:

  • updateScope [0..*]: scope of data to which maintenance is applied / domain value: MD_ScopeCode

  • maintenanceNote [0..*]: information regarding specific requirements for maintaining the resource / domain value: free text

Implementing instructions

Example

Example XML encoding

Comments

8.3.2. Metadata elements for reporting data quality

📘

Recomendation 40

For reporting the results of the data quality evaluation, the data quality elements, sub-elements and (for quantitative evaluation) measures defined in chapter 7 should be used.
📘

Recomendation 41

The metadata elements specified in the following sections should be used to report the results of the data quality evaluation. At least the information included in the row "Implementation instructions" should be provided.

The first section applies to reporting quantitative results (using the element DQ_QuantitativeResult), while the second section applies to reporting non-quantitative results (using the element DQ_DescriptiveResult).

📘

Recomendation 42

If a dataset does not pass the tests of the Application schema conformance class (defined in Annex A), the results of each test should be reported using one of the options described in sections 8.3.2.1 and 8.3.2.2.

NOTE 1 If using non-quantitative description, the results of several tests do not have to be reported separately, but may be combined into one descriptive statement.

NOTE 2 The sections 8.3.2.1 and 8.3.2.2 may need to be updated once the XML schemas for ISO 19157 have been finalised.

The scope for reporting may be different from the scope for evaluating data quality (see section 7). If data quality is reported at the data set or spatial object type level, the results are usually derived or aggregated.

📘

Recomendation 43

The scope element (of type DQ_Scope) of the DQ_DataQuality subtype should be used to encode the reporting scope.

Only the following values should be used for the level element of DQ_Scope: Series, Dataset, featureType.

If the level is featureType the levelDescription/MDScopeDescription/features element (of type Set< GF_FeatureType>) shall be used to list the feature type names.

NOTE In the level element of DQ_Scope, the value featureType is used to denote spatial object type.

8.3.2.1. Guidelines for reporting quantitative results of the data quality evaluation
Metadata element name See chapter 7

Definition

See chapter 7

ISO/DIS 19157 number and name

  1. report

ISO/TS 19139 path

dataQualityInfo/*/report

INSPIRE obligation / condition

optional

INSPIRE multiplicity

0..*

Data type (and ISO/DIS 19157 no.)

Corresponding DQ_xxx subelement from ISO/DIS 19157, e.g. 12. DQ_CompletenessCommission

Domain

Lines 7-9 from ISO/DIS 19157

  1. DQ_MeasureReference (C.2.1.3)

  2. DQ_EvaluationMethod (C.2.1.4.)

  3. DQ_Result (C2.1.5.)

Implementing instructions

  1. nameOfMeasure

NOTE This should be the name as defined in Chapter 7.

  1. evaluationMethodType

  2. evaluationMethodDescription

NOTE If the reported data quality results are derived or aggregated (i.e. the scope levels for evaluation and reporting are different), the derivation or aggregation should also be specified using this property.

  1. dateTime

NOTE This should be data or range of dates on which the data quality measure was applied.

  1. DQ_QuantitativeResult / 64. value

NOTE The DQ_Result type should be DQ_QuantitativeResult and the value(s) represent(s) the application of the data quality measure (39.) using the specified evaluation method (42-43.)

Example

See Table E.12 — Reporting commission as metadata (ISO/DIS 19157)

Example XML encoding
8.3.2.2. Guidelines for reporting descriptive results of the Data Quality evaluation
Metadata element name See chapter 7

Definition

See chapter 7

ISO/DIS 19157 number and name

  1. report

ISO/TS 19139 path

dataQualityInfo/*/report

INSPIRE obligation / condition

optional

INSPIRE multiplicity

0..*

Data type (and ISO/DIS 19157 no.)

Corresponding DQ_xxx subelement from ISO/DIS 19157, e.g. 12. DQ_CompletenessCommission

Domain

Line 9 from ISO/DIS 19157

  1. DQ_Result (C2.1.5.)

Implementing instructions

  1. DQ_DescripitveResult / 68. statement

NOTE The DQ_Result type should be DQ_DescriptiveResult and in the statement (68.) the evaluation of the selected DQ sub-element should be expressed in a narrative way.

Example

See Table E.15 — Reporting descriptive result as metadata (ISO/DIS 19157)

Example XML encoding

9. Delivery

9.1. Updates

📕

IR Requirement
Article 8
Updates

  1. Member States shall make available updates of data on a regular basis.

  2. All updates shall be made available at the latest 6 months after the change was applied in the source data set, unless a different period is specified for a specific spatial data theme in Annex II.

NOTE In this data specification, no exception is specified, so all updates shall be made available at the latest 6 months after the change was applied in the source data set.

9.2. Delivery medium

According to Article 11(1) of the INSPIRE Directive, Member States shall establish and operate a network of services for INSPIRE spatial data sets and services. The relevant network service types for making spatial data available are:

  • view services making it possible, as a minimum, to display, navigate, zoom in/out, pan, or overlay viewable spatial data sets and to display legend information and any relevant content of metadata;

  • download services, enabling copies of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly;

  • transformation services, enabling spatial data sets to be transformed with a view to achieving interoperability.

NOTE For the relevant requirements and recommendations for network services, see the relevant Implementing Rules and Technical Guidelines[21].

EXAMPLE 1 Through the Get Spatial Objects function, a download service can either download a pre-defined data set or pre-defined part of a data set (non-direct access download service), or give direct access to the spatial objects contained in the data set, and download selections of spatial objects based upon a query (direct access download service). To execute such a request, some of the following information might be required:

  • the list of spatial object types and/or predefined data sets that are offered by the download service (to be provided through the Get Download Service Metadata operation),

  • and the query capabilities section advertising the types of predicates that may be used to form a query expression (to be provided through the Get Download Service Metadata operation, where applicable),

  • a description of spatial object types offered by a download service instance (to be provided through the Describe Spatial Object Types operation).

EXAMPLE 2 Through the Transform function, a transformation service carries out data content transformations from native data forms to the INSPIRE-compliant form and vice versa. If this operation is directly called by an application to transform source data (e.g. obtained through a download service) that is not yet conformant with this data specification, the following parameters are required:

  • Input data (mandatory). The data set to be transformed.

    • Source model (mandatory, if cannot be determined from the input data). The model in which the input data is provided.

  • Target model (mandatory). The model in which the results are expected.

  • Model mapping (mandatory, unless a default exists). Detailed description of how the transformation is to be carried out.

9.3. Encodings

The IRs contain the following two requirements for the encoding to be used to make data available.

📕

IR Requirement
Article 7
Encoding

1. Every encoding rule used to encode spatial data shall conform to EN ISO 19118. In particular, it shall specify schema conversion rules for all spatial object types and all attributes and association roles and the output data structure used.

2. Every encoding rule used to encode spatial data shall be made available.

2a. Every encoding rule used to encode spatial data shall also specify whether and how to represent attributes and association roles for which a corresponding value exists but is not contained in the spatial data sets maintained by a Member State, or cannot be derived from existing values at reasonable costs.

NOTE ISO 19118:2011 specifies the requirements for defining encoding rules used for interchange of geographic data within the set of International Standards known as the "ISO 19100 series". An encoding rule allows geographic information defined by application schemas and standardized schemas to be coded into a system-independent data structure suitable for transport and storage. The encoding rule specifies the types of data being coded and the syntax, structure and coding schemes used in the resulting data structure. Specifically, ISO 19118:2011 includes

  • requirements for creating encoding rules based on UML schemas,

  • requirements for creating encoding services, and

  • requirements for XML-based encoding rules for neutral interchange of data.

While the IRs do not oblige the usage of a specific encoding, these Technical Guidelines propose to make data related to the spatial data theme Transport Networks available at least in the default encoding(s) specified in section 0. In this section, a number of TG requirements are listed that need to be met in order to be conformant with the default encoding(s).

The proposed default encoding(s) meet the requirements in Article 7 of the IRs, i.e. they are conformant with ISO 19118 and (since they are included in this specification) publicly available.

9.3.1. Default Encoding(s)

9.3.1.1. Specific requirements for GML encoding

This data specification proposes the use of GML as the default encoding, as recommended in sections 7.2 and 7.3 of [DS-D2.7]. GML is an XML encoding in compliance with ISO 19118, as required in Article 7(1). For details, see [ISO 19136], and in particular Annex E (UML-to-GML application schema encoding rules).

The following TG requirements need to be met in order to be conformant with GML encodings.

📒

TG Requirement 6

Data instance (XML) documents shall validate without error against the provided XML schema.

NOTE 1 Not all constraints defined in the application schemas can be mapped to XML. Therefore, the following requirement is necessary.

NOTE 2 The obligation to use only the allowed code list values specified for attributes and most of the constraints defined in the application schemas cannot be mapped to the XML sch. They can therefore not be enforced through schema validation. It may be possible to express some of these constraints using other schema or rule languages (e.g. Schematron), in order to enable automatic validation.

9.3.1.2. Default encoding(s) for application schema Common Transport Elements

Name: Common Transport Elements GML Application Schema
Version: 5.0
Specification: D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines
Character set: UTF-8

The xml schema document is available from http://inspire.ec.europa.eu/schemas/tn/5.0/CommonTransportElements.xsd

9.3.1.2.1. Encoding rules used

The encoding rule used for this encoding is specified in Annex B of [DS-D2.7].

NOTE Annex B of [DS-D2.7], version 3.3rc3, requires that the "encoding rule specified in ISO 19136 Annex E with the extensions in GML 3.3 shall be applied with the additional rules stated in this Annex. For types within the scope of the ISO/TS 19139 encoding rule, the encoding rule of ISO/TS 19139 shall be applied."

9.3.1.3. Default encoding(s) for application schema Road transport Elements

Name: Road Transport Elements GML Application Schema
Version: 5.0
Specification: D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines
Character set: UTF-8

The xml schema document is available from
http://inspire.ec.europa.eu/schemas/tn-ro/5.0/RoadTransportNetwork.xsd

9.3.1.3.1. Encoding rules used

The encoding rule used for this encoding is specified in Annex B of [DS-D2.7].

NOTE Annex B of [DS-D2.7], version 3.3rc3, requires that the "encoding rule specified in ISO 19136 Annex E with the extensions in GML 3.3 shall be applied with the additional rules stated in this Annex. For types within the scope of the ISO/TS 19139 encoding rule, the encoding rule of ISO/TS 19139 shall be applied."

9.3.1.4. Default encoding(s) for application schema Rail Transport Elements

Name: Rail Transport Elements GML Application Schema
Version: 5.0
Specification: D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines
Character set: UTF-8

The xml schema document is available from https://inspire.ec.europa.eu/schemas/tn-ra/5.0/RailwayTransportNetwork.xsd

9.3.1.4.1. Encoding rules used

The encoding rule used for this encoding is specified in Annex B of [DS-D2.7].

NOTE Annex B of [DS-D2.7], version 3.3rc3, requires that the "encoding rule specified in ISO 19136 Annex E with the extensions in GML 3.3 shall be applied with the additional rules stated in this Annex. For types within the scope of the ISO/TS 19139 encoding rule, the encoding rule of ISO/TS 19139 shall be applied."

9.3.1.5. Default encoding(s) for application schema Cable Transport Elements

Name: Cable Transport Elements GML Application Schema
Version: 4.0
Specification: D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines
Character set: UTF-8

The xml schema document is available from
http://inspire.ec.europa.eu/schemas/tn-c/4.0/CableTransportNetwork.xsd

9.3.1.5.1. Encoding rules used

The encoding rule used for this encoding is specified in Annex B of [DS-D2.7].

NOTE Annex B of [DS-D2.7], version 3.3rc3, requires that the "encoding rule specified in ISO 19136 Annex E with the extensions in GML 3.3 shall be applied with the additional rules stated in this Annex. For types within the scope of the ISO/TS 19139 encoding rule, the encoding rule of ISO/TS 19139 shall be applied."

9.3.1.6. Default encoding(s) for application schema Water Transport Elements

Name: Water Transport Elements GML Application Schema
Version: 5.0
Specification: D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines
Character set: UTF-8

The xml schema document is available from
http://inspire.ec.europa.eu/schemas/tn-w/5.0/WaterTransportNetwork.xsd.

9.3.1.6.1. Encoding rules used

The encoding rule used for this encoding is specified in Annex B of [DS-D2.7].

NOTE Annex B of [DS-D2.7], version 3.3rc3, requires that the "encoding rule specified in ISO 19136 Annex E with the extensions in GML 3.3 shall be applied with the additional rules stated in this Annex. For types within the scope of the ISO/TS 19139 encoding rule, the encoding rule of ISO/TS 19139 shall be applied."

9.3.1.7. Default encoding(s) for application schema Air Transport Elements

Name: Air Transport Elements Application Schema
Version: 4.0
Specification: D2.8.I.7 Data Specification on Transport Networks – Technical Guidelines
Character set: UTF-8

The xml schema document is available from
http://inspire.ec.europa.eu/schemas/tn-a/4.0/AirTransportNetwork.xsd.

9.3.1.7.1. Encoding rules used

The encoding rule used for this encoding is specified in Annex B of [DS-D2.7].

NOTE Annex B of [DS-D2.7], version 3.3rc3, requires that the "encoding rule specified in ISO 19136 Annex E with the extensions in GML 3.3 shall be applied with the additional rules stated in this Annex. For types within the scope of the ISO/TS 19139 encoding rule, the encoding rule of ISO/TS 19139 shall be applied."

10. Data Capture

For every spatial object type: Capturing rules describing the criteria which spatial objects are part of spatial data sets ("selection criteria") as free text. Typical selection criteria are minimum area or length or functional characteristics like the class of a road.

Data capturing rules are the main element to define the targeted level of detail. For instance, there may be a need for transport networks on two levels of detail (at the European level, scale about 1:1000000 and at the local level, scale about 1:10000) with very similar feature catalogues. However, the data will be very different. This difference is a result of different capturing rules / selection criteria for both levels of detail.

The data capturing processes used by a data provider, i.e. the "how", are not relevant for this component.

The topics in this chapter highlight specific cases that require specific attention in collecting and assembling data and information that constitutes the components of Transport networks (Road, Rail, Cable, Water and Air).

10.1. Centrelines

The primary way of representing a network is by a centreline (ie a line that approximates the centre of the real world object. It would be prohibitively expensive and impracticable to faithfully record the true centreline since this would result in an irregular line and far too many data points. Therefore a pragmatic approach is often taken which results in a much smoother line requiring the minimum number of data points to represent the object.

However problems can arise when too few points are used and the line will no longer be smooth or useful in most applications. Equally the centreline may often be combined with (topographic) area objects e.g. the paved or metalled surface, or track. It may also be combined with other themes (e.g. run closely adjacent to a river or another form of transport (railway and road in a narrow gorge for example). It is therefore important that the centreline falls within the physical boundary of the object it represents.

📕

IR Requirement
Annex II, Section 7.9.5
Theme-specific Requirements – Centrelines

The centrelines of Road and Rail objects shall fall within the extent of the physical real world object that they represent if the Link is indicated as not being 'fictitious'.
image

Not acceptable

The centreline falls outside the real world object
image

Acceptable

The centreline falls inside the real world object
image

Not acceptable

The centreline falls outside the real world object
image

Not acceptable

The centreline falls inside the real world object but does not follow the shape faithfully.
image

Acceptable

The centreline falls inside the real world object and while it does not follow the exact centreline it is acceptable

Figure 42 – Acceptable and non acceptable forms of centreline representation.

10.2. Ensuring Network Connectivity

This data specification does not incorporate a topological model for the reasons given in Chapters 4 and 5.1.1.1. Since a users system will build the topology for an application it is essential that the data is captured in such a way that this topology build can be undertaken automatically, repeatedly and faultlessly each time.

Therefore the data has to be supplied to the user with topology "implicit" in the structure (i.e. it must be "clean"). This implicit topology is based on coincidence which does not have to be absolute but relies on a connectivity tolerance. This connectivity tolerance will be supplied as metadata with the transport data. (see Section 7.1.6)

When automatically constructing topological relationships:

  • All points, nodes, vertices and link ends that are located at a distance of less than the connectivity tolerance of each other are considered to coincide,

  • All points, nodes, vertices and link ends that are located at a distance of more than the connectivity tolerance of each other are considered not to coincide.

To ensure automatic and unambiguous creation of centreline topology:

  • All link ends and the optional node that take part in a connection have to be positioned at a distance of less than the connectivity tolerance from each other,

  • Link ends and nodes that are not connected shall always be separated by a distance that is greater than the connectivity tolerance.

This will ensure the correct connectivity between links and the nodes in the system. Supporting quality criteria will be found in Section 7.1.6

📕

IR Requirement
Annex II, Section 7.9.6
Theme-specific Requirements – Ensuring Network Connectivity

  1. Wherever a connection exists in a transport network, all connected link ends and the optional node that take part in this connection have to be positioned at a distance of less than the connectivity tolerance from each other.
📕

IR Requirement
Annex II, Section 7.9.6
Theme-specific Requirements – Ensuring Network Connectivity

  1. Link ends and nodes that are not connected shall always be separated by a distance that is greater than the connectivity tolerance.
📕

IR Requirement
Annex II, Section 7.9.6
Theme-specific Requirements – Ensuring Network Connectivity

  1. In data sets where both transport links and nodes are present, the relative position of nodes and link ends in relation to the specified connectivity tolerance shall correspond to the associations that exist between them in the dataset.
TopologyOK_3

Acceptable

The perfect case where the node and all link ends share the same coordinates.
TopologyOK_1

Acceptable

The three link ends (a, b and c) and the node are all within a distance of less than the connectivity tolerance (indicated by the blue circle).

All of these elements will be assumed connected during an automatic topology build.
TopologyNA_1

Not acceptable

The three link ends (a, b and c) and the node are all within a distance of less than the connectivity tolerance.

Link end (d) lies within a distance of less than the connectivity tolerance from link end (c), but at a distance greater than the tolerance from link ends (a) and (b) and the transport node.

The connectivity is ambiguous and the topology building would fail.
TopologyOK_2

Acceptable (but possible error)

The three link ends (a, b and c) and the node are all within a distance of less than the connectivity tolerance and will be assumed connected during an automatic topology build.

Link end (d) is at a distance greater than the tolerance from all three link ends and the node. It will be considered not connected (dangle).

Note: while this is an acceptable situation for automatic topology build, it can constitute an error in the data: if, in reality, (d) is connected to (a), (b) and (c) it should be moved to within the tolerance distance from all three link ends and the node.

Figure 43 – Acceptable and unacceptable positioning of link ends and nodes.

10.3. Linear Referencing

Linear referencing as defined in the ISO 19148:2012 will be adopted and aligned with the GNM (and hence this data specification) with after it reaches DIS status, The adoption in the Transport networks data specification is limited to a simple model at this stage.

In general it is expected that linear referencing will be used to model the relationships of objects that are associated with an network, but where the position of those associated objects is not known (or required) to a very high level of absolute accuracy ~ better than 1-3m at local level (e.g. traffic accidents, planned works, restrictions).

The position of centrelines and nodes in a network in many cases will vary from the "true position" (since the centreline is rarely that and the node is not a tangible physical feature or location (see 10.1 above).

Where absolute accuracy is required (e.g. the location of drain covers, excavations, line side signalling equipment, masts etc) such objects should be reused, and referenced, if they already exist e.g. as topographic features.

10.4. Alternative and Multiple Representations

Alternative and multiple representations are discussed further in Annex B.1.

Alternative Representations

Where centreline and topographic area objects coexist it is important that users holding information on one of these forms can share information with another e.g. details of a planned excavation at the topographic level with the corresponding centreline representation to plan diversions during the time of the works. It is important therefore that these alternative representations are well synchronised and follow the requirement in 10.1. Cross referencing them will support easy and unambiguous data exchange and support synchronised maintenance (see Annex B.1) – which ever organisation is responsible for the alternative forms.

📘

Recomendation 44

Alternative representations should be cross referenced to support data sharing and synchronised maintenance.

Multiple Representations

In this sense the different resolutions may extend from the local to European level in a number of steps (levels of detail). An ideal model is described in D2.6 A.19 but has yet to be fully developed and realised.

At the moment transforming existing vector datasets, at different levels of detail, beyond the local level to this data specification will not necessarily result in a set of harmonised transport networks for each of the themes Road, Rail, Water (this will be dependent on the Hydrography specification) and Air (where there are probably fewer levels of detail).

Nevertheless as a step towards a more harmonised model users should aim to collect their own application data and hold that once and reference it to each corresponding level of detail (rather than embed the application data in the local or intermediate level). This will promote reuse, easier data sharing and make national and European reporting (through aggregation) easier.

📘

Recomendation 45

As a step towards a more harmonised set of levels of detail, users should hold their application data once and simply reference this to each level of detail in a network.

11. Portrayal

This clause defines the rules for layers and styles to be used for portrayal of the spatial object types defined for this theme. Portrayal is regulated in Article 14 of the IRs.

📕

IR Requirement
Article 14
Portrayal

  1. For the portrayal of spatial data sets using a view network service as specified in Commission Regulation No 976/2009 ([22]), the following shall be available:

    1. the layers specified in Annex II for the theme or themes the data set is related to;

    2. for each layer at least a default portrayal style, with as a minimum an associated title and a unique identifier.

  1. For each layer, Annex II defines the following:

    1. a human readable title of the layer to be used for display in user interface;

    2. the spatial object type(s), or sub-set thereof, that constitute(s) the content of the layer.

In section 0, the types of layers are defined that are to be used for the portrayal of the spatial object types defined in this specification. A view service may offer several layers of the same type, one for each dataset that it offers data on a specific topic.

NOTE The layer specification in the IRs only contains the name, a human readable title and the (subset(s) of) spatial object type(s), that constitute(s) the content of the layer. In addition, these Technical Guidelines suggest keywords for describing the layer.

📘

Recomendation 46

It is recommended to use the keywords specified in section 0 in the Layers Metadata parameters of the INSPIRE View service (see Annex III, Part A, section 2.2.4 in Commission Regulation (EC) No 976/2009).

Section 11.2 specifies one style for each of these layers. It is proposed that INSPIRE view services support this style as the default style required by Article 14(1b).

📒

TG Requirement 7

For each layer specified in this section, the styles defined in section 11.2 shall be available.

NOTE The default style should be used for portrayal by the view network service if no user-defined style is specified in a portrayal request for a specific layer.

In section 11.1.1, further styles can be specified that represent examples of styles typically used in a thematic domain. It is recommended that also these styles should be supported by INSPIRE view services, where applicable.

📘

Recomendation 47

In addition, it is recommended that, where applicable, INSPIRE view services also support the styles defined in section 11.1.

Where XML fragments are used in the following sections, the following namespace prefixes apply:

  • sld="http://www.opengis.net/sld" (WMS/SLD 1.1)

  • se="http://www.opengis.net/se" (SE 1.1)

  • ogc="http://www.opengis.net/ogc" (FE 1.1)

11.1. Layers to be provided by INSPIRE view services

Layer Name Layer Title Spatial object type(s) Keywords

TN.CommonTransportElements.TransportNode

Generic Transport Node Default Style

Transport Node

Generic Transport Node, default style, Transport Networks.

TN.CommonTransportElements.TransportLink

Generic Transport Link Default Style

Transport Link

Generic Transport Node, default style, Transport Networks.

TN.CommonTransportElements.TransportArea

Generic Transport Area Default Style

Area

Generic Transport Area, default style, Transport Networks.

TN.RoadTransportNetwork.RoadLink

RoadLink default Style

RoadLink

Transport Networks, RoadLink, Default Style

TN.RoadTransportNetwork.VehicleTrafficArea

Vehicle traffic Area Default Style

VehicleTrafficArea

Transport Network, Road Transport Network, Vehicle Traffic Area, Default Style

TN.RoadTransportNetwork.RoadServiceArea

Road Service Area Default Style

RoadServiceArea

Transport Network, Road Transport Network,Road Service Area, Default Style

TN.RoadTransportNetwork.RoadArea

Road Area Default Style

RoadArea

Transport Network, Road Transport Network, Road Area, Default Style

TN.RailTransportNetwork.RailwayLink

Railway Link Default Style

RailwayLink

Transport Network, Rail Transport Network, Railway Link, Default Style

TN.RailTransportNetwork.RailwayStationArea

Railway Station Area Default Style

RailwayStationArea

Transport Network, Rail Transport Network, Railway Station Area, Default Style

TN.RailTransportNetwork.RailwayYardArea

Railway Yard Area Default Style

RailwayYardAreaDefaultStyle

Transport Network, Rail Transport Network, Railway Yard Area, Default Style

TN.RailTransportNetwork.RailwayArea

RailwayArea

RailwayAreaDefaultStyle

Transport Network, Rail Transport Network, Railway Area, Default Style

TN.WaterTransportNetwork.WaterwayLink

Waterway Link Default Style

WaterwayLinkDefaultStyle

Transport Network, Water Transport Network, Waterway Link, Default Style

TN.WaterTransportNetwork.FairwayArea

Fairway Area Default Style

FairwayAreaDefaultStyle

Transport Network, Water Transport Network, Fairway Area, Default Style

TN.WaterTransportNetwork.PortArea

Port Area Default Style

PortAreaDefaultStyle

Transport Network, Water Transport Network, Port Area, Default Style

TN.AirTransportNetwork.AirLink

Air Link Default Style

AirLinkDefaultStyle

Transport Network, Air Transport Network, Air Link, Default Style

TN.AirTransportNetwork.AerodromeArea

Aerodrome Area Default Style

AerodromeAreaDefaultStyle

Transport Network, Air Transport Network, Aerodrome Area, Default Style

TN.AirTransportNetwork.RunwayArea

Runway Area Default Style

RunwayAreaDefaultStyle

Transport Network, Air Transport Network, Runway Area, Default Style

TN.AirTransportNetwork.AirSpaceArea

Air Space Area Default Style

AirSpaceAreaDefaultStyle

Transport Network, Air Transport Network, Air Space Area, Default Style

TN.AirTransportNetwork.ApronArea

Apron Area Default Style

ApronAreaDefaultStyle

Transport Network, Air Transport Network, Apron Area, Default Style

TN.AirTransportNetwork.TaxiwayArea

Taxiway Area Default Style

TaxiwayAreaDefaultStyle

Transport Network, Air Transport Network, Taxi Runway Area, Default Style

TN.CableTransportNetwork.CablewayLink

Cableway Link Default Style

CableLinkDefaultStyle

Transport Network, Cable Transport Network, Cable Link, Default Style

11.1.1. Layers organisation

None.

11.2. Styles required to be supported by INSPIRE view services

11.2.1. Styles for the layer TN.CommonTransportElements.TransportNode

Style Name TN.CommonTransportElements.TransportNode.Default

Default Style

yes

Style Title

Generic Transport Node Default Style

Style Abstract

The geometry is rendered as a circle with a size of 3 pixels, with a red (#FF0000) fill and a black outline (#000000).

Symbology

 
  <sld:NamedLayer>
    <se:Name>TN.CommonTransportElements.TransportNode</se:Name>
    <sld:UserStyle>
      <se:Name> TN.CommonTransportElements.TransportNode.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Generic Node Default Style</se:Title>
          <se:Abstract>The geometry is rendered as a circle with a size of 3 pixels, with a red (#FF0000) fill and a black outline (#000000).</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>Network:Node</se:FeatureTypeName>
        <se:Rule>
          <se:PointSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry
              </ogc:PropertyName>
            </se:Geometry>
            <se:Graphic/>
          </se:PointSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.2. Styles for the layer TN.CommonTransportElements.TransportLink

Style Name TN.CommonTransportElements.TransportLink.Default

Default Style

yes

Style Title

Generic Transport Link Default Style

Style Abstract

The geometry is rendered as a solid Black line with a stroke width of 3 pixel (#000000). Ends are rounded and have a 2 pixel black casing (#000000).

Symbology

 
  <sld:NamedLayer>
    <se:Name>TN.CommonTransportElements.TransportLink</se:Name>
    <sld:UserStyle>
      <se:Name> TN.CommonTransportElements.TransportLink.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Generic Link Default Style</se:Title>
          <se:Abstract> The geometry is rendered as a solid Black line with a stroke width of 3 pixel (#000000). Ends are rounded and have a 2 pixel black casing (#000000).</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>Network:Link</se:FeatureTypeName>
        <se:Rule>
          <se:LineSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:centerlineGeometry
            </se:Geometry>
            <se:Stroke/>
          </se:LineSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.3. Styles for the layer TN.CommonTransportElements.TransportArea

Style Name TN.CommonTransportElements.TransportArea.Default

Default Style

yes

Style Title

Generic Transport Area Default Style

Style Abstract

The geometry is rendered using a grey (#A9A9A9) fill and a solid black (#000000) outline with a stroke width of 1 pixel.

Symbology

 
  <sld:NamedLayer>
    <se:Name>TN.CommonTransportElements.TransportArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.CommonTransportElements.TransportArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Generic Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a grey (#A9A9A9) fill and a solid black (#000000) outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>Network:Area</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.4. Styles for the layer TN.RoadTransportNetwork.RoadLink

Style Name TN.RoadTransportNetwork.RoadLink.Default

Default Style

yes

Style Title

RoadLink Default Style

Style Abstract

The geometry is rendered as a solid green line with a stroke width of 3 pixel (#008000). Ends are rounded and have a 2 pixel black casing (#000000).

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.RoadTransportNetwork.RoadLink</se:Name>
    <sld:UserStyle>
      <se:Name> TN.RoadTransportNetwork.RoadLink.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>RoadLink Default Style</se:Title>
          <se:Abstract> The geometry is rendered as a solid Green line with a stroke width of 3 pixel (#008000).  Ends are rounded and have a 2 pixel black casing (#000000).</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:RoadLink</se:FeatureTypeName>
        <se:Rule>
          <se:LineSymbolizer>
            <se:Geometry>
             <ogc:PropertyName>Network:centrelineGeometry
             </ogc:PropertyName>
            </se:Geometry>
            <se:Stroke/>
          </se:LineSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.5. Styles for the layer TN.RoadTransportNetwork.RoadServiceArea

Style Name TN.RoadTransportNetwork.RoadServiceArea.Default

Default Style

yes

Style Title

Road Service Area Default Style

Style Abstract

The geometry is rendered using a grey (#A9A9A9) fill and a solid black (#000000) outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.RoadTransportNetwork.RoadServiceArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.RoadTransportNetwork.RoadServiceArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Road Service Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a grey (#A9A9A9) fill and a solid black (#000000) outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:RoadServiceArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.6. Styles for the layer TN.RoadTransportNetwork.RoadArea

Style Name TN.RoadTransportNetwork.RoadArea.Default

Default Style

yes

Style Title

Road Area Default Style

Style Abstract

The geometry is rendered using a grey (#A9A9A9) fill and a solid black (#000000) outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.RoadTransportNetwork.RoadArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.RoadTransportNetwork.RoadArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Road Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a grey (#A9A9A9) fill and a solid black (#000000) outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:RoadArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.7. Styles for the layer TN.RoadTransportNetwork.VehicleTrafficArea

Style Name TN.RoadTransportNetwork.VehicleTrafficArea.Default

Default Style

yes

Style Title

Vehicle Traffic Area Default Style

Style Abstract

The geometry is rendered using a grey (#A9A9A9) fill and a solid black (#000000) outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.RoadTransportNetwork.VehicleTrafficArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.RoadTransportNetwork.VehicleTrafficArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Vehicle Traffic Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a grey (#A9A9A9) fill and a solid black (#000000) outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:VehicleTrafficArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.8. Styles for the layer TN.RailTransportNetwork.RailwayLink

Style Name TN.RailTransportNetwork.RailwayLink.Default

Default Style

yes

Style Title

Railway Link Default Style

Style Abstract

The geometry is rendered as a solid Black line with a stroke width of 3 pixel (#000000). Ends are rounded and have a 2 pixel black casing (#000000).

Symbology

 
  <sld:NamedLayer>
    <se:Name>TN.RailTransportNetwork.RailwayLink</se:Name>
    <sld:UserStyle>
      <se:Name> TN.RailTransportNetwork.RailwayLink.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Railway Link Default Style</se:Title>
          <se:Abstract> The geometry is rendered as a solid Black line with a stroke width of 3 pixel (#000000).  Ends are rounded and have a 2 pixel black casing (#000000).</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:RailwayLink</se:FeatureTypeName>
        <se:Rule>
          <se:LineSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:centerlineGeometry </ogc:PropertyName>
            </se:Geometry>
            <se:Stroke/>
          </se:LineSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.9. Styles for the layer TN.RailTransportNetwork.RailwayStationArea

Style Name TN.RailTransportNetwork.RailwayStationArea.Default

Default Style

yes

Style Title

Railway Station Area Default Style

Style Abstract

The geometry is rendered using a Brown (#8B4513) fill and a solid black (#000000) outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.RailTransportNetwork.RailwayStationArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.RailTransportNetwork.RailwayStationArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Railway Station Area</se:Title>
          <se:Abstract> The geometry is rendered using a Brown (#8B4513) fill and a solid black (#000000) outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
      <se:FeatureTypeName>TN:RailwayStationArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.10. Styles for the layer TN.RailTransportNetwork.RailwayYardArea

Style Name TN.RailTransportNetwork.RailwayYardArea.Default

Default Style

yes

Style Title

Railway Yard Area Default Style

Style Abstract

The geometry is rendered using a Brown (#8B4513) fill and a solid black (#000000) outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.RailTransportNetwork.RailwayYardArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.RailTransportNetwork.RailwayYardArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Railway Yard Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a Brown (#8B4513) fill and a solid black (#000000) outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
      <se:FeatureTypeName>TN:RailwayYardArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.11. Styles for the layer TN.RailTransportNetwork.RailwayArea

Style Name TN.RailTransportNetwork.RailwayArea.Default

Default Style

yes

Style Title

Railway Area Default Style

Style Abstract

The geometry is rendered using a Brown (#8B4513) fill and a solid black (#000000) outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.RailTransportNetwork.RailwayArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.RailTransportNetwork.RailwayArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Railway Yard Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a Brown (#8B4513) fill and a solid black (#000000) outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
      <se:FeatureTypeName>TN:RailwayYardArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.12. Styles for the layer TN.WaterTransportNetwork.WaterwayLink

Style Name TN.WaterTransportNetwork.WaterwayLink.Default

Default Style

yes

Style Title

Waterway Link Default Style

Style Abstract

The geometry is rendered as a solid Violet line with a stroke width of 3 pixel (#EE82EE). Ends are rounded and have a 2 pixel black casing (#000000).

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.WaterTransportNetwork.WaterwayLink</se:Name>
    <sld:UserStyle>
      <se:Name> TN.WaterTransportNetwork.WaterwayLink.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Waterway Link Default Style</se:Title>
          <se:Abstract>The geometry is rendered as a solid violet line with a stroke width of 3 pixel (#EE82EE).  Ends are rounded and have a 2 pixel black casing (#000000).</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:WaterwayLink</se:FeatureTypeName>
        <se:Rule>
          <se:LineSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:centerlineGeometry</ogc:PropertyName>
            </se:Geometry>
            <se:Stroke/>
          </se:LineSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.13. Styles for the layer TN.WaterTransportNetwork.FairwayArea

Style Name TN.WaterTransportNetwork.FairwayArea.Default

Default Style

yes

Style Title

Fairway Area default style

Style Abstract

The geometry is rendered using a Blue (#4169E1) fill and a solid black (#000000) outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.WaterTransportNetwork.FairwayArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.WaterTransportNetwork.FairwayArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Fairway Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a Blue (#4169E1) fill and a solid black (#000000) outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:FairwayArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.14. Styles for the layer TN.WaterTransportNetwork.PortArea

Style Name TN.WaterTransportNetwork.PortArea.Default

Default Style

yes

Style Title

Port Area default style

Style Abstract

The geometry is rendered using a Grey (#696969) fill and a solid black (#000000) outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.WaterTransportNetwork.PortArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.WaterTransportNetwork.PortArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Port Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a Grey (#696969) fill and a solid black (#000000) outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:PortArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.15. Styles for the layer TN.AirTransportNetwork.AirLink

Style Name TN.AirTransportNetwork.AirLink.Default

Default Style

yes

Style Title

Air Link default style

Style Abstract

The geometry is rendered as a solid Maroon line with a stroke width of 3 pixel (#800000). Ends are rounded and have a 2 pixel black casing (#000000).

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.AirTransportNetwork.AirLink</se:Name>
    <sld:UserStyle>
      <se:Name> TN.AirTransportNetwork.AirLink.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>AirAir Link Default Style</se:Title>
          <se:Abstract> The geometry is rendered as a solid Maroon line with a stroke width of 3 pixel (#800000).  Ends are rounded and have a 2 pixel black casing (#000000).</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:AirLink</se:FeatureTypeName>
        <se:Rule>
          <se:LineSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:centerlineGeometry</ogc:PropertyName>
            </se:Geometry>
            <se:Stroke/>
          </se:LineSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.16. Styles for the layer TN.AirTransportNetwork.AerodromeArea

Style Name TN.AirTransportNetwork.AerodromeArea.Default

Default Style

yes

Style Title

Aerodrome Area default style

Style Abstract

The geometry is rendered using a 50% Blue (#0000CD) fill and a solid Blue (#0000CD)outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.AirTransportNetwork.AerodromeArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.AirTransportNetwork.AerodromeArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Aerodrome Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a 50% Blue (#0000CD) fill and a solid Blue (#0000CD)outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:AerodromeArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.17. Styles for the layer TN.AirTransportNetwork.RunwayArea

Style Name TN.AirTransportNetwork.RunwayArea.Default

Default Style

yes

Style Title

Runway Area default style

Style Abstract

The geometry is rendered using a White (#FFFFFF) fill and a solid Blue (#0000CD)outline with a stroke width of 2 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.AirTransportNetwork.RunwayArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.AirTransportNetwork.RunwayArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Runway Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a White (#FFFFFF) fill and a solid Blue (#0000CD)outline with a stroke width of 2 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:RunwayArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.18. Styles for the layer TN.AirTransportNetwork.AirSpaceArea

Style Name TN.AirTransportNetwork.AirSpaceArea.Default

Default Style

yes

Style Title

Air Space Area Default Style

Style Abstract

The geometry is rendered using a 25% Megenta (#8B008B) fill and a solid Megenta (#8B008B) outline with a stroke width of 2 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.AirTransportNetwork.AirspaceArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.AirTransportNetwork.AirSpaceArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Airspace Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a 25% Megenta (#8B008B) fill and a solid Megenta (#8B008B) outline with a stroke width of 2 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:AirspaceArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.19. Styles for the layer TN.AirTransportNetwork.ApronArea

Style Name TN.AirTransportNetwork.ApronArea.Default

Default Style

yes

Style Title

Apron Area Default Style

Style Abstract

The geometry is rendered using a 50% grey (#808080) fill and a solid black outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.AirTransportNetwork.ApronArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.AirTransportNetwork.ApronArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Apron Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a 50% grey (#808080) fill and a solid black outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:ApronArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.20. Styles for the layer TN.AirTransportNetwork.TaxiwayArea

Style Name TN.AirTransportNetwork.TaxiwayArea.Default

Default Style

yes

Style Title

Taxiway Area Default Style

Style Abstract

The geometry is rendered using a Blue (#B0E0E6) fill and a solid black outline with a stroke width of 1 pixel.

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.AirTransportNetwork.TaxiwayArea</se:Name>
    <sld:UserStyle>
      <se:Name> TN.AirTransportNetwork.TaxiwayArea.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>Taxiway Area Default Style</se:Title>
          <se:Abstract>The geometry is rendered using a Blue (#B0E0E6) fill and a solid black outline with a stroke width of 1 pixel.</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>TN:TaxiwayArea</se:FeatureTypeName>
        <se:Rule>
          <se:PolygonSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:geometry</ogc:PropertyName>
            </se:Geometry>
            <se:Fill/>
            <se:Stroke/>
          </se:PolygonSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

11.2.21. Styles for the layer TN.CableTransportNetwork.CablewayLink

Style Name TN.CableTransportNetwork.CablewayLink.Default

Default Style

yes

Style Title

Cable Transport Network default style

Style Abstract

The geometry is rendered as a solid Black line with a stroke width of 3 pixel (#B10787). Ends are rounded and have a 2 pixel black casing (#000000).

Symbology

 
<sld:NamedLayer>
    <se:Name>TN.CableTransportNetwork.CablewayLink</se:Name>
    <sld:UserStyle>
      <se:Name> TN.CableTransportNetwork.CablewayLink.Default</se:Name>
      <sld:IsDefault>1</sld:IsDefault>
      <se:FeatureTypeStyle version="1.1.0">
        <se:Description>
          <se:Title>CableTransportNetworkDefaultStyle</se:Title>
          <se:Abstract> The geometry is rendered as a solid Black line with a stroke width of 3 pixel (#B10787).  Ends are rounded and have a 2 pixel black casing (#000000).</se:Abstract>
        </se:Description>
        <se:FeatureTypeName>CablewayLink</se:FeatureTypeName>
        <se:Rule>
          <se:LineSymbolizer>
            <se:Geometry>
              <ogc:PropertyName>Network:centerlineGeometry</ogc:PropertyName>
            </se:Geometry>
            <se:Stroke/>
          </se:LineSymbolizer>
        </se:Rule>
      </se:FeatureTypeStyle>
    </sld:UserStyle>
  </sld:NamedLayer>

Minimum & maximum scales

None

Bibliography

[DS-D2.3] INSPIRE DS-D2.3, Definition of Annex Themes and Scope, v3.0, http://inspire.ec.europa.eu/reports/ImplementingRules/DataSpecifications/D2.3_Definition_of_Annex_Themes_and_scope_v3.0.pdf

[DS-D2.5] INSPIRE DS-D2.5, Generic Conceptual Model, v3.4rc2, 3http://inspire.ec.europa.eu/documents/Data_Specifications/D2.5_v3.4rc3.pdf

[DS-D2.6] INSPIRE DS-D2.6, Methodology for the development of data specifications, v3.0, http://inspire.ec.europa.eu/reports/ImplementingRules/DataSpecifications/D2.6_v3.0.pdf

[DS-D2.7] INSPIRE DS-D2.7, Guidelines for the encoding of spatial data, v3.3rc3, http://inspire.ec.europa.eu/documents/Data_Specifications/D2.7_v3.3rc3.pdf

[ISO 19101] EN ISO 19101:2005 Geographic information – Reference model (ISO 19101:2002)

[ISO 19103] ISO/TS 19103:2005, Geographic information – Conceptual schema language

[ISO 19107] EN ISO 19107:2005, Geographic information – Spatial schema (ISO 19107:2003)

[ISO 19108] EN ISO 19108:2005 Geographic information - Temporal schema (ISO 19108:2002)

[ISO 19111] EN ISO 19111:2007 Geographic information - Spatial referencing by coordinates (ISO 19111:2007)

[ISO 19115] EN ISO 19115:2005, Geographic information – Metadata (ISO 19115:2003)

[ISO 19118] EN ISO 19118:2006, Geographic information – Encoding (ISO 19118:2005)

[ISO 19135] EN ISO 19135:2007 Geographic information – Procedures for item registration (ISO 19135:2005)

[ISO 19139] ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation

[ISO 19157] ISO/DIS 19157, Geographic information – Data quality

[OGC 06-103r3] Implementation Specification for Geographic Information - Simple feature access – Part 1: Common Architecture v1.2.0

1n1005 - DBPrior10k
Intesa GIS, Italy
http://www.centrointerregionale-gis.it/script/scrp.asp?Pagecode=002

1n1007_1 - Specifications for producing general Topographic Data Base - Layers, Themes, Classes
Intesa GIS, Italy
http://www.centrointerregionale-gis.it/script/scrp.asp?Pagecode=002

1n1007_3 - "Specifiche per la realizzazione dei Database Topografici di interesse generale, Specifiche di contenuto: La presentazione cartografica".
Intesa GIS, Italy
http://www.centrointerregionale-gis.it/script/scrp.asp?Pagecode=002

Additional Military Layers 
NATO 
http://defence.ukho.gov.uk/content/addAttachments/AML/Product%20Specs/AML_PS_Corrigenda_1.pdf

Aeronautical Information Exchange
Federal Aviation Authority
http://www.faa.gov/AIXM/

Airspace: Email exchange with the Civil Aviation Authority for the UK
TWG TN Records [not publically available]

AIXM3.3 Conceptual Model
http://www.aixm.aero

AIXM5.0 Conceptual Model
http://www.aixm.aero

ATKIS Feature catalogue – chapter D3 : DLM250
Working Committee of the State Survey Offices of the Federal Republic of Germany
AdV, Germany
http://www.geodatenzentrum.de/geodaten/gdz_rahmen.gdz_div?gdz_spr=eng&gdz_akt_zeile=2&gdz_anz_zeile=3&gdz_user_id=0

ATKIS Feature catalogue – chapter D4 : DLM1000
Working Committee of the State Survey Offices of the Federal Republic of Germany
AdV, Germany
http://www.geodatenzentrum.de/geodaten/gdz_rahmen.gdz_div?gdz_spr=eng&gdz_akt_zeile=2&gdz_anz_zeile=3&gdz_user_id=0

BD Carto Descriptif technique
IGN France
www.ign.france

BD TOPO v2.0 - Content description - IGN France (May 2008)
www.ign.france

BD Topo version 3.1 descriptif technique
IGN France
www.ign.france

BTN25 Concise Technical Specification
National Geographic Institute (Spain)
www.ign.es

Candidate OpenGIS CityGML Implementation Specification
Open Geospatial Consortium, Inc.
www.opengeospatial.org

CEMT Resolution No. 92/2 on New Classification of Inland Waterways http://www.internationaltransportforum.org/europe/acquis/wat19922e.pdf

COUNCIL DIRECTIVE of 27 June 1985 on the assessment of the effects of certain public and private projects on the environment (85/337/EEC) (OJ L 175, 5.7.1985, p. 40)
http://ec.europa.eu/environment/eia/full-legal-text/85337.htm

Data Base Topografico alle grandi scale (1:1.000 - 1:2.000 - 1:5.000)
Regione Emilia-Romagna, Italy

DECISION No 884/2004/EC OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 29 April 2004 amending Decision No 1692/96/EC on Community guidelines for the development of the trans-European transport network
http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2004:167:0001:0038:EN:PDF

Document de doctrine sur la notion de référentiel
CNIG, France
www.cnig.gouv.fr

Draft EuroSpec Feature Catalogue for topographic data – Transport
EuroGeographics
www.eurogeographics.org

[DS-D2.3] INSPIRE DS-D2.3, Definition of Annex Themes and Scope, v3.0, https://knowledge-base.inspire.ec.europa.eu/publications/definition-annex-themes-and-scope-d-23-version-30_en

[DS-D2.5] INSPIRE DS-D2.5, Generic Conceptual Model, v3.4rc2, https://knowledge-base.inspire.ec.europa.eu/publications/inspire-generic-conceptual-model_en

[DS-D2.6] INSPIRE DS-D2.6, Methodology for the development of data specifications, v3.0, https://knowledge-base.inspire.ec.europa.eu/publications/methodology-development-data-specifications-baseline-version-d-26-version-30_en

[DS-D2.7] INSPIRE DS-D2.7, Guidelines for the encoding of spatial data, v3.3rc2, https://knowledge-base.inspire.ec.europa.eu/publications/guidelines-encoding-spatial-data_en

[DS-D2.8.I.3] INSPIRE DS-D2.8.I.3, INSPIRE Data Specifiications on Geographical Names – Guidelines, v3.0

EDC-11031 EuroRegioMap EuroRegionalMap: Incremental Development of a Pan-European Database at Medium Scale
EuroGeographics
ftp://ftp.ign.fr/ign/INSPIRE/ERM_Updating_report.doc

EGM Specifications
EuroGeographics,
www.eurogeographics.org

ERM Data Model
EuroGeographics
www.eurogeographics.org

ERM Specifications and data catalogue
http://www.ngi.be/

ERM Technical Guide
EuroGeographics
www.eurogeographics.org

Especificaciones de la Base Topográfica Armonizada 1:5000 (BTA) v1.0
National Geographic High Council
Cartociudad specifications 
Instituto Geográfico Nacional (Spain) 
www.ign.es

Especificaciones técnicas de la Base topográfica de Catalunya 1:25000 (BT25M) v1.0 
Institut Cartogràfic de Catalunya, Spain
http://www.icc.es/web/content/ca/index.html

EUROCONTROL:
Traffic flow and management
www.eurocontrol.int

European Commission STAFF WORKING DOCUMENT Accompanying document to the COMMUNICATION FROM THE COMMISSION Trans-European Networks : Toward and integrated approach \{COM(2007) 135 final} Brussels, 21.3.2007 SEC(2007) 374
http://europa.eu/legislation_summaries/transport/intermodality_transeuropean_networks/l24481_en.htm

European Commission: DRAFT Guidelines – INSPIRE Data Specification Addresses
http://inspire.jrc.ec.europa.eu/implementingRulesDocs_ds.cfm

European Commission: DRAFT Guidelines – INSPIRE Data Specification Hydrography
http://inspire.jrc.ec.europa.eu/implementingRulesDocs_ds.cfm

EuroRegionalMap Specification and Data Catalogue
IGN Belgium, other contributors: BKG Germany, IGN France
http://www.ngi.be/

EuroRegionalMap: Incremental Development of a Pan-European Database at Medium Scale
IGN France
www.ign.fr

EuroRoadS Documents (Final Specification of Road Network Exchange Model, Final Specification of Road Network Exchange Format, Final terminology Catalogue, Final Specifications of Core European Road Data,Metadata Catalogue & Final Specification of Road Network Information Model)
www.euroroads.org

Evaluation des produits publics d’information géographique en regard des critères definissant un référentiel
CNIG, France
www.cnig.gouv.fr

Geographic Data Files
http://www.ertico.com/en/links/links/gdf-geographic_data_files.htm

GiMoDig, Global Schema specification
GiMoDig consortium
http://gimodig.fgi.fi/

Highway Agency (England and Wales) EnvIS methodology (TWG TN Reference Material on Circa)
www.highways.gov.uk

IHO Hydrographic Registry
http://www.iho-wms.net:8080/iho_registry/home.php

Implementation report on the TEN-T guidelines
TINA Vienna - Transport strategies Gmbh, Austria
http://www.tinavienna.at/index.php?l_id=en

INSPIRE Feature Concept Dictionary, INSPIRE Registry, European Commission

[ISO 19101] EN ISO 19101:2005 Geographic information – Reference model (ISO 19101:2002)

[ISO 19103] ISO/TS 19103:2005, Geographic information – Conceptual schema language

[ISO 19107] EN ISO 19107:2005, Geographic information – Spatial schema (ISO 19107:2003)

[ISO 19111] EN ISO 19111:2007 Geographic information - Spatial referencing by coordinates (ISO 19111:2007)

[ISO 19115] EN ISO 19115:2005, Geographic information – Metadata (ISO 19115:2003)

[ISO 19118] EN ISO 19118:2006, Geographic information – Encoding (ISO 19118:2005)

[ISO 19135] EN ISO 19135:2007 Geographic information – Procedures for item registration (ISO 19135:2005)

[ISO 19139] ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation

[ISO 19157] ISO/DIS 19157, Geographic information – Data quality

ISO/AWI 19148 Geographic information — Location based services — Linear referencing system

ITS Vienna Region - platform to integrate graphs 
„ITS Vienna Region im Verkehrsverbund Ostregion

National Land and Property Gazetteer 
Local Government Information House (LGIH)
www.idea.gov.uk/idk/core/page.do?pageId=8021533

National Street Gazetteer 

Local Government Information House (LGIH)

www.idea.gov.uk/idk/core/page.do?pageId=8021533

NEN3610 - Basic scheme for geo-information

NEN, Netherlands

http://www2.nen.nl/nen/servlet/dispatcher.Dispatcher?id=253335

Network Rail – Corporate Model (graphic),
Not publically available, Network Rail, UK
www.networkrail.co.uk

Network statement - Common structure and implementation guide
Rail Net Europe
www.railneteurope.com

Norwegian feature catalogue and standards,
Digital Norway
http://www.statkart.no/Norge_digitalt/Engelsk/About_Norway_Digital/

Nuova base dati cartografica del Reticolo Stradale
Regione Emilia-Romagna, Italy

Objekt katalog für das Straßen- und Verkehrswesen
Bundesanstalt für Strassenwesen, Germany

OGC 06-103r3 Implementation Specification for Geographic Information - Simple feature access – Part 1: Common Architecture v1.2.0

OJEC L228, 09/09/1996 Community Guidelines for the development of the trans-European transport network. As referenced in Annex I of the INSPIRE Directive:
http://europa.eu/legislation_summaries/regional_policy/management/transeuropean_networks/l24094_en.htm

OS MasterMap Integrated Transport Network Layer - user guide
Ordnance Survey, UK
http://www.ordnancesurvey.co.uk/oswebsite/products/osmastermap/userguides/docs/OSMM_ITN_userguide_v1.0.pdf

OS MasterMap Topography Layer - user guide and technical specification
Ordnance Survey, UK
http://www.ordnancesurvey.co.uk/oswebsite/products/osmastermap/userguides/docs/OSMMTopoLayerUserGuide.pdf

OS MasterMap® Integrated Transport Network™ - GML Data Examples
Ordnance Survey, UK
http://www.ordnancesurvey.co.uk

Productspecification TOP10NL 
Kadaster,
Geonovum, Netherlands
www.geonovum.nl

Productspecification TOP10NL - UML schema
Kadaster,
Geonovum, Netherlands
www.geonovum.nl

Reference data model for public transport
CEN TC278
www2.nen.nl/nen/servlet/dispatcher.Dispatcher?id=204514

Reference Model and the Objective and Scope of River Information Services
COMPRIS
http://www.euro-compris.org/index2.asp

Report on Global Schema for GiMoDig
GiMoDig consortium
http://gimodig.fgi.fi/

Report on Reference Data Sets and Feature types in Europe.
EuroGeographics
www.eurogeographics.org

Route 120 descriptif de contenu
IGN France
ftp://ftp.ign.fr/ign/INSPIRE/DC_ROUTE120.pdf

Route 500 descriptif technique
IGN France
www.ign.fr

S-100 (IHO Hydrographic Geospatial Standard for Marine Data and Information)
(only draft version available – not yet a standard)
http://www.iho-ohi.net/english/home/

S-32 (IHO International Hydrographic Dictionary) - http://www.iho.shom.fr/Dhydro/Html/site_edition/disclaimer.html

S-57 Electronic Navigational Chart Product Specification
IHO
http://www.iho-ohi.net/english/home/

Single European Sky
http://ec.europa.eu/transport/air_portal/sesame/index_en.htm

SIS/TK 320 Road and railway information
Stanli, Sweden
www.stanli.se

Skyguide Glossary, Switzerland
http://www.skyguide.ch/en/Tools/Glossary/glossary.xml

Specification Georoute
IGN France
www.ign.fr

Spécifications BD Uni v0.1
IGN France
www.ign.fr

Spécifications des données de réference et Avis du CNIG
CNIG, France
www.cnig.gouv.fr

Specifikation for fælles objekt typer (Common object types specification)
National Survey and Cadastre, Denmark
www.kms.dk

SS 63 70 04-1 (draft) Geographic information – Road and railway network – Part 1: Concept model and application schema
SIS, Swedish Standards Institute 
www.stanli.se

SS 63 70 04-1:2006 Geographic information – Road and Railway networks - Part 1: Concept model and application schema 
SIS, Swedish Standards Institute 
www.stanli.se

Annex A: Abstract Test Suite - (normative)

Disclaimer

While this Annex refers to the Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services, it does not replace the legal act or any part of it.

The objective of the Abstract Test Suite (ATS) included in this Annex is to help the conformance testing process. It includes a set of tests to be applied on a data set to evaluate whether it fulfils the requirements included in this data specification and the corresponding parts of Commission Regulation No 1089/2010 (implementing rule as regards interoperability of spatial datasets and services, further referred to as ISDSS Regulation). This is to help data providers in declaring the conformity of a data set to the "degree of conformity, with implementing rules adopted under Article 7(1) of Directive 2007/2/EC", which is required to be provided in the data set metadata according to Commission Regulation (EC) No 2008/1205 (the Metadata Regulation).

Part 1 of this ATS includes tests that provide input for assessing conformity with the ISDSS regulation. In order to make visible which requirements are addressed by a specific test, references to the corresponding articles of the legal act are given. The way how the cited requirements apply to tn specification is described under the testing method.

In addition to the requirements included in ISDSS Regulation this Technical guideline contains TG requirements too. TG requirements are technical provisions that need to be fulfilled in order to be conformant with the corresponding IR requirement when the specific technical implementation proposed in this document is used. Such requirements relate for example to the default encoding described in section 9. Part 2 of the ATS presents tests necessary for assessing the conformity with TG requirements.

NOTE Conformance of a data set with the TG requirement(s) included in this ATS implies conformance with the corresponding IR requirement(s).

The ATS is applicable to the data sets that have been transformed to be made available through INSPIRE download services (i.e. the data returned as a response to the mandatory "Get Spatial Dataset" operation) rather than the original "source" data sets.

The requirements to be tested are grouped in several conformance classes. Each of these classes covers a specific aspect: one conformance class contains tests reflecting the requirements on the application schema, another on the reference systems, etc. Each conformance class is identified by a URI (uniform resource identifier) according to the following pattern:

http://inspire.ec.europa.eu/conformance-class/ir/tn/<conformance class identifier>

EXAMPLE 1 The URI http://inspire.ec.europa.eu/conformance-class/ir/ef/rs identifies the Reference Systems ISDSS conformance class of the Environmental Monitoring Facilities (EF) data theme.

The results of the tests should be published referring to the relevant conformance class (using its URI).

When an INSPIRE data specification contains more than one application schema, the requirements tested in a conformance class may differ depending on the application schema used as a target for the transformation of the data set. This will always be the case for the application schema conformance class. However, also other conformance classes could have different requirements for different application schemas. In such cases, a separate conformance class is defined for each application schema, and they are distinguished by specific URIs according to the following pattern:

http://inspire.ec.europa.eu/conformance-class/ir/tn/<conformance class identifier>/<application schema namespace prefix>

EXAMPLE 2 The URI http://inspire.ec.europa.eu/conformance-class/ir/el/as/el-vec identifies the conformity with the application schema (as) conformance class for the Elevation Vector Elements (el-vec) application schema.

An overview of the conformance classes and the associated tests is given in the table below.

Table 6. Overview of the tests within this Abstract Test Suite.

Annex A (normative) Abstract Test Suite

A.1 Application Schema Conformance Class

A.1.1 Schema element denomination test

A.1.2 Value type test

A.1.3 Value test

A.1.4 Attributes/associations completeness test

A.1.5 Abstract spatial object test

A.1.6 Constraints test

A.1.7 Geometry representation test

A.1.8 Object references modelling test

A.1.9 Centrelines test

A.1.10 Network Connectivity test

A.2 Reference Systems Conformance Class

A.2.1 Datum test

A.2.2 Coordinate reference system test

A.2.3 Grid test

A.2.4 View service coordinate reference system test

A.2.5 Temporal reference system test

A.2.6 Units of measurements test

A.3 Data Consistency Conformance Class

A.3.1 Unique identifier persistency test

A.3.2 Version consistency test

A.3.3 Life cycle time sequence test

A.3.4 Validity time sequence test

A.3.5 Update frequency test

A.3.6 Spatial consistency test

A.4 Metadata IR Conformance Class

A.4.1 Metadata for interoperability test

A.5 Information Accessibility Conformance Class

A.5.1 Code list publication test

A.5.2 CRS publication test

A.5.3 CRS identification test

A.5.4 Grid identification test

A.6 Data Delivery Conformance Class

A.6.1 Encoding compliance test

A.7 Portrayal Conformance Class

A.7.1 Layer designation test

A.8 Technical Guideline Conformance Class

A.8.1 Multiplicity test

A.8.2 CRS http URI test

A.8.3 Metadata encoding schema validation test

A.8.4 Metadata occurrence test

A.8.5 Metadata consistency test

A.8.6 Encoding schema validation test

A.8.7 Coverage multipart representation test

A.8.8 Coverage domain consistency test

A.8.9 Style test

In order to be conformant to a conformance class, a data set has to pass all tests defined for that conformance class.

In order to be conformant with the ISDSS regulation the inspected data set needs to be conformant to all conformance classes in Part 1. The conformance class for overall conformity with the ISDSS regulation is identified by the URI http://inspire.ec.europa.eu/conformance-class/ir/tn/.

In order to be conformant with the Technical Guidelines, the dataset under inspection needs to be conformant to all conformance classes included both in Part 1 and 2. Chapter 8 describes in detail how to publish the result of testing regarding overall conformity and conformity with the conformance classes as metadata. The conformance class for overall conformity with the Technical Guidelines is identified by the URI http://inspire.ec.europa.eu/conformance-class/tg/tn/3.2.

It should be noted that data providers are not obliged to integrate / decompose the original structure of the source data sets when they deliver them for INSPIRE. It means that a conformant dataset can contain less or more spatial object / data types than specified in the ISDSS Regulation.

A dataset that contains less spatial object and/or data types can be regarded conformant when the corresponding types of the source datasets after the necessary transformations fulfil the requirements set out in the ISDSS Regulation.

A dataset that contain more spatial object and/or data types may be regarded as conformant when

  • all the spatial object / data types that have corresponding types in the source dataset after the necessary transformations fulfil the requirements set out in the ISDSS Regulation and

  • all additional elements of the source model (spatial object types, data types, attributes, constraints and code lists together with their values) do not conflict with any rule defined in the interoperability target specifications defined for any theme within INSPIRE.

Opens issue 2: Even though the last condition can be derived from Art. 8(4) of the Directive, the ISDSS Regulation does not contain requirements concerning the above issue. Therefore, no specific tests have been included in this abstract suite for testing conformity of extended application schemas. Annex F of the Generic Conceptual Model (D2.5) provides an example how to extend INSPIRE application schemas in a compliant way.

The ATS contains a detailed list of abstract tests. It should be noted that some tests in the Application schema conformance class can be automated by utilising xml schema validation tools. It should be noted that failing such validation test does not necessary reflect non-compliance to the application schema; it may be the results of erroneous encoding.

Each test in this suite follows the same structure:

  • Requirement: citation from the legal texts (ISDSS requirements) or the Technical Guidelines (TG requirements);

  • Purpose: definition of the scope of the test;

  • Reference: link to any material that may be useful during the test;

  • Test method: description of the testing procedure.

According to ISO 19105:2000 all tests in this ATS are basic tests. Therefore, this statement is not repeated each time.

Part 1 - (normative)

Conformity with Commission Regulation No 1089/2010

A.1. Application Schema Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-a

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-c

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-ra

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-ro

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-w

A.1.1. Schema element denomination test

  1. Purpose: Verification whether each element of the dataset under inspection carries a name specified in the target application schema(s).

  2. Reference: Art. 3 and Art.4 of Commission Regulation No 1089/2010

  3. Test Method: Examine whether the corresponding elements of the source schema (spatial object types, data types, attributes, association roles and code lists) are mapped to the target schema with the correct designation of mnemonic names.

NOTE Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

A.1.2. Value type test

  1. Purpose: Verification whether all attributes or association roles use the corresponding value types specified in the application schema(s).

  2. Reference: Art. 3, Art.4, Art.6(1), Art.6(4), Art.6(5) and Art.9(1)of Commission Regulation No 1089/2010.

  3. Test Method: Examine whether the value type of each provided attribute or association role adheres to the corresponding value type specified in the target specification.

NOTE 1 This test comprises testing the value types of INSPIRE identifiers, the value types of attributes and association roles that should be taken from code lists, and the coverage domains.

NOTE 2 Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

A.1.3. Value test

  1. Purpose: Verify whether all attributes or association roles whose value type is a code list take the values set out therein.

  2. Reference: Art.4 (3) of Commission Regulation No 1089/2010.

  3. Test Method: When an attribute / association role has a code list as its type, compare the values of each instance with those provided in the application schema. To pass this tests any instance of an attribute / association role

    • shall take only values explicitly specified in the code list when the code list’s extensibility is "none".

    • shall take only a value explicitly specified in the code list or shall take a value that is narrower (i.e. more specific) than those explicitly specified in the application schema when the code list’s extensibility is "narrower".

NOTE 1 This test is not applicable to code lists with extensibility "open" or "any".

NOTE 2 When a data provider only uses code lists with narrower (more specific values) this test can be fully performed based on internal information.

A.1.4. Attributes/associations completeness test

  1. Purpose: Verification whether each instance of spatial object type and data types include all attributes and association roles as defined in the target application schema.

  2. Reference: Art. 3, Art.4(1), Art.4(2), and Art.5(2) of Commission Regulation No 1089/2010.

  3. Test Method: Examine whether all attributes and association roles defined for a spatial object type or data type are present for each instance in the dataset.

NOTE 1 Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

NOTE 2 For all properties defined for a spatial object, a value has to be provided if it exists in or applies to the real world entity – either the corresponding value (if available in the data set maintained by the data provider) or the value of void. If the characteristic described by the attribute or association role does not exist in or apply to the real world entity, the attribute or association role does not need to be present in the data set.

A.1.5. Abstract spatial object test

  1. Purpose: Verification whether the dataset does NOT contain abstract spatial object / data types defined in the target application schema(s).

  2. Reference: Art.5(3) of Commission Regulation No 1089/2010

  3. Test Method: Examine that there are NO instances of abstract spatial object / data types in the dataset provided.

NOTE Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

A.1.6. Constraints test

  1. Purpose: Verification whether the instances of spatial object and/or data types provided in the dataset adhere to the constraints specified in the target application schema(s).

  2. Reference: Art. 3, Art.4(1), and Art.4(2) of Commission Regulation No 1089/2010.

  3. Test Method: Examine all instances of data for the constraints specified for the corresponding spatial object / data type. Each instance shall adhere to all constraints specified in the target application schema(s).

NOTE Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

A.1.7. Geometry representation test

  1. Purpose:

Verification whether the value domain of spatial properties is restricted as specified in the Commission Regulation No 1089/2010.

Verification that Transport link ends are connected wherever an intersection exists between the real world phenomena they represent. When it is not possible to pass from one element to another verify that there is no connection created.

Verify that if in a Transport Networks is a data set which contains nodes, these nodes are only presented where Transport Links connect or end.

  1. Reference: Art.12(1), Annex II Section 7 of Commission Regulation No 1089/2010

  2. Test Method:

Check whether all spatial properties only use 0, 1 and 2-dimensional geometric objects that exist in the right 2-, 3- or 4-dimensional coordinate space, and where all curve interpolations respect the rules specified in the reference documents.

Check if Transport link ends are connected wherever an intersection exists between the real world phenomena they represent. Check that there is no connection when it is not possible to pass from one element to another.

Check that nodes presented in Transport Networks are only present where Transport Links connect or end.

NOTE Further technical information is in OGC Simple Feature spatial schema v1.2.1 [06-103r4].

A.1.8. Object references modelling test

  1. Purpose:

    Verification that if linear referencing is used in Transport Networks data, the position of referenced properties on links and link sequences are expressed as distances measured along the supplied geometry of the underlying link object(s).

    Verification that an inter-modal connection always referencing two elements which belong to different networks.

    Verification that the Water transport networks re-uses, where it exists and is practicable, the water network centreline geometry of the Hydrography theme.

  2. Reference: Annex II Section 7.9 of Commission Regulation No 1089/2010

  3. Test Method:

    Check, if linear referencing is used, that the position of referenced properties on links and link sequences are expressed as distances measured along the supplied geometry of the underlying link object(s).

    Check that an inter-modal connection always referencing two elements which belong to different networks.

    Check that the Water transport networks re-uses, where it exists and is practicable, the water network centreline geometry of the Hydrography theme. Therefore, object referencing shall be used to link the water transport course with the existing water network geometry in the Hydrography theme.

A.1.9. Centrelines test

  1. Purpose: Verification that the centrelines of Road and Rail objects are falling within the extent of the physical real world object that they represent if the Link is indicated as not being 'fictitious'.

  2. Reference: Annex II Section 7.9 of Commission Regulation No 1089/2010

  3. Test Method: Check whether the centrelines of Road and Rail objects are falling within the extent of the physical real world object that they represent if the Link is indicated as not being 'fictitious'.

A.1.10. Network Connectivity test

  1. Purpose:

    Verification that wherever a connection exists in a transport network, all connected link ends and the optional node that take part in this connection are positioned at a distance of less than the connectivity tolerance from each other.

    Verification that link ends and nodes that are not connected are always separated by a distance that is greater than the connectivity tolerance.

    Verification that in data sets where both transport links and nodes are presented, the relative position of nodes and link ends in relation to the specified connectivity tolerance corresponds to the associations that exist between them in the data set.

  2. Reference: Annex II Section 7.9 of Commission Regulation No 1089/2010

  3. Test Method:

    Check that wherever a connection exists in a transport network, all connected link ends and the optional node that take part in this connection are positioned at a distance of less than the connectivity tolerance from each other.

    Check that link ends and nodes that are not connected are always separated by a distance that is greater than the connectivity tolerance.

    Check if in data sets where both transport links and nodes are presented, the relative position of nodes and link ends in relation to the specified connectivity tolerance corresponds to the associations that exist between them in the data set.

A.2. Reference Systems Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/tn/rs

A.2.1. Datum test

  1. Purpose: Verify whether each instance of a spatial object type is given with reference to one of the (geodetic) datums specified in the target specification.

  2. Reference: Annex II Section 1.2 of Commission Regulation No 1089/2010

  3. Test Method: Check whether each instance of a spatial object type specified in the application schema(s) in section 5 has been expressed using:

    • the European Terrestrial Reference System 1989 (ETRS89) within its geographical scope; or

    • the International Terrestrial Reference System (ITRS) for areas beyond the ETRS89 geographical scope; or

    • other geodetic coordinate reference systems compliant with the ITRS. Compliant with the ITRS means that the system definition is based on the definition of ITRS and there is a well-established and described relationship between both systems, according to the EN ISO 19111.

NOTE Further technical information is given in Section 6 of this document.

A.2.2. Coordinate reference system test

  1. Purpose: Verify whether the two- and three-dimensional coordinate reference systems are used as defined in section 6.

  2. Reference: Section 6 of Commission Regulation 1089/2010.

  3. Test Method: Inspect whether the horizontal and vertical components of coordinates one of the corresponding coordinate reference system has been:

    • Three-dimensional Cartesian coordinates based on a datum specified in 1.2 and using the parameters of the Geodetic Reference System 1980 (GRS80) ellipsoid.

    • Three-dimensional geodetic coordinates (latitude, longitude and ellipsoidal height) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.

    • Two-dimensional geodetic coordinates (latitude and longitude) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.

    • Plane coordinates using the ETRS89 Lambert Azimuthal Equal Area coordinate reference system.

    • Plane coordinates using the ETRS89 Lambert Conformal Conic coordinate reference system.

    • Plane coordinates using the ETRS89 Transverse Mercator coordinate reference system.

    • For the vertical component on land, the European Vertical Reference System (EVRS) shall be used to express gravity-related heights within its geographical scope. Other vertical reference systems related to the Earth gravity field shall be used to express gravity-related heights in areas that are outside the geographical scope of EVRS.

    • For the vertical component in marine areas where there is an appreciable tidal range (tidal waters), the Lowest Astronomical Tide (LAT) shall be used as the reference surface.

    • For the vertical component in marine areas without an appreciable tidal range, in open oceans and effectively in waters that are deeper than 200 meters, the Mean Sea Level (MSL) or a well-defined reference level close to the MSL shall be used as the reference surface."

    • For the vertical component in the free atmosphere, barometric pressure, converted to height using ISO 2533:1975 International Standard Atmosphere, or other linear or parametric reference systems shall be used. Where other parametric reference systems are used, these shall be described in an accessible reference using EN ISO 19111-2:2012.

NOTE Further technical information is given in Section 6 of this document.

A.2.3. Grid test

  1. Purpose: Verify that gridded data related are available using the grid compatible with one of the coordinate reference systems defined in Commission Regulation No 1089/2010

  2. Reference: Annex II Section 2.1 and 2.2 of Commission Regulation 1089/2010.

  3. Test Method: Check whether the dataset defined as a grid is compatible with one of the coordinate reference.

    • Grid_ETRS89_GRS80 based on two-dimensional geodetic coordinates using the parameters of the GRS80 ellipsoid

    • Grid_ETRS89_GRS80zn based on two-dimensional geodetic coordinates with zoning,

    • Plane coordinates using the Lambert Azimuthal Equal Area projection and the parameters of the GRS80 ellipsoid (ETRS89-LAEA)

    • Plane coordinates using the Lambert Conformal Conic projection and the parameters of the GRS80 ellipsoid (ETRS89-LCC)

    • Plane coordinates using the Transverse Mercator projection and the parameters of the GRS80 ellipsoid (ETRS89-TMzn)

NOTE Further technical information is given in Section 6 of this document.

A.2.4. View service coordinate reference system test

  1. Purpose: Verify whether the spatial data set is available in the two dimensional geodetic coordinate system for their display with the INSPIRE View Service.

  2. Reference: Annex II Section 1.4 of Commission Regulation 1089/2010

  3. Test Method: Check that each instance of a spatial object types specified in the application schema(s) in section 5 is available in the two-dimensional geodetic coordinate system

NOTE Further technical information is given in Section 6 of this document.

A.2.5. Temporal reference system test

  1. Purpose: Verify whether date and time values are given as specified in Commission Regulation No 1089/2010.

  2. Reference: Art.11(1) of Commission Regulation 1089/2010

  3. Test Method: Check whether:

    • the Gregorian calendar is used as a reference system for date values;

    • the Universal Time Coordinated (UTC) or the local time including the time zone as an offset from UTC are used as a reference system for time values.

NOTE Further technical information is given in Section 6 of this document.

A.2.6. Units of measurements test

  1. Purpose: Verify whether all measurements are expressed as specified in Commission Regulation No 1089/2010.

  2. Reference: Art.12(2) of Commission Regulation 1089/2010

  3. Test Method: Check whether all measurements are expressed in SI units or non-SI units accepted for use with the International System of Units.

NOTE 1 Further technical information is given in ISO 80000-1:2009.

NOTE 2 Degrees, minutes and seconds are non-SI units accepted for use with the International System of Units for expressing measurements of angles.

A.3. Data Consistency Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-a

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-c

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-ra

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-ro

http://inspire.ec.europa.eu/conformance-class/ir/tn/as/tn-w

A.3.1. Unique identifier persistency test

  1. Purpose: Verify whether the namespace and localId attributes of the external object identifier remain the same for different versions of a spatial object.

  2. Reference: Art. 9 of Commission Regulation 1089/2010.

  3. Test Method: Compare the namespace and localId attributes of the external object identifiers in the previous version(s) of the dataset with the namespace and localId attributes of the external object identifiers of current version for the same instances of spatial object / data types; To pass the test, neither the namespace, nor the localId shall be changed during the life-cycle of a spatial object.

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

NOTE 2 When using URI this test includes the verification whether no part of the construct has been changed during the life cycle of the instances of spatial object / data types.

NOTE 3 Further technical information is given in section 14.2 of the INSPIRE Generic Conceptual Model.

A.3.2. Version consistency test

  1. Purpose: Verify whether different versions of the same spatial object / data type instance belong to the same type.

  2. Reference: Art. 9 of Commission Regulation 1089/2010.

  3. Test Method: Compare the types of different versions for each instance of spatial object / data type

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

A.3.3. Life cycle time sequence test

  1. Purpose: Verification whether the value of the attribute beginLifespanVersion refers to an earlier moment of time than the value of the attribute endLifespanVersion for every spatial object / object type where this property is specified.

  2. Reference: Art.10(3) of Commission Regulation 1089/2010.

  3. Test Method: Compare the value of the attribute beginLifespanVersion with attribute endLifespanVersion. The test is passed when the beginLifespanVersion value is before endLifespanVersion value for each instance of all spatial object/data types for which this attribute has been defined.

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

A.3.4. Validity time sequence test

  1. Purpose: Verification whether the value of the attribute validFrom refers to an earlier moment of time than the value of the attribute validTo for every spatial object / object type where this property is specified.

  2. Reference: Art.12(3) of Commission Regulation 1089/2010.

  3. Test Method: Compare the value of the attribute validFrom with attribute validTo. The test is passed when the validFrom value is before validTo value for each instance of all spatial object/data types for which this attribute has been defined.

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

A.3.5. Update frequency test

  1. Purpose: Verify whether all the updates in the source dataset(s) have been transmitted to the dataset(s) which can be retrieved for the TN data theme using INSPIRE download services.

  2. Reference: Art.8 (2) of Commission Regulation 1089/2010.

  3. Test Method: Compare the values of beginning of life cycle information in the source and the target datasets for each instance of corresponding spatial object / object types. The test is passed when the difference between the corresponding values is less than 6 months.

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

A.3.6. Spatial consistency test

  1. Purpose:

    Verification whether the Transport Networks centreline representations and nodes are always located within the extent of the area representation of the same object.

    Verification whether the connectivity between transport networks across state borders and – where applicable – also across regional borders (and data sets) within Member States is made using the cross-border connectivity mechanisms provided by the NetworkConnection type.

  2. Reference: Annex II Section 8.7.1 of Commission Regulation No 1089/2010

  3. Test Method:

    Check that Transport Networks centreline representations and nodes are always located within the extent of the area representation of the same object.

    Check that NetworkConnection type is used for connectivity between transport networks within Member States.

A.4. Metadata IR Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/tn/md

A.4.1. Metadata for interoperability test

  1. Purpose: Verify whether the metadata for interoperability of spatial data sets and services described in 1089/2010 Commission Regulation have been created and published for each dataset related to the TN data theme.

  2. Reference: Art.13 of Commission Regulation 1089/2010

  3. Test Method: Inspect whether metadata describing the coordinate reference systems, encoding, topological consistency and spatial representation type have been created and published. If the spatial data set contains temporal information that does not refer to the default temporal reference system, inspect whether metadata describing the temporal reference system have been created and published. If an encoding is used that is not based on UTF-8, inspect whether metadata describing the character encoding have been created.

NOTE Further technical information is given in section 8 of this document.

A.5. Information Accessibility Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/tn/ia

A.5.1. Code list publication test

  1. Purpose: Verify whether all additional values used in the data sets for attributes, for which narrower values or any other value than specified in Commission Regulation 1089/2010 are allowed, are published in a register.

  2. Reference: Art.6(3) and Annex II Section 7.

  3. Test Method: For each additional value used in the data sets for code list-valued attributes, check whether it is published in a register.

NOTE Further technical information is given in section 5 of this document.

A.5.2. CRS publication test

  1. Purpose: Verify whether the identifiers and the parameters of coordinate reference system are published in common registers.

  2. Reference: Annex II Section 1.5

  3. Test Method: Check whether the identifier and the parameter of the CRS used for the dataset are included in a register. .

NOTE Further technical information is given in section 6 of this document.

A.5.3. CRS identification test

  1. Purpose: Verify whether identifiers for other coordinate reference systems than specified in Commission Regulation 1089/2010 have been created and their parameters have been described according to EN ISO 19111 and ISO 19127.

  2. Reference: Annex II Section 1.3.4

  3. Test Method: Check whether the register with the identifiers of the coordinate reference systems is accessible.

NOTE Further technical information is given in section 6 of this document.

A.5.4. Grid identification test

  1. Purpose: Verify whether identifiers for other geographic grid systems than specified in Commission Regulation 1089/2010 have been created and their definitions have been either described with the data or referenced.

  2. Reference: Annex II Section 2.1 and 2.2

  3. Test Method: Check whether the identifiers for grids have been created. Inspect the dataset and/or the metadata for inclusion of grid definition.

NOTE Further technical information is given in section 6 of this document.

A.6. Data Delivery Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/tn/de

A.6.1. Encoding compliance test

  1. Purpose: Verify whether the encoding used to deliver the dataset comply with EN ISO 19118.

  2. Reference: Art.7 (1) of Commission Regulation 1089/2010.

  3. Test Method: Follow the steps of the Abstract Test Suit provided in EN ISO 19118.

NOTE 1 Datasets using the default encoding specified in Section 9 fulfil this requirement.

NOTE 2 Further technical information is given in Section 9 of this document.

A.7. Portrayal Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/tn/po

A.7.1. Layer designation test

  1. Purpose: verify whether each spatial object type has been assigned to the layer designated according to Commission Regulation 1089/2010.

  2. Reference: Art. 14(1), Art14(2) and Annex II Section 7.10.

  3. Test Method: Check whether data is made available for the view network service using the specified layers respectively:

    • TN.CommonTransportElements.TransportNode

    • TN.CommonTransportElements.TransportLink

    • TN.CommonTransportElements.TransportArea

    • TN.RoadTransportNetwork.RoadLink

    • TN.RoadTransportNetwork.VehicleTrafficArea

    • TN.RoadTransportNetwork.RoadServiceArea

    • TN.RoadTransportNetwork.RoadArea

    • TN.RailTransportNetwork.RailwayLink

    • TN.RailTransportNetwork.RailwayStationArea

    • TN.RailTransportNetwork.RailwayYardArea

    • TN.RailTransportNetwork.RailwayArea

    • TN.WaterTransportNetwork.WaterwayLink

    • TN.WaterTransportNetwork.FairwayArea

    • TN.WaterTransportNetwork.PortArea

    • TN.AirTransportNetwork.AirLink

    • TN.AirTransportNetwork.AerodromeArea

    • TN.AirTransportNetwork.RunwayArea

    • TN.AirTransportNetwork.AirspaceArea

    • TN.AirTransportNetwork.ApronArea

    • TN.AirTransportNetwork.TaxiwayArea

    • TN.CableTransportNetwork.CablewayLink

NOTE Further technical information is given in section 11 of this document.

Part 2 - (informative)

Conformity with the technical guideline (TG) Requirements

A.8. Technical Guideline Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/tg/tn/as/tn/3.2

http://inspire.ec.europa.eu/conformance-class/tg/tn/as/tn-a/3.2

http://inspire.ec.europa.eu/conformance-class/tg/tn/as/tn-c/3.2

http://inspire.ec.europa.eu/conformance-class/tg/tn/as/tn-ra/3.2

http://inspire.ec.europa.eu/conformance-class/tg/tn/as/tn-ro/3.2

http://inspire.ec.europa.eu/conformance-class/tg/tn/as/tn-w/3.2

A.8.1. Multiplicity test

  1. Purpose: Verify whether each instance of an attribute or association role specified in the application schema(s) does not include fewer or more occurrences than specified in section 5.

  2. Reference: Feature catalogue and UML diagram of the application schema(s) in section 5 of this guideline.

  3. Test Method: Examine that the number of occurrences of each attribute and/or association role for each instance of a spatial object type or data type provided in the dataset corresponds to the number of occurrences of the attribute / association role that is specified in the application schema(s) in section 5.

A.8.2. CRS http URI test

  1. Purpose: Verify whether the coordinate reference system used to deliver data for INSPIRE network services has been identified by URIs according to the EPSG register.

  2. Reference: Section 6 of this technical guideline

  3. Test Method: Compare the URI of the dataset with the URIs in the table.

NOTE 1 Passing this test implies the fulfilment of test A6.2

NOTE 2 Further reference please see http://www.epsg.org/geodetic.html

A.8.3. Metadata encoding schema validation test

  1. Purpose: Verify whether the metadata follows an XML schema specified in ISO/TS 19139.

  2. Reference: Section 8 of this technical guideline, ISO/TS 19139

  3. Test Method: Inspect whether provided XML schema is conformant to the encoding specified in ISO 19139 for each metadata instance.

NOTE 1 Section 2.1.2 of the Metadata Technical Guidelines discusses the different ISO 19139 XML schemas that are currently available.

A.8.4. Metadata occurrence test

  1. Purpose: Verify whether the occurrence of each metadata element corresponds to those specified in section 8.

  2. Reference: Section 8 of this technical guideline

  3. Test Method: Examine the number of occurrences for each metadata element. The number of occurrences shall be compared with its occurrence specified in Section 8:

NOTE 1 Section 2.1.2 of the Metadata Technical Guidelines discusses the different ISO 19139 XML schema

A.8.5. Metadata consistency test

  1. Purpose: Verify whether the metadata elements follow the path specified in ISO/TS 19139.

  2. Reference: Section 8 of this technical guideline, ISO/TS 19139

  3. Test Method: Compare the XML schema of each metadata element with the path provide in ISO/TS 19137.

NOTE 1 This test does not apply to the metadata elements that are not included in ISO/TS 19139.

A.8.6. Encoding schema validation test

  1. Purpose: Verify whether the provided dataset follows the rules of default encoding specified in section 9 of this document

  2. Reference: section 9 of this technical guideline

  3. Test Method: Inspect whether provided encoding(s) is conformant to the encoding(s) for the relevant application schema(s) as defined in section 9:

NOTE 1 Applying this test to the default encoding schema described in section 9 facilitates testing conformity with the application schema specified in section 5. In such cases running this test with positive result may replace tests from A1.1 to A1.4 provided in this abstract test suite.

NOTE 2 Using Schematron or other schema validation tool may significantly improve the validation process, because some some complex constraints of the schema cannot be validated using the simple XSD validation process. On the contrary to XSDs Schematron rules are not delivered together with the INSPIRE data specifications. Automating the process of validation (e.g. creation of Schematron rules) is therefore a task and an opportunity for data providers.

A.8.7. Coverage multipart representation test

  1. Purpose: Verify whether coverage data encoded as multipart messages comply with the multipart representation conformance class defined in GML Application Schema for Coverages [OGC 09-146r2].

  2. Reference: OGC standard GML Application Schema for Coverages [OGC 09-146r2].

  3. Test Method: Inspect whether coverage data encoded as multipart messages comply with the multipart representation conformance class defined in GML Application Schema for Coverages [OGC 09-146r2].

NOTE further information is provided in section 9.4 of this technical guideline.

A.8.8. Coverage domain consistency test

  1. Purpose: Verify whether the encoded coverage domain is consistent with the information provided in the GML application schema.

  2. Reference: Section 9.4.1.2 of this technical guideline.

  3. Test Method: For multipart coverage messages compare the encoded coverage domain with the description of the coverage component in the GML application schema

NOTE 1 This test applies only to those multipart messages, where the coverage range is encoded together with the coverage domain (some binary formats).

NOTE 2 .This test does not apply to multipart messages where the coverage range is embedded without describing the data structure (e.g. text based formats).

A.8.9. Style test

  1. Purpose: Verify whether the styles defined in section 11.2 have been made available for each specified layer.

  2. Reference: section 11.2.

  3. Test Method: Check whether the styles defined in section 11.2 have been made available for each specified layer.

Annex B: Use cases - (informative)

This annex describes the use cases that were used as a basis for the development of this data specification.

B.1. Environmental Impact Assessment of TEN-T related developments.

Use Case Description

Name

Environmental Impact Assessment of TEN-T related developments.

Priority

High

Description

This Use Case

This use case provides a very high level summary to support the development of the INSPIRE Transport Networks Data Specification.

From the INSPIRE Directive:

"7. Transport networks

Road, rail, air and water transport networks and related infrastructure. Includes links between different networks. Also includes the trans-European transport network as defined in Decision No 1692/96/EC of the European Parliament and of the Council of 23 July 1996 on Community Guidelines for the development of the trans-European transport network (1) and future revisions of that Decision.

(1) OJ L 228, 9.9.1996, p. 1. Decision as last amended by Council Regulation (EC) No 1791/2006 (OJ L 363, 20.12.2006, p. 1)."

L228 (Ref A) was updated in 2004 and that update is referred to in this document as Ref B. 1791/2006 (Ref C) introduces new member states but has less impact on the types of objects and how these might be used as part of an integrated transport network in Europe

The use case is based on the section on pre-conditions below – ie that an Environmental Impact Assessment will be performed on any new transport development.

The data sources section below outlines the transport network information/objects that are required as part of the transport network.

The Flow of Events section outlines some of the activities that might be executed using the transport network information (and possibly 3rd party information as well) to conduct an Environmental Impact Assessment based on Ref D.

Documentation

  1. Decision No 1692/96/EC of the European Parliament and of the Council of 23 July 1996 on Community guidelines for the development of the trans-European transport network Official Journal L 228 , 09/09/1996 P. 0001 - 0104

  2. DECISION No 884/2004/EC OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 29 April 2004 amending Decision No 1692/96/EC on Community guidelines for the development of the trans-European transport network

  3. COUNCIL REGULATION (EC) No 1791/2006 of 20 November 2006 adapting certain Regulations and Decisions in the fields of free movement of goods, freedom of movement of persons, company law, competition policy, agriculture (including veterinary and phytosanitary legislation), transport policy, taxation, statistics, energy, environment, cooperation in the fields of justice and home affairs, customs union, external relations, common foreign and security policy and institutions, by reason of the accession of Bulgaria and Romania

  4. COUNCIL DIRECTIVE of 27 June 1985 on the assessment of the effects of certain public and private projects on the environment (85/337/EEC) (OJ L 175, 5.7.1985, p. 40)

  5. Highway Agency (England and Wales) EnvIS methodology (see TWG TN Reference Material EnvIS Manual Parts 1-4)

B.2. Speed advice

Use Case Description

Name

Speed advice

Priority

Medium

Description

Demonstration of on-trip information and warning services on current speed limits on the road

Pre-condition

The EU project EuroRoadS has, based on requirements being described in the EU project Speed Alert, created a speed limit information model, which includes a number of characteristics of importance for giving a driver advice on highest recommended speed on a road segment. The model includes

  • differentiation of minimum/maximum speed limit

  • lane reference

  • validity period

  • area condition

  • source of information

  • vehicle dependency

Flow of Events – Basic Path

Step 1

The draft Inspire specification for Transport networks is compared with the EuroRoadS framework of specifications in order to find out if the specification gives the right level of detail for speed advice services

Step 2

After the theoretical study in step 1 a practical test might be carried out following the demonstration that was carried out within EuroRoadS. This requires contribution from the organisations who took part in this work.

Flow of Events – Alternative Paths

Step 1

  1. Review and comparison of the two specifications

  2. Report on findings

Step 2

  1. Agreement on demonstration area and participants for a more practical demonstration

  2. Establishment of work flow for demonstration

  3. Loading of test data according to the specification

  4. Practical tests

  5. Report on findings

Post-condition

Show the benefits from the specification for an application being of interest for political reasons (road safety, environmental protection, etc) as well as for private industry developments (speed advice device).

Data source: <Name> [repeat per data source]

Description

To be decided

Data provider

Geographic scope

Thematic scope

Scale, resolution

Delivery

Documentation

B.3. Journey planning

Use Case Description

Name

Journey planning

Priority

High

Description

Journey planning must provide information to travellers about timelines, transports services, transportation duration travel prices and travel plan.

Travel information must be provided by mean of website but too public information screens or personal devices.

Pre-condition

  • Existing information databases on public transport.

  • Geolocated information on transport stop, station and line.

Flow of Events – Basic Path

Step 1

Transport authority maintain a geolocated transport database

Step 2

Transport authority provide deliver transport information by mean of online platform

Step 3

Travellers request information by mean of browser with some very simple functions.

Flow of Events – Alternative Paths

Step 1

Report of event on transport network

Step 2

Take in account by transport autorithy

Post-condition

Data source:

Description

Data contain transport stops, stations and lines with associated transport timetables and prices.

Data provider

Transports authorities

Geographic scope

EU

Thematic scope

Public transport, urban planning, CO2 emissions

Scale, resolution

N/A

Delivery

Various in accordance with administrative organization of members states

Documentation

www.mivb.be

www.tec-wl.be

www.transport-idf.com

www.tmb.net

www.bluestarbus.co.uk

http://www.firstgroup.com/

Annex C: Code list values - (normative)

C.1. INSPIRE Application Schema 'Common Transport Elements'

Code List

AccessRestrictionValue

RestrictionTypeValue

AccessRestrictionValue

Definition:

Types of access restrictions for a transport element.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AccessRestrictionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

RestrictionTypeValue

Definition:

Possible restrictions on vehicles that can access a transport element.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RestrictionTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

C.2. INSPIRE Application Schema 'Road Transport Network'

Code List

AreaConditionValue

FormOfRoadNodeValue

FormOfWayValue

RoadPartValue

RoadServiceTypeValue

RoadSurfaceCategoryValue

ServiceFacilityValue

SpeedLimitSourceValue

VehicleTypeValue

WeatherConditionValue

AreaConditionValue

Definition:

Speed limit restriction depending on the area.

Description:

SOURCE [Euroroads].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AreaConditionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

FormOfRoadNodeValue

Definition:

Functions of road nodes within Euroroads.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FormOfRoadNodeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

FormOfWayValue

Definition:

Classification based on the physical properties of the road link.

Description:

SOURCE Based on [Euroroads].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FormOfWayValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

RoadPartValue

Definition:

Indication to which part of a road the value of a measurement applies.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RoadPartValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

RoadServiceTypeValue

Definition:

Types of road service areas.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RoadServiceTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

RoadSurfaceCategoryValue

Definition:

Values to indicate whether a road is paved or not paved.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RoadSurfaceCategoryValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

ServiceFacilityValue

Definition:

Possible service facilities available at a road service area.

Extensibility:

none

Identifier:

https://inspire.ec.europa.eu/codelist/ServiceFacilityValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

SpeedLimitSourceValue

Definition:

Possible sources for speed limits.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/SpeedLimitSourceValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

VehicleTypeValue

Definition:

Possible types of vehicles.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/VehicleTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

WeatherConditionValue

Definition:

Values to indicate weather conditions that affect speed limits.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/WeatherConditionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

C.3. INSPIRE Application Schema 'Railway Transport Network'

Code List

FormOfRailwayNodeValue

RailwayTypeValue

RailwayUseValue

FormOfRailwayNodeValue

Definition:

The possible functions of a railway node within the railway network.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FormOfRailwayNodeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

RailwayTypeValue

Definition:

The possible types of railway transport.

Extensibility:

none

Identifier:

!http://inspire.ec.europa.eu/codelist/RailwayTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

RailwayUseValue

Definition:

The possible uses of railways.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RailwayUseValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

C.4. INSPIRE Application Schema 'Cable Transport Network'

Code List

CablewayTypeValue

CablewayTypeValue

Definition:

The possible types of cableway transport.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/CablewayTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

C.5. INSPIRE Application Schema 'Water Transport Network'

Code List

FerryUseValue

FormOfWaterwayNodeValue

FerryUseValue

Definition:

Types of transport carried out by a ferry.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FerryUseValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

FormOfWaterwayNodeValue

Definition:

Function of a WaterwayNode in the water transport network.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/FormOfWaterwayNodeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

C.6. INSPIRE Application Schema 'Air Transport Network'

Code List

AerodromeCategoryValue

AerodromeTypeValue

AirRouteLinkClassValue

AirRouteTypeValue

AirUseRestrictionValue

AirspaceAreaTypeValue

NavaidTypeValue

PointRoleValue

RunwayTypeValue

SurfaceCompositionValue

AerodromeCategoryValue

Definition:

Aerodrome possible categories concerning the scope and importance of the air traffic services offered from and to it.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AerodromeCategoryValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

AerodromeTypeValue

Definition:

A code specifying whether a particular entity occurrence is an Aerodrome or a Heliport.

Description:

SOURCE [CodeAirportHeliportType - AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AerodromeTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

AirRouteLinkClassValue

Definition:

The type of the route from the navigation point of view.

Description:

SOURCE [CodeRouteNavigationType - AIXM5.0].

NOTE These values enumerate the possible usages of a AirRouteLink.

EXAMPLES Conventional, RNAV.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AirRouteLinkClassValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

AirRouteTypeValue

Definition:

The route classification as ATS route or North Atlantic Tracks.

Description:

SOURCE [CodeRouteType - AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AirRouteTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

AirUseRestrictionValue

Definition:

The use restrictions for an air network object.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AirUseRestrictionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

AirspaceAreaTypeValue

Definition:

Recognised types of Airspace.

Description:

SOURCE [CodeAirspaceType - AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/AirspaceAreaTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

NavaidTypeValue

Definition:

Types of Navaid Services.

Description:

SOURCE [AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/NavaidTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

PointRoleValue

Definition:

Role of the Runway Centreline Point.

Description:

SOURCE [AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/PointRoleValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

RunwayTypeValue

Definition:

A code that makes a distinction between runways for airplanes and FATO for helicopters.

Description:

SOURCE [CodeRunwayType - AIXM5.0].

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/RunwayTypeValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

SurfaceCompositionValue

Definition:

A code indicating the composition of a surface.

Description:

SOURCE [CodeSurfaceCompositionType - AIXM5.0].

EXAMPLES Asphalt, concrete.

Extensibility:

none

Identifier:

http://inspire.ec.europa.eu/codelist/SurfaceCompositionValue

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.

Annex D: Imported Types - (informative)

This annex lists definitions for feature types, data types and code lists that are defined in other documents. The annex is purely informative and should help the reader understand the feature catalogues presented in sections 5.2.2, 5.2.3, 5.2.4, 5.2.5, 5.2.6 and 5.2.7. For the normative documentation of these types, see the references in sections 5.x.2.1 to 5.x.2.3.

D.1. Spatial object types

D.1.1. CrossReference

CrossReference

Definition:

Represents a reference between two elements in the same network.

Description:

The cross reference may represent the case where two elements are different representations of the same spatial object.

Status:

Proposed

Stereotypes:

«featureType»

Association role: element

Value type:

NetworkElement

Definition:

The cross referenced elements

Multiplicity:

2

D.1.2. GeneralisedLink

GeneralisedLink (abstract)

Subtype of:

NetworkElement

Definition:

Abstract base type representing a linear network element that may be used as a target in linear referencing.

Status:

Proposed

Stereotypes:

«featureType»

D.1.3. GradeSeparatedCrossing

GradeSeparatedCrossing

Subtype of:

NetworkElement

Definition:

Indicator which of two or more intersecting elements is/are above and which is/are below, to be used if elevation coordinates are not present or cannot be trusted.

Description:

Status:

Proposed

Stereotypes:

«featureType»

Association role: element

Value type:

Link

Definition:

Multiplicity:

2..*

D.1.4. Link

Link (abstract)

Subtype of:

GeneralisedLink

Definition:

Curvilinear network element that connects two positions and represents a homogeneous path in the network. The connected positions may be represented as nodes.

Status:

Proposed

Stereotypes:

«featureType»

Attribute: centrelineGeometry

Value type:

GM_Curve

Definition:

The geometry that represents the centreline of the link.

Multiplicity:

1

Attribute: fictitious

Value type:

Boolean

Definition:

Indicator that the centreline geometry of the link is a straight line with no intermediate control points – unless the straight line represents the geography in the resolution of the dataset appropriately.

Multiplicity:

1

Association role: endNode

Value type:

Node

Definition:

The optional end node for this link. The end node may be the same instance as the start node.

Multiplicity:

0..1

Association role: startNode

Value type:

Node

Definition:

The optional start node for this link.

Multiplicity:

0..1

D.1.5. LinkSequence

LinkSequence (abstract)

Subtype of:

GeneralisedLink

Definition:

A network element which represents a continuous path in the network without any branches. The element has a defined beginning and end and every position on the link sequence is identifiable with one single parameter such as length.

Description:

EXAMPLE A link sequence may represent a route.

Status:

Proposed

Stereotypes:

«featureType»

Attribute: link

Value type:

DirectedLink

Definition:

The ordered collection of directed links that constitute the link sequence.

Multiplicity:

1..*

Collection Constraints:

ordered

D.1.6. LinkSet

LinkSet (abstract)

Subtype of:

NetworkElement

Definition:

A collection of link sequences and/or individual links that has a specific function or significance in a network.

Description:

Status:

Proposed

Stereotypes:

«featureType»

Association role: link

Value type:

GeneralisedLink

Definition:

Multiplicity:

1..*

D.1.7. Network

Network

Definition:

A network is a collection of network elements.

Description:

The reason for collecting certain elements in a certain network may vary (e.g. connected elements for the same mode of transport)

Status:

Proposed

Stereotypes:

«featureType»

Attribute: geographicalName

Value type:

GeographicalName

Definition:

Geographical name for this network.

Multiplicity:

0..*

Stereotypes:

«voidable»

Association role: elements

Value type:

NetworkElement

Definition:

The collection of elements that constitutres the network.

Multiplicity:

0..*

D.1.8. NetworkArea

NetworkArea (abstract)

Subtype of:

NetworkElement

Definition:

A 2-dimensional element in a network.

Status:

Proposed

Stereotypes:

«featureType»

Attribute: geometry

Value type:

GM_Surface

Definition:

Represents the geometric properties of the area

Multiplicity:

1

D.1.9. NetworkConnection

NetworkConnection

Subtype of:

NetworkElement

Definition:

Represents a logical connection between two or more network elements in different networks.

Description:

In the case where the networks are in different spatial data sets, a network connection object may exist in both data sets.

Status:

Proposed

Stereotypes:

«featureType»

Attribute: type

Value type:

ConnectionTypeValue

Definition:

Categorisation of the network connection.

Multiplicity:

1

Stereotypes:

«voidable»

Association role: element

Value type:

NetworkElement

Definition:

Network elements in different networks

Multiplicity:

2..*

Constraint: Elements in different networks

Natural language:

All elements have to be in different networks

OCL:

inv: element→forAll( e1, e2

e1<>e2 implies e1.inNetwork→excludesAll(e2.inNetwork) )
!===

D.1.10. NetworkElement

NetworkElement (abstract)

Definition:

Abstract base type representing an element in a network. Every element in a network provides some function that is of interest in the network.

Status:

Proposed

Stereotypes:

«featureType»

Attribute: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the network element was inserted or changed in the spatial data set.

Multiplicity:

1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the network element.

Description:

NOTE An external object identifier is a unique object identifier published by the responsible body, which may be used by external applications to reference the spatial object. The identifier is an identifier of the spatial object, not an identifier of the real-world phenomenon.

Multiplicity:

0..1

Attribute: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the network element was superseded or retired in the spatial data set.

Multiplicity:

0..1

Stereotypes:

«lifeCycleInfo,voidable»

Association role: inNetwork

Value type:

Network

Definition:

The networks in which a network element is a member.

Multiplicity:

1..*

Stereotypes:

«voidable»

D.1.11. NetworkProperty

NetworkProperty (abstract)

Definition:

Abstract base type representing phenomena located at or along a network element. This base type provides general properties to associate the network-related phenomena (network properties) with the network elements.

Description:

In the simplest case (NetworkReference), the network property applies to the whole network element. In the case of a Link, the spatial reference may be restricted to part of the Link by using a linear reference. ISO/TC 211 is currently in the early stages of developing a standard for Linear Referencing (ISO 19148). A simple mechanism to express linear references is provided in this version of the network model; it is expected that the model will be extended once ISO 19148 is stable. The current simple model requires for all linear references two expressions representing a distance from the start of the Link along its curve geometry. The network property applies to the part of the Link between fromPosition and toPosition.

Status:

Proposed

Stereotypes:

«featureType»

Attribute: networkRef

Value type:

NetworkReference

Definition:

Spatial reference of the network-related property.

Description:

This attribute provides an indirect spatial reference based on a reference to an element of an underlying network. See the chapter on Object Referencing in the Generic Conceptual Model for a discussion on modelling object references.

Multiplicity:

1..*

Stereotypes:

«voidable»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the network property.

Description:

NOTE An external object identifier is a unique object identifier published by the responsible body, which may be used by external applications to reference the spatial object. The identifier is an identifier of the spatial object, not an identifier of the real-world phenomenon.

Multiplicity:

0..1

Attribute: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the network element was inserted or changed in the spatial data set.

Multiplicity:

1

Stereotypes:

«voidable,lifeCycleInfo»

Attribute: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the network element was superseded or retired in the spatial data set.

Multiplicity:

0..1

Stereotypes:

«voidable,lifeCycleInfo»

D.1.12. Node

Node (abstract)

Subtype of:

NetworkElement

Definition:

Represents a significant position in the network that always occurs at the beginning or the end of a link.

Description:

NOTE if a topological representation of the network is used the road node is either a topological connection between two or more links or the termination of a ink. If a geometric representation of the network is used road nodes are represented by points or alternatively another geometric shape. [EuroRoadS]

Status:

Proposed

Stereotypes:

«featureType»

Attribute: geometry

Value type:

GM_Point

Definition:

The location of the node.

Multiplicity:

1

Association role: spokeEnd

Value type:

Link

Definition:

The links that enter the node.

Description:

NOTE In the INSPIRE context, this spoke property is to be published when this information is published in current exchange formats of the data set.

Multiplicity:

0..*

Stereotypes:

«voidable»

Association role: spokeStart

Value type:

Link

Definition:

The links that leave the node.

Description:

NOTE In the INSPIRE context, this spoke property is to be published when this information is published in current exchange formats of the data set.

Multiplicity:

0..*

Stereotypes:

«voidable»

D.2. Data types

D.2.1. DirectedLink

DirectedLink

Definition:

A link either in its positive or negative direction.

Status:

Proposed

Stereotypes:

«dataType»

Attribute: direction

Value type:

Sign

Definition:

Indicates if the directed link agrees (positive) or disagrees (negative) with the positive direction of the link.

Multiplicity:

1

Association role: link

Value type:

Link

Definition:

The link

Multiplicity:

1

D.2.2. LinkReference

LinkReference

Subtype of:

NetworkReference

Definition:

A network reference to a linear network element.

Status:

Proposed

Stereotypes:

«dataType»

Attribute: applicableDirection

Value type:

LinkDirectionValue

Definition:

The directions of the generalised link to which the reference applies. In cases where a property does not apply to a direction along a link, but represents a phenomenon along a link, "inDirection" refers to the right side in the of the link.

Description:

EXAMPLE A speed limit is a property that applies to a direction of the link (or both directions) while a house number is a phenomenon along a link.

Multiplicity:

1

Stereotypes:

«voidable»

Constraint: Linear reference targets must be linear network elements

Natural language:

Linear reference targets must be linear network elements. I.e., if linear referencing is used or direction is relevant, the target of the network reference shall be a link or a link sequence.

OCL:

inv: element.oclIsKindOf(GeneralisedLink)

D.2.3. NetworkReference

NetworkReference

Definition:

A network reference to a network element.

Status:

Proposed

Stereotypes:

«dataType»

Association role: element

Value type:

NetworkElement

Definition:

Multiplicity:

1

Stereotypes:

«version»

D.2.4. SimpleLinearReference

SimpleLinearReference

Subtype of:

LinkReference

Definition:

A network reference that is restricted to part of a linear network element. The part is the part of the network element between the position along the network element between fromPosition and toPosition.

Status:

Proposed

Stereotypes:

«dataType»

Attribute: fromPosition

Value type:

Length

Definition:

The start position of the linear element, expressed as the distance from the start of the linear network element along its curve geometry.

Multiplicity:

1

Attribute: toPosition

Value type:

Length

Definition:

The end position of the linear element, expressed as the distance from the start of the linear network element along its curve geometry.

Multiplicity:

1

Attribute: offset

Value type:

Length

Definition:

An offset from the centerline geometry of the generalised link, where applicable; a positive offset is to the right in the direction of the link, a negative offset is to the left.

Multiplicity:

0..1

Stereotypes:

«voidable»

D.2.5. SimplePointReference

SimplePointReference

Subtype of:

LinkReference

Definition:

A network reference that is restricted to a point on a linear network element. The point is the location on the network element at the position atPosition along the network.

Status:

Proposed

Stereotypes:

«dataType»

Attribute: atPosition

Value type:

Length

Definition:

Position of the point, expressed as the distance from the start of the linear network element along its curve geometry.

Multiplicity:

1

Attribute: offset

Value type:

Length

Definition:

An offset from the centerline geometry of the generalised link, where applicable; a positive offset is to the right in the direction of the link, a negative offset is to the left.

Multiplicity:

0..1

Stereotypes:

«voidable»

D.3. Code lists

D.3.1. ConnectionTypeValue

ConnectionTypeValue

Definition:

Types of connections between different networks.

Status:

Proposed

Stereotypes:

«codeList»

Governance:

Centrally managed in INSPIRE code list register. URN: urn:x-inspire:def:codeList:INSPIRE:ConnectionTypeValue

Value: crossBorderConnected

Definition:

Connection between two network elements in different networks of the same type, but in adjacent areas. The referenced network elements represent the different, but spatially connected real-world phenomena.

Value: intermodal

Definition:

Connection between two network elements in different transport networks that use a different transport mode. The connection represents a possibility for the transported media (people, goods, etc) to change from one transport mode to another.

Value: crossBorderIdentical

Definition:

Connection between two network elements in different networks of the same type, but in adjacent areas. The referenced network elements represent the same real-world phenomena.

D.3.2. LinkDirectionValue

LinkDirectionValue

Definition:

List of values for directions relative to a link

Status:

Proposed

Stereotypes:

«codeList»

Governance:

Centrally managed in INSPIRE code list register. URN: urn:x-inspire:def:codeList:INSPIRE:LinkDirectionValue

Value: bothDirections

Definition:

In both directions.

Value: inDirection

Definition:

In direction of the link.

Value: inOppositeDirection

Definition:

In the opposite direction of the link.

Annex E: Supplementary Information regarding alternative representations of network objects - (informative)

E.1. Alternative Representations

This section describes the three main forms of road, rail and water transport network representation. The model supports Physical (topographic) and centreline representations.

image

Figure C1-1. Alternative transport network Representations

In the above Figure B1-1 the road is represented in three forms:

  1. Physical (topographic) extents. The lines shown in red above (ie edges of area objects) normally represent the extent of the surface of the highway, (or banks of the river at a given time of year e.g. winter water level). The area is normally segmented into several sub units (not shown on this sketch) where their aggregation will define the full extent of the road or river. Narrow sections will often be represented by a single line.

    This network can only be inferred since there is no knowledge of which objects connect in any ordered sequence or state (though this could be achieved if required – it is not covered on this version of the specification. Similar approaches are applicable to road, air and some aspects of cable and rail networks.

  2. Centreline model – (the green dashed line above) is a set of (or aggregation of) lines that represent the centre of the physical object e.g. a road or river – this usually the approximate centre (sometimes known as a reference line instead because of this). Nodes (red disks) are also shown in the figure above.

    Generally this approach will support topology and specific forms of network analysis. Therefore the sequence and relationships between the lines is understood and in some cases ordered. Nodes may be implied or explicit. All spatial objects will be described by coordinates.

    Centrelines are often linked to the underlying physical (topographic) extents – see Figure B1-2 below.

image

Figure C1-2: Linking centrelines and physical (topographic) extents

  1. Logical model – (the blue dashed line in Figure B1-1 above) is a set of lines linking all the nodes of the network (chosen to be junctions & ends). The spatial content is therefore limited or non-existent (spatial coordinates of the nodes are not always included) and the logical model has limited value to a spatial data infrastructure but it is used in some transport operations. The approach can be modelled in this specification by simply inserting a single link between nodes.

  2. Aligning Logical and Centreline Models: users may if they wish align a logical model with the centreline/physical models to share information between them within a set of applications. This can be achieved by relating (e.g. cross referencing all those nodes that are common in each system). The logical model can then inherit the spatial location of the centreline nodes which will provide a level of spatial positioning and interoperability.

1. The common document template is available in the "Framework documents" section of the data specifications web page at http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2
2. For all 34 Annex I,II and III data themes: within two years of the adoption of the corresponding Implementing Rules for newly collected and extensively restructured data and within 5 years for other data in electronic format still in use
3. The current status of registered SDICs/LMOs is available via INSPIRE website: http://inspire.jrc.ec.europa.eu/index.cfm/pageid/42
4. Surveys on unique identifiers and usage of the elements of the spatial and temporal schema,
5. The Data Specification Drafting Team has been composed of experts from Austria, Belgium, Czech Republic, France, Germany, Greece, Italy, Netherlands, Norway, Poland, Switzerland, UK, and the European Environment Agency
6. The Thematic Working Groups have been composed of experts from Austria, Australia, Belgium, Bulgaria, Czech Republic, Denmark, Finland, France, Germany, Hungary, Ireland, Italy, Latvia, Netherlands, Norway, Poland, Romania, Slovakia, Spain, Slovenia, Sweden, Switzerland, Turkey, UK, the European Environment Agency and the European Commission.
7. For Annex IIIII, the consultation and testing phase lasted from 20 June to 21 October 2011.
8. Commission Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services, published in the Official Journal of the European Union on 8th of December 2010.
9. The framework documents are available in the "Framework documents" section of the data specifications web page at http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2
10. UML – Unified Modelling Language
11. Conceptual models related to specific areas (e.g. INSPIRE themes)
12. In the case of the Annex IIIII data specifications, the extracted requirements are used to formulate an amendment to the existing Implementing Rule.
13. OJ L 228, 9.9.1996, p.1. Decision as last amended by Council Regulation (EC) No 1791/2006 (OJ L 363, 20.12.2006, p.1).
14. Included in the data specification as a separate sub-theme based on the comments received in the consultation process.
15. http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_tc_browse.htm?commid=54904
16. Generic Network Model (GNM) is described in the Generic Conceptual Model (v3.4rc3). The GNM provides the basic structure for network nodes, links, aggregated links and areas and basic mechanisms for: grade separating crossings between network elements, cross-referencing, adding properties to a network (including the use of linear referencing) and adding inter-network connections.
17. Linear referencing is included in the GNM based on ISO 19148.
18. http://inspire.jrc.ec.europa.eu/
19. The INSPIRE Glossary is available from http://inspire-registry.jrc.ec.europa.eu/registers/GLOSSARY
20. OJ L 326, 4.12.2008, p. 12.
21. The Implementing Rules and Technical Guidelines on INSPIRE Network Services are available at http://inspire.jrc.ec.europa.eu/index.cfm/pageid/5
22. OJ L 274, 20.10.2009, p. 9.