INSPIRE

Infrastructure for Spatial Information in Europe

[Link].6 Data Specification on "Utility and governmental

services" – Draft Guidelines
Title [Link].6 INSPIRE Data Specification on "Utility and governmental services" – Draft
Guidelines
Creator INSPIRE Thematic Working Group "Utility and governmental services"
Date 2012-07-09
Subject INSPIRE Data Specification for the spatial data theme "Utility and governmental
services"
Publisher INSPIRE Thematic Working Group "Utility and governmental services"
Type Text
Description This document describes the INSPIRE Data Specification for the spatial data theme
"Utility and governmental services"
Contributor Members of the INSPIRE Thematic Working Group "Utility and governmental
services"
Format Portable Document Format (pdf)
Source
Rights Restricted to TWG members, DT DS and CT
Identifier [Link].6_v3.0rc2
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)
Coverage Project duration
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page I

Change Log
Version Changed Sections Changes made
2.9 All Finalization of the relatedParty, and roles
2.9 Utility Networks Split of the Utility Network model in Core, Basic and Extended
The Core model has been trimmed in terms of properties and
2.9 Utility Networks
some of the trimmed parts are put in Extended (mainly codelists)
Oil and Gas Network is changed to Oil, Gas and Chemicals
2.9 Utility Networks
Network
2.9 Utility Networks New Thermal Network was added
2.9 Utility Networks New relationships defined between Cable, Pipe and Duct
2.9 Utility Networks New container elements added (Tower, Cabinet)
Model has been split in Core and Extended, in order to make it
2.9 Governmental Services
more simple and flexible
ServiceTypeValue codelist has been reduced, according to
2.9 Governmental Services
revised eligibility criteria (cf. § 2.2.2.)
Relation to external entities have been redefined (simplification +
2.9 Governmental Services opening to other subdomains : activityComplex + UtilityNode /
UtilityNetwork)
2.9 Governmental Services Use of the relatedParty (or contact for core profile)
Model has become an extension of the common ―Activity
Environmental
2.9 Complex‖ in order to improve the harmonization of common
Management Facilities
elements through ―Facilities‖ teams (AF, PF, US)
Integration of all remarks received from DT / DS, based on
3.0rc1 All
version 2.9
Intergation of all remarks received from the review by Member
3.0rc2 All
States (JIRA IRMS), based on 3.0rc1
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page II

Foreword
How to read the document?
This document describes the “INSPIRE data specification on "Utility and governmental services" –
Guidelines” version 3.0rc as developed by the Thematic Working Group (TWG) TWG_US using both
natural and a conceptual schema language.

The data specification is based on a common template used for all data specifications and has been
harmonised using the experience from the development of the Annex I data specifications.

This document provides guidelines for the implementation of the provisions laid down in the draft
Implementing Rule for spatial data sets and services of the INSPIRE Directive.

This document includes two executive summaries that provide a quick overview of the INSPIRE data
specification process in general, and the content of the data specification on "Utility and governmental
services" 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/will be responsible for implementing INSPIRE within the field of "Utility and
governmental services".

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.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page III

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 will be 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 are being specified: metadata,
interoperability of spatial data themes (as described in Annexes I, II, III of the Directive) and spatial
data services, network services and technologies, data and service sharing, and monitoring and
reporting procedures.
1
INSPIRE does not require collection of new data. However, after the period specified in the Directive
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 within
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
2
Communities (SDIC) and Legally Mandated Organisations (LMO) , have provided reference materials,
3
participated in the user requirement and technical surveys, proposed experts for the Data
4 5
Specification Drafting Team and Thematic Working Groups and participated in the public stakeholder

1
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
2
The current status of registered SDICs/LMOs is available via INSPIRE website:
[Link]
3
Surveys on unique identifiers and usage of the elements of the spatial and temporal schema,
4
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
5
The Thematic Working Groups of Annex II and III themes have been composed of experts from
Austria, Belgium, Bulgaria, Czech Republic, Denmark, Finland, France, Germany, Hungary, Ireland,
Italy, Latvia, Netherlands, Norway, Poland, Romania, Slovakia, Spain, Sweden, Switzerland, Turkey,
UK, the European Commission, and the European Environment Agency
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page IV

consultations on draft versions of the data specifications. These consultations covered expert reviews
6
as well as feasibility and fitness-for-purpose testing of the data specifications .

This open and participatory approach was successfully used during the development of the data
specification on Annex I data themes as well as during the preparation of the Implementing Rule on
7
Interoperability of Spatial Data Sets and Services for Annex I spatial data themes.,

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
data specifications and provides a coherent set of requirements and recommendations to achieve
interoperability. The pillars of the framework are five technical documents:


8
The Definition of Annex Themes and Scope describes in greater detail the spatial data
themes defined in the Directive, and thus provides a sound starting point for the thematic
aspects of the data specification development.


9
The Generic Conceptual Model defines the elements necessary for interoperability and
data harmonisation including cross-theme issues. It specifies requirements and
recommendations with regard to data specification elements of common use, like the
spatial and temporal schema, unique identifier management, object referencing, a generic
network model, some common code lists, etc. Those requirements of the Generic
Conceptual Model that are directly implementable will be included in the Implementing
Rule on Interoperability of Spatial Data Sets and Services.


10
The Methodology for the Development of Data Specifications defines a repeatable
methodology. It describes how to arrive from user requirements to a data specification
through a number of steps including use-case development, initial specification
development and analysis of analogies and gaps for further specification refinement.


11
The ―Guidelines for the Encoding of Spatial Data‖ defines how geographic information
can be encoded to enable transfer processes between the systems of the data providers
in the Member States. Even though it does not specify a mandatory encoding rule it sets
GML (ISO 19136) as the default encoding for INSPIRE.

 The ―Guidelines for the use of Observations & Measurements and Sensor Web
Enablement-related standards in INSPIRE Annex II and III data specification
development‖ provides guidelines on how the ―Observations and Measurements‖
standard (ISO 19156) is to be used within INSPIRE.

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
12
natural language as well as a formal conceptual schema language .

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

6
For Annex II+III, the consultation phase lasted from 20 June to 21 October 2011.
7
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
th
the Official Journal of the European Union on 8 of December 2010.
8
[Link]
ex_Themes_and_scope_v3.[Link]
9
[Link]
10
[Link]
11
[Link]
12
UML – Unified Modelling Language
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page V

13
19100 series, the INSPIRE Generic Conceptual Model, and the application schemas 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. Once finalised (version 3.0), the data specifications are
published as technical guidelines and provide the basis for the content of the Implementing Rule on
14
Interoperability of Spatial Data Sets and Services . The content of the Implementing Rule is extracted
from the data specifications keeping in mind short- and medium-term feasibility as well as cost-benefit
considerations. The requirements included in the Implementing Rule will be 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.

13
Conceptual models related to specific areas (e.g. INSPIRE themes)
14
In the case of the Annex II+III data specifications, the extracted requirements will be used to
formulate an amendment to the existing Implementing Rule.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page VI

"Utility and governmental services" – Executive Summary

The theme “Utility and Governmental Services” covers a huge number of feature types under its scope
(i.e. miscellaneous energy networks, plentiful public services of different types and several
environmental management facilities).

In order to develop data specifications, the list of geographical entities has been strongly restricted to
the features linked with environment (according to the INSPIRE directive fundamentals) and moreover
dispatched in three main subthemes described below.

Nevertheless, the “Utility and Governmental Services” thematic approach consists in providing quite
simple information describing such services, among which:
 Feature location;
 Party involved in the service (Administration or organization on behalf of an administrative
mandate);
 Basic technical characteristics, such as capacity or details on the type of service provided.

The use cases studied and taken into account in the data specifications development process are
based on few European regulation processes (such as the Waste Framework Directive– cf. Annexes B
& C of the current document), but other non-legally referenced basic uses - as locating features and
simply describing information - were also to be considered.
This statement is principally due to (i) various national and local uses – impossible to be exhaustively
considered – and also (ii) the aim of simplicity underlying the data specifications development process.

Considering width of the scope, it has been decided to split the thematic into 3 different sub-domains:
1. Utility networks;
2. Administrative and social governmental services;
3. Environmental management facilities.

Each of them has its own modelization, independent from one to another (though some elements may
be linked between sub-domains).
The purpose of such an approach is permitting to any data provider and user to exchange its own data
with as much flexibility as possible.

1. The “Utility networks” sub-model is structured into 2 profiles:

 Core Utility Networks Profile: derived from the Generic Network model , this modelization is
15

based on a node-arc-node structure and network concept. Especially designed for utility
networks managers willing to describe their data into a structured modelization that allows its
business use (estimation of propagation, calculation of capacities, etc.); the technical
description of several network elements is limited to very simple information (type of material
transported and basic characteristics). The use of this profile is also adapted for non-
topological data, since the relation between nodes and arcs is optional;

 Extended Utility Networks Profile: annexed proposals for richer models, detailing the Core
Utility Networks Profile, i.e. same structure based on the Generic Network model and many
other attributes and lists of values proposed to better describe the utility networks
characteristics for a richer use.

In each profile, the information is detailed in several application schemas:

 Electricity network
 Oil, Gas & Chemicals network
 Sewer network
 Telecommunications network (only proposed in the technical guidance, out of legislation)
 Thermal network
 Water network

15
developed and used by Annex I “Transport networks” and “Hydrography” themes
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page VII

In addition to generic network information (utility link elements, connection with nodes and belonging
to a network), each element (UtilityLinkSequenceOrLink, UtilityNode and UtilityNetwork) is detailed
within its specific application schema through various attributes, developed through several codelists
values or Measure types for most of them.

2. The model of the “Administrative and social governmental services” sub-theme is based on
one single central feature type, ―GovernmentalService‖, that is basic in a core-defined profile (mainly
location, contact and type of service information) and detailed in an extended one (including
occupancy, resources and other description).
Its geometric reference can be whether another existing object (such as INSPIRE Annex I ―Address‖,
Annex III ―Building‖ or abstract type ―ActivityComplex‖ described below) or a created object
(GM_Object, mostly GM_Point to be consistent with the well-used notion of POI = Point of Interest).
The GovernmentalService type value is selected from a codelist of more than 50 items, organized in a
hierarchical structure, based on the ―Classification of the functions of government‖ - abbreviated as
COFOG, currently used by EUROSTAT, and developed within the respect of INSPIRE criteria (focused
on public & environmental aspects).

3. The “Environmental Management Facilites” application schema defines a single feature type
called ―EnvironmentalManagementFacility‖, with a generic geometric reference (GM_Object).
―EnvironmentalManagementFacility‖ is a specialisation of the Generic Conceptual Model
―ActivityComplex‖ feature type. This ensures close alignment (harmonisation) with other feature types
derived from ―ActivityComplex‖, especially those from the Production and Industrial Facilities (PF) and
Agricultural and Aquaculture Facilities (AF) themes.
The ―EnvironmentalManagementFacility‖ feature type is suitable for the representation of sites and
installations. The ―parentFacility‖-association from ―EnvironmentalManagementFacility‖ to
―EnvironmentalManagementFacility‖ supports the representation of hierarchies among installations
and sites.
Several aspects of environmental management facilities are represented in the model, most notably
facility functions, permissions, capacities, related parties (owners, operators, authorities) and status
information. Several established codelists are used for the representation of such aspects, including
Eurostat‘s NACE list of economic activities, the Decision 2000/532 List of Wastes and the Waste
Framework Directive (2008/98) list of disposal and recovery operations.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page VIII

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

The Thematic Working Group Utility and governmental services (TWG-US) included:
Frédéric BRÖNNIMANN (TWG Facilitator), Pedro A. GONZÁLEZ PÉREZ, Frank HAUGAN, Angel LÓPEZ ALÓS
(European Commission contact point), Nadine MAGDALINSKI, Katleen MISEREZ, Norbert PFAFFINGER
(―Environmental Management Facilities‖ Editor), Janine RITSCHL, Frank SCHWARZBACH (―Administrative
and social governmental services‖ Editor), Maksim ŠESTIĆ (TWG Editor), Jef VANBOCKRYCK (―Utility
Networks‖ Editor).

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) or Legally Mandated Organisations (LMOs).

Contact information
Vanda Nunes de Lima
European Commission Joint Research Centre
Institute for Environment and Sustainability
Spatial Data Infrastructures Unit
TP262, Via Fermi 2749
I-21027 Ispra (VA)
ITALY
E-mail: [Link]@[Link]
Tel.: +39-0332-7865052
Fax: +39-0332-7866325
[Link]
[Link]
[Link]
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page IX

Table of contents
1 Scope .............................................................................................................................................. 1

2 Overview ......................................................................................................................................... 1
2.1 Name ......................................................................................................................................... 1
2.2 Informal description ................................................................................................................... 1
2.2.1 Utility networks ................................................................................................................... 2
2.2.2 Administrative and social governmental services .............................................................. 3
2.2.3 Environmental management facilities ................................................................................ 5
2.3 Normative References .............................................................................................................. 7
2.4 Terms and definitions ................................................................................................................ 8
2.5 Symbols and abbreviations ....................................................................................................... 8
2.6 Notation of requirements and recommendations ...................................................................... 9
2.7 Conformance............................................................................................................................. 9
3 Specification scopes ..................................................................................................................... 10

4 Identification information ............................................................................................................... 10

5 Data content and structure ........................................................................................................... 10

5.1 Basic notions ........................................................................................................................... 16
5.1.1 Stereotypes ...................................................................................................................... 16
5.1.2 Placeholder and candidate types..................................................................................... 17
5.1.3 Voidable characteristics ................................................................................................... 17
5.1.4 Enumerations ................................................................................................................... 18
5.1.5 Code lists ......................................................................................................................... 18
5.1.6 Choices of standard types ............................................................................................... 20
5.2 Application Schemas ―Utility Networks‖ .................................................................................. 21
5.2.1 General Description ......................................................................................................... 21
5.2.2 ―Common Core Utility Networks Elements‖ application schema ..................................... 24
5.2.3 ―Core Electricity Network‖ application schema ................................................................ 44
5.2.4 ―Core Oil-Gas-Chemicals Network‖ application schema ................................................. 51
5.2.5 ―Core Sewer Network‖ application schema ..................................................................... 56
5.2.6 ―Core Thermal Network‖ application schema .................................................................. 60
5.2.7 ―Core Water Network‖ application schema ...................................................................... 63
5.3 Application schema ―Administrative and social governmental services‖ ................................ 70
5.3.1 Description ....................................................................................................................... 70
5.3.2 Feature Catalogue: Core Administrative and Social Governmental Services. ................ 74
5.3.3 Feature Catalogue: Extension Administrative and Social Governmental Services. ........ 81
5.3.4 INSPIRE-governed code lists .......................................................................................... 84
5.3.5 Externally governed code lists ......................................................................................... 88
5.4 Application schema ―Environmental Management Facilities‖ ................................................. 88
5.4.1 Description ....................................................................................................................... 88
5.4.2 Feature catalogue ............................................................................................................ 94
5.4.3 INSPIRE-governed code lists ........................................................................................ 101
5.4.4 Externally governed code lists ....................................................................................... 101
6 Reference systems ..................................................................................................................... 101
6.1 Coordinate reference systems .............................................................................................. 101
6.1.1 Datum ............................................................................................................................ 101
6.1.2 Coordinate reference systems ....................................................................................... 101
6.1.3 Display ........................................................................................................................... 102
6.1.4 Identifiers for coordinate reference systems .................................................................. 102
6.2 Temporal reference system .................................................................................................. 103
6.3 Theme-specific requirements and recommendations on reference systems ....................... 103
7 Data quality ................................................................................................................................. 103
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page X

7.1 Data quality elements............................................................................................................ 104

7.1.1 Completeness – Commission ........................................................................................ 105
7.1.2 Completeness – Omission ............................................................................................. 105
7.1.3 Logical consistency – Conceptual consistency ............................................................. 106
7.1.4 Logical consistency – Domain consistency ................................................................... 106
7.1.5 Logical Consistency – Format consistency ................................................................... 106
7.1.6 Logical Consistency – Topological consistency ............................................................ 107
7.1.7 Positional accuracy – Absolute or external accuracy .................................................... 109
7.1.8 Positional accuracy – Relative or internal accuracy ...................................................... 111
7.1.9 Thematic accuracy – Classification correctness ............................................................ 112
7.1.10 Thematic accuracy – Non-quantitative attribute correctness ..................................... 112
7.1.11 Thematic accuracy – Quantitative attribute accuracy ................................................ 113
7.1.12 Temporal quality – Accuracy of a time measurement ................................................ 114
7.1.13 Temporal quality – Temporal consistency ................................................................. 115
7.2 Minimum data quality requirements ...................................................................................... 115
7.3 Recommendation on data quality ......................................................................................... 115
8 Dataset-level metadata ............................................................................................................... 116
8.1 Common metadata elements ................................................................................................ 116
8.1.1 Coordinate Reference System....................................................................................... 118
8.1.2 Temporal Reference System ......................................................................................... 118
8.1.3 Encoding ........................................................................................................................ 119
8.1.4 Character Encoding ....................................................................................................... 120
8.1.5 Data Quality – Logical Consistency – Topological Consistency .................................... 120
8.2 Metadata elements for reporting data quality ....................................................................... 121
8.3 Theme-specific metadata elements ...................................................................................... 122
8.3.1 Maintenance Information ............................................................................................... 122
8.4 Guidelines on using metadata elements defined in Regulation 1205/2008/EC ................... 123
8.4.1 Conformity...................................................................................................................... 123
8.4.2 Lineage .......................................................................................................................... 123
8.4.3 Temporal reference ....................................................................................................... 124
9 Delivery ....................................................................................................................................... 124
9.1 Delivery medium ................................................................................................................... 124
9.1.1 Specific Delivery medium .............................................................................................. 125
9.2 Encodings ............................................................................................................................. 125
9.2.1 Default Encoding(s) ....................................................................................................... 125
9.2.2 Alternative Encoding(s) .................................................................................................. 126
10 Data Capture............................................................................................................................... 126

11 Portrayal ...................................................................................................................................... 127

11.1 Layers to be provided by INSPIRE view services ............................................................. 128
11.1.1 Layers organisation .................................................................................................... 129
11.2 Styles to be supported by INSPIRE view services ............................................................ 129
11.2.1 Styles for the layer ―Administrative and social governmental services‖ ..................... 130
11.2.2 Styles for the layer ―Environmental Management Facilities‖ ...................................... 131
11.3 Other recommended styles ............................................................................................... 132
Bibliography ......................................................................................................................................... 133

Annex A (normative) Abstract Test Suite ........................................................................................... 134

Annex B (informative) Use cases ........................................................................................................ 135

B.1 Use case for ―Utility networks‖ .............................................................................................. 135
B.1.1 Introduction .................................................................................................................... 135
B.1.2 Use case description: Use case TWG_US_UN_KLIP ................................................... 135
B.2 Use case for ―Administrative and social governmental services‖ ......................................... 138
B.2.1 Introduction .................................................................................................................... 138
B.2.2 Use case TWG_US_GS_Map_case ............................................................................. 139
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page XI

B.2.3 Use case TWG_US_GS_Data_case ............................................................................. 141

B.2.4 Use Case: SITMAP – Territorial Information System of Málaga Province (Spain) ....... 144
B.3 Use case for ―Waste Management‖ ...................................................................................... 145
B.3.1 Introduction .................................................................................................................... 145
B.3.2 Use case description: Use case Waste Management Plans and Waste Shipments. ... 146
B.3.3 Cross Thematic Data requirements ............................................................................... 158
Annex C (informative) Checklists for data interoperability .................................................................. 161

Annex D (informative) ServiceTypeValue codelist .............................................................................. 162

Annex E (informative) Portrayal analysis ............................................................................................ 164

Annex F (informative) Extended Utility Networks ................................................................................ 165

F_1 Application schema ―Extended Utility Networks‖ .................................................................. 165
F_1.1 ―Common Extended Utility Networks Elements‖ application schema ................................... 165
F_1.1.1 UML Overview ............................................................................................................. 165
F_1.2 ―Extended Electricity Network‖ application schema ............................................................ 166
F_1.2.1 UML Overview ............................................................................................................. 166
F_1.2.2 Feature catalogue ........................................................................................................ 166
F_1.3 ―Core Oil-Gas-Chemicals Network‖ application schema ..................................................... 168
F_1.3.1 UML Overview ............................................................................................................. 168
F_1.4 ―Core Sewer Network‖ application schema ........................................................................ 171
F_1.4.1 UML Overview ............................................................................................................. 171
F_1.4.2 Feature catalogue ........................................................................................................ 172
F_1.5 ―Core Thermal Network‖ application schema ...................................................................... 174
F_1.5.1 UML Overview ............................................................................................................. 174
F_1.5.2 Feature catalogue ........................................................................................................ 175
F_1.6 ―Core Water Network‖ application schema .......................................................................... 176
F_1.6.1 UML Overview ............................................................................................................ 176
F_1.6.2 Feature catalogue ........................................................................................................ 177
F_1.7 INSPIRE-governed code lists for the ―Extended Utility Networks‖ subdomain‘s application
schemas ........................................................................................................................................... 179
F_1.8 Externally governed code lists for the ―Extended Utility Networks‖ subdomain‘s application
schemas ........................................................................................................................................... 197
Annex G (informative) External new types .......................................................................................... 198
G_1 Application schema ―RelatedParty‖....................................................................................... 199
G_1.1 UML Overview ................................................................................................................... 199
G_1.2 INSPIRE-governed code lists for the ―RelatedParty‖ application schema ........................ 200
G_1.3 Externally governed code lists for the ―RelatedParty‖ application schema ....................... 200
Annex H (informative) Telecommunication Networks ......................................................................... 201
H_1.1 UML Overview ..................................................................................................................... 201
H_1.2 Feature Catalogue................................................................................................................ 202
H_1.3 INSPIRE-governed code lists ............................................................................................... 204
H_1.3.1 Values of code list TelecommunicationsAppurtenanceTypeBaseValue ....................... 204
H_1.3.2 Values of code list TelecommunicationsCableMaterialTypeBaseValue ................ 206
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 1

1 Scope
This document specifies a harmonised data specification for the spatial data theme "Utility and
governmental services" as defined in Annex III 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 will be published as
implementation guidelines accompanying these Implementing Rules.

2 Overview

2.1 Name
INSPIRE data specification for the theme "Utility and governmental services".

2.2 Informal description

Definition:

The "Utility and governmental services" theme is defined within the INSPIRE Directive as:

“Includes utility facilities such as sewage, waste management, energy supply and water supply,
administrative and social governmental services such as public administrations, civil protection sites,
schools and hospitals.”

[Directive 2007/2/EC]

Description:

In order to facilitate the drafting of the data specifications of this declared “very broad INSPIRE theme
16
including different kinds of objects” , the Thematic Working Group (TWG) on "Utility and governmental
services" developed the following specific approach:
The theme "Utility and governmental services" has been divided in three sub-themes, dealing respectively
with:
 Utility networks
 Administrative and social governmental services
 Environmental management facilities

16
D2.3 Definition of Annex Themes and scope
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 2

Figure 1 – Initial repartition of the US theme’s scope within 3 sub-themes

Nota Bene: The above figure represents (in blue boxes) elements of the sub-scopes as they were initially
proposed for the development of these data specifications. Sub-scopes’ elements have evolved since.

The ―Environmental protection facilities‖ initial part of the scope has been quickly split into the
17
―Administrative and social governmental services‖ and the ―Waste treatment facilities and waste
storage‖ sub-themes.

Each sub-theme‘s specific sub-scope is detailed hereunder.

2.2.1 Utility networks

Comprehension of the scope

Utility services and networks include the physical constructions for transport of defined utility products
(namely pipelines for transport of oil, gas, chemicals, water, sewage and thermal products), transmission
lines and cables (included those for transmission of electricity, phone and cable-TV signals) and other
network elements for encasing pipes and cases (e.g. ducts, poles and towers).

All kinds of transmission utility systems have nodes like e.g. pump stations, and they are linked to
facilities for production and treatment of different kinds of utility products. These major production and
treatment sites are treated in the theme production and industrial facilities.

Six important types of utility networks are distinguished, namely Electricity Network, Oil, Gas & Chemicals
Network, Sewer Network, Telecommunications Network, Thermal Network and Water Network.

All these networks use the node-arc-node model, as defined in the generic network model developed by
the Transport Networks and the Hydrography thematic working groups (Annex I). Especially designed for

17
and later became OtherContruction features in the Buildings Theme
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 3
a structured modelization of utility networks that allows its business use (estimation of propagation,
calculation of capacities, etc.), the use of this node-arc-node model is also adapted for non-topological
data, since the relation between nodes and arcs is optional.

It is acknowledged that each organization has different responsibilities and this will influence the kind of
data they collect, manage and use. Some organizations will use simple models while other will have more
complex data models. This data specification is a basic framework that user can adopt and, if necessary,
adapt and extend for themselves. The specification is focused on the core spatial objects required by
networks, i.e. network centerlines etc. Not all the application-specific spatial objects (e.g. flow
measurement sensors) are incorporated. Non-geographic data (e.g. information on flow in m³/s) is also
out of scope of this specification.

In the utility services and networks there are ―ducts‖, which are utility links used to protect and guide cable
and pipes via an encasing construction. A duct may contain other duct(s), pipes and cables. ―Duct‖
contains information about the position and characteristics of ducts as seen from a manhole, vault, or a
cross section of a trench and duct.
The nodes of the networks include poles. Poles represent node objects that support utility devices and
cables. ―Pole‖ is a container to other utility objects. Other important nodes are manholes, towers and
cabinets. A ―Manhole‖ is the top openings to an underground public utility or service. A ―Tower‖ is a
vertical tower object that carries utility cables or pipes. A ―Cabinet‖ is container for utility node objects
(e.g. appurtenances). Poles, manholes, towers and cabinets represent containers for other network
elements belonging to one or more utility networks.

Overlaps / links with other themes

This sub-theme might overlap with themes:

 Hydrography (A-I.8)
 Buildings (A-III.2)
 Land use (A-III.4)
 Environmental monitoring facilities (like treatment plants/pumping stations) (A-III.7)
 Production and industrial facilities (A-III.8)
 Energy resources (A-III.20)

Current sub-theme holds potential dependencies with the following themes:

 Annex I
o Coordinate reference systems (geo-referencing of the point)
o Geographical grid systems (geo-referencing of the point)
o Geographical names (Identification of the point and of the place where it is located)
o Administrative units (that contain the point)
o Addresses (referencing of the point)
o Cadastral parcels (that contain the given service and from which the service is provided)
o Transport networks (that provide access to/from the services)
o Protected sites (that may contain services or being potential receptors of these)
 Annex II
o Elevation (referencing of the point)
 Annex III
o Statistical units (that contain the point)
o Buildings (that contain the given service and from which the service is provided)
o Population distribution – demography (potential service ―clients‖)
o Utilities (that the service make use/depend on)

2.2.2 Administrative and social governmental services

Comprehension of the scope

According to the INSPIRE Directive, the scope of the sub-theme comprises ―… administrative and social
governmental services such as public administrations, civil protection sites, schools and hospitals. [Annex
III].‖
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 4

On another hand, INSPIRE document ―Definition of Annex Themes and Scope v3.0 (D 2.3)‖ details
governmental services as those fitting the following description:
“Administrative and social governmental services such as public administrations, civil protection sites,
schools, hospitals. The kinds of sites that are commonly presented in governmental and municipal portals
and map systems as “points of interest”-data (POI), and may be point-based location of a variety of
categories of municipal and governmental services and social infrastructure”.

Given this description and, very specially, the concrete mention to the use of this type of data as POI, a
wide interpretation of what ―administrative and social governmental services‖ should be done.

In this same sense, the following words from the manual of the Spanish EIEL (Spanish acronym for
Enquiry on Local Infrastructures and Services) database, which does also contain information on public
services, may be considered as highly relevant: ―(...)The variety of ways how public services are provided
and the correspondent variety in facilities management, as well as the concurrent activity of different
Public Administration bodies, do recommend having in mind a broad scope on what are the utilities and
services that are collectively facing the same needs‖.

Eligibility criteria
To identify the relevant service types, legal requirements (mainly the wording of the INSPIRE directive
itself) as well as requirements based on use cases have to be considered. In detail a list of relevant
criteria has been defined. Thus service types are within the scope, when they are
 explicitly mentioned in the INSPIRE directive Annex III (―such as public administrations, civil
protection sites, schools and hospitals‖) or
 in a common understanding covered by the general scope of the annex theme (―administrative and
social governmental services‖) and which are similar to the explicitly mentioned ones (e.g.
kindergarten) or
 covered by the general scope of the annex theme (partly in a broader sense of ―public‖ service)
and which obviously address environmental issues (e.g. environmental education center) or
 generally considered as ―social governmental services‖ (e.g. specialized service for the disabled) or
 in a common understanding covered by the general scope of the annex theme and whose main
purpose is to provide services for environmental risk/disaster assessment/management (e.g. civil
protection sites) or
 in a common understanding covered by the general scope of the annex theme and which are the
most important means of governments to manage (environmental) disaster events (e.g. police
services).

Aside, there are a lot of public services (in a broader sense), whose main purpose is not to provide
services in environmental disaster events but can be used in these situations, like sports halls or fair
venues. For example, thousands of people took shelter in the New Orleans‘ Superdome during the
hurricane Katrina. Despite this, these sites are neither seen first and foremost as ―administrative and
social governmental services‖ nor do they have an environmental context. Therefore, they are not
considered to be within the scope of this data specification.
Furthermore, some ―administrative and social governmental services‖ can be regarded as especially
―vulnerable‖ to environmental disasters. This aspect is covered by the ―Natural risk zones‖ theme and
therefore out of scope of this data specification.

In opposite to the criteria listed above, the fact whether the service is provided by a Public Administration
Body (PAB) or by private institutions is not a relevant criterion. Very often, administrative and social
governmental services are not provided by the PAB itself but by a private institution as a matter of public
interest. In many cases, this varies from Member State to Member State, from region to region and from
municipality to municipality.

Overlaps / links with other themes

Overlaps: This sub-themeoverlaps the following ones:

 Buildings (A-III.2), e.g. use of buildings
 Human health and safety (A-III.5), e.g. hospitals
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 5
 Natural risk zones (A-III.12), e.g. a number of governmental services can be considered as
vulnerable elements too (e.g. schools)

Namely, in the case of ―Human health and safety‖, there is a clear overlap given that, despite its
description estates: ―Geographical distribution of dominance of pathologies (allergies, cancers, respiratory
diseases, etc.), information indicating the effect on health (biomarkers, decline of fertility, epidemics) or
well-being of humans (fatigue, stress, etc.) linked directly (air pollution, chemicals, depletion of the ozone
layer, noise, etc.) or indirectly (food, genetically modified organisms, etc.) to the quality of the
environment‖, further in the document it has been written that, between other, this theme should focus on
the description of ―health care services‖.

Links and dependencies: The sub-theme holds potential dependencies with the following themes,
primarily in order to provide the spatial reference of the services respectively the (spatial) area of
responsibility of the service
 Annex I
Coordinate reference systems
Geographical names
Administrative units
Addresses
 Annex III
Buildings

2.2.3 Environmental management facilities

Comprehension of the scope

The INSPIRE Directive ―Definition of Annex Themes and Scope v3.0 (D 2.3)‖ states that this sub-theme
comprises several categories in order to identify the environmental protection facilities. Categories such
as waste treatment sites, waste treatment facilities, regulated and illegal areas for dumping, mining waste
and sewage sludge are mentioned as categories to be included. The use cases also indicate the need for
providing information on waste treatment, storage and disposal.

The sub-theme scope therefore includes all the facilities involved or/and requested by law to be
registered on the management of all kind of wastes of the ―European Waste Catalogue and Hazardous
Waste List‖. Locations of the facilities are given by point or polygon. The waste management facilities are
referred to either as installations or sites, where an installation is understood as a stationary unit where
one or more waste management activities are carried out, or any other directly associated activities. The
site is understood as a single location, in which certain infrastructure and facilities are shared, and where
waste management activities take place.

All of the following is considered relevant for the scope: The function of the environmental facility,
expressed as economic activity (typically as waste management activity), permissions, inputs and
outputs. In addition, information on service hours and capacities are also linked to facility, as well as
operators, owners, contacts, and competent authorities.

Waste management activities are distinguished by categories such as storage, recovery, and/or disposal
of waste. Economic activities can be categorized by entries of the NACE catalogue (Classification of
Economic Activities in the European Community), particularly those under the `E´-Group ―Water supply;
sewerage; waste management and remediation activities‖. The Eurostat CPA list of products (Annex to
Regulation (EC) n. 451/2008) is used for the classification of output products.

The Environmental Management Facilities Model is based on the Generic Activity Complex Model and in
the Data Types described on it as potential extensions.

Organization of information

The following types of data are within the scope of the TWG-US sub-theme. They are provided with links
to reference documents that illustrate which user requirements the type of data originate from.
 Discharge [9] (of waste water)
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 6
 Disposal [1] (of waste)
 Dumping [1] (of waste at sea)
 Facility [3] (of waste production, treatment, storage)
 Hazardous waste [1]
 Incineration [8] (of waste)
 Installation [3]
 Landfill [13] (of waste)
 Non-hazardous waste [1]
 Plant [8] (of waste production, treatment, storage)
 Radioactive waste [14]
 Recovery [1] (of waste)
 Site [3] (of waste production, treatment, storage)
 Storage [8] (of waste)
 Treatment [1] (of waste or waste water)
 Transfer [3],[4] (of waste)
 Waste [1]
 Waste water [9]

Data out of scope:

 Emissions [2]
 Exhaust gas [8]
 Flooding
 Pollutants [3]

Dependencies and Overlaps

The following overlaps with other Feature Types have been identified:
 Buildings: Certain environmental management facilities may be regarded as buildings (and vice versa).
 Production and Industrial Facilities: A production facility may be an environmental management facility, for
instance in cases where waste is used as fuel.
 Land use: Dumping of waste onto land and landfills may be seen as overlapping with land use

Reference documents
[1] Directive 2008/98/EC of the European Parliament and of the Council of 19 November 2008 on
waste
[2] Directive 2008/1/EC of the European Parliament and of the Council of 15 January 2008 concerning
integrated pollution prevention and control
[3] Regulation (EC) No 166/2006 of the European Parliament and of the Council of 18 January 2006
concerning the establishment of a European Pollutant Release and Transfer Register
[4] Regulation (EC) No 1013/2006 of the European Parliament and of the Council of 14 June 2006 on
shipments of waste
[5] Directive 2006/66/EC of the European Parliament and of the Council of 6 September 2006 on
batteries and accumulators and waste batteries and accumulators
[6] Directive 2006/21/EC of the European Parliament and of the Council of 15 March 2006 on the
management of waste from extractive industries and amending Directive 2004/35/EC - Statement
by the European Parliament, the Council and the Commission
[7] Regulation (EC) No 2150/2002 of the European Parliament and of the Council of 25 November
2002 on waste statistics
[8] Directive 2002/96/EC of the European Parliament and of the Council of 27 January 2003 on waste
electrical and electronic equipment (WEEE)
[9] 2000/532/EC: Commission Decision of 3 May 2000 replacing Decision 94/3/EC establishing a list
of wastes pursuant to Article 1(a) of Council Directive 75/442/EEC on waste and Council Decision
94/904/EC establishing a list of hazardous waste pursuant to Article 1(4) of Council Directive
91/689/EEC on hazardous waste (notified under document number C(2000) 1147) (Text with EEA
relevance)
[10] Directive 2000/76/EC of the European Parliament and of the Council of 4 December 2000 on the
incineration of waste
[11] Directive 2000/60/EC of the European Parliament and of the Council of 23 October 2000
establishing a framework for Community action in the field of water policy
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 7
[12] Directive 2000/53/EC of the European Parliament and of the Council of 18 September 2000 on
end-of life vehicles
[13] Council Regulation (EEC) No 696/93 of 15 March 1993 on the statistical units for the observation
and analysis of the production system in the Community
[14] European Parliament and Council Directive 94/62/EC of 20 December 1994 on packaging and
packaging waste
[15] Council Directive 1999/31/EC of 26 April 1999 on the landfill of waste
[16] Council Directive 92/3/Euratom of 3 February 1992 on the supervision and control of shipments of
radioactive waste between Member States and into and out of the Community
[17] Council Directive 91/271/EEC of 21 May 1991 concerning urban waste-water treatment

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 19108] EN ISO 19108:2005, Geographic Information – Temporal Schema

[ISO 19108-c] ISO 19108:2002/Cor 1:2006, Geographic Information – Temporal Schema, Technical
Corrigendum 1

[ISO 19111] EN ISO 19111:2007 Geographic information - Spatial referencing by coordinates (ISO
19111:2007)

[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 19123] EN ISO 19123:2007, Geographic Information – Schema for coverage geometry and
functions

[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-103r3] Implementation Specification for Geographic Information - Simple feature access – Part
1: Common Architecture v1.2.0

NOTE This is an updated version of "EN ISO 19125-1:2006, Geographic information – Simple
feature access – Part 1: Common architecture". A revision of the EN ISO standard has been proposed.

[Regulation 1205/2008/EC] Regulation 1205/2008/EC implementing Directive 2007/2/EC of the

European Parliament and of the Council as regards metadata
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 8

2.4 Terms and definitions

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

There are no new terms defined in this specification.

2.5 Symbols and abbreviations

Here is a list of abbreviations and acronyms used in the data specification:

ABS Acrylonitrile butadiene styrene

AF Agricultural and aquaculture facilities (INSPIRE theme)
AM Area management/restriction/regulation zones and reporting units (INSPIRE theme)
BU Buildings (INSPIRE theme)
COFOG Classification of the Functions of Government
CPA Statistical Classification of Products by Activity in the EEC
CPVC Collapsed polyvinylchloride
CS Collective services (within COFOG)
DLC Digital loop carrier
DXC Digital cross connect
EEC European Economic Community
EIEL Enquiry on Local Infrastructures and Services (Spanish acronym for)
ESSPROS European System of integrated Social Protection Statistics
FIC Fiber interconnect
FRP Fibre reinforced plastic
GCM Generic Conceptual Model
GISCO Geographic Information System of the European Commission
GM Gravity main
GNM Generic Network Model
GPRS General packet radio service
GSM Global system for mobile communications
HDPE High density polyethylene
IHO International Hydrographic Organization
IMO International Maritime Organization
IS Individual services (within COFOG)
ISO International Organization for Standardization
LAN Local area network
LE Local exchange
LEC Local exchange carrier
LL Lateral line
MAN Metropolitan area network
MDF Main distribution frame
ML Main line
MS Member State
MUX Multiplexer
NACE Classification of Economic Activities in the European Community (French
acronym for)
NaN Node-Arc-Node
NEC or n.e.c. Not elsewhere classified (within COFOG)
ODF Optical distribution frame
OECD Organization for Economic Co-operation and Development
OH Overhead
OSPAR Oslo/Paris convention (for the Protection of the Marine Environment of the North-
East Atlantic)

18
The INSPIRE Glossary is available from [Link]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 9
PAB Public Administrative Body
PB Polybutylene
PE Polyethylene
PEX Cross-linked high-density polyethylene
PF Production and industrial facilities (INSPIRE theme)
PM Pressurized main
POI Point of interest
POTS Plain old telephone services
PP Polypropylene
PSTN Public switched telephone networks
PVC Polyvinylchloride
RPMP Reinforced polymer mortar
RR Radio-relay
S-100 IHO Hydrographic Geospatial Standard for Marine Data and Information
S-32 IHO International Hydrographic Dictionary
SCADA Supervisory control and data acquisition
SERIEE European System for the Collection of Economic Information on the Environment
(French acronym for)
SP Single-phase
TP Three-phase
UG Underground
UMTS Universal mobile telephone system
VPN virtual private network
WAN Wide area network
WFD Water Framework Directive (Directive 2000/60/EC of the European Parliament
and of the Council of 23 October 2000 establishing a framework for Community
action in the field of water policy)
WLAN Wireless local area network

2.6 Notation of requirements and recommendations

To make it easier to identify the mandatory requirements and the recommendations for spatial data sets
in the text, they are highlighted and numbered.

IR Requirement X Requirements that are reflected in the Implementing Rule on interoperability of

spatial data sets and services are shown using this style.

TG Requirement X Requirements that are not reflected in the Implementing Rule on interoperability
of spatial data sets and services are shown using this style.

Recommendation X Recommendations are shown using this style.

2.7 Conformance
TG Requirement 1 Any dataset claiming conformance with this INSPIRE data specification shall
pass the requirements described in the abstract test suite presented in Annex A.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 10

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
NOTE Since the content of this chapter was redundant with the overview description (section 2) and
executive summary, it has been decided that this chapter will be removed in v3.0.

5 Data content and structure

This data specification defines the following application schemas:

For Utility networks:

 The “Core Utility Networks Profile” application schemas are based on a node-arc-node
structure and network concept (derived from the Generic Network model). Especially designed to
describe data into a structured model with only the most basic characteristics, but adhering to the
node-arc-node concept (taken from the ―Network‖ concept in the GCM), respectively for the six
types of utility networks (electricity, oil-gas-chemicals, water, sewer, thermal and
telecommunications). Topology is not required being possible to represent networks as single
features not topologically interconnected (―spaghetti‖ representation)

 The “Extended Utility Networks” application schemas cannot be considered as accomplished

application schemas, since their development is at its first step and they are proposed in the
present document in Annex G only as leads for defining more-detailed standards later;

For Administrative and social governmental services:

 The “Core Administrative and Social Governmental Services” application schema that
provides information concerning the location and the type of administrative and social
governmental services;

 The “Extended Administrative and Social Governmental Services” application schema that
provides more detailed information concerning administrative and social governmental services
such as occupancy, resources and other specific descriptions;

For Environmental Management Facilities:

 The “Environmental Management Facilities” application schema that supports information

about waste treatment and storage practices, plus other environmental activities.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 11

Figure 2 – Organization of the different application schemas of the 3 sub-domains of the theme “Utility
and governmental services”

Narrative description and UML Overview

The INSPIRE theme Utility and governmental services has been split in 3 separate main application
schemas, that are developed hereafter.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 12
Though main features of the 3 sub-themes have common concepts related to the theme (such as
localization, technical description and responsible party), they were treated separately with different
modelization approaches within 3 nearly independent application schemas. This is principally due to the
observation that data providers and data users for each sub-theme are almost different.

It has also been decided to not apply a coverage / grid modelization at this stage of the development of
the data specification, due to the fact that such coverage, if existing, are more resulting of spatial analysis
outputs (e.g. access to telecommunication networks – GSM, 3G, etc.) than real spatial information (e.g.
position of antennas).

Next page is the UML diagram of these 3 application schemas.

Figure 3 – UML class diagram: Overview of the “Utility and governmental services” application
schema
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 13

Consistency between spatial data sets

The location of some Utility and governmental services features may be originally defined in the real
world relative to administrative, cadastral or natural boundaries (roads, rivers, walls, etc.). These
locations are initially similar to the position of a facility or a service (exact location of the networks
elements, or of a zone where some public service is provided), which may be known to exist up to a
natural or administrative feature. However, the INSPIRE Utility and governmental services data
specification represents such facilities or services as absolute, not relative geometries. That is, they
have their own, absolute geometries (as INSPIRE defined GM_Object or GM_MultiSurface) and their
geographical location is not dependent on other features (other than during their original delineation).
This is because many Member States do not update Utility and governmental services geometries if
there are changes to administrative or natural boundaries, and in any case, the official definition of a
Utility and governmental services remains fixed even if there are underlying changes to the
administrative boundary or the location of natural features.
For example, one can see that some underground networks can remain at the same position, even
after some road works.

On another hand, some other Utility and governmental services features do really share their
existence with other datasets (buildings, facilities described in other themes, like Production and
industrial facilities). For those elements, the location refers directly to the objects of those related
themes, so that if an instantiation of these supportive objects are deleted from a database, the service
object has to be deleted in cascade. That reflects the dependence in real world: if a governmental
service is provided in a building that is destroyed, then no more service is provided, or if a service is
provided for a certain aggregation of administrative units (such as intercommunality, or region), the
perimeter of responsibility will evolve with the new geometry of such administrative area, if modified.
In such case, the model refers directly to the objects (among the proposed location or area in the
union type, for example).

Identifier management

The Utility and governmental services data specification uses the Identifier DataType from the
INSPIRE General Conceptual Model [DS-D2.5]. These identifiers include version number, so can be
used to track changes to an object. The use of identifiers in combination with dates is described in
more detail in Section [Link].

Additional identifiers may also be represented with the Id attribute for Facility features or can be men-
tioned in the note attribute for GovenmentalServices. These attributes may be used to store some
specified identification reference, such as in national registers, but may also contain international
identifiers or other thematic identifiers, depending on the features.

Modelling of object references

According to the specific approach of the INSPIRE theme Utility and governmental services, some
features described in the model already exist as features in other thematic models.
EXAMPLE: Indeed, a school can be comprehended as a building, where several rooms are used as
classrooms, or as a governmental service dedicated to a certain amount of children, or as a service
provided by a PAB on a given regulated area (scholar districts) or also as an exposed element
regarding the natural risk zones.
Another example concerns an environmental facility that can be a place where waste (type, quantity) is
treated or stored, but also a specific activity allowed by an administrative permit, or also to a polluting
activity subjected delivering frequent reports.
All this information is developed in INSPIRE, but some is described within the scope of the theme
Utility and governmental services, some other in other scopes (e.g. 2. Buildings, 11. Area
management / restriction / regulation zones & reporting units, or 12 Natural risk zones)

When such objects are already defined (e.g. in Annex I data specifications) or because most of the
information required is produced and spread out, supported by a feature type from another model, the
Thematic Working Group on Utility and governmental services has chosen to use these objects, rather
than doubling feature types that support such information. This position implies that the sub-models
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 14

refer to external references, as described in the paragraph ―[Link]. Consistency between spatial data
sets‖.

Geometry representation

IR Requirement 1 The value domain of spatial properties used in this specification shall be
restricted to the Simple Feature spatial schema as defined by EN ISO 19125-
1.

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

The 3D modelization has been abandoned, at least for the basic or core profiles. In some extensions,
3D could be assessed, if needed.

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 EN ISO 19125-1).

Since the data concerned by the INSPIRE theme Utility and governmental services can be also
produced and used at a local level (according to many decentralization processes), the level of detail
should be important. In fact, description of a utility network or of services provided by or for a specific
Public Administrative Body will be rich in their geometries and attributes (large scale data, accurate
distinction between several services provided at local level).
This seems opposite to one goal of the INSPIRE directive, which is to gather similar data from different
producers and users, at a greater level (regional, national or European). Then, the level of details
described in the former paragraph is less important than collecting exhaustively the same type of data
for the whole territory analysed.
This data collection work is somehow developed by aggregating agencies (regional, national or pan-
European) and therefore may include some generalization processes, whether geometric or semantic.
Thus data can be simplified, as soon as they‘re used at a greater level, and the use of large scale data
at such greater levels can prove to be counterproductive. Then, if certain datasets are inappropriate to
be used at certain scales, it should be specified within its restrictions metadata.
On another hand, the different use cases (localization, management of services, spatial and semantic
analysis or reporting) implies different approaches and treatments of the data related to Utility and
governmental services.

Thus, the models proposed for the theme Utility and governmental services tend to be as simple as
possible and should fit to the use of such data at any scale (whether local or global). Nevertheless, the
level of detail (according to the scale and accuracy of the dataset) should be provided within the
metadata and data quality information.

Recommendation 1 All spatial objects should be provided at the source resolution where
possible.

Recommendation 2 If spatial objects are provided at different accuracies, the accuracy

should be specified for each spatial object using the attribute accuracy.

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.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 15

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".

Recommendation 1 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".

The beginLifespanVersion stores the date on which the data instance representing the features of the
Utility and Governmental Services theme was first created, and the endLifespanVersion is populated
when some attribute or geometry of that instance changes. At this point, an entirely new instance is
created repeating all of the attributes of the instance that have not changed, and providing new values
for the attributes or geometries that have changed. The new instance uses the same value for
[Link] and [Link], but has a new value for
[Link]. Using this method for representing temporality, all of the versions of features
of the Utility and Governmental Services theme can be established by looking for all the Utility and
Governmental Services instances with the same value for [Link] and
[Link].

The system dates can also be used for incremental updates. Instances that have been added since
the last update can be determined by finding instances whose beginLifespanVersion is after the date
of the last update. Instances that have been changed since the last update can be determined by
finding instances whose endLifespanVersion is after the date of the last update.

The Simple application schema does not include system lifecycle information and does not store
historical versions of features. The Full application schema includes full temporality and historical
versions.

IR Requirement 2 Spatial data sets related to the theme "Utility and governmental services" shall
be made available using the spatial object types and data types specified in
the following application schema(s):
• Core Utility Networks Profile (6 application schemas, 1 per type of
network);

• Core Administrative and Social Governmental Services;

• Environmental Management Facilities.

These spatial object types and data types shall comply with the definitions and
constraints and include the attributes and association roles defined in this
section.

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

NOTE The application schema specifies requirements on the properties of each spatial object
including its multiplicity, domain of valid values, constraints, etc. All properties have to be reported, if
the relevant information is part of the data set. Most properties may be reported as ―void‖, if the data
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 16

set does not include relevant information. See the Generic Conceptual Model [DS-D2.5] for more
details.

In addition to the application schemas listed in IR Requirement 2, additional application schemas have
been defined for the theme "Utility and governmental services". These additional application schemas
typically address requirements from specific (groups of) use cases and/or may be used to provide
additional information. They are included in this specification in order to improve interoperability also
for these additional aspects.

Recommendation 3 Additional and/or use case-specific information related to the theme "Utility
and governmental services" should be made available using the spatial
object types and data types specified in the following application
schema(s):
• Extended Utility Networks Profile (6 application schemas, 1 per type of
network – only provided as annex of the present document);
• Extended Administrative and Social Governmental Services

These spatial object types and data types should comply with the
definitions and constraints and include the attributes and association roles defined in this section.

5.1 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.1.1 Stereotypes
In the application schemas in this sections 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])

Model
Stereotype Description
element
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.
placeholder Class A class that acts as a placeholder for a class, typically a spatial
object type, that will be specified in the future as part of another
spatial data theme. The class should at least have a definition,
but may otherwise have a preliminary or no specification (see
section 5.1.2).
type Class A conceptual, abstract type that is not a spatial object type.
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.
enumeration Class A fixed list of valid identifiers of named literal values. Attributes
of an enumerated type may only take values from this list.
codeList Class A code list.
import Dependency The model elements of the supplier package are imported.
voidable Attribute, A voidable attribute or association role (see section 5.1.3).
association
role
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 17

lifeCycleInfo Attribute, If in an application schema a property is considered to be part

association of the life-cycle information of a spatial object type, the property
role shall receive this stereotype.
version Association If in an application schema an association role ends at a spatial
role 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.1.2 Placeholder and candidate types

Some of the INSPIRE Annex I data specifications (which were developed previously to the Annex II+III
data specifications) refer to types that were considered to thematically belong and which were
expected to be fully specified in Annex II or III spatial data themes. Two kinds of such types were
distinguished:

 Placeholder types were created as placeholders for types (typically spatial object types) that
were to be specified as part of a future spatial data theme, but which was already used as a
value type of an attribute or association role in this data specification.

Placeholder types received the stereotype «placeholder» and were placed in the application
schema package of the future spatial data theme where they thematically belong. For each
placeholder, a definition was specified based on the requirements of the Annex I theme. The
Annex II+III TWGs were required to take into account these definitions in the specification work
of the Annex II or III theme.

If necessary, the attributes or association roles in the Annex I data specification(s) that have a
placeholder as a value type shall be updated if necessary.

 Candidate types were types (typically spatial object types) for which already a preliminary
specification was given in the Annex I data specification. Candidate types did not receive a
specific stereotype and were placed in the application schema package of the future spatial data
theme where they thematically belong. For each candidate type, a definition and attributes and
association roles were specified based on the requirements of the Annex I theme. The Annex
II+III TWGs were required to take into account these specifications in the specification work of
the Annex II or III theme.

If the type could not be incorporated in the Annex II or III data specification according to its
preliminary specification, it should be moved into the application schema of the Annex I theme
where it had first been specified. In this case, the attributes or association roles in the Annex I
data specification(s) that have the type as a value type shall be updated if necessary.

NOTE Once the Annex II+III data specifications have been finalised by the TWGs (version 3.0), all
placeholders and candidate types should have been removed. In some cases, this may require one or
several of the Annex I data specifications (and the Implementing Rule on interoperability of spatial data
sets and services) to be updated.

5.1.3 Voidable characteristics

If a characteristic of a spatial object is not present in the spatial data set, but may be present or
applicable in the real world, the property shall receive this stereotype.

If and only if a property receives this stereotype, the value of void may be used as a value of the
property. A void value shall imply that no corresponding value is contained in the spatial data set
maintained by the data provider or no corresponding value can be derived from existing values at
reasonable costs, even though the characteristic may be present or applicable in the real world.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 18

It is possible to qualify a value of void in the data with a reason using the VoidValueReason type. The
VoidValueReason type is a code list, which includes the following pre-defined values:
 Unpopulated: The characteristic 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
characteristic receives this value for all 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 on an object-by-object
basis in a spatial data set.

NOTE It is expected 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, an 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. A value (the real value or void) only needs to
be made available for properties that have a minimum cardinality of 1.

5.1.4 Enumerations
Enumerations are modelled as classes in the application schemas. Their values are modelled as
attributes of the enumeration class using the following modelling style:
 No initial value, but only the attribute name part, is used.
 The attribute name conforms to the rules for attributes names, i.e. is a lowerCamelCase name.
Exceptions are words that consist of all uppercase letters (acronyms).

IR Requirement 3 Attributes of spatial object types or data types whose type is an enumeration
shall only take values included in the enumeration.

5.1.5 Code lists

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

[Link]. Obligation

For each attribute that has a code list as its value, a tagged value called ―obligation‖ is specified to
define the level of obligation to use values from the list. The tagged value can take the following
values:
 IR means that only the values defined by the code list shall be used for the attribute. This
obligation is also included in the Implementing Rule on interoperability of spatial data and
services.
 TG means that only the values defined by the code list should be used for the attribute. This
obligation is not included in the Implementing Rule on interoperability of spatial data and
services.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 19

IR Requirement 4 Attributes of spatial object types or data types whose type is a code list with
an ―obligation‖ value of ―IR‖ shall only take values that are valid according to
the code list‘s specification.

Recommendation 4 Attributes of spatial object types or data types whose type is a code list with
an ―obligation‖ value of ―TG‖ should only take values that are valid
according to the code list‘s specification.

[Link]. 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, which is managed and governed by the
INSPIRE expert group on maintenance and implementation. Change requests to these code
lists (e.g. to add, deprecate or supersede values) are processed and decided upon using the
maintenance workflows defined by the INSPIRE expert group.

INSPIRE-governed code lists will be made available in the INSPIRE code list register at
[Link] 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 [Link]

 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.

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.
 If the code list is versioned, the Version column specifies which version of the code list
shall be used in INSPIRE. The version can be specified using a version number or the
publication date of a version. The specification can also refer to the ―latest available
version‖.
 The Availability column specifies from where the values of the externally governed code
list are available, through a URL for code lists that are available online, or a citation for
code lists that are only available offline.
 In the Formats column the formats are listed, in which a code list is available. These can
be machine-readable (e.g. SKOS/RDF, XML) or human-readable (e.g. HTML, PDF).
 In some cases, for INSPIRE only a subset of an externally governed code list is relevant.
The subset is specified using the Subset column.
 For encoding values of externally governed code lists, rules have to be specified for
generating URI identifiers and labels for code list values. These are specified in a
separate table.

[Link]. 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
[Link]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 20

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}".

[Link]. Extensibility

For each code list, a tagged value called ―extensibility‖ is specified to define which additional values
(other than those explicitly specified) are allowed as valid values of the code list. The tagged value can
take the following values:
 none means that only the values explicitly specified shall / should be used for the attribute.
19

This obligation is also included in the Implementing Rule on interoperability of spatial data and
services.
 narrower means that only the values explicitly specified or values narrower than the specified
values shall / should be used for the attribute.
 any means that, in addition to the values explicitly specified, any other value may be used.

5.1.6 Choices of standard types

For harmonization reasons, it has been decided to prefer the use of standardized types in all
application schemas of the theme ―Utility and governmental services‖, rather than creating customized
types, even if these latter may have better fitted the constraints and requirements from each sub-
theme.

This approach is mainly conceptual, since some of the standards are still in discussions and not
consolidated (e.g. OM_Measurement). The standards concerned are:

Table 2 – Standard types used in US data specifications

Standard type Standard reference Comment
PT_FreeText ISO TC211. ISO 19139 Instead of any CharacterString type or open text
(Metadata - XML PT_FreeText type offers to allow translation in
Implementation) multiple languages of textual input, through a link
(type: 1 to many) to LocalisedCharacterString
Measure ISO TC211. ISO 19103:2005 Prefered to ISO 19156:2010 (Observations and
(Schema Language) Measurements) OM_Measurmement type, the
ISO 19103:2005 Measure type is systematically
used for all data providing information on a pair of
items (value + non-metric unit)
Length ISO TC211. ISO 19103:2005 Prefered to ISO 19156:2010 (Observations and
(Schema Language) Measurements) OM_Measurmement type, the
ISO 19103:2005 Length type is systematically
used for all data providing information on a pair of
items (value + metric unit in 2D)
Volume ISO TC211. ISO 19103:2005 Prefered to ISO 19156:2010 (Observations and
(Schema Language) Measurements) OM_Measurmement type, the
ISO 19103:2005 Length type is systematically
used for all data providing information on a pair of
items (value + metric unit in 3D)

19
It depends on the level of the ―obligation‖ tagged value on the attribute, whether this is a requirement
or recommendation.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 21

Originally the TWG has taken into account to reuse CI_ResponsibleParty (ISO TC211. ISO 19115
(Metadata - Corrigendum). Since both the definition of the data type itself and, more relevant, the
items and their definitions of the included code list CI_RoleCode do not match the needs of this
specification, it has been decided to define an own data type ―RelatedParty‖.

5.2 Application Schemas “Utility Networks”

5.2.1 General Description

Definition

Utility services and networks include the physical constructions for transport of utility products - namely
pipelines for transport of oil, gas, chemicals, water, sewage and thermal products – and cables for
transmission of electricity, phone and cable-TV signals, etc.

All kinds of utility systems have nodes like e.g. pump stations, and they are linked to facilities for
production and treatment of different kinds of utility products. These major production and treatment
sites are treated in the theme production and industrial facilities.

Description

It is acknowledged that each organization has different responsibilities and this will influence the kind
of data they collect, manage and use. Some organizations will use simple models while other will have
more complex data models.
This data specification is a basic framework that user can adopt and, if necessary, adapt and extend
for themselves. The specification is focused on the core spatial objects required by networks, i.e.
network centrelines etc.

Not all the application-specific spatial objects (e.g. flow measurement sensors) are incorporated. Non-
geographic data (e.g. information on flow in m3/s) is also out of scope of this specification.

Abstract

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 II and III themes. This is the
foundation model for every utility network – with the intention that any additional network may be
combined in future and used in a way that is predicable.

The scope of the INSPIRE Utility Networks Data Product Specification incorporates six distinct utility
themes:
 Water Network
 Sewer Network
 Electricity Network
 Oil, Gas & Chemicals Network
 Thermal Network
 Telecommunications (Excluded from the IRs)

Understanding of the Generic Conceptual Model is essential and the GCM/GNM should be read in
conjunction with this document. The GCM describes the basic form of real world abstraction. The GNM
adapts this and describes the basic concepts that underpin and define the common Utility Networks
Application Schema upon which all six themes are based. The GCM relies on ISO standards and the
19xxx series in particular.

Purpose
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 22

The purpose of this document is to specify a harmonized data specification for the spatial data theme
Utility Networks, being a sub-scope of the Utility and Governmental Services, as defined in Annex III of
the INSPIRE Directive.

This data specification is provided as basic framework that users can adopt and - if required – extend
for themselves. The model is structured to maximize reuse and the sharing of organizational data
about a network. The specification is concerned only with the core spatial objects required by Utility
Networks. This specification is mainly focused on the ―widely reused – widely referenced― segment of
spatial objects (e.g. utility pipes‘ centerlines, or utility node objects).

Associated “non-Geographic” data

Any ―non geographic data‖ (the majority of the data holdings in any organization) – is also out of scope
of this specification – such records maybe ―an asset condition report‖, ―flow report‖, ―images of assets‖,
―statistics‖ and so on. Therefore much of the data used in the utility industry is classified as 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 maximize reuse, the linkage of such organizational 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 be reused in several different applications and any associated information shared
and exchanged as desired.

Applications and use cases

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
 Estate management
 Flow modelling
 Maintenance

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 specification 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 standardization is necessary.

Characteristics of the specification

The key characteristics of the Utility Networks datasets are:

 They contain information of specific interest for the public sector in its role to support economic
growth through efficient utility networks (electricity, telecommunications, water, sewer, 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, e.g. telecommunications).
 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.

Spatial resolution and Topology

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 23

In the real world, objects are connected to each other: an optical cable is connected to a multiplexer
that in turn is connected to copper cables connecting into our homes to provide cable TV, telephony
and internet access. Using GIS to support network utility management typically involves many types of
features that may have connectivity to each other.
Topology in GIS is generally defined as the spatial relationship between connecting or adjacent
features, and is an essential prerequisite for many spatial operations such as network analysis. Utility
networks can be described as NaN (Node-Arc-Node) network using two basic geometric types: points
(aka nodes) and polylines (aka arcs). NaN topologies can be directed or un-directed, depending on
specific type of network (i.e. water networks are directed, while telecommunications networks are not).
Such topology structure provides an automated way to handle digitizing and editing errors, and enable
advanced spatial analyses such as adjacency, connectivity and containment. Infrastructure networks
rely on Generic network model developed during Annex I.

That being said, Utility Networks support single spatial resolution. Containment (e.g. equipment being
installed in manholes or on poles) is not taken in account as a different Level of Detail (LOD).

The topology or spatial relationships between utility network features can be defined explicitly by
referring nodes within links and vice versa. But this is an option and so is not mandatory.

According to the Generic Network Model, the relations between starting/ending nodes and links are
voidable, therefore these relationships can be provided if the source data already contains this
information, but if the source data doesn't contain this relationship information a data provider should
not be forced to provide them. In the latter case, such topology could be implicit if the source data is
sufficiently clean in which a users' application could construct such topology automatically.
Furthermore, the cardinality of the links is mentioned to be [0..1] or [0..*], so a dataset can be INSPIRE
compliant, even if containing no relation between links and nodes.

Color-coding used on model classes

In order to facilitate easier reading of the Utility Networks UML model, color-coding on the UML model
classes is used. This helps to visually recognize immediately the different kind of model classes.
With the color-coding we differentiate the abstract featureTypes, main and common featureTypes from
the Core Utility Networks Profile, featureTypes from Extended Utility Networks, codelists from Core
and from Extended Utility Networks. These are the assigned codes:
● default white (EA) for abstract featureTypes
● green for the common featureTypes
● red for the main featureTypes from a particular utility network
● yellow for the featureTypes of Extended
● grey for the codelists of the Core Utility Networks Profile
● dark grey for the codelist of Extended Utility Networks

Organisation of the diagrams

For the Core Utility Networks Profile there is on Common Application Schema that contains all the
common elements shared among thematic packages and ―applicationSchema‖ packages for each
utility network type (Electricity, Oil-Gas-Chemicals, Sewer, Thermal and Water) with one diagram for
each ―applicationSchema‖
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 24

The Core Abstract Types in the Core Utility Networks Profile inherit much from the generic Network
model from the GCM. The Core Utility Networks Profile can be used if a data provider has data
available based on a node-arc-node topological concept. The node-arc-node logic is represented in
the GCM using Node and Link featureTypes which contain associations in both directions. There are
two types of Link featureTypes, normal Link and LinkSequence, being a sequence with of directed
Links.

The Core Utility Networks Profile extends the Network LinkSequence, Link, Node and Network
featureTypes with respectively UtilityLinkSequence, UtilityLink, UtilityNode and UtilityNetwork
featureTypes.
The UtilityNodeContainer featureType has no counterpart in the generic Network model. This
UtilityNodeContainer featureType has a part-relationship with UtilityNode, indicating a utility container
object can contain many utility node objects.
The UtilityNetworkElement contains the properties that are common to all these abstract utility
featureTypes.
UtilityNetworkElement has two special properties for referencing features of other themes that are
related to the Utility Network (sub)theme. One is ―utilityFacilityReference‖ which references an
ActivityComplex featureType (from INSPIRE Base Models), which can be used to describe more
complex objects that are utility facilities having a more complex geometry. The other one is
―governmentalServiceReference‖ referencing a GovernmentalService feature (from Administrative and
social governmental services (sub) theme of INSPIRE US), which can be used to refer to
governmental service features that are conceptually related to utility network features.
The UtilityLinkSequenceOrLink featureType contains the properties that are common only to the
UtilityLinkSequence and UtilityLink featureTypes.

The Core Utility Network Profile - Core Abstract Types further contain two codelists that are used by
the two properties of the UtilityLinkSequenceOrLink featureType and two codelists from the INSPIRE
Base Types.

5.2.2 “Common Core Utility Networks Elements” application schema

[Link]. Description

[Link].1. Narrative description

The Core Common Types of the Core Utility Networks Profile contain the Cable, Pipe and Duct
featureTypes. These are link objects which can extend either the UtilityLinkSequence or UtilityLink
featureTypes.
These three featureTypes have various associations that can be used to model their real-life
relationships:
● A Duct can contain multiple other Ducts, e.g. in case the outer duct is a larger construction
containing multiple smaller ducts;
● A Duct can contain multiple Pipes, e.g. in case the duct acts as a protecting layer or as a
construction to keep the pipes together;
● A Duct can contain multiple Cables, idem as with the Duct-Pipe relationship;
● A Pipe can contain multiple other Pipes, e.g. in case the other pipe is used to keep a number
of inner pipes together;
● A Pipe can contain multiple Cables, idem as with the Pipe-Pipe relationship.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 25

Figure 4 – Physical relations between cables, pipes and ducts

Cable is an abstract featureType and can be used in the various utility themes by concrete
featureTypes (e.g. ElectricityCable).
Duct and Pipe on the other hand are not abstract, so this means that all utility themes can use the
Duct and Pipe featureTypes as concrete featureTypes as part of their concrete utility network (e.g.
ElectricityNetwork can have ElectricityCables and Ducts). Hence Duct and Pipe are here color-coded
in green. Furthermore, Duct and Pipe can be used in utility networks that we call ―crossTheme‖. This
means that we can have a cross-theme utility networks with ducts and pipes that are used to encase
cables and pipes from other utility network themes.

Cable, Pipe and Duct inherit from the abstract UtilityLinkSequenceOrLink featureType, but a constraint
has been put on the Duct featureType indicating that the utilityDeliveryType property cannot be used
in a Duct. This utilityDeliveryType property indicates that a link object is used in e.g. transport or
distribution type of utility networks. But a Duct can contain link objects from more than one specific
utility network them, it should not use this property, which is expressed by the constraint.

The UtilityNetwork featureType has a property ―utilityNetworkType‖ with a codelist

―UtilityNetworkTypeValue‖ that describe the kind of utility network. Note that there‘s also a
―crossTheme‖ utility network type that can be used for ducts and pipes for encasing of cables and
pipes from other utility networks.
The UtilityNetwork featureType has a reflexive association, meaning a utility network can contain other
networks. A UtilityNetwork has a number of authorities with different roles, but these roles can be
different for certain parts of a utility network. This reflexive association allows to model this case by
having a main utility network with several sub networks, each having different organisations - modelled
using the RelatedParty data type (from INSPIRE Basic Types 2) - fulfilling the authority roles.
The UtilityNetwork featureType also uses the ―utilityFacilityReference‖ property to allow to
conceptually include a utility facility in a utility network.

There are four utility node container objects, indicated as green color-coded featureTypes, meaning
they are concrete and can be used in all utility networks: Manhole, Tower, Pole and Cabinet.

Finally there is the Appurtenance featureType which has the ―appurtenanceType‖ property and a
hierarchy of codelists that can be used for values. The lowest level of codelists are codelists with the
base values we provide in our data specification, but these can be extended for application specific
purposes.

[Link].2. UML Overview

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 26

class Core Utility Networks Profile - Core Abstract Typ...

Generic Network Model (from GCM)

«featureType»
Network::NetworkElement +inNetwork «featureType»
«voidable» Network::Network
+ inspireId: Identifier [0..1]
«lifeCycleInfo, voidable» 0..* 1..* «voidable»
+ beginLifespanVersion: DateTime +elements + geographicalName: GeographicalName [0..*]
+ endLifespanVersion: DateTime [0..1]

«featureType» «dataType»
Network:: Network::
GeneralisedLink DirectedLink
+ direction: Sign
+link 10..*
+spokeStart
+startNode
«featureType» «voidable»
«featureType» «featureType»
Network::Link 0..* 0..1
Network::LinkSequence Network::Node
+ centrelineGeometry: GM_Curve
+ link: DirectedLink [1..*] {ordered} + geometry: GM_Point
+ fictitious: Boolean = false
0..*
+spokeEnd 0..1
«voidable» +endNode

«featureType» «featureType» «featureType» +nodes

UtilityLinkSequence UtilityLink UtilityNode «voidable»

0..*
constraints constraints constraints
{All components belong to same utility network} {All objects have inspireId} {All objects have inspireId}
{All objects have inspireId}

«featureType»
UtilityNetworkElement
«featureType»
UtilityLinkSequenceOrLink «voidable»
+ currentStatus: ConditionOfFacilityValue
«featureType»
«voidable» + validFrom: DateTime
UtilityNodeContainer
+ utilityDeliveryType: UtilityDeliveryTypeValue [0..1] + validTo: DateTime
+ warningType: WarningTypeValue + verticalPosition: VerticalPositionValue + geometry: GM_Point
+ utilityFacilityReference: ActivityComplex [0..1]
+ governmentalServiceReference: GovernmentalService [0..1] constraints
«codeList» {All objects have inspireId}
UtilityDeliveryTypeValue
«codeList»
Base Types:: «enumeration»
ConditionOfFacilityValue Base Types::
VerticalPositionValue
+ disused
«codeList» + functional onGroundSurface
WarningTypeValue + projected suspendedOrElevated
+ underConstruction underground

Figure 5 – UML class diagram: Overview of the “Core Utility Networks Profile - Core Abstract
Types”
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 27

class Core Utility Networks Profile - Core Common Typ...

UtilityNetwork Element «featureType»

«featureType» Network::Network
UtilityLinkSequenceOrLink
«voidable»
«voidable» + geographicalName: GeographicalName [0..*]
+ utilityDeliveryType: UtilityDeliveryTypeValue [0..1]
+ warningType: WarningTypeValue

«featureType»
«featureType» +cables «featureType» +pipes «featureType»
Duct
Cable «voidable» Pipe UtilityNetwork
«voidable»
0..* «voidable» 0..* + utilityNetworkType: UtilityNetworkTypeValue
+ ductWidth: Length
+ pipeDiameter: Measure + authorityRole: RelatedParty [1..*]
+ pressure: Measure [0..1] constraints «voidable»
0..*
+cables +pipes {"Duct" shall not have a "utilityDeliveryType"}
+ducts + utilityFacilityReference: ActivityComplex [0..*]
«voidable» «voidable» «voidable» + disclaimer: PT_FreeText [0..*]
0..* 0..*
constraints
{All objects have inspireId}
{"telecommunications" value of "utilityNetworkType" is not in IR}
+nodes
«voidable» Node +networks
UtilityNetwork Element UtilityNetwork Element «voidable»
0..*
«featureType» «featureType» 0..*
UtilityNodeContainer UtilityNode
+ geometry: GM_Point

«featureType» «featureType» «featureType» «featureType»

«codeList»
Manhole Tower Pole Cabinet
UtilityNetworkTypeValue
«voidable» «voidable» «featureType» + electricity
+ towerHeight: Length + poleHeight: Length Appurtenance + oilGasChemicals
+ sewer
+ appurtenanceType: AppurtenanceTypeValue
+ water
constraints + thermal
«codeList» {"TelecommunicationsAppurtenanceTypeValue" is not in IR} + telecommunications [0..1]
AppurtenanceTypeValue + crossTheme

{complete
{complete {complete
«codeList» {complete
{complete {complete
Core Oil-Gas-Chemicals Network::
OilGasChemicalsAppurtenanceTypeValue «codeList» «codeList»
Core Water Network:: Core Thermal Network::
WaterAppurtenanceTypeValue ThermalAppurtenanceTypeValue

«codeList»
Core Sewer Network::
SewerAppurtenanceTypeValue

«codeList»
Core Telecommunications Network::
«codeList» TelecommunicationsAppurtenanceTypeValue
Core Electricity Network::
ElectricityAppurtenanceTypeValue

Figure 6 – UML class diagram: Overview of the “Core Utility Networks Profile - Core Common Types”
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 28

[Link].3. Consistency between spatial data sets

Nothing more than what‘s written in the general paragraph.

[Link].4. Identifier management

Nothing more than what‘s written in the general paragraph.

[Link].5. Modelling of object references

Nothing more than what‘s written in the general paragraph.

[Link].6. Geometry representation

There are two types of geometry in the Core specification:

a) Centreline objects in Utility Networks

b) Point objects in Utility Networks

Type (b) are network nodes, but can also be used to associate appurtenances with the network (e.g.
antenna, pump, treatment plant etc).

Levels of detail: The specification addresses the highest resolution of data capture in Utility 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.

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
lever or disaggregated as the user increases the resolution.

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 focused on establishing a more coherent approach to those datasets that are
universally used, probably held at regional and local level and at the highest resolution within this
context.

Seamless resolution representations at the local and regional level

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 (SCADA), planning and
policy making.

In the meantime this specification applies to all levels of detail, although data providers are
encouraged to introduce this specification at the local level as a priority.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 29

Recommendation 5 All Utility Networks spatial objects should be provided at the source resolution
and accuracy where possible.

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

IR Requirement 5 The value domain of spatial properties used in this specification shall be
restricted to the Simple Feature spatial schema as defined by EN ISO
19125-1.

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

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 EN ISO 19125-1).

[Link].7. Temporality representation

Nothing more than what‘s written in the general paragraph.

[Link]. Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Common Core Utility Network Elements
Scope Common Core Utility Network Elements
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Common Core Utility Network Elements
Types defined in the feature catalogue

Type Package Stereotypes Section

Appurtenance Common Core Utility Network «featureType» [Link].1.1
Elements
AppurtenanceTypeValue Common Core Utility Network «codeList» [Link].2.1
Elements
Cabinet Common Core Utility Network «featureType» [Link].1.2
Elements
Cable Common Core Utility Network «featureType» [Link].1.3
Elements
Duct Common Core Utility Network «featureType» [Link].1.4
Elements
Manhole Common Core Utility Network «featureType» [Link].1.5
Elements
Pipe Common Core Utility Network «featureType» [Link].1.6
Elements
Pole Common Core Utility Network «featureType» [Link].1.7
Elements
Tower Common Core Utility Network «featureType» [Link].1.8
Elements
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 30

Type Package Stereotypes Section

UtilityDeliveryTypeBaseValue Common Core Utility Network «codeList» [Link].2.2
Elements
UtilityDeliveryTypeValue Common Core Utility Network «codeList» [Link].2.3
Elements
UtilityLink Common Core Utility Network «featureType» [Link].1.9
Elements
UtilityLinkSequence Common Core Utility Network «featureType» [Link].1.10
Elements
UtilityLinkSequenceOrLink Common Core Utility Network «featureType» [Link].1.11
Elements
UtilityNetwork Common Core Utility Network «featureType» [Link].1.12
Elements
UtilityNetworkElement Common Core Utility Network «featureType» [Link].1.13
Elements
UtilityNetworkTypeValue Common Core Utility Network «codeList» [Link].2.4
Elements
UtilityNode Common Core Utility Network «featureType» [Link].1.14
Elements
UtilityNodeContainer Common Core Utility Network «featureType» [Link].1.15
Elements
WarningTypeBaseValue Common Core Utility Network «codeList» [Link].2.5
Elements
WarningTypeValue Common Core Utility Network «codeList» [Link].2.6
Elements
[Link].1. Spatial object types
Appurtenance
Appurtenance
Name: appurtenance
Subtype of: UtilityNode
Definition: An appurtenance is a node object that is described by its type (via the attribute
"appurtenanceType").
Description: The "appurtenanceType" attribute uses the "AppurtenanceTypeValue" codelist
for its values. But this is an empty codelist that needs to be extended by a
concrete codelist of appurtenance types for each utility network type.
So e.g. for the electricity network, the "ElectricityAppurtenanceTypeValue"
codelist should be used.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: appurtenanceType

Name appurtenance type value

Value type: AppurtenanceTypeValue
Definition: Appurtenance types defined by the "AppurtenanceTypeValue" codelist.
Description: The "AppurtenanceTypeValue" codelist is an abstract codelist that can be
replaced by the various appurtenance type value codelists for each utility
network.
Multiplicity: 1
Obligation: Implementing Rule (requirement)
Constraint: "TelecommunicationsAppurtenanceTypeValue" is not in IR
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 31

Appurtenance
Natural
language:

Cabinet
Cabinet
Name: cabinet
Subtype of: UtilityNodeContainer
Definition: Simple cabinet object which may carry utility objects belonging to either single or
multiple utility networks.
Description: Cabinets represent mountable node objects that can contain smaller utility
devices and cables.
Status: Proposed
Stereotypes: «featureType»
Identifier: null

Cable
Cable (abstract)
Name: cable
Subtype of: UtilityLinkSequenceOrLink
Definition: A utility link or link sequence used to convey electricity or data from one location
to another.
Status: Proposed
Stereotypes: «featureType»
Identifier: null

Duct
Duct
Name: duct
Subtype of: UtilityLinkSequenceOrLink
Definition: A utility link or link sequence used to protect and guide cable and pipes via an
encasing construction.
Description: A Duct (or Conduit, or Duct-bank, or Wireway) is a linear object which belongs to
the structural network. It is the outermost casing. A Duct may contain Pipe(s),
Cable(s) or other Duct(s).
Duct is a concrete feature class that contains information about the position and
characteristics of ducts as seen from a manhole, vault, or a cross section of a
trench and duct.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: ductWidth

Name duct width

Value type: Length
Definition: The width of the duct.
Description: The measurement of the object - in this case, the duct - from side to side.
Multiplicity: 1
Stereotypes: «voidable»
Association role: cables

Value type: Cable

Definition: A duct may contain one or more cables.
Multiplicity: 0..*
Stereotypes: «voidable»
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 32

Duct
Association role: ducts

Value type: Duct

Definition: A single duct or set of ducts that constitute the inner-duct.
Multiplicity: 0..*
Stereotypes: «voidable»
Association role: pipes

Value type: Pipe

Definition: The set of pipes that constitute the duct bank.
Multiplicity: 0..*
Stereotypes: «voidable»
Constraint: "Duct" shall not have a "utilityDeliveryType"

Natural The multiplicity of "utilityDeliveryType" shall be 0

language:
OCL: inv: utilityDeliveryType->size()=0

Manhole
Manhole
Name: manhole
Subtype of: UtilityNodeContainer
Definition: Simple container object which may contain either single or multiple utility
networks objects.
Description: Manholes perform following functions:

 Provide drainage for the conduit system so that freezing water does not
damage the conduit or wires.

 Provide a location for bending the conduit run without damaging the
wires.

 Provide a junction for conduits coming from different directions.

 Provide access to the system for maintenance.

Status: Proposed
Stereotypes: «featureType»
Identifier: null

Pipe
Pipe
Name: pipe
Subtype of: UtilityLinkSequenceOrLink
Definition: A utility link or link sequence for the conveyance of solids, liquids, chemicals or
gases from one location to another. A pipe can also be used as an object to
encase several cables (a bundle of cables) or other (smaller) pipes.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: pipeDiameter
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 33

Pipe
Name pipe diameter
Value type: Measure
Definition: Pipe outer diameter.
Description: For convex shaped objects (e.g. a circle) the diameter is defined to be the largest
distance that can be formed between two opposite parallel lines tangent to its
boundery.
Multiplicity: 1
Stereotypes: «voidable»
Attribute: pressure

Name pressure
Value type: Measure
Definition: The maximum allowable operating pressure at which a product is conveyed
through a pipe.
Description: The unit of measure for pressure is commonly expressed in "bar".
Multiplicity: 0..1
Stereotypes: «voidable»
Association role: cables

Value type: Cable

Definition: A pipe may contain one or more cables.
Multiplicity: 0..*
Stereotypes: «voidable»
Association role: pipes

Value type: Pipe

Definition: A pipe may contain one or more pipes.
Multiplicity: 0..*
Stereotypes: «voidable»

Pole
Pole
Name: pole
Subtype of: UtilityNodeContainer
Definition: Simple pole (mast) object which may carry utility objects belonging to either
single or multiple utility networks.
Description: Poles represent node objects that can support utility devices and cables.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: poleHeight

Name pole height

Value type: Length
Definition: The height of the pole.
Description: The height is the vertical extend measuring accross the object - in this case, the
pole - at right angles to the lenght.
Multiplicity: 1
Stereotypes: «voidable»

Tower
Tower
Name: tower
Subtype of: UtilityNodeContainer
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 34

Tower
Definition: Simple tower object which may carry utility objects belonging to either single or
multiple utility networks.
Description: Towers represent node objects that support reservoirs, cables or antennas.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: towerHeight

Name tower height

Value type: Length
Definition: The height of the tower.
Description: The height is the vertical extend measuring accross the object - in this case, the
tower - at right angles to the lenght.
Multiplicity: 1
Stereotypes: «voidable»

UtilityLink
UtilityLink (abstract)
Name: utility link
Subtype of: Link, UtilityLinkSequenceOrLink
Definition: A linear spatial object that describes the geometry and connectivity of an utility
network between two points in the network. Utility links may represent pipes,
ducts, cables, etc.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Constraint: All objects have inspireId

Natural All utility links have an external object identifier.

language:
OCL: inv:inspireId->notEmpty()

UtilityLinkSequence
UtilityLinkSequence (abstract)
Name: utility link sequence
Subtype of: LinkSequence, UtilityLinkSequenceOrLink
Definition: A linear spatial object, composed of an ordered collection of utility links, which
represents a continuous path in an utility network without any branches
(monotone chain). The element has a defined beginning and end and every
position on the utility link sequence is identifiable with one single parameter such
as length. It describes an element of the utility network, characterized by one or
more thematic identifiers and/or properties.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Constraint: All components belong to same utility network

Natural An utility link sequence must be composed of utility links that all belong to the
language: same utility network.
OCL: inv: link->forAll(l | [Link] = [Link])
Constraint: All objects have inspireId

Natural All utility link sets have an external object identifier.

language:
OCL: inv:inspireId->notEmpty()
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 35

UtilityLinkSequenceOrLink
UtilityLinkSequenceOrLink (abstract)
Name: utility link sequence or link
Subtype of: UtilityNetworkElement
Definition: An abstract utility network class which groups common properties of
UtilityLinkSequence and UtilityLink.
Description: This class allows Cable, Pipe and Duct classes to use either the
UtilityLinkSequence or UtilityLink class as class from which they can be
extended.
This means that data providers have the choice to use the more complex
UtilityLinkSequence or the more simple UtilityLink.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: utilityDeliveryType

Name utility delivery type

Value type: UtilityDeliveryTypeValue
Definition: Kind of utility delivery network e.g. transport, distribution, collection ...
Multiplicity: 0..1
Stereotypes: «voidable»
Obligation: Implementing Rule (requirement)
Attribute: warningType

Name warning type

Value type: WarningTypeValue
Definition: Kind of overground visible warning mechanism used to indicate an underground
utility network element.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Implementing Rule (requirement)

UtilityNetwork
UtilityNetwork
Name: utility network
Subtype of: Network
Definition: Collection of network elements that belong to a single type of utility network.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 36

UtilityNetwork
Description: In the real world, objects are connected to each other: an optical cable is
connected to a multiplexer that in turn is connected to copper cables connecting
into our homes to provide cable TV, telephony and internet access. Using GIS to
support network utility management typically involves many types of features that
may have connectivity to each other. Topology in GIS is generally defined as the
spatial relationship between connecting or adjacent features, and is an essential
prerequisite for many spatial operations such as network analysis. Utility
networks can be described as NaN (Node-Arc-Node) network using two basic
geometric types: points (aka nodes) and polylines (aka arcs). NaN topologies
can be directed or un-directed, depending on specific type of network (i.e. water
networks are directed, while telecommunications networks are not). Such
topology structure provides an automated way to handle digitising and editing
errors, and enable advanced spatial analyses such as adjacency, connectivity
and containment. Infrastructure networks rely on Generic network model
developed during Annex I.

Note:
Via the attribute "utilityNetworkType", that uses the "UtilityNetworkTypeValue"
codelist, the type of utility network can be defined. E.g. by selecting the "sewer"
value, the utility network becomes a "sewer utility network".
Using the "crossTheme" value, a utility network can be created that contains e.g.
ducts, which can contain pipes and cables from various utility network types.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: utilityNetworkType

Name utility network type

Value type: UtilityNetworkTypeValue
Definition: The type of utility network or the utilily network theme.
Description: Uses the codelist "UtilityNetworkTypeValue" to describe the possible utility
networks. This also contains the "crossTheme" value to be used for utility
networks that can contain cables or pipes from various themes, typically used by
utility network providers that provide ducts.
Multiplicity: 1
Obligation: Implementing Rule (requirement)
Attribute: authorityRole

Name authority role

Value type: RelatedParty
Definition: Parties authorized to manage a utility network, such as maintainers, operators or
owners.
Multiplicity: 1..*
Attribute: utilityFacilityReference

Name utility facility reference

Value type: ActivityComplex
Definition: Reference to a facility activity complex that is linked to (e.g. part of) this utility
network.
Description: This reference can be used to link utility facilities - having a more complex
geometry - to a utility network.
Multiplicity: 0..*
Stereotypes: «voidable»
Attribute: disclaimer

Name disclaimer
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 37

UtilityNetwork
Value type: PT_FreeText
Definition: Legal text describing confidentiality clauses applying to the utility network
information.
Multiplicity: 0..*
Stereotypes: «voidable»
Association role: networks

Value type: UtilityNetwork

Definition: A single sub-network that can be considered as part of a higher-order utility
network.
Multiplicity: 0..*
Stereotypes: «voidable»
Constraint: "telecommunications" value of "utilityNetworkType" is not in IR

Natural The multiplicity of "telecommunications" shall be 0

language:
OCL: inv: telecommunications->size()=0
Constraint: All objects have inspireId

Natural All utility nodes have an external object identifier.

language:
OCL: inv:inspireId->notEmpty()

UtilityNetworkElement
UtilityNetworkElement (abstract)
Name: utility network element
Definition: Abstract base type representing an utility network element in an utility network.
Every element in an utility network provides some function that is of interest in
the utility network.
Description: NOTE Derived 'views' of real-world utility objects are represented through
specialisations in other application schemas; all representations of the same
real-world object share a common geographic name.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: currentStatus

Name current status

Value type: ConditionOfFacilityValue
Definition: The status of an utility object with regards to its completion and use.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Implementing Rule (requirement)
Attribute: validFrom

Name valid from

Value type: DateTime
Definition: The time when the utility network element started to exist in the real world.
Multiplicity: 1
Stereotypes: «voidable»
Attribute: validTo

Name valid to
Value type: DateTime
Definition: The time from which the utility network element no longer exists in the real world.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 38

UtilityNetworkElement (abstract)
Multiplicity: 1
Stereotypes: «voidable»
Attribute: verticalPosition

Name vertical position

Value type: VerticalPositionValue
Definition: Vertical position of the utility object relative to ground.
Multiplicity: 1
Stereotypes: «voidable»
Attribute: utilityFacilityReference

Name utility facility reference

Value type: ActivityComplex
Definition: Reference to a facility activity complex that is linked (related) to this utility
network element.
Description: This reference can be used to link a utility facility - having a more complex
geometry - to a utility network element.
Multiplicity: 0..1
Stereotypes: «voidable»
Attribute: governmentalServiceReference

Name governmental service reference

Value type: GovernmentalService
Definition: Reference to a governmental service object that is linked (related) to this utility
network element.
Description: This reference can be used to link a governmental service object to a utility
network element.
Multiplicity: 0..1
Stereotypes: «voidable»

UtilityNode
UtilityNode (abstract)
Name: utility node
Subtype of: Node, UtilityNetworkElement
Definition: A point spatial object which is used for connectivity.
Description: Nodes are found at both ends of the UtilityLink.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Constraint: All objects have inspireId

Natural All utility nodes have an external object identifier.

language:
OCL: inv:inspireId->notEmpty()

UtilityNodeContainer
UtilityNodeContainer (abstract)
Name: utility node container
Subtype of: UtilityNetworkElement
Definition: A point spatial object which is used for connectivity, and also may contain other
spatial objects (not neccessarily belonging to the same utility network).
Description: Nodes are found at either end of the UtilityLink.
Status: Proposed
Stereotypes: «featureType»
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 39

UtilityNodeContainer (abstract)
Identifier: null
Attribute: geometry

Name geometry
Value type: GM_Point
Definition: Location of the utility node container.
Multiplicity: 1
Association role: nodes

Value type: UtilityNode

Definition: Contained utility nodes.
Multiplicity: 0..*
Stereotypes: «voidable»
Constraint: All objects have inspireId

Natural All utility nodes have an external object identifier.

language:
OCL: inv:inspireId->notEmpty()

[Link].2. Code lists

AppurtenanceTypeValue
AppurtenanceTypeValue
Name: appurtenance type value
Definition: Codelist containing a classification of appurtenances.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

UtilityDeliveryTypeBaseValue
UtilityDeliveryTypeBaseValue
Name: utility delivery type base value
Subtype of: UtilityDeliveryTypeValue
Definition: Codelist containing a base classification of utility delivery types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

UtilityDeliveryTypeValue
UtilityDeliveryTypeValue
Name: utility delivery type value
Definition: Codelist containing a classification of utility delivery types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

UtilityNetworkTypeValue
UtilityNetworkTypeValue
Name: utility network type value
Definition: Codelist containing a classification of utility network types.
Status: Proposed
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 40

UtilityNetworkTypeValue
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

WarningTypeBaseValue
WarningTypeBaseValue
Name: warning type base value
Subtype of: WarningTypeValue
Definition: Codelist containing a base classification of warning types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

WarningTypeValue
WarningTypeValue
Name: warning type value
Definition: Codelist containing a classification of warning types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

[Link].3. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

ActivityComplex
ActivityComplex
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Activity Complex::Activity Complex Core [Include reference to the
document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: A single unit, both technically and economically, under the management control
of the same legal entity (operator), covering activities as those listed in the
Eurostat NACE classification, products and services. Activity Complex includes
all infrastructure, equipment and materials. It must represent the whole area, at
the same or different geographical location, managed by a "single unit" as it has
been previously described.
Description: NOTE 1 This class describes the minimal set of elements necessary to describe
and identify geographically a legal entity and the activities taken place on it under
the context of a Environmental purposes.

NOTE 2 "Activity Complex" could be assimilated to terms described on the

legislation as Facility, Establishment, Plant, Holding, Organization ,Farm,
Extractive Industries or Aquaculture Production Business among others

EXAMPLE i.e. an Agro-business that is legally registered under the Emissions

Directive.

ConditionOfFacilityValue
ConditionOfFacilityValue
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 41

ConditionOfFacilityValue
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Types::Base Types [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: The status of a facility with regards to its completion and use.

DateTime
DateTime
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Primitive::Date and Time [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

GM_Point
GM_Point
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19107:2003 Spatial Schema:: Geometry::Geometric primitive [Include reference
to the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]

GovernmentalService
GovernmentalService
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::
AdministrativeAndSocialGovernmentalServices::ExtensionAdministrativeAndSoci
alGovernmentalServices [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Administrative and social governmental services provided by, or on behalf of, a
Public Administrative Body, in order to be used in the treatment of environmental
issues (broad meaning) for public use or to the benefit of citizens
Description: Administrative and social governmental services such as public administrations,
civil protection, sites, schools, hospitals. The kinds of sites are commonly
presented in governmental and municipal portals and map system as "point of
interest"-data, and may be point-based location of a variety of categories of
municipal and governmental services and social infrastructure

Length
Length
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

Link
Link (abstract)
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Network [Include reference to the document that includes the package,
e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Curvilinear network element that connects two positions and represents a
homogeneous path in the network. The connected positions may be represented
as nodes.

LinkSequence
LinkSequence (abstract)
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Network [Include reference to the document that includes the package,
e.g. INSPIRE data specification, ISO standard or the GCM]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 42

LinkSequence (abstract)
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.

Measure
Measure
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Production and Industrial
Facilities::ProductionAndIndustrialFacilitiesExtension [Include reference to the
document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: Declared or measured quantity of any kind of physical entity.

Measure
Measure
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

Network
Network
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Network [Include reference to the document that includes the package,
e.g. INSPIRE data specification, ISO standard or the GCM]
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)

Node
Node (abstract)
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Network [Include reference to the document that includes the package,
e.g. INSPIRE data specification, ISO standard or the GCM]
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]

PT_FreeText
PT_FreeText
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19139 Metadata - XML Implementation::Cultural and linguistic adapdability
[Include reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

RelatedParty
RelatedParty
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Types::Base Types 2::Drafts - for x-TWG discussion::RelatedParty [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]
Definition: An organisation or a person with a role related to a resource.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 43

RelatedParty
Description: NOTE 1 A party, typically an individual person, acting as a general point of
contact for a resource can be specified without providing any particular role.

VerticalPositionValue
VerticalPositionValue
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Types::Base Types [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: The relative vertical position of a spatial object.

[Link]. INSPIRE-governed code lists for the “Common Core Utility Network
Elements”

[Link].1. Values of code list UtilityNetworkTypeValue

Value Name Definition

electricity Electricity Electricity Networks
oilGasChemical OilGasChemical Oil Gas or Chemical Networks
sewer Sewer Sewer Networks
water Water Water Networks
thermal Thermal Thermal Networks
Telecommunications Telecommunications Telecommunications Networks

[Link].2. Values of code list UtilityDeliveryTypeBaseValue

Value Name Definition

collection Collection To describe a type of utility network delivering it‘s utility product
via collection (e.g. for sewer utility networks, collecting
sewer water from customers)
distribution Distribution To describe a type of utility network delivering it‘s utility product
via mainly local distribution (e.g. local distribution of electricity),
connecting directly to consumers
private Private To describe a type of utility network delivering it‘s utility product
via a small private network (e.g. owned by a private
company)
transport Transport To describe a type of utility network delivering it‘s utility product
via a large transport network (e.g. to convey oil-gas-
chemicals products over larger distances)

[Link].3. Values of code list WarningTypeBaseValue

Value Name Definition

net Net Warning net for protection of cables and pipes. Due to the mesh
size of the net an excavator will catch the net and so will warn
the excavator
tape Tape Caution tape (also known as warning tape) is a resilient plastic
tape of a signal colour or highly contrasting colour combination
(such as yellow-black or red-white).
concretePaving Concrete paving A set or paving of pavers or tiles in concrete material covering
cables or pipes.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 44

[Link]. Externally governed code lists for the “Common Core Utility Network
Elements”

Not externally governed code lists have been defined in this application schema.

5.2.3 “Core Electricity Network” application schema

[Link]. Description

[Link].1. Narrative Description

There are six diagrams in each application Schema for each specific utility network type of the Core
Utility Networks Profile:
● Core Electricity Network;
● Core Oil-Gas-Chemicals Network;
● Core Sewer Network;
● Core Telecommunications Network;
● Core Thermal Network;
● Core Water Network.

Core Electricity Network application schema is structured containing:

● One concrete link object extending from an abstract Cable or Pipe featureType (shown in red
color);
● One Appurtenance node object (green color) ;
● One UtilityNetwork object (green color);
● All codelists used by the featureType properties of this diagram (grey color):
○ Those used by the abstract UtilityLinkSequenceOrLink featureType properties;
○ Those used by the concrete cable or pipe and appurtenance featureType properties of
the specific utility network;
○ Those used by the ―appurtenanceType‖ property of the Appurtenance object;
○ The ―UtilityNetworkTypeValue‖ used by the ―utilityNetworkType‖ property of the
UtilityNetwork object..
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 45

[Link].2. UML Overview

class Core Electricity Netw...

UtilityNetwork Element Node «featureType»

«featureType» UtilityNetwork Element Network::Network
Common Core Utility Network Elements:: «featureType»
UtilityLinkSequenceOrLink Common Core Utility «voidable»
Network Elements:: + geographicalName: GeographicalName [0..*]
«voidable» UtilityNode
+ utilityDeliveryType: UtilityDeliveryTypeValue [0..1]
+ warningType: WarningTypeValue +networks
«voidable» 0..*

«featureType» «featureType»
«featureType»
Common Core Utility Common Core Utility Network Elements::UtilityNetwork
Common Core Utility Network Elements::Appurtenance
Network Elements::
+ utilityNetworkType: UtilityNetworkTypeValue
Cable + appurtenanceType: AppurtenanceTypeValue
+ authorityRole: RelatedParty [1..*]
constraints «voidable»
{"TelecommunicationsAppurtenanceTypeValue" is not in IR} + utilityFacilityReference: ActivityComplex [0..*]
+ disclaimer: PT_FreeText [0..*]
«featureType»
constraints
ElectricityCable
{All objects have inspireId}
«voidable» {"telecommunications" value of "utilityNetworkType" is not in IR}
+ operatingVoltage: Measure
+ nominalVoltage: Measure
«codeList»
Common Core Utility
Network Elements::
«codeList» AppurtenanceTypeValue «codeList»
Common Core Utility Network Common Core Utility Network
Elements:: Elements::
UtilityDeliveryTypeValue UtilityNetworkTypeValue
+ electricity
{complete
+ oilGasChemicals
+ sewer
+ water
«codeList» «codeList»
+ thermal
Common Core Utility Network Elements::UtilityDeliveryTypeBaseValue ElectricityAppurtenanceTypeValue
+ telecommunications [0..1]
+ collection + crossTheme
+ distribution
+ private
+ transport

tags «codeList»
asDictionary = true ElectricityAppurtenanceTypeBaseValue
extensibility = any
vocabulary = [Link] + capacitorControl
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions + connectionBox
+ correctingEquipment
+ deliveryPoint
+ dynamicProtectiveDevice
+ fuse
«codeList» + generator
Common Core Utility Network + loadTapChanger
Elements::WarningTypeValue + mainStation
+ netStation
+ networkProtector
+ openPoint
+ primaryMeter
+ recloserElectronicControl
+ recloserHydraulicControl
+ regulatorControl
«codeList» + relayControl
Common Core Utility Network Elements::WarningTypeBaseValue + sectionalizerElectronicControl
+ sectionalizerHydraulicControl
+ net
+ streetLight
+ tape
+ subStation
+ concretePaving
+ switch
tags + transformer
asDictionary = true + voltageRegulator
extensibility = any + detectionEquipment
vocabulary = [Link] + pointSettingMachine
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions + monitoringAndControlEquipment
+ anode

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 7 – UML class diagram: Overview of the “Core Electricity Networks”

[Link].3. Feature catalogue
Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Core Electricity Network

Scope Core Electricity Network
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Core Electricity Network
Types defined in the feature catalogue

Type Package Stereotypes Section

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 46

Type Package Stereotypes Section

ElectricityAppurtenanceTypeBaseValue Core Electricity Network «codeList» [Link].2.1
ElectricityAppurtenanceTypeValue Core Electricity Network «codeList» [Link].2.2
ElectricityCable Core Electricity Network «featureType» [Link].1.1
Spatial object types
ElectricityCable
ElectricityCable
Name: electricity cable
Subtype of: Cable
Definition: A utility link or link sequence used to convey electricity from one location to
another.
Status: Proposed
Stereotypes: «featureType»
Attribute: operatingVoltage

Name operating voltage

Value type: Measure
Definition: The utilization or operating voltage by the equipment using the electricity.
Multiplicity: 1
Stereotypes: «voidable»
Attribute: nominalVoltage

Name nominal voltage

Value type: Measure
Definition: The nominal system voltage at the point of supply.
Multiplicity: 1
Stereotypes: «voidable»

Code lists
ElectricityAppurtenanceTypeBaseValue
ElectricityAppurtenanceTypeBaseValue
Name: electricity appurtenance type base value
Subtype of: ElectricityAppurtenanceTypeValue
Definition: Codelist containing a base classification of electricity appurtenance types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
ElectricityAppurtenanceTypeValue
ElectricityAppurtenanceTypeValue
Name: electricity appurtenance type value
Subtype of: AppurtenanceTypeValue
Definition: Codelist containing a classification of electricity appurtenances.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.
AppurtenanceTypeValue
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 47

AppurtenanceTypeValue
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: Codelist containing a classification of appurtenances.
Cable
Cable (abstract)
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: A utility link or link sequence used to convey electricity or data from one location
to another.
Measure
Measure
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Production and Industrial
Facilities::ProductionAndIndustrialFacilitiesExtension [Include reference to the
document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: Declared or measured quantity of any kind of physical entity.

[Link]. INSPIRE-governed code lists for the “Core Electricity Networks”

[Link].1. Values of code list ElectricityAppurtenanceTypeBaseValue

Value Name Definition Description

Capacior control is usually done to achieve as
many as possible of the following goals: reduce
losses due to reactive load current, reduce kVA
capacitorCo capacitor Capacitor demand, decrease customer energy consumption,
ntrol Control control. improve voltage profile, and increase revenue.
Indirectly capacitor control also results in longer
equipment lifetimes because of reduced equipment
stresses.
connection Connectio Connection box protects and/or encloses electric
connection Box
Box n box. circuits and equipment on the ground.
Power distribution is more efficient if operated
when the power factor (PF) is unity. An alternating
Power voltage and the current causing it to flow should
factor rise and fall in value equally and reverse direction
correctingE correcting
correcting at the same instant. When this happens, the two
quipment Equipment
equipment waves are said to be in phase and the power factor
. is unity (1.0). However, various inductive effects,
such as idle running induction motors or
transformers, can lower the power factor.
deliveryPoi Delivery
delivery Point Point the electric power is being delivered to.
nt point.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 48

Value Name Definition Description

In addition to opening when a fault is detected,
dynamic protective devices also reclose to attempt
to re-establish service. If the fault remains after a
prescribed number of reclosings, the device may
dynamicPro dynamic Dynamic
lock open the circuit. Reclosing is designed to
tectiveDevic Protective protective
reduce or eliminate the effects of temporary faults.
e Device device.
NOTE It may include following subtypes: Circuit
Breakers,
Fault Interrupter, Reclosers (Single Phase
Hydraulic, etc.), and Sectionalizers.
Fuses are used to protect distribution devices from
damaging currents. A fuse is an intentionally
weakened spot in the electric circuit that opens the
circuit at a predetermined current that is maintained
fuse fuse Fuse. for a predetermined amount of time. Fuses are not
dynamic in that they remain open and do not
reclose. By automatically interrupting the flow of
electricity, a fuse prevents or limits damage caused
by an overload or short circuit.
Generator is an alternative, third-party power
generator generator Generator.
source feeding into the electrical network.
Load tap changer represents power transformer
controls that change the primary to-secondary turns
ratio of a transformer winding while the transformer
is under load to regulate the flow of current and
minimize voltage drop. Automatic loadtap changers
loadTapCh load Tap Load tap
in the power transformer provides voltage control
anger Changer changer.
on the substation bus. Control systems of voltage
regulators and tap changing equipment beyond the
substation usually have a line-drop compensator to
simulate voltage drop between the substation and
points in the distribution system.
Electric station represents a building or fenced-in
enclosure that houses the equipment that switches
and modifies the characteristics of energy from a
Main
mainStation main Station generation source. Distribution systems include
station.
primary feeders (circuits), transformer banks, and
secondary circuits (overhead or underground) that
serve a specified area.
Net
netStation net Station Net station.
station.
Network transformers connect to the secondary
network through a network protector. Network
protector components may be the circuit breaker,
networkProt network Network
relays, backup fuses and controls required for
ector Protector protector.
automatically disconnecting a transformer from the
secondary network in response to predetermined
conditions on primary feeder or transformer.
Open point contains information about a variety of
insulated and shielded devices that connect high-
voltage cables to apparatus, including
Open
openPoint open Point transformers. Separable, load-break insulated
point.
connectors are used with primary bushings of
submersible distribution transformers for safety.
This is known as a dead-front configuration.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 49

Value Name Definition Description

Primary meters are installed if commercial
customers elect to have power delivered at
distribution voltages, such as 12.5 kV. Residential
primaryMet Primary
primary Meter customers are generally billed for kilowatt hours
er meter.
(kWH) used. Commercial and industrial customers
may additionally be billed for demand charges and
power factor charges.
Reclosers and sectionalizers isolate temporary and
permanent faults in electric lines. Reclosers open
circuits (trip) in case of a fault, and reclose after a
recloserEle recloser Recloser predetermined time. The time-current
ctronicContr Electronic electronic characteristic, usually expressed in a curve, is
ol Control control. based on temperature and fuse tolerances and is
used to coordinate recloser operations. Reclosers
allow (usually) four trip operations to clear
temporary faults.
Recloser hydraulic control is an intregral part of
recloserHyd recloser Recloser single-phase reclosers. A trip coil in series with the
raulicContro Hydraulic hydraulic line is used to sense overcurrent and trip open the
l Control control. recloser contacts. The contacts close after a preset
interval.
Voltage provided by regulators is changed using a
tap-changing switch to adjust the number of
secondary windings. Line load can be regulated
regulatorCo regulator Regulator from 10 percent above to 10 percent below normal
ntrol Control control. line voltage. Voltage regulators that control
distribution system voltage are rated from 2.5 kV to
34.5 grd Y kV. Most feeder regulators have the 32-
step design.
Protective relay systems detect and isolate faults.
Time-delayed phase and ground relays are
coordinated with fuses and reclosers further out on
Relay the circuit. They are instantaneous units with
relayControl relay Control
control. inverse TCCs to coordinate with fuses and
reclosers further downstream. Relays are usually
set to trip feeder breakers and protect the fuse in
the event of temporary faults beyond the fuse.
Sectionalizers are automatic circuit opening
devices that are installed on the load side of fault-
interrupting devices and count its fault-trip
Sectionaliz
sectionalize sectionalizer operations. Sectionalizers can be set to open after
er
rElectronic Electronic one, two, or three counts have been detected
electronic
Control Control with a predetermined time span. Sectionalizers are
control.
used in conjunction with fuses and reclosers and
may have inrush current restraint features to
prevent a false count when lines are re-energized.
Sectionalizer controls store a pulse counter when
the minimum actuating current drops to zero
Sectionaliz
sectionalize sectionalizer because a fault is interrupted by the recloser (or
er
rHydraulicC Hydraulic other protective device). Sectionalizers operate in
hydraulic
ontrol Control conjunction with breakers and reclosers to lock out
control.
fault current after a predetermined number (usually
three) of recloser operations (trips).
A street light (or lamppost, street lamp, light
Street standard, or lamp standard) is a raised source of
streetLight street Light
light. light on the edge of a road, which is turned on or lit
at a certain time every night.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 50

Value Name Definition Description

An electrical substation is a subsidiary station of an
electricity generation, transmission and distribution
system where voltage is transformed from high to
low or the reverse using transformers. Electric
power may flow through several substations
Sub between generating plant and consumer, and may
subStation sub Station
station. be changed in voltage in several steps. A
substation that has a step-up transformer increases
the voltage while decreasing the current, while a
step-down transformer decreases the voltage while
increasing the current for domestic and commercial
distribution.
A switch disconnects circuits within the distribution
network and can be manually or power operated.
Switches are either open or closed. Switches are
critical to the electric distribution system to allow
switch switch Switch. current interruption to allow system maintenance,
redirecting current in case of emergency, or to
isolate system failures. Switches may be
automated and controlled remotely through SCADA
operation.
Transformers transfer electrical energy from one
circuit to another circuit usually with changed
values of voltage and current in the process.
Transform
transformer transformer
er. NOTE Subtypes include: Network, Single Phase
Overhead, Single Phase Underground, Two Phase
Overhead, Three Phase Overhead, Three Phase
Underground, Step, and Power.
Voltage regulators vary the ac supply or source
voltage to the customer to maintain the voltage
within desired limits. Voltage provided by regulators
is changed using a tap-changing switch to adjust
the number of secondary windings. Bypass
voltageReg voltage Voltage switches allow a regulator to be removed for
ulator Regulator regulator. normal service without interrupting the downstream
load.

NOTE Subtypes include: Single Phase Overhead,

Two Phase Overhead, Three Phase Overhead,
Three Phase Pad-Mounted.
detectionEq detection
uipment Equipment
pointSetting point Setting
Machine Machine
monitoringA monitoring And
ndControlE Control
quipment Equipment
[Link]. Externally governed code lists for the “Core Electricity Networks”

ElectricityAppertunanceTypeValue code lists included in the “Electricuty Networks” application

schemas is empty and can be extensible by any external codelist. The
ElectricityAppertunanceTypeBaseValue is an internal code list which is also extended from the empty
ElectricityAppertunanceTypeValue code list.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 51

5.2.4 “Core Oil-Gas-Chemicals Network” application schema

[Link]. Description

[Link].1. Narrative Description

Core Oil-Gas-Chemicals Network application schema is structured containing:

● One concrete link object extending from an abstract Cable or Pipe featureType (shown in red
color);
● One Appurtenance node object (green color) ;
● One UtilityNetwork object (green color);
● All codelists used by the featureType properties of this diagram (grey color):
○ Those used by the abstract UtilityLinkSequenceOrLink featureType properties;
○ Those used by the concrete cable or pipe and appurtenance featureType properties of
the specific utility network;
○ Those used by the ―appurtenanceType‖ property of the Appurtenance object;
○ The ―UtilityNetworkTypeValue‖ used by the ―utilityNetworkType‖ property of the
UtilityNetwork object..
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 52

[Link].2. UML Overview

class Core Oil-Gas-Chemicals Netw...

UtilityNetwork Element Node «featureType»

«featureType» UtilityNetwork Element Network::Network
Common Core Utility Network Elements:: «featureType»
UtilityLinkSequenceOrLink Common Core Utility «voidable»
Network Elements:: + geographicalName: GeographicalName [0..*]
«voidable» UtilityNode
+ utilityDeliveryType: UtilityDeliveryTypeValue [0..1]
+ warningType: WarningTypeValue

+networks
+pipes «voidable»
«featureType» «voidable» «featureType» «featureType» 0..*
Common Core Utility Network 0..* Common Core Utility Network Elements::Appurtenance Common Core Utility Network Elements::UtilityNetwork
Elements::Pipe
+ appurtenanceType: AppurtenanceTypeValue + utilityNetworkType: UtilityNetworkTypeValue
«voidable» + authorityRole: RelatedParty [1..*]
+ pipeDiameter: Measure constraints «voidable»
+ pressure: Measure [0..1] {"TelecommunicationsAppurtenanceTypeValue" is not in IR} + utilityFacilityReference: ActivityComplex [0..*]
+ disclaimer: PT_FreeText [0..*]

«featureType» constraints
OilGasChemicalsPipe {All objects have inspireId}
{"telecommunications" value of "utilityNetworkType" is not in IR}
«voidable»
+ oilGasChemicalsProductType: OilGasChemicalsProductTypeValue [1..*]
«codeList»
Common Core Utility
Network Elements::
«codeList» AppurtenanceTypeValue «codeList»
OilGasChemicalsProductTypeValue Common Core Utility
Network Elements::
UtilityNetworkTypeValue
{complete + electricity
+ oilGasChemicals
+ sewer
«codeList» «codeList» + water
OilGasChemicalsProductTypeBaseValue OilGasChemicalsAppurtenanceTypeValue + thermal
+ liquefiedNaturalGas + telecommunications [0..1]
+ methane + crossTheme
+ naturalGas
+ naturalGasAndTetrahydrothiophene
+ nitrogenGas
+ residualGas
+ accetone
«codeList»
+ air
OilGasChemicalsAppurtenanceTypeBaseValue
+ argon
+ butadiene + pump
+ butadiene1,3 + gasStation
+ butane + node
+ c3 + compression
+ carbonMonoxide + terminal
+ chlorine + deliveryPoint
+ compressedAir + frontier
+ crude + marker
+ dichloroethane + beacon
+ diesel
+ ethylene tags
+ gasFabricationOfCocs asDictionary = true
+ gasHFx extensibility = any
+ gasoil vocabulary = [Link]
+ hydrogen xsdEncodingRule = iso19136_2007_INSPIRE_Extensions
+ isobutane
+ JET-A1
+ kerosene «codeList»
+ liquidAmmonia Common Core Utility Network
+ liquidHydrocarbon Elements::WarningTypeValue
+ multiProduct
+ MVC
+ nitrogen
+ oxygen
+ phenol
+ propane
+ propyleen «codeList»
+ propylene Common Core Utility Network «codeList»
+ raffinate Elements:: Common Core Utility Network Elements::WarningTypeBaseValue
+ refineryProducts UtilityDeliveryTypeValue
+ saltWater + net
+ saumur + tape
+ tetrachloroethane + concretePaving
+ unknown
tags
+ empty
asDictionary = true
tags extensibility = any
asDictionary = true vocabulary = [Link]
extensibility = any xsdEncodingRule = iso19136_2007_INSPIRE_Extensions
«codeList»
vocabulary = [Link] Common Core Utility Network Elements::UtilityDeliveryTypeBaseValue
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions
+ collection
+ distribution
+ private
+ transport

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 8 – UML class diagram: Overview of the “Core Oil-Gas-Chemicals Networks”

[Link].3. Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Core Oil-Gas-Chemicals Network

Scope Core Oil-Gas-Chemicals Network
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Core Oil-Gas-Chemicals Network
Types defined in the feature catalogue
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 53

Type Package Stereotypes Section

OilGasChemicalsAppurtenanceTypeBaseValue Core Oil-Gas- «codeList» [Link].2.1
Chemicals Network
OilGasChemicalsAppurtenanceTypeValue Core Oil-Gas- «codeList» [Link].2.2
Chemicals Network
OilGasChemicalsPipe Core Oil-Gas- «featureType» [Link].1.1
Chemicals Network
OilGasChemicalsProductTypeBaseValue Core Oil-Gas- «codeList» [Link].2.3
Chemicals Network
OilGasChemicalsProductTypeValue Core Oil-Gas- «codeList» [Link].2.4
Chemicals Network
Spatial object types
OilGasChemicalsPipe
OilGasChemicalsPipe
Name: oil, gas and chemicals pipe
Subtype of: Pipe
Definition: A pipe used to convey oil, gas or chemicals from one location to another.
Status: Proposed
Stereotypes: «featureType»
Attribute: oilGasChemicalsProductType

Name oil, gas and chemicals product type

Value type: OilGasChemicalsProductTypeValue
Definition: The type of oil, gas or chemicals product that is conveyed through the oil, gas,
chemicals pipe.
Multiplicity: 1..*
Stereotypes: «voidable»
Obligation: Implementing Rule (requirement)

Code lists
OilGasChemicalsAppurtenanceTypeBaseValue
OilGasChemicalsAppurtenanceTypeBaseValue
Name: oil, gas and chemicals appurtenance type base value
Subtype of: OilGasChemicalsAppurtenanceTypeValue
Definition: Codelist containing a base classification of oil, gas, chemicals appurtenance types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
OilGasChemicalsAppurtenanceTypeValue
OilGasChemicalsAppurtenanceTypeValue
Name: oil, gas and chemicals appurtenance type value
Subtype of: AppurtenanceTypeValue
Definition: Codelist containing a classification of oil, gas and chemicals appurtenances.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
OilGasChemicalsProductTypeBaseValue
OilGasChemicalsProductTypeBaseValue
Name: oil, gas and chemicals product type base value
Subtype of: OilGasChemicalsProductTypeValue
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 54

OilGasChemicalsProductTypeBaseValue
Definition: Codelist containing a base classification of oil, gas and chemicals product types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
OilGasChemicalsProductTypeValue
OilGasChemicalsProductTypeValue
Name: oil, gas and chemicals product type value
Definition: Codelist containing a classification of oil, gas and chemicals products.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.
AppurtenanceTypeValue
AppurtenanceTypeValue
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: Codelist containing a classification of appurtenances.
Pipe
Pipe
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: A utility link or link sequence for the conveyance of solids, liquids, chemicals or
gases from one location to another. A pipe can also be used as an object to
encase several cables (a bundle of cables) or other (smaller) pipes.

[Link]. INSPIRE-governed code lists for the “Core Oil-Gas-Chemical”

[Link].1. Values of code list OilGasChemicalsAppurtenanceTypeBaseValue

Value Name Definition

pump Pump Pump
gasStation Gas station Gas station
node Node Node
compression Compression Compression
terminal Terminal Terminal
deliveryPoint Delivery point Delivery point
frontier Frontier Frontier
marker Marker Marker
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 55

[Link].2. Values of code list OilGasChemicalsProductTypeBaseValue

Value Name Definition

highCalorificGas high Calorific Gas high Calorific Gas
liquefiedNaturalGas liquefied Natural Gas liquefied Natural Gas
lowCalorificGas low Calorific Gas low Calorific Gas
methane methane methane
naturalGas natural Gas natural Gas
natural Gas And natural Gas And
naturalGasAndTetrahydrothiophene
Tetrahydrothiophene Tetrahydrothiophene
nitrogenGas nitrogen Gas nitrogen Gas
residualGas residual Gas residual Gas
accetone accetone accetone
air air air
argon argon argon
butadiene butadiene butadiene
butadiene1,3 butadiene1,3 butadiene1,3
butane butane butane
c3 c3 c3
carbonMonoxide carbon Monoxide carbon Monoxide
chlorine chlorine chlorine
compressedAir compressed Air compressed Air
crude crude crude
dichloroethane dichloroethane dichloroethane
diesel diesel diesel
ethylene ethylene ethylene
gas Fabrication Of
gasFabricationOfCocs gas Fabrication Of Cocs
Cocs
gasHFx gasH Fx gasH Fx
gasoil gasoil gasoil
hydrogen hydrogen hydrogen
isobutane isobutane isobutane
JET-A1 JET-A1 JET-A1
kerosene kerosene kerosene
liquidAmmonia liquid Ammonia liquid Ammonia
liquidHydrocarbon liquid Hydrocarbon liquid Hydrocarbon
multiProduct multi Product multi Product
MVC MVC MVC
nitrogen nitrogen nitrogen
oxygen oxygen oxygen
phenol phenol phenol
propane propane propane
propyleen propyleen propyleen
propylene propylene propylene
raffinate raffinate raffinate
refineryProducts refinery Products refinery Products
saltWater salt Water salt Water
saumur saumur saumur
tetrachloroethane tetrachloroethane tetrachloroethane
unknown unknown unknown
empty empty empty

[Link]. Externally governed code lists for the “Core Oil-Gas-Chemical”

OilGasChemicalAppertunanceTypeValue code lists included in the “Core Oil-Gas-Chemical Networks”

application schemas is empty and can be extensible by any external codelist. The
OilGasChemicalAppertunanceTypeBaseValue is an internal code list which is also extended from the
empty OilGasChemicalAppertunanceTypeValue code list.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 56

OilGasChemicalsProductTypeValue code lists included in the “Core Oil-Gas-Chemical Networks”

application schemas is empty and can be extensible by any external codelist. The
OilGasChemicalsProductTypeBaseValue is an internal code list which is also extended from the
empty OilGasChemicalsProductTypeValue code list.

5.2.5 “Core Sewer Network” application schema

[Link]. Description

[Link].1. Narrative Description

Core Sewer Network application schema is structured containing:

● One concrete link object extending from an abstract Cable or Pipe featureType (shown in red
color);
● One Appurtenance node object (green color) ;
● One UtilityNetwork object (green color);
● All codelists used by the featureType properties of this diagram (grey color):
○ Those used by the abstract UtilityLinkSequenceOrLink featureType properties;
○ Those used by the concrete cable or pipe and appurtenance featureType properties of
the specific utility network;
○ Those used by the ―appurtenanceType‖ property of the Appurtenance object;
○ The ―UtilityNetworkTypeValue‖ used by the ―utilityNetworkType‖ property of the
UtilityNetwork object..
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 57

[Link].2. UML Overview

class Core Sewer Netw...

UtilityNetwork Element Node «featureType»

«featureType» UtilityNetwork Element Network::Network
Common Core Utility Network Elements:: «featureType»
UtilityLinkSequenceOrLink Common Core Utility «voidable»
Network Elements:: + geographicalName: GeographicalName [0..*]
«voidable» UtilityNode
+ utilityDeliveryType: UtilityDeliveryTypeValue [0..1]
+networks
+ warningType: WarningTypeValue
«voidable»
0..*

«featureType» «featureType» «featureType»

Common Core Utility Common Core Utility Network Elements::Appurtenance Common Core Utility Network Elements::UtilityNetwork
Network Elements::Pipe
+ appurtenanceType: AppurtenanceTypeValue + utilityNetworkType: UtilityNetworkTypeValue
«voidable» + authorityRole: RelatedParty [1..*]
+ pipeDiameter: Measure constraints «voidable»
+ pressure: Measure [0..1] {"TelecommunicationsAppurtenanceTypeValue" is not in IR} + utilityFacilityReference: ActivityComplex [0..*]
+pipes
+ disclaimer: PT_FreeText [0..*]
«voidable»
0..*
constraints
{All objects have inspireId}
«featureType» {"telecommunications" value of "utilityNetworkType" is not in IR}
SewerPipe

«voidable»
+ sewerWaterType: SewerWaterTypeValue
«codeList»
Common Core Utility
«codeList» Network Elements:: «codeList»
SewerWaterTypeValue AppurtenanceTypeValue Common Core Utility Network
Elements::
UtilityNetworkTypeValue

{complete + electricity
+ oilGasChemicals
+ sewer
«codeList» «codeList» + water
SewerWaterTypeBaseValue SewerAppurtenanceTypeValue + thermal
+ combined + telecommunications [0..1]
+ reclaimed + crossTheme
+ sanitary
+ storm

tags
asDictionary = true
extensibility = any
vocabulary = [Link] «codeList»
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions SewerAppurtenanceTypeBaseValue
+ anode
+ barrel
«codeList» + barScreen
Common Core Utility Network + catchBasin
Elements:: + cleanOut
UtilityDeliveryTypeValue + dischargeStructure
+ meter
+ pump
+ regulator
«codeList» + scadaSensor
Common Core Utility Network Elements::UtilityDeliveryTypeBaseValue + thrustProtection
+ tideGate
+ collection + other
+ distribution + node
+ private + connection
+ transport + specificStructure
+ mechanicAndElectromechanicEquipment
tags + rainwaterCollector
asDictionary = true + watertankOrChamber
extensibility = any
vocabulary = [Link] tags
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions asDictionary = true
extensibility = any
vocabulary = [Link]
«codeList» xsdEncodingRule = iso19136_2007_INSPIRE_Extensions
Common Core Utility Network
Elements::WarningTypeValue

«codeList»
Common Core Utility Network Elements::WarningTypeBaseValue
+ net
+ tape
+ concretePaving

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 9 – UML class diagram: Overview of the “Core Sewer Networks”

[Link].3. Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Core Sewer Network

Scope Core Sewer Network
Version number 3.0rc2
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 58

Version date 2012-07-09

Definition source INSPIRE data specification Core Sewer Network
Types defined in the feature catalogue

Type Package Stereotypes Section

SewerAppurtenanceTypeBaseValue Core Sewer Network «codeList» [Link].2.1
SewerAppurtenanceTypeValue Core Sewer Network «codeList» [Link].2.2
SewerPipe Core Sewer Network «featureType» [Link].1.1
SewerWaterTypeBaseValue Core Sewer Network «codeList» [Link].2.3
SewerWaterTypeValue Core Sewer Network «codeList» [Link].2.4
Spatial object types
SewerPipe
SewerPipe
Name: sewer pipe
Subtype of: Pipe
Definition: A sewer pipe used to convey wastewater (sewer) from one location to another.
Status: Proposed
Stereotypes: «featureType»
Attribute: sewerWaterType

Name sewer water type

Value type: SewerWaterTypeValue
Definition: Type of sewer water.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Implementing Rule (requirement)

Code lists
SewerAppurtenanceTypeBaseValue
SewerAppurtenanceTypeBaseValue
Name: sewer appurtenance type value
Subtype of: SewerAppurtenanceTypeValue
Definition: Codelist containing a classification of the extension of sewer appurtenance
types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
SewerAppurtenanceTypeValue
SewerAppurtenanceTypeValue
Name: sewer appurtenance type value
Subtype of: AppurtenanceTypeValue
Definition: Codelist containing a classification of sewer appurtenances.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
SewerWaterTypeBaseValue
SewerWaterTypeBaseValue
Name: sewer water type base value
Subtype of: SewerWaterTypeValue
Definition: Codelist containing a base classification of sewer water types.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 59

SewerWaterTypeBaseValue
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
SewerWaterTypeValue
SewerWaterTypeValue
Name: sewer water type value
Definition: Codelist containing a classification of sewer water types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.
AppurtenanceTypeValue
AppurtenanceTypeValue
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: Codelist containing a classification of appurtenances.
Pipe
Pipe
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: A utility link or link sequence for the conveyance of solids, liquids, chemicals or
gases from one location to another. A pipe can also be used as an object to
encase several cables (a bundle of cables) or other (smaller) pipes.

[Link]. INSPIRE-governed code lists for the “Core Sewer Network”

[Link].1. Values of code list SewerWaterTypeBaseValue

Value Name Definition

combined Combined Combined sewer network
reclaimed Reclaimed Reclaimed sewer network
sanitary Sanitary Sanitary sewer network
storm Storm Storm sewer network

[Link].2. Values of code list SewerAppurtenanceTypeBaseValue

Value Name Definition

anode anode Anode.
barrel barrel Barrel.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 60

barScreen bar Screen Bar screen.

catchBasin catch Basin Catch basin.
cleanOut clean Out Clean out.
dischargeStructure discharge Discharge structure.
Structure
meter meter Meter.
pump pump Pump.
regulator regulator Regulator.
scadaSensor scada Sensor SCADA sensor.
thrustProtection thrust Thrust protection.
Protection
tideGate tide Gate Tide gate.
Other other
Node node Node
connection connection Connection
specificStructure specific Specific Structure
Structure
mechanicAndElectromecha mechanic And Mechanic And Electromechanic Equipment
nicEquipment Electromechani
c Equipment
rainwaterCollector rainwater Rainwater Collector
Collector
watertankOrChamber watertank Or Watertank Or Chamber
Chamber

[Link]. Externally governed code lists for the “Core Sewer Network”

SewerAppertunanceTypeBaseValue code lists included in the ―Core Sewer Networks‖ application

schemas is empty and can be extensible by any value.

SewerAppertunanceTypeValue code lists included in the “Sewer Networks” application schemas is

empty and can be extensible by any external codelist. The SewerAppertunanceTypeBaseValue is an
internal code list which is also extended from the empty SewerAppertunanceTypeValue code list.

5.2.6 “Core Thermal Network” application schema

[Link]. Description

[Link].1. Narrative Description

Core Thermal Network application schema is structured containing:

● One concrete link object extending from an abstract Cable or Pipe featureType (shown in red
color);
● One Appurtenance node object (green color) ;
● One UtilityNetwork object (green color);
● All codelists used by the featureType properties of this diagram (grey color):
○ Those used by the abstract UtilityLinkSequenceOrLink featureType properties;
○ Those used by the concrete cable or pipe and appurtenance featureType properties of
the specific utility network;
○ Those used by the ―appurtenanceType‖ property of the Appurtenance object;
○ The ―UtilityNetworkTypeValue‖ used by the ―utilityNetworkType‖ property of the
UtilityNetwork object..
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 61

[Link].2. UML Overview

class Core Thermal Netw...

UtilityNetwork Element Node «featureType»

«featureType» UtilityNetwork Element Network::Network
Common Core Utility Network Elements:: «featureType»
UtilityLinkSequenceOrLink Common Core Utility «voidable»
Network Elements:: + geographicalName: GeographicalName [0..*]
«voidable» UtilityNode +networks
+ utilityDeliveryType: UtilityDeliveryTypeValue [0..1] «voidable»
+ warningType: WarningTypeValue 0..*
+pipes
«voidable» «featureType» «featureType»
0..* Common Core Utility Network Elements::Appurtenance Common Core Utility Network Elements::UtilityNetwork
«featureType» + appurtenanceType: AppurtenanceTypeValue + utilityNetworkType: UtilityNetworkTypeValue
Common Core Utility + authorityRole: RelatedParty [1..*]
Network Elements::Pipe constraints
«voidable»
{"TelecommunicationsAppurtenanceTypeValue" is not in IR}
«voidable» + utilityFacilityReference: ActivityComplex [0..*]
+ pipeDiameter: Measure + disclaimer: PT_FreeText [0..*]
+ pressure: Measure [0..1]
constraints
{All objects have inspireId}
{"telecommunications" value of "utilityNetworkType" is not in IR}

«featureType»
ThermalPipe «codeList»
«voidable»
Common Core Utility «codeList»
Network Elements:: Common Core Utility Network
+ thermalProductType: ThermalProductTypeValue
AppurtenanceTypeValue Elements::
UtilityNetworkTypeValue
+ electricity
{complete + oilGasChemicals
«codeList» + sewer
Common Core Utility Network + water
Elements:: «codeList» + thermal
UtilityDeliveryTypeValue ThermalAppurtenanceTypeValue + telecommunications [0..1]
+ crossTheme

«codeList» «codeList»
Common Core Utility Network Elements::UtilityDeliveryTypeBaseValue ThermalProductTypeValue
+ collection
+ distribution
+ private
+ transport

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

«codeList»
Common Core Utility Network
Elements::WarningTypeValue

«codeList»
Common Core Utility Network Elements::WarningTypeBaseValue
+ net
+ tape
+ concretePaving

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 10 – UML class diagram: Overview of the “Core Thermal Networks”

[Link].3. Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Core Thermal Network

Scope Core Thermal Network
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Core Thermal Network
Types defined in the feature catalogue
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 62

Type Package Stereotypes Section

ThermalAppurtenanceTypeValue Core Thermal Network «codeList» [Link].2.1
ThermalPipe Core Thermal Network «featureType» [Link].1.1
ThermalProductTypeValue Core Thermal Network «codeList» [Link].2.2
Spatial object types
ThermalPipe
ThermalPipe
Name: thermal pipe
Subtype of: Pipe
Definition: A pipe used to disseminate heating or cooling from one location to another.
Status: Proposed
Stereotypes: «featureType»
Attribute: thermalProductType

Name thermal product type

Value type: ThermalProductTypeValue
Definition: The type of thermal product that is conveyed through the thermal pipe.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Technical Guidance (recommendation)

Code lists
ThermalAppurtenanceTypeValue
ThermalAppurtenanceTypeValue
Name: thermal appurtenance type value
Subtype of: AppurtenanceTypeValue
Definition: Codelist containing a classification of thermal appurtenances.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
ThermalProductTypeValue
ThermalProductTypeValue
Name: thermal product type value
Definition: Codelist containing a classification of thermal products.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.
AppurtenanceTypeValue
AppurtenanceTypeValue
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: Codelist containing a classification of appurtenances.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 63

Pipe
Pipe
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: A utility link or link sequence for the conveyance of solids, liquids, chemicals or
gases from one location to another. A pipe can also be used as an object to
encase several cables (a bundle of cables) or other (smaller) pipes.

[Link]. INSPIRE-governed code lists for the “Core Thermal Network”

[Link].1. Values of code list ThermalProductTypeBaseValue

Parent
Value Name Definition Description
value
heatingSteam heating Steam
heatingWater heating Water
coolingWater cooling Water
[Link]. Externally governed code lists for the “Core Thermal Network”

ThermalAppertunanceTypeValue code lists included in the “Core Thermal Networks” application

schemas is empty and can be extensible by any external codelist.

ThermalProductTypeValue code lists included in the “Core Thermal Networks” application schemas is
empty and can be extensible by any external codelist. The ThermalProductTypeBaseValue is an
internal code list which is also extended from the empty ThermalProductTypeValue code list.

5.2.7 “Core Water Network” application schema

[Link]. Description

[Link].1. Narrative Description

Core Water Network application schema is structured containing:

● One concrete link object extending from an abstract Cable or Pipe featureType (shown in red
color);
● One Appurtenance node object (green color) ;
● One UtilityNetwork object (green color);
● All codelists used by the featureType properties of this diagram (grey color):
○ Those used by the abstract UtilityLinkSequenceOrLink featureType properties;
○ Those used by the concrete cable or pipe and appurtenance featureType properties of
the specific utility network;
○ Those used by the ―appurtenanceType‖ property of the Appurtenance object;
○ The ―UtilityNetworkTypeValue‖ used by the ―utilityNetworkType‖ property of the
UtilityNetwork object..
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 64

[Link].2. UML Overview

class Core Water Netw...

UtilityNetwork Element Node «featureType»

«featureType» UtilityNetwork Element Network::Network
Common Core Utility Network Elements:: «featureType»
UtilityLinkSequenceOrLink Common Core Utility «voidable»
Network Elements:: + geographicalName: GeographicalName [0..*]
«voidable» UtilityNode
+ utilityDeliveryType: UtilityDeliveryTypeValue [0..1]
+ warningType: WarningTypeValue
+networks
+pipes «voidable»
«featureType» «voidable» 0..*
0..* «featureType»
Common Core Utility
«featureType» Common Core Utility Network Elements::UtilityNetwork
Network Elements::Pipe
Common Core Utility Network Elements::Appurtenance
+ utilityNetworkType: UtilityNetworkTypeValue
«voidable» + appurtenanceType: AppurtenanceTypeValue + authorityRole: RelatedParty [1..*]
+ pipeDiameter: Measure
«voidable»
+ pressure: Measure [0..1] constraints + utilityFacilityReference: ActivityComplex [0..*]
{"TelecommunicationsAppurtenanceTypeValue" is not in IR} + disclaimer: PT_FreeText [0..*]

«featureType» constraints
WaterPipe {All objects have inspireId}
{"telecommunications" value of "utilityNetworkType" is not in IR}
«voidable»
+ waterType: WaterTypeValue «codeList»
Common Core Utility Network
Elements::
«codeList» «codeList»
AppurtenanceTypeValue
WaterTypeValue Common Core Utility
Network Elements::
UtilityNetworkTypeValue
+ electricity
{complete + oilGasChemicals
«codeList» + sewer
WaterTypeBaseValue + water
«codeList» + thermal
+ potable + telecommunications [0..1]
WaterAppurtenanceTypeValue
+ raw + crossTheme
+ salt
+ treated

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

«codeList»
«codeList»
WaterAppurtenanceTypeBaseValue
Common Core Utility Network
Elements::UtilityDeliveryTypeValue + anode
+ clearWell
+ controlValve
+ fitting
+ hydrant
+ junction
+ lateralPoint
«codeList» + meter
Common Core Utility Network Elements::UtilityDeliveryTypeBaseValue + pump
+ collection + pumpStation
+ distribution + samplingStation
+ private + scadaSensor
+ transport + storageBasin
+ storageFacility
tags + surgeReliefTank
asDictionary = true + systemValve
extensibility = any + thrustProtection
vocabulary = [Link] + treatmentPlant
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions + well
+ pressureRelieveValve
+ airRelieveValve
+ checkValve
+ waterExhaustPoint
+ waterServicePoint
«codeList» + fountain
Common Core Utility Network + pressureController
Elements::WarningTypeValue + vent
+ recoilCheckValve
+ waterDischargePoint

tags
asDictionary = true
extensibility = any
«codeList» vocabulary = [Link]
Common Core Utility Network Elements::WarningTypeBaseValue xsdEncodingRule = iso19136_2007_INSPIRE_Extensions
+ net
+ tape
+ concretePaving

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 11 – UML class diagram: Overview of the “Core Water Networks”

[Link].3. Feature catalogue

Feature catalogue metadata
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 65

Feature catalogue name INSPIRE feature catalogue Core Water Network

Scope Core Water Network
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Core Water Network
Types defined in the feature catalogue

Type Package Stereotypes Section

WaterAppurtenanceTypeBaseValue Core Water Network «codeList» [Link].2.1
WaterAppurtenanceTypeValue Core Water Network «codeList» [Link].2.2
WaterPipe Core Water Network «featureType» [Link].1.1
WaterTypeBaseValue Core Water Network «codeList» [Link].2.3
WaterTypeValue Core Water Network «codeList» [Link].2.4
Spatial object types
WaterPipe
WaterPipe
Name: water pipe
Subtype of: Pipe
Definition: A water pipe used to convey water from one location to another.
Status: Proposed
Stereotypes: «featureType»
Attribute: waterType

Name water type

Value type: WaterTypeValue
Definition: Type of water.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Implementing Rule (requirement)

Code lists
WaterAppurtenanceTypeBaseValue
WaterAppurtenanceTypeBaseValue
Name: water appurtenance type base value
Subtype of: WaterAppurtenanceTypeValue
Definition: Codelist containing a base classification of water appurtenance types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
WaterAppurtenanceTypeValue
WaterAppurtenanceTypeValue
Name: water appurtenance type value
Subtype of: AppurtenanceTypeValue
Definition: Codelist containing a classification of water appurtenances.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
WaterTypeBaseValue
WaterTypeBaseValue
Name: water type base value
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 66

WaterTypeBaseValue
Subtype of: WaterTypeValue
Definition: Codelist containing a base classification of water types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
WaterTypeValue
WaterTypeValue
Name: water type value
Definition: Codelist containing a classification of water types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.
AppurtenanceTypeValue
AppurtenanceTypeValue
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: Codelist containing a classification of appurtenances.
Pipe
Pipe
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility
Networks Profile::Common Core Utility Network Elements [Include reference to
the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]
Definition: A utility link or link sequence for the conveyance of solids, liquids, chemicals or
gases from one location to another. A pipe can also be used as an object to
encase several cables (a bundle of cables) or other (smaller) pipes.

[Link]. INSPIRE-governed code lists for the “Core Water Network”

[Link].1. Values of code list WaterAppurtenanceTypeBaseValue

Value Name Definition Description

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 67

Value Name Definition Description

An anode is a feature (specifically, an
electrical mechanism) that’s
applied to system components for the
prevention of rust, pitting, and the
corrosion of metal surfaces that are in
contact with water or soil. A low-
voltage current is applied to the water
or soil in contact with the metal, such
anode anode Anode. that the
electromotive force renders the metal
component cathodic. Corrosion is
concentrated on the anodes instead
of on the associated (and protected)
water system components. This type
of corrosion may occur in copper,
steel, stainless steel, cast iron, and
ductile iron pipes.
A clear well is an enclosed tank that
is associated with a treatment plant.
Clear wells are used to store filtered
water of sufficient capacity to prevent
the need to vary the filtration rate with
clearWell clear Well Clear well. variations in demand. Clear wells are
also used to provide chlorine contact
time for disinfection. Pumps are
used to move the water from the clear
well to the treatment plant or to a
distribution system.
Control valves represent set of valves
that operate in special ways. There
controlValve control Valve Control valve. are three fundamental types of control
valves: backflow control, air control,
and altitude.
The fitting represents the facility
found at the joint between two lines
where a transition of some sort must
fitting fitting Fitting. occur. The basic connecting devices
between pipes; fittings are rarely used
to control the flow of water through
the network.
A hydrant enables fire fighters to
attach fire hoses to the distribution
network. Hydrants also have
hydrant hydrant Hydrant. secondary uses that include flushing
main lines and laterals, filling tank
trucks, and providing a temporary
water source for construction jobs.
The junction is a water network node
where two or more pipes combine, or
junction junction Junction.
a point where water consumption is
allocated and defined as demand.
A lateral point represents the location
lateralPoint lateral Point Lateral point. of the connection between the
customer and the distribution system.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 68

Value Name Definition Description

A meter is a facility that is used to
measure water consumption
(volume). Being a facility, a meter
plays the role of a junction on the
active network.
meter meter Meter.
NOTE Meters are also much like
hydrants as they also have an
associated warehouse object,
namely, a WarehouseMeter.
A pump is a piece of equipment that
moves, compresses, or alters the
pressure of a fluid, such as water or
air, being conveyed through a natural
or artificial channel.
pump pump Pump.
NOTE Pump types include AxialFlow,
Centrifugal, Jet, Reciprocating,
Rotary,
Screw, and Turbine.
A pump station is a facility for
pumping water on the network to
pumpStation pump Station Pump station.
transport to another part of the
network (lift pump).
A sampling station is a facility that is
used for collecting water samples.
samplingStati sampling Sampling stations may be dedicated
Sampling station.
on Station sampling devices, or they may be
other devices of the system where a
sample may be obtained.
The SCADA sensor is a feature
that’s used to remotely
measure the status of network
components as part of a supervisory
control and data acquisition (SCADA)
scada
scadaSensor SCADA sensor. system. SCADA systems provide
Sensor
alarms, responses, data acquisition,
and control for collection and
distribution systems. Operators use
the SCADA system to monitor and
adjust processes and facilities.
A storage basin represents artificially
storage enclosed area of a river or harbor
storageBasin Storage basin.
Basin designed so that the water level
remains unaffected by tidal changes.
storageFacilit storage Enclosed storage
y Facility facility.
A surge relief tank is a piece of
equipment used to absorb pressure
increases in the water system. Surge
surgeReliefTa surge Relief
Surge relief tank. relief tanks provide a buffer against
nk Tank
throttling within the system by
accepting water into a tank through a
pressure valve.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 69

Value Name Definition Description

A system valve is a facility that is
fitted to a pipeline or orifice in which
the closure member is either rotated
or moved transversely or
longitudinally in the waterway so as to
control or stop the flow. System
valves are used to regulate pressure,
system
systemValve System valve. isolate, throttle flow, prevent
Valve
backflow, and relieve
pressure.

NOTE System valve types include

Gate, Plug, Ball, Cone, and Butterfly.
These specific types may be
classified as isolation valves.
The thrust protection represents a
type of line protector that’s
used to prevent pipe movement.
Thrust protection is commonly
implemented as thrust blocks
thrustProtecti thrust (masses of concrete material) that are
Thrust protection.
on Protection placed at bends and around valve
structures.

NOTE The types of thrust protection

include Anchor,
Blocking, Deadman, and Kicker.
treatmentPlan treatment
Treatment plant. Treatment plant.
t Plant
well well Production well. Production well.
pressure
pressureRelie
Relieve pressure Relieve Valve pressure Relieve Valve
veValve
Valve
airRelieveValv air Relieve
air Relieve Valve air Relieve Valve
e Valve
checkValve check Valve check Valve check Valve
water
waterExhaust
Exhaust water Exhaust Point water Exhaust Point
Point
Point
waterService water
water Service Point water Service Point
Point Service Point
fountain fountain fountain fountain
fireHydrant fire Hydrant fire Hydrant fire Hydrant
pressureContr pressure
pressure Controller pressure Controller
oller Controller
vent vent vent vent
recoilCheckV recoil Check
recoil Check Valve recoil Check Valve
alve Valve
water
waterDischarg
Discharge water Discharge Point water Discharge Point
ePoint
Point

[Link].2. Values of code list WaterTypeBaseValue

Value Name Definition

potable Potable Potable water
raw Raw Raw water
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 70

Value Name Definition

salt Salt Salt water
treated Treated Treated water

[Link]. Externally governed code lists for the “Utility Networks” subdomain’s
application schemas

WaterAppertunanceTypeBaseValue code lists included in the ―Core Thermal Networks‖ application

schema is empty and can be extensible by any value.

WaterAppertunanceTypeValue code lists included in the “Core Water Networks” application schemas
is empty and can be extensible by any external codelist. The WaterAppertunanceTypeBaseValue is
an internal code list which is also extended from the empty WaterAppertunanceTypeValue code list.

5.3 Application schema “Administrative and social governmental

services”

5.3.1 Description
[Link]. Narrative description and UML Overview

The Administrative and social governmental services application schema consists of the class
GovernmentalService, the related data types, union classes plus a code list.

Non-voidable attributes of the class GovernmentalService (core) are InspireID, the location where the
service is provided (serviceLocation) and the type of the service (serviceType).

The location of the service (attribute serviceLocation) can be modelled variously, so data providers
can choose the most appropriate alternative. Since the data type of these alternatives can vary, a
20 21
union-class is used for that attribute .
If services are located inside buildings or activity complexes, the service geometry should be provided
as a reference to these features. Some service sites are located outside buildings or activity
complexes, but they have an address (e.g. rescue helicopter landing site). Then the spatial reference
should be allocated by the address.
In single cases the service location coincides with a network element which can also be used as
spatial reference. The approach to use existing geometries avoids redundancy between the
application schemas of different INSPIRE themes. Beyond that the service location can be provided
by a geometry.

The type of the service is specified by a code list (ServiceTypeValue). Foundation is the COFOG
22
classification by EUROSTAT [COFOG 1999] . The acronym COFOG means ―Classification of the
Functions of Government‖. This classification covers a broad range of administrative and social
governmental services but provides primarily a template for statistics regarding government
expenditures. Therefore COFOG can‘t be used unmodified.

20
See [ISO 19103]
21
Attention: The “union” type is not yet taken into account in the process “Extraction of feature
catalogue”. It is therefore not included in the § “5.4.2 Feature catalogue”, but visible in the following
figure “UML class diagram: Overview of the US ―Administrative and social governmental services‖
application schema‖
22

[Link]
_COFOG99 &StrLanguageCode=EN&IntPcKey=&StrLayoutCode=HIERARCHIC)
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 71

The list has been tailored and refined by types, which are based on requirements derived from
23
legislation, use cases and interviews. The code list is organized hierarchically . In order to map the
hierarchy inside the code list, parent value is mentioned in the codelist table (cf. § [Link]).
To be complete, the sub-part of the code list regarding the education domain, it has involved the
recent evolution of the ISCED (International Standard Classification of Education) that occurred in
24
2011 .

In this context, it‘s important to note that the meaning of any item has to be taken not only from its
name, definition or description, but also from its position within the hierarchy. The type
―GovernmentalService‖ is the (fictive – because not part of the list) root element of the tree. Both
nodes (e.g. fire-protection service) and leafs (e.g. fire station) are useable as service types. The tree
is intentionally unbalanced.

The further attributes of GovernmentalService (core) are of stereotype <<voidable>>. Beside

begin/endLifespanVersion, which refer to the lifecycle of a version of the (digital) spatial object, the
feature type in its core version contains the attributes pointOfContact and areaOfResponsibility.
PointOfContact (data type Contact from GCM) provides contact information in order to get access to a
service and/or initial information regarding a service.
The attribute areaOfResponsibility contains the spatial responsibility of a service instance, e.g. of an
administration or a police station.
This information simplifies the identification of the appropriate service location for users. The spatial
reference can be provided either by an AdministrativeUnit, a NamedPlace, an ActivityComplex or a
geometry (union-class).

In its extended version GovernmentalService includes a number of voidable attributes (see the feature
catalog for further information):
 additionalLocationDescription can be used to give an additional textual description of the
service location. This is useful to find the service (e.g. an office) inside a large building
complex.
 hoursOfService refers to the time, when the service itself is available. The temporal availability
of a service itself will often coincide with the availability of the dedicated point of contact, which
is specified inside the pointOfContact attribute (e.g. in case of a medical practice). In other
cases, there is a clear distinction. For example a rescue station is engaged only a limited time
(shall be expressed by hoursOfService) but there is a central hotline which is available twenty-
four-seven (shall be expressed by hoursOfService inside the contact data type of the core
attribute pointOfContact).
 name can be used to provide a common denotation for the service (e.g. ―hôtel de ville‖)
 note can be used to provide further information regarding the service. The inclusion of note
considers the fact, that the scope of feature type inside the application schema is very broad
and therefore not all information data providers want to publish can be covered by the given
attributes.
 occupancy states the type (as PTFreeText) and number of persons a service can handle in
terms of a capacity (e.g. the capacity of a school).
 relatedParty (see GCM for definition) contains the owner(s), the operator(s) or the authorit(y|ies)
of the service inclusive their contact [Link] point of contact of a service (which is
provided as pointOfContact inside the core) will coincide often with the contact information of
one of the three mentioned party types, but not in always
 resources is comparable to occupancy but describes the type and amount of technical
resources a service provides (e.g. type and capacity of a hydrant).
 serviceLevel allows data providers to classify services regarding the administrative level where
the service is provided from (based on NUTS classification).
 validFrom and validTo refer to the lifecycle of the real world object.

23
For a better overview, the code list is provided within Annex D.
24
[Link]
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 72

Figure 12 – UML class diagram: Overview of the “Core Administrative and Social Governmental Services” application schema
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 73

Figure 13 – UML class diagram: Overview of the “Extended Administrative and Social Governmental Services” application schema
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 74

[Link]. Consistency between spatial data sets

Nothing more than what‘s written in the general paragraph [Link].

[Link]. Identifier management

Nothing more than what‘s written in the general paragraph [Link].

[Link]. Modelling of object references

Internal references:
The application schema describes single services. Several services can be offered at the same location
or by the same authority. Such internal references aren‘t explicitly modelled but can be analysed by
spatial or logical intersections.

External references:
This application schema provides a special view at real world objects. Very often the same real world
object, which is modelled as a service in the application schema, can be seen as a building, an
ActivityComplex or a vulnerable element as well. Such external references are partly explicitly modelled in
the application schema by using references to buildings or to activity complexes as data types for the
spatial attribute serviceLocation. Beyond that external references can be analysed by spatial
intersections.

[Link]. Geometry representation

As depicted and explained in the UML model above, instances of feature type GovernmentalService,
may be modelled by using several types of spatial references or any kind of geometry (geometry type:
GM_Geometry) in order not to force any MS or data producer to introduce changes in the way how they
model and store their original data sets.

Since this application schema is focussed on services (and not on the spatial objects where services are
located), it is strongly recommended to provide no other geometries as points. The intention to use the
data type GM_Object in the application schema is to ease the effort for data provides if the geometry is
originally stored with other data types. Anyway, the usage of other geometry types than point should be
an exception.

Recommendation 1 When the spatial reference of an administrative and social governmental service
is provided by an autonomous geometry, then the data should be modelled as
point objects (geometry type: GM_Point).

[Link]. Temporality representation

Nothing more than what‘s written in the general paragraph [Link].

5.3.2 Feature Catalogue: Core Administrative and Social Governmental

Services.
[Link]. Feature catalogue
Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue

CoreAdministrativeAndSocialGovernmentalServices
Scope CoreAdministrativeAndSocialGovernmentalServices
Version number 3.0rc2
Version date 2012-07-09
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 75

Definition source INSPIRE data specification

CoreAdministrativeAndSocialGovernmentalServices
Types defined in the feature catalogue

Type Package Stereotypes Section

AreaOfResponsibilityType CoreAdministrativeAndSocialGovernmentalServices «union» [Link].1
GovernmentalService CoreAdministrativeAndSocialGovernmentalServices «featureType» [Link].1
ServiceLocationType CoreAdministrativeAndSocialGovernmentalServices «union» [Link].2
ServiceTypeValue CoreAdministrativeAndSocialGovernmentalServices «codeList» [Link].1
[Link].1. Spatial object types
GovernmentalService
GovernmentalService
Name: governmental service
Definition: Administrative and social governmental services such as public administrations, civil
protection sites, schools and hospitals provided by Public Administrative Bodies or
by private institutions as far as they are covered by the scope of the INSPIRE
directive. This scope is mapped to the values of the corresponding code list
serviceType Value.
Description: The accordant sites are commonly presented in governmental and municipal portals
and map systems as "point of interest"-data, and may be point-based locations of a
variety of categories of municipal and governmental services and social
infrastructure. The spatial object type itself is generic in terms of the modelling
approach, that the concrete type of a GovernmentalService is determined by the
value of the attribute serviceType.
Status: Proposed
Stereotypes: «featureType»
Attribute: areaOfResponsibility

Name area of responsibility

Value type: AreaOfResponsibilityType
Definition: The spatial responsibility of a service instance.
Description: EXAMPLE 1: An administration is responsible for a municipality;
EXEMPLE 2: A specialized hospital is responsible for a region.
Multiplicity: 0..1
Stereotypes: «voidable»
Attribute: beginLifespanVersion

Name begin lifespan version

Value type: DateTime
Definition: Date and time at which this version of the spatial object was inserted or changed in
the spatial data set.
Description: Related to the life-cycle of the spatial object in the data set.
Multiplicity: 1
Stereotypes: «lifeCycleInfo,voidable»
Attribute: endLifespanVersion

Name end lifespan version

Value type: DateTime
Definition: Date and time at which this version of the spatial object was superseded or retired in
the spatial data set.
Description: Related to the life-cycle of the spatial object in the data set.
Multiplicity: 0..1
Stereotypes: «lifeCycleInfo,voidable»
Attribute: inspireId
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 76

GovernmentalService
Name INSPIRE identifier
Value type: Identifier
Definition: External object identifier of the governmental service.
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: 1
Attribute: pointOfContact

Name point of contact

Value type: Contact
Definition: Contains necessary information to get access to a service and/or initial information
regarding a service.
Description: In some cases this information will coincide with the contact information of the
service authority, owner or operator (i.e. specific position or role of the responsible
party, described in the relatedParty attribute of the GovernmentalServiceExtended
in the extended profile).
Multiplicity: 1..*
Stereotypes: «voidable»
Attribute: serviceLocation

Name service location

Value type: serviceLocationType
Definition: Location where the service is offered.
Multiplicity: 1
Obligation: null
Attribute: serviceType

Name service type value

Value type: ServiceTypeValue
Definition: Type of an administrative and governmental service.
Multiplicity: 1
Obligation: Implementing Rule (requirement)
Constraint: endLifespanVersion

Natural If set, the date endLifespanVersion shall be later than beginLifespanVersion.

language:
OCL: inv: [Link] .isAfter([Link])

[Link].2. Data types

AreaOfResponsibilityType
AreaOfResponsibilityType
Name: area of responsibility type
Definition: Set of types for the description of spatial responsibility.
Status: Proposed
Stereotypes: «union»
Attribute: areaOfResponsibilityByAdministrativeUnit

Name area of responsibility by administrative unit

Value type: AdministrativeUnit
Definition: Administrative unit describing the geographic extent of the responsibility of a
service.
Multiplicity: 1..*
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 77

AreaOfResponsibilityType
Attribute: areaOfResponsibilityByNamedPlace

Name area of responsibility by named place

Value type: NamedPlace
Definition: Geographical object describing the geographic extent of the responsibility of a
service.
Multiplicity: 1..*
Attribute: areaOfResponsibilityByNetwork

Name area of responsibility by network

Value type: NetworkReference
Definition: Part of a network describing the geographic extent of the competence of a service.
Multiplicity: 1..*
Attribute: areaOfResponsibilityByPolygon

Name area of responsibility by polygon

Value type: GM_MultiSurface
Definition: Polygon describing the geographic extent of the responsibility of a service.
Multiplicity: 1

ServiceLocationType
ServiceLocationType
Name: service location type
Definition: Set of types of references to locate a service.
Status: Proposed
Stereotypes: «union»
Attribute: serviceLocationByAddress

Name service location by address

Value type: Address
Definition: Location of the service by referencing to an address.
Multiplicity: 1
Attribute: serviceLocationByBuilding

Name service location by building

Value type: Building
Definition: Location of the service by referencing to a building.
Multiplicity: 1..*
Attribute: serviceLocationByActivityComplex

Name service location by activity complex

Value type: ActivityComplex
Definition: Location of the service by referencing to an activity complex.
Multiplicity: 1
Attribute: serviceLocationByGeometry

Name service location by geometry

Value type: GM_Object
Definition: Location of the service by referencing to a geometry.
Multiplicity: 1
Attribute: serviceLocationByUtilityNode

Name location service by utility node

Value type: UtilityNode
Definition: Location of the service by referencing to a node related to a utility network (water,
telecommunication, etc.), e.g. hydrant or emergency call point.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 78

ServiceLocationType
Multiplicity: 1

[Link].3. Code lists

ServiceTypeValue
ServiceTypeValue
Name: service type value
Definition: Codelist containing a classification of governmental services.
Status: Proposed
Stereotypes: «codeList»
Extensibility: narrower
Identifier: [Link]

[Link].4. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

ActivityComplex
ActivityComplex
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Activity Complex::Activity Complex [Include reference to the document that
includes the package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: A "single unit", both technically and economically, under the management control of
the same legal entity (operator), covering activities as those listed in the Eurostat
NACE classification, products and services. Activity Complex includes all
infrastructure, equipment and materials. It must represent the whole area, at the
same or different geographical location, managed by a "single unit".
Description: NOTE 1 This class describes the minimal set of elements necessary to describe and
identify geographically a legal entity and the activities taken place on it under the
context of a Environmental purposes.

NOTE 2 "Activity Complex" could be assimilated to terms described on the

legislation as Facility, Establishment, Plant, Holding, Organization ,Farm, Extractive
Industries or Aquaculture Production Business among others

EXAMPLE i.e. an Agro-business that is legally registered under the Emissions

Directive.

Address
Address
Package: INSPIRE Consolidated UML Model::Themes::Annex I::Addresses::Addresses
[Include reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]
Definition: An identification of the fixed location of property by means of a structured
composition of geographic names and identifiers.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 79

Address
Description: NOTE 1 The spatial object, referenced by the address, is defined as the
"addressable object". The addressable object is not within the application schema,
but it is possible to represent the address' reference to a cadastral parcel or a
building through associations. It should, however, be noted that in different countries
and regions, different traditions and/or regulations determine which object types
should be regarded as addressable objects.

NOTE 2 In most situations the addressable objects are current, real world objects.
However, addresses may also reference objects which are planned, under
construction or even historical.

NOTE 3 Apart from the identification of the addressable objects (like e.g. buildings),
addresses are very often used by a large number of other applications to identify
object types e.g. statistics of the citizens living in the building, for taxation of the
business entities that occupy the building, and the utility installations.

NOTE 4 For different purposes, the identification of an address can be represented

in different ways (see example 3).

EXAMPLE 1 A property can e.g., be a plot of land, building, part of building, way of
access or other construction,

EXAMPLE 2 In the Netherlands the primary addressable objects are buildings and
dwellings which may include parts of buildings, mooring places or places for the
permanent placement of trailers (mobile homes), in the UK it is the lowest level of
unit for the delivery of services, in the Czech Republic it is buildings and entrance
doors.

EXAMPLE 3 Addresses can be represented differently. In a human readable form

an address in Spain and an address in Denmark could be represented like this:
"Calle Mayor, 13, Cortijo del Marqués, 41037 Écija, Sevilla, España" or
"Wildersgade 60A, st. th, 1408 Copenhagen K., Denmark".

AdministrativeUnit
AdministrativeUnit
Package: INSPIRE Consolidated UML Model::Themes::Annex I::Administrative
Units::AdministrativeUnits [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Unit of administration where a Member State has and/or exercises jurisdictional
rights, for local, regional and national governance.

Building
Building
Package: INSPIRE Consolidated UML Model::Themes::Annex
III::Buildings::BuildingExtended2D [Include reference to the document that includes
the package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: A Building is an enclosed construction above and/or underground, used or intended
for the shelter of humans, animals or things or for the production of economic
goods. A building refers to any structure permanently constructed or erected on its
site.

Contact
Contact
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base Types::Base
Types 2::Drafts - for x-TWG discussion::RelatedParty [Include reference to the
document that includes the package, e.g. INSPIRE data specification, ISO standard
or the GCM]
Definition: Communication channels by which it is possible to gain access to someone or
something.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 80

Contact
Description:

DateTime
DateTime
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Primitive::Date and Time [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

GM_MultiSurface
GM_MultiSurface
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19107:2003 Spatial Schema:: Geometry::Geometric aggregates [Include reference
to the document that includes the package, e.g. INSPIRE data specification, ISO
standard or the GCM]

GM_Object
GM_Object (abstract)
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19107:2003 Spatial Schema:: Geometry::Geometry root [Include reference to the
document that includes the package, e.g. INSPIRE data specification, ISO standard
or the GCM]

Identifier
Identifier
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base Types::Base
Types [Include reference to the document that includes the package, e.g. INSPIRE
data specification, ISO standard or the GCM]
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.

NamedPlace
NamedPlace
Package: INSPIRE Consolidated UML Model::Themes::Annex I::Geographical
Names::Geographical Names [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Any real world entity referred to by one or several proper nouns.

NetworkReference
NetworkReference
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Network [Include reference to the document that includes the package, e.g.
INSPIRE data specification, ISO standard or the GCM]
Definition: A reference to a network element.

UtilityNode
UtilityNode (abstract)
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 81

UtilityNode (abstract)
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Common Core Utility Network Elements [Include reference to the document
that includes the package, e.g. INSPIRE data specification, ISO standard or the
GCM]
Definition: A point spatial object which is used for connectivity.
Description: Nodes are found at both ends of the UtilityLink.

5.3.3 Feature Catalogue: Extension Administrative and Social Governmental

Services.
[Link]. Feature catalogue
Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue

ExtensionAdministrativeAndSocialGovernmentalServices
Scope ExtensionAdministrativeAndSocialGovernmentalServices
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification
ExtensionAdministrativeAndSocialGovernmentalServices
Types defined in the feature catalogue

Type Package Stereotypes Section

OccupancyType ExtensionAdministrativeAndSocialGovernmentalServices «dataType» [Link].1
ResourceType ExtensionAdministrativeAndSocialGovernmentalServices «dataType» [Link].2
ServiceLevelValue ExtensionAdministrativeAndSocialGovernmentalServices «enumeration» [Link].1
[Link].1. Data types
OccupancyType
OccupancyType
Name: occupancy type
Definition: Description of a group of occupants.
Status: Proposed
Stereotypes: «dataType»
Attribute: numberOfOccupants

Name number of occupants

Value type: Integer
Definition: Number of occupants.
Multiplicity: 1
Stereotypes: «voidable»
Attribute: typeOfOccupant

Name type of occupant

Value type: PT_FreeText
Definition: Qualitative description of a group of occupants.
Description: EXAMPLE: Elderly people, partly immobile.
Multiplicity: 1

ResourceType
ResourceType
Name: resource type
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 82

ResourceType
Definition: Description of a single technical resource.
Description: EXAMPLE: Capacity of a fire water reservoir.
Status: Proposed
Stereotypes: «dataType»
Attribute: amount

Name amount
Value type: Measure
Definition: Quantitative description of a technical resource.
Multiplicity: 1
Stereotypes: «voidable»
Attribute: typeOfTechnicalMeans

Name type of technical means

Value type: PT_FreeText
Definition: Qualitative description of a technical resource.
Multiplicity: 1

[Link].2. Enumerations
ServiceLevelValue
ServiceLevelValue
Name: service level value
Definition: Classification of European territorial units, based on EUROSTAT values (extension
to sub-national levels).
Status: Proposed
Stereotypes: «enumeration»
Value: GLB

Name: global
Definition: Global, supra-European level.
Value: EUR

Name: european
Definition: Pan-European level.
Value: STA

Name: state
Definition: Member State or national level.
Value: NUTS1

Name: NUTS 1
Definition: Major socio-economic region level.
Value: NUTS2

Name: NUTS 2
Definition: Basic region level (for the aplication of regional policies).
Value: NUTS3

Name: NUTS 3
Definition: Small region level (for specific diagnoses).
Value: LAU1

Name: LAU 1
Definition: Local administrative units at the supramunicipal level.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 83

ServiceLevelValue
Value: LAU2

Name: LAU 2
Definition: Local administrative units at the municipal level.

[Link].3. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

DateTime
DateTime
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Primitive::Date and Time [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

GeographicalName
GeographicalName
Package: INSPIRE Consolidated UML Model::Themes::Annex I::Geographical
Names::Geographical Names [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Proper noun applied to a real world entity.

GovernmentalService
GovernmentalService
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::
AdministrativeAndSocialGovernmentalServices::CoreAdministrativeAndSocialGove
rnmentalServices [Include reference to the document that includes the package,
e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Administrative and social governmental services such as public administrations,
civil protection sites, schools and hospitals provided by Public Administrative
Bodies or by private institutions as far as they are covered by the scope of the
INSPIRE directive. This scope is mapped to the values of the corresponding code
list serviceType Value.
Description: The accordant sites are commonly presented in governmental and municipal
portals and map systems as "point of interest"-data, and may be point-based
locations of a variety of categories of municipal and governmental services and
social infrastructure. The spatial object type itself is generic in terms of the
modelling approach, that the concrete type of a GovernmentalService is determined
by the value of the attribute serviceType.

Integer
Integer
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Primitive::Numerics [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

Measure
Measure
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 84

PT_FreeText
PT_FreeText
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO 19139
Metadata - XML Implementation::Cultural and linguistic adapdability [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

RelatedParty
RelatedParty
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base Types::Base
Types 2::Drafts - for x-TWG discussion::RelatedParty [Include reference to the
document that includes the package, e.g. INSPIRE data specification, ISO standard
or the GCM]
Definition: An organisation or a person with a role related to a resource.
Description: NOTE 1 A party, typically an individual person, acting as a general point of contact
for a resource can be specified without providing any particular role.

5.3.4 INSPIRE-governed code lists

The INSPIRE-defined code lists included in this application schema include the values specified in the
tables in this section.

[Link]. Values of code list “ServiceTypeValue”

Value Name Definition

public
publicAdministrationOffi
administration Public administration offices (not further differentiated).
ce
office
general
generalAdministrationO
administration General administration offices e.g. town halls.
ffice
office
Specialized administration offices which can not be
specialized allocated to the following areas: social protection,
specializedAdministrati
administration education, health,
onOffice
office environmental protection, public order and safety (e. g.
surveying administration).
public order and
publicOrderAndSafety Services concerned with public order and safety.
safety
administration for
administrationForPublic Administration offices concerned with public order and
public order and
OrderAndSafety safety.
safety
Services concerned with police affairs.
policeService police service
[Based on COFOG 1999]
Services concerned with fire-prevention and fire-fighting
affairs; operation of regular and auxiliary fire brigades
fire-protection and of other fire-prevention and fire-fighting services
fireProtectionService
service maintained by public authorities; operation or support of
fire-prevention and fire-fighting training programmes.
[Based on COFOG 1999]
Services concerned with a station housing fire fighters,
fireStation fire station their equipment and vehicles.
[Based on Ordnance Survey 2001]
Stationary device, often electrically operated, for
siren siren producing a penetrating sound for warning the public.
[Based on Merriam-Webster Online Dictionary]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 85

Special water access points of water supply networks

that are specifically designed and built to serve as on-site
hydrant hydrant water sources for fire fighting and other emergency
services.
[Based on Ordnance Survey 2001]
anti-fire water Location, installation or designated area from where
antiFireWaterProvision
provision water for fire-fighting is provided.
fireDetectionAndObserv fire detection and Location, facility, construction or device for the detection
ationSite observation site and observation of fires.
Services dedicated to the search-and-rescue of people,
rescueService rescue service
animals and goods in emergency situations.
Services concerned with the housing of technical staff,
rescueStation rescue station
equipment and auxiliary elements of land rescue teams.
A designated area from which rescue helicopters can
rescueHelicopterLandin Rescue helicopter
take off and land.
gSite landing site
[Based on DGIWG 2000]
Services on the coast providing buildings, mooring areas
marine rescue or piers to host marine rescue teams and their
marineRescueStation
station equipment, boats and other marine crafts.
[Based on Ordnance Survey 2001]
Site offering protection and shelter from disasters and
civilProtectionSite civil protection site
emergency situations to the civilian population.
Location of telephones in a box or on a post for the use
emergency call
emergencyCallPoint of motorists in the event of an emergency situation.
point
[Based on Ordnance Survey 2001]
Element or set of First Aid elements or equipment made
standaloneFirstAidEqui standalone First
available to anyone who may need them, located in
pment Aid equipment
highly visible and accessible places.
defence defence Services concerned with military defence.
Services concerned with the provision of buildings used
barrack barrack especially for lodging soldiers in garrison.
[Based on Merriam-Webster Online Dictionary]
Place usually away from urban areas where tents or
simple buildings (as cabins) are erected for shelter or for
camp camp
temporary residence or instruction of military forces.
[Based on Merriam-Webster Online Dictionary]
Services concerned with the administration, supervision,
environmentalProtectio environmental
inspection, operation or support of activities relating to
n protection
the protection and conservation of the environment.
administration for
administrationForEnviro Administration offices concerned with environmental
environmental
nmentalProtection protection.
protection
Institution engaged in developing programs and material
environmentalEducatio environmental
to increase awareness about the environment and
nCentre education centre
sustainable development.
health health Services concerned with health issues.
This item comprises establishments primarily engaged in
administration for the regulation of activities of agencies that provide health
administrationForHealth
health care and overall administration of health policy.
[Based on ICHA-HP 2000]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 86

Services concerned with medicaments, prostheses,

medical appliances and equipment and other health-
related products obtained by individuals or households,
medical products,
medicalProductsApplia either with or without a prescription, usually from
appliances and
ncesAndEquipment dispensing chemists, pharmacists or medical equipment
equipment
suppliers. They are intended for consumption or use
outside a health facility or institution.
[Based on COFOG 1999]

Medical, dental and paramedical services delivered to

outpatients by medical, dental and paramedical
practitioners and auxiliaries. The services may be
delivered at home, in individual or group consulting
facilities, dispensaries or the outpatient clinics of
outpatientService outpatient service hospitals and the like.
Outpatient services include the medicaments,
prostheses, medical appliances and equipment and other
health-related products supplied directly to outpatients by
medical, dental and paramedical practitioners and
auxiliaries.
[Based on COFOG 1999]
General medical services delivered by general medical
general medical
generalMedicalService clinics and general medical practitioners.
service
[Based on COFOG 1999]
Specialized medical services delivered by specialized
medical clinics and specialist medical practitioners.
Specialized medical clinics and specialist medical
specializedMedicalServ specialized medical practitioners differ from general medical clinics and
ices services general medical practitioners in that their services are
limited to treatment of a particular condition, disease,
medical procedure or class of patient.
[Based on COFOG 1999]
Provision of paramedical health services to outpatients;
Administration, inspection, operation or support of health
services delivered by clinics supervised by nurses,
midwives, physiotherapists, occupational therapists,
paramedical
paramedicalService speech therapists or other paramedical personnel and of
service
health services delivered by nurses, midwives and
paramedical personnel in non-consulting rooms, in
patients' homes or other non-medical institutions.
[COFOG 1999]
Services concerned with hospitalization. Hospitalization
is defined as occurring when a patient is accommodated
in a hospital for the duration of the treatment. Hospital
day-care and home-based hospital treatment are
hospitalService hospital service included, as are hospices for terminally ill persons.
Hospitals are defined as institutions which offer in-patient
care under direct supervision of qualified medical
doctors.
[Based on COFOG 1999]
Hospital services that do not limit their services to a
generalHospital general hospital particular medical speciality.
[Based on COFOG 1999]
Hospital services that limit their services to a particular
specializedHospital specialized hospital medical speciality.
[Based on COFOG 1999]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 87

In-patient services to persons recovering from surgery or

a debilitating disease or condition that requires chiefly
nursing and monitoring and administering of medicaments,
nursingAndConvalesce
convalescent home physiotherapy and training to compensate for loss of
ntHomeService
service function or rest.
[Based on COFOG 1999]

This item comprises establishments primarily engaged in

providing analytic or diagnostic services, including body
medical and
medicalAndDiagnosticL fluid analysis and diagnostic imaging, generally to the
diagnostic
aboratory medical profession or the patient on referral from a health
laboratory
practitioner.
[ICHA-HP 2000]
Services concerned with educational affairs. These
services include military schools and colleges where
curricula resemble those of civilian institutions, police
education education
colleges offering general education in addition to police
training.
[Based on COFOG 1999]
administrationForEduca administration for Administration offices concerned with educational
tion education matters.
Services concerned with pre-primary education at
earlyChildhoodEducatio early childhood
ISCED-2011 level 0 (International Standard Classification
n education
of Education).
Services concerned with primary education at ISCED-
primaryEducation primary education 2011 level 1 (International Standard Classification of
Education).
Services concerned with lower secondary education at
lowerSecondaryEducati lower secondary
ISCED-2011 level 2 (International Standard Classification
on education
of Education).
Services concerned with upper secondary education at
upperSecondaryEducat upper secondary
ISCED-2011 level 3 (International Standard Classification
ion education
of Education).
post-secondary Services concerned with post-secondary non-tertiary
postSecondaryNonTerti
non-tertiary education at ISCED-2011 level 4 (International Standard
aryEducation
education Classification of Education).
Services concerned with post-secondary non-tertiary
shortCycleTertiaryEduc short-cycle tertiary
education at ISCED-2011 level 5 (International Standard
ation education
Classification of Education).
bachelor or Services concerned with post-secondary non-tertiary
bachelorOrEquivalentE
equivalent education at ISCED-2011 level 6 (International Standard
ducation
education Classification of Education).
master or Services concerned with post-secondary non-tertiary
masterOrEquivalentEdu
equivalent education at ISCED-2011 level 7 (International Standard
cation
education Classification of Education).
doctoral or Services concerned with post-secondary non-tertiary
doctoralOrEquivalentEd
equivalent education at ISCED-2011 level 8 (International Standard
ucation
education Classification of Education).
education not Services concerned with education not elsewhere
educationNotElsewhere
elsewhere classified in ISCED-2011, refered as level 9 (International
Classified
classified Standard Classification of Education).
Subsidiary services to education, services concerned
with transportation, food, lodging, medical and dental
subsidiaryServicesToE subsidiary services
care and related subsidiary services chiefly for students
ducation to education
regardless of level.
[Based on COFOG 1999]
socialService social service Services concerned with social protection.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 88

administrationForSocial administration for Administration offices concerned with matters of social

Protection social protection protection.
Various specialized services concerned with transport,
specializedServiceOfSo specialized service home-, day- and holiday-care for the disabled and people
cialProtection of social protection in need of care. Services specifically concerned with
education and employment of people with disabilities.
Services concerned with any home, residence, facility, or
premises which provides temporary, interim, or
housing housing
permanent housing to various groups of persons.
[Pasadena Municipal Code 2011]
childCareService child care service Services concerned with the day care of children.
Institutions and services providing benefits in kind and/or
charity and counselling for the needy, e.g. people who are
charityAndCounselling
counselling unemployed, the socially deprived, disaster victims,
victims of assault and abuse, potential suicides, etc.

5.3.5 Externally governed code lists

No externally governed code lists is included in the ―Administrative and Social Governmental Services‖
subdomain‘s application schemas.

5.4 Application schema “Environmental Management Facilities”

5.4.1 Description
[Link]. Narrative description and UML Overview

The Environmental Management Facilities application schema introduces a single Feature Type named
EnvironmentalManagementFacility, which is defined as follows:
A physical structure designed, built or installed to serve specific functions in relation to environmental
material flows, such as waste or waste water flows, or a delimitable area of land or water used to
serve such functions.
EnvironmentalManagementFacility is modelled as specialisation of the INSPIRE Generic Conceptual
Model Feature Type ActivityComplex and the extended DataTypes described on it.
The environmental management facility data as defined by the Environmental Management Facilities
application schema can be categorised as follows:
 Identification
 Spatiality (extent or position, any type of geometry)
 Temporality (start and potentially end of existence in the ―real world‖)
 Classification and basic information, consisting of the following details:
 Facility functions, i.e., activities and types of input/output the facility is designed or built for.
Example: incineration of residual waste;
 Facility capacities in relation to activities and types of input/output.
Example: physical capacity to incinerate 250000 tons of residual waste per year;
 Permissions granted in relation to the facility, especially permitted functions and/or capacities.
Example: permission to incinerate at most 100000 tons of residual waste per year;
 Classification of the type of facility.
Example: installation or site;
 Parties related to the facility, such as operators, owners or competent authorities;
 Parties related to facility permissions, such as the authority granting a permission;
 Facility service hours;
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 89

 The link to parent facilities, i.e., other environmental management facilities of which the facility is
a part.
Note: The link to parent facilities makes it possible to represent facility hierarchies, such as a
number of installations on one site, or multiple installations that are parts of another
installation.
The objectives for the development of the Environmental Management Facilities application schema were
as follows:
 To cover the most essential use case requirements from environmental management, foremost
waste management;
 To harmonise with respect to identical or similar requirements from other themes, especially
Production and Industrial Facilities (PF) and Agricultural Facilities (AF);
 To support avoidance of redundancy in data instances;
 To avoid redundancy in the application schema and the data specification.
In the field of waste management the concepts of site and installation are very common. These terms are
used in legislation such as the EU directive on waste (2008/98) and the EU regulation on a Pollutant
Release and Transfer Register (PRTR) (2006/166). In the Environmental Management Facilities
application schema these concepts are covered with the single Feature Type
EnvironmentalManagementFacility for the following reasons:
1. While in the majority of cases there is clarity about whether something qualifies as a site or as an
installation, there are also other cases where such a clear distinction may not be possible. For
example, a landfill could qualify as both site and installation;
2. The information relevant to sites, such as spatial extents or positions, permissions, operators, etc.
is similar or corresponding to the information relevant to installations. Thus redundancy in the
application schema is avoided by using a single Feature Type.

The vast majority of EnvironmentalManagementFacility content is derived from the Generic Conceptual
Model ActivityComplex Feature Type and its recommended Data Types. This ensures close alignment
with various related Annex III Feature Types, especially ones from Production and Industrial Facilities
(PF) and Agricultural Facilities (AF). The ActivityComplex Feature Type includes a classification of
activities according to the Statistical Classification of Economic Activities in the European Community
(NACE). A description of the NACE codelist and of the other codelists in use in the application schema is
given in the last paragraphs of this section. The functions considered for the Environmental Management
Facilities Theme fall mainly under the NACE rev. 2 category E "Water supply; Sewerage; Waste
management and remediation activities".
The EnvironmentalManagementFacility Feature Type includes the same basic temporality information
that is common with all INSPIRE Feature Types, especially the date from which and optionally the date
up to which the object exists or existed in the ―real world‖. Additional temporality information can be
provided in relation to permissions. For permissions, both the validity period as well as the date when the
permission was granted is taken into account in the application schema.
There are associations with three of the Annex I Feature Types from EnvironmentalManagementFacility.
These are:
1. Address (facility address);
2. CadastralParcel (cadastral parcels covered by the facility);
3. AbstractBuilding (buildings wherein the facility is located or considered part of the facility);
The application schema makes use of several standardised codelists:
 Statistical Classification of Economic Activities in the European Community (NACE)
[Link]
=NACE_REV2&StrLanguageCode=EN&StrLayoutCode=HIERARCHIC
Sample entries (out of a total number of 615 entries):
o 01.11 - Growing of cereals (except rice), leguminous crops and oil seeds
...
o 38.11 - Collection of non-hazardous waste
o 38.12 - Collection of hazardous waste
o 38.21 - Treatment and disposal of non-hazardous waste
o 38.22 - Treatment and disposal of hazardous waste
o 38.31 - Dismantling of wrecks
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 90

o 38.32 - Recovery of sorted materials

o 39.00 - Remediation activities and other waste management services
...
o 99.00 - Activities of extraterritorial organisations and bodies
 List of economic activities according to Annex I Section 8 of Regulation (EC) No 2150/2002 on
waste statistics
[Link]
Sample entries (out of a total number of 20 entries):
o 1 – Agriculture, hunting and forestry
...
o 17 – Recycling
o 18 – Wholesale of waste and scrap
o 19 – Sewage and refuse disposal, sanitation and similar activities
o 20 – Waste generated by households
 List of recovery and disposal operations according to Annex I and Annex II of Directive 2008/98/EC
on waste
[Link]
Sample entries (out of a total number of 28 entries):
o R1 - Use principally as a fuel or other means to generate energy
o R2 - Solvent reclamation/regeneration
...
o R10 - Land treatment resulting in benefit to agriculture or ecological improvement
o R11 - Use of waste obtained from any of the operations numbered R 1 to R 10
o R12 - Exchange of waste for submission to any of the operations numbered R 1 to R 11
o R13 - Storage of waste pending any of the operations numbered R 1 to R 12 (excluding
temporary storage, pending collection, on the site where the waste is produced)
o D1 - Deposit into or on to land (e.g. landfill, etc.)
o D2 - Land treatment (e.g. biodegradation of liquid or sludgy discards in soils, etc.)
o D3 - Deep injection (e.g. injection of pumpable discards into wells, salt domes or naturally
occurring repositories, etc.)
...
o D11 - Incineration at sea
o D12 - Permanent storage (e.g. emplacement of containers in a mine, etc.)
o D13 - Blending or mixing prior to submission to any of the operations numbered D 1 to D
12
o D14 - Repackaging prior to submission to any of the operations numbered D 1 to D 13
o D15 - Storage pending any of the operations numbered D 1 to D 14 (excluding temporary
storage, pending collection, on the site where the waste is produced)
 EU Decision 2000/532 List of Wastes
[Link]
[Link]
ml
Sample entries (out of a total number of 839 entries):
o 01 01 01 - Wastes from mineral metalliferous excavation
o 01 01 02 - Wastes from mineral non-metalliferous excavation
...
o 20 03 06 - Waste from sewage cleaning
o 20 03 07 - Bulky waste
o 20 03 99 - Municipal wastes not otherwise specified
 Eurostat Statistical Classification of Products by Activity in the European Economic Community
[Link]
=CPA_2008&StrLanguageCode=EN&StrLayoutCode=HIERARCHIC
Sample entries (out of a total number of 3520 entries):
o 01.11.11 - Durum wheat
o 01.11.12 - Wheat, except durum wheat
...
o 38.11.11 - Collection services of non-hazardous recyclable waste, municipal
o 38.11.19 - Collection services of non-hazardous recyclable waste, other
...
o 38.11.51 - Glass waste
o 38.11.52 - Paper and paperboard waste
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 91

...
o 38.11.55 - Plastic waste
...
o 99.00.10 - Services provided by extraterritorial organisations and bodies
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 92

class Environmental Management Facilit...

«featureType»
Activity Complex::ActivityComplex
+ inspireId: Identifier
+ thematicId: ThematicIdentifier [0..*]
+ geometry: GM_Object
+ function: Function [1..*]
«voidable»
+ name: CharacterString [0..1]
+ validFrom: DateTime
+ validTo: DateTime [0..1]
«voidable, lifeCycleInfo»
+ beginLifespanVersion: DateTime
+ endLifespanVersion: DateTime [0..1]

+parentFacility
«voidable» 0..*
ActivityComplex
«featureType» «dataType»
EnvironmentalManagementFacility Activity Complex::
ActivityComplexDescription
«voidable»
+ type: EnvironmentalManagementFacilityTypeValue [0..*] «voidable»
+ serviceHours: PT_FreeText [0..1] + description: PT_FreeText [0..1]
+ facilityDescription: ActivityComplexDescription [0..1] + address: AddressRepresentation [0..1]
+ physicalCapacity: Capacity [0..*] + contact: Contact [0..1]
+ permission: Permission [0..*] + relatedParty: RelatedParty [0..*]
+ status: ConditionOfFacilityValue

Figure 14 – UML class diagram: US “Environmental Management Facilities” application schema, Feature Type
“EnvironmentalManagementFacility”

class Environmental Management Facilities Dataty...

Data Types from Activity Complex Core Data Types from Activity Complex Extended Data Types from Related Party

«dataType»
«dataType» Activity Complex Extended::
Activity Complex::Function InputOutputAmount
«dataType»
+ activity: ActivityValue [1..*] + inputOutput: InputOutputValue
RelatedParty::RelatedParty
«voidable» «voidable»
+ input: InputOutputValue [0..*] + amount: Measure «voidable»
+ output: InputOutputValue [0..*] + contact: Contact [0..1]
+ description: PT_FreeText [0..1] + individualName: PT_FreeText [0..1]
«dataType»
+ organisationName: PT_FreeText [0..1]
Activity Complex Extended::Capacity
+ positionName: PT_FreeText [0..1]
+ activity: ActivityValue [1..*] + role: PartyRoleValue [0..*]
+ input: InputOutputAmount [0..*]
+ output: InputOutputAmount [0..*]
+ time: Time [0..1]
Data Types from Annex I, II and III
«voidable» «dataType»
+ description: PT_FreeText [0..1] RelatedParty::Contact
«dataType»
Addresses::AddressRepresentation
«voidable»
+ adminUnit: GeographicalName [1..*] {ordered} «dataType» + address: AddressRepresentation [0..1]
+ locatorDesignator: CharacterString [0..*] {ordered} Activity Complex Extended::Permission + contactInstructions: PT_FreeText [0..1]
+ locatorName: GeographicalName [0..*] {ordered} + Id: ThematicIdentifier [0..*] + electronicMailAddress: CharacterString [0..1]
«voidable» + hoursOfService: PT_FreeText [0..1]
«voidable»
+ addressArea: GeographicalName [0..*] {ordered} + telephoneFacsimile: CharacterString [0..*]
+ relatedParty: RelatedParty [0..*]
+ postName: GeographicalName [0..*] {ordered} + telephoneVoice: CharacterString [0..*]
+ decisionDate: DateTime
+ postCode: CharacterString [0..1] + website: URL [0..1]
+ dateFrom: DateTime
+ thoroughfare: GeographicalName [0..*] {ordered} + dateTo: DateTime [0..1]
+ description: PT_FreeText [0..1]
+ permittedFunction: Function [0..*]
+ permittedCapacity: Capacity [0..*]

Figure 15 – UML class diagram: US “Environmental Management Facilities” application schema, datatypes
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 93

class Environmental Management Facilities Codeli...

Environmental Management Facilities INSPIRE Internal Codelists INSPIRE Internal Codelists from Activity Complex
«codeList»
EnvironmentalManagementFacilityTypeValue «codeList»
Activity Complex Extended::ActivityComplexStatusValue

tags
asDictionary = true tags
extensibility = narrower asDictionary = true
vocabulary = [Link] extensibility = narrower
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

INSPIRE External Codelists from Activity Complex

«codeList»
Activity Complex::ActivityValue

tags
asDictionary = true
extensibility = any
vocabulary =
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

{incomplete,
overlapping}Activity

«codeList» «codeList»
Activity Complex::EconomicActivityNACEValue Activity Complex::WasteRecoveryDisposalValue

tags tags
asDictionary = true asDictionary = true
extensibility = narrower extensibility = narrower
vocabulary = [Link] vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

«codeList»
Activity Complex::EconomicActivityWasteStatisticsValue

tags
asDictionary = true
extensibility = narrower
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

«codeList»
Activity Complex::InputOutputValue

tags
asDictionary = true
extensibility = any
vocabulary =
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

{incomplete,
overlapping}InputOutput

«codeList» «codeList»
Activity Complex::ProductCPAValue Activity Complex::WasteValue

tags tags
asDictionary = true asDictionary = true
extensibility = narrower extensibility = narrower
vocabulary = [Link] vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 16 – UML class diagram: US “Environmental Management Facilities” application schema, codelists

[Link]. Consistency between spatial data sets

Nothing more than what‘s written in the general paragraph [Link].

[Link]. Identifier management

The Environmental Management Facilities application schema uses the Identifier dataType from the
INSPIRE General Conceptual Model [DS-D2.5]. These identifiers include version number, so can be used
to track changes to an object.
Identifiers may have been assigned to Environmental Facilities in multiple contexts and datasets (legal
registration, registry based on legislation, etc.). In the thematicId attribute, which is of unbounded
multiplicity, any such identifiers can be represented in application schema data instances.

Recommendation 2 The identifier provided must be unique and representative for the Facility from
the point of view of the geographical representation. Generic Identifiers not
directly linked with geographical entities should be avoided (e.g. Company Name
Identifier).

[Link]. Modelling of object references

References to data types are represented using attributes of the relevant data type.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 94

[Link]. Geometry representation

Datasets relating to Environmental Facilities may be provided by different organizations, especially

private and public administration related with waste and waste water management. Independently of the
level of detail the geographical position of the facility should be represented at least as a ―point‖.
According to the most generic legislation (waste, IPPC, E-PRTR) the geographical information is required
in the form of geographical coordinates (X,Y). In certain cases the geographical position can be estimated
by automatic processing of addresses provided at the facility‘s registration. Care has to be taken though
to avoid that automatic processing yields incorrect geospatial positions, such as in cases where a legal
address is provided instead of a facility address.
If a single facility is considered to be composed of separate geographical extents not connected to each
other, then it is valid to provide just the one continuous extent which can be regarded as the main one. It
is however not valid to provide the centroid of the separate extents as the facility‘s position.
References to addresses, cadastral parcels or buildings shall be provided in addition to geographical
position or extent information, but not as the only spatiality information of environmental facilities.
In some cases related with activities which cover a representative extension of land, ―Sites‖, this could be
provided as the geographical representation of the facility, described as polygons (2D) in Local –
Regional Datasets. Based on this option, the model includes an extension for this particular case. In
some cases ―Sites‖ or Polygons in which the facility is placed could be linked with cadastral parcels but
this relation seems to be quite complex from the ontological point of view.
Other kind of potential geo-referenced information is required under the legislation embedded on
documents and descriptions requested without references to specific formats. This option only could be
resolved with external elements (like URL‘s) or the inclusion of raster layers (out of scope).
The model is open to other kind of detailed elements included on the Facility (e.g. Installations, Technical
Units). These elements should be represented by points topologically related with the ―Site‖ or the
Facility. In some cases, the geographical representation could be coincident and inherited from the higher
hierarchical level to which they belong.

Recommendation 3 Based on the aforementioned requirements the value domain of spatial

properties used in this specification is based on ―GM_Object‖ specified within
ISO 19107.

IR Requirement 6 The value domain of spatial properties used in this specification shall be
restricted to the Simple Feature spatial schema as defined by EN ISO 19125-1.

Recommendation 4 Based on this requirements the value domain of spatial properties used in this
specification is based on the ―GM_Object‖ described by ISO 19107

Recommendation 5 Only tested geographical information should be provided in order to guarantee a

minimum error respecting the real perimeter (real emplacement) of the Facility.
Information is valid if the coordinates are inside the perimeter (It‘s not required
the centroïd) or in a margin of 100 meters around it for State or European scale.

[Link]. Temporality representation

Nothing more than what‘s written in the general paragraph [Link].

5.4.2 Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Environmental Management Facilities

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 95

Scope Environmental Management Facilities

Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Environmental Management Facilities
Types defined in the feature catalogue

Type Package Stereotypes Section

EnvironmentalManagementFacility Environmental Management «featureType» [Link].1
Facilities
EnvironmentalManagementFacilityTypeValue Environmental Management «codeList» [Link].1
Facilities
[Link]. Spatial object types
[Link].1. EnvironmentalManagementFacility
EnvironmentalManagementFacility
Name: environmental management facility
Subtype of: ActivityComplex, ActivityComplex
Definition: A physical structure designed, built or installed to serve specific functions in relation
to environmental material flows, such as waste or waste water flows, or a
delimitable area of land or water used to serve such functions.
Description: EXAMPLE In the context of waste management the "specific function" may be a
waste recovery or disposal operation. Typically, waste management sites and waste
management installations (such as incineration plants, landfills or storages) get
distinguished. Multiple waste management installations may be found at the same
site. Waste management installations can be a part of other waste management
installations.

The functions considered for the Environmental Facilities Theme fall mainly under
the NACE rev. 2 category E "Water supply; Sewerage; Waste management and
remediation activities".
Status: Proposed
Stereotypes: «featureType»
Attribute: type

Name type
Value type: EnvironmentalManagementFacilityTypeValue
Definition: The type of facility, such as installation or site.
Multiplicity: 0..*
Stereotypes: «voidable»
Obligation: Technical Guidance (recommendation)
Attribute: serviceHours

Name service hours

Value type: PT_FreeText
Definition: Service hours of the facility.
Multiplicity: 0..1
Stereotypes: «voidable»
Attribute: facilityDescription

Name facility description

Value type: ActivityComplexDescription
Definition: Additional information on an Environmental Management Facilities, including its
address, a contact, related parties and a free text description.
Multiplicity: 0..1
Stereotypes: «voidable»
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 96

EnvironmentalManagementFacility
Attribute: physicalCapacity

Name physical capacity

Value type: Capacity
Definition: A quantification of an actual or potential ability to perform an activity, that typically
does not change, does not change often, or does not change to a significant degree.
Description: NOTE Capacity could refer depending of the thematic scope to different concepts
included on the legislation as ―emission limits‖, ―capacity incineration‖, ―nominal
capacity‖, ―objective estimation data‖, ―rate of desulphurization‖ or ―recycling rate‖.
Multiplicity: 0..*
Stereotypes: «voidable»
Attribute: permission

Name permission
Value type: Permission
Definition: Official Decision (formal consent) granting authorization to operate all or part of an
Environmental Management Facility , subject to certain conditions which guarantee
that the installation or parts of installations on the same site operated by the same
operator complies with the requirements fixed by the law or standards. A permit may
cover one or more functions and fix parameters of capacity; The term may be
extended to other kind of certificates or documents of special relevance depending
of the scope (e.g. ISO, EMAS, National Quality Standards, etc).
Description: NOTE This terms is referred in several legislative acts as ―permit‖ , ―authorization‖,
―development consent‖ or ―exploration permit‖ among others.

EXAMPLE 1 ―…a [written] decision by which the competent authority grants

permission to operate all or part of an installation‖ ;
EXAMPLE 2 ―.. the decision of the competent authority or authorities which entitles
the developer
Multiplicity: 0..*
Stereotypes: «voidable»
Attribute: status

Name status
Value type: ConditionOfFacilityValue
Definition: The status of the Environmental Management Facility, such as operational or
decommissioned.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Implementing Rule (requirement)
Association role: parentFacility

Value type: EnvironmentalManagementFacility

Definition: A parent facility, i.e., a facility to which this facility belongs.
Description: A facility may belong to multiple other facilities.
Multiplicity: 0..*
Stereotypes: «voidable»

[Link]. Code lists

[Link].1. EnvironmentalManagementFacilityTypeValue
EnvironmentalManagementFacilityTypeValue
Name: environmental facility classification
Definition: Classification of environmental facilities, such as into sites and installations.
Status: Proposed
Stereotypes: «codeList»
Extensibility: narrower
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 97

EnvironmentalManagementFacilityTypeValue
Identifier: [Link]

[Link]. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

[Link].1. ActivityComplex
ActivityComplex
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Activity Complex::Activity Complex Extended [Include reference to the
document that includes the package, e.g. INSPIRE data specification, ISO standard
or the GCM]
Definition: A single unit, both technically and economically, under the management control of
the same legal entity (operator), covering activities as those listed in the Eurostat
NACE classification, products and services. Activity Complex includes all
infrastructure, equipment and materials. It must represent the whole area, at the
same or different geographical location, managed by a "single unit" as it has been
previously described.
Description: NOTE 1 This class describes the minimal set of elements necessary to describe and
identify geographically a legal entity and the activities taken place on it under the
context of a Environmental purposes.

NOTE 2 "Activity Complex" could be assimilated to terms described on the

legislation as Facility, Establishment, Plant, Holding, Organization ,Farm, Extractive
Industries or Aquaculture Production Business among others

EXAMPLE i.e. an Agro-business that is legally registered under the Emissions

Directive.

[Link].2. ActivityComplex
ActivityComplex
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Activity Complex::Activity Complex [Include reference to the document that
includes the package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: A "single unit", both technically and economically, under the management control of
the same legal entity (operator), covering activities as those listed in the Eurostat
NACE classification, products and services. Activity Complex includes all
infrastructure, equipment and materials. It must represent the whole area, at the
same or different geographical location, managed by a "single unit".
Description: NOTE 1 This class describes the minimal set of elements necessary to describe and
identify geographically a legal entity and the activities taken place on it under the
context of a Environmental purposes.

NOTE 2 "Activity Complex" could be assimilated to terms described on the

legislation as Facility, Establishment, Plant, Holding, Organization ,Farm, Extractive
Industries or Aquaculture Production Business among others

EXAMPLE i.e. an Agro-business that is legally registered under the Emissions

Directive.

[Link].3. ActivityComplexDescription
ActivityComplexDescription
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Activity Complex::Activity Complex [Include reference to the document that
includes the package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Additional information on an activity complex, including its address, a contact,
related parties and a free text description.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 98

[Link].4. Capacity
Capacity
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Activity Complex::Activity Complex [Include reference to the document that
includes the package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: A quantification of an actual or potential ability to perform an activity, that typically
does not change, does not change often, or does not change to a significant degree.
Description: NOTE Capacity could refer depending of the thematic scope to different concepts
included on the legislation as ―emission limits‖, ―capacity incineration‖, ―livestock
units‖, ―nominal capacity‖, ―objective estimation data‖, ―rate of desulphurization‖ or
―recycling rate‖.

[Link].5. ConditionOfFacilityValue
ConditionOfFacilityValue
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base Types::Base
Types [Include reference to the document that includes the package, e.g. INSPIRE
data specification, ISO standard or the GCM]
Definition: The status of a facility with regards to its completion and use.

[Link].6. PT_FreeText
PT_FreeText
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO 19139
Metadata - XML Implementation::Cultural and linguistic adapdability [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

[Link].7. Permission
Permission
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Activity Complex::Activity Complex [Include reference to the document that
includes the package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Official Decision (formal consent) granting authorization to operate all or part of an
Activity Complex , subject to certain conditions which guarantee that the installation
or parts of installations on the same site operated by the same operator complies
with the requirements fixed by the law or standards. A permit may cover one or
more functions and fix parameters of capacity; The term may be extended to other
kind of certificates or documents of special relevance depending of the scope (e.g.
ISO, EMAS, National Quality Standards, etc).
Description: NOTE This terms is referred in several legislative acts as ―permit‖ , ―authorization‖,
―development consent‖ or ―exploration permit‖ among others.

EXAMPLE 1 ―…a [written] decision by which the competent authority grants

permission to operate all or part of an installation‖ ;
EXAMPLE 2 ―.. the decision of the competent authority or authorities which entitles
the developer to proceed with the project..‖.

Table 3 - Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Environmental Management Facilities

Scope Environmental Management Facilities
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Environmental Management Facilities
Table 4 - Types defined in the feature catalogue
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 99

Type Package Stereotypes Section

EnvironmentalManagementFacility Environmental Management «featureType» [Link].1
Facilities
EnvironmentalManagementFacilityTypeValue Environmental Management «codeList» [Link].1
Facilities
[Link]. Spatial object types
[Link].1. EnvironmentalManagementFacility
EnvironmentalManagementFacility
Name: environmental management facility
Subtype of: ActivityComplex, ActivityComplexExtended
Definition: A physical structure designed, built or installed to serve specific functions in relation
to environmental material flows, such as waste or waste water flows, or a
delimitable area of land or water used to serve such functions.
Description: EXAMPLE In the context of waste management the "specific function" may be a
waste recovery or disposal operation. Typically, waste management sites and waste
management installations (such as incineration plants, landfills or storages) get
distinguished. Multiple waste management installations may be found at the same
site. Waste management installations can be a part of other waste management
installations.

The functions considered for the Environmental Facilities Theme fall mainly under
the NACE rev. 2 category E "Water supply; Sewerage; Waste management and
remediation activities".
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: type

Name type
Value type: EnvironmentalManagementFacilityTypeValue
Definition: The type of facility, such as installation or site.
Multiplicity: 0..*
Obligation: Technical Guidance (recommendation)
Attribute: serviceHours

Name service hours

Value type: PT_FreeText
Definition: Service hours of the facility.
Multiplicity: 0..1
Stereotypes: «voidable»
Association role: parentFacility

Value type: EnvironmentalManagementFacility

Definition: A parent facility, i.e., a facility to which this facility belongs.
Description: A facility may belong to multiple other facilities.
Multiplicity: 0..*
Stereotypes: «voidable»

[Link]. Code lists

[Link].1. EnvironmentalManagementFacilityTypeValue
EnvironmentalManagementFacilityTypeValue
Name: environmental facility classification
Definition: Classification of environmental facilities, such as into sites and installations.
Status: Proposed
Stereotypes: «codeList»
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 100

EnvironmentalManagementFacilityTypeValue
Extensibility: narrower
Identifier: [Link]

[Link]. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

[Link].1. ActivityComplex
ActivityComplex
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Activity Complex::Activity Complex Core [Include reference to the document
that includes the package, e.g. INSPIRE data specification, ISO standard or the
GCM]
Definition: A single unit, both technically and economically, under the management control of
the same legal entity (operator), covering activities as those listed in the Eurostat
NACE classification, products and services. Activity Complex includes all
infrastructure, equipment and materials. It must represent the whole area, at the
same or different geographical location, managed by a "single unit" as it has been
previously described.
Description: NOTE 1 This class describes the minimal set of elements necessary to describe and
identify geographically a legal entity and the activities taken place on it under the
context of a Environmental purposes.

NOTE 2 "Activity Complex" could be assimilated to terms described on the

legislation as Facility, Establishment, Plant, Holding, Organization ,Farm, Extractive
Industries or Aquaculture Production Business among others

EXAMPLE i.e. an Agro-business that is legally registered under the Emissions

Directive.

[Link].2. ActivityComplexExtended
ActivityComplexExtended
Package: INSPIRE Consolidated UML Model::Generic Conceptual Model::Base
Models::Activity Complex::Activity Complex Extended [Include reference to the
document that includes the package, e.g. INSPIRE data specification, ISO standard
or the GCM]
Definition: A single unit, both technically and economically, under the management control of
the same legal entity (operator), covering activities as those listed in the Eurostat
NACE classification, products and services. Activity Complex includes all
infrastructure, equipment and materials. It must represent the whole area, at the
same or different geographical location, managed by a "single unit" as it has been
previously described.
Description: NOTE 1 This class describes the minimal set of elements necessary to describe and
identify geographically a legal entity and the activities taken place on it under the
context of a Environmental purposes.

NOTE 2 "Activity Complex" could be assimilated to terms described on the

legislation as Facility, Establishment, Plant, Holding, Organization ,Farm, Extractive
Industries or Aquaculture Production Business among others

EXAMPLE i.e. an Agro-business that is legally registered under the Emissions

Directive.

[Link].3. PT_FreeText
PT_FreeText
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 101

PT_FreeText
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO 19139
Metadata - XML Implementation::Cultural and linguistic adapdability [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

5.4.3 INSPIRE-governed code lists

The INSPIRE-defined code lists included in this application schema include the values specified in the
tables in this section.

[Link]. Values of code list EnvironmentalManagementFacilityTypeValue

Value Name Definition Description Parent value

installation installation Something installed, such as
machinery, an apparatus, a
device, a system, or a piece of
equipment placed in position
or connected for use.
site site A single piece of land that
serves a specific function, or
where units that serve specific
functions are located and
shared or used in combination.

5.4.4 Externally governed code lists

No externally governed code lists is included in the ―Environmental Management Activities‖ subdomain‘s
application schema.

6 Reference systems

6.1 Coordinate reference systems

6.1.1 Datum

IR Requirement 7 For the coordinate reference systems used for making available the INSPIRE
spatial data sets, the datum shall be the datum of the European Terrestrial
Reference System 1989 (ETRS89) in areas within its geographical scope, and
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-
established and described relationship between both systems, according to EN
ISO 19111.

6.1.2 Coordinate reference systems

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 102

IR Requirement 8 INSPIRE spatial data sets shall be made available using one of the three-
dimensional, two-dimensional or compound coordinate reference systems
specified in the list below.

Other coordinate reference systems than those listed below may only be used for
regions outside of continental Europe. The geodetic codes and parameters for
these coordinate reference systems shall be documented, and an identifier shall
be created, according to EN ISO 19111 and ISO 19127.

1. Three-dimensional Coordinate Reference Systems

– Three-dimensional Cartesian coordinates
– Three-dimensional geodetic coordinates (latitude, longitude and ellipsoidal height), using the
parameters of the GRS80 ellipsoid

2. Two-dimensional Coordinate Reference Systems

– Two-dimensional geodetic coordinates, using the parameters of the GRS80 ellipsoid
– Plane coordinates using the Lambert Azimuthal Equal Area projection and the parameters of the
GRS80 ellipsoid
– Plane coordinates using the Lambert Conformal Conic projection and the parameters of the
GRS80 ellipsoid
– Plane coordinates using the Transverse Mercator projection and the parameters of the GRS80
ellipsoid

3. Compound Coordinate Reference Systems

– For the horizontal component of the compound coordinate reference system, one of the two-
dimensional coordinate reference systems specified above 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. The geodetic codes and
parameters for these vertical reference systems shall be documented and an identifier shall be
created, according to EN ISO 19111 and ISO 19127.
– For the vertical component in the free atmosphere, barometric pressure, converted to height using
ISO 2533:1975 International Standard Atmosphere shall be used.

6.1.3 Display

IR Requirement 9 For the display of the INSPIRE spatial data sets with the View Service specified
in D003152/02 Draft Commission Regulation implementing Directive 2007/2/EC
of the European Parliament and of the Council as regards Network Services, at
least the two dimensional geodetic coordinate system shall be made available.

6.1.4 Identifiers for coordinate reference systems

IR Requirement 10 For referring to the non-compound coordinate reference systems listed in this
Section, the identifiers listed below shall be used.

For referring to a compound coordinate reference system, an identifier composed of

the identifier of the horizontal component, followed by a slash (/), followed by the
identifier of the vertical component, shall be used.

- ETRS89-XYZ for Cartesian coordinates in ETRS89

- ETRS89-GRS80h for three-dimensional geodetic coordinates in ETRS89 on the GRS80 ellipsoid
- ETRS89-GRS80 for two-dimensional geodetic coordinates in ETRS89 on the GRS80
- EVRS for height in EVRS
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 103

- LAT for depth of the sea floor, where there is an appreciable tidal range
- MSL for depth of the sea floor, in marine areas without an appreciable tidal range, in open oceans and
effectively in waters that are deeper than 200m
- ISA for pressure coordinate in the free atmosphere
- PFO for Pressure coordinate in the free ocean
- ETRS89-LAEA for ETRS89 coordinates projected into plane coordinates by the Lambert Azimuthal
Equal Area projection
- ETRS89-LCC for ETRS89 coordinates projected into plane coordinates by the Lambert Conformal
Conic projection
- ETRS89-TMzn for ETRS89 coordinates projected into plane coordinates by the Transverse Mercator
projection

6.2 Temporal reference system

IR Requirement 11 The Gregorian calendar shall be used for as a reference system for date values,
and the Universal Time Coordinated (UTC) or the local time including the time
zone as an offset from UTC shall be used as a reference system for time values.

6.3 Theme-specific requirements and recommendations on

reference systems
There are no theme-specific requirements or recommendations on reference systems.

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 "Utility and governmental services" (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 "Utility and governmental services" (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 "Utility and governmental services" (see sections 7.2
and 7.3).

At least for Utility Networks sub-theme (but sometimes for the whole scope of the Utility and
governmental services theme), the provision of data quality information is necessary to cover the
following specific purposes:
- check that the different data providers supply a minimum set of data quality elements and sub-
elements in order to evaluate and quantify the quality of datasets for specific purposes in the
context of INSPIRE.
- guarantee that a continuous utility network can be built from the elements provided in the utility
network datasets, by assessing their conformance to some basic topological consistency rules
aimed to ensure at least topologically clean connections between features.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 104

The descriptions of the elements and measures are based on Annex D of ISO/DIS 19157 Geographic
information – Data quality.

This specification is also compliant with ISO 19113 and ISO 19114, but it does not fix any concrete
conformance criteria for the data quality information proposed, since it should be valid for a wide range of
European utility network datasets, with very different levels of detail and quality requirements.

However, for the topological consistency rules mentioned above, a minimum set of measures are needed
in order to make it possible the creation of a well-connected utility network.

All rules / DQ elements apply to all sub-themes, except for those mentioning specific use (e.g.
Topological consistency for Utility networks or Absolute or external accuracy).

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 "Utility and governmental services"

Data quality Data quality Evaluation

Section Definition
element sub-element Scope
7.1.1 Completeness Commission Excess data present in the dataset, as dataset series;
described by the scope dataset; spatial
object type
7.1.2 Completeness Omission Data absent from the dataset, as dataset series;
described by the scope dataset; spatial
object type
7.1.3 Logical Conceptual Adherence to rules of the conceptual dataset
consistency consistency schema
7.1.4 Logical Domain Adherence of values to the value dataset
consistency consistency domains
7.1.5 Logical Format Degree to which data is stored in dataset
consistency consistency accordance with the physical structure
of the dataset, as described by the
scope
7.1.6 Logical Topological Correctness of the explicitly encoded spatial object
consistency consistency topological characteristics of the
dataset, as described by the scope
7.1.7 Positional Absolute or Closeness of reported coordinate spatial object
accuracy external values to values accepted as or being
accuracy true
7.1.8 Positional Relative or Closeness of the relative positions of spatial object
accuracy internal features in the scope to their
accuracy respective relative positions accepted
as or being true
7.1.9 Thematic Classification Comparison of the classes assigned spatial object
accuracy correctness to features or their attributes to a
universe of discourse
7.1.10 Thematic Non- Correctness of non-quantitative spatial object
accuracy quantitative attributes
attribute
correctness
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 105

7.1.11 Thematic Quantitative Accuracy of quantitative attributes spatial object

accuracy attribute
accuracy
7.1.12 Temporal quality Accuracy of a Correctness of the temporal spatial object
time references of an item (reporting of
measurement error in time measurement)
7.1.13 Temporal quality Temporal Correctness of ordered events or spatial object
consistency sequences, if reported

7.1.1 Completeness – Commission

Recommendation 7 Commission should be evaluated and documented using the rate of excess
items as specified in the table 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 No specific description for version 2.9
Evaluation scope spatial object type: all spatial object types
dataset
dataset series
Reporting scope spatial object type: all spatial object types
dataset
dataset series
Parameter –
Data quality value type Real ; percentage ; ratio
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example 0.0189 ; 98.11% ; 11:582
Measure identifier 3 (ISO 19157)

7.1.2 Completeness – Omission

Recommendation 8 Omission should be evaluated and documented using the rate of missing
items as specified in the table below.

Name Rate of missing items

Alternative name –
Data quality element Completeness
Data quality sub-element Omission
Data quality basic measure Error rate
Definition Number of missing items in the dataset in relation to the number of
items that should have been present
Description No specific description for version 2.9
Evaluation scope spatial object type: all spatial object types
dataset
dataset series
Reporting scope spatial object type: all spatial object types
dataset
dataset series
Parameter –
Data quality value type Real ; percentage ; ratio
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 106

Source reference ISO/DIS 19157 Geographic information – Data quality

Example 0.0189 ; 98.11% ; 11:582
Measure identifier 7 (ISO 19157)

7.1.3 Logical consistency – Conceptual consistency

Recommendation 9 Conceptual consistency should be evaluated and documented using the

compliance rate with the rules of the conceptual schema as specified in the
table below.

Name Compliance rate with the rules of the conceptual schema

Alternative name –
Data quality element Logical consistency
Data quality sub-element Conceptual consistency
Data quality basic measure Rate of correct items
Definition Adherence to rules of the conceptual schema
Description Number of items in the dataset in compliance with the rules of the
conceptual schema in relation to the total number of items
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Real, percentage, ratio
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example The 95% of the mandatory components or attributes exist and no
constraints are violated within the dataset
Measure identifier 13 (ISO 19157)

7.1.4 Logical consistency – Domain consistency

Recommendation 10 Domain consistency should be evaluated and documented using the value
domain conformance rate as specified in the table below.

Name Value domain conformance rate

Alternative name –
Data quality element Logical consistency
Data quality sub-element Domain consistency
Data quality basic measure Correct items rate
Definition Adherence of values to the value domains
Description Number of items in the dataset that are in conformance with their
value domain in relation to the total number of items in the dataset
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Percentage, ratio
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example 95% of utility features consist of components whose values are
within the domains stated in the application schema.
Measure identifier 17 (ISO 19157)

7.1.5 Logical Consistency – Format consistency

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 107

Recommendation 11 Format consistency should be evaluated and documented using the physical
structure conflict rate as specified in the table below.

Name Physical structure conflict rate

Alternative name –
Data quality element Logical consistency
Data quality sub-element 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 No specific description for version 2.9
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Real ; percentage ; ratio
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example 0.0189 ; 98.11% ; 11:582
Measure identifier 20 (ISO 19157)

7.1.6 Logical Consistency – Topological consistency

The following topological consistency quality sub-elements are strongly required in order to ensure
building a ―clean‖ and connected utility network while working with the Core Utility Networks Profile (or
Extended Utility Networks).
They are less needed with the use of the Basic Utility Profile, even though the respect of these quality
criteria would bring comfort in the use of such data.

Recommendation 12 Topological consistency should be evaluated and documented using the

number of missing connections due to undershoots, the number of missing
connections due to overshoots and the number of invalid self-overlap errors as
specified in the tables below.

Name Number of missing connections due to undershoots

Alternative name Undershoots
Data quality element Logical consistency
Data quality sub-element 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 utility
network
Evaluation scope dataset
Reporting scope dataset
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
utility network.

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):
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 108

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:
o 130. specification
o 131. Explanation
from DQ_Result class.

Note: Metadata elements defined in ISO 19115

Data quality value type Integer
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example
1

Key
1 Connectivity tolerance = 1:10 000 of the resolution of the dataset
(cf. Metadata elements defined in ISO 19115)
Measure identifier 23 (ISO 19157)

Name Number of missing connections due to overshoots

Alternative name Overshoots
Data quality element Logical consistency
Data quality sub-element 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 utility
network
Evaluation scope dataset
Reporting scope dataset
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
utility network.

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
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 109

obtained value (or set of values) against a specified acceptable

conformance quality level‖.
Specifically, the tolerance must be defined within the two
elements:
o 130. specification
o 131. Explanation
from DQ_Result class.

Note: Metadata elements defined in ISO 19115

Data quality value type Integer
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example
1

Key
1 Connectivity tolerance = 1:10 000 of the resolution of the dataset
(cf. Metadata elements defined in ISO 19115)
Measure identifier 24 (ISO 19157)

Name Number of invalid self-overlap errors

Alternative name Kickbacks
Data quality element Logical consistency
Data quality sub-element Topological consistency
Data quality basic measure Error count
Definition Count of all items in the data that illegally self overlap
Description No specific description for version 2.9
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Integer
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example

Key
a
vertices
Measure identifier 27 (ISO 19157)

7.1.7 Positional accuracy – Absolute or external accuracy

Recommendation 13 Absolute or external accuracy should be evaluated and documented using the
mean value of positional uncertainties and the rate of positional errors above a
given threshold as specified in the tables below.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 110

The ―mean value of positional uncertainties‖ sub-element shows the closeness of reported coordinate
values to values accepted as or being true. It is used for the features of the Utility networks sub-
theme only.

Name Mean value of positional uncertainties

Alternative name Mean value of positional uncertainties (1D, 2D and 3D)
Data quality element Positional accuracy
Data quality sub-element 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: ei=|xmi−xti|
2 2
2D: ei=[(xmi−xti) +(ymi−yti) ]
2 2 2
3D: ei=[(xmi−xti) +(ymi−yti) +(zmi−zti) ]
The mean positional uncertainties of the horizontal absolute or
external
positions are then calculated as

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 dataset
Reporting scope dataset
Parameter –
Data quality value type Measure
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example No specific example for version 2.9
Measure identifier 28 (ISO 19157)

The ―mean value of positional uncertainties‖ sub-element shows the closeness of reported coordinate
values to values accepted as or being true. It is used for the features of the Governmental services
and Waste management sub-themes only.

Name Rate of positional errors above a given threshold

Alternative name –
Data quality element Positional accuracy
Data quality sub-element Absolute or external accuracy
Data quality basic measure Not applicable
Definition Number of positional uncertainties above a given threshold for a
set of positions in relation to the total number of measured
positions.
The errors 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
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 111

the position of the point is measured. A corresponding set of

coordinates, xti, yti and zti, are considered to represent the true
positions. The calculation of ei is given by the data quality measure
―mean value of positional uncertainties‖ in one, two and three
dimensions.
All positional uncertainties above a defined threshold emax (ei>emax)
are then counted as error. The number of errors is set in relation to
the total number of measured points.
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.
Evaluation scope dataset
Reporting scope dataset
Parameter Name: emax
Definition: is the threshold above which the positional uncertainties
are counted
Value type: Number
Data quality value type Real ; percentage ; ratio
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example 25% of the nodes within the data quality scope have error distance
greater than 1 metre
Measure identifier 31 (ISO 19157)

Once again, the POI nature of governmental services data and the needs expressed within the analyzed
use cases have clear implications regarding their expected positional accuracy, in the sense that it can be
stated that this parameter is not to be critical to assure their quality and their usability.

7.1.8 Positional accuracy – Relative or internal accuracy

Recommendation 14 Relative or internal accuracy should be evaluated and documented using the
relative horizontal error as specified in the table below.

Name Relative horizontal error

Alternative name Rel CE90
Data quality element Positional accuracy
Data quality sub-element Relative or internal accuracy
Data quality basic measure Not applicable
Definition Closeness of the relative positions of features in the scope to their
respective relative positions accepted as or being true, especially
the evaluation of the random errors in the horizontal position of one
feature to another in the same dataset or on the same map/chart.
Description A comparison of the data (measured) and the control (true) is
calculated in the following manner:

1. Determine all possible point pair combinations:

Point Pair Combinations = m = n(n-1)/2

2. Calculate the absolute error in the X and Y dimensions at each

point:
ΔXi = Measured Xi - True Xi for i = 1…n
ΔYi = Measured Yi - True Yi for i = 1…n

3. Calculate the relative error in X and Y for all point pair

combinations:
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 112

ΔXrel kj = ΔXk - ΔXj for k = 1…m-1, j = k+1, … m

ΔYrel kj = ΔYk – Δyj for k = 1…m-1, j = k+1, … m

4. Calculate the relative standard deviations in each axis:

5. Calculate the relative horizontal standard deviation:

6. Calculate the Relative CE by converting the sigma to a 90 %

significance level:
Rel CE90 = 2,146 σH rel
Evaluation scope dataset
Reporting scope dataset
Parameter Name: n
Definition: Sample size
Value type: Integer
Data quality value type Measure
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Mapping, Charting and Geodesy Accuracy [Department of Defense
(US). Standard Practice: Mapping, Charting and Geodesy
Accuracy. MIL STD 600001, 1990]
Example No specific example for version 2.9
Measure identifier 53 (ISO 19157)

7.1.9 Thematic accuracy – Classification correctness

Recommendation 15 Classification correctness should be evaluated and documented using the

misclassification rate as specified in the table below.

Name Misclassification rate

Alternative name –
Data quality element Thematic accuracy
Data quality sub-element 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 dataset
Reporting scope dataset
Parameter –
Data quality value type Real, percentage, ratio
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example 0.0189 ; 98.11% ; 11:582
Measure identifier 61 (ISO 19157)

7.1.10 Thematic accuracy – Non-quantitative attribute correctness

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 113

Recommendation 16 Non-quantitative attribute correctness should be evaluated and documented

using the Rate of correct attribute values as specified in the table below.

Name Rate of correct attribute values

Alternative name –
Data quality element Thematic accuracy
Data quality sub-element Non-quantitative attribute correctness
Data quality basic measure Correct items rate
Definition Number of correct attribute values in relation to the total number of
attribute values
Description No specific description for version 2.9
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Real, percentage, ratio
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example 0.0189 ; 98.11% ; 11:582
Measure identifier 66 (ISO 19157)

7.1.11 Thematic accuracy – Quantitative attribute accuracy

Recommendation 17 Quantitative attribute accuracy should be evaluated and documented using the
attribute value uncertainty at 50 %, 90 % or 99 % significance level as
specified in the tables below.

Name Attribute value uncertainty at 50 % significance level

Alternative name –
Data quality element Thematic accuracy
Data quality sub-element Quantitative attribute accuracy
Data quality basic measure LE50 or LE50(r), depending on the evaluation procedure
Definition Half length of the interval defined by an upper and a lower limit, in
which the true value for the quantitative attribute lies with
probability 50 %
Description Please, cf. Annex G § 3.2 ―One-dimensional random variable, Ζ‖ of
the chapter ―Uncertainty-related data quality basic measures‖ of
the ISO/DIS 19157 Geographic information – Data quality
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Measure
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example No specific example for version 2.9
Measure identifier 69 (ISO 19157)

Name Attribute value uncertainty at 90 % significance level

Alternative name –
Data quality element Thematic accuracy
Data quality sub-element Quantitative attribute accuracy
Data quality basic measure LE90 or LE90(r), depending on the evaluation procedure
Definition Half length of the interval defined by an upper and a lower limit, in
which the true value for the quantitative attribute lies with
probability 90 %
Description Please, cf. Annex G § 3.2 ―One-dimensional random variable, Ζ‖ of
the chapter ―Uncertainty-related data quality basic measures‖ of
the ISO/DIS 19157 Geographic information – Data quality
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 114

Evaluation scope dataset

Reporting scope dataset
Parameter –
Data quality value type Measure
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example No specific example for version 2.9
Measure identifier 70 (ISO 19157)

Name Attribute value uncertainty at 99 % significance level

Alternative name –
Data quality element Thematic accuracy
Data quality sub-element Quantitative attribute accuracy
Data quality basic measure LE99 or LE99(r), depending on the evaluation procedure
Definition Half length of the interval defined by an upper and a lower limit, in
which the true value for the quantitative attribute lies with
probability 99 %
Description Please, cf. Annex G § 3.2 ―One-dimensional random variable, Ζ‖ of
the chapter ―Uncertainty-related data quality basic measures‖ of
the ISO/DIS 19157 Geographic information – Data quality
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Measure
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example No specific example for version 2.9
Measure identifier 72 (ISO 19157)

7.1.12 Temporal quality – Accuracy of a time measurement

Two different measuring elements are proposed:
● Time accuracy at 50% significance level, for the use cases related to mapping and POI querying
● Time accuracy at 95% significance level, for the use cases related to disaster management

Recommendation 18 Accuracy of a time measurement should be evaluated and documented using

the time accuracy at 50 % or 95 % significance level as specified in the tables
below.

Name Time accuracy at 50 % significance level

Alternative name –
Data quality element Temporal quality
Data quality sub-element Accuracy of a time measurement
Data quality basic measure LE50 or LE50(r), depending on the evaluation procedure
Definition Half length of the interval defined by an upper and a lower limit, in
which the true value for the time instance lies with probability 50 %
Description Please, cf. Annex G § 3.2 ―One-dimensional random variable, Ζ‖ of
the chapter ―Uncertainty-related data quality basic measures‖ of
the ISO/DIS 19157 Geographic information – Data quality
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Measure
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example No specific example for version 2.9
Measure identifier 55 (ISO 19157)
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 115

Name Time accuracy at 95 % significance level

Alternative name –
Data quality element Temporal quality
Data quality sub-element Accuracy of a time measurement
Data quality basic measure LE95 or LE95(r), depending on the evaluation procedure
Definition Half length of the interval defined by an upper and a lower limit, in
which the true value for the time instance lies with probability 95 %
Description Please, cf. Annex G § 3.2 ―One-dimensional random variable, Ζ‖ of
the chapter ―Uncertainty-related data quality basic measures‖ of
the ISO/DIS 19157 Geographic information – Data quality
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Measure
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example No specific example for version 2.9
Measure identifier 57 (ISO 19157)

7.1.13 Temporal quality – Temporal consistency

Recommendation 19 Temporal consistency should be evaluated and documented using the value
domain conformance rate as specified in the tables below.

Name Value domain conformance rate

Alternative name –
Data quality element Temporal quality
Data quality sub-element Temporal consistency
Data quality basic measure Correct items rate
Definition Number of items in the dataset that are in conformance with their
value domain in relation to the total number of items in the dataset
Description No specific description for version 2.9
Evaluation scope dataset
Reporting scope dataset
Parameter –
Data quality value type Real, percentage, ratio
Data quality value structure Single value, Bag, Set, Sequence, Table, Matrix or Coverage
Source reference ISO/DIS 19157 Geographic information – Data quality
Example 0.0189 ; 98.11% ; 11:582
Measure identifier 17 (ISO 19157)

7.2 Minimum data quality requirements

No minimum data quality requirements are defined for the spatial data theme "Utility and governmental
services".

7.3 Recommendation on data quality

No minimum data quality recommendations are defined.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 116

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. When using ISO 19115/19157/19139 to encode the metadata, the
following rules should be followed:

 The scope element (of type DQ_Scope) of the DQ_DataQuality subtype should be used to
encode the reporting scope.

NOTE The reporting scope can be different from the evaluation scope (see section 7).

 Only the following values should be used for the level element of DQ_Scope: Series, Dataset,
featureType.

NOTE The value featureType is used to denote spatial object type.

 If the level is featureType the levelDescription/MDScopeDescription/features element (of type

Set< GF_FeatureType>) shall be used to list the feature type names.

Mandatory or conditional metadata elements are specified in Section 8.1. Optional metadata elements
are specified in Section 8. The tables describing the metadata elements contain 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.
 The fourth column specifies the condition, under which the given element becomes mandatory
(only for Table 4 and Table 5).

8.1 Common metadata elements

IR Requirement 12 The metadata describing a spatial data set or a spatial data set series related to
the theme "Utility and governmental services" shall comprise the metadata
elements required by Regulation 1205/2008/EC (implementing Directive
2007/2/EC of the European Parliament and of the Council as regards metadata)
for spatial datasets and spatial dataset series (Table 4) as well as the metadata
elements specified in Table 5.

Table 4 – Metadata for spatial datasets and spatial dataset series specified in Regulation
1205/2008/EC (implementing Directive 2007/2/EC of the European Parliament and of the Council as
regards metadata)
Metadata
Regulation Metadata element Multiplicity Condition
Section
1.1 Resource title 1

1.2 Resource abstract 1

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 117

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 1..*

use

8.2 Limitations on public 1..*

access

9 Responsible organisation 1..*

10.1 Metadata point of contact 1..*

10.2 Metadata date 1

10.3 Metadata language 1

Table 5 – Mandatory and conditional common metadata elements

INSPIRE Data
Specification
"Utility and
Metadata element Multiplicity Condition
governmental
services"
Section
8.1.1 Coordinate Reference 1
System

8.1.2 Temporal Reference 0..* Mandatory, if the spatial data set or

System one of its feature types contains
temporal information that does not refer
to the Gregorian Calendar or the
Coordinated Universal Time.

8.1.3 Encoding 1..*

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 118

8.1.4 Character Encoding 0..* Mandatory, if an encoding is used that

is not based on UTF-8.

8.1.5 Data Quality – Logical 0..* Mandatory, if the data set includes
Consistency – Topological types from the Generic Network Model
Consistency and does not assure centreline
topology (connectivity of centrelines)
for the network.

8.1.1 Coordinate Reference System

Metadata element name Coordinate Reference System
Description of the coordinate reference system used in the
Definition
dataset.
ISO 19115 number and name 13. referenceSystemInfo
ISO/TS 19139 path referenceSystemInfo
INSPIRE obligation / condition mandatory
INSPIRE multiplicity 1
Data type(and ISO 19115 no.) 186. MD_ReferenceSystem
To identify the reference system, the referenceSystemIdentifier
(RS_Identifier) shall be provided.

Domain 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
referenceSystemIdentifier:
Example code: ETRS_89
codeSpace: INSPIRE RS registry
<gmd:referenceSystemInfo>
<gmd:MD_ReferenceSystem>
<gmd:referenceSystemIdentifier>
<gmd:RS_Identifier>
<gmd:code>
<gco:CharacterString>ETRS89
</gco:CharacterString>
</gmd:code>
Example XML encoding
<gmd:codeSpace>
<gco:CharacterString>INSPIRE RS
registry</gco:CharacterString>
</gmd:codeSpace>
</gmd:RS_Identifier>
</gmd:referenceSystemIdentifier>
</gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>
Comments

8.1.2 Temporal Reference System

Metadata element name Temporal Reference System
Description of the temporal reference systems used in the
Definition
dataset.
ISO 19115 number and name 13. referenceSystemInfo
ISO/TS 19139 path referenceSystemInfo
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 119

Mandatory, if the spatial data set or one of its feature types

INSPIRE obligation / condition 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.) 186. MD_ReferenceSystem
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.
Domain
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
referenceSystemIdentifier:
Example code: GregorianCalendar
codeSpace: INSPIRE RS registry
<gmd:referenceSystemInfo>
<gmd:MD_ReferenceSystem>
<gmd:referenceSystemIdentifier>
<gmd:RS_Identifier>
<gmd:code>

<gco:CharacterString>GregorianCalendar</gco:CharacterString
>
Example XML encoding </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.1.3 Encoding
Metadata element name Encoding
Description of the computer language construct that specifies the
Definition representation of data objects in a record, file, message, storage
device or transmission channel
ISO 19115 number and name 271. distributionFormat
ISO/TS 19139 path distributionInfo/MD_Distribution/distributionFormat
INSPIRE obligation / condition mandatory
INSPIRE multiplicity 1
Data type (and ISO 19115 no.) 284. MD_Format
See B.2.10.4. The property values (name, version, specification)
Domain specified in section 9 shall be used to document the default and
alternative encodings.
Implementing instructions
name: "Utility and governmental services" GML application
schema
version: version 2.9, GML, version 3.2.1
Example
specification: [Link].6 Data Specification on "Utility and
governmental services" –
Draft Guidelines
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 120

<gmd:MD_Format>
<gmd:name>
<gco:CharacterString> "Utility and governmental
services" GML application schema </gco:CharacterString>
</gmd:name>
<gmd:version>
<gco:CharacterString>2.9, GML, version
Example XML encoding 3.2.1</gco:CharacterString>
</gmd:version>
<gmd:specification>
<gco:CharacterString>[Link].6 Data
Specification on "Utility and governmental services" –
Draft Guidelines</gco:CharacterString>
</gmd:specification>
</gmd:MD_Format>
Comments

8.1.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 -
<gmd:characterSet>
<gmd:MD_CharacterSetCode
codeListValue="8859part2"
Example XML encoding codeList="[Link]
SO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#C
haracterSetCode">8859-2</gmd:MD_CharacterSetCode>
</gmd:characterSet>
Comments

8.1.5 Data Quality – Logical Consistency – Topological Consistency

Data Quality – Logical Consistency – Topological
Metadata element name
Consistency
Correctness of the explicitly encoded topological characteristics
Definition
of the dataset as described by the scope
Mandatory, if the data set includes types from the Generic Network
INSPIRE obligation / condition Model and does not assure centreline topology (connectivity of
centrelines) for the network.
INSPIRE multiplicity 0..*
See clauses on topological consistency in section 7 for detailed
information.

This metadata element is mandatory if connectivity is not assured

Comments
for network centrelines in the dataset. In this case the Connectivity
tolerance parameter – as described in section 7 – must be
provided in order to ensure automatic and unambiguous creation
of centreline topology in post-process.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 121

NOTE See section 8.2 for further instructions on how to implement metadata elements for reporting
data quality.

8.2 Metadata elements for reporting data quality

Recommendation 20 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.

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.

Recommendation 21 The metadata elements specified in the following tables 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 table applies to reporting quantitative results (using the element DQ_QuantitativeResult), while
the second table applies to reporting non-quantitative results (using the element DQ_DescriptiveResult).

NOTE These tables may need to be updated once the XML schemas for ISO 19157 have been finalised.

Metadata element name See chapter 7

Definition See chapter 7
ISO/DIS 19157 number and name 3. report
ISO/TS 19139 path dataQualityInfo/*/report
INSPIRE obligation / condition optional
INSPIRE multiplicity 0..*
Data type (and ISO/DIS 19157 Corresponding DQ_xxx subelement from ISO/DIS 19157, e.g.
no.) 12. DQ_CompletenessCommission
Lines 7-9 from ISO/DIS 19157
7. DQ_MeasureReference (C.2.1.3)
Domain
8. DQ_EvaluationMethod (C.2.1.4.)
9. DQ_Result (C2.1.5.)
39. nameOfMeasure

NOTE This should be the name as defined in Chapter 7.

42. evaluationMethodType

43. 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
Implementing instructions specified using this property.

46. dateTime

NOTE This should be data or range of dates on which the

data quality measure was applied.

63. 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.)
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 122

See Table E.12 — Reporting commission as metadata

Example
(ISO/DIS 19157)
Example XML encoding

Metadata element name See chapter 7

Definition See chapter 7
ISO/DIS 19157 number and name 3. report
ISO/TS 19139 path dataQualityInfo/*/report
INSPIRE obligation / condition optional
INSPIRE multiplicity 0..*
Data type (and ISO/DIS 19157 Corresponding DQ_xxx subelement from ISO/DIS 19157, e.g.
no.) 12. DQ_CompletenessCommission
Line 9 from ISO/DIS 19157
Domain
9. DQ_Result (C2.1.5.)
67. DQ_DescripitveResult / 68. statement

Implementing instructions 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.
See Table E.15 — Reporting descriptive result as metadata
Example
(ISO/DIS 19157)
Example XML encoding

Open issue 1: For reporting compliance with minimum data quality requirements and
recommendations specified in section 7, the INSPIRE conformity metadata element should be used.
However, since this issue is part of the larger discussion on the Abstract Test Suite and the definition of
conformance classes for the data specification, detailed instructions on how to provide metadata on
compliance with minimum data quality requirements and recommendations will only be provided for
v3.0.

8.3 Theme-specific metadata elements

No mandatory theme-specific metadata elements are defined for this theme.

No optional theme-specific metadata elements are defined for this theme.

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.) 142. MD_MaintenanceInformation
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 123

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:
Domain
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.4 Guidelines on using metadata elements defined in Regulation

1205/2008/EC

8.4.1 Conformity

The Conformity metadata element defined in Regulation 1205/2008/EC allows to report the conformance
with the Implementing Rule for interoperability of spatial data sets and services or another specification.
The degree of conformity of the dataset 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).

Recommendation 22 The Conformity metadata element should be used to report conceptual

consistency with this INSPIRE data specification. The value of Conformant
should be used for the Degree element only if the dataset passes all the
requirements described in the abstract test suite presented in Annex A. The
Specification element should be given as follows:
- title: ―INSPIRE Data Specification on <Theme Name> – Draft Guidelines‖
- date:
- dateType: publication
- date: 2012-02-28

Open issue 2: Conformance testing is still an open issue under discussion.

Instructions on conformance testing and a common abstract test suite (including detailed instructions
on how to test specific requirements) will be added at a later stage.

This may also lead to an update of the recommendations on how to fill the conformity metadata
element.

8.4.2 Lineage

Recommendation 23 Following the ISO 19113 Quality principles, if a data provider has a procedure
for quality validation of their spatial data sets then the data quality elements
listed in the Chapters 7 and 8 should be used. 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.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 124

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 specify that the
statement sub-element of LI_Lineage (EN ISO 19115) should be used to implement the lineage metadata
element.

Recommendation 24 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 This recommendation is based on the conclusions of the INSPIRE Data Quality Working Group
to avoid overloading of the overall lineage statement element with information on the transformation steps
and related source data.

NOTE 2 In order to improve the interoperability, domain templates and instructions for filling these free
text elements (descriptions) may be specified in an Annex of this data specification.

Open issue 3: The suggested use of the LI_Lineage sub-elements needs to be discussed as part of
the maintenance of the INSPIRE metadata Technical Guidelines.

8.4.3 Temporal reference

According to Regulation 1205/2008/EC, at least one of the following temporal reference metadata
elements shall be provided: temporal extent, date of publication, date of last revision, date of creation. If
feasible, the date of the last revision of a spatial data set should be reported using the Date of last
revision metadata element.

9 Delivery

9.1 Delivery medium

TG Requirement 2 Data conformant to this INSPIRE data specification shall be made available
through an INSPIRE network service.

TG Requirement 3 All information that is required by a calling application to be able to retrieve the
data through the used network service shall be made available in accordance
with the requirements defined in the Implementing Rules on Network Services.

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),
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 125

 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 proviced 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.1.1 Specific Delivery medium

―Administrative and social governmental services are commonly presented in governmental and
municipal portals and map systems as "point of interest"-data …‖ [D2.3: Definition of Annex Themes and
Scope]

The portrayal of a service as a symbol in a map won‘t be sufficient in many cases. Further information,
e.g. contact data, is essential to use the service.

Recommendation 6 View services delivering governmental services data should provide queryable
layers and the GetFeatureInfo operation [ISO 19128]

9.2 Encodings
9.2.1 Default Encoding(s)

TG Requirement 4 Data conformant to the application schema(s) defined in section 5 shall be

encoded using the encoding(s) specified in this section.

[Link]. Default encoding for application schemas of “Utility and Governmental Services”

Name:
 ―Core Administrative and Social Governmental Services‖ GML Application Schema;
 ―Extended Administrative and Social Governmental Services‖ GML Application Schema;
 ―Environmental Management Facilities‖ GML Application Schema;
 ―Core Utility Networks Profile‖ GML Application Schema;
 ―Core Electricity Network‖ GML Application Schema;
 ―Core Oil, Gas & Chemicals Network‖ GML Application Schema;
 ―Core Sewer Network‖ GML Application Schema;
 ―Core Telecommunications Network‖ GML Application Schema;
 ―Core Thermal Network‖ GML Application Schema;
 ―Core Water Network‖ GML Application Schema;
 ―Basic Utility Profile‖ GML Application Schema;
 ―Basic Electricity‖ GML Application Schema;
 ―Basic Oil, Gas & Chemicals‖ GML Application Schema;
 ―Basic Sewer‖ GML Application Schema;
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 126

 ―Basic Telecommunications‖ GML Application Schema;

 ―Basic Thermal‖ GML Application Schema;
 ―Basic Water‖ GML Application Schema;
 ―Codelists for Core & Basic Utility Profiles‖ GML Application Schema
Version: version 2.9, GML, version 3.2.1
Specification: [Link].6 Data Specification on "Utility and governmental services" – Draft Guidelines
Character set: UTF-8

The GML Application Schemas are distributed in a zip-file separately from the data specification
document.

9.2.2 Alternative Encoding(s)

Recommendation 25 It is recommended that also the encodings specified in this section be provided
for the relevant application schemas.

[Link]. Alternative encoding for application schemas of “Utility and Governmental Services”

No alternative encoding should be used.

10 Data Capture
For Utility networks

The data capture for utility networks refers a lot to any other network.
Then, please have a look to what has been written in Transport Networks data specification document,
regarding network data capture, this will be relevant for our sub-theme too.

For Administrative and social governmental services

Recommendation 7 All administrative and social governmental services data which fall under the
INSPIRE scope shall be published

Administrative and social governmental services data, due to their nature, may be captured and provided
by different producers at different levels of (mainly) Public Administration, from local to European,
depending on what is the level and the administrative scope of the correspondent responsible party.

Due to this fact, it is expected that data are provided at very different scales/resolutions, covering different
sub-sets of service types and following different modelling approaches, depending on the concrete needs
of their producers and target users. This way, it can not be expected that a single set of requirements
may be established in order to harmonize this theme's data sets. In consequence, just the
recommendations that follow are proposed:

Recommendation 8 Data should be captured in such conditions that they may be classified into one
or several of the service types listed within ServiceTypeValue codelist.

In order to fulfill the previous recommendation:

Recommendation 9 Datasets should be built by setting different sub-sets for each of the service types
covered.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 127

If the dataset fulfills only administrative and social governmental services model, each one of the resulting
sub-sets shall correspond to one of the service types included in, at least, main level of ServiceTypeValue
codelist.

When data about an instance of administrative and social governmental services is located by means of a
point or an address:

Recommendation 10 Point or address locations should correspond to the main access point to the
space where the service is provided from.

In the case that different services are provided from a single building/facility, they may be located by
different points/addresses by following the previous recommendation to each of those points/addresses.
I.e: a hospital may consist of different buildings. If hospital service is modelled as a whole, its location
point or address should correspond to that of the main entrance to the hospital. In the opposite, if different
services (e.g. General hospital service or Specialized hospital service) within the hospital building or
facility are modelled separately, their location references should correspond, whenever possible, to the
main access point to each of those services.

With regards to data referring to hydrants or emergency call points, which are nodes of, respectively,
water supply networks and communication networks, whenever possible:

Recommendation 11 Data describing services provided from points within a facility network should be
located, whenever possible, by referencing them to the correspondent network
node elements.

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.

In section 11.1, 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 on a specific topic.

Section 11.2 specifies the styles that shall be supported by INSPIRE view services for each of these layer
types.

In section 11.2.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.

Where XML fragments are used in these sections, the following namespace prefixes apply:
 sld="[Link] (WMS/SLD 1.1)
 se="[Link] (SE 1.1)
 ogc="[Link] (FE 1.1)

IR Requirement 1 If an INSPIRE view service supports the portrayal of data related to the theme
"Utility and governmental services", it shall provide layers of the types specified
in this section.

TG Requirement 5 If an INSPIRE view network service supports the portrayal of spatial data sets
corresponding to the spatial data theme "Utility and governmental services", it
shall support the styles specified in section 11.2.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 128

If no user-defined style is specified in a portrayal request for a specific layer to an

INSPIRE view service, the default style specified in section 11.2 for that layer
shall be used.

Recommendation 12 In addition to the styles defined in section 11.2, it is recommended

that, where applicable, INSPIRE view services also support the styles defined in
section 11.2.1.

11.1 Layers to be provided by INSPIRE view services

Layer Name Layer Title Spatial object type(s) Keywords

[Link](Bas Core or Basic UtilityLink(Basic) Utility Cable, Electricity
ic) Electricity Cable Network
Default Style
[Link] Core or Basic UtilityNode(Basic) Utility Appurtenance,
nce(Basic) Electricity Electricity Network
Appurtenance Default
Style
[Link] Core or Basic Oil, Gas UtilityLink(Basic) Utility Pipe, Oil, Gas or
pe(Basic) or Chemicals Pipe Chemicals Network
Default Style
[Link] Core or Basic Oil, Gas UtilityNode(Basic) Utility Appurtenance,
purtenance(Basic) or Chemicals Oil, Gas or Chemicals
Appurtenance Default Network
Style
[Link](Basic) Core or Basic Sewer UtilityLink(Basic) Utility Pipe, Sewer
Pipe Default Style Network
[Link] Core or Basic Sewer UtilityNode(Basic) Utility Appurtenance,
e Appurtenance Default Sewer Network
Style
[Link] Core or Basic UtilityLink(Basic) Utility Cable,
sCable(Basic) Telecommunications Telecommunication
Cable Default Style Network
[Link] Core or Basic UtilityNode(Basic) Utility Appurtenance,
sAppurtenance(Basic) Telecommunications Telecommunication
Appurtenance Default Network
Style
25
UN .ThermalPipe(Basi Core or Basic Thermal UtilityLink(Basic) Utility Pipe, Thermal
c) Pipe Default Style Network
[Link] Core or Basic Thermal UtilityNode(Basic) Utility Appurtenance,
ce(Basic) Appurtenance Default Thermal Network
Style
26
UN .WaterPipe(Basic) Core or Basic Water UtilityLink(Basic) Utility Pipe, Water
Pipe Default Style Network
[Link] Core or Basic Water UtilityNode(Basic) Utility Appurtenance,
(Basic) Appurtenance Default Water Network
Style
[Link] Administrative and (Extended)Government Keywords accordant to
ocialGovernmentalServi social governmental alService the name of the
27
ce service Style corresponding
serviceTypeValue code
list item

25
UN stands for Utility Networks subdomain, i.e. Core and Basic Utility profiles
26
UN stands for Utility Networks subdomain, i.e. Core and Basic Utility profiles
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 129

Layer Name Layer Title Spatial object type(s) Keywords

[Link] Environmental EnvironmentalManage Environment Waste,
gementInstallation Management Facility – mentFacility facility
Installation Style
[Link] Environmental EnvironmentalManage Environment Waste,
gementSite Management Facility – mentFacility facility
Site Style

11.1.1 Layers organisation

The layer ―Utility and governmental services‖ could be comprised of three main layers:
 Utility network;
 Administrative and social governmental service; and
 Environmental management facility;

Concerning the first one (Utility networks), it could be comprised of 5 sub-layers:

 Electricity network
 Oil, gas & Chemicals network
 Water network
 Sewer network
 Thermal network
 Telecommunications network

Best practices and specific recommendations for administrative and social governmental services:

Recommendation 13 The organisation of layers for administrative and social governmental services
shall correspond to the structure of the serviceTypeValue code list.

―correspond to the structure of the serviceTypeValue code list‖ means, that the layer structure:
a) contains only upper items (e.g. the main group items) or
b) (partly) refines the structure of the code list (e.g. regarding types of specialized hospitals) or
c) is a mixture of a) and b) or
d) is identical to the structure of the code list.

This recommendation causes an extensive number of layers but is conform to the fact, that the majority of
governmental geo-portals contain a very fine-grained layer structure and a large number of layers.

Recommendation 14 In order to harmonize the naming of the layers and sub-layers, these should be
denominated by adding the general prefix ―GS― (for Governmental Service) to the
name of the main level type of service, followed by the name of the first level type
of service and so on (separated by ―_‖).

E.g. the name for a sub-layer showing hospitals would be: GS_Health_HospitalService

11.2 Styles to be supported by INSPIRE view services

Without any specific mention below, all objects from the ―Utility and governmental service‖ thematic will
be represented with the default styles of the portrayal according to their type and geometry.

27
One layer for each service type accordant to the serviceTypeValue code list
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 130

11.2.1 Styles for the layer

“Administrative and social
governmental services”
Best practices and specific recommendations for administrative and social governmental services:

The spatial attribute, which can be used for portrayal of GovernmentalServices is serviceLocation.

The location of the service shall be portrayed as point symbols. Depending on the chosen data type for
serviceLocation, the position of the symbol can either taken directly from a point geometry or can be
computed by GIS functionality (e.g. by functions like ―centroid‖ or ―pointOnSurface‖).

The usage of point symbols has some relevant advantages:

 This visualisation suits the ―POI-nature‖ of administrative and social governmental services best.
 The visualisation as point separates the service (scope of INSPIRE theme US), which is provided
e.g. inside a building from the building itself (which is under the scope of INSPIRE theme
Buildings and is visualised as polygon). The simultaneous representation of the service as a
polygon too would create some issues (e.g. interpretation conflicts, missing coherence due to
different data sources).
 When dealing with different services being provided from the same site/building (multi-purpose
ones) or from neighbour ones, the point representation will make it easier to understand this
multiplicity of services, whilst the representation of several overlapping polygons may also cause
confusion to the user.

In the example below, the overlapping of different GS data sub-layers on a complex background
consisting of a set of different base maps and thematic layers could be rather difficult to understand if all
of those services where portrayed as polygons, overlapping with building, street and hydrography
polygons.

Figure 17: Example of portrayal of a multiplicity of GS type data over a complex background (Source:
webEIEL, from Diputación de A Coruña – Spain. [Link]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 131

Recommendation 15 Administrative and social governmental services shall be visualised by point

symbols, even when their spatial reference is modelled different from GM_Point.

This specification doesn‘t provide default styles for the portrayal of spatial data sets corresponding to the
sub-theme Administrative and social governmental services. This issue is discussed in Annex E.

To avoid misinterpretations by the users, it is proposed to have a fine-grained layer resolution (see clause
11.1) and layer structure (see clause 11.1.1). The GetFeatureInfo operation [ISO 19128] (see
Recommendation 22) will additionally help users to interpret different symbols from different data
providers

11.2.2 Styles for the layer

“Environmental Management
Facilities”

Style Name [Link]

Default Style yes

Style Title Environmental Management Facility – Installation Style

Point geometries are rendered as a triangle with a size of 5 pixels,
Style Abstract
with a 50% grey (#808080) fill and a black outline
<sld:NamedLayer>
Symbology <se:Name>[Link]</se:Name>
<sld:UserStyle>
<se:Name> [Link] </se:Name>
<sld:IsDefault>1</sld:IsDefault>
<se:FeatureTypeStyle version="1.1.0" xmlns:PS="urn:xinspire:
specification:EnvironmentalManagementFacility:3.1">
<se:Description>
<se:Title> Environmental Man-agement Facility – Installation Style </se:Title>
<se:Abstract>Point geometries are rendered as a triangle with a size of 5 pixels,
with a 50% grey (#808080) fill and a black outline.</se:Abstract>
</se:Description>
<se:FeatureTypeName>US:EnvironmentalManagementFacility</se:FeatureTypeName>
<se:Rule>US:[Link]=‘installation‘</se:Rule>
<se:PointSymbolizer>
<se:Geometry>
<ogc:PropertyName>US:geometry</ogc:PropertyName>
</se:Geometry>
</se:PointSymbolizer>
</se:Rule>
</se:FeatureTypeStyle>
</sld:UserStyle>
</sld:NamedLayer>

Minimum &
maximum 1:50 000 – 1:20 000
scales

Style Name [Link]

Default Style yes

Style Title Environmental Management Facility – Site Style

Point geometries are rendered as a triangle with a size of 5 pixels,
with a 50% grey (#808080) fill and a black outline.
Style Abstract Line geometries are rendered as a solid black line with a stroke width of 1 pixel.
Polygon geometries are rendered using a 50% grey (#808080) fill and
a solid black outline with a stroke width of 1 pixel
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 132

<sld:NamedLayer>
<se:Name>[Link]</se:Name>
<sld:UserStyle>
<se:Name> [Link] </se:Name>
<sld:IsDefault>1</sld:IsDefault>
<se:FeatureTypeStyle version="1.1.0" xmlns:PS="urn:xinspire:
specification:EnvironmentalManagementFacility:3.1">
<se:Description>
<se:Title> Environmental Man-agement Facility – Installation Style </se:Title>
<se:Abstract>Point geometries are rendered as a circle with a size of 7 pixels,
with a 50% grey (#808080) fill and a black outline.
Line geometries are rendered as a solid black line with a stroke width of 1 pixel.
Polygon geometries are rendered using a 50% grey (#808080) fill and
Symbology a solid black outline with a stroke width of 1pixel.</se:Abstract>
</se:Description>
<se:FeatureTypeName>US:EnvironmentalManagementFacility</se:FeatureTypeName>
<se:Rule>US:[Link]=‘site‘</se:Rule>
<se:PointSymbolizer>
<se:Geometry>
<ogc:PropertyName>US:geometry</ogc:PropertyName>
</se:Geometry>
</se:PointSymbolizer>
</se:Rule>
</se:FeatureTypeStyle>
</sld:UserStyle>
</sld:NamedLayer>

Minimum &
maximum 1:50 000 – 1:20 000
scales

11.3 Other recommended styles

No other well-defined styles are defined in this specification.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 133

Bibliography
[DS-D2.3] INSPIRE DS-D2.3, Definition of Annex Themes and Scope, v3.0,
[Link]
_of_Annex_Themes_and_scope_v3.[Link]

[DS-D2.5] INSPIRE DS-D2.5, Generic Conceptual Model, v3.3,

[Link]

[DS-D2.6] INSPIRE DS-D2.6, Methodology for the development of data specifications, v3.0,
[Link]

[DS-D2.7] INSPIRE DS-D2.7, Guidelines for the encoding of spatial data, v3.2,
[Link]

[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

[Kaden 2011] Nancy Kaden: ―Spezifikation von Darstellungsregeln für das INSPIRE-Thema
"Versorgungswirtschaft und staatliche Dienste" (Bachelor Thesis)

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

[W3C POI Core] World Wide Web Consortium: Data model and XML syntax for representing information
about points of interest (POI) on the World Wide Web ([Link]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 134

Annex A
(normative)

Abstract Test Suite

Any dataset conforming to this INSPIRE data specification shall meet all requirements specified in this
document.

Open issue 4: Conformance testing is still an open issue under discussion.

Instructions on conformance testing and a common abstract test suite (including detailed instructions on
how to test specific requirements) will be added at a later stage.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 135

Annex B
(informative)
Use cases

This annex describes the use cases that were used as a basis for the development of this data
specification:
As mentioned in Annex E of the "―Data Specifications‖ Methodology for the development of data
specifications", the TWG-US identified several use cases for some sub-themes that are hereunder
referenced, or detailed within the checklist framework presented in another Annex (i.e. Annex C Check
Lists for Data Interoperability").

B.1 Use case for “Utility networks”

B.1.1 Introduction

This document provides a use case of the subtheme ―Utility networks‖ within the INSPIRE theme ―Utility
and Government services‖ (US).

This subtheme is described in the INSPIRE Feature Concept Dictionary as follows:

“Utility services/networks: Physical construction for transport of defined products: These may include
pipelines for transport of oil, gas, water, sewage or other pipelines. Transmission lines may include
electrical, phone, cable-TV or other networks. Transmission lines for both land and at sea/water (bottom)
is important. All kinds of transmission systems have nodes and are linked to facilities for production and
treatment of different kinds of products. Despite being heavily interlinked, the themes in INSPIRE are
treated separately – the production and treatment facilties are treated mainly in the theme production and
industrial facilities. Transmission systems may be of different kinds;
 Oil and gas pipelines: Major lines from oil and gas fields/extraction areas and storage sites.
Important production and treatment facilities of such resources is linked to a such a transport
network, such as nuclear power stations, power stations, transformer stations and oil tanks.
GISCO, Energy/ industry authorities, Companies
 Water pipelines: Location of water pipelines – large and local network. Large transmission lines are
of interest here. Linked to production facilities for water for consumption/processes. Irrigation
lines treated separately under agricultural facilities. Water supply institutions, Utilities/ health
 Sewage pipelines: Sewage network, linked to sewerage facilities. Major lines of interest here.
Utilities
 Transmission lines- electrical: Data set showing larger transmission lines for electricity, both at land
and sea. The location of lines is important knowledge for the energy sector itself, land use
planners, construction, fisheries for sea cables. Parts of the information important in low flight
hindrance databases. Large: national energy/industry institutions. Local authorities, Companies
 Transmission lines-phone/ data/cable-TV: Location of phone/ data: Rough data needed in land
planning. Important transmission nodes, e.g. antennas, may be seen as part of the network. The
cables placement can conflict other natural resource utilization activities, e.g. fisheries. Technical
data accuracy for local level Companies

Rough pipeline and utility service databases exist at European level, e.g. GISCO database with scale
1:1.000.000. Data within countries is non-homogenous. There are examples of national portals warning
on construction, distributing maps/data on location of pipelines. At local and regional level the
responsibility of government offices or different operators/ firms. In some countries there are national
portals for information about cables etc. in construction work.‖

B.1.2 Use case description: Use case TWG_US_UN_KLIP

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 136

Part 1: UML use case diagram

Perform plan request Send plan request

Cables and lines

information portal
Confirm plan request Define area of work
Plan applicant Managing Authoristies of Cables and Lines

Send plans

Part 2: Narrative explanation of the use case

The cables and pipes information portal (called KLIP) has been designed to unlock the information
concerning cables and pipelines. This information is available with the managing authorities of the cables
and pipes. The purpose of the information portal is to avoid excavation damage. Excavation damage may
occur when a contractor digs and hits a cable or pipe. When a contractor hits a cable or pipe, this can
cause environmental problems. When a sewage pipeline is hit, wastewater can flow into the environment.
Also damaging oil, gas and chemical pipelines can cause severe environmental problems. When a water
pipeline is hit, drinking water can get contaminated. Damaging an electricity cable poses also a big health
risk for the people in the direct neighborhood. Therefore this KLIP portal is very important.

When a contractor plans excavation works he/she sends a plan request to the cables and pipes
information portal. The information portal checks which managing authorities of cables and pipes are
present in this area, and forwards the request to the managing authorities that are present in the area.
This can be managing authorities of oil, gas and chemicals pipelines, water pipelines, sewage pipelines,
transmission cables – electrical, telecommunication cables - phone/data/cable tv, etc. - and heating
pipelines.

The cables and pipes information portal sends a confirmation to the contractor who asked for the plans.
The managing authority checks if they have indeed cables and/or pipes in the defined area. The relevant
plans in this area are selected. The managing authority sends the selected plans by mail. After the
contractor has received the plans, he can start the works.

Part 3: Detailed, structured description of the use case

Use Case Description

Name Cables and pipes information portal
Priority <high/medium/low>
This information portal has been designed to unlock the information concerning
cables and pipes. This information is available with the managing authorities of
the cables and pipes. The purpose of the information portal is to avoid excavation
Description damage.
The managing authorities of cables and pipes indicate the zones where they
Pre-condition manage cables and pipes.
Flow of Events - Basic Path
Step 1 The contractor goes to the information portal and defines the area of work.
The information portal checks which managing authorities of cables and pipes are
Step 2 present in this area and sends a request to these managing authorities.
Step 3 The information portal also sends a confirmation to the contractor.
The managing authority checks if they have indeed cables and/or pipes in the
Step 4 defined area. The relevant plans in this area are selected.
The managing authority sends the selected plans by mail. After the contractor has
Step 5 received the plans, he can start the works.

Flow of Events - Alternative Paths

Step 6 In future View Services will be provided instead of paper maps
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 137

Post-condition The contractor can start working in the area of work.

Data source: Oil, gas and chemicals pipelines
Description Location of oil, gas and chemicals pipelines
Data provider Municipalities, private bodies managing the oil, gas and chemicals pipelines
Geographic
scope Europe
Thematic
scope See description
Scale,
resolution Local
Delivery Map, View Services (map layer)
Documentation [Link]
Data source: Water pipelines
Description Location of water pipelines
Data provider Municipalities, private bodies managing the water pipelines
Geographic
scope Europe
Thematic
scope See description
Scale,
resolution Local
Delivery Map, View Services (map layer)
Documentation [Link]
Data source: Sewage pipelines
Description Location of sewage pipelines
Data provider Municipalities, private bodies managing the sewage pipelines
Geographic
scope Europe
Thematic
scope See description
Scale,
resolution Local
Delivery Map, View Services (map layer)
Documentation [Link]
Data source: Heating pipelines
Description Location of heating pipelines
Data provider Municipalities, private bodies managing the heating pipelines
Geographic
scope Europe
Thematic
scope See description
Scale,
resolution Local
Delivery Map, View Services (map layer)
Documentation [Link]
Data source: Electricity cables
Description Location of electricity cables
Data provider Municipalities, private bodies managing the electrical transmission cables
Geographic
scope Europe
Thematic
scope See description
Scale,
resolution Local
Delivery Map, View Services (map layer)
Documentation [Link]
Data source: Telecommunication cables
Description Location of phone/data/cable tv transmission cables
Municipalities, private bodies managing the phone/data/cable tv transmission
Data provider cables
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 138

Geographic
scope Europe
Thematic
scope See description
Scale,
resolution Local
Delivery Map, View Services (map layer)
Documentation [Link]

B.2 Use case for “Administrative and social governmental services”

B.2.1 Introduction
This documents provides two use cases of the subtheme ―Government services‖ (GS) within the INSPIRE
theme ―Utility and Government services‖ (US).

According to (D 2.6, p. 79) the theme and the subtheme respectively is ―A very broad INSPIRE theme
including different kinds of objects …‖.

The subtheme is defined as follows (D 2.6, p. 81):

―Administrative and social governmental services such as public administrations, civil protection, sites,
schools, hospitals. The kinds of sites are commonly presented in governmental and municipal portals and
map system as "point of interest"-data, and may be point-based location of a variety of categories of
municipal and governmental services and social infrastructure.
• police stations,
• fire fighter stations
• hospitals
• health care centres
• care centres for the elderly
• schools and kindergartens
• renovation/ waste delivery sites
• government and municipal offices‖

The given scope and use examples are (D 2.6, p. 82):

―Administrative and governmental service information is being used by the citizen and public information
systems, in government and municipal management actions and in planning. The navigation databases
used in cars commonly include such information.‖

Accordingly to this presetting, the spread of possible use cases is very wide, too. To capture this scope
and to gain a basement for the next steps, the subgroup has decided to define first two generic, high level
use cases. This two use cases may be refined in further work to fulfill special requirements. It should be
mentioned, that the previous requirement survey by the JRC couldn‘t provide any use case for the
subgroup.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 139

B.2.2 Use case TWG_US_GS_Map_case

Part 1: UML use case diagram

Part 2: Narrative explanation of the use case

The data, which represent the scope, are usually used in governmental and municipal portals. The data
are provided as map layers, optional supplemented by some thematic data (WMS GetFeatureInfo
operation). The user (actor) searches for the layer using the functionality of a geoportal, selects the layer,
navigates to a location and views (―consumes‖) the map. POI‘s are displayed as symbols. The actor can
click at a symbol and gets some information to the POI (in case the layer is queryable).

In contrast to the majority of INSPIRE themes, the group of actors is as inhomogeneous as the interfaces
they use. It varies from a GI-expert (PAB officer, private planning office staff, …), who wants to add the
layer in its GIS to a layman, who uses a map application on its mobile phone. This diversity is addressed
by the functionality of the map clients mainly, but has some influence to the data, too:
 The symbols for the POI‘s should be easy to understand.
 The map layer metadata should provide a list of keywords, so that the clients are able to
support search by laymen (in an emergency case search for ―Doctor‖ should find
―Hospital‖, too).
 A minimum of thematic information is necessary for a lot of use cases in detail (e.g. kind
of service, short explanation, contact information, service/office hours, URL, …). Usually
the map applications don‘t include rich WFS clients, so this information should be
provided by the INSPIRE View Service. It has to be mentioned, that the GetFeatureInfo
operation is optional in INSPIRE View Services.

The purposes of use are different, but the flows of events are comparable.

Part 3: Detailed, structured description of the use case

Use Case Description

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 140

Name TWG_US_GS_map_case
Priority depending on the situation high, medium or low
An actor is searching for a service (including government and municipal
offices) for varying purposes and in different situations.
The actor wants to get a map layer, wherein the location of the service is
marked with a symbol.
Description The actor wants to get some further information about the service.
The data have to exist and have to be provided by an INSPIRE View Service,
preferably with the GetFeatureInfo Interface.
Pre-condition The actor uses a map client with a base map.
Flow of Events - Basic Path
Step 1 The actor accesses to a geoportal.
The actor opens a base map and selects a map window (by map navigation,
Step 2 by means of a gazetteer, with the built-in GPS, ...).
The actor selects the map layer "Government services" and a subitem (e.g.
Step 3 "Hospitals").
Step 4 The desired layer is added to the map.
Flow of Events - Alternative Paths
By clicking at the symbol some further information about the service are
Step 5 displayed.
Post-condition none
Data source: POI
Data about "a variety of categories of municipal and governmental services
and social infrastructure." (D 2.3.)
This overall use case requires the type/subtype of the POI, its location (given
as GM_Point), the core attributes (see above) and some other attributes,
depending on the specific use case. A portrayal rule is needed. To support
thin GPS devices, the CRS ―WGS 84 / plate carrée‖ should be available.
Usually the POI's location originally is given as a reference to an
address/building/cadastral parcel. In these cases the reference has to be
Description mapped to coordinates.
Data provider regions, communes, municipalities, private bodies
Geographic scope Europe
Thematic scope see description
Scale, resolution local
INSPIRE View Service (map layer), INSPIRE Download Service (for additional
Delivery information)
Documentation Partly in the documentation of the national base maps.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 141

B.2.3 Use case TWG_US_GS_Data_case

Part 1: UML use case diagram

Part 2: Narrative explanation of the use case

Unlike TWG_US_GD_map_case, the actor in this use case is a GIS user. He needs information about a
service for varying purposes and in different situations and he wants to import the data into a GIS.
Examples are:

 planning of governmental services (location allocation)

 definition of limit values for air pollution
Some government services (kindergartens, schools and hospitals) can be protected by
stricter limit values.
(DIRECTIVE 1999/30/EC of 22 April 1999 relating to limit values for sulphur dioxide,
nitrogen dioxide and oxides of nitrogen, particulate matter and lead in ambient air (Article
4): "Whereas the limit values laid down in this Directive are minimum requirements;
whereas, in accordance with Article 130t of the Treaty, Member States may maintain or
introduce more stringent protective measures; whereas, in particular, stricter limit values
may be introduced to protect the health of particularly vulnerable categories of the
population, such as children and hospital patients;")
([Link]
 emergency management
Use case: A hospital/kindergarten/home for the elderly has to be evacuated: Which other
facility is adequate equipped to host the people?
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 142

 reporting
Some governmental services (schools and hospitals) have to be part of noise maps.
(Directive 2002/49/EC of the European Parliament and of the Council of 25 June 2002
relating to the assessment and management of environmental noise (Annex IV))
([Link]
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 143

Part 3: Detailed, structured description of the use case

Use Case Description

Name TWG_US_GS_data_case
Priority depending on the situation high, medium or low
Description An actor wants to import data about a governmental service into his GIS.
The data have to exist and have to be provided by an INSPIRE Download
Service.
Pre-condition The actor uses a GIS.
Flow of Events - Basic Path
Using a Metadata Information System (Catalog), the actor searches, finds and
Step 1 evaluates the data and the corresponding INSPIRE Download Service.
The actor uses the INSPIRE Downsload Service and imports the data in his
Step 2 GIS.
Flow of Events - Alternative Paths
none
Post-condition The actor is able to process the data for his purpose.
Data source: POI
Data about "a variety of categories of municipal and governmental services and
social infrastructure." (D 2.3.)
The use case requires the POI as feature data. Although a spatial reference by
coordinates is preferable, the reference can be given by a geographic identifier
Description as well. In this case the actor has to use a gazetteer service first.
Data provider regions, communes, municipalities, private bodies
Geographic scope Europe
Thematic scope see description
Scale, resolution local
Delivery INSPIRE Download Service
Documentation Partly in the documentation of the national base maps.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 144

B.2.4 Use Case: SITMAP – Territorial Information System of Málaga Province (Spain)

Part 1: UML use case diagram

Part 2: Narrative explanation of the use case

SITMAP is the territorial information system that Diputación de Málaga (Málaga Province Council) has
developed to both manage its territorial data, Málaga Province municipalities managing those same data
and both of them, as well as general users, querying SITMAP database. This latter is the case that we are
considering within this document, as it implies the use of web services and interfaces.

Moreover topological data, SITMAP database contains a broad set of data referring to utilities and public
28
services. The contents of that set are basically structured accordingly to EIEL requirements, as
approved by the Spanish Ministry for Territorial Policies and Public Administrations (MPT). Nevertheless,
SITMAP database contains also data regarding features which are currently not included within EIEL, but
needed by Diputación de Málaga to manage different services. So SITMAP is broader in scope than
EIEL.

Due to the above explained, this use case can be considered as a paradigmatic example between all of
those that make use of EIEL database as support for local and provincial governments activities
managing, namely ―BDT-EIEL‖ from Diputación de A Coruña or ―SITMUN‖ from Diputación de Barcelona.

Part 3: Detailed, structured description of the use case

Use Case Description

Name TWG_US_GS_SITMAP
Priority depending on the situation high, medium or low
An actor (be her a Local Level Public Sector one, a citizen or an employee from a
company) is searching for territorial data about utilities and services (including
government and municipal offices) for different purposes.
The actor wants to access the database, select a feature type (or a given instance of
a feature type) and, through the appropriate interface, being able of getting some
information about the existence or characteristics of instances location of the
features in the database, or about the relationships between given features in
different classes (e.g.: distance from schools to main roads, schools in a municipality,
Description etc).

28
EIEL: Spanish acronym for “Enquiry on Local Infrastructures and Services”
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 145

The data have to exist and have to be provided by means of an OGC compliant Web
Mapping Service.
The data have to be referenced upon an standard System (WGS84, ED50, ETRS89)
Pre-condition The actor uses a map client with a base map.
Flow of Events - Basic Path
Step 1 The actor accesses to a geoportal.
The actor opens a base map and selects a map window (by map navigation, by
Step 2 meaning of a gazetteer, with the built-in GPS, ...).
The actor selects one map layer (e.g. "Utilities") and a sub-item (e.g. "water supply
Step 3a networks").
Step 4 The desired layer is depicted on the map.
Step 5 The actor clicks on a part of the layer and queries it about its attributes
Step 6 The required attributes are shown in a data window
Step 7 The actor prints the so built map, the contents of the data window or both of them
Flow of Events - Alternative Paths
The actor selects several map layers and sub-items. She may also select layers
being provided by third parties (e.g.: Cadastral parcels or orthoimagery) to add them
Step 3b to the base map as reference information.
Step 4b The desired set of layers are depicted on the map
The actor selects different objects from the active map layers and queries the
Step 5b database about their atributes
The required attributes and the relations between geographical objects are shown in
Step 6b a data window
Step 7 As above
Post-condition none
Data source: Multi-geometry
Data about "a variety of categories of municipal and governmental services and
social infrastructure." (D 2.3.)
This use case, given that it refers to local scales/resolutions, requires different kinds
of geometries to represent the different feature classes, as well as their location (by
Description means of planar or geographic coordinates) and their descriptive attributes.
Data provider Province Council, municipalities, third parties.
Geographic scope Province
Thematic scope see description
Scale, resolution local
INSPIRE View Service (map layer), INSPIRE Download Service (for additional
Delivery information)
TWG US/US_Check-list_UserRequirements_Template_Má[Link]
at CIRCA Library/Drafting Team Folders/Data Specifications/Thematic Working
Documentation Groups/Utility an...ices (US)/TWG US Use cases

B.3 Use case for “Waste Management”

B.3.1 Introduction

Developing Use-Cases is a powerful method for creating information products, which has been adopted
for INSPIRE data specification process. The INSPIRE Methodology for Data Specification Development
(D2.6) foresees a user-driven specification method based on use-case development. This approach has
been followed during the development of the Annex I Data themes and is now followed by the Annex II
and III Thematic Working Groups (TWGs).

Development of common Use-Cases would not only show possible inter-linkages and dependencies
among INSPIRE Data themes, also serve as a real demonstrator of the interoperability of the INSPIRE
data specifications.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 146

This document is related with the development, monitoring and disclosure of waste plans developed by
different Members States, directly or transferred to Regional Governments, following the requirements
stablished by the Directive 2006/12/EC of the European Parliament and of the Council of 5 April 2006
on waste. As resume, this establishes the legislative framework for the handling of waste in the
Community and the obligation for the member states to draw up waste managements plans as part of it.
A more general extract of the Directive and its potential implication

There are several initiatives already accessible that show Geo-referenced information, different thematic
covertures linked, as result of the implementation of these plans. Geographical information is also
attached to other kind of formats where this plans are described.

Some real examples can be acceded here:

[Link]

[Link]
2011%20Waste%20Management%20Plan%20Volume%[Link]

[Link]

[Link]

[Link]
system/planning_minerals_and_waste/waste_planning/waste_local_plan-[Link]

[Link]

There are different approaches to this Use Case (definition, management, publication). In each of them
take relevance different thematic information as is explained.

B.3.2 Use case description: Use case Waste Management Plans and Waste
Shipments.

Part 1: UML use case diagram

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 147

Part 2: Background Legislation

Directive 2008/98/EC sets the basic concepts and definitions related to waste managament, such as
definitions of waste, recycling, recovery. It explains when waste ceases to be waste and becomes a
secondary raw material (so called end-of-waste criteria), and how to distinguish between waste and by-
products. The Directive lays down some basic waste management principles: it requires that waste be
managed without endangering human health and harming the environment, and in particular without risk
to water, air, soil, plants or animals, without causing a nuisance through noise or odours, and without
adversely affecting the countryside or places of special interest. Waste legislation and policy of the EU
Member States shall apply as a priority order the following waste management hierarchy:

Figure.1 Graphical representation of the Waste Hierarchy (not included on the legal document)

Waste management planning is the cornerstone of any national, regional or local policy on waste
management. Indeed, the establishment of a plan allows, taking stock of the existing situation, to define
the objectives that need to be met in the future, to formulate appropriate strategies and identify the
necessary implementation means.

The drawing up of waste management plans is required by EU legislation on waste. The Directive
2006/12/EC on waste sets out the general requirement in Article 7, while specific provisions are laid down
with regard to Hazardous waste in Article 6 of Directive 91/689/EEC and Packaging and Packaging
Waste in Article 6 of Directive 94/62/EC .

Economic growth and globalization have led to a worldwide increase of waste transports across borders,
whether on the road, by railway or ship. These waste movements or "shipments" sometimes involve
hazardous wastes and can pose potential risks to the human health and the environment: Regulation
(EC) No 1013/2006 of the European Parliament and of the Council of 14 June 2006 on shipments of
waste - applicable since 12 July 2007.

Recommendation 16 This information about legal acts was extracted from the European
Commission wed site. For more detailed information you could visit the original
site: [Link]

Part 3: Main Geo-referenced Contents of Waste Plans

Based on the analysis preformed, only have been referred the potential chapters or parts in which
geographic information could be included and in consequence described as part of the Use Cases:
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 148

The most common administrative level of applicability is at National and Regional. Usually the National
level set the guidelines to the Regional and it provides aggregated information of them, following the
request of the directive, to be sent to the Commission (Art.35.2)

1. Regional Overview Description: This is usually a common chapter for all the projects that take
place over a delimited territory. In general is focus to describe the territory covered by the plan from
different points of view (Environmental, Physical, Economic, demographic, …). This involves links
with different INSPIRE TWGs in two main ways:

a. As source of information for the definition of the plan (Art.1.37)

b. As base reference information to identify the Network over the territory (Art.31)
c. As reference for the publication of related indicators (Art.35.2)

Examples of information required and related with other TWG that could be included on this chapter is:

Geology - Hydrogeology (Water Quality Management Plans)

 Groundwater Vulnerability
 Groundwater Protection Scheme
 Groundwater Usage
Hydrography
Mineral Resources
Transport Networks Infrastructure
 Road Network
 Rail Network
 Ports
Utilities and Governmental Services
 Water Supply
 Sewerage Treatment Plants
 Health Care Services
Population and Settlement
 Population
 Household Numbers
Economic Structure and Activities
 Agriculture
 Commercial Activity
 Industrial Activity
Statistical Units
 Waste Production Indicators.
 Waste Processing Indicators.
Production and Industrial Facilities.
Agricultural and Aquaculture Facilities.
Land Use
Land Cover
Restriction Areas
Risk Zones.

2. Waste Inventory: This part of the Plan should be focus on the source‘s description and categories of
waste that are managed on the areas included under the plan. Potentially should include at least:

Data Sources: following the legislation, information referred to producers of waste is not mandatory
depending of the quantity and classification of the waste (Art. 1.15). Anyway some information about it
could be provided at different levels of Geographical detail, from Installations (detailed geo-referenced
information detailed by activities that generate waste) to Global (at regional level, agglomeration or NUT
Region). Different TWG could be related as providers of information.

 Household and Commercial Waste

 Industrial Waste
 Mining Waste
 Agricultural Waste Arising
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 149

 Ash and other incineration waste

 Contaminated Soil
 Construction and Demolition Waste
 Healthcare Waste
 Waste Electrical and Electronic Equipment (WEEE)
 Batteries
 Waste Oil
 PCBs
 Tyres
 End of Life Vehicles (ELV‘s)

Waste Movements
 Inter-Regional Waste Movement
 Exports of waste

All this chapters and descriptions can be linked to geographical entities, from Facilities to Statistical or
reporting Areas.

3. Management Plan: Chapter focus on the actions to be proposed by the plan in order to improve the
related indicators, based on the hierarchy (Infrastructure to be developed, Actions, Improvements…).
The definition of these indicators could be related with geographical information from the Statistical point
of view.

 Prevention and Minimization

 Recovery/Recycling/Reuse
 Energy Recovery
 Waste Disposal
 Waste Collection
 Sludge Management
 Hazardous Waste
 Waste Planning and Data Collection

4. Waste Management Arrangements (Network): Chapter focused on the Waste Collection Facilities
and Existing Waste Management Facilities Inventory. It should include apart the geo-referenced location,
detailed information about the specific indicators related with the operation and activities that take place
on them.
 Bring Sites.
 Recycling Centres.
 Transfer Stations.
 Landfills
 Operational EPA Licensed Waste Management Facilities
 Waste Permitted Facilities
 Licensing of Unauthorised Waste Disposal Site
 Others.

Part 4: Detailed, structured description of the use case

Use-Case: Waste Infrastructure Mapping

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 150

Use Case Description

Generic Waste Infrastructure mapping could be accessible for many different
actors from Citizens to European Institutions. It could be required from
analytical or reporting purposes to general consultancy information.
Name
Actually, this is information is provided by several Public Administrations in
different supporting formats, generally including some kind of geo-referenced
information, and being used for many different purposes.

Priority High / Medium

A data provider (Generally Public Authority but not exclusively) or modeler

will present information about the emplacement of Waste Infrastructures and
Description their related information (Activities, Waste Capacities, Operations,..) in a
spatial context to a wider community of potential interested stakeholders.

The representation of all main waste cycle related elements, from the
Socioeconomic of the region to which the plan apply to the position of the
Waste facilities (all typologies including landfills or valorization plants)
included on the waste network is needed to provide a map for orientation and
to understand spatial relationships.

Feature classification may be required as reference data or defined rules to

Pre-condition choose reference elements (features, dimensions).

Portrayal: Generalization and symbols rules for reference data and waste
facilities related information

Alternatively a set of pre-defined raster data. Reference maps could be

specified as context.

Flow of Events – Basic Path

Public Authority defines the purpose of the information to be
provided and the Thematic covertures (Bring Sites, Recycling
Step 1. Facilities, Statistical Information, Landfill Locations, Waste
Production, Statistical Information about Waste,… ).

Complementary information: maps (SDI/ view service …) and for

Environmental, Physical and Human related information such as
Step 2 Agglomerations, Urban Planning, Statistical information, Protected
Sites, Species Distribution, etc

Several objects and thematic covertures are requested by the

Waste Plan Manager for reference data at specific resolutions
(Name and position of the urban and environmental elements,
Step 3 Production Sites, GIS-layer with topographic elements etc.) and
Waste Infrastructures emplaced over the territory. Complementary
information and classification criteria are of special relevance.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 151

Use Case Description

Generalization and symbol assignment rules should be applied,
suitability waste infrastructure related information for each purpose
Step 4 should be checked by a competent authority to avoid false
statements with respect to conclusions.

Step 5 Data provider delivers requested layers

When thematic layers containing the same information from

different providers there may be a requirement to manipulate data
Step 6 before merging, analyzing etc. (e.g. recalculation of values,
classes)

Flow of Events – Alternative Paths

Request, concurrent with delivery, a pre-defined target data model
Step 3 (e.g. features, values) to support merging, harmonization etc.

Step 4. Pre-defined reference map selection

Delivery of seamless and as far as possible harmonized requested

Step 5 layer

Layers coming from different thematic databases should be merged

Post-condition to produce the reference map: e. g. Waste Infrastructures Network
level information and verified by a competent authority.

Data source: Thematic information for example relating to environmental

aspects
For example Restricted Areas, Soil, Species Distribution, Land
Description Use.

Thematic Data Providers, geo-referenced information should be

Data provider harmonized.

Geographic Various (Pan-European, cross-border, national, regional, local)

scope
Useful to answer waste question (related for example with capacity
Thematic scope or the nearest places to transfer the waste). Urban Planning.

Scale, resolution Various (depends on the purpose)

Delivery GIS-Raster files, GIS-Vector-files, GML-files, WFS

Documentation Metadata, Model description

Use Case: Waste Plan Definition

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 152

Waste Plans as described in Directive 2006/12/EC.

The different aspects to be described or having into account during the

process could be:

o Territory Description: Base information focus on describing the territory

covered by the plan from different points of view (Environmental, Physical,
Socio-Economic, Demographic, …). This involves links with different
INSPIRE TWGs in two main ways:

 As source of information for the definition of the plan (Art.1.37)

Name  As base reference information to identify the Network over the territory
(Art.31)
 As reference for the publication of related indicators (Art.35.2)

o Waste Infrastructures Inventory: This part of the Plan should be focus on

the source‘s description and categories of waste that are managed on the
areas included under the plan.

o Waste Management Arrangements (Network): Chapter focused on the

Waste Collection Facilities and Existing Waste Management Facilities
Inventory. It should include apart the geo-referenced location, detailed
information about the specific indicators related with the activities,
permissions and capacities for each of them:

Priority High

For the purposes of the Waste Directive, Waste Plans maps must
show the geographic area covered by the plan with the distribution
of the Waste Infrastructure (Pass, Actual and Projected) and the
potential description of their impact on the environment.

The rates of treatment capacity in relation with the amount of waste

generated (potentially received) and the operational descriptions.

Description
Planning of future scenarios and improvements on the indicators.

Background information for spatial orientation is needed.

A land use planner may have to refer to these in the definition of an

area for development of a certain type relating to Member State
planning regulation.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 153

Collection and composition of basic data (hydrological,

environmental data, population, land use, etc); determination of
modeling-software (1D, 2D or couplings, 3D)

Feature classification as reference data or defined rules to choose

reference elements (features, dimensions).
Pre-condition
Portrayal: Generalisation and symbol assignment rules for reference
data and waste infraestructures related information

Another possibility could be to have a set of pre-defined reference

maps as raster data.

Flow of Events – Basic Path

Screen, check and analyze existing material (analog and digital

Step 1. information)

Describe the Area from different points of view.

Step 2
General Description: Administrative (Socio-Economic) and
Geophysical.

Preliminary Waste Facilities Network: identify databases of registers

and unregistered activities that are related with the waste cycle of life.
Geo-referenced or not.
Step 3
Identify the Waste Facilities by categories of Waste, Capacity of
Process and Technical Installations or Treatments.

Calculate the geographical area which could be covert under

different scenarios of waste generation. Rates and Statistical
information.

Step 4 Evaluation of improvements by different periods based on the

Hierarchy established as waste best practices.

For each scenario: Prepare alternatives (projection of new Waste

Infrastructures, Waste trans-border Movements estimations)

Step 5 Define most appropriate map scale(s), definition of colors, symbols

Combine relevant thematic information with topographic reference

Step 6 information to build-up Waste Infrastructures Maps.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 154

Data sources: Legally Required information relating to Waste Plans

Carried out for different scenarios:

1. Authorized registration of actors related with Waste Treatment

and transaction of movements derived from the legislation
requirements.

Description
2. Statistical Information related with the waste generation capacity
in relation with the human activity (industrial, particular consumption,
agricultural, …)

2. Described information in reference with potential entities damaged

by the emplacement of this kind of activities.

Competent authorities (e.g. Regional Governments, Registered

Data provider Establishments), Mapping agencies, Meteorological Services

Geographic In terms of INSPIRE: Pan-European, cross-border, national,

scope regional, local

Thematic scope Spatial information supporting Waste Plans developments

Scale, resolution Generally 1:2.500 – 1.10.000 for detailed maps provided by MS.

Delivery GIS-Vector files or GML-files, WMS

Metadata, model description (it is very important to describe

precisely the specification that form the boundary of the simulation
Documentation used for scenarios because in terms of locations, conditions in the
treatment (installations) there are an infinite number of possibilities)

Data source: Topographic Reference Data

For example Restricted Areas, Soil, Species Distribution, Land Use,

Description Land Cover, Transport and Hydrographic Networks, Statistical Units
and Population Distribution, Health and safety.

Thematic Data Providers, geo-referenced information should be

Data provider harmonized.

Geographic Various (Pan-European, cross-border, national, regional, local)

scope
Useful to define (Public Administration or companies delegated on
Thematic scope behalf of them) and communicate Waste Plans definition (Public
Administration Web-portals, Documents).

Scale, resolution Various (depends on the purpose)

Delivery GIS-Raster files, GIS-Vector-files, GML-files, WFS

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 155

Documentation Metadata, Model description

Use Case: Waste Shipments

Regulation (EC) No 1013/2006 of the European Parliament and of the Council

of 14 June 2006 on shipments of waste - applicable since 12 July 2007.

This use case was proposed by the European Union Network for the
Implementation and Enforcement of Environmental Law (IMPEL), an
international non-profit association of the environmental authorities of the EU
Member States.
Name
The purpose of the IMPEL-―Waste Sites‖ project was to exchange information
and best practices on identification, inspection and compliance measures
regarding upstream waste sites that are relevant for illegal waste exports, and
by this to give input to the guidance tools (handbook and field manual) that
are to be developed in the course of the project.

Cartography information provided under INSPIRE was pointed out as a very

useful tools during the different stages in the project.

Priority Medium.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 156

The last years have seen an increase in problematic waste streams

worldwide, notably of electronic waste, end-of-life vehicles and their
components from Europe to Africa. Spot checks of waste shipments in transit
ports and on motorways in the EU can often do no more than uncover the tip
of an iceberg. This situation has prompted waste shipment experts to think
more about targeting the sources of illegal waste streams and the ―upstream‖
facilities where such waste is collected, stored and/or treated before its export
from the EU.

The main objective of the ―Waste Sites‖ project is to identify good practices
and develop a practical guidance tool for the inspection of upstream waste
sites, and for the promotion of compliance with waste law on these sites, by
competent authorities in the IMPEL member countries. More specifically this
Description means:
 Better understanding of problematic waste streams (especially WEEE,
ELVs and their components, plastic waste and a few others) and the
role of upstream waste sites in them,
 Exchange of best practices concerning such waste sites,
 Guidance on site identification, inspection and follow-up, in the form of
a handbook and a field manual on inspections,
 Better collaboration between relevant agencies (environmental
licensing and inspection, police, customs and others) at national and
international level.
Distributed access to information related to Waste Sites, could support all the
objectives proposed by the project.

Information should be accessible and detailed metadata information

Pre-condition provided in order to guarantee its validity because of the sensible
scope to which it would be applied.

Flow of Events – Basic Path

Information about Waste Sites (Emplacement, Treatment

Step 1. Permissions, Process Capacities,..) is collected and served under
INSPIRE

Transport permissions in which information about origin and

destination sites, waste categorizations are requested for waste
Step 2 transport. These documents must be provided by drivers if
requested by public authorities on the way (police, border controls,
portuary authorities).

Based on the information contained on the transport documents,

authorities should be able to verify the existence of the origin and
Step 3 destination sites and its correlation with the waste transported and
the treatment – management capacity and permission in possession
of the Site.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 157

Calculate the geographical area which could be covert under

different scenarios of waste generation. Rates and Statistical
information.

Step 4 Evaluation of improvements by different periods based on the

Hierarchy established as waste best practices.

For each scenario: Prepare alternatives (projection of new Waste

Infrastructures, Waste trans-border Movements estimations)

Data sources:
Legally Required In terms of INSPIRE: Pan-European, cross-border, national,
information regional, local
relating to Waste
Plans
Description Spatial information supporting Waste Sites

Geographic GIS-Vector files or GML-files, WMS

scope
Data provider Generally 1:2.500 – 1.10.000 for detailed maps provided by MS.

Metadata, model description (it is very important to describe

precisely the specification that form the boundary of the simulation
Thematic scope used for scenarios because in terms of locations, conditions in the
treatment (installations) there are an infinite number of possibilities)

Scale, resolution Generally 1:2.500 – 1.25.000 for detailed maps provided by MS.

In the directive there is no specification for Member States, WISE

Delivery will use Google earth and other free available data

Documentation

Data source:
Topographic
Reference Data
For example Restricted Areas, Soil, Species Distribution, Land Use,
Description Land Cover, Transport and Hydrographic Networks, Statistical Units
and Population Distribution, Health and safety.

Geographic Thematic Data Providers, geo-referenced information should be

scope harmonized and periodically updated and mainteined.

Data provider
Various (Pan-European, cross-border, national, regional, local)

Useful to answer waste question (related for example with capacity

Thematic scope or the nearest places to transfer the waste). Urban Planning.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 158

Scale, resolution Various (depends on the purpose)

Delivery GIS-Raster files, GIS-Vector-files, GML-files, WFS

Documentation Metadata, Model description

B.3.3 Cross Thematic Data requirements

TWG Affected? Datasets affected

Administrative Units (AU) Yes Boundaries of administrative units from
the cities to regional and national
borders, including toponyms.

Competent Authorities for waste

infrastructures permissions and
inspections.
Municipalities and Authorities affected
by events
Addresses (AD) Yes Address of competent authorities.
Address of Waste Infrastructures.
Addresses of register producers.
Agricultural and aquacultural facilities Yes Producers registered. Manure
(AF) Producers, Plastic, Oils, Nitratus, …
Area Yes River basin management
management/restriction/regulation Units of management, Landfills
zones and reporting units (AM) restrictions,
Atmospheric Yes The design of Waste Water treatment
conditions+Meteorological plants and Storm ponds are closely
geographical features (AC-MF) connected with weather forecast
systems (severe weather warnings)
Incineration Plants location depends of
Atmospheric simulations.
Landfills are quite susceptible of
movements and lixiviation process.

Bio-geographical regions + Habitats Yes with regards to adverse consequences

and biotopes + Species distribution for environment.
(BR-HB-SD)
Buildings Yes Related/included on the Waste
Treatment Facilities – Stablishments,
Installations.
Cadastral Parcels (CP) Yes Identification of Sites related with
Facilities/Stablishments/Installations.

Coordinate reference systems Yes No specific related requirements. Only

as geographical requirement.
Energy Resources Yes Reservoirs used for energy generation.
Landfill as gas producers.
Environmental Monitoring Facilities Yes Noise pollution, Points of Discharges,
(EMF)
Geographical grid systems ? Population density or similar coverage
information
Geographical names (GN) Yes name of locations/regions included
under the Waste Plan
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 159

TWG Affected? Datasets affected

Geology + Mineral resources (GE- Yes Permeability
MR) Landforms (geomorphology),
Applicability to landfill emplacement.
Mining Activity: Waste producers.
Human Health and Safety (HH) Yes Location of potential detrimental health
effects.

Hydrography (HY) Yes watercourses, river basins

pipelines
sewerage systems.

LandCover (LC) Yes Small-scale comprehensive land-cover

LandUse (LU) Yes residential areas / zones/districts // rural

communities
asset maps
industrial areas
asset maps
agriculture
asset maps

Natural Risk Zones Yes Prevention and Selection criteria for the
establishment of infrastructures.

Production and industrial facilities Yes Register of Producers and Activities that
(PF) handled Specific categories of waste.
Very close related information because
some activities related with the waste
management and processing are
included under their scope. (e.g.
Reccycling).
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 160

TWG Affected? Datasets affected

Protected Sites (PS) Yes cultural heritage
protected areas as defined under article
6 and article 7 2000/60/EC respectively
article 6 2007/60/EC:
- Bathing (= bodies of water
designated as recreational waters,
including areas designated as
bathing waters under Directive
76/160/EEC)
- Birds (= areas as designated for the
protection of wild birds under
Directive 2009/147/EC)
- Fish (= waterbodies as designated
under 2006/44/EC )
- Shellfish (= areas as designated
under Directive 2006/113/EC of the
European Parliament and of the
Council of 12 December 2006 on
the quality required of shellfish
waters (codified version))
- Habitats (= areas as designated for
the protection of habitats under
Directive 97/62/EC)
- Nitrates (=areas as designated
under Directive 91/676//EC)
- UWWT (=sensitive areas which are
subject to eutrophication as
identified in Annex II.A(a) of
91/271/EEC)
- WFD Art. 7 Abstraction for drinking
water (
- Other European
- National
- local

Soil (SO) Yes transmissibility, permeability,

slack water, drainage. Quite important
for Landfills.

Statistical Units + Population Yes Publication of global indicator related

distribution, demography (SU-PD) with Waste treatment. From the
production by categories to ratios of
processing.
TransportNetwork (TN) Yes Transport network assets – road,
railroad, .
Valid in extension related with the waste
transport.
Utility and governmental services Yes Water supply
(US) Sewerage system
Waste Infrastructures and Facilities
Managed by governments
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 161

Annex C
(informative)
Checklists for data interoperability

As mentioned in Annex F of the "―Data Specifications‖ Methodology for the development of data
specifications", the TWG-US identified several user requirements for some sub-themes that are listed
hereunder:

C.1 User requirements for “Utility Networks”

C.1.1 Checklist for Flemish (Belgium) Environment Agency

C.2 User requirements for “Administrative and social governmental services”

C.2.1 Checklist for the Use case TWG_US_GD_map_case (ref. Annex B.1.2)
C.2.2 Checklist for Spanish EIEL Database
C.2.3 Checklist for Málaga (Spain) Province Council
C.2.4 Checklist for French Statistical Environmental Observatory
C.2.5 Checklist for German State‘s Administrations and Organizations concerned with security issues

C.3 User requirements for “Waste Management”

C.3.1 Checklist for Austrian Environmental Data Management System EDM
C.3.2 Checklist for Piemonte (Italy) Regional Waste Information System

Several tables, based on Annex F of the "“Data Specifications” Methodology for the development of data
specifications" framework, have been developed, but due to the size of the current document, such
requirement information will not be provided directly within the data specification.
Anyway, interested persons can contact the TWG members to get it if wanted.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 162

Annex D
(informative)
ServiceTypeValue codelist

Main group First level Second level COFOG

public
administration
office
general administration office
specialized administration office

public order
GF03
and safety
administration for public order and
safety
police service GF0301
fire-protection service GF0302
fire station
siren
hydrant
anti-fire water provision
fire detection and
observation site
rescue service
rescue station
rescue helicopter landing site
marine rescue station
civil protection site
emergency call point
standalone First Aid equipment
defence
barrack
camp

environmental
GF05
protection
administration for environmental
protection
environmental education centre

health GF07
administration for health
medical products, appliances and
GF0701
equipment
outpatient service GF0702
general medical service GF070201
specialized medical services GF070202
paramedical service GF070204
hospital service GF0703
general hospital
specialized hospital
nursing and convalescent
GF070304
home service
medical and diagnostic laboratory
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 163

Main group First level Second level COFOG

education GF09
administration for education
early childhood education
primary education
lower secondary education
upper secondary education
post-secondary non-tertiary
GF0903
education
short-cycle tertiary education
bachelor or equivalent education
master or equivalent education
doctoral or equivalent education
education not elsewhere classified
subsidiary services to education GF0906
social
GF10
protection
administration for social protection
specialized service of social
protection
service for families and children
housing GF1006
child care service
charity and counselling

Items in red are extracted from the COFOG listing

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 164

Annex E
(informative)
Portrayal analysis

Unfortunately no European-wide accepted standard for map symbolisation exists, which could be applied
for the more than 50 different service types of the administrative and social governmental services
application schema.
29
In a bachelor thesis [Kaden 2011 ] the great diversity of existing symbols in European geoportals and
printed maps are shown. Figure E.1 contains some symbols, which are used for the portrayal of police
stations:

Figure E.1: Map symbols for police stations used in European geoportals and maps
(sources see [Kaden 2011])

Based on this survey, the TWG US has abstained from proposing a common style for the subtheme
Governmental Services. The provision of a harmonized, widely accepted cartographic symbology of such
a broad scope wasn't seen as a realistic aim. Instead of that a fine-grained layer structure according to
the items of the ServiceTypeValue code list has been proposed (see chapter 11.1.1).

29
[Kaden 2011]
Nancy Kaden: ―Spezifikation von Darstellungsregeln für das INSPIRE-Thema "Versorgungswirtschaft und
staatliche Dienste" (Bachelor Thesis)
[Link]
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 165

Annex F
(informative)
Extended Utility Networks

F_1 Application schema “Extended Utility Networks”

F_1.1 “Common Extended Utility Networks Elements” application

schema
F_1.1.1 UML Overview
class Extended Utility Networks - Extended Common Ty...

+pipes
«voidable»
0..* UtilityLink SequenceOrLink UtilityLink SequenceOrLink UtilityNodeContainer UtilityNodeContainer UtilityNodeContainer
+ducts
UtilityLink SequenceOrLink «featureType» «featureType» «featureType» «featureType» «featureType»
«voidable»
«featureType» Common Core Utility Common Core Utility Common Core Utility Common Core Utility Common Core Utility
+pipes 0..*
Common Core Utility +cables Network Elements::Pipe Network Elements::Duct Network Elements:: Network Elements::Pole Network Elements::
Network Elements::Cable «voidable» Manhole Cabinet
0..* «voidable» 0..* «voidable» «voidable»
+cables + pipeDiameter: Measure + ductWidth: Length + poleHeight: Length
«voidable» + pressure: Measure [0..1]
0..*

«featureType»
Common Extended «featureType»
Utility Network Common Extended Utility Network Elements:: «featureType»
«featureType» «featureType»
Elements:: ManholeExtended Common Extended
Common Extended Utility Network Common Extended Utility Network
CableExtended UtilityNodeContainer Utility Network Elements:
Elements::PipeExtended Elements::DuctExtended
«voidable» «featureType» :CabinetExtended
«voidable» + manholeCoverLength: Length
«voidable» «voidable» Common Extended Utility Network Elements::
+ capacity: Measure + manholeType: ManholeTypeValue «voidable»
+ pipeCoatingType: PipeCoatingTypeValue + ductCasingType: DuctCasingTypeValue PoleExtended
+ manholeCoverOpeningType: ManholeCoverOpeningTypeValue + cabinetHeight: Length
+ pipeMaterialType: codevalue + ductType: DuctTypeValue
+ manholeCoverWidth: Length «voidable» + cabinetLength: Length
+ pipeShapeType: PipeShapeTypeValue + columns: Integer
+ manholeCoverShapeType: ManholeCoverShapeTypeValue + poleType: PoleTypeValue + cabinetWidth: Length
+ rows: Integer
+ spacer: Length + manholeShaftAccessType: ManholeShaftAccessTypeValue + poleMaterialType: PoleMaterialTypeValue
+ manholeShaftMaterialType: ManholeShaftMaterialTypeValue + poleFoundationType: PoleFoundationTypeValue
Pipe & Duct Enumerations + manholeShaftHeight: Length + poleDiameter: Length
+ manholeShaftLength: Length + hasAnchorGuy: Boolean
+ manholeShaftWidth: Length + hasPushBrace: Boolean
+ hasRiser: Boolean
«codeList»
Common Extended Utility Network Elements::
DuctTypeValue

Pole Enumerations

Manhole Enumerations
«codeList»
Extended Electricity:: «codeList»
«codeList»
ElectricityCableConductorMaterialTypeValue:: Common Extended Utility Network Elements::
Common Extended Utility Network Elements::
DuctCasingTypeValue PoleTypeValue
ManholeShaftAccessTypeValue
+ concrete + hFrame
+ climbingIron
+ directBuried + other
+ ladder
+ none + standard
+ ladderFittings
+ streetLight
+ noAccess
+ tower
+ stairs
+ veryHighVoltage
+ other

«codeList» «codeList» «codeList»

Common Extended Utility Network Elements:: Common Extended Utility Network Elements:: Common Extended Utility Network Elements::
PipeShapeTypeValue ManholeShaftMaterialTypeValue PoleMaterialTypeValue
+ arched + cement + aluminiuim
+ circle + concrete + composite
+ cunette + fiberglass + concrete
+ other + masonry + fiberglass
+ rectangle + other + other
+ square + plasteredMasonry + steel
+ trapezoid + plastic + wood
+ oval + precastConcrete
+ ovoid + reinforcedPolyester

«codeList»
«codeList» Common Extended Utility Network Elements::
«codeList» Common Extended Utility Network Elements:: PoleFoundationTypeValue
Common Extended Utility Network Elements:: ManholeCoverOpeningTypeValue
PipeCoatingTypeValue + extraDeepInEarth
+ bolts + normallyInEarth
+ CPVC + hooks + normalWithConcreteBackfill
+ epoxy + lever + onConcreteFoundation
+ HDPE + socket + other
+ none + other
+ other
+ PVC
«codeList»
Common Extended Utility Network Elements::
ManholeCoverShapeTypeValue
«codeList» + circle
Common Extended Utility Network Elements:: + composite
PipeMaterialTypeValue + grid
+ other
+ ABS
+ rectangle
+ asbestos
+ square
+ blackIron
+ blackSteel
+ castIron
+ clay
+ compositeConcrete «codeList»
+ concrete Common Extended Utility Network Elements::
+ CPVC ManholeTypeValue
+ FRP + handhole
+ galvanizedSteel + manhole
+ masonry + vault
+ other
+ PB
+ PE
+ PEX
+ PP
+ prestressedReinforcedConcrete
+ PVC
+ reinforcedConcrete
+ RPMP
+ steel
+ terracota
+ wood

Figure 1 – UML class diagram: Overview of the “Extended Utility Networks - Extended Common
Types”
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 166

F_1.2 “Extended Electricity Network” application schema

F_1.2.1 UML Overview

class Extended Electricity Netw...

Cable
«featureType»
Core Electricity Network::
ElectricityCable

«voidable»
+ operatingVoltage: Measure
+ nominalVoltage: Measure

«featureType»
ElectricityCableExtended

«voidable»
+ electricityCableType: ElectricityCableTypeValue
+ electricityCableConductorMaterialType: ElectricityCableConductorMaterialTypeValue
+ conductorSize: Length

«codeList» «codeList»
ElectricityCableTypeValue ElectricityCableConductorMaterialTypeValue
+ P_OH_Single + aluminium
+ P_OH_Three + copper
+ P_OH_Two + steel
+ P_UG_Single
+ P_UG_Three tags
+ S_OH_Single asDictionary = true
+ S_OH_Three extensibility = any
+ S_UG_Single vocabulary = [Link]
+ S_UG_Three xsdEncodingRule = iso19136_2007_INSPIRE_Extensions
+ streetLightConductor
+ other

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 2 – UML class diagram: Overview of the “Core Electricity Networks”

F_1.2.2 Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Extended Electricity

Scope Extended Electricity
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Extended Electricity
Types defined in the feature catalogue

Type Package Stereotypes Section

ElectricityCableConductorMaterialTypeValue Extended Electricity «codeList» [Link].1
ElectricityCableExtended Extended Electricity «featureType» [Link].1
ElectricityCableTypeValue Extended Electricity «codeList» [Link].2
[Link]. Spatial object types
[Link].1. ElectricityCableExtended
ElectricityCableExtended
Name: Electricity cable (Extended)
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 167

ElectricityCableExtended
Subtype of: ElectricityCable
Definition: Extends the ElectricityCable feature in the Core Utility Network Profile.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: electricityCableType

Value type: ElectricityCableTypeValue

Definition: Type of electricity cable.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Technical Guidance (recommendation)
Attribute: electricityCableConductorMaterialType

Value type: ElectricityCableConductorMaterialTypeValue

Definition: Cable conductor material type.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Technical Guidance (recommendation)
Attribute: conductorSize

Value type: Length

Definition: Size of the conductor.
Multiplicity: 1
Stereotypes: «voidable»

[Link]. Code lists

[Link].1. ElectricityCableConductorMaterialTypeValue
ElectricityCableConductorMaterialTypeValue
Name: Electricity cable conductor material type value (Extended)
Definition: Codelist containing a classification of electricity cable conductor material types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

[Link].2. ElectricityCableTypeValue
ElectricityCableTypeValue
Name: Electricity cable type value (Extended)
Definition: Codelist containing a classification of electricity cable types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

[Link]. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

[Link].1. ElectricityCable
ElectricityCable
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 168

ElectricityCable
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Core Electricity Network [Include reference to the document that includes
the package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: A utility link or link sequence used to convey electricity from one location to another.

[Link].2. Length
Length
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

F_1.3 “Core Oil-Gas-Chemicals Network” application schema

F_1.3.1 UML Overview

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 169

class Extended Oil, Gas & Chemicals Netw...

Pipe
«featureType»
Core Oil-Gas-Chemicals Network::OilGasChemicalsPipe

«voidable»
+ oilGasChemicalsProductType: OilGasChemicalsProductTypeValue [1..*]

«featureType»
OilGasChemicalsPipeExtended

«voidable»
+ oilGasChemicalsPipeType: OilGasChemicalsPipeTypeValue
+ averageVolume: Volume
+ maxCapacity: Measure

«codeList»
OilGasChemicalsPipeTypeValue

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

OilGasChemicalsProductTypeValue
«codeList»
Core Oil-Gas-Chemicals Network::OilGasChemicalsProductTypeBaseValue
+ liquefiedNaturalGas
+ methane
+ naturalGas
+ naturalGasAndTetrahydrothiophene
+ nitrogenGas
+ residualGas
+ accetone
+ air
+ argon
+ butadiene
+ butadiene1,3
+ butane
+ c3
+ carbonMonoxide
+ chlorine
+ compressedAir
+ crude
+ dichloroethane
+ diesel
+ ethylene
+ gasFabricationOfCocs
+ gasHFx
+ gasoil
+ hydrogen
+ isobutane
+ JET-A1
+ kerosene
+ liquidAmmonia
+ liquidHydrocarbon
+ multiProduct
+ MVC
+ nitrogen
+ oxygen
+ phenol
+ propane
+ propyleen
+ propylene
+ raffinate
+ refineryProducts
+ saltWater
+ saumur
+ tetrachloroethane
+ unknown
+ empty

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 3 – UML class diagram: Overview of the “Core Oil-Gas-Chemicals Networks”

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 170

F_1.3.2 Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Extended Oil-Gas-Chemicals

Scope Extended Oil-Gas-Chemicals
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Extended Oil-Gas-Chemicals
Types defined in the feature catalogue

Type Package Stereotypes Section

OilGasChemicalsPipeExtended Extended Oil-Gas-Chemicals «featureType» [Link].1
OilGasChemicalsPipeTypeValue Extended Oil-Gas-Chemicals «codeList» [Link].1
[Link].3. Spatial object types
OilGasChemicalsPipeExtended
OilGasChemicalsPipeExtended
Name: Oil, gas and chemicals pipe (Extended)
Subtype of: OilGasChemicalsPipe
Definition: Extends the OilGasChemicalsPipe feature in the Core Utility Network Profile.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: oilGasChemicalsPipeType

Value type: OilGasChemicalsPipeTypeValue

Definition: Type of oil/gas/chemicals pipe.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Technical Guidance (recommendation)
Attribute: averageVolume

Value type: Volume

Definition: Average volume of the pipe.
Multiplicity: 1
Stereotypes: «voidable»
Attribute: maxCapacity

Value type: Measure

Definition: Maximum capacity of the pipe.
Multiplicity: 1
Stereotypes: «voidable»

[Link].4. Code lists

OilGasChemicalsPipeTypeValue
OilGasChemicalsPipeTypeValue
Name: Oil, gas and chemicals pipe type value (Extended)
Definition: Codelist containing a classification of oil, gas and chemical pipe types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 171

[Link].5. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

Measure
Measure
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

OilGasChemicalsPipe
OilGasChemicalsPipe
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Core Oil-Gas-Chemicals Network [Include reference to the document that
includes the package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: A pipe used to convey oil, gas or chemicals from one location to another.

Volume
Volume
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

F_1.3.3 INSPIRE-governed code lists for the “Core Oil-Gas-Chemical”

Not additional Code Lists

F_1.3.4 Externally governed code lists for the “Core Oil-Gas-Chemical”

OilGasChemicalPipeTypeValue code lists included in the “Core Oil-Gas-Chemical Networks” application

schemas is empty and can be extensible by any external codelist. The OilGasChemicalPipeTypeValue is
an internal code list which is also extended from the empty OilGasChemicalPipeTypeValue code list.

F_1.4 “Core Sewer Network” application schema

F_1.4.1 UML Overview

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 172

class Extended Sewer Netw...

Pipe
«featureType»
Core Sewer Network::SewerPipe

«voidable»
+ sewerWaterType: SewerWaterTypeValue

«featureType»
SewerPipeExtended

«voidable»
+ sewerPipeType: SewerPipeTypeValue
+ averageVolume: Volume [0..1]
+ maxCapacity: Measure [0..1]

«codeList»
SewerPipeTypeValue SewerWaterTypeValue
«codeList»
+ LL
Core Sewer Network::SewerWaterTypeBaseValue
+ LL_Combination
+ LL_Commercial + combined
+ LL_Domestic + reclaimed
+ LL_Irrigation + sanitary
+ LL_Storm + storm
+ ML
+ ML_GM tags
+ ML_GM_Collector asDictionary = true
+ ML_GM_Culvert extensibility = any
+ ML_GM_InLineStorage vocabulary = [Link]
+ ML_GM_Interceptor xsdEncodingRule = iso19136_2007_INSPIRE_Extensions
+ ML_GM_InvertedSiphon
+ ML_GM_OpenChannel
+ ML_GM_Outfall
+ ML_GM_Overflow
+ ML_GM_Tunnel
+ ML_PM
+ ML_PM_ForceMain
+ ML_PM_PipeBridge
+ ML_PM_Pressure
+ ML_PM_Vacuum

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 4 – UML class diagram: Overview of the “Core Sewer Networks”

F_1.4.2 Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Extended Sewer

Scope Extended Sewer
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Extended Sewer
Types defined in the feature catalogue

Type Package Stereotypes Section

SewerPipeExtended Extended Sewer «featureType» [Link].1
SewerPipeTypeValue Extended Sewer «codeList» [Link].1
[Link]. Spatial object types
[Link].1. SewerPipeExtended
SewerPipeExtended
Name: Sewer pipe (Extended)
Subtype of: SewerPipe
Definition: Extends the SewerPipe feature in the Core Utility Network Profile.
Status: Proposed
Stereotypes: «featureType»
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 173

SewerPipeExtended
Identifier: null
Attribute: sewerPipeType

Value type: SewerPipeTypeValue

Definition: Type of sewer pipe.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Technical Guidance (recommendation)
Attribute: averageVolume

Value type: Volume

Definition: Average volume of the pipe.
Multiplicity: 0..1
Stereotypes: «voidable»
Attribute: maxCapacity

Value type: Measure

Definition: Maximum capacity of the pipe.
Multiplicity: 0..1
Stereotypes: «voidable»

[Link]. Code lists

[Link].1. SewerPipeTypeValue
SewerPipeTypeValue
Name: Sewer pipe type value (Extended)
Definition: Codelist containing a classification of sewer pipe types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

[Link]. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

[Link].1. Measure
Measure
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

[Link].2. SewerPipe
SewerPipe
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Core Sewer Network [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: A sewer pipe used to convey wastewater (sewer) from one location to another.

[Link].3. Volume
Volume
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 174

Volume
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

F_1.5 “Core Thermal Network” application schema

F_1.5.1 UML Overview

class Extended Thermal Netw...

Pipe
«featureType»
Core Thermal Network::ThermalPipe

«voidable»
+ thermalProductType: ThermalProductTypeValue

«featureType»
ThermalPipeExtended

«voidable»
+ thermalPipeType: ThermalPipeTypeValue

«codeList»
ThermalPipeTypeValue

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

ThermalProductTypeValue
ThermalProductTypeValue
«codeList»
ThermalProductTypeExtendedValue
+ heatingSteam
+ heatingWater
+ coolingWater

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 5 – UML class diagram: Overview of the “Core Thermal Networks”

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 175

F_1.5.2 Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Extended Thermal

Scope Extended Thermal
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Extended Thermal
Types defined in the feature catalogue

Type Package Stereotypes Section

ThermalAppurtenanceTypeExtendedValue Extended Thermal «codeList» [Link].1
ThermalPipeExtended Extended Thermal «featureType» [Link].1
ThermalPipeTypeValue Extended Thermal «codeList» [Link].2
ThermalProductTypeExtendedValue Extended Thermal «codeList» [Link].3
[Link]. Spatial object types
[Link].1. ThermalPipeExtended
ThermalPipeExtended
Name: Thermal pipe (Extended)
Subtype of: ThermalPipe
Definition: Extends the ThermalPipe feature in the Core Utility Network Profile.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: thermalPipeType

Value type: ThermalPipeTypeValue

Definition: Type of thermal pipe.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Technical Guidance (recommendation)

[Link]. Code lists

[Link].1. ThermalAppurtenanceTypeExtendedValue
ThermalAppurtenanceTypeExtendedValue
Name: Thermal appurtenance type value (Extended)
Subtype of: ThermalAppurtenanceTypeValue
Definition: Codelist containing a classification of the extension of thermal appurtenance types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

[Link].2. ThermalPipeTypeValue
ThermalPipeTypeValue
Name: Thermal pipe type value (Extended)
Definition: Codelist containing a classification of thermal pipe types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

[Link].3. ThermalProductTypeExtendedValue
ThermalProductTypeExtendedValue
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 176

ThermalProductTypeExtendedValue
Name: Thermal product type value (Extended)
Subtype of: ThermalProductTypeValue, ThermalProductTypeValue
Definition: Codelist containing a classification of the extension of thermal product types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

[Link]. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

[Link].1. ThermalAppurtenanceTypeValue
ThermalAppurtenanceTypeValue
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Core Thermal Network [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Codelist containing a classification of thermal appurtenances.

[Link].2. ThermalPipe
ThermalPipe
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Core Thermal Network [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: A pipe used to disseminate heating or cooling from one location to another.

[Link].3. ThermalProductTypeValue
ThermalProductTypeValue
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Core Thermal Network [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: Codelist containing a classification of thermal products.

F_1.6 “Core Water Network” application schema

F_1.6.1 UML Overview

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 177

class Extended Water Netw...

Pipe
«featureType»
Core Water Network::WaterPipe

«voidable»
+ waterType: WaterTypeValue

«featureType»
WaterPipeExtended

«voidable»
+ waterPipeType: WaterPipeTypeValue
+ averageVolume: Volume
+ maxCapacity: Measure

«codeList» WaterTypeValue
WaterPipeTypeValue «codeList»
+ LL Core Water Network::WaterTypeBaseValue
+ LL_Commercial + potable
+ LL_Domestic + raw
+ LL_Fire + salt
+ LL_HydrantLaterals + treated
+ LL_Industrial
+ LL_Irrigation tags
+ ML asDictionary = true
+ ML_GM extensibility = any
+ ML_GM_Carrier vocabulary = [Link]
+ ML_GM_InLineStorage xsdEncodingRule = iso19136_2007_INSPIRE_Extensions
+ ML_GM_TransportPipe
+ ML_PM
+ ML_PM_AirRelease
+ ML_PM_BlowOff
+ ML_PM_Bypass
+ ML_PM_ChemicalInjection
+ ML_PM_DistributionMain
+ ML_PM_Interconnect
+ ML_PM_PipeBridge
+ ML_PM_SamplingStation
+ ML_PM_TransmissionMain
+ ML_PM_RawWaterTransport

tags
asDictionary = true
extensibility = any
vocabulary = [Link]
xsdEncodingRule = iso19136_2007_INSPIRE_Extensions

Figure 6 – UML class diagram: Overview of the “Core Water Networks”

F_1.6.2 Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Extended Water

Scope Extended Water
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Extended Water
Types defined in the feature catalogue

Type Package Stereotypes Section

WaterPipeExtended Extended Water «featureType» [Link].1
WaterPipeTypeValue Extended Water «codeList» [Link].1
[Link]. Spatial object types
[Link].1. WaterPipeExtended
WaterPipeExtended
Name: Water pipe (Extended)
Subtype of: WaterPipe
Definition: Extends the WaterPipe feature in the Core Utility Network Profile.
Status: Proposed
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 178

WaterPipeExtended
Stereotypes: «featureType»
Identifier: null
Attribute: waterPipeType

Value type: WaterPipeTypeValue

Definition: Type of water pipe.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Technical Guidance (recommendation)
Attribute: averageVolume

Value type: Volume

Definition: Average volume of the pipe.
Multiplicity: 1
Stereotypes: «voidable»
Attribute: maxCapacity

Value type: Measure

Definition: Maximum capacity of the pipe.
Multiplicity: 1
Stereotypes: «voidable»

[Link]. Code lists

[Link].1. WaterPipeTypeValue
WaterPipeTypeValue
Name: Water pipe type value (Extended)
Definition: Codelist containing a classification of water pipe types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

[Link]. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

[Link].1. Measure
Measure
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

[Link].2. Volume
Volume
Package: INSPIRE Consolidated UML Model::Foundation Schemas::ISO TC211::ISO
19103:2005 Schema Language::Basic Types::Derived::Units of Measure [Include
reference to the document that includes the package, e.g. INSPIRE data
specification, ISO standard or the GCM]

[Link].3. WaterPipe
WaterPipe
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 179

WaterPipe
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Core Water Network [Include reference to the document that includes the
package, e.g. INSPIRE data specification, ISO standard or the GCM]
Definition: A water pipe used to convey water from one location to another.

F_1.7 INSPIRE-governed code lists for the “Extended Utility

Networks” subdomain’s application schemas
The INSPIRE-defined code lists included in this application schema include the values specified in the
tables in this section.

F_1.7.1 Values of code list DuctTypeValue

This codelist is empty

F_1.7.2 Values of code list ElectricityAppurtenanceTypeExtendedValue

Parent
Value Name Definition Description
value
Capacior control is usually done to achieve as many as
possible of the following goals: reduce losses due to
reactive load current, reduce kVA demand, decrease
capacitorCon capacitor Capacitor
customer energy consumption, improve voltage profile,
trol Control control.
and increase revenue. Indirectly capacitor control also
results in longer equipment lifetimes because of reduced
equipment stresses.
connectionBo connection Connection Connection box protects and/or encloses electric circuits
x Box box. and equipment on the ground.
Power distribution is more efficient if operated when the
power factor (PF) is unity. An alternating voltage and the
current causing it to flow should rise and fall in value
Power factor
correctingEq correcting equally and reverse direction at the same instant. When
correcting
uipment Equipment this happens, the two waves are said to be in phase and
equipment.
the power factor is unity (1.0). However, various
inductive effects, such as idle running induction motors
or transformers, can lower the power factor.
Delivery
deliveryPoint delivery Point Point the electric power is being delivered to.
point.
In addition to opening when a fault is detected, dynamic
protective devices also reclose to attempt to re-establish
service. If the fault remains after a prescribed number of
reclosings, the device may lock open the circuit.
dynamic Dynamic Reclosing is designed to reduce or eliminate the effects
dynamicProt
Protective protective of temporary faults.
ectiveDevice
Device device.
NOTE It may include following subtypes: Circuit
Breakers,
Fault Interrupter, Reclosers (Single Phase Hydraulic,
etc.), and Sectionalizers.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 180

Parent
Value Name Definition Description
value
Fuses are used to protect distribution devices from
damaging currents. A fuse is an intentionally weakened
spot in the electric circuit that opens the circuit at a
predetermined current that is maintained for a
fuse fuse Fuse. predetermined amount of time. Fuses are not dynamic in
that they remain open and do not reclose. By
automatically interrupting the flow of electricity, a fuse
prevents or limits damage caused by an overload or
short circuit.
Generator is an alternative, third-party power source
generator generator Generator.
feeding into the electrical network.
Load tap changer represents power transformer controls
that change the primary to-secondary turns ratio of a
transformer winding while the transformer is under load
to regulate the flow of current and minimize voltage drop.
loadTapChan load Tap Load tap Automatic loadtap changers in the power transformer
ger Changer changer. provides voltage control on the substation bus. Control
systems of voltage regulators and tap changing
equipment beyond the substation usually have a line-
drop compensator to simulate voltage drop between the
substation and points in the distribution system.
Electric station represents a building or fenced-in
enclosure that houses the equipment that switches and
modifies the characteristics of energy from a generation
mainStation main Station Main station.
source. Distribution systems include primary feeders
(circuits), transformer banks, and secondary circuits
(overhead or underground) that serve a specified area.
netStation net Station Net station. Net station.
Network transformers connect to the secondary network
through a network protector. Network protector
components may be the circuit breaker, relays, backup
networkProte network Network
fuses and controls required for automatically
ctor Protector protector.
disconnecting a transformer from the secondary network
in response to predetermined conditions on primary
feeder or transformer.
Open point contains information about a variety of
insulated and shielded devices that connect high-voltage
cables to apparatus, including transformers. Separable,
openPoint open Point Open point.
load-break insulated connectors are used with primary
bushings of submersible distribution transformers for
safety. This is known as a dead-front configuration.
Primary meters are installed if commercial customers
elect to have power delivered at distribution voltages,
primary Primary such as 12.5 kV. Residential customers are generally
primaryMeter
Meter meter. billed for kilowatt hours (kWH) used. Commercial and
industrial customers may additionally be billed for
demand charges and power factor charges.
Reclosers and sectionalizers isolate temporary and
permanent faults in electric lines. Reclosers open circuits
(trip) in case of a fault, and reclose after a predetermined
recloser Recloser
recloserElect time. The time-current characteristic, usually expressed
Electronic electronic
ronicControl in a curve, is based on temperature and fuse tolerances
Control control.
and is used to coordinate recloser operations. Reclosers
allow (usually) four trip operations to clear temporary
faults.
Recloser hydraulic control is an intregral part of single-
recloser Recloser
recloserHydr phase reclosers. A trip coil in series with the line is used
Hydraulic hydraulic
aulicControl to sense overcurrent and trip open the recloser contacts.
Control control.
The contacts close after a preset interval.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 181

Parent
Value Name Definition Description
value
Voltage provided by regulators is changed using a tap-
changing switch to adjust the number of secondary
windings. Line load can be regulated from 10 percent
regulatorCont regulator Regulator
above to 10 percent below normal line voltage. Voltage
rol Control control.
regulators that control distribution system voltage are
rated from 2.5 kV to 34.5 grd Y kV. Most feeder
regulators have the 32-step design.
Protective relay systems detect and isolate faults. Time-
delayed phase and ground relays are coordinated with
fuses and reclosers further out on the circuit. They are
relayControl relay Control Relay control. instantaneous units with inverse TCCs to coordinate with
fuses and reclosers further downstream. Relays are
usually set to trip feeder breakers and protect the fuse in
the event of temporary faults beyond the fuse.
Sectionalizers are automatic circuit opening devices that
are installed on the load side of fault-interrupting devices
and count its fault-trip operations. Sectionalizers can be
sectionalizer sectionalizer Sectionalizer set to open after one, two, or three counts have been
ElectronicCo Electronic electronic detected
ntrol Control control. with a predetermined time span. Sectionalizers are used
in conjunction with fuses and reclosers and may have
inrush current restraint features to prevent a false count
when lines are re-energized.
Sectionalizer controls store a pulse counter when the
minimum actuating current drops to zero because a fault
sectionalizer sectionalizer Sectionalizer
is interrupted by the recloser (or other protective device).
HydraulicCon Hydraulic hydraulic
Sectionalizers operate in conjunction with breakers and
trol Control control.
reclosers to lock out fault current after a predetermined
number (usually three) of recloser operations (trips).
A street light (or lamppost, street lamp, light standard, or
lamp standard) is a raised source of light on the edge of
streetLight street Light Street light.
a road, which is turned on or lit at a certain time every
night.
An electrical substation is a subsidiary station of an
electricity generation, transmission and distribution
system where voltage is transformed from high to low or
the reverse using transformers. Electric power may flow
through several substations between generating plant
subStation sub Station Sub station. and consumer, and may be changed in voltage in several
steps. A substation that has a step-up transformer
increases the voltage while decreasing the current, while
a step-down transformer decreases the voltage while
increasing the current for domestic and commercial
distribution.
A switch disconnects circuits within the distribution
network and can be manually or power operated.
Switches are either open or closed. Switches are critical
to the electric distribution system to allow current
switch switch Switch.
interruption to allow system maintenance, redirecting
current in case of emergency, or to isolate system
failures. Switches may be automated and controlled
remotely through SCADA operation.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 182

Parent
Value Name Definition Description
value
Transformers transfer electrical energy from one circuit
to another circuit usually with changed values of voltage
and current in the process.
transformer transformer Transformer.
NOTE Subtypes include: Network, Single Phase
Overhead, Single Phase Underground, Two Phase
Overhead, Three Phase Overhead, Three Phase
Underground, Step, and Power.
Voltage regulators vary the ac supply or source voltage
to the customer to maintain the voltage within desired
limits. Voltage provided by regulators is changed using a
tap-changing switch to adjust the number of secondary
windings. Bypass switches allow a regulator to be
voltageRegul voltage Voltage
removed for normal service without interrupting the
ator Regulator regulator.
downstream load.

NOTE Subtypes include: Single Phase Overhead, Two

Phase Overhead, Three Phase Overhead, Three Phase
Pad-Mounted.
detectionEqui detection
pment Equipment
pointSetting point Setting
Machine Machine
monitoringAn monitoring
dControlEqui And Control
pment Equipment

F_1.7.3 Values of code list ElectricityCableConductorMaterialTypeValue

Parent
Value Name Definition Description
value
aluminium aluminium Aluminium.
copper copper Copper.
steel steel Steel.

F_1.7.4 Values of code list ElectricityCableTypeValue

Parent
Value Name Definition Description
value
P_OH_Single P_OH_ Single Single phase primary overhead.
P_OH_Three P_OH_ Three Three phase primary overhead.
P_OH_Two P_OH_ Two Two phase primary overhead.
P_UG_Single P_UG_ Single Single phase primary underground.
P_UG_Three P_UG_ Three Three phase primary underground.
S_OH_Single S_OH_ Single Single phase secondary overhead.
S_OH_Three S_OH_ Three Three phase secondary overhead.
S_UG_Single S_UG_ Single Single phase secondary underground.
S_UG_Three S_UG_ Three Three phase secondary underground.
streetLightConduct street Light
Street light conductor.
or Conductor
other other Other.

F_1.7.5 Values of code list ManholeCoverOpeningTypeValue

Parent
Value Name Definition Description
value
bolts bolts Bolts.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 183

Parent
Value Name Definition Description
value
hooks hooks Hooks.
lever lever Lever.
socket socket Socket.
other other Other.

F_1.7.6 Values of code list ManholeCoverShapeTypeValue

Parent
Value Name Definition Description
value
circle circle Circle.
composite composite Composite.
grid grid Grid.
other other Other.
rectangle rectangle Rectangle.
square square Square.

F_1.7.7 Values of code list ManholeShaftAccessTypeValue

Parent
Value Name Definition Description
value
climbingIron climbing Iron Climbing iron.
ladder ladder Ladder.
ladderFittings ladder Fittings Ladder fittings.
noAccess no Access No access.
stairs stairs Stairs.
other other Other.

F_1.7.8 Values of code list ManholeShaftMaterialTypeValue

Parent
Value Name Definition Description
value
cement cement Cement.
concrete concrete Concrete.
fiberglass fiberglass Fiberglass.
masonry masonry Masonry.
other other Other.
plasteredMasonry plastered Masonry Plastered masonry.
plastic plastic Plastic.
precastConcrete precast Concrete Precast concrete.
reinforcedPolyester reinforced Polyester Reinforced polyester.

F_1.7.9 Values of code list ManholeTypeValue

Parent
Value Name Definition Description
value
A handhole represents a small hole for the insertion of
handhole handhole Handhole.
the hand for cleaning purposes, etc.
manhole manhole Manhole.
vault vault Vault.

F_1.7.10 Values of code list OilGasChemicalsAppurtenanceTypeExtendedValue

Parent
Value Name Definition Description
value
Pump pump
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 184

Parent
Value Name Definition Description
value
gasStation gas Station
Node node
Compression compression
Terminal terminal
deliveryPoint delivery Point
Frontier frontier
Marker marker
Beacon beacon

F_1.7.11 Values of code list OilGasChemicalsPipeTypeValue

This codelist is empty

F_1.7.12 Values of code list OilGasChemicalsProductTypeExtendedValue

Parent
Value Name Definition Description
value
highCalorificGas high Calorific Gas
liquefiedNaturalGas liquefied Natural Gas
lowCalorificGas low Calorific Gas
methane methane
naturalGas natural Gas
naturalGasAndTetrahydro natural Gas And
thiophene Tetrahydrothiophene
nitrogenGas nitrogen Gas
residualGas residual Gas
accetone accetone
air air
argon argon
butadiene butadiene
butadiene1,3 butadiene1,3
butane butane
c3 c3
carbonMonoxide carbon Monoxide
chlorine chlorine
compressedAir compressed Air
crude crude
dichloroethane dichloroethane
diesel diesel
ethylene ethylene
gasFabricationOfCocs gas Fabrication Of Cocs
gasHFx gasH Fx
gasoil gasoil
hydrogen hydrogen
isobutane isobutane
JET-A1 JET-A1
kerosene kerosene
liquidAmmonia liquid Ammonia
liquidHydrocarbon liquid Hydrocarbon
multiProduct multi Product
MVC MVC
nitrogen nitrogen
oxygen oxygen
phenol phenol
propane propane
propyleen propyleen
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 185

Parent
Value Name Definition Description
value
propylene propylene
raffinate raffinate
refineryProducts refinery Products
saltWater salt Water
saumur saumur
tetrachloroethane tetrachloroethane
unknown unknown
empty empty

F_1.7.13 Values of code list PipeCoatingTypeValue

Parent
Value Name Definition Description
value
CPVC CPVC Collapsed polyvinylchloride (CPVC).
epoxy epoxy Epoxy.
HDPE HDPE High density polyethylene (HDPE).
none none No coating.
other other Other.
PVC PVC Polyvinylchloride (PVC).

F_1.7.14 Values of code list PipeMaterialTypeValue

Parent
Value Name Definition Description
value
ABS ABS Acrylonitrile butadiene styrene (ABS).
asbestos asbestos Asbestos.
Iron without any finish on it, gray-black
blackIron black Iron
in color.
Steel with a surface layer of dark
blackSteel black Steel
coloured iron oxides.
Iron with a high Carbon content
castIron cast Iron
(above 2%).
clay clay Clay.
compositeConcrete composite Concrete Composite concrete.
concrete concrete Concrete.
CPVC CPVC Chlorinated polyvinyl chloride (CPVC).
FRP FRP Fibre reinforced plastic (FRP).
galvanizedSteel galvanized Steel Galvanized steel.
masonry masonry Masonry.
other other Other.
PB PB Polybutylene (PB).
PE PE Polyethylene (PE).
Cross-linked high-density
PEX PEX
polyethylene (PEX).
PP PP Polypropylene (PP).
prestressed
prestressedReinfor
Reinforced Prestressed reinforced concrete.
cedConcrete
Concrete
PVC PVC Polyvinyl chloride (PVC).
reinforcedConcrete reinforced Concrete Reinforced concrete.
RPMP RPMP Reinforced polymer mortar (RPMP).
steel steel Steel.
terracota terracota Terracota.
wood wood Wood.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 186

F_1.7.15 Values of code list PipeShapeTypeValue

Parent
Value Name Definition Description
value
arched arched Arched.
circle circle Circle.
cunette cunette Cunette.
other other Other.
rectangle rectangle Rectangle.
square square Square.
trapezoid trapezoid Trapezoid.
oval oval Oval.
ovoid ovoid

F_1.7.16 Values of code list PoleFoundationTypeValue

Parent
Value Name Definition Description
value
Pole foundation set extra deep in the
extraDeepInEarth extra Deep In Earth
Earth.
Pole foundation set normally in the
normallyInEarth normally In Earth
Earth.
normalWithConcret normal With Pole foundation set normally, with
eBackfill Concrete Backfill concrete backfill.
onConcreteFoundat on Concrete Pole foundation set on concrete
ion Foundation foundation.
other other Other.

F_1.7.17 Values of code list PoleMaterialTypeValue

Parent
Value Name Definition Description
value
aluminiuim aluminiuim Aluminium.
composite composite Composite.
concrete concrete Concrete.
fiberglass fiberglass Fiberglass.
other other Other material.
steel steel Steel.
wood wood Wood.

F_1.7.18 Values of code list PoleTypeValue

Parent
Value Name Definition Description
value
hFrame h Frame H-frame pole.
other other Other.
standard standard Standard pole.
streetLight street Light Street light pole.
tower tower Tower (not a pole).
veryHighVoltage very High Voltage

F_1.7.19 Values of code list SewerAppurtenanceTypeExtendedValue

Parent
Value Name Definition Description
value
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 187

Parent
Value Name Definition Description
value
An anode is a feature (specifically, an electrical
mechanism) that&rsquo;s applied to system components
for the prevention of rust, pitting, and the corrosion of
metal surfaces that are in contact with water or soil. A
low-voltage current is applied to the water or soil in
contact with the metal, such that the
anode anode Anode.
electromotive force renders the metal component
cathodic. Corrosion is concentrated on the anodes
instead of on the associated (and protected) water
system components. This type of corrosion may occur in
copper, steel, stainless steel, cast iron, and ductile iron
pipes.
A barrel is the cylindrical part of a manhole between the
barrel barrel Barrel. cone and the shelf. Barrels are only found in wastewater
and stormwater systems.
A bar screen is a set of parallel bars, either vertical
or inclined, that is placed in a sewer or other waterway to
barScreen bar Screen Bar screen.
catch debris. Bar screens are only found in wastewater
and stormwater systems.
A catch basin is a chamber or well used with storm or
combined sewers to receive runoff into the collection
system. Catch basins are used as a means of removing
catchBasin catch Basin Catch basin.
debris and solids that could enter thecollection system.
Catch basins may also be modeled as curb inlets or
stormwater inlets.
A cleanout is a sewer and stormwater-specific facility that
is used as an opening in a collection system for inserting
tools, rods, or snakes while cleaning a pipeline or
clearing a stoppage. Cleanout types include two-way
cleanOut clean Out Clean out.
cleanouts, which are designed for working a snake into
the pipe in either
direction. Two-way cleanouts are commonly found in
laterals or near a property line.
A discharge structure is a sewer and stormwater-specific
dischargeStr discharge Discharge facility where wastewater drainage is discharged from
ucture Structure structure. the system. A discharge point may be located at the
terminus of an outfall.
A meter is a facility that is used to measure wastewater
meter meter Meter. volume. Being a facility, a meter plays the role of a
junction on the active network.
A pump is a piece of equipment that moves,
compresses, or alters the pressure of a fluid, such as
water or air, being conveyed through a natural or artificial
pump pump Pump.
channel. Pump types include AxialFlow, Centrifugal, Jet,
Reciprocating, Rotary,
Screw, and Turbine.
A regulator is a device that is used in combined sewer
regulator regulator Regulator.
systems to control or regulate the diversion flow.
The SCADA sensor is a feature that&rsquo;s used to
remotely measure the status of network components as
part of a supervisory control and data acquisition
scada SCADA
scadaSensor (SCADA) system. SCADA systems provide alarms,
Sensor sensor.
responses, data acquisition, and control for collection
and distribution systems. Operators use the SCADA
system to monitor and adjust processes and facilities.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 188

Parent
Value Name Definition Description
value
The thrust protection represents a type of line protector
that&rsquo;s used to prevent pipe movement. Thrust
protection is commonly implemented as thrust blocks
thrustProtecti thrust Thrust
(masses of concrete material) that are placed at bends
on Protection protection.
and around valve structures. The types of thrust
protection include Anchor,
Blocking, Deadman, and Kicker.
A tide gate is a device used in sewer and stormwater
systems that is suspended from a free-swinging
horizontal hinge and is usually placed at the end of a
tideGate tide Gate Tide gate.
conduit, discharging into a body of water with a
fluctuating surface elevation. This piece of equipment is
also termed a backwater gate, flap gate, or check gate.
Other other
Node node
connection connection
specificStruct specific
ure Structure
mechanic
mechanicAnd
And
Electromech
Electromech
anicEquipme
anic
nt
Equipment
rainwaterColl rainwater
ector Collector
watertankOr watertank Or
Chamber Chamber

F_1.7.20 Values of code list SewerPipeTypeValue

Parent
Value Name Definition Description
value
A lateral line is a small-diameter pipe that runs
LL LL Lateral line.
from the main line to the customer premises.
Lateral line that
transports a
LL_Combinati LL_ Lateral line that transports a combination of
combination of
on Combination sanitary and storm water.
sanitary and storm
water.
Lateral line that
LL_Commerci LL_ transport Lateral line that transport wastewater from
al Commercial commercial-origin commercial facilities.
wastewater.
Lateral line that
Lateral line that transports domestic
LL_Domestic LL_ Domestic transports domestic
wastewater.
sanitary water.
Lateral line that transports irrigation
LL_Irrigation LL_ Irrigation Irrigation lateral line.
wastewater.
Lateral line that
LL_Storm LL_ Storm transports storm Lateral line that transports storm water.
water.
A main line is a large-diameter pipe that carries
ML ML Main line.
sewer from the source through the network.
A gravity main is a type of main line that is
Main line's gravity
ML_GM ML_GM unpressurized and relies on gravity to move the
main.
water through the main.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 189

Parent
Value Name Definition Description
value
A collector is a pipe that collects and transports
ML_GM_Colle ML_GM_ Main line's gravity
wastewater to a treatment plant or disposal
ctor Collector main's collector.
system. Service laterals connect to collectors.
ML_GM_Culve ML_GM_ Main line's gravity A culvert is a pipe used to channel water e.g.
rt Culvert main's culvert. underneath a road, railway or embankment.
Main line's gravity
ML_GM_InLin ML_GM_ In In-line storage involves retaining wet-weather
main's in-line
eStorage Line Storage flow in the pipe for small rainstorms.
storage.
Large sewer line that controls the flow of
sewage to the treatment plant. In a storm it
ML_GM_Interc ML_GM_ Main line's gravity
allows some of the sewage to flow directly into
eptor Interceptor main's interceptor.
a receiving stream, thus keeping it from
overflowing onto the streets.
An inverted siphon is a pipe that must dip
ML_GM_ Main line's gravity below an obstruction to form a „U&ldquo;
ML_GM_Invert
Inverted main's inverted shaped flow path. Inverted siphons are
edSiphon
Siphon siphon. commonly used for preventing smelly sewer
gases from coming back out of drains.
Main line's gravity An open channel is a channel open to the
ML_GM_Open ML_GM_
main's open environment that transmits raw water and
Channel Open Channel
channel. drainage.
Outfalls are the conduit leading to the final
disposal point or area for wastewater and
ML_GM_Outfa ML_GM_ Main line's gravity
drainage. Outfalls discharge into a receiving
ll Outfall main's outfall.
water body, such as a stream, river, lake,
ocean, or other surface, or groundwater.
An overflow connects a chamber or pipe to
ML_GM_Overf ML_GM_ Main line's gravity
another part of the system or outfall during
low Overflow main's overflow.
overload conditions or peak flows.
Tunnels are used to transmit sewer through
mountains or deep below the ground. Tunnels
ML_GM_Tunn ML_GM_ Main line's gravity
are generally created in bedrock and may
el Tunnel main's tunnel.
contain features such as pipes and ducts
(conduits) within the tunnel.
A pressurized main is a type of main line that is
pressurized. Pressure sewers are particularly
adaptable for rural or
semi-rural communities where public contact
with
effluent from failing drain fields presents a
substantial
Main line's
ML_PM ML_PM health concern.
pressurized main.
NOTE There are numerous types of
PressurizedMains in the sewer distribution
model; they include AirRelease, BlowOff,
Bypass, ChemicalInjection, DistributionMain,
Interconnect, PipeBridge, SamplingStation, and
TransmissionMain.
Main line's
ML_PM_Force ML_PM_
pressurized main's
Main Force Main
force main.
Main line's
ML_PM_PipeB ML_PM_ Pipe
pressurized main's
ridge Bridge
pipe bridge.
Main line's
ML_PM_Press ML_PM_
pressurized main's
ure Pressure
pressure.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 190

Parent
Value Name Definition Description
value
Main line's
ML_PM_Vacu ML_PM_
pressurized main's
um Vacuum
vacuum.

F_1.7.21 Values of code list SewerWaterTypeExtendedValue

Parent
Value Name Definition Description
value
A combined wastewater sewer is a type of sewer system
Combined
combined combined that collects sanitary sewage and stormwater runoff in a
wastewater.
single pipe system.
Reclaimed water, sometimes called recycled water, is
former wastewater (sewage) that has been treated to
Reclaimed
reclaimed reclaimed remove solids and certain impurities, and then used in
water.
sustainable landscaping irrigation or to recharge
groundwater aquifers.
Sanitary Sanitary sewers remove waste products from peoples'
sanitary sanitary
wastewater. home and send them underground to a treatment plant.
Storm wastewater drains gather rain and storm runoff
Storm runoff
storm storm and direct them to wetlands and lakes. Ditches and curb
wastewater.
line grates are storm drains.

F_1.7.22 Values of code list TelecommunicationsAppurtenanceTypeExtendedValue

Parent
Value Name Definition Description
value
An antenna (or aerial) is a transducer that transmits or
receives electromagnetic waves. In other words,
antenna antenna Antenna.
antennas convert electromagnetic radiation into electric
current, or vice versa.
Copper
copper A maintenance loop is a coil of slack copper cable that is
copperMainte (twisted-pair)
Maintenance used to support future joining or other maintenance
nanceLoop maintenance
Loop activities.
loop.
copperRepea copper Copper A copper repeater is copper line conditioning equipment
ter Repeater repeater. that amplifies the analog or digital input signal.
Digital cross A digital cross connect is a patch panel for copper cables
digitalCrossC digital Cross
connect that are used to provide digital service. Fibers in cables
onnect Connect
(DXC). are connected to signal ports in this equipment.
A digital loop carrier is a device that multiplexes an
digitalLoopC digital Loop Digital loop optical signal in to multiple lower level digital signals.
arrier Carrier carrier (DLC). Fibers in cables are connected to signal ports in this
equipment.
The exchange (central office) is the physical building
Exchange
exchange exchange used to house the inside plant equipment (distribution
(switch).
frames, lasers, switches etc).
A fiber interconnect terminates individual fibers or
Fiber
fiberIntercon fiber establishes a connection between two or more fiber
interconnect
nect Interconnect cables. Fibers in cables are connected to signal ports in
(FIC).
the equipment.
Joint closure A protective joint closure for either copper or fiber-optic
jointClosure joint Closure (copper of cable joints. A cable joint consists of spliced conductors
fiber). and a closure.
A load coil is a copper line conditioning equipment.
Standard voice phone calls degrade noticeably when the
loadCoil load Coil Load coil. copper portion of a phone line is greater than 18 kilofeet
long. In order to restore call quality, load coils are
inserted at specific intervals along the loop.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 191

Parent
Value Name Definition Description
value
A main distribution frame is often found at the local
exchange (Central Office) and is used to terminate the
main Main
mainDistributi copper cables running from the customer's site. The
Distribution distribution
onFrame frame allows these cables to be cross connected using
Frame frame (MDF).
patch cords to other equipment such as a concentrator or
switch.
A multiplexer is a device that combines multiple inputs
Multiplexer into an aggregate signal to be transported via a single
multiplexer multiplexer
(MUX). transmission channel. Fibers in cables are connected to
signal ports in this equipment.
optical Optical An optical maintenance loop is a coil of slack fiber cable
opticalMainte
Maintenance maintenance that is used to support future splicing or other
nanceLoop
Loop loop. maintenance activities.
An optical repeater is a device that receives an optical
signal, amplifies it (or, in the case of a digital signal,
opticalRepea optical Optical
reshapes, retimes, or otherwise reconstructs it), and
ter Repeater repeater.
retransmits it as an optical signal. Fibers in cables are
connected to signal ports in this equipment.
A patch panel is device where connections are made
patchPanel patch Panel Patch panel. between incoming and outgoing fibers. Fibers in cables
are connected to signal ports in this equipment.
A splice closure is usually a weatherproof encasement,
commonly made of tough plastic, that envelops the
exposed area between spliced cables, i.e., where the
jackets have been removed to expose the individual
transmission media, optical or metallic, to be joined. The
closure usually contains some device or means to
maintain continuity of the tensile strength members of the
splice Splice cables involved, and also may maintain electrical
spliceClosure
Closure closure. continuity of metallic armor, and/or provide external
connectivity to such armor for electrical grounding. In the
case of fiber optic cables, it also contains a splice
organizer to facilitate the splicing process and protect the
exposed fibers from mechanical damage. In addition to
the seals at its seams and points of cable entry, the
splice closure may be filled with an encapsulate to further
retard the entry of water.
A splitter is a transmission coupling device for separately
sampling (through a known coupling loss) either the
splitter splitter Splitter. forward (incident) or the backward (reflected) wave in a
transmission line. Fibers in cables are connected to
signal ports in this equipment.
Terminals are in-loop plant hardware, specifically
designed to facilitate connection and removal of
distribution cable, drop or service wire to and from cable
terminal terminal Terminal. pairs at a particular location. Terminals are a class of
equipment that establishes the end point of a section of
the transmission network between the CO and the
customer.
Terminations are a generic feature class for the end
points of cables. These may be considered similar to
termination termination Termination. service drops to buildings. They represent a point at
which the telephone company network ends and
connects with the wiring at the customer premises.
noticeBoard notice Board

F_1.7.23 Values of code list TelecommunicationsCableMaterialTypeExtendedValue

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 192

Parent
Value Name Definition Description
value
A coaxial cable, or coax, is an electrical cable with an
Coaxial inner conductor surrounded by a flexible, tubular
coaxial coaxial
cable. insulating layer, surrounded by a tubular conducting
shield.
A fiber optic cable is composed of thin filaments of glass
through which light beams are transmitted to carry large
amounts of data. The optical fibers are surrounded by
Fibre-optic
opticalFiber optical Fiber buffers, strength members, and jackets for protection,
cable.
stiffness, and strength. A fiber-optic cable may be an all-
fiber cable, or contain both optical fibers and metallic
conductors.
A copper cable is a group of metallic conductors (copper
wires) bundled together that are capable of carrying
Twisted pair
voice and data transmissions. The copper wires are
twistedPair twisted Pair (copper)
bound together, usually with a protective sheath, a
cable.
strength member, and insulation between individual
conductors and the entire group.
other other Other.

F_1.7.24 Values of code list ThermalAppurtenanceTypeExtendedValue

This codelist is empty

F_1.7.25 Values of code list ThermalPipeTypeValue

This codelist is empty

F_1.7.26 Values of code list ThermalProductTypeExtendedValue

Parent
Value Name Definition Description
value
heatingSteam heating Steam
heatingWater heating Water
coolingWater cooling Water

F_1.7.27 Values of code list UtilityDeliveryTypeExtendedValue

Parent
Value Name Definition Description
value
collection collection
distribution distribution
private private
transport transport

F_1.7.28 Values of code list WarningTypeExtendedValue

Parent
Value Name Definition Description
value
net net
tape tape
concretePaving concrete Paving

F_1.7.29 Values of code list WaterAppurtenanceTypeExtendedValue

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 193

Parent
Value Name Definition Description
value
An anode is a feature (specifically, an electrical
mechanism) that&rsquo;s applied to system components
for the prevention of rust, pitting, and the corrosion of
metal surfaces that are in contact with water or soil. A
low-voltage current is applied to the water or soil in
contact with the metal, such that the
anode anode Anode.
electromotive force renders the metal component
cathodic. Corrosion is concentrated on the anodes
instead of on the associated (and protected) water
system components. This type of corrosion may occur in
copper, steel, stainless steel, cast iron, and ductile iron
pipes.
A clear well is an enclosed tank that is associated with a
treatment plant. Clear wells are used to store filtered
water of sufficient capacity to prevent the need to vary
the filtration rate with variations in demand. Clear wells
clearWell clear Well Clear well.
are also used to provide chlorine contact time for
disinfection. Pumps are
used to move the water from the clear well to the
treatment plant or to a distribution system.
Control valves represent set of valves that operate in
controlValve control Valve Control valve. special ways. There are three fundamental types of
control valves: backflow control, air control, and altitude.
The fitting represents the facility found at the joint
between two lines where a transition of some sort must
fitting fitting Fitting. occur. The basic connecting devices between pipes;
fittings are rarely used to control the flow of water
through the network.
A hydrant enables fire fighters to attach fire hoses to the
distribution network. Hydrants also have secondary uses
hydrant hydrant Hydrant. that include flushing main lines and laterals, filling tank
trucks, and providing a temporary water source for
construction jobs.
The junction is a water network node where two or more
junction junction Junction. pipes combine, or a point where water consumption is
allocated and defined as demand.
A lateral point represents the location of the connection
lateralPoint lateral Point Lateral point.
between the customer and the distribution system.
A meter is a facility that is used to measure water
consumption (volume). Being a facility, a meter plays the
role of a junction on the active network.
meter meter Meter.
NOTE Meters are also much like hydrants as they also
have an associated warehouse object, namely, a
WarehouseMeter.
A pump is a piece of equipment that moves,
compresses, or alters the pressure of a fluid, such as
water or air, being conveyed through a natural or artificial
channel.
pump pump Pump.
NOTE Pump types include AxialFlow, Centrifugal, Jet,
Reciprocating, Rotary,
Screw, and Turbine.
A pump station is a facility for pumping water on the
pumpStation pump Station Pump station. network to transport to another part of the network (lift
pump).
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 194

Parent
Value Name Definition Description
value
A sampling station is a facility that is used for collecting
samplingStati sampling Sampling water samples. Sampling stations may be dedicated
on Station station. sampling devices, or they may be other devices of the
system where a sample may be obtained.
The SCADA sensor is a feature that&rsquo;s used to
remotely measure the status of network components as
part of a supervisory control and data acquisition
scada SCADA
scadaSensor (SCADA) system. SCADA systems provide alarms,
Sensor sensor.
responses, data acquisition, and control for collection
and distribution systems. Operators use the SCADA
system to monitor and adjust processes and facilities.
A storage basin represents artificially enclosed area of a
storage Storage
storageBasin river or harbor designed so that the water level remains
Basin basin.
unaffected by tidal changes.
Enclosed
storageFacilit storage
storage
y Facility
facility.
A surge relief tank is a piece of equipment used to
absorb pressure increases in the water system. Surge
surgeReliefT surge Relief Surge relief
relief tanks provide a buffer against throttling within the
ank Tank tank.
system by accepting water into a tank through a pressure
valve.
A system valve is a facility that is fitted to a pipeline or
orifice in which the closure member is either rotated or
moved transversely or longitudinally in the waterway so
as to control or stop the flow. System valves are used to
regulate pressure, isolate, throttle flow, prevent backflow,
System
systemValve system Valve and relieve
valve.
pressure.

NOTE System valve types include Gate, Plug, Ball,

Cone, and Butterfly. These specific types may be
classified as isolation valves.
The thrust protection represents a type of line protector
that&rsquo;s used to prevent pipe movement. Thrust
protection is commonly implemented as thrust blocks
thrustProtecti thrust Thrust (masses of concrete material) that are placed at bends
on Protection protection. and around valve structures.

NOTE The types of thrust protection include Anchor,

Blocking, Deadman, and Kicker.
treatmentPla treatment Treatment
nt Plant plant.
Production
well well
well.
pressure
pressureReli
Relieve
eveValve
Valve
airRelieveVal air Relieve
ve Valve
checkValve check Valve
water
waterExhaust
Exhaust
Point
Point
waterService water Service
Point Point
fountain fountain
fireHydrant fire Hydrant
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 195

Parent
Value Name Definition Description
value
pressureCont pressure
roller Controller
vent vent
recoilCheckV recoil Check
alve Valve
water
waterDischar
Discharge
gePoint
Point

F_1.7.30 Values of code list WaterPipeTypeValue

Parent
Value Name Definition Description
value
A lateral line is a small-diameter pipe that runs
from the main line to the customer premises.
LateralLine is a concrete class. The types of
LL LL Lateral line.
lateral lines are Combination, Commercial,
Domestic, Fire, HydrantLateral, Industrial, and
Irrigation.
LL_Commerci LL_ Commercial lateral Lateral line that transport water to commercial
al Commercial line. facilities.
Lateral line that transports water to domestic
LL_Domestic LL_ Domestic Domestic lateral line.
users.
Lateral line that transports water for the
LL_Fire LL_ Fire Fire lateral line.
purposes of distinguishing fire.
LL_HydrantLat LL_ Hydrant Lateral line that transports water to the
Hydrant laterals.
erals Laterals hydrants.
Lateral line that transports water to the
LL_Industrial LL_ Industrial Industrial lateral line.
industrial facilities.
Lateral line that transports water for the
LL_Irrigation LL_ Irrigation Irrigation lateral line.
irrigation purposes.
A main line is a large-diameter pipe that carries
ML ML Main line.
water from the source through the network.
A gravity main is a type of main line that is
unpressurized and relies on gravity to move the
water through the main.
Main line's gravity
ML_GM ML_GM
main.
NOTE For the water distribution model, the
types of gravity mains are Carrier,
InlineStorage, and TransportPipe.
A carrier pipe is an inner pipe, or a hollow
cylindrical tube contained inside an outer
ML_GM_Carri ML_GM_ Main line's gravity sheath. Responsible for carrying fluids, the
er Carrier main's carrier. carrier pipe runs through an outer, insulated
casing that acts as a containment system that
protects against spills.
Main line's gravity
ML_GM_InLin ML_GM_ In
main's in-line
eStorage Line Storage
storage.
Main line's gravity
ML_GM_Trans ML_GM_
main's transport
portPipe Transport Pipe
pipe.
 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 196

Parent
Value Name Definition Description
value
A pressurized main is a type of main line that is
pressurized.
There are numerous types of
Main line's PressurizedMains in the water distribution
ML_PM ML_PM
pressurized main. model; they include AirRelease, BlowOff,
Bypass, ChemicalInjection, DistributionMain,
Interconnect, PipeBridge, SamplingStation, and
TransmissionMain.
Main line's
ML_PM_AirRe ML_PM_ Air
pressurized main's
lease Release
air release.
Main line's
ML_PM_Blow ML_PM_ Blow
pressurized main's
Off Off
blow off.
Main line's
ML_PM_Bypa ML_PM_
pressurized main's
ss Bypass
bypass.
ML_PM_ Main line's
ML_PM_Chem
Chemical pressurized main's
icalInjection
Injection chemical injection.
ML_PM_ Main line's
ML_PM_Distri
Distribution pressurized main's
butionMain
Main distribution main.
Main line's
ML_PM_Interc ML_PM_
pressurized main's
onnect Interconnect
interconnect.
Main line's
ML_PM_PipeB ML_PM_ Pipe
pressurized main's
ridge Bridge
pipe bridge.
ML_PM_ Main line's
ML_PM_Samp
Sampling pressurized main's
lingStation
Station sampling station.
ML_PM_ Main line's
ML_PM_Trans
Transmission pressurized main's
missionMain
Main transmission main.
ML_PM_Raw ML_PM_ Raw
WaterTranspor Water
t Transport

F_1.7.31 Values of code list WaterTypeExtendedValue

Parent
Value Name Definition Description
value
Potable water or drinking water is water of sufficiently
Potable
potable potable high quality that can be consumed or used without risk of
water.
immediate or long term harm.
Raw water is water taken from the environment, and is
subsequently treated or purified to produce potable water
raw raw Raw water. in a water purification works. Raw water should not be
considered safe for drinking or washing without further
treatment.
Salt water or saline water is a general term for water that
salt salt Salt water. contains a significant concentration of dissolved salts
(NaCl).
Treated water is the water that went throgh treatment
Treated
treated treated [Link] processes are the ones commonly
water.
used in water purification plants.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 197

F_1.8 Externally governed code lists for the “Extended Utility

Networks” subdomain’s application schemas
No externally governed code lists is included in the ―Extended Utility Networks‖ subdomain‘s application
schemas.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 198

Annex G
(informative)
External new types

New types have been created since version 2.0, that are submitted to the Generic Conceptual Model
(GCM), since they are dedicated to a broader user than Utility and governmental services.

Here are presented these types, in order to permit an autonomous reading:

 RelatedParty
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 199

G_1 Application schema “RelatedParty”

G_1.1 UML Overview

Figure 7 – UML class diagram: Overview of the “RelatedParty” application schema

 INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 200

G_1.2 INSPIRE-governed code lists for the “RelatedParty” application

schema

The INSPIRE-defined code lists included in this application schema include the values specified in the
tables in this section.

G_1.2.1 Values of code list PartyRoleValue

Parent
Value Name Definition Description
value
authority authority A party legally mandated to supervise a resource and/or
parties related to a resource.
operator operator A party that runs a resource.
owner owner A party that owns a resource, i.e., to which a resource
belongs in a legal sense.

G_1.3 Externally governed code lists for the “RelatedParty”

application schema
No externally governed code lists is included in the ―Related Party‖ application schema.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 201

Annex H
(informative)
Telecommunication Networks

H_1 “Core Telecommunications Network” application schema

H_1.1 UML Overview

Figure 8 – UML class diagram: Overview of the “Core Telecommunications Network”

INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 202

H_1.2 Feature Catalogue

[Link]. Feature catalogue

Feature catalogue metadata

Feature catalogue name INSPIRE feature catalogue Core Telecommunications Network

Scope Core Telecommunications Network
Version number 3.0rc2
Version date 2012-07-09
Definition source INSPIRE data specification Core Telecommunications Network
Types defined in the feature catalogue

Type Package Stereotypes Section

TelecommunicationsAppurtenanceTypeBaseValue Core «codeList» [Link].1
Telecommunications
Network
TelecommunicationsAppurtenanceTypeValue Core «codeList» [Link].2
Telecommunications
Network
TelecommunicationsCable Core «featureType» [Link].1
Telecommunications
Network
TelecommunicationsCableMaterialTypeBaseValue Core «codeList» [Link].3
Telecommunications
Network
TelecommunicationsCableMaterialTypeValue Core «codeList» [Link].4
Telecommunications
Network
[Link].1. Spatial object types
TelecommunicationsCable
TelecommunicationsCable
Name: telecommunications cable
Subtype of: Cable
Definition: A utility link or link sequence used to convey data signals (PSTN, radio or computer)
from one location to another.
Status: Proposed
Stereotypes: «featureType»
Identifier: null
Attribute: telecommunicationsCableMaterialType

Name telecommunications cable material type

Value type: TelecommunicationsCableMaterialTypeValue
Definition: Type of cable material.
Multiplicity: 1
Stereotypes: «voidable»
Obligation: Technical Guidance (recommendation)
Constraint: "TelecommunicationsCable" is not in IR

Natural
language:

[Link].2. Code lists

TelecommunicationsAppurtenanceTypeBaseValue
TelecommunicationsAppurtenanceTypeBaseValue
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 203

TelecommunicationsAppurtenanceTypeBaseValue
Name: telecommunications appurtenance type base value
Subtype of: TelecommunicationsAppurtenanceTypeValue
Definition: Codelist containing a base classification of telecommunication appurtenance types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

TelecommunicationsAppurtenanceTypeValue
TelecommunicationsAppurtenanceTypeValue
Name: telecommunications appurtenance type value
Subtype of: AppurtenanceTypeValue
Definition: Codelist containing a classification of telecommunications appurtenances.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

TelecommunicationsCableMaterialTypeBaseValue
TelecommunicationsCableMaterialTypeBaseValue
Name: telecommunications cable material type base value
Subtype of: TelecommunicationsCableMaterialTypeValue
Definition: Codelist containing a base classification of telecommunications cable material types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

TelecommunicationsCableMaterialTypeValue
TelecommunicationsCableMaterialTypeValue
Name: telecommunications cable material type value
Definition: Codelist containing a classification of telecommunications cable material types.
Status: Proposed
Stereotypes: «codeList»
Extensibility: any
Identifier: [Link]

[Link].3. Imported types (informative)

This section lists definitions for feature types, data types and enumerations 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.

AppurtenanceTypeValue
AppurtenanceTypeValue
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Common Core Utility Network Elements [Include reference to the document
that includes the package, e.g. INSPIRE data specification, ISO standard or the
GCM]
Definition: Codelist containing a classification of appurtenances.

Cable
Cable (abstract)
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 204

Cable (abstract)
Package: INSPIRE Consolidated UML Model::Themes::Annex III::Utility and Governmental
Services::Utility and Governmental Services::Utility Networks::Core Utility Networks
Profile::Common Core Utility Network Elements [Include reference to the document
that includes the package, e.g. INSPIRE data specification, ISO standard or the
GCM]
Definition: A utility link or link sequence used to convey electricity or data from one location to
another.

H_1.3 INSPIRE-governed code lists

H_1.3.1 Values of code list TelecommunicationsAppurtenanceTypeBaseValue

Parent
Value Name Definition Description
value
An antenna (or aerial) is a transducer that
transmits or receives electromagnetic waves.
antenna antenna Antenna. In other words, antennas convert
electromagnetic radiation into electric current,
or vice versa.
Copper
copper A maintenance loop is a coil of slack copper
copperMainte (twisted-pair)
Maintenance cable that is used to support future joining or
nanceLoop maintenance
Loop other maintenance activities.
loop.
A copper repeater is copper line conditioning
copperRepeat copper Copper
equipment that amplifies the analog or digital
er Repeater repeater.
input signal.
A digital cross connect is a patch panel for
Digital cross
digitalCrossC digital Cross copper cables that are used to provide digital
connect
onnect Connect service. Fibers in cables are connected to
(DXC).
signal ports in this equipment.
A digital loop carrier is a device that
digitalLoopCa digital Loop Digital loop multiplexes an optical signal in to multiple
rrier Carrier carrier (DLC). lower level digital signals. Fibers in cables are
connected to signal ports in this equipment.
The exchange (central office) is the physical
Exchange building used to house the inside plant
exchange exchange
(switch). equipment (distribution frames, lasers,
switches etc).
A fiber interconnect terminates individual
Fiber
fiberInterconn fiber fibers or establishes a connection between
interconnect
ect Interconnect two or more fiber cables. Fibers in cables are
(FIC).
connected to signal ports in the equipment.
Joint closure A protective joint closure for either copper or
jointClosure joint Closure (copper of fiber-optic cable joints. A cable joint consists
fiber). of spliced conductors and a closure.
A load coil is a copper line conditioning
equipment. Standard voice phone calls
degrade noticeably when the copper portion
loadCoil load Coil Load coil. of a phone line is greater than 18 kilofeet
long. In order to restore call quality, load coils
are inserted at specific intervals along the
loop.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 205

Parent
Value Name Definition Description
value
A main distribution frame is often found at the
local exchange (Central Office) and is used to
main Main terminate the copper cables running from the
mainDistributi
Distribution distribution customer's site. The frame allows these
onFrame
Frame frame (MDF). cables to be cross connected using patch
cords to other equipment such as a
concentrator or switch.
A multiplexer is a device that combines
multiple inputs into an aggregate signal to be
Multiplexer
multiplexer multiplexer transported via a single transmission channel.
(MUX).
Fibers in cables are connected to signal ports
in this equipment.
optical Optical An optical maintenance loop is a coil of slack
opticalMainte
Maintenance maintenance fiber cable that is used to support future
nanceLoop
Loop loop. splicing or other maintenance activities.
An optical repeater is a device that receives
an optical signal, amplifies it (or, in the case
opticalRepeat optical Optical of a digital signal, reshapes, retimes, or
er Repeater repeater. otherwise reconstructs it), and retransmits it
as an optical signal. Fibers in cables are
connected to signal ports in this equipment.
A patch panel is device where connections
are made between incoming and outgoing
patchPanel patch Panel Patch panel.
fibers. Fibers in cables are connected to
signal ports in this equipment.
A splice closure is usually a weatherproof
encasement, commonly made of tough
plastic, that envelops the exposed area
between spliced cables, i.e., where the
jackets have been removed to expose the
individual transmission media, optical or
metallic, to be joined. The closure usually
contains some device or means to maintain
continuity of the tensile strength members of
Splice the cables involved, and also may maintain
spliceClosure splice Closure
closure. electrical continuity of metallic armor, and/or
provide external connectivity to such armor
for electrical grounding. In the case of fiber
optic cables, it also contains a splice
organizer to facilitate the splicing process and
protect the exposed fibers from mechanical
damage. In addition to the seals at its seams
and points of cable entry, the splice closure
may be filled with an encapsulate to further
retard the entry of water.
A splitter is a transmission coupling device for
separately sampling (through a known
coupling loss) either the forward (incident) or
splitter splitter Splitter.
the backward (reflected) wave in a
transmission line. Fibers in cables are
connected to signal ports in this equipment.
Terminals are in-loop plant hardware,
specifically designed to facilitate connection
and removal of distribution cable, drop or
service wire to and from cable pairs at a
terminal terminal Terminal.
particular location. Terminals are a class of
equipment that establishes the end point of a
section of the transmission network between
the CO and the customer.
INSPIRE Reference: [Link].6_v3.0rc2
TWG-US Data Specification on "Utility and governmental services" 2012-07-09 Page 206

Parent
Value Name Definition Description
value
Terminations are a generic feature class for
the end points of cables. These may be
considered similar to service drops to
termination termination Termination. buildings. They represent a point at which the
telephone company network ends and
connects with the wiring at the customer
premises.
noticeBoard notice Board

H_1.3.2 Values of code list TelecommunicationsCableMaterialTypeBaseValue

Parent
Value Name Definition Description
value
A coaxial cable, or coax, is an electrical cable
Coaxial with an inner conductor surrounded by a flexible,
coaxial coaxial
cable. tubular insulating layer, surrounded by a tubular
conducting shield.
A fiber optic cable is composed of thin filaments
of glass through which light beams are
transmitted to carry large amounts of data. The
optical optical Fibre-optic optical fibers are surrounded by buffers, strength
Fiber Fiber cable. members, and jackets for protection, stiffness,
and strength. A fiber-optic cable may be an all-
fiber cable, or contain both optical fibers and
metallic conductors.
A copper cable is a group of metallic conductors
(copper wires) bundled together that are capable
Twisted pair of carrying voice and data transmissions. The
twisted
twisted Pair (copper) copper wires are bound together, usually with a
Pair
cable. protective sheath, a strength member, and
insulation between individual conductors and the
entire group.
other other Other.