image

image INSPIRE Infrastructure for Spatial Information in Europe

D2.8.III.4 Data Specification on Land Use – Technical Guidelines

Title

D2.8.III.4 Data Specification on Land Use – Technical Guidelines

Creator

Temporary MIWP 2021-2024 sub-group 2.3.1

Date of publication

2024-07-31

Subject

INSPIRE Data Specification for the spatial data theme Land Us

Publisher

INSPIRE Maintenance and Implementation Group (MIG)

Type

Text

Description

This document describes the INSPIRE Data Specification for the spatial data theme Land Us

Format

AsciiDoc

Licence

Creative Commons Attribution (cc-by) 4.0

Rights

Public

Identifier

D2.8.III.4_v3.1.1

Changelog

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

Language

en

Relation

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

Foreword

How to read the document?

This document describes the "INSPIRE data specification on Land Use – Technical Guidelines" version 3.0 as developed by the Thematic Working Group (TWG) LU using both natural and a conceptual schema language.

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

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

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

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

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

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

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

Legal Notice

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

Interoperability of Spatial Data Sets and Services – General Executive Summary

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

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

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

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

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

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

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

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

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

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

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

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

Land Use – Executive Summary

The cornerstone of the specification development was the fact that Land Use shapes our environment in positive and negative ways. Productive land is a critical resource for food and biomass production and land use strongly influences soil erosion and soil functions such as carbon storage. Land management largely determines the beauty of Europe’s landscapes. It is important therefore to monitor land cover and land-use change[13].

In the INSPIRE directive, Land Use is defined as Territory characterised according to its current and future planned functional dimension or socio-economic purpose (e.g. residential, industrial, commercial, agricultural, forestry, recreational). [Directive 2007/2/EC] It is the description of land in terms or its socio-economic and ecological purpose. The inland water bodies as well as coastal waters are considered within the connected piece of land and planning of the use of sea and the use of seabed has been taken into consideration.

Land Use is itself split up into two different types:

  1. The Existing Land Use (current land use in the above definition), which objectively depicts the use and functions of a territory as it has been and effectively still is in real life. Geographical data-sets that provide Land Use information, at the time of observation, are modeled according to three application schemas:

    1. organized as a partition (in the mathematical sense) of a given area. Each element of the partition is homogeneous regarding the functional use of land. (ExistingLandUse application schema),

    2. organized as a set of discrete observation points informing on the functional use at the exact location and/or at its surrounding at the time of observation, (SampledExistingLandUse application schema),

    3. organized as a set of pixels informing on the functional use (GriddedExistingLandUse application schema)

  1. The Planned Land Use or PLU (future planned land use in the above definition), which corresponds to spatial plans, defined by spatial planning authorities, depicting the possible utilization of the land in the future. Planned land use is regulated by spatial planning documents elaborated at various levels of administration. Land Use regulation over a geographical area is in general composed of an overall strategic orientation, a textual regulation and a cartographic representation. Spatial planning documents result from the spatial planning process, once adopted and therefore which third parties must conform with. The scope of the INSPIRE Land Use Data Specification is giving the exact spatial dimension of all the elements a spatial plan is composed of. Planned Land Use application schema is mainly based on ZoningElement that depicts the zoning defined by spatial planners and SupplementaryRegulation that enables to inform on regulations that superimpose on the zoning.

The Land Use data specification supports two systems of classification:

Land Use has connexion with several other INSPIRE themes but it has been preferred not to include relationships with these themes in the model assuming that geometric functions of user information systems will enable to compute the spatial relationships. For example the inclusion of a feature from another theme in a Land Use feature or the overlap between them can be recomputed with spatial analysis tools.

In the Land Use data specification the description of the use of land will not provide the description of the geographical objects as done in the other theme. For example, an area in which energy is produced will be seen as a unique object in a Land Use datasets where in the Energy resource theme more detailed description of the plant may be provided including differentiation of its parts.

As stated by the INSPIRE directive, Land Use is different from Land Cover (LC, Annex II, theme number 2). The choice has been made to consider those two themes with different geometries.

Planned Land Use information is often overlaid on cadastral maps or other background mapping such as orthoimagery. The choice has been made to allow the data provider to inform on the version of the background map which the spatial plan has been drawn over without implementing direct relationships with the corresponding theme as described in the INSPIRE Data Specification .

Planned land use incorporate elements that in the real world can be related to other INSPIRE spatial data themes (see Figure 1) such as Area management/restriction/regulation zones and reporting units (AM, Annex III theme 11) or Natural Risk Zones (NZ, annex III theme 12). These will be seen as supplementary regulation in the Land Use data model (planned land Use) as soon as this information is incorporated in the legal spatial plan, i.e. only information that is geographical and legally binding in the spatial plan will be considered as a supplementary regulation although it may belong to another theme.

image

Figure 1: Relation of the land use theme with the area management and natural risk zone theme.

Comparable data on top of harmonised specification elements create additional value for achieving interoperability in INSPIRE. For this finality the data specification on Land Use includes recommendations on reporting data quality parameters.

Regardless whether these recommendations on data quality are met, the actual values of data quality elements should be published as metadata. These elements usually have to be published at the dataset level.

For visualisation purposes, simple rules for default portrayal are given by specifying the colour attached to classes of the Hierarchical INSPIRE Land Use Classification System.

The main value of the INSPIRE Land Use model is its simplicity, a yet flexible structure that allows data providers to publish their existing data in the most convenient way. It is expected that the effective use of the model will help explaining how to implement this data specification including how to use it for structure plans and construction plans.

Acknowledgements

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

The Thematic Working Group Land Use (TWG-LU) included:

François Salgé (TWG Facilitator), Wilko Quak (TWG Editor), Aaro Mikkola, Anneloes van Noordt, Gerard Willem Hazeu, Isabel Goñi, Julián Delgado Hernández, Kai-Uwe Krause, Maria Andrzejewska, Marjo Kasanko, Walter Richter, Maria Vanda Nunes de Lima (European Commission contact point).

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

Contact information

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

Table of Contents

1. Scope

This document specifies a harmonised data specification for the spatial data theme Land Use 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 is published as implementation guidelines accompanying these Implementing Rules.

2. Overview

2.1. Name

INSPIRE data specification for the theme Land Use.

2.2. Informal description

Definition:

Territory characterised according to its current and future planned functional dimension or socio–economic purpose (e.g. residential, industrial, commercial, agricultural, forestry, recreational). [Directive 2007/2/EC]

Description:

The definition of the INSPIRE spatial data theme 'Land Use' stresses two important parts of this theme:

First of all Land Use is defined as the use and functions of a territory. It is the description of land in terms of its socio-economic and ecological purpose. Land Use is different from Land Cover (Annex III, theme number 3), dedicated to the description of the surface of the earth by its (bio-)physical characteristics. Land Cover and Land Use are, however, related and often combined in practical applications. Data sets combining Land Use and Land Cover often emphasize land use aspects in intensively used areas and land cover aspects in extensively used areas. An example of the difference in description of the same piece of land would be an agricultural area with grass. In Land Cover it would be described as a pasture (the cover of the land is grass), while in Land Use it would be classified as agriculture (its use would be for grazing cattle).

Secondly Land Use is itself split up into two different types (see Table 1):

  • The existing land use (current land use in the above definition), which objectively depicts the use and functions of a territory as it has been and effectively still is in real life. Existing land use will be modeled according to three application schemas:

    • The Existing Land Use or ELU composed of polygons,

    • The Sampled Land Use or SLU which corresponds to the use and functions as observed around a set of locations sampled over a given area,

    • The Gridded Land Use or GLU which correspond to a georeferenced gridded version of an existing land use dataset.

  • The Planned Land Use or PLU (future planned land use in the above definition), which is composed of spatial plans, defined by spatial planning authorities, depicting the possible utilization of the land in the future. The corresponding application schema contains either a vector data or a raster data.

Existing Land Use

Planned Land Use

Polygons or vector data

ELU

PLU

Set of locations

SLU

Raster data

GLU

PLU

Table 1– different types of land use datasets and the corresponding application schemas

To accommodate the wide variety of spatial information that is already available on Land Use, the application schemas described in chapter 5 are as open ended as possible. They are based on a common aspect which can be applied for ELU, SLU, GLU and PLU, and supports two different systems of classification. First of all there is the Hierarchical INSPIRE Land Use Classification System (HILUCS). This is a new, multi-level, classification system. It will be general enough for the member states to map their specific classification system to the appropriate level of HILUCS. This classification system will allow comparing the different data sets from different member states. It has been necessary to define HILUCS as no existing classification system was fulfilling the requirements for consistently describing existing and planned land use in Europe. The second possibility is to add the local classification system of the member state, or in the case of PLU, the authority issuing the plan. This local system should however be well documented, allowing users to use the data and compare it with datasets from other sources.

The scope of the theme Land Use does not only include the actual earth’s surface (the use at ground level), but can also indicate which uses are directly below or above ground level, restricted to their physical impact at ground level. A mine for instance can be completely below the surface but still be the land use. Another example is a high rise set of buildings which includes shops on the ground floor and residences on the other floors.

In most cases human activities occur on areas that include the "infrastructures" necessary for the activity to take place (e.g. an industrial area includes the car-parks necessary for the staff and clients, gardens necessary for the "well fare", warehouses for the stocks, front office – back office). The inland water bodies as well as coastal waters are considered within the connected piece of land as soon as they participate to the use or function of that connected piece of land, e.g. a harbour includes the water that is inside the harbour. More generally their use may be documented according to HILUCS.

Planning of the use of sea and the use of seabed has been taken into consideration. HILUCS is applicable although some further work is needed to construct the correspondence between HILUCS and the terminology used in this area of spatial planning.

2.2.1. Existing land use

Geographical data-sets that provide Land Use information, at the time of observation, are often organised as a partition (in the mathematical sense) of a given area (see Figure 2). They are called Existing Land Use (ELU). Each element of the partition (polygon) is homogeneous regarding the functional use of land. The fact that one land use is defined does not mean only one land use exists, the model will enable the possibility to also provide the other kinds of land use in the same area. The polygons do not overlap each other (i.e. "polygons" are mutually exclusive). The area covered by a Land Use data set may differ from the area managed by an authority. For example a local government may be responsible for the data set but the area covered by the data set may be smaller than the administrative boundaries of the local government or may have holes. That may be due to multiple reason including the data capture method (e.g. from imagery) or the legal context.

Geographical data-sets that provide Land Use information, at the time of observation, may also be organised as discrete set of points each of them being observed and associated with attributes describing the land use. It will be called Sampled Land Use (SLU) (see Figure 3)

Gridded Land Use (GLU) is a way of presenting existing land use in a raster form. (see Figure 4)

image

Figure 2 – example of existing land use datasets. Left: Urban Atlas over Bruxelles, Belgium. Right: Land Use over the city of Espoo, Finland

image

Figure 3 – example of sampled land use of LUCAS 2009 in Luxembourg

image

Figure 4 –examples of a gridded land use left from the area of Rouen (France) right from the Netherlands

A nomenclature provides the functional uses that are taken into consideration; many nomenclatures exist in the world today, from those applicable at continental level, to those defined locally. For the INSPIRE Land Use theme the new HILUCS classification system will be used (e.g. area used for primary production such as agriculture or forestry, for secondary production such as industrial areas, for transport networks, logistics or other basic infrastructure, for residential etc.).

Each separate dataset of Existing Land Use will be a snapshot of a certain moment in time, the added value of these separate datasets with different timestamps is the fact that Land Use changes over time can be monitored if they are put together.

Associated with the nomenclature, the minimum unit of interest (also called minimum mapping unit or observation unit) defines the level of detail within the dataset, i.e. the minimum size of the polygons or the minimum distance between observation points that are in the dataset. This information is provided within the metadata associated with the dataset.

2.2.2. Planned land use

In the context of INSPIRE, sharing land use information supports the requirements common in spatial planning. The spatial plans established at the various levels of administration need to be supported by other spatial plans made by public authorities at different levels or even with spatial plans across the border of a nation. Different zoning elements across borders can have a great influence on each other.

Planned land use is regulated by spatial planning documents elaborated at various levels of administration.

Land Use regulation over a geographical area (spatial planning documents resulting from the spatial planning process, once adopted and therefore which third parties must conform with) is often composed of three parts:

  • the overall strategic orientation that describes the development will of the competent administrative authority which is a textual document,

  • the textual regulation that affects each zone and orientates the planned land use. It is composed of articles and dictates what is possible and impossible with regard to the use of land,

  • the cartographic representation composed of elements that are binding (affecting the actual rights and constraints of cadastral parcels) or not binding (e.g. for illustration only).

Although the original planned Land Use documents are legally binding the derived INSPIRE dataset is not.

The scope of the INSPIRE Land Use Data Specification is giving the exact spatial dimension of all the elements a spatial plan is composed of. These elements can be based on other INSPIRE spatial data themes, like Cadastral Parcels, Area Management Zones or Natural Risk Zones. The main spatial objects of a spatial plan will be the zoning elements and the supplementary regulations that add regulations to the zoning elements. Additional information like the exact textual regulation will be linked to these objects.

Until now, there is no agreed nomenclature at the international level regarding planned land use. Like for the Existing Land Use the new HILUCS nomenclature will be mandatory to be used at the most appropriate level. But besides this mandatory classification system, any other system like the local system which is supposed to be well documented can also be added.

Spatial planning is performed at several governmental levels and the cartographic expression of the regulation differs in its graphical expression as well as the concepts that are represented. It is worth mentioning that due to the terms of the directive itself, the local governments being at the lower level of administration in any member state will have to make available their spatial plan only if a law imposes the responsibility on them to produce such spatial plans.

Below the illustrative description of structure plans – zoning plans – and constructions plans is an example reflecting the different levels of detail in which planned land use can be spatially represented. Other plan types may exist in the EU.

Plans on different administrative levels have different uses and therefore different values, but one is not better than the other. Structure plans give a different type of information as opposed to construction plans, more detail does not necessarily mean more value, especially when viewed on an European level. It is therefore important that plans on all levels can be exchanged using INSPIRE.

The area covered by a Planned Land Use data set may differ from the area managed by the local government responsible for. The area covered by the data set may be smaller than the administrative boundaries of the local government or may have holes. That may be due to multiple reason including the legal context.

Structure plans. At a level of a wide area (several thousands of km², i.e. a country, a state, or a region), spatial planning documents outline the spatial structures and development in pursuance of spatial planning goals (see Figure 5). All public bodies and planning authorities must ensure that planning and measures affecting spatial structures are strictly compliant with the spatial planning goals. In the INSPIRE context, they are seen as geographic information. The concepts cartographically represented include "areas loosing attractiveness", "areas that require controlled development", "economic area of metropolitan importance", "green heart", "green belt around cities", "peri-urban area with rural predominance", "ecological corridors", "liaison between ecological corridors" "limits and intensity of potential areas of urban expansion", "reinforcement project of public transportation networks". The cartographic expressions are not always binding when they are given for illustration only, although the textual parts are legally binding. In the INSPIRE context, these cartographic representation may be viewed as simple drawings, being either raster or vector. In case of legally binding georeferenced Structure Plans, it could be also implemented as any other spatial plan with its Zoning Elements, Supplementary Regulations and Official Documentation. Some suggestions on how structure plans can be modelled is given in Annex I of this document (based on testing reports).

image

Figure 5 – examples of cartographic representation of planned Land Use for a wide area. Top: Directive territoriale d’aménagement du départment du Rhône. Bottom: spatial structure plan of the federal state "Lower Saxony" and part of a regional plan in the federal state "Schleswig Holstein"

Zoning Plans. At a level of a municipality or group of municipalities (i.e. several hundred of km²), the concepts cartographically represented includes the zoning and supplementary regulations (such as easements) (see Figure 6). Zoning refers to a partition where the planned land use is depicted. To each polygon are attached articles of the regulation that explicit the rights and prohibitions regarding new constructions or modification to existing constructions. Supplementary regulations overlap the zoning where it exists and provide additional information and/or limitations to the development of the area. The supplementary regulations can be for spatial planning reasons, or due to the need to formalise external regulations. They affect the constructability of cadastral parcels and therefore have "well-defined" boundaries. In the INSPIRE context, they are seen as geographic information.

image

Figure 6 –examples of cartographic representation of zoning and supplementary regulations. Left: Green lines represent the zoning overlaid on cadastre. Right: Supplementary regulations overlaid on cadastre and zoning

Construction Plans. At a development area level (i.e. few km²) the concept cartographically represented are the actual geographical objects that will be created such as building, parking lots, gardens (see Figure 7). This detailed level is not really necessary to be exchanged on a European level, but may be exchanged between public authorities at a local level, perhaps even across borders of member states. In the INSPIRE context, they may be seen as geographic information or as simple drawings.

image

Figure 7 – examples of cartographic representation of planned development area

2.2.3. Interrelationships with INSPIRE spatial data themes

2.2.3.1. Similarities between Land Use and other INSPIRE Themes

There is a similarity between the scope of Land Use (LU) and the following themes:

  • Annex I: Protected Sites (PS) and Annex III: Area Management, Restriction and Regulation Zones (AM) and Natural Risk Zones (NZ)

  • Annex III: Land Cover (LC)

  • Annex III: Agricultural and Aquacultural Facilities (AF), Production and Industrial Facilities (PF) and Utility and Governmental Services(US)

  • Annex III: Building (BU)

Similarity between LU and PS, AM and NZ

The key difference between LU and the three themes is that PS, AM and NZ are established to manage, regulate and restrict any activities in a given area where LU (planned land use) only considers these area as supplementary regulations only if they are bundled into the spatial plan as a whole. Thus when a zone has been established to regulate planned land use and defined within a legally binding spatial plan it falls within the scope of the Land Use theme and as such be encoded as a SupplementaryRegulation.

Similarity between LU and LC

The key difference between LU and LC is that LC describes the surface of the earth by its (bio‑)physical characteristics where LU defines the use and functions of a territory in terms of its socio-economic and ecological purpose

Similarity between LU and AF, PF and US

The key difference between LU and the three themes is that AF, PF and US describe in details the objects relevant to their theme such as a farm, a plant of a governmental office, where LU defines the piece of land which use corresponds to a primary, secondary or tertiary economic sector as defined by the HILUCS code attach to the piece of land.

Similarity between LU and BU

The key difference between LU and BU is that BU does not take account of the surroundings of any building where LU incorporates inside a piece of land all the objects that contributes to the same socio-economic and ecological purpose.

2.2.3.2. Interrelationships between Land Use and other INSPIRE Themes

Because of the wide heterogeneity of activities covered by HILUCS, several interrelationships with other INSPIRE spatial data themes exist.

Associations or relationships between spatial objects

No associations have been defined between spatial object types of other themes to represent explicit relationships. It has been considered to expensive for producers to compute them and it has been preferred to let the users recompute them using the feature geometry.

Land Use shares the same geometry as another INSPIRE spatial object

Land Use features are often defined based on the extent of another related spatial object such as cadastral parcels (planned land use) or land cover polygons (existing land use). These shared geometry has not been considered in the data model. Regarding cadastral parcels, the share of geometry is not stable with time as a spatial plan often refers to a cadastral map as it existed when the plan was adopted.

Definition:

Territory characterised according to its current and future planned functional dimension or socio–economic purpose (e.g. residential, industrial, commercial, agricultural, forestry, recreational).

Description

Land Use theme is defined as the use and functions of a territory and it is description of land in terms of its socio-economic and ecological purpose. Land use theme is itself split in two different types:

  • The Existing Land Use which objectively depicts the use and functions of a territory as it has been and effectively still is in real life

  • The Planned Land Use which corresponds to spatial plans, defined by spatial planning authorities, depicting the possible utilization of the land in the future.

Two types of classification systems are supported by Land Use theme, the (obligatory) Hierarchical INSPIRE Land Use Classification System which is a multi-level, classification system that will apply to the existing and planned land use; the (optional) specific classification system in use in a member state.

Entry in the INSPIRE registry: http://inspire.ec.europa.eu/theme/lu/

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)

[Directive 2007/60/EC] Directive of the European Parliament and of the Council of 23 October 2007 on the assessment and management of flood risks

[ISO 19105] EN ISO 19105:2000, Geographic information — Conformance and testing

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

[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 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 19139] ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation

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

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

[Regulation 976/2009/EC] Commission Regulation (EC) No 976/2009 of 19 October 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards the Network Services

[Regulation 1089/2010/EC] Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services

2.4. Terms and definitions

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

Specifically, for the theme Land Use, the following terms are defined:

  1. Coverage

    Any data representation that assigns values (attributes) directly to a spatial position with regard to spatial, temporal or spatiotemporal aspects. In this data specification coverage is a continuous coverage which maps direct spatial positions to value records (i.e. raster data that has been georeferenced).

  1. Easements

    Rights to use someone else’s land for a public utility specified purpose.

  1. Existing Land Use

    An objective depiction of the use and functions of a territory as it has been and effectively still is in real life.

  1. Gridded Land Use

    An objective depiction as a regular orthorectified grid (image) of the use and functions of a territory as it has been and effectively still is in real life.

  1. Hierarchical INSPIRE Land Use Classification System (HILUCS)

    A multi-level classification system for Land Use whose use is mandatory at the most appropriate level.

  1. Minimum Unit of Interest

    The smallest size of the land use objects taken into consideration in the data set.

  1. Planned Land Use

    Spatial plans, defined by spatial planning authorities, depicting the possible utilization of the land in the future.

  1. Sampled Land Use

    An objective depiction of the use and functions of a territory [as it has been and effectively still is] in real life as observed in sampled location.

  1. Supplementary regulations

    Geographic features providing supplementary information and/or limitation of the use of land. The supplementary regulations can be for spatial planning reasons or due to the need to formalise external regulations.

  1. Zoning

    A partition where the planned land use is depicted, making explicit the rights and prohibitions regarding new constructions that apply within each partition element.

NOTE "Zoning is an important component of land-use planning. It commonly includes regulation of the kinds of activities which will be acceptable on particular lots (such as open spaces, residential, agricultural, commercial or industrial), the densities at which those activities can be performed, the amount of space structures may occupy, etc." : Spatial development glossary European Conference of Ministers responsible for Spatial/Regional Planning (CEMAT), http://www.coe.int/t/dg4/cultureheritage/heritage/cemat/VersionGlossaire/Bilingue-en-fr.pdf

2.5. Symbols and abbreviations

ATS

Abstract Test Suite

EC

European Commission

EEA

European Environment Agency

ELU

Existing Land Use

ETRS89

European Terrestrial Reference System 1989

ETRS89-LAEA

Lambert Azimuthal Equal Area

FAO

Food and Agriculture Organization

GLU

Gridded Land Use

GML

Geography Markup Language

HILUCS

Hierarchical INSPIRE Land Use Classification System

HSRCL

Hierarchical Supplementary Regulation Code List

ISDSS

interoperability of spatial data sets and services

ISIC

International Standard Classification of All Economic Activities

ISO

International Organization for Standardization

ITRS

International Terrestrial Reference System

LBCS

Land-Based Classification Standards

LGN

Landelijk Grondgebruiksbestand Nederland

LUCAS

Land Use / Cover Area Frame Survey

MCA

Mapa de Cultivos y Aprovechamientos

MUI

Minimum Unit of Interest

NACE

Nomenclature des Activités de la Communauté Européenne

PLU

Planned Land Use

SEEA

System of Environmental Economic Accounts

SIOSE

Sistema de información sobre Ocupación del Suelo de España

SLU

Sampled Land Use

TG

Technical Guidance

UML

Unified Modeling Language

XML

EXtensible Markup Language

2.6. XML Extensible Markup Language How the Technical Guidelines map to the Implementing Rules

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

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

image

Figure 8 - Relationship between INSPIRE Implementing Rules and Technical Guidelines

2.6.1. Requirements

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

📕

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

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

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

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

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

📒

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

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

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

2.6.2. Recommendations

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

📘

Recommendation X
Recommendations are shown using this style.

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

2.6.3. Conformance

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

3. Specification scopes

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

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

4. Identification information

These Technical Guidelines are identified by the following URI:

http://inspire.ec.europa.eu/tg/lu/3.0

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

5. Data content and structure

5.1. Application schemas – Overview

5.1.1. Application schemas included in the IRs

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

📕

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

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

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

The types to be used for the exchange and classification of spatial objects from data sets related to the spatial data theme Land Use are defined in the following application schemas (see following sections):

  • Land Use Nomenclature application schema

  • Existing Land Use application schema

  • Gridded Land Use application schema

  • Sampled Land Use application schema

  • Planned Land Use application schema

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

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

📒

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

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

📕

IR Requirement
Article 3
Common Types

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

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

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

5.2. Basic notions

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

5.2.1. Notation

5.2.1.1. Unified Modeling Language (UML)

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

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

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

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

📕

IR Requirement
Article 5
Types

(…​)

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

  2. Abstract types shall not be instantiated.

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

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

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

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

5.2.1.2. Stereotypes

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

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

Stereotype

Model element

Description

applicationSchema

Package

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

leaf

Package

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

featureType

Class

A spatial object type.

type

Class

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

dataType

Class

A structured data type without identity.

union

Class

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

codeList

Class

A code list.

import

Dependency

The model elements of the supplier package are imported.

voidable

Attribute, association role

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

lifeCycleInfo

Attribute, association role

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

version

Association role

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

5.2.2. Voidable characteristics

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

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

📘

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

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

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

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

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

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

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

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

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

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

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

5.2.3. Code lists

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

5.2.3.1. Code list types

The IRs distinguish the following types of code lists.

📕

IR Requirement
Article 6
Code Lists for Spatial Data Sets

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

📘

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

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

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

📕

IR Requirement
Article 6
Code Lists for Spatial Data Sets

(…​)

  1. Code lists may be hierarchical. Values of hierarchical code lists may have a more generic parent value. Where the valid values of a hierarchical code list are specified in a table in this Regulation, the parent values are listed in the last column.

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

5.2.3.2. Obligations on data providers
📕

IR Requirement
Article 6
Code Lists for Spatial Data Sets

(…​.)

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

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

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

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

5.2.3.3. Recommended code list values

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

📘

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

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

5.2.3.4. Governance

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

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

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

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

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

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

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

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

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

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

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

📘

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

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

5.2.3.5. Vocabulary

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

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

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

5.2.4. Identifier management

📕

IR Requirement
Article 9
Identifier Management

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

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

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

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

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

5.2.5. Geometry representation

📕

IR Requirement
Article 12
Other Requirements & Rules

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

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

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

5.2.6. Temporality representation

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

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

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

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

📕

IR Requirement
Article 10
Life-cycle of Spatial Objects

(…​)

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

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

📘

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

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

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

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

📕

IR Requirement
Article 12
Other Requirements & Rules

(…​)

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

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

5.2.7. Coverages

Coverage functions are used to describe characteristics of real-world phenomena that vary over space and/or time. Typical examples are temperature, elevation, precipitation, imagery. A coverage contains a set of such values, each associated with one of the elements in a spatial, temporal or spatio-temporal domain. Typical spatial domains are point sets (e.g. sensor locations), curve sets (e.g. isolines), grids (e.g. orthoimages, elevation models), etc.

In INSPIRE application schemas, coverage functions are defined as properties of spatial object types where the type of the property value is a realisation of one of the types specified in ISO 19123.

To improve alignment with coverage standards on the implementation level (e.g. ISO 19136 and the OGC Web Coverage Service) and to improve the cross-theme harmonisation on the use of coverages in INSPIRE, an application schema for coverage types is included in the Generic Conceptual Model in 9.9.4. This application schema contains the following coverage types:

  • RectifiedGridCoverage: coverage whose domain consists of a rectified grid – a grid for which there is an affine transformation between the grid coordinates and the coordinates of a coordinate reference system (see Figure 9, left).

  • ReferenceableGridCoverage: coverage whose domain consists of a referenceable grid – a grid associated with a transformation that can be used to convert grid coordinate values to values of coordinates referenced to a coordinate reference system (see Figure 9, right).

In addition, some themes make reference to the types TimeValuePair and Timeseries defined in Taylor, Peter (ed.), OGC® WaterML 2.0: Part 1 – Timeseries, v2.0.0, Open Geospatial Consortium, 2012. These provide a representation of the time instant/value pairs, i.e. time series (see Figure 10).

Where possible, only these coverage types (or a subtype thereof) are used in INSPIRE application schemas.

image

Figure 9 – Examples of a rectified grid (left) and a referenceable grid (right)

image

Figure 10 – Example of a time series

Conceptually the Land Use theme has a coverage component expressing the partition of a given area but technology is not yet fully operational and user communities not yet prepared to use coverages. Therefore it is recommended when the coverage technology will be widely implemented in operational tools to provide Land Use data according to coverages. In the meanwhile it is recommended to use a set of polygons with the constraint that these polygons do not overlap.

📘

Recommendation 6
The use of coverage for Land Use dataset will be recommended once the technology is effectively implemented in operational tools.

5.3. Application schema Land Use

5.3.1. Description

5.3.1.1. Narrative description and UML Overview

There is a multitude of different ways to describe land use. This is partly due to the wide range of aspects of the functional use of land embraced by land use, partly due to the versatility of the land use data, and partly due to the confusion between land use and land cover in existing datasets. There is only one "real world" but many different descriptions of this world circulate (depending on the aims, methodology and terminology of the observer). A common application schema cannot support all uses across all computer environments.

Therefore many, sometimes incompatible, ways of describing land use will continue to exist. Land Use classification starts from a universe of discourse – "the real world". This universe is analyzed according to a set of rules regarding the functional dimension of the land and water in terms of the economic activities in order to establish a classification system. A selected list of classes, also named LUTypes (possibly parameterized) from the classification system, generates a nomenclature (analogous to a Feature catalogue) as part of any particular Application schema.

Different classification systems can be matched and compared when they are well documented.

The solution used in this INSPIRE data specification is therefore to create an application schema (named Land Use) that defines feature types but is as open ended as possible with respect to particular classification systems. This approach assures that a wide range of data based on different land use classification systems can co-exist in INSPIRE, as long as these systems are sufficiently well documented. The application schema provides mechanisms to document several classification systems. In order to allow progress in the area of semantic interoperability, i.e. the capacity to compare datasets natively connected to various classification systems, the application schema proposes a hierarchical INSPIRE Land Use classification system (HILUCS), general enough to allow any Land Use feature to be linked to a Land Use type from the classification system. This applies to all land use datasets. This HILUCS is hierarchical in order to allow semantic generalisation and flexibility.

The Land Use theme is itself split up into four application schemas according to their temporal reference and definition (see Table 3):

  • The existing land use (current land use in the INSPIRE definition), which objectively depicts the use and functions of a territory as it has been and effectively still is in real life. Existing land use will be modelled according to three forms:

    • The Existing Land Use or ELU composed of polygons which objectively depicts the use and functions of a territory as it has been and effectively still is in real life.

    • The Sampled Land Use or SLU which corresponds to the use and functions as observed around a set of locations sampled over a given area.

    • The Gridded Land Use or GLU which correspond to a geo-referenced gridded version of an existing land use dataset.

  • The Planned Land Use or PLU (Future Planned Land Use in the INSPIRE definition), which is composed of spatial plans, defined by spatial planning authorities, depicting the possible utilization of the land in the future. This information could be modelled either as polygons,lines and points or as raster data.

image

Table 3 – Classification of the Land Use application schemas according to their temporal reference and geometry definition

For building the Land Use application schemas, common aspects are first defined for Land Use, it includes the HILUCS principles (see section 5.3.1.1.1). These common aspects are then applied for the description of the existing land use application schema (present or past) (see section 5.3.1.1.2), the sampled land use application schema (see section 5.3.1.1.3), the gridded land use application schema (see section 5.3.1.1.4) and the planned land use application schema (see section 5.3.1.1.5).

5.3.1.1.1. Common aspects

The common aspects for Land Use corresponds to a Land Use dataset that covers an area and provides a partition of that area with polygons that are mutually exclusive or with pixels (see Figure 11). The area covered by a Land Use data set may differ from the area managed by an authority due to multiple reasons including the data capture method (e.g. from imagery) or the legal context. The common aspects are also valid for a Land Use dataset that provide Land Use information attached to a discrete set of location (samples) as shown in Figure 11. These polygons and locations are described by a land use category.

The covered area can be irregularly shaped and multipart. The covered area of a dataset, also called extent, is defined depending on the dataset type and form. It is defined as the boundary of the geometrical union of all the land use objects present in the dataset.

image

Figure 11 – showing three types of datasets containing Land Use information: Top left polygons overlaid on an orthophotography, Top right pixels overlaid on administrative boundaries and water bodies, Down left set of discrete location, Down right classification system shown as a legend

The common aspects enable the assignment of a land use category to each polygon, pixel or location from the hierarchical INSPIRE Land Use classification system (HILUCS) through HILUCS values and presences (see Figure 12).

image

Figure 12 – UML Overview the common aspects and the Land Use classification systems

HILUCS will gradually evolve in a consistent way. The responsible body guiding this evolution is yet to be defined. The objective is to move towards a stable classification system at the European level. In order to ensure a minimum level of interoperability, it is mandatory to use the appropriate level of HILUCS that best fits the local nomenclatures.

📕

IR Requirement
Annex IV Section 4.8
Theme specific requirements

Any Land Use data sets shall assign to each polygon, pixel or location a land use type from the Hierarchical INSPIRE Land Use Classification System (HILUCS) at the most appropriate and detailed level of the hierarchy.

The mandatory HILUCS code will allow to consistently visualise datasets from diverse sources with the same legend.

HILUCSValue has a «codeList» data type in order to connect to a register managed within INSPIRE.

The common aspects also enable the assignment of a land use category from at least one classification system that is stable and well-defined either at an international (such as SEEA from the UN, LUCAS from Eurostat), national or infra-national level, through specific values or presences. Mapping such a specific land use classification system with HILUCS will improve interoperability. Examples of such mapping is provided in annex D.

Any well-defined and stable classification system defined at a national or infra-national level shall be stored in a register managed by the member states. These code lists do not need to be translated in English but only the correspondence between the national codes and the HILUCS code shall be documented.

📘

Recommendation 7
If specific land use is provided, the authority managing any well-defined and stable Classification system should document a mapping with the Hierarchical INSPIRE Land Use Classification System (HILUCS).

In order to allow progress in the area of semantic interoperability, i.e. the capacity to compare datasets connected to various (national) classification systems, the proposed hierarchical INSPIRE Land Use classification system (HILUCS) is general enough to allow any Land Use features to be linked to a Land Use type from the classification system. This applies to any land use data sets. HILUCS is hierarchical in order to allow semantic generalisation and flexibility.

For the definition of HILUCS the following principles have been applied:

  • Completeness: the classification enables to cover the entire land area for all types of land use including land without specific use.

  • Absence of overlap: the classification enables to assign for each piece of land a land use descriptor that describes the land use.

  • Dominance: this is to account for multi-purpose nature of land-use. The use corresponds to the use of a piece of land as a whole. The use is not always easy to define and is most of the time based on pragmatic rules or on political will in the case of planned land use.

  • Independency of scale and data collection tools: the classification, mainly due to its hierarchical nature, enables the accommodation of data obtained from different sources and at any scale.

  • Strict logic: the classification has a sound foundation that is further explained in this section.

  • Time independency: as the Land Use Theme addresses both the existing and the planned land use, the classification enables the definition of both the land use at the time of observation and the land use that is planned by spatial planning authorities.

The HILUCS has tried to be as pragmatic and easy to understand as possible in order to promote a consistent terminology. Rules for describing and naming headings for classes have reused widely recognized rationale and definitions such as NACE, LUCAS, SEEA. As this is a first attempt in the INSPIRE context, there should be a mechanism to manage the evolution of HILUCS. The next step of HILUCS will add characteristics representing the socio-economic aspects of the use of land necessary for environmental impact assessment.

The hierarchical nature of HILUCS has been devised based on two dimensions: the land and water perspective, and the economic perspective (see Figure 13). The objective is to provide a list of generic classes that every country could implement in their Land Use datasets at costs as marginal as possible enabling a basic level of semantic interoperability between datasets from all countries.

Planning of the use of sea and the use of seabed has been taken into consideration. HILUCS is applicable although some further work is needed to construct the correspondence between HILUCS and the terminology used in this area of spatial planning.

It must be noted that the models are not meant to provide information on the use of the underground of land unless they indicate which uses are directly below or above ground level, restricted to their physical impact at ground level.

From the land perspective (and how territories function) three aspects have been taken into consideration:

  • Nature: it is the piece of land or water where most biodiversity (animal and vegetation) exists and develops. Obviously the agricultural land as well as forests and water bodies fall within nature as from a biodiversity point of view, animals use these areas for feeding or moving [Oxford dictionary says: Nature is the phenomena of the physical world collectively, including plants, animals, the landscape, and other features and products of the earth].

  • Networking: it is the piece of land enabling people to get connected to each other. Thus it includes roads, railways, canals and by extension electricity, gas and telecommunication networks.

  • Built up: these are the places where most of human activities take place when they are not in the natural environment or while travelling. Thus it includes residential areas as well as manufactures and mining & quarrying but also stadiums and sports area.

From an economical perspective, modern economy distinguishes at a basic level three activity categories:

  • The primary sector of the economy involves the extraction and production of raw materials, such as corn, coal, wood and iron.

  • The secondary sector of the economy involves the transformation of raw or intermediate materials into goods. This sector is often divided into light industry and heavy industry. Many of these industries consume large quantities of energy and require factories and machinery to convert the raw materials into goods and products. They also produce waste materials and waste heat that may pose environmental problems or cause pollution.

  • The tertiary sector of the economy involves the provision of services to consumers and businesses, activities where people offer their knowledge, skills and time to improve productivity, performance, potential, and sustainability. The basic characteristic of this sector is the production of services instead of end products. Services (also known as "intangible goods") include attention, advice, experience, and discussion. It includes a way to describe a knowledge-based part of the economy which typically includes services such as information generation and sharing, information technology, consultation, education, research and development, financial planning, and other knowledge-based services as well as government.

From an INSPIRE point of view most of the 34 themes actually directly or indirectly refer to geographical objects of the real world. These objects may be connected to land use. The list below is an indication of the INSPIRE themes connected to Land Use. HILUCS is not meant to describe the uses in the same detail as the other themes do.

  • annex I theme 7 and 8 is dealing with transport and hydrographical networks,

  • annex II theme 4 geology may be dealing with surface bed rocks,

  • annex III theme 2 building may enable to derive Land Use class from the information of activities occurring in buildings within a specific area

  • annex III theme 5 may include hospitals and clinics,

  • annex III theme 6 is dealing with Utility and government services,

  • annex III themes 8 and 9 with production, industrial, agricultural and aquaculture facilities,

  • annex III theme 18 with habitats and biotopes, and

  • annex III theme 20 and 21 with energy resources and mineral resources.

Combining the 3 categories of the Land perspective and the 3 categories of the economic perspective one can relate the different characteristics of Land Use that are relevant to each combination.

image

Figure 13 – Land perspective and economic perspective in HILUCS

The use of HILUCS (necessarily multi-language) is a first attempt. It will require revisiting within three years and it is recommended to place the maintenance under the auspices of CEMAT with potentially EEA as the actual secretariat and EIONET as the technical body to involve member states. An alternative would be to use EUROSTAT or DG Regio and ESPON to instrument the maintenance of HILUCS.

📘

Recommendation 8

It is recommended that a working party within INSPIRE shall be entrusted to propose an authority, a process and a mechanism for managing the evolution of HILUCS.
5.3.1.1.2. Existing land use

The Existing Land Use application schema (see Figure 14) corresponds to a dataset that depicts the reality of the land use at a certain time.

Usage of dataset depicting existing land use may require providing information on the same piece of land at different time. The application schema does not implement this requirement. It means that the existing land use on the same area at two different times will be provided as two different datasets.

The «featureType» ExistingLandUseDataset contains the ExistingLandUseObject that correspond to an area having a unique defined land use.

An ExistingLandUseDataset may be created from several sources. Thus each ExistingLandUseObject may be associated with the time the documented land use corresponds to (attribute observationDate of «featureType» ExistingLandUseObject in Figure 14).

image

Figure 14 – UML Overview of the Existing Land Use application schema

The Existing Land Use application schema enables the provision of information on land uses inside one land use object. The ExistingLandUseObject may be associated with

  • 1 to many hilucsLandUse that represents the Land Use for the polygon from the economical point of view. It makes possible the assignment of more than one hilucsLandUse existence when they cannot be managed by hilucsPresences.

  • 0 to many «dataType» hilucsPresence and specificPresence to collect more than one hilucsLandUse existence perfectly identifiable by importance order or percentages.

  • 1 to many specificLandUse from other well-defined and stable classification system (national or local).

  • 0 to many «dataType» specificPresence, to collect more than one specificLandUse existence perfectly identifiable by importance order or percentages.

According to these possibilities, four situations are identified (see Table 4):

  • the land use object is associated with just one land use, its dominant land use: hilucsLandUse will have only one value (cardinality of 1) (see Figure 15 )

type1-exampleA

Figure 15 – Land Use object with only one hilucsLandUse value

  • the land use object is associated with several land uses with no knowledge of relative importance: hilucsLandUse will have several values (cardinality greater than 1). This fact happens in different circumstances, when mapping between national classes and HILUCS is not complete for few detail in national classes (example A); or when information is supplied at different vertical levels (example B) or at different times (example C) (see Figure 16):

type2-exampleA
type2-exampleB
type2-exampleC

Figure 16 – Land Use object with several hilucsLandUse value with no knowledge of relative importance

  • the land use object is associated with several land uses with the knowledge of relative importance but no knowledge of the proportion: HilucsLandUse will have one value (cardinality of 1) being the dominant land use and hilucsPresence will provide the ordered list of land use but without informing on percentages (see Figure 17),

type3-exampleA

Figure 17 – Land Use object with several hilucsLandUse value with knowledge of relative importance

  • the land use object is associated with several land uses with the knowledge of relative importance and proportion: HilucsLandUse will have one value (cardinality of 1) being the dominant land use, and hilucsPresence will provide the ordered list of land use together with percentages (see Figure 18),

type3-exampleB

Figure 18 – Land Use object with several hilucsLandUse value with knowledge of relative importance and propotion

image

Table 4 – Options for representing land uses

The opportunity of providing several land uses will not indicate the location of each land uses but it will enable the provision of their relative importance, and the opportunity of providing their respective percentages gives the possibility to enable calculations of the surface of each land use inside one area. But only one type of presence (importance orders or percentages) can be supplied at same time.

SpecificLandUse always has a constant cardinality of 1, only one specific value can be supplied. However specificPresence works similarity than hilucsPresence.

The two attributes 'percentage' are given for both the hilucsPresence and the specificPresence as it is not expected that the Member States will redraw the ExistingLandUseObject limits. These are voidable as it may exist real situation where multiple uses exist in a given area without knowing their relative importance.

The extent of an ExistingLandUseDataset is defined as the boundary of the union of all the polygons (ExistingLandUseObject) that are a member of the ExistingLandUseDataset (see Figure 19)

image

Figure 19 – the dotted line defines the Extent of an ExistingLandUseDataset

5.3.1.1.3. Sampled Land Use

The Sampled Land Use application schema (see Figure 20) corresponds to a dataset that depicts the reality of the land surface at discrete location on the earth. Often these datasets are collected for statistical purposes to provide estimates of land use over wider areas.

The «featureType» SampledExistingLandUseDataset contains the LandUseSample that corresponds to a location which land use information is gathered at.

A SampledExistingLandUseDataset may correspond to surveys done at different moment. Thus each LandUseSample may be associated with the time when the survey has been performed (attribute observationDate of «featureType» LandUseSample in Figure 20).

The Sampled Land Use application schema enables the provision of information on other land uses besides the dominant land use at the surveyed location. The LandUseSample may be associated with 1 to many hilucsLandUse, 0 to many «dataType» hilucsPresence, 1 to many specificLandUse and 0 to many «dataType» specificPresence. That will enable to provide importances and percentages in similar way than for Existing Land Use. The same four situations are identified (see Table 3 in 5.3.1.1.2).

image

Figure 20 – UML Overview of the Sampled Land Use application schema

The extent of a SampledExistingLandUseDataset is defined as the convex hull that includes all the locations which land use information is gathered at (ExistingLandUseSample (see Figure 21)

NewExtentSELU

Figure 21 – the dotted line defines the Extent of an SampledExistingLandUseDataset

5.3.1.1.4. Gridded Land Use

The gridded land use application schema corresponds to a dataset that depicts land use with pixels, each pixel being associated with 1 hilucspresence or (exclusive) 1 specificPresence (see Figure 22 where range in the NOTE expresses the way this association is done).

The pixels are grouped in a coverage («featureType» LandUseGridCoverage in the UML overview in Figure 22). Coverage («featureType» CoverageByDomainAndRange::RectifiedGridCoverage) inherits the properties from the coverage as described in section 5.2.8. Only the GridCoverage subtypes of CoverageByDomainAndRange is permitted.

📕

IR Requirement
Annex IV Section 4.8
Theme specific requirements

The spatial object type CoverageByDomainAndRange must only be of subtypes of GridCoverage.

The definitions below are exported from the above mentioned document:

  • CoverageByDomainAndRange: coverage which provides the domain and range as separate properties.

  • MultiPointCoverage: coverage characterized by a finite domain consisting of points. Usually the

  • GridCoverage : coverage whose domain consists of a collection of grid points

image

Figure 22 – UML Overview of the gridded land use coverage

5.3.1.1.5. Planned land use

The planned land use conceptual schema (see Figure 23) corresponds to a dataset that corresponds to a spatial planning document. Geographical information as well as the informative or descriptive parts contained in a spatial planning documents are taken into consideration in the Land Use data application schema. Only the spatial planning documents that are or have to be legally adopted by an authority and are opposable to third parties are considered within INSPIRE.

A spatial planning document corresponds to the «featureType» SpatialPlan. It has specific attributes such as its name (planTypeName) and the level of the administrative hierarchy it has been adopted in (levelOfSpatialPlan). It is possible to attach other information such as the legislation reference or the date and reference of the legal act that make it entering into force (see UML overview in Figure 23).

The concept of zoning is part of Planned Land Use in many countries. The zoning is composed of polygons that are mutually exclusive. Zoning provides regulation on how LandUse can evolve. The «featureType» SpatialPlan contains the «featureType» ZoningElement which allow expressing the land use that the administrative authority plans through its attribute hilucsLandUse. ZoningElements have several specific attributes such as the nature of the regulation (regulationNature), indications on dimension rules that apply to the use of land and reference to the applicable regulation.The zoning elements are always viewed as polygons.

The nomenclature provides information on the type of land use that is permitted or forbidden inside each zoning element.

The attribute hilucsLandUse has a multiplicity of 1 to many because planners on the one hand reserve areas for the future installation of economic activities not knowing a priori which activities will be installed and on the other hand they more and more create areas for "non-conflicting" activities or "mixed zones". Thus providing several hilucsLandUse values enables to provide the list of HILUCSValue that may apply to a ZoningElement.

Where in a SpatialPlan, areas are not subject to zoning, it is up to the data provider to decide on one of the following solutions:

  • consider the area as a "hole"

  • consider the area as a ZoningElement with the HILUCS code corresponding to "notKnownLandUse"

image

Figure 23 – UML Overview of the Planned Land Use application schema

Supplementary regulation

Supplementary information is often present in spatial planning document and delimits locations where a specific regulation applies and supplements the regulations of the zoning. These supplementary regulations may be seen as a buffer around an object of the real world. A point or a line can bear the regulation. This supplementary information is implemented in the «featureType» SupplementaryRegulation.

For any given point within a SpatialPlan, the intended land use is given by the attributes of the Zon-ingElement it falls into. The FeatureType SupplementaryRegulation must be used if any intention or limitation also exists at this point.

A specific nomenclature indicates the types of Supplementary Regulations that may exist in the spatial plan. It is country-dependant as it directly links to legal articles. The application schema enables the documentation of the fact that a Supplementary Regulation exists at a certain location and allows to connect to the description on how it affects the land use via country-dependant mechanism. These Supplementary Regulations vary in nature inside any spatial plan.

Figure 24 illustrates Supplementary Regulations that may exist over a given area. The type of supplementary regulations is given by the attributes supplementaryRegulation (with values from a hierarchical supplementary regulation code list managed within INSPIRE) and localSupplementaryRegulation of the «featureType» SupplementaryRegulation (with values from a local code list). Mapping the equivalence between these values should be provided by data producers. Further work is though needed for achieving a European harmonisation on that matter; annex E provides the proposed hierarchical INSPIRE supplementary regulation code list (HSRCL).

NOTE1: by extension, any point or line that in a spatial plan provides information related to HILUCS should be modelled as a SupplementaryRegulation with the code corresponding to "other supplementary regulation" in the HSRCL.

NOTE2: Any information related to the use of the underground should be modelled as a SupplementaryRegulation.

NOTE3: Planned land use incorporate elements that in the real world can be related to other INSPIRE spatial data themes such as Area management/restriction/regulation zones and reporting units (AM, Annex III theme 11) or Natural Risk Zones (NZ, annex III theme 12). These will be seen as supplementary regulation in the Land Use data model (planned land Use) as soon as this information is incorporated in the legal spatial plan, i.e. only information that is geographical and legally binding in the spatial plan will be considered as a supplementary regulation although it may belong to another theme. For example, any Restriction/Regulation Zone that is not explicitly incorporated in a spatial plan belongs to the AM theme, and any Restriction/Regulation Zone that is incorporated in a spatial plan (i.e. whose geometry and attributes are included in the "paper form" spatial plan) will be modelled as supplementary regulation.

📕

IR Requirement
Annex IV Section 4.8
Theme specific requirements

Where a zone has been established to regulate planned land use and defined within a legally binding spatial plan, it falls within the scope of the Land Use theme and shall be encoded as a SupplementaryRegulation. However, if the zone has been established by legislative requirement but not defined within a legally binding spatial plan, then it shall be encoded as a ManagementRestrictionOrRegulationZone.
📘

Recommendation 9

The codelist for SupplementaryRegulation (see annex C) is a first draft. It is recommended that Member states start the process of mapping their national code list with the proposed one and that a working party be established at the European level to make progress towards an improved European code list for supplementary regulations (HSRCL).
image

Figure 24 – graphical representation of Supplementary Regulations overlaid on a topographic map

Other aspects

Planned land use datasets are specific as they correspond to legal documents containing the regulations. The application schema implements the requirement to include inside the dataset the digital facsimile of the regulation («dataType» DocumentCitation). But the regulation itself may be attached to the spatial plan as well as to any Zoning Element or to any Supplementary Regulations. The «featureType» OfficialDocumentation implements that requirement. OffcialDocumentation can either be the text itself, the reference to the official journal that contains it or the URL of the document that contains it.

The scanned version of any maps included in spatial planning documents may also be associated to the spatial plan («dataType» DocumentCitation). The objective for the provision of scanned map is two fold:

  • allow the provision of the scanned version of the official spatial plan together with the vector SpatialPlan because only the paper based version is the official one in many member states,

  • allow the provision of spatial plans in digital form where no vector data exists.

The attribute planDocument of the feature type OfficialDocumentation must be used to provide scanned version of a spatial plan either as text, image or georeferenced image. The MIME extension should be used to inform on its format.

The PLU application schema also accommodates the situation where several spatial plans have already been aggregated into a single dataset as well as situation where several spatial plan has been aggregated into a single spatial plan itself being a single dataset.

The extent of a SpatialPlan is defined as the limit of the union of all the ZoningElements and the SupplementaryRegulation that are a member of the SpatialPlan (see Figure 25).

image

Figure 25 – the dotted line defines the Extent of a SpatialPlan where in blue are the SupplementaryRegulation and in red the ZoningElement

Where a SpatialPlan only contains the scanned version of a paper map, the extent should be defined as the outer limit of the cartographic image of the spatial plan (see Figure 26)

image

Figure 26 – the dotted line defines the Extent of a SpatialPlan that only contains a scanned version of the spatial plan

Figure 27 provides a UML overview of the code lists used in the Planned Land Use application schema

Figure 28 provides a UML overview of the data types used in the Planned Land Use application schema

Figure 29 provides a UML overview of the data type LegislationReference from the generic conceptual model used in the Planned Land Use application schema.

image

Figure 27 – UML Overview of the Planned Land Use code lists

image

Figure 28 – UML Overview of the Planned Land Use data types

image

Figure 29 – UML diagram of document and legislation citation from Generic Conceptual Model

5.3.1.2. Consistency between spatial data sets

Spatial plans are often drawn on the backdrop of another map (e.g. cadastral parcels or topographic data or orthoimagery). However, the INSPIRE Planned Land Use data specification represents spatial plans as absolute, not relative geometries. That is, they have their own, absolute geometries 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 their spatial plans if there are changes to the backdrop data, and in any case, the legal definition of a spatial plan remains fixed even if there are underlying changes to the backdrop data. Metadata may provide information on the backdrop that has been used at the time the spatial plan enters into force.

Existing Land Use data is often collected in combination with Land Cover data and in that case geometries in the two datasets will often be equivalent. Because there is no relationship in INSPIRE between Land Use and Land Cover this consistency will not be enforced.

It can be possible that different spatial plans (different datasets), for example of different levels (municipal and regional) or of different times (one from 1970 and one from 2010), are overlapping.

Data providers may solve the slivers[15] between adjacent spatial plans if they provide such a combined data set. If slivers cannot be resolved, it is recommended to provide different datasets. INSPIRE will not thus solve the slivers issues.

At a regional level it is not necessary to take care of municipality borders, in contrast at the municipality level (e.g. preparatory land-use plans for the entire area) zoning elements should not overlay with zoning elements of a neighbouring municipality. It is up to data providers to possibly resolve such slivers. INSPIRE will not provide mechanisms for that level of harmonisation.

Annex I of this document provides example of spatial plans at state level modelled according to the planned land use data application schema.

5.3.1.3. Identifier management

The reason for having INSPIRE identifiers are twofold:

  • provide a stable identifier for users to liaise with their own information,

  • provide a stable identifier internal to the dataset in order to implement the relationships identified in the application schema.

Regarding ExistingLandUseDataSet and SampledExistingLandUseDataSet, stable identifiers are required when several datasets provide information over the same area but at different date. They ease the construction of how land use evolved through time.

At national level, Spatial plans usually have a unique identifier but sub-elements (e.g. ZoningElement and SupplementaryRegulation) may have identifiers that are only unique within the context of a given dataset. An inspireId can be constructed by combining the identifiers of the plan with the local identifier.

5.3.1.4. Modelling of object references

Spatial plans are legal documents that regulate what developments are allowed, allowed under certain circumstances and not allowed in an area. The various parts of the plan use the OfficialDocumentation object to make references to the legal text or a specific location in the legal document or even to other documents such as scanned versions of the plan.

Furthermore, Spatial Plans can be provided as scanned documents or structural drawing that are not always geo-referencable maps (See Figure 30 as an example).

image

Figure 30 – example of a non-georeferencable map in a spatial plan (Scot Flandre-Dunkerque)

A link to these documents can be provided via the officialDocumentation association (see Figure 23).

5.3.1.5. Temporality representation

In Existing Land Use the temporal attributes validFrom and validTo are used to indicate when the given object is valid in reality (as opposed to the beginLifespanVersion and endLifespanVersion that gives information on the validity of the object in the system). In many cases this information will not be known: It may be observed that an area has changed from one land use type to another, but not when the change happened. In this case the observationDate can be used to specify when the new type was observed.

In Planned Land Use a SpatialPlan describes the future and it has the attributes validFrom and validTo to define the validity of the SpatialPlan in reality, i.e. the time period during which the rules of the plan are legally valid. For spatial plans the end date of the legal validity may not be known, e.g. when a spatial plan is valid till it is superseded by a more recent plan. In that case the validTo date will have the void value. It is also possible that (part of) a spatial plan is annulled by a legal body. In that case the valid to date will be filled.

The application schemas also are usable for archived datasets although data providers may decide not to provide the corresponding data through INSPIRE.

5.3.2. Land Use Nomenclature Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Land Use Nomenclature

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

HILUCSPercentage

Land Use Nomenclature

«dataType»

HILUCSPresence

Land Use Nomenclature

«union»

HILUCSValue

Land Use Nomenclature

«codeList»

LandUseClassificationValue

Land Use Nomenclature

«codeList»

SpecificPercentage

Land Use Nomenclature

«dataType»

SpecificPresence

Land Use Nomenclature

«union»
5.3.2.1. Data types
5.3.2.1.1. HILUCSPercentage
HILUCSPercentage

Name:

HILUCS percentage

Definition:

Percentage of land use object that is covered by this HILUCS presence.

Description:

NOTE1:The percentage is according to the socio-economic or functional importance of the use.

NOTE2:examples are provided in the narrative description part of the data specification.

Stereotypes:

«dataType»

Attribute: hilucsValue

Value type:

HILUCSValue

Definition:

HILUCS category for this HILUCS percentage.

Multiplicity:

1

Attribute: percentage

Value type:

Integer

Definition:

Percentage of land use object that is covered by this specific presence.

Description:

NOTE The percentage is according to the socio-economic importance of the use. In section 5.2.1.1.2. examples of the use of percentages are given.

Multiplicity:

1
5.3.2.1.2. HILUCSPresence
HILUCSPresence

Name:

HILUCS presence

Definition:

Presence of one or several HILUCS values in an area, indicated either as the percentage covered for each value or as the values listed in their order of importance.

Description:

The HILUCS presence data type enables the provision of information on land uses inside one land use object in order to collect more than one land use existence perfectly identifiable by importance order or percentages.
NOTE 1: The order of land use value presence without percentages enable providing an order of dominance/importance of each land use present in the land use object
NOTE 2: The sum of the percentages can be below 100%, or above. The order is provided according to the respective importance when the percentages are not known.

Stereotypes:

«union»

Attribute: orderedList

Value type:

HILUCSValue

Multiplicity:

1..*

Attribute: percentageList

Value type:

HILUCSPercentage

Multiplicity:

1..*
5.3.2.1.3. SpecificPercentage
SpecificPercentage

Name:

specific percentage

Definition:

Percentage of land use object that is covered by this specific presence.

Stereotypes:

«dataType»

Attribute: specificValue

Value type:

LandUseClassificationValue

Definition:

specific value category for this specific percentage.

Multiplicity:

1

Attribute: percentage

Value type:

Integer

Definition:

Percentage of land use object that is covered by a specific presence.

Description:

NOTE The percentage is according to the socio-economic importance of the use. In section 5.2.1.1.2. examples of the use of percentages are given.

Multiplicity:

1
5.3.2.1.4. SpecificPresence
SpecificPresence

Name:

specific presence

Definition:

Presence of one or several land use classification values in an area according to the code list provided by the data provider, indicated either as the percentage covered for each value or as the values listed in their order of importance.

Description:

NOTE 1: The order of land use value presence without percentages enable providing an order of dominance/importance of each land use present in the land use object
NOTE 2: The sum of the percentages can be below 100%, or above. The order is provided according to the respective importance when the percentages are not known.

Stereotypes:

«union»

Attribute: orderedList

Value type:

LandUseClassificationValue

Multiplicity:

1..*

Attribute: percentageList

Value type:

SpecificPercentage

Multiplicity:

1..*
5.3.2.2. Code lists
5.3.2.2.1. HILUCSValue
HILUCSValue

Name:

HILUCS value

Definition:

List of land use categories to be used in INSPIRE Land Use and agreed at the European level.

Description:

This list is populated with the land use categories of the Hierarchical INSPIRE Land Use Classification System (HILUCS).

The elements of the list should be both applicable to existing land use and planned land use.

Extensibility:

none

Identifier:

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

Values:

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

Name:

land use classification value

Definition:

List of land use categories to be used in INSPIRE Land Use and agreed at a national or local level.

Description:

This CodeList is empty in the INSPIRE context and must be extended by each data provider in their national codeList register.

Extensibility:

any

Identifier:

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

Values:

The allowed values for this code list comprise any values defined by data providers.
5.3.2.3. Imported types (informative)

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

5.3.2.3.1. Integer
Integer

Package:

Numerics

Reference:

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

5.3.3. Existing land use Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Existing Land Use

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

ExistingLandUseDataSet

Existing Land Use

«featureType»

ExistingLandUseObject

Existing Land Use

«featureType»
5.3.3.1. Spatial object types
5.3.3.1.1. ExistingLandUseDataSet
ExistingLandUseDataSet

Name:

existing land use data set

Definition:

An existing land use data set is a collection of areas for which information on existing (present or past) land uses is provided.

Stereotypes:

«featureType»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the existing land use dataset.

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: extent

Name:

existing land use data set

Value type:

GM_MultiSurface

Definition:

Boundary of the geometrical union of all the instances of the spatial object type ExistingLandUseObject.

Multiplicity:

1

Attribute: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the existing land use data set was inserted or changed in the provided set of data.

Multiplicity:

1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the existing land use data set was superseded or retired in the provided set of data.

Multiplicity:

0..1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: name

Value type:

CharacterString

Definition:

Human readable name of the data set.

Multiplicity:

1

Attribute: validFrom

Value type:

Date

Definition:

the time when the existing land use data set started to exist in the real world

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

Date

Definition:

The time from which this existing land use data set no longer exists in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Association role: member

Value type:

ExistingLandUseObject

Definition:

Existing land use objects that belong to this existing land use data set.

Multiplicity:

0..*
5.3.3.1.2. ExistingLandUseObject
ExistingLandUseObject

Name:

existing land use object

Definition:

An existing land use object describes the land use of an area having a homogeneous combination of land use types.

Stereotypes:

«featureType»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the existing land use object.

Description:

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: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

Multiplicity:

1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

Multiplicity:

0..1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: geometry

Value type:

GM_MultiSurface

Definition:

Geometric representation of spatial area covered by this spatial object.

Multiplicity:

1

Attribute: hilucsLandUse

Value type:

HILUCSValue

Definition:

Land use HILUCS classes that are present in this existing land use object.

Description:

NOTE The Existing Land Use model enables the provision of information on land uses inside one land use object. The ExistingLandUseObject may be associated with 1 to many HILUCSLandUse that represents the Land Uses for the polygon from the economical point of view. It makes possible the assignment of more than one HILUCSLandUse existences when they cannot be managed by HILUCSPresences.

Multiplicity:

1..*

Attribute: hilucsPresence

Name:

land use presence

Value type:

HILUCSPresence

Definition:

Actual presence of a land use category according to HILUCS within the object.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: specificLandUse

Value type:

LandUseClassificationValue

Definition:

Land Use Category according to the nomenclature specific to this data set.

Description:

Reference to an entry in the classfication that is part of the SpecificLandUseClassification.

Multiplicity:

1..*

Stereotypes:

«voidable»

Attribute: specificPresence

Name:

land use presence

Value type:

SpecificPresence

Definition:

Actual presence of a land use category within the object.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: observationDate

Name:

Observation Date.

Value type:

Date

Definition:

The observation date associated to a description.

Description:

Defines the observation date of the description. It could be the date of an aerial/satellite acquisition or a field survey. The observation date allows the user to have accurate date of when the description was made in the real word. In a database, not all objects are necessarily captured at the same time.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: validFrom

Value type:

Date

Definition:

The time when the phenomenon started to exist in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

Date

Definition:

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

Multiplicity:

0..1

Stereotypes:

«voidable»

Association role: dataset

Value type:

ExistingLandUseDataSet

Definition:

Existing land use data set to which this land use object belongs.

Multiplicity:

1
5.3.3.2. Imported types (informative)

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

5.3.3.2.1. CharacterString
CharacterString

Package:

Text

Reference:

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

Package:

Date and Time

Reference:

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

Package:

Date and Time

Reference:

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

Package:

Geometric aggregates

Reference:

Geographic information — Spatial schema [ISO 19107:2003]
5.3.3.2.5. HILUCSPresence
HILUCSPresence

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

Presence of one or several HILUCS values in an area, indicated either as the percentage covered for each value or as the values listed in their order of importance.

Description:

The HILUCS presence data type enables the provision of information on land uses inside one land use object in order to collect more than one land use existence perfectly identifiable by importance order or percentages.
NOTE 1: The order of land use value presence without percentages enable providing an order of dominance/importance of each land use present in the land use object
NOTE 2: The sum of the percentages can be below 100%, or above. The order is provided according to the respective importance when the percentages are not known.
5.3.3.2.6. HILUCSValue
HILUCSValue

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

List of land use categories to be used in INSPIRE Land Use and agreed at the European level.

Description:

This list is populated with the land use categories of the Hierarchical INSPIRE Land Use Classification System (HILUCS).

The elements of the list should be both applicable to existing land use and planned land use.
5.3.3.2.7. Identifier
Identifier

Package:

Base Types

Reference:

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

Definition:

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

Description:

NOTE1 External object identifiers are distinct from thematic object identifiers.

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

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

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

List of land use categories to be used in INSPIRE Land Use and agreed at a national or local level.

Description:

This CodeList is empty in the INSPIRE context and must be extended by each data provider in their national codeList register.
5.3.3.2.9. SpecificPresence
SpecificPresence

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

Presence of one or several land use classification values in an area according to the code list provided by the data provider, indicated either as the percentage covered for each value or as the values listed in their order of importance.

Description:

NOTE 1: The order of land use value presence without percentages enable providing an order of dominance/importance of each land use present in the land use object
NOTE 2: The sum of the percentages can be below 100%, or above. The order is provided according to the respective importance when the percentages are not known.

5.3.4. Gridded land use Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Gridded Land Use

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

ExistingLandUseGrid

Gridded Land Use

«featureType»
5.3.4.1. Spatial object types
5.3.4.1.1. ExistingLandUseGrid
ExistingLandUseGrid

Name:

existing land use grid

Subtype of:

RectifiedGridCoverage

Definition:

An existing land use grid is a collection of pixels for which information on existing (present or past) land use is provided. The HILUCS system shall be used for classification.

Stereotypes:

«featureType»

Attribute: name

Value type:

CharacterString

Definition:

Human readable name of the data set.

Multiplicity:

1

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the sampled land use data grid.

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: extent

Name:

extent

Value type:

EX_Extent

Definition:

Contains the extent of the data set.

Description:

NOTE Extents may be specified in space, time or space-time.

Multiplicity:

1

Attribute: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

Multiplicity:

1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

Multiplicity:

0..1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: validFrom

Value type:

Date

Definition:

First date at which this grid is a valid representation of reality.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

Date

Definition:

The time from which the grid is no longer a valid representation of reality.

Multiplicity:

1

Stereotypes:

«voidable»

Constraint: rangeIsCategoryOrNill

Natural language:

rangeSet values shall be of type CategoryOrNilReason NOTERange is based on either HILUCS or on a specific land use classification sytem defined by the data provider

OCL:

inv: rangeSet.forAll(oclIsKindOf(CategoryOrNilReason))
5.3.4.2. Imported types (informative)

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

5.3.4.2.1. CharacterString
CharacterString

Package:

Text

Reference:

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

Package:

Date and Time

Reference:

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

Package:

Date and Time

Reference:

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

Package:

Extent information

Reference:

Geographic information — Metadata [ISO 19115:2003/Cor 1:2006]
5.3.4.2.5. Identifier
Identifier

Package:

Base Types

Reference:

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

Definition:

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

Description:

NOTE1 External object identifiers are distinct from thematic object identifiers.

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

NOTE 3 The unique identifier will not change during the life-time of a spatial object.

RectifiedGridCoverage

RectifiedGridCoverage

Package:

Coverages (Domain and Range)

Reference:

INSPIRE Data Specifications – Base Models – Coverage Types, version 1.0 [DS-D2.10.2]

Definition:

Coverage whose domain consists of a rectified grid

Description:

A rectified grid is a grid for which there is an affine transformation between the grid coordinates and the coordinates of a coordinate reference system.

NOTE This type can be used for both discrete and continuous coverages.

5.3.5. Sampled land use Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Sampled Land Use

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

ExistingLandUseSample

Sampled Land Use

«featureType»

SampledExistingLandUseDataSet

Sampled Land Use

«featureType»
5.3.5.1. Spatial object types
5.3.5.1.1. ExistingLandUseSample
ExistingLandUseSample

Name:

existing land use sample

Definition:

Description of the existing land use that is present at the specific location.

Stereotypes:

«featureType»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the land use sample.

Description:

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: location

Value type:

GM_Point

Definition:

Location where the land use sample is taken.

Multiplicity:

1

Attribute: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

Multiplicity:

1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: hilucsLandUse

Value type:

HILUCSValue

Definition:

Land use HILUCS classes that are present in this existing land use sample.

Description:

NOTE The Sampled Existing Land Use model enables the provision of information on land uses inside one land use object. The ExistingLandUseObject may be associated with 1 to many HILUCSLandUse that represents the Land Uses for the polygon from the economical point of view. It makes possible the assignment of more than one HILUCSLandUse existences when they cannot be managed by HILUCSPresences.

Multiplicity:

1..*

Attribute: hilucsPresence

Name:

land use presence

Value type:

HILUCSPresence

Definition:

Actual presence of a land use category according to HILUCS within the object.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: specificLandUse

Value type:

LandUseClassificationValue

Definition:

Land Use Category according to the nomenclature specific to this data set.

Description:

Reference to an entry in the classfication that is part of the SpecificLandUseClassification provided by the data producer.

Multiplicity:

1..*

Stereotypes:

«voidable»

Attribute: observationDate

Name:

Observation Date.

Value type:

Date

Definition:

The observation date associated to a description.

Description:

Defines the observation date of the description. It could be the date of an aerial/satellital acquisition or a field survey. The observation date allows the user to have accurate date of when the description was made in the real word. In a database, not all object informations are necessarily captured at the same time.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: specificPresence

Value type:

SpecificPresence

Definition:

Actual presence of a land use category within the object.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

Multiplicity:

0..1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: validFrom

Value type:

Date

Definition:

The time when the phenomenon started to exist in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

Date

Definition:

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

Multiplicity:

0..1

Stereotypes:

«voidable»

Association role: dataset

Value type:

SampledExistingLandUseDataSet

Definition:

Data set to which this sample belongs.

Multiplicity:

1
5.3.5.1.2. SampledExistingLandUseDataSet
SampledExistingLandUseDataSet

Name:

sampled existing land use data set

Definition:

A sampled existing land use data set is a collection of locations for which information on existing (present or past) land uses is provided.

Stereotypes:

«featureType»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the sampled land use data set.

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: extent

Value type:

GM_MultiSurface

Definition:

The convex hull of all the instances of the spatial object type ExistingLandUseSample.

Multiplicity:

1

Attribute: name

Value type:

CharacterString

Definition:

Human readable name of the data set.

Multiplicity:

1

Attribute: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

Multiplicity:

1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

Multiplicity:

0..1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: validFrom

Value type:

Date

Definition:

First date at which this data set is valid in reality.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

Date

Definition:

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

Multiplicity:

0..1

Stereotypes:

«voidable»

Association role: member

Value type:

ExistingLandUseSample

Definition:

Reference to the members of the sampled existing land use data set.

Multiplicity:

0..*
5.3.5.2. Imported types (informative)

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

5.3.5.2.1. CharacterString
CharacterString

Package:

Text

Reference:

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

Package:

Date and Time

Reference:

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

Package:

Date and Time

Reference:

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

Package:

Geometric aggregates

Reference:

Geographic information — Spatial schema [ISO 19107:2003]
5.3.5.2.5. GM_Point
GM_Point

Package:

Geometric primitive

Reference:

Geographic information — Spatial schema [ISO 19107:2003]
5.3.5.2.6. HILUCSPresence
HILUCSPresence

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

Presence of one or several HILUCS values in an area, indicated either as the percentage covered for each value or as the values listed in their order of importance.

Description:

The HILUCS presence data type enables the provision of information on land uses inside one land use object in order to collect more than one land use existence perfectly identifiable by importance order or percentages.
NOTE 1: The order of land use value presence without percentages enable providing an order of dominance/importance of each land use present in the land use object
NOTE 2: The sum of the percentages can be below 100%, or above. The order is provided according to the respective importance when the percentages are not known.
5.3.5.2.7. HILUCSValue
HILUCSValue

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

List of land use categories to be used in INSPIRE Land Use and agreed at the European level.

Description:

This list is populated with the land use categories of the Hierarchical INSPIRE Land Use Classification System (HILUCS).

The elements of the list should be both applicable to existing land use and planned land use.
5.3.5.2.8. Identifier
Identifier

Package:

Base Types

Reference:

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

Definition:

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

Description:

NOTE1 External object identifiers are distinct from thematic object identifiers.

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

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

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

List of land use categories to be used in INSPIRE Land Use and agreed at a national or local level.

Description:

This CodeList is empty in the INSPIRE context and must be extended by each data provider in their national codeList register.
5.3.5.2.10. SpecificPresence
SpecificPresence

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

Presence of one or several land use classification values in an area according to the code list provided by the data provider, indicated either as the percentage covered for each value or as the values listed in their order of importance.

Description:

NOTE 1: The order of land use value presence without percentages enable providing an order of dominance/importance of each land use present in the land use object
NOTE 2: The sum of the percentages can be below 100%, or above. The order is provided according to the respective importance when the percentages are not known.

5.3.6. Planned Land Use Feature catalogue

Feature catalogue metadata

Application Schema

INSPIRE Application Schema Planned Land Use

Version number

3.0

Types defined in the feature catalogue

Type Package Stereotypes

BackgroundMapValue

Planned Land Use

«dataType»

DimensioningIndicationCharacterValue

Planned Land Use

«dataType»

DimensioningIndicationIntegerValue

Planned Land Use

«dataType»

DimensioningIndicationMeasureValue

Planned Land Use

«dataType»

DimensioningIndicationRealValue

Planned Land Use

«dataType»

DimensioningIndicationValue

Planned Land Use

«dataType»

LevelOfSpatialPlanValue

Planned Land Use

«codeList»

OfficialDocumentation

Planned Land Use

«featureType»

OrdinanceValue

Planned Land Use

«dataType»

PlanTypeNameValue

Planned Land Use

«codeList»

ProcessStepGeneralValue

Planned Land Use

«codeList»

RegulationNatureValue

Planned Land Use

«codeList»

SpatialPlan

Planned Land Use

«featureType»

SpecificSupplementaryRegulationValue

Planned Land Use

«codeList»

SupplementaryRegulation

Planned Land Use

«featureType»

SupplementaryRegulationValue

Planned Land Use

«codeList»

ZoningElement

Planned Land Use

«featureType»
5.3.6.1. Spatial object types
5.3.6.1.1. OfficialDocumentation
OfficialDocumentation

Name:

official documentation

Definition:

The official documentation that composes the spatial plan; it may be composed of, the applicable legislation, the regulations, cartographic elements, descriptive elements that may be associated with the complete spatial plan, a zoning element or a supplementary regulation . In some Member States the actual textual regulation will be part of the data set (and can be put in the regulationText attribute), in other Member States the text will not be part of the data set and will be referenced via a reference to a document or a legal act. At least one of the three voidable values shall be provided.

Description:

NOTE The LegislationCitation is the value type of the attribute regulation reference. An example of a regulation reference would be: http://www2.vlaanderen.be /ruimtelijk/grup/00350/00362_00001/data/ 212_00362_00001_d_0BVR.pdf.

Stereotypes:

«featureType»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of this spatial textual regulation.

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: legislationCitation

Value type:

LegislationCitation

Definition:

Reference to the document that contains the text of the regulation.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: regulationText

Value type:

CharacterString

Definition:

Text of the regulation.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: planDocument

Value type:

DocumentCitation

Definition:

Citation of scanned plans and structural drawings which may sometimes be geo-referenced or not,. E.g. raster images, vector drawings or scanned text.

Multiplicity:

0..1

Stereotypes:

«voidable»

Constraint: OneMustBeFilled

Natural language:

** At least one of the values must be populated with a non-void value

OCL:
5.3.6.1.2. SpatialPlan
SpatialPlan

Name:

spatial plan

Definition:

A set of documents that indicates a strategic direction for the development of a given geographic area, states the policies, priorities, programmes and land allocations that will implement the strategic direction and influences the distribution of people and activities in spaces of various scales. Spatial plans may be developed for urban planning, regional planning, environmental planning, landscape planning, national spatial plans, or spatial planning at the Union level.

Stereotypes:

«featureType»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the spatial plan.

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: extent

Value type:

GM_MultiSurface

Definition:

Geometrical union of all the instances of the spatial objects ZoningElement and SupplementaryRegulation. When a SpatialPlan is only composed of a document, the attribute extent is the border of the cartographic image that contains the land use information (i.e. the land use map extent).

Multiplicity:

1

Attribute: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

Multiplicity:

1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: officialTitle

Value type:

CharacterString

Definition:

Official title of the spatial plan.

Multiplicity:

1

Attribute: levelOfSpatialPlan

Name:

level of spatial plan

Value type:

LevelOfSpatialPlanValue

Definition:

Level of the administrative units covered by the plan.

Description:

Member states should make a mapping to this code list.

Multiplicity:

1

Attribute: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

Multiplicity:

0..1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: validFrom

Value type:

Date

Definition:

First date at which this spatial plan is valid in reality.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

Date

Definition:

The time from which the spatial plan no longer exists in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: alternativeTitle

Value type:

CharacterString

Definition:

Alternative (unofficial) title of the spatial plan.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: planTypeName

Value type:

PlanTypeName

Definition:

Name of the type of plan that the Member State has given to the plan.

Description:

NOTE The admissible values for this attribute are managed at the member state level via a code list

EXAMPLE:
FR: DTA, SCOT, PLU, etc.
DE: Bebauungsplan, Flächennutzungsplan, Regionalplan, Landesentwicklungsplan
NL: bestemmingsplan, structuurvisie.

Multiplicity:

1

Attribute: processStepGeneral

Value type:

ProcessStepGeneralValue

Definition:

General indication of the step of the planning process that the plan is undergoing.

Description:

NOTE This code list contains values that are common to most planning systems.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: backgroundMap

Name:

background map

Value type:

BackgroundMapValue

Definition:

Identification of the background map that has been used for constructing this Plan.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: ordinance

Value type:

OrdinanceValue

Definition:

Reference to relevant administrative ordinance.

Description:

NOTE This attribute is multiple because, independently from the current legal status of the plan, there can be references to more than one ordinance, in relation to the different steps that the planning process has already undergone (e.g. ordinance for the preparation of a new plan, ordinance of adoption, ordinance of approval, etc.).

Multiplicity:

1..*

Stereotypes:

«voidable»

Association role: officialDocument

Value type:

OfficialDocumentation

Definition:

Link to the official documents that relate to the spatial plan.

Multiplicity:

1..*

Stereotypes:

«voidable»

Association role: member

Value type:

ZoningElement

Definition:

Reference to the ZoningElements which belong to this SpatialPlan.

Multiplicity:

0..*

Association role: restriction

Value type:

SupplementaryRegulation

Definition:

Links to supplementary regulations providing information and/or limitations on the use of land/water that supplements the zoning as part of this spatial plan.

Multiplicity:

0..*
5.3.6.1.3. SupplementaryRegulation
SupplementaryRegulation

Name:

supplementary regulation

Definition:

A spatial object (point, line or polygon) of a spatial plan that provides supplementary information and/or limitation of the use of land/water necessary for spatial planning reasons or to formalise external rules defined in legal text.

Description:

NOTE the supplementary regulations affects all land use that overlap with the geometry
EXAMPLE an air field generates restriction in its surroundings regarding aircraft landing, radar and telecommunication devices. It is the buffer around these artefacts that generates the supplementary regulation on the Land Use.

Stereotypes:

«featureType»

Attribute: validFrom

Value type:

Date

Definition:

First date at which this version of this supplementary regulation is valid in reality.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

Date

Definition:

The time from which the supplementary regulation is no longer valid.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: specificSupplementaryRegulation

Value type:

SpecificSupplementaryRegulationValue

Definition:

Reference to a category of supplementary regulation provided in a specific nomenclature of supplementary regulations provided by the data provider.

Multiplicity:

1..*

Stereotypes:

«voidable»

Attribute: processStepGeneral

Value type:

ProcessStepGeneralValue

Definition:

General indication of the step of the planning process that the supplementary regulation is undergoing.

Description:

NOTE This code list contains values that are common to most planning systems.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: backgroundMap

Name:

background map

Value type:

BackgroundMapValue

Definition:

Identification of the background map that has been used for constructing the supplementary regulation.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

Multiplicity:

1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: dimensioningIndication

Value type:

DimensioningIndicationValue

Definition:

Specifications about the dimensioning that are added to the dimensioning of the zoning elements that overlap the geometry of the supplementary regulation.

Multiplicity:

0..*

Stereotypes:

«voidable»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the spatial object.

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: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

Multiplicity:

0..1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: geometry

Value type:

GM_Object

Definition:

Geometry of the piece of land on which the supplementary regulation applies.

Multiplicity:

1

Attribute: inheritedFromOtherPlans

Name:

inherited from other plans

Value type:

Boolean

Definition:

Indication whether the supplementary regulation is inherited from another spatial plan.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: specificRegulationNature

Name:

specific regulation nature

Value type:

CharacterString

Definition:

Legal nature of the land use regulation from a national perspective.

Description:

On member state level the legal classification for plan regulations may be complex. A supplementary regulation may be principally "bindingOnlyForAuthorities" but according to national law this regulation have to be more specified to explain the specific degree of binding. (e.g. on state or regional planning level in Germany: principles of spatial planning, other spatial planning requirements or goals of spatial planning).

NOTE This attribute complements the information provided by the attribute regulationNature.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: name

Value type:

CharacterString

Definition:

Official name of the supplementary regulation

Multiplicity:

0..*

Stereotypes:

«voidable»

Attribute: regulationNature

Value type:

RegulationNatureValue

Definition:

Legal nature of the land use regulation.

Description:

NOTE Indicates whether the land use regulation is legally binding or not.

Multiplicity:

1

Attribute: supplementaryRegulation

Value type:

SupplementaryRegulationValue

Definition:

Code of the supplementary regulation from the hierarchical supplementary regulation code list agreed at the European level.

Multiplicity:

1..*

Association role: plan

Value type:

SpatialPlan

Definition:

Link to the plan this supplementary regulation is part of.

Multiplicity:

1

Association role: officialDocument

Value type:

OfficialDocumentation

Definition:

Link to the Textual regulations that correspond to this supplementary regulation.

Multiplicity:

1..*

Stereotypes:

«voidable»
5.3.6.1.4. ZoningElement
ZoningElement

Name:

zoning element

Definition:

A spatial object which is homogeneous regarding the permitted uses of land based on zoning which separate one set of land uses from another.

Description:

Zoning elements refer to the regulation of the kinds of activities which will be acceptable on particular lots (such as open space, residential, agricultural, commercial or industrial). The intensity of use at which those activities can be performed (from low-density housing such as single family homes to high-density such as high-rise apartment buildings), the height of buildings, the amount of space that structures may occupy, the proportions of the types of space on a lot, such as how much landscaped space, impervious surface, traffic lanes, and parking may be provided.

Stereotypes:

«featureType»

Attribute: inspireId

Value type:

Identifier

Definition:

External object identifier of the spatial object.

Description:

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: geometry

Value type:

GM_MultiSurface

Definition:

Geometry of this zoning element

Multiplicity:

1

Attribute: validFrom

Value type:

Date

Definition:

The date when the phenomenon started to exist in the real world.

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: validTo

Value type:

Date

Definition:

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

Multiplicity:

0..1

Stereotypes:

«voidable»

Attribute: hilucsLandUse

Value type:

HILUCSValue

Definition:

Land use HILUCS class that is dominant in this land use object.

Multiplicity:

1..*

Attribute: beginLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

Multiplicity:

1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: hilucsPresence

Name:

land use presence

Value type:

HILUCSPresence

Definition:

Actual presence of a land use HILUCS category wihtin the object.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: specificLandUse

Value type:

LandUseClassificationValue

Definition:

Land Use Category according to the nomenclature specific to this data set.

Description:

Reference to an entry in the classfication that is part of the SpecificLandUseClassification.

Multiplicity:

1..*

Stereotypes:

«voidable»

Attribute: specificPresence

Name:

land use presence

Value type:

SpecificPresence

Definition:

Actual presence of a land use category wihtin the object.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: regulationNature

Value type:

RegulationNatureValue

Definition:

Legal nature of the land use indication.

Description:

NOTE Indicates whether the land use indication is legally binding or not.

Multiplicity:

1

Attribute: endLifespanVersion

Value type:

DateTime

Definition:

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

Multiplicity:

0..1

Stereotypes:

«lifeCycleInfo,voidable»

Attribute: processStepGeneral

Value type:

ProcessStepGeneralValue

Definition:

General indication of the step of the planning process that the zoning element is undergoing.

Description:

NOTE This code list contains values that are common to most planning systems.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: backgroundMap

Name:

background map

Value type:

BackgroundMapValue

Definition:

Identification of the background map that has been used for constructing this zoning element.

Multiplicity:

1

Stereotypes:

«voidable»

Attribute: dimensioningIndication

Value type:

DimensioningIndicationValue

Definition:

Specifications about the dimensioning of the urban developments.

Multiplicity:

0..*

Stereotypes:

«voidable»

Association role: plan

Value type:

SpatialPlan

Definition:

SpatialPlan which this ZoningElement belongs to.

Multiplicity:

1

Association role: officialDocument

Value type:

OfficialDocumentation

Definition:

Textual Regulation that is part of this zoning element.

Multiplicity:

1..*

Stereotypes:

«voidable»
5.3.6.2. Data types
5.3.6.2.1. BackgroundMapValue
BackgroundMapValue

Definition:

Information regarding the map that has been used as a background in the definition of a spatial plan, a zoning element or a supplementary regulation.

Stereotypes:

«dataType»

Attribute: backgroundMapDate

Name:

background map date

Value type:

DateTime

Definition:

Date of the background map used.

Multiplicity:

1

Attribute: backgroundMapReference

Value type:

CharacterString

Definition:

Reference to the background map that has been used.

Multiplicity:

1

Attribute: backgroundMapURI

Name:

background map URI

Value type:

URI

Definition:

URI referring to service that provides background map.

Multiplicity:

1

Stereotypes:

«voidable»
5.3.6.2.2. DimensioningIndicationCharacterValue
DimensioningIndicationCharacterValue

Name:

dimension indication character value

Subtype of:

DimensioningIndicationValue

Definition:

Dimensioning indication whose value is of type CharacterString.

Stereotypes:

«dataType»

Attribute: value

Value type:

CharacterString

Definition:

value of the dimension indications.

Multiplicity:

1
5.3.6.2.3. DimensioningIndicationIntegerValue
DimensioningIndicationIntegerValue

Name:

dimension indication integer value

Subtype of:

DimensioningIndicationValue

Definition:

Dimensioning indication whose value is of type integer.

Stereotypes:

«dataType»

Attribute: value

Value type:

Integer

Multiplicity:

1
5.3.6.2.4. DimensioningIndicationMeasureValue
DimensioningIndicationMeasureValue

Name:

dimension indication measure value

Subtype of:

DimensioningIndicationValue

Definition:

Dimensioning indication whose value is a measure.

Stereotypes:

«dataType»

Attribute: value

Value type:

Measure

Multiplicity:

1
5.3.6.2.5. DimensioningIndicationRealValue
DimensioningIndicationRealValue

Name:

dimension indication real value

Subtype of:

DimensioningIndicationValue

Definition:

Dimensioning indication whose value is a floating point number.

Stereotypes:

«dataType»

Attribute: value

Value type:

Real

Multiplicity:

1
5.3.6.2.6. DimensioningIndicationValue
DimensioningIndicationValue

Name:

Dimension Indication

Definition:

Specifications about the dimensioning of the urban developments.

Stereotypes:

«dataType»

Attribute: indicationReference

Value type:

CharacterString

Definition:

Description of the dimension indication.

Multiplicity:

1
5.3.6.2.7. OrdinanceValue
OrdinanceValue

Definition:

Reference to administrative ordinance. Ordinance is a regulation/rule that is adopted by an authority that is legally mandated to take such ordinance.

Stereotypes:

«dataType»

Attribute: ordinanceDate

Value type:

DateTime

Definition:

Date of the relevant administrative ordinance.

Description:

NOTE This attribute is multiple because, independently from the current legal status of the plan, there can be references to the dates of more than one ordinance, in relation to the different steps that the planning process has already undergone (e.g. ordinance for the preparation of a new plan, ordinance of adoption, ordinance of approval, etc.).

Multiplicity:

1

Attribute: ordinanceReference

Value type:

CharacterString

Definition:

Reference to relevant administrative ordinance.

Description:

NOTE This attribute is multiple because, independently from the current legal status of the plan, there can be references to more than one ordinance, in relation to the different steps that the planning process has already undergone (e.g. ordinance for the preparation of a new plan, ordinance of adoption, ordinance of approval, etc.).

Multiplicity:

1
5.3.6.3. Code lists
5.3.6.3.1. LevelOfSpatialPlanValue
LevelOfSpatialPlanValue

Name:

level of spatial plan

Definition:

Territorial hierarchy of plan.

Extensibility:

none

Identifier:

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

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.3.6.3.2. PlanTypeNameValue
PlanTypeNameValue

Name:

plan type name value

Definition:

Types of plans as defined in the Member States. The allowed values for this code list comprise any values defined by data providers.

Description:

NOTE For each plan type name a level of spatial plan must be provided using the code list LevelOfSpatialPlanValue

Extensibility:

any

Identifier:

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

Values:

The allowed values for this code list comprise any values defined by data providers.
5.3.6.3.3. ProcessStepGeneralValue
ProcessStepGeneralValue

Name:

process step general

Definition:

General indication of the step of the planning process that the plan is undergoing.

Description:

NOTE This code list contains values that are common to most planning systems.

Extensibility:

none

Identifier:

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

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.3.6.3.4. RegulationNatureValue
RegulationNatureValue

Name:

regulation nature

Definition:

Legal nature of the land use indication.

Extensibility:

none

Identifier:

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

Values:

The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
5.3.6.3.5. SpecificSupplementaryRegulationValue
SpecificSupplementaryRegulationValue

Name:

specific supplementary regulation value

Definition:

Category of supplementary regulation provided in a specific nomenclature of supplementary regulations provided by the data provider. The allowed values for this code list comprise any values defined by data providers.

Extensibility:

any

Identifier:

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

Values:

The allowed values for this code list comprise any values defined by data providers.
5.3.6.3.6. SupplementaryRegulationValue
SupplementaryRegulationValue

Name:

supplementary regulation value

Definition:

Types of conditions and constraints in spatial plans.

Description:

This list is populated with the categories of the Hierarchical Supplementary Regulation Code List (HSRCL).

Extensibility:

any

Identifier:

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

Values:

The allowed values for this code list comprise any values defined by data providers. INSPIRE Registry includes recommended values that may be used by data providers.
5.3.6.4. Imported types (informative)

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

5.3.6.4.1. Boolean
Boolean

Package:

Truth

Reference:

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

Package:

Text

Reference:

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

Package:

Date and Time

Reference:

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

Package:

Date and Time

Reference:

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

Package:

Base Types 2

Reference:

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

Definition:

Citation for the purposes of unambiguously referencing a document.
5.3.6.4.6. GM_MultiSurface
GM_MultiSurface

Package:

Geometric aggregates

Reference:

Geographic information — Spatial schema [ISO 19107:2003]
5.3.6.4.7. GM_Object
GM_Object (abstract)

Package:

Geometry root

Reference:

Geographic information — Spatial schema [ISO 19107:2003]
5.3.6.4.8. HILUCSPresence
HILUCSPresence

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

Presence of one or several HILUCS values in an area, indicated either as the percentage covered for each value or as the values listed in their order of importance.

Description:

The HILUCS presence data type enables the provision of information on land uses inside one land use object in order to collect more than one land use existence perfectly identifiable by importance order or percentages.
NOTE 1: The order of land use value presence without percentages enable providing an order of dominance/importance of each land use present in the land use object
NOTE 2: The sum of the percentages can be below 100%, or above. The order is provided according to the respective importance when the percentages are not known.
5.3.6.4.9. HILUCSValue
HILUCSValue

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

List of land use categories to be used in INSPIRE Land Use and agreed at the European level.

Description:

This list is populated with the land use categories of the Hierarchical INSPIRE Land Use Classification System (HILUCS).

The elements of the list should be both applicable to existing land use and planned land use.
5.3.6.4.10. Identifier
Identifier

Package:

Base Types

Reference:

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

Definition:

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

Description:

NOTE1 External object identifiers are distinct from thematic object identifiers.

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

NOTE 3 The unique identifier will not change during the life-time of a spatial object.
5.3.6.4.11. Integer
Integer

Package:

Numerics

Reference:

Geographic information — Conceptual schema language [ISO/TS 19103:2005]
5.3.6.4.12. LandUseClassificationValue
LandUseClassificationValue (abstract)

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

List of land use categories to be used in INSPIRE Land Use and agreed at a national or local level.

Description:

This CodeList is empty in the INSPIRE context and must be extended by each data provider in their national codeList register.
5.3.6.4.13. LegislationCitation
LegislationCitation

Package:

Base Types 2

Reference:

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

Definition:

Citation for the purposes of unambiguously referencing a legal act or a specific part of a legal act.
5.3.6.4.14. Measure
Measure

Package:

ProductionAndIndustrialFacilitiesExtension

Reference:

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

Definition:

Declared or measured quantity of any kind of physical entity.
5.3.6.4.15. PlanTypeName
PlanTypeName

Package:

NOT FOUND PlanTypeName
5.3.6.4.16. Real
Real

Package:

Numerics

Reference:

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

Package:

Land Use Nomenclature

Reference:

INSPIRE Data specification on Land Use [DS-D2.8.III.4]

Definition:

Presence of one or several land use classification values in an area according to the code list provided by the data provider, indicated either as the percentage covered for each value or as the values listed in their order of importance.

Description:

NOTE 1: The order of land use value presence without percentages enable providing an order of dominance/importance of each land use present in the land use object
NOTE 2: The sum of the percentages can be below 100%, or above. The order is provided according to the respective importance when the percentages are not known.

URI

URI

Package:

basicTypes

Reference:

Geographic information — Geography Markup Language (GML) [ISO 19136:2007]

6. Reference systems, units of measure and grids

6.1. Default reference systems, units of measure and grid

The reference systems, units of measure and geographic grid systems included in this sub-section are the defaults to be used for all INSPIRE data sets, unless theme-specific exceptions and/or additional requirements are defined in section 6.2.

6.1.1. Coordinate reference systems

6.1.1.1. Datum
📕

IR Requirement
Annex II, Section 1.2
Datum for three-dimensional and two-dimensional coordinate reference systems

For the three-dimensional and two-dimensional coordinate reference systems and the horizontal component of compound coordinate reference systems used for making spatial data sets available, the datum shall be the datum of the European Terrestrial Reference System 1989 (ETRS89) in areas within its geographical scope, or the datum of the International Terrestrial Reference System (ITRS) or other geodetic coordinate reference systems compliant with ITRS in areas that are outside the geographical scope of ETRS89. Compliant with the ITRS means that the system definition is based on the definition of the ITRS and there is a well documented relationship between both systems, according to EN ISO 19111.
6.1.1.2. Coordinate reference systems
📕

IR Requirement
Annex II, Section 1.3
Coordinate Reference Systems

Spatial data sets shall be made available using at least one of the coordinate reference systems specified in sections 1.3.1, 1.3.2 and 1.3.3, unless one of the conditions specified in section 1.3.4 holds.

1.3.1. Three-dimensional Coordinate Reference Systems

  • Three-dimensional Cartesian coordinates based on a datum specified in 1.2 and using the parameters of the Geodetic Reference System 1980 (GRS80) ellipsoid.

  • Three-dimensional geodetic coordinates (latitude, longitude and ellipsoidal height) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.

1.3.2. Two-dimensional Coordinate Reference Systems

  • Two-dimensional geodetic coordinates (latitude and longitude) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.

  • Plane coordinates using the ETRS89 Lambert Azimuthal Equal Area coordinate reference system.

  • Plane coordinates using the ETRS89 Lambert Conformal Conic coordinate reference system.

  • Plane coordinates using the ETRS89 Transverse Mercator coordinate reference system.

1.3.3. Compound Coordinate Reference Systems

  1. For the horizontal component of the compound coordinate reference system, one of the coordinate reference systems specified in section 1.3.2 shall be used.

  2. For the vertical component, one of the following coordinate reference systems shall be used:

    • For the vertical component on land, the European Vertical Reference System (EVRS) shall be used to express gravity-related heights within its geographical scope. Other vertical reference systems related to the Earth gravity field shall be used to express gravity-related heights in areas that are outside the geographical scope of EVRS.

    • For the vertical component in the free atmosphere, barometric pressure, converted to height using ISO 2533:1975 International Standard Atmosphere, or other linear or parametric reference systems shall be used. Where other parametric reference systems are used, these shall be described in an accessible reference using EN ISO 19111-2:2012.

    • For the vertical component in marine areas where there is an appreciable tidal range (tidal waters), the Lowest Astronomical Tide (LAT) shall be used as the reference surface.

    • For the vertical component in marine areas without an appreciable tidal range, in open oceans and effectively in waters that are deeper than 200 meters, the Mean Sea Level (MSL) or a well-defined reference level close to the MSL shall be used as the reference surface.

1.3.4. Other Coordinate Reference Systems

Exceptions, where other coordinate reference systems than those listed in 1.3.1, 1.3.2 or 1.3.3 may be used, are:

  1. Other coordinate reference systems may be specified for specific spatial data themes.

  2. For regions outside of continental Europe, Member States may define suitable coordinate reference systems.

The geodetic codes and parameters needed to describe these other coordinate reference systems and to allow conversion and transformation operations shall be documented and an identifier shall be created in a coordinate systems register established and operated by the Commission, according to EN ISO 19111 and ISO 19127.
The Commission shall be assisted by the INSPIRE Commission expert group in the maintenance and update of the coordinate systems register.
6.1.1.3. Display
📕

IR Requirement
Annex II, Section 1.4
Coordinate Reference Systems used in the View Network Service

For the display of spatial data sets with the view network service as specified in Regulation No 976/2009, at least the coordinate reference systems for two-dimensional geodetic coordinates (latitude, longitude) shall be available.
6.1.1.4. Identifiers for coordinate reference systems
📕

IR Requirement
Annex II, Section 1.5
Coordinate Reference System Identifiers

  1. Coordinate reference system parameters and identifiers shall be managed in one or several common registers for coordinate reference systems.

  2. Only identifiers contained in a common register shall be used for referring to the coordinate reference systems listed in this Section.

These Technical Guidelines propose to use the http URIs provided by the Open Geospatial Consortium as coordinate reference system identifiers (see identifiers for the default CRSs in the INSPIRE coordinate reference systems register). These are based on and redirect to the definition in the EPSG Geodetic Parameter Registry (http://www.epsg-registry.org/).

The identifiers listed in the INSPIRE coordinate reference systems register (https://inspire.ec.europa.eu/crs) shall be used for referring to the coordinate reference systems used in a data set.

NOTE CRS identifiers may be used e.g. in:
data encoding,
data set and service metadata, and
requests to INSPIRE network services.

6.1.2. Temporal reference system

📕

IR Requirement
Article 11
Temporal Reference Systems

  1. The default temporal reference system referred to in point 5 of part B of the Annex to Commission Regulation (EC) No 1205/2008 ([16]) shall be used, unless other temporal reference systems are specified for a specific spatial data theme in Annex II.

NOTE 1 Point 5 of part B of the Annex to Commission Regulation (EC) No 1205/2008 (the INSPIRE Metadata IRs) states that the default reference system shall be the Gregorian calendar, with dates expressed in accordance with ISO 8601.

NOTE 2 ISO 8601 Data elements and interchange formats – Information interchange – Representation of dates and times is an international standard covering the exchange of date and time-related data. The purpose of this standard is to provide an unambiguous and well-defined method of representing dates and times, so as to avoid misinterpretation of numeric representations of dates and times, particularly when data is transferred between countries with different conventions for writing numeric dates and times. The standard organizes the data so the largest temporal term (the year) appears first in the data string and progresses to the smallest term (the second). It also provides for a standardized method of communicating time-based information across time zones by attaching an offset to Coordinated Universal Time (UTC).

EXAMPLE 1997 (the year 1997), 1997-07-16 (16th July 1997), 1997-07-16T19:20:3001:00 (16th July 1997, 19h 20' 30'', time zone: UTC1)

6.1.3. Units of measure

📕

IR Requirement
Article 12
Other Requirements & Rules

(…​)

  1. All measurement values shall be expressed using SI units or non-SI units accepted for use with the International System of Units, unless specified otherwise for a specific spatial data theme or type.

6.1.4. Grids

📕

IR Requirement
Annex II, Section 2.2
Grids

Either of the grids with fixed and unambiguously defined locations defined in Sections 2.2.1 and 2.2.2 shall be used as a geo-referencing framework to make gridded data available in INSPIRE, unless one of the following conditions holds:

  1. Other grids may be specified for specific spatial data themes in Annexes II-IV. In this case, data exchanged using such a theme-specific grid shall use standards in which the grid definition is either included with the data, or linked by reference.

  2. For grid referencing in regions outside of continental Europe Member States may define their own grid based on a geodetic coordinate reference system compliant with ITRS and a Lambert Azimuthal Equal Area projection, following the same principles as laid down for the grid specified in Section 2.2.1. In this case, an identifier for the coordinate reference system shall be created.

2.2 Equal Area Grid

The grid is based on the ETRS89 Lambert Azimuthal Equal Area (ETRS89-LAEA) coordinate reference system with the centre of the projection at the point 52o N, 10o E and false easting: x0 = 4321000 m, false northing: y0 = 3210000 m.

The origin of the grid coincides with the false origin of the ETRS89-LAEA coordinate reference system (x=0, y=0).

Grid points of grids based on ETRS89-LAEA shall coincide with grid points of the grid.

The grid is hierarchical, with resolutions of 1m, 10m, 100m, 1000m, 10000m and 100000m.

The grid orientation is south-north, west-east.

The grid is designated as Grid_ETRS89-LAEA. For identification of an individual resolution level the cell size in metres is appended.

For the unambiguous referencing and identification of a grid cell, the cell code composed of the size of the cell and the coordinates of the lower left cell corner in ETRS89-LAEA shall be used. The cell size shall be denoted in metres ("m") for cell sizes up to 100m or kilometres ("km") for cell sizes of 1000m and above. Values for northing and easting shall be divided by 10n, where n is the number of trailing zeros in the cell size value.

6.2. Theme-specific requirements and recommendations

6.2.1. Coordinate reference systems

📕

IR Requirement
Annex IV Section 4.8
Theme specific requirements

Based on the INSPIRE horizontal coordinate reference system, each Member State shall define a projection or a set of projections suitable for working with the underlying cadastral parcels on national territory and cross-border areas where applicable for a SpatialPlan. A projection is suitable if it offers few linear alterations (ideally less than 50 cm per 500 m) and so enables users to measure distances and surfaces in meaningful way. This projection or set of projections has to be defined in agreement with neighbouring countries. This projection or set of projections must be well documented to allow the conversion from and to the common Coordinate Reference System. The documentation shall be provided according to ISO 19111, which states how a projected coordinate reference system must be described.

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 Land Use (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 Land Use (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 Land Use (see sections 7.2 and 7.3).

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

7.1. Data quality elements

Table 6 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 6 – Data quality elements used in the spatial data theme Land Use

Section

Data quality element

Data quality sub-element

Definition

Evaluation Scope

7.1.1

Completeness

Commission

excess data present in the dataset, as described by the scope

dataset

7.1.2

Completeness

Omission

data absent from the dataset, as described by the scope

dataset

7.1.3

Logical consistency

Domain consistency

adherence of values to the value domains

dataset

7.1.4

Positional accuracy

Absolute or external accuracy

closeness of reported coordinate values to values accepted as or being true

dataset

7.1.5

Thematic accuracy

Classification correctness

comparison of the classes assigned to features or their attributes to a universe of discourse

dataset series; dataset; spatial object type; spatial object

7.1.6

Thematic accuracy

Non-quantitative attribute correctness

correctness of non-quantitative attributes

dataset series; dataset; spatial object type; spatial object
📘

Recommendation 10

Where it is impossible to express the evaluation of a data quality element in a quantitative way, the evaluation of the element should be expressed with a textual statement as a data quality descriptive result.

7.1.1. Completeness – Commission

📘

Recommendation 11

Commission should be evaluated and documented using rate of excess as specified in the table below.

Name

Rate of excess

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

This data quality element is not applicable to SLU or GLU.

For ELU and PLU, the land use features (ExistingLandUseObject and ZoningElement)are mutually exclusive, therefore possible existence of polygons' excess can be managed by topological principles.

This data quality element applies only for SupplementaryRegulation in PLU

Evaluation scope

Data set

Reporting scope

Data set

Parameter

-

Data quality value type

Real

Data quality value structure

Single value

Source reference

ISO/DIS 19157 Geographic information – Data quality

Example

Value 1,89 (measured or estimated value) means that 1,89 % of all features in SupplementaryRegulation element are excess items.

Measure identifier

3 (ISO 19157)

7.1.2. Completeness – Omission

📘

Recommendation 12

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

Name

Rate of missing items

Alternative name

-

Data quality element

Completeness

Data quality 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

All land use features in schemas (ELU, PLU, SLU, GLU) should have at least one land use type defined as HILUCS value.

Rate of missing items shows the known or estimated rate of the missing HILUCS values in relation to all land use features in a schema.

Evaluation scope

Data set

Reporting scope

Data set

Parameter

-

Data quality value type

Real

Data quality value structure

Single value

Source reference

ISO/DIS 19157 Geographic information – Data quality

Example

Rate of missing items is set to 1.89 for ELU meaning that 1.89 % of all polygons are missing the HILUCS value.

Rate of missing items for GLU dataset is set to 5 meaning 5 % of pixels are classified as "nodata".

Rate of missing items values 0 % are not reported (data is complete).

Measure identifier

5 (ISO 19157)

Name

Missing item

Alternative name

-

Data quality element

Completeness

Data quality sub-element

Omission

Data quality basic measure

Error indicator

Definition

Indicator that shows that a specific item is missing in the data.

Description

Indicator shall have value "true" when a certain land use type (HILUCS class) is missing in the dataset (data not collected) but that specific land use type exists (in real world) in the area the dataset covers and the data producer knows / recognizes that existence.

Indicator shall have value "false" when a certain land use type is missing in the dataset and that land use type does not exist in the real world either.

Evaluation scope

Data set

Reporting scope

Data set

Parameter

-

Data quality value type

Boolean (true indicates that an item is missing, false indicates that an item is missing in data and also in the real world)

Data quality value structure

Single value

Source reference

ISO/DIS 19157 Geographic information – Data quality

Example

HILUCS class 3 "Services" does not exist in the dataset. When the data producer knows that this class occurs in the area the dataset covers he sets the missing item value for this class "true". That indication covers also the sub-classes (3.1, 3.1.1. etc).

HILUCS class 1.2 "Forestry use" data exists in the dataset but the sub-classes 1.2.1, 1.2.2 and 1.2.3 do not. Data producer knows that classes 1.2.2 and 1.2.3 exist in the area but 1.2.1 does not. Missing item will have value "true" for HILUCS classes 1.2.2 and 1.2.3 and a value "false" to 1.2.1.

HILUCS class 1.2 "Forestry use" data exists in the dataset but sub-classes 1.2.1, 1.2.2 and 1.2.3 do not. Data producer does not know whether there exist sub-classes 1.2.1 - 1.2.3 in the area or not. Values for missing items are not set.

Measure identifier

7 (ISO 19157)

7.1.3. Logical consistency – Domain consistency

The Application Schema conformance class of the Abstract Test Suite in Annex A defines a number of tests to evaluate the domain consistency (tests A1.10-A.1.12) of a data set.

📘

Recommendation 13

For the tests on domain consistency, it is recommended to use the Logical consistency – Domain consistency data quality sub-element and the measure Number of items not in conformance with their value domain as specified in the table below.

Name

Number of items not in conformance with their value domain

Alternative name

-

Data quality element

logical consistency

Data quality sub-element

domain consistency

Data quality basic measure

error count

Definition

count of all items in the dataset that are not in conformance with their value domain

Description

Evaluation scope

spatial object / spatial object type

Reporting scope

data set

Parameter

-

Data quality value type

integer

7.1.4. Positional accuracy – Absolute or external accuracy

📘

Recommendation 14

Absolute or external accuracy should be evaluated and documented using mean value of positional uncertainties (2D) as specified in the table below.

Name

Mean value of positional uncertainties (2D)

Alternative name

-

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

Element is valid only for land use schemas ELU and PLU. Measurement unit is meters.

For ELU a estimation of positional error in sampled points can be evaluated:

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

image

The mean positional uncertainties of the horizontal absolute or external positions is then calculated as

image

A criterion for the establishing of correspondence should also be stated (e.g. allowing for correspondence to the closest position, correspondence on vertices or along lines, etc.). The criterion/criteria for finding the corresponding points shall be reported with the data quality evaluation result.

NOTE This data quality measure is different than the standard deviation.

For PLU (polygons) the positional accuracy is portrayed as an estimated value based to the scale of the data as follows:

Scale, 1:n Estimated geometric accuracy; normal data quality

1 000 000

500 m

500 000

250 m

250 000

125 m

100 000

50 m

50 000

25 m

20 000

10 m

10 000

5 m

5 000

2,5 m

2 000

1 m

1 000

0,5 m

Evaluation scope

Data set

Reporting scope

Data set

Parameter

-

Data quality value type

Measure or real

Data quality value structure

-

Source reference

ISO/DIS 19157 Geographic information – Data quality

Example

Value 30.5 for ELU dataset means that the mean positional uncertainty of a land use type (position of the outer limit) is ± 30.5 meters compared to the true position.

Value 50 for PLU dataset means that dataset’s estimated positional accuracy corresponds to the 1:100 000 scale.

Measure identifier

28 (ISO 19157)

7.1.5. Thematic accuracy – Classification correctness

📘

Recommendation 15

Classification correctness should be evaluated and documented using 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

Number of incorrectly classified features relative to the number of features that should be there.

Description

Land Use type classes in dataset in relation to the land use types in the real world.

This element is used only for existing land use: ELU, SLU, GLU.

Evaluation scope

Data set

Reporting scope

Data set

Parameter

-

Data quality value type

Real

Data quality value structure

Source reference

ISO/DIS 19157 Geographic information – Data quality

Example

Value 1.89 indicates that 1.89 % of all features in a dataset (polygons, points or pixels) have different land use type than the corresponding feature in a real world.

Measure identifier

61 (ISO 19157)

7.1.6. Thematic accuracy – Non-quantitative attribute correctness

📘

Recommendation 16

Non-quantitative attribute correctness should be evaluated and documented using rate of incorrect attribute values as specified in the table below.

Name

Rate of incorrect attribute values

Alternative name

-

Data quality element

Thematic accuracy

Data quality sub-element

Non-quantitative attribute correctness

Data quality basic measure

Error rate

Definition

Number of attribute values where incorrect values are assigned in relation to the total number of attribute values.

Description

This element is used only for planned land use: PLU (Zoning Element and SupplementaryRegulation) features and is used to non-quantitative attributes like Inspire-id, RegulationNature, ProcessStepGeneral and SupplementaryRegulationValue.

Evaluation scope

Data set

Reporting scope

Data set

Parameter

-

Data quality value type

Real ; percentage

Data quality value structure

Source reference

ISO/DIS 19157 Geographic information – Data quality

Example

Value 1.89 means that 1.89 % of all non-quantitative attributes have incorrect value.

Measure identifier

67 (ISO 19157)

7.2. Minimum data quality requirements

No minimum data quality requirements are defined for the spatial data theme Land Use.

7.3. Recommendation on data quality

📘

Recommendation 17
For the data quality elements listed in Table 7, all data sets related to the spatial data theme Land Use should meet the specified target results.

Table 7 – Recommended minimum data quality results for spatial data theme Land Use

Section

Data quality element and sub-element

Measure name(s)

Target result(s)

Condition

7.1.1

Completeness - Commission

Error rate

0 %

7.1.2

Completeness - Omission

Rate of missing items

0 %

7.1.3

Logical consistency - Domain consistency

Correct items rate

Min 95 %

7.1.4

Positional accuracy - Absolute or external accuracy

Estimation of positional error

Corresponding normal data quality (table above)

7.1.5

Thematic accuracy - classification correctness

Error rate

Max 5 %

8. Dataset-level metadata

This section specifies dataset-level metadata elements, which should be used for documenting metadata for a complete dataset or dataset series.

NOTE Metadata can also be reported for each individual spatial object (spatial object-level metadata). Spatial object-level metadata is fully described in the application schema(s) (section 5).

For some dataset-level metadata elements, in particular those for reporting data quality and maintenance, a more specific scope can be specified. This allows the definition of metadata at sub-dataset level, e.g. separately for each spatial object type (see instructions for the relevant metadata element).

8.1. Metadata elements defined in INSPIRE Metadata Regulation

Table 8 gives an overview of the metadata elements specified in Regulation 1205/2008/EC (implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata).

The table contains the following information:

  • The first column provides a reference to the relevant section in the Metadata Regulation, which contains a more detailed description.

  • The second column specifies the name of the metadata element.

  • The third column specifies the multiplicity.

  • The fourth column specifies the condition, under which the given element becomes mandatory.

Table 8 – Metadata for spatial datasets and spatial dataset series specified in Regulation 1205/2008/EC

Metadata Regulation Section

Metadata element

Multiplicity

Condition

1.1

Resource title

1

1.2

Resource abstract

1

1.3

Resource type

1

1.4

Resource locator

0..*

Mandatory if a URL is available to obtain more information on the resource, and/or access related services.

1.5

Unique resource identifier

1..*

1.7

Resource language

0..*

Mandatory if the resource includes textual information.

2.1

Topic category

1..*

3

Keyword

1..*

4.1

Geographic bounding box

1..*

5

Temporal reference

1..*

6.1

Lineage

1

6.2

Spatial resolution

0..*

Mandatory for data sets and data set series if an equivalent scale or a resolution distance can be specified.

7

Conformity

1..*

8.1

Conditions for access and use

1..*

8.2

Limitations on public access

1..*

9

Responsible organisation

1..*

10.1

Metadata point of contact

1..*

10.2

Metadata date

1

10.3

Metadata language

1

Generic guidelines for implementing these elements using ISO 19115 and 19119 are available at http://inspire.jrc.ec.europa.eu/index.cfm/pageid/101. The following sections describe additional theme-specific recommendations and requirements for implementing these elements.

8.1.1. Conformity

The Conformity metadata element defined in Regulation 1205/2008/EC requires to report the conformance with the Implementing Rule for interoperability of spatial data sets and services. In addition, it may be used also to document the conformance to another specification.

📘

Recommendation 18

Dataset metadata should include a statement on the overall conformance of the dataset with this data specification (i.e. conformance with all requirements).
📘

Recommendation 19

The Conformity metadata element should be used to document conformance with this data specification (as a whole), with a specific conformance class defined in the Abstract Test Suite in Annex A and/or with another specification.

The Conformity element includes two sub-elements, the Specification (a citation of the Implementing Rule for interoperability of spatial data sets and services or other specification), and the Degree of conformity. The Degree can be Conformant (if the dataset is fully conformant with the cited specification), Not Conformant (if the dataset does not conform to the cited specification) or Not Evaluated (if the conformance has not been evaluated).

📘

Recommendation 20

If a dataset is not yet conformant with all requirements of this data specification, it is recommended to include information on the conformance with the individual conformance classes specified in the Abstract Test Suite in Annex A.
📘

Recommendation 21
If a dataset is produced or transformed according to an external specification that includes specific quality assurance procedures, the conformity with this specification should be documented using the Conformity metadata element.
📘

Recommendation 22
If minimum data quality recommendations are defined then the statement on the conformity with these requirements should be included using the Conformity metadata element and referring to the relevant data quality conformance class in the Abstract Test Suite.

NOTE Currently no minimum data quality requirements are included in the IRs. The recommendation above should be included as a requirement in the IRs if minimum data quality requirements are defined at some point in the future.

📘

Recommendation 23
When documenting conformance with this data specification or one of the conformance classes defined in the Abstract Test Suite, the Specification sub-element should be given using the http URI identifier of the conformance class or using a citation including the following elements:

  • title: "INSPIRE Data Specification on Land Use – Technical Guidelines – <name of the conformance class>"

  • date:

    • dateType: publication

    • date: 2013-04-10

EXAMPLE 1: The XML snippets below show how to fill the Specification sub-element for documenting conformance with the whole data specification on Addresses v3.0.1.

<gmd:DQ_ConformanceResult>
	<gmd:specification href="http://inspire.ec.europa.eu/conformanceClass/ad/3.0.1/tg" />
	<gmd:explanation> (...) </gmd:explanation>
	<gmd:pass> (...) </gmd:pass>
</gmd:DQ_ConformanceResult>

or (using a citation):

<gmd:DQ_ConformanceResult>
	<gmd:specification>
		<gmd:CI_Citation>
			<gmd:title>
				<gco:CharacterString>INSPIRE Data Specification on Land Use – Technical Guidelines</gco:CharacterString>
			</gmd:title>
			<gmd:date>
				<gmd:date>
					<gco:Date>2013-04-10</gco:Date>
				</gmd:date>
				<gmd:dateType>
					<gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resou
rces/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
				</gmd:dateType>
			</gmd:date>
		</gmd:CI_Citation>
	</gmd:specification>
	<gmd:explanation> (...) </gmd:explanation>
	<gmd:pass> (...) </gmd:pass>
</gmd:DQ_ConformanceResult>

EXAMPLE 2: The XML snippets below show how to fill the Specification sub-element for documenting conformance with the CRS conformance class of the data specification on Addresses v3.0.1.

<gmd:DQ_ConformanceResult>
	<gmd:specification href="http://inspire.ec.europa.eu/conformanceClass/ad/3.0.1/crs" />
	<gmd:explanation> (...) </gmd:explanation>
	<gmd:pass> (...) </gmd:pass>
</gmd:DQ_ConformanceResult>

or (using a citation):

<gmd:DQ_ConformanceResult>
	<gmd:specification>
		<gmd:CI_Citation>
			<gmd:title>
				<gco:CharacterString>INSPIRE Data Specification on Land Use – Technical Guidelines – CRS</gco:CharacterString>
			</gmd:title>
			<gmd:date>
				<gmd:date>
					<gco:Date>2013-04-10</gco:Date>
				</gmd:date>
				<gmd:dateType>
					<gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resou
rces/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
				</gmd:dateType>
			</gmd:date>
		</gmd:CI_Citation>
	</gmd:specification>
	<gmd:explanation> (...) </gmd:explanation>
	<gmd:pass> (...) </gmd:pass>
</gmd:DQ_ConformanceResult>

8.1.2. Lineage

📘

Recommendation 24

Following the ISO/DIS 19157 Quality principles, if a data provider has a procedure for the quality management of their spatial data sets then the appropriate data quality elements and measures defined in ISO/DIS 19157 should be used to evaluate and report (in the metadata) the results. If not, the Lineage metadata element (defined in Regulation 1205/2008/EC) should be used to describe the overall quality of a spatial data set.

According to Regulation 1205/2008/EC, lineage "is a statement on process history and/or overall quality of the spatial data set. Where appropriate it may include a statement whether the data set has been validated or quality assured, whether it is the official version (if multiple versions exist), and whether it has legal validity. The value domain of this metadata element is free text".

The Metadata Technical Guidelines based on EN ISO 19115 and EN ISO 19119 specifies that the statement sub-element of LI_Lineage (EN ISO 19115) should be used to implement the lineage metadata element.

📘

Recommendation 25

To describe the transformation steps and related source data, it is recommended to use the following sub-elements of LI_Lineage:

  • For the description of the transformation process of the local to the common INSPIRE data structures, the LI_ProcessStep sub-element should be used.

  • For the description of the source data the LI_Source sub-element should be used.

NOTE 1 In order to improve the interoperability, domain templates and instructions for using these free text elements (descriptive statements) may be specified here and/or in an Annex of this data specification.

8.1.3. Temporal reference

According to Regulation 1205/2008/EC, at least one of the following temporal reference metadata sub-elements shall be provided: temporal extent, date of publication, date of last revision, date of creation.

📘

Recommendation 26

It is recommended that at least the date of the last revision of a spatial data set should be reported using the Date of last revision metadata sub-element.

8.1.4. Keywords

Keywords are used to classify resource to facilitate effective discovery and thematic discovery. The keyword value is a commonly used word, formalised word or phrase used to describe the subject and thus help narrowing a full text search and they allow for structured keyword search.

📕

IR Requirement
Annex IV Section 4.8
Theme specific requirements

Data providers shall include the following keywords in addition to the mandatory keywords defined in Regulation (EC) No 1205/2008/EC:

  1. One of the following language-neutral keywords to describe the type of land use data set: ExistingLandUse, SampledExistingLandUse, GriddedExistingLandUse, PlannedLandUse.

  2. If the data set contains SpatialPlan objects, one keyword describing the level of the administrative units covered by the plan, as defined in the LevelOfSpatialPlan code list.

8.1.5. Spatial Resolution

Guidelines may provide further information on how to use common metadata

elements or how to restrict the use of common metadata elements according

to the metadata regulation.

📕

IR Requirement
Annex IV Section 4.8
Theme specific requirements

The use of the common metadata element "Spatial Resolution" (according to Section 6.2 of part B of the Annex to Regulation (EC) No 1205/2008) shall be restricted to providing a resolution distance.

NOTE The "minimum unit of interest" concept directly indicated the size of the smallest polygonal area for Land Use types to be found in the dataset. That information is transferred to the user via the "spatial resolution" MD-element and may be dependent on HILUCS categories.

8.2. Metadata elements for interoperability

📕

IR Requirement
Article 13
Metadata required for Interoperability

The metadata describing a spatial data set shall include the following metadata elements required for interoperability:

  1. Coordinate Reference System: Description of the coordinate reference system(s) used in the data set.

  2. Temporal Reference System: Description of the temporal reference system(s) used in the data set.

    This element is mandatory only if the spatial data set contains temporal information that does not refer to the default temporal reference system.

  3. Encoding: Description of the computer language construct(s) specifying the representation of data objects in a record, file, message, storage device or transmission channel.

  4. Topological Consistency: Correctness of the explicitly encoded topological characteristics of the data set as described by the scope.

    This element is mandatory only if the data set includes types from the Generic Network Model and does not assure centreline topology (connectivity of centrelines) for the network.

  5. Character Encoding: The character encoding used in the data set.

    This element is mandatory only if an encoding is used that is not based on UTF-8.

  6. Spatial Representation Type: The method used to spatially represent geographic information.

These Technical Guidelines propose to implement the required metadata elements based on ISO 19115 and ISO/TS 19139.

The following TG requirements need to be met in order to be conformant with the proposed encoding.

📒

TG Requirement 2
Metadata instance (XML) documents shall validate without error against the used ISO 19139 XML schema.

NOTE Section 2.1.2 of the Metadata Technical Guidelines discusses the different ISO 19139 XML schemas that are currently available.

📒

TG Requirement 3
Metadata instance (XML) documents shall contain the elements and meet the INSPIRE multiplicity specified in the sections below.
📒

TG Requirement 4
The elements specified below shall be available in the specified ISO/TS 19139 path.
📘

Recommendation 27

The metadata elements for interoperability should be made available together with the metadata elements defined in the Metadata Regulation through an INSPIRE discovery service.

NOTE While this not explicitly required by any of the INSPIRE Implementing Rules, making all metadata of a data set available together and through one service simplifies implementation and usability.

8.2.1. Coordinate Reference System

Metadata element name Coordinate Reference System

Definition

Description of the coordinate reference system used in the dataset.

ISO 19115 number and name

13. referenceSystemInfo

ISO/TS 19139 path

referenceSystemInfo

INSPIRE obligation / condition

mandatory

INSPIRE multiplicity

1..*

Data type(and ISO 19115 no.)

186. MD_ReferenceSystem

Domain

To identify the reference system, the referenceSystemIdentifier (RS_Identifier) shall be provided.

NOTE More specific instructions, in particular on pre-defined values for filling the referenceSystemIdentifier attribute should be agreed among Member States during the implementation phase to support interoperability.

Implementing instructions

Example

referenceSystemIdentifier:

code: ETRS_89

codeSpace: INSPIRE RS registry

Example XML encoding

 
<gmd:referenceSystemInfo>
		<gmd:MD_ReferenceSystem>
			<gmd:referenceSystemIdentifier>
				<gmd:RS_Identifier>
					<gmd:code>
						<gco:CharacterString>ETRS89 </gco:CharacterString>
					</gmd:code>
					<gmd:codeSpace>
						<gco:CharacterString>INSPIRE RS registry</gco:CharacterString>
					</gmd:codeSpace>
				</gmd:RS_Identifier>
			</gmd:referenceSystemIdentifier>
		</gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>

Comments

8.2.2. Temporal Reference System

Metadata element name Temporal Reference System

Definition

Description of the temporal reference systems used in the dataset.

ISO 19115 number and name

13. referenceSystemInfo

ISO/TS 19139 path

referenceSystemInfo

INSPIRE obligation / condition

Mandatory, if the spatial data set or one of its feature types contains temporal information that does not refer to the Gregorian Calendar or the Coordinated Universal Time.

INSPIRE multiplicity

0..*

Data type(and ISO 19115 no.)

186. MD_ReferenceSystem

Domain

No specific type is defined in ISO 19115 for temporal reference systems. Thus, the generic MD_ReferenceSystem element and its reference SystemIdentifier (RS_Identifier) property shall be provided.

NOTE More specific instructions, in particular on pre-defined values for filling the referenceSystemIdentifier attribute should be agreed among Member States during the implementation phase to support interoperability.

Implementing instructions

Example

referenceSystemIdentifier:
code: GregorianCalendar
codeSpace: INSPIRE RS registry

Example XML encoding

 
<gmd:referenceSystemInfo>
	<gmd:MD_ReferenceSystem>
		<gmd:referenceSystemIdentifier>
			<gmd:RS_Identifier>
				<gmd:code>
			<gco:CharacterString>GregorianCalendar </gco:CharacterString>
				</gmd:code>
				<gmd:codeSpace>
					<gco:CharacterString>INSPIRE RS registry</gco:CharacterString>
				</gmd:codeSpace>
			</gmd:RS_Identifier>
		</gmd:referenceSystemIdentifier>
	</gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>

Comments

8.2.3. Encoding

Metadata element name Encoding

Definition

Description of the computer language construct that specifies the representation of data objects in a record, file, message, storage device or transmission channel

ISO 19115 number and name

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

Domain

See B.2.10.4. The property values (name, version, specification) specified in section 5 shall be used to document the default and alternative encodings.

Implementing instructions

Example

name: <Application schema name> GML application schema

version: 4.0

specification: D2.8.III.4 Data Specification on Land Use – Technical Guidelines

Example XML encoding

 
<gmd:MD_Format>
	<gmd:name>
		<gco:CharacterString>SomeApplicationSchema GML application schema</gco:CharacterString>
	</gmd:name>
	<gmd:version>
		<gco:CharacterString>4.0</gco:CharacterString>
	</gmd:version>
	<gmd:specification>
		<gco:CharacterString>D2.8.III.4 Data Specification on Land Use – Technical Guidelines</gco:CharacterString>
	</gmd:specification>
</gmd:MD_Format>

Comments

8.2.4. Character Encoding

Metadata element name Character Encoding

Definition

The character encoding used in the data set.

ISO 19115 number and name

ISO/TS 19139 path

INSPIRE obligation / condition

Mandatory, if an encoding is used that is not based on UTF-8.

INSPIRE multiplicity

0..*

Data type (and ISO 19115 no.)

Domain

Implementing instructions

Example

-

Example XML encoding

 
<gmd:characterSet>
	<gmd:MD_CharacterSetCode codeListValue="8859part2" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CharacterSetCode">8859-2</gmd:MD_CharacterSetCode>
</gmd:characterSet>

Comments

8.2.5. Spatial representation type

Metadata element name Spatial representation type

Definition

The method used to spatially represent geographic information.

ISO 19115 number and name

37. spatialRepresentationType

ISO/TS 19139 path

INSPIRE obligation / condition

Mandatory

INSPIRE multiplicity

1..*

Data type (and ISO 19115 no.)

B.5.26 MD_SpatialRepresentationTypeCode

Domain

Implementing instructions

Of the values included in the code list in ISO 19115 (vector, grid, textTable, tin, stereoModel, video), only vector, grid and tin should be used.

NOTE Additional code list values may be defined based on feedback from implementation.

Example

-

Example XML encoding

Comments

8.2.6. Data Quality – Logical Consistency – Topological Consistency

See section 8.3.2 for instructions on how to implement metadata elements for reporting data quality.

8.3. Recommended theme-specific metadata elements

📘

Recommendation 28

The metadata describing a spatial data set or a spatial data set series related to the theme Land Use should comprise the theme-specific metadata elements specified in Table 9.

The table contains the following information:

  • The first column provides a reference to a more detailed description.

  • The second column specifies the name of the metadata element.

  • The third column specifies the multiplicity.

Table 9 – Optional theme-specific metadata elements for the theme Land Use

Section

Metadata element

Multiplicity

8.3.1

Maintenance Information

0..1

8.3.2

Logical Consistency – Conceptual Consistency

0..*

8.3.2

Logical Consistency – Domain Consistency

0..*

8.3.2

Other DQ elements from chapter 7

0..*
📘

Recommendation 29

For implementing the metadata elements included in this section using ISO 19115, ISO/DIS 19157 and ISO/TS 19139, the instructions included in the relevant sub-sections should be followed.

8.3.1. Maintenance Information

Metadata element name Maintenance information

Definition

Information about the scope and frequency of updating

ISO 19115 number and name

  1. resourceMaintenance

ISO/TS 19139 path

identificationInfo/MD_Identification/resourceMaintenance

INSPIRE obligation / condition

optional

INSPIRE multiplicity

0..1

Data type(and ISO 19115 no.)

  1. MD_MaintenanceInformation

Domain

This is a complex type (lines 143-148 from ISO 19115).

At least the following elements should be used (the multiplicity according to ISO 19115 is shown in parentheses):

  • maintenanceAndUpdateFrequency [1]: frequency with which changes and additions are made to the resource after the initial resource is completed / domain value: MD_MaintenanceFrequencyCode:

  • updateScope [0..*]: scope of data to which maintenance is applied / domain value: MD_ScopeCode

  • maintenanceNote [0..*]: information regarding specific requirements for maintaining the resource / domain value: free text

Implementing instructions

Example

Example XML encoding

Comments

8.3.2. Metadata elements for reporting data quality

📘

Recommendation 30

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

Recommendation 31

The metadata elements specified in the following sections should be used to report the results of the data quality evaluation. At least the information included in the row "Implementation instructions" should be provided.

The first section applies to reporting quantitative results (using the element DQ_QuantitativeResult), while the second section applies to reporting non-quantitative results (using the element DQ_DescriptiveResult).

📘

Recommendation 32

If a dataset does not pass the tests of the Application schema conformance class (defined in Annex A), the results of each test should be reported using one of the options described in sections 8.3.2.1 and 8.3.2.2.

NOTE 1 If using non-quantitative description, the results of several tests do not have to be reported separately, but may be combined into one descriptive statement.

NOTE 2 The sections 8.3.2.1 and 8.3.2.2 may need to be updated once the XML schemas for ISO 19157 have been finalised.

The scope for reporting may be different from the scope for evaluating data quality (see section 7). If data quality is reported at the data set or spatial object type level, the results are usually derived or aggregated.

📘

Recommendation 33

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

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

If the level is featureType the levelDescription/MDScopeDescription/features element (of type Set< GF_FeatureType>) shall be used to list the feature type names.

NOTE In the level element of DQ_Scope, the value featureType is used to denote spatial object type.

8.3.2.1. Guidelines for reporting quantitative results of the data quality evaluation
Metadata element name See chapter 7

Definition

See chapter 7

ISO/DIS 19157 number and name

3. report

ISO/TS 19139 path

dataQualityInfo/*/report

INSPIRE obligation / condition

optional

INSPIRE multiplicity

0..*

Data type (and ISO/DIS 19157 no.)

Corresponding DQ_xxx subelement from ISO/DIS 19157, e.g. 12. DQ_CompletenessCommission

Domain

Lines 7-9 from ISO/DIS 19157

  1. DQ_MeasureReference (C.2.1.3)

  2. DQ_EvaluationMethod (C.2.1.4.)

  3. DQ_Result (C2.1.5.)

Implementing instructions

  1. nameOfMeasure

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

  1. evaluationMethodType

  2. evaluationMethodDescription

NOTE If the reported data quality results are derived or aggregated (i.e. the scope levels for evaluation and reporting are different), the derivation or aggregation should also be specified using this property.

  1. dateTime

NOTE This should be data or range of dates on which the data quality measure was applied.

  1. DQ_QuantitativeResult / 64. value

NOTE The DQ_Result type should be DQ_QuantitativeResult and the value(s) represent(s) the application of the data quality measure (39.) using the specified evaluation method (42-43.)

Example

See Table E.12 — Reporting commission as metadata (ISO/DIS 19157)

Example XML encoding
8.3.2.2. Guidelines for reporting descriptive results of the Data Quality evaluation
Metadata element name See chapter 7

Definition

See chapter 7

ISO/DIS 19157 number and name

3. report

ISO/TS 19139 path

dataQualityInfo/*/report

INSPIRE obligation / condition

optional

INSPIRE multiplicity

0..*

Data type (and ISO/DIS 19157 no.)

Corresponding DQ_xxx subelement from ISO/DIS 19157, e.g. 12. DQ_CompletenessCommission

Domain

Line 9 from ISO/DIS 19157

  1. DQ_Result (C2.1.5.)

Implementing instructions

  1. DQ_DescripitveResult / 68. statement

NOTE The DQ_Result type should be DQ_DescriptiveResult and in the statement (68.) the evaluation of the selected DQ sub-element should be expressed in a narrative way.

Example

See Table E.15 — Reporting descriptive result as metadata (ISO/DIS 19157)

Example XML encoding

9. Delivery

9.1. Updates

📕

IR Requirement
Article 8
Updates

  1. Member States shall make available updates of data on a regular basis.

  2. All updates shall be made available at the latest 6 months after the change was applied in the source data set, unless a different period is specified for a specific spatial data theme in Annex II.

NOTE In this data specification, no exception is specified, so all updates shall be made available at the latest 6 months after the change was applied in the source data set.

9.2. Delivery medium

According to Article 11(1) of the INSPIRE Directive, Member States shall establish and operate a network of services for INSPIRE spatial data sets and services. The relevant network service types for making spatial data available are:

  • view services making it possible, as a minimum, to display, navigate, zoom in/out, pan, or overlay viewable spatial data sets and to display legend information and any relevant content of metadata;

  • download services, enabling copies of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly;

  • transformation services, enabling spatial data sets to be transformed with a view to achieving interoperability.

NOTE For the relevant requirements and recommendations for network services, see the relevant Implementing Rules and Technical Guidelines[17].

EXAMPLE 1 Through the Get Spatial Objects function, a download service can either download a pre-defined data set or pre-defined part of a data set (non-direct access download service), or give direct access to the spatial objects contained in the data set, and download selections of spatial objects based upon a query (direct access download service). To execute such a request, some of the following information might be required:

  • the list of spatial object types and/or predefined data sets that are offered by the download service (to be provided through the Get Download Service Metadata operation),

  • and the query capabilities section advertising the types of predicates that may be used to form a query expression (to be provided through the Get Download Service Metadata operation, where applicable),

  • a description of spatial object types offered by a download service instance (to be provided through the Describe Spatial Object Types operation).

EXAMPLE 2 Through the Transform function, a transformation service carries out data content transformations from native data forms to the INSPIRE-compliant form and vice versa. If this operation is directly called by an application to transform source data (e.g. obtained through a download service) that is not yet conformant with this data specification, the following parameters are required:

Input data (mandatory). The data set to be transformed.

  • Source model (mandatory, if cannot be determined from the input data). The model in which the input data is provided.

  • Target model (mandatory). The model in which the results are expected.

  • Model mapping (mandatory, unless a default exists). Detailed description of how the transformation is to be carried out.

9.3. Encodings

The IRs contain the following two requirements for the encoding to be used to make data available.

📕

IR Requirement
Article 7
Encoding

1. Every encoding rule used to encode spatial data shall conform to EN ISO 19118. In particular, it shall specify schema conversion rules for all spatial object types and all attributes and association roles and the output data structure used.

2. Every encoding rule used to encode spatial data shall be made available.

2a. Every encoding rule used to encode spatial data shall also specify whether and how to represent attributes and association roles for which a corresponding value exists but is not contained in the spatial data sets maintained by a Member State, or cannot be derived from existing values at reasonable costs.

NOTE ISO 19118:2011 specifies the requirements for defining encoding rules used for interchange of geographic data within the set of International Standards known as the "ISO 19100 series". An encoding rule allows geographic information defined by application schemas and standardized schemas to be coded into a system-independent data structure suitable for transport and storage. The encoding rule specifies the types of data being coded and the syntax, structure and coding schemes used in the resulting data structure. Specifically, ISO 19118:2011 includes

  • requirements for creating encoding rules based on UML schemas,

  • requirements for creating encoding services, and

  • requirements for XML-based encoding rules for neutral interchange of data.

While the IRs do not oblige the usage of a specific encoding, these Technical Guidelines propose to make data related to the spatial data theme Land Use available at least in the default encoding(s) specified in section 0. In this section, a number of TG requirements are listed that need to be met in order to be conformant with the default encoding(s).

The proposed default encoding(s) meet the requirements in Article 7 of the IRs, i.e. they are conformant with ISO 19118 and (since they are included in this specification) publicly available.

9.3.1. Default Encoding(s)

9.3.1.1. Specific requirements for GML encoding

This data specification proposes the use of GML as the default encoding, as recommended in sections 7.2 and 7.3 of [DS-D2.7]. GML is an XML encoding in compliance with ISO 19118, as required in Article 7(1). For details, see [ISO 19136], and in particular Annex E (UML-to-GML application schema encoding rules).

The following TG requirements need to be met in order to be conformant with GML encodings.

📒

TG Requirement 5
Data instance (XML) documents shall validate without error against the provided XML schema.

NOTE 1 Not all constraints defined in the application schemas can be mapped to XML. Therefore, the following requirement is necessary.

NOTE 2 The obligation to use only the allowed code list values specified for attributes and most of the constraints defined in the application schemas cannot be mapped to the XML sch. They can therefore not be enforced through schema validation. It may be possible to express some of these constraints using other schema or rule languages (e.g. Schematron), in order to enable automatic validation.

9.3.1.2. Default encoding(s) for application schema Land Use

Name: Existing Land Use GML Application Schema
Version: 4.0
Specification: D2.8.III.4 Data Specification on Land Use – Technical Guidelines
Character set: UTF-8
The xml schema document is available from http://inspire.ec.europa.eu/schemas/elu/4.0/ExistingLandUse.xsd.

Name: Gridded Land Use GML Application Schema
Version: 4.0
Specification: D2.8.III.4 Data Specification on Land Use – Technical Guidelines
Character set: UTF-8
The xml schema document is available from https://inspire.ec.europa.eu/schemas/gelu/4.0/GriddedExistingLandUse.xsd.

Name: Sampled Land Use Application Schema

Version: 4.0
Specification: D2.8.III.4 Data Specification on Land Use – Technical Guidelines
Character set: UTF-8
The xml schema document is available from https://inspire.ec.europa.eu/schemas/selu/4.0/SampledExistingLandUse.xsd

Name: Planned Land Use GML Application Schema

Version: 4.0
Specification: D2.8.III.4 Data Specification on Land Use – Technical Guidelines
Character set: UTF-8
The xml schema document is available from https://inspire.ec.europa.eu/schemas/plu/4.0/PlannedLandUse.xsd.

Open issue 1: Encoding of Gridded Land Use should be harmonized with the Land cover theme.

9.4. Options for delivering coverage data

For coverages, different encodings may be used for the domain and the range of the coverage. There are several options for packaging the domain and range encoding when delivering coverage data through a download service, as discussed below[18].].

Multipart representation

For performance reasons, binary file formats are usually preferred to text-based formats such as XML for storing large amounts of coverage data. However, they cannot directly constitute an alternative to pure GML, since their own data structure might often not support all the ISO 19123 elements used to describe coverages in the conceptual model.

The OGC standard GML Application Schema for coverages [OGC 09-146r2] offers a format encoding which combines these two approaches. The first part consists of a GML document representing all coverage components except the range set, which is contained in the second part in some other encoding format such as 'well known' binary formats'. Some information in the second part may be redundant with the GML content of the first part. In this case, consistency must be necessarily ensured, for example by defining a GML mapping of the additional encoding format.

The advantage of this multipart representation is that coverage constituents are not handled individually but as a whole. This is not really the case with GML which also allows the encoding of the value side of the coverage in external binary files, but via references to remote locations.

📒

TG Requirement 6
Coverage data encoded as multipart messages shall comply with the multipart representation conformance class defined in GML Application Schema for Coverages [OGC 09-146r2].

NOTE The GML Application Schema for Coverages establishes a one-to-one relationship between coverages and multipart document instances.

Reference to an external file

The range set can be encoded within the XML structure as an external binary file using the gml:File element. This has the benefit of efficiently storing the range set data within an external file that is of a well-known format type, for example TIFF or GeoTIFF. This method of encoding is of most use for the storage of large files.

Encoding the range inline

This option encodes the range set data within the XML inline. This is encoded as a DataBlock element. This encoding provides much greater visibility for the range set values, however, this comes at the cost of reduced efficiency. This method of encoding would therefore only be suitable for small datasets.

Encoding the domain inside a JPEG 2000 file

This option consists in packaging all the components of one or several coverages, including the domain expressed in GML, in a single JPEG 2000 file. It is based on the OGC standard GML in JPEG 2000 for Geographic Imagery [OGC 05-047r2], also known as GMLJP2, which specifies how to use GML within the XML boxes of JPEG 2000 files.

📒

TG Requirement 7
Coverage data encoded in standalone JPEG 2000 files shall comply with the OGC standard GML in JPEG 2000 for Geographic Imagery [OGC 05-047r2].

TG Requirement 7 implies that all the encoding rules presented in GMLJP2 shall be strictly followed for including GML within JPEG 2000 data files correctly. For the sake of harmonization, the encoding rules adopted for the multipart message encoding should also apply to the GMLJP2 encoding.

📘

Recommendation 34
The encoding of coverage components in GMLJP2 within a JPEG 2000 file should conform to the rules specified in the Guidelines for the encoding of spatial data [DS-D2.7].

10. Data Capture

There is no specific guidance required with respect to data capture.

11. Portrayal

This clause defines the rules for layers and styles to be used for portrayal of the spatial object types defined for this theme. Portrayal is regulated in Article 14 of the IRs.

📕

IR Requirement
Article 14
Portrayal

  1. For the portrayal of spatial data sets using a view network service as specified in Commission Regulation No 976/2009 ([19]), the following shall be available:

    1. the layers specified in Annex II for the theme or themes the data set is related to;

    2. for each layer at least a default portrayal style, with as a minimum an associated title and a unique identifier.

  1. For each layer, Annex II defines the following:

    1. a human readable title of the layer to be used for display in user interface;

    2. the spatial object type(s), or sub-set thereof, that constitute(s) the content of the layer.

In section 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 data on a specific topic.

NOTE The layer specification in the IRs only contains the name, a human readable title and the (subset(s) of) spatial object type(s), that constitute(s) the content of the layer. In addition, these Technical Guidelines suggest keywords for describing the layer.

📘

Recommendation 35
It is recommended to use the keywords specified in section 11.1 in the Layers Metadata parameters of the INSPIRE View service (see Annex III, Part A, section 2.2.4 in Commission Regulation (EC) No 976/2009).

Section 11.2 specifies one style for each of these layers. It is proposed that INSPIRE view services support this style as the default style required by Article 14(1b).

📒

TG Requirement 8
For each layer specified in this section, the styles defined in section 11.2 shall be available.

NOTE The default style should be used for portrayal by the view network service if no user-defined style is specified in a portrayal request for a specific layer.

In section 11.3, 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.

📘

Recommendation 36
In addition, it is recommended that, where applicable, INSPIRE view services also support the styles defined in section 11.3.

Where XML fragments are used in the following sections, the following namespace prefixes apply:

  • sld="http://www.opengis.net/sld" (WMS/SLD 1.1)

  • se="http://www.opengis.net/se" (SE 1.1)

  • ogc="http://www.opengis.net/ogc" (FE 1.1)

11.1. Layers to be provided by INSPIRE view services

Layer Name Layer Title Spatial object type(s) Keywords

LU.ExistingLandUse

Existing Land Use objects according to the Hierarchical INSPIRE Land Use Classification System at the most appropriate level

ExistingLandUseObject

Land Use

LU.SpatialPlan

Extent of a spatial plan

SpatialPlan

Land Use, Spatial Plan

LU.ZoningElement

Spatial planning Zoning objects according to the Hierarchical INSPIRE Land Use Classification System at the most appropriate level

ZoningElement

Land Use, Spatial Plan, zoning

LU.SupplementaryRegulation

Regulations that supplement the zoning and that affect the use of land

SupplementaryRegulation

Land Use, Spatial Plan, regulation zone

NOTE The table above contains several layers for some spatial object types, which can be further classified using a code list-valued attribute. Such sets of layers are specified as described in Article 14(3) of the IRs.

📕

IR Requirement
Article 14
Portrayal

(…​)

  1. For spatial object types whose objects can be further classified using a code list-valued attribute, several layers may be defined. Each of these layers shall include the spatial objects corresponding to one specific code list value. In the definition of such sets of layers in Annexes II-IV,

    1. the placeholder <CodeListValue> shall represent the values of the relevant code list, with the first letter in upper case,

    2. the placeholder <human-readable name> shall represent the human-readable name of the code list values;

    3. the spatial object type shall include the relevant attribute and code list, in parentheses;

    4. one example of a layer shall be given.

11.1.1. Layers organisation

None.

11.2. Styles required to be supported by INSPIRE view services

11.2.1. Styles for the layer LandUse.ExistingLandUse

Style Name LandUse.ExistingLandUse.Default

Default Style

yes

Style Title

Existing Land Use Default Style

Style Abstract

Existing Land Use objects filled with a colour depending on the value of the attribute from HILUCS level 1 nomenclature and their boundaries as black lines of 2 pixels

image

Some data providers may be willing to make adjustments to the above colour chart in order to provide a better interpretation of the different land uses at first sight. These adjustments should be as limited as possible and should stick to the color convention above.

For example one may differentiate agricultural use from the forestry use, depict the water bodies underneath or differentiate the various type of other uses. The possible adjustments are given below:

image

Symbology

The SLD specifying the symbology is distributed in a file separately from the data specification document.

Minimum & maximum scales

to be provided by the data provider (it depends on the Minimum Unit of Interest (MUI) as provided in the Metadata)

Example
PortrayalELU2

11.2.2. Styles for the layer LandUse.SpatialPlan

Style Name LandUse.SpatialPlan.Default

Default Style

yes

Style Title

Planned Land Use Default Style

Style Abstract

Spatial plan extent provided by black lines of 2 pixels

Symbology

The SLD specifying the symbology is distributed in a file separately from the data specification document.

Minimum & maximum scales

to be provided by the data provider (it depends on the type of spatial plan, i.e. structural plan, zoning plan or construction plan)

Example
PortrayalExtent

11.2.3. Styles for the layer LandUse.ZoningElement

Style Name LandUse.ZoningElement.Default

Default Style

yes

Style Title

Planned Zoning Element Default Style

Style Abstract

Planned Land Use zoning elements filled with a colour depending on the value of the attribute from HILUCS level 1 nomenclature and their boundaries as black lines of 2 pixels

image

Some data providers may be willing to make adjustments to the above colour chart in order to provide a better interpretation of the different land uses at first sight. These adjustments should be as limited as possible and should stick to the color convention above.

For example one may differentiate agricultural use from the forestry use, depict the water bodies underneath or differentiate the various type of other uses. The possible adjustments are given below:

image

Symbology

The SLD specifying the symbology is distributed in a file separately from the data specification document.

Minimum & maximum scales

to be provided by the data provider (it depends on the type of spatial plan, i.e. structural plan, zoning plan or construction plan)

Example
PortrayalPLU2

11.2.4. Styles for the layer LandUse.SupplementaryRegulation

Style Name LandUse.SupplementaryRegulation.Default

Default Style

yes

Style Title

Supplementary Regulation Default Style

Style Abstract

Contour or line of the Supplementary regulation depicted by a colour line of two pixels, colour depending of the value of the attribute supplementaryRegulation

image

Symbol for point supplementary regulation

Symbology

The SLD specifying the symbology is distributed in a file separately from the data specification document.

Minimum & maximum scales

to be provided by the data provider (it depends on the type of spatial plan, i.e. structural plan, zoning plan or construction plan)

Example
PortrayalSR1

11.3. Styles recommended to be supported by INSPIRE view services

None.

Bibliography

[DS-D2.3] INSPIRE DS-D2.3, Definition of Annex Themes and Scope, v3.0, https://knowledge-base.inspire.ec.europa.eu/publications/definition-annex-themes-and-scope-d-23-version-30_en

[DS-D2.5] INSPIRE DS-D2.5, Generic Conceptual Model, v3.3, https://knowledge-base.inspire.ec.europa.eu/publications/inspire-generic-conceptual-model_en

[DS-D2.6] INSPIRE DS-D2.6, Methodology for the development of data specifications, v3.0, https://knowledge-base.inspire.ec.europa.eu/publications/methodology-development-data-specifications-baseline-version-d-26-version-30_en

[DS-D2.7] INSPIRE DS-D2.7, Guidelines for the encoding of spatial data, v3.2, https://knowledge-base.inspire.ec.europa.eu/publications/guidelines-encoding-spatial-data_en

[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

Annex A: Abstract Test Suite - (normative)

Disclaimer

While this Annex refers to the Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services, it does not replace the legal act or any part of it.

The objective of the Abstract Test Suite (ATS) included in this Annex is to help the conformance testing process. It includes a set of tests to be applied on a data set to evaluate whether it fulfils the requirements included in this data specification and the corresponding parts of Commission Regulation No 1089/2010 (implementing rule as regards interoperability of spatial datasets and services, further referred to as ISDSS Regulation). This is to help data providers in declaring the conformity of a data set to the "degree of conformity, with implementing rules adopted under Article 7(1) of Directive 2007/2/EC", which is required to be provided in the data set metadata according to Commission Regulation (EC) No 2008/1205 (the Metadata Regulation).

Part 1 of this ATS includes tests that provide input for assessing conformity with the ISDSS regulation. In order to make visible which requirements are addressed by a specific test, references to the corresponding articles of the legal act are given. The way how the cited requirements apply to lu specification is described under the testing method.

In addition to the requirements included in ISDSS Regulation this Technical guideline contains TG requirements too. TG requirements are technical provisions that need to be fulfilled in order to be conformant with the corresponding IR requirement when the specific technical implementation proposed in this document is used. Such requirements relate for example to the default encoding described in section 9. Part 2 of the ATS presents tests necessary for assessing the conformity with TG requirements.

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

The ATS is applicable to the data sets that have been transformed to be made available through INSPIRE download services (i.e. the data returned as a response to the mandatory "Get Spatial Dataset" operation) rather than the original "source" data sets.

The requirements to be tested are grouped in several conformance classes. Each of these classes covers a specific aspect: one conformance class contains tests reflecting the requirements on the application schema, another on the reference systems, etc. Each conformance class is identified by a URI (uniform resource identifier) according to the following pattern:

http://inspire.ec.europa.eu/conformance-class/ir/lu/<conformance class identifier>

EXAMPLE 1 The URI http://inspire.ec.europa.eu/conformance-class/ir/ef/rs identifies the Reference Systems ISDSS conformance class of the Environmental Monitoring Facilities (EF) data theme.

The results of the tests should be published referring to the relevant conformance class (using its URI).

When an INSPIRE data specification contains more than one application schema, the requirements tested in a conformance class may differ depending on the application schema used as a target for the transformation of the data set. This will always be the case for the application schema conformance class. However, also other conformance classes could have different requirements for different application schemas. In such cases, a separate conformance class is defined for each application schema, and they are distinguished by specific URIs according to the following pattern:

http://inspire.ec.europa.eu/conformance-class/ir/lu/<conformance class identifier>/
<application schema namespace prefix>

EXAMPLE 2 The URI http://inspire.ec.europa.eu/conformance-class/ir/el/as/el-vec identifies the conformity with the application schema (as) conformance class for the Elevation Vector Elements (el-vec) application schema.

An overview of the conformance classes and the associated tests is given in the table below.

A.1 Application Schema Conformance Class

A.1.1 Schema element denomination test

A.1.2 Value type test

A.1.3 Value test

A.1.4 Attributes/associations completeness test

A.1.5 Abstract spatial object test

A.1.6 Constraints test

This test should include

A.1.7 Geometry representation test

A.2 Reference Systems Conformance Class

A.2.1 Datum test

A.2.2 Coordinate reference system test

A.2.3 Grid test

A.2.4 View service coordinate reference system test

A.2.5 Temporal reference system test

A.2.6 Units of measurements test

A.3 Data Consistency Conformance Class

A.3.1 Unique identifier persistency test

A.3.2 Version consistency test

A.3.3 Life cycle time sequence test

A.3.4 Validity time sequence test

A.3.5 Update frequency test

A.4 Metadata IR Conformance Class

A.4.1 Metadata for interoperability test

A.5 Information Accessibility Conformance Class

A.5.1 Code list publication test

A.5.2 CRS publication test

A.5.3 CRS identification test

A.5.4 Grid identification test

A.6 Data Delivery Conformance Class

A.6.1 Encoding compliance test

A.7 Portrayal Conformance Class

A.7.1 Layer designation test

A.8 Technical Guideline Conformance Class

A.8.1 Multiplicity test

A.8.2 CRS http URI test

A.8.3 Metadata encoding schema validation test

A.8.4 Metadata occurrence test

A.8.5 Metadata consistency test

A.8.6 Encoding schema validation test

A.8.7 Coverage multipart representation test

A.8.8 Coverage domain consistency test

A.8.9 Style test

In order to be conformant to a conformance class, a data set has to pass all tests defined for that conformance class.

In order to be conformant with the ISDSS regulation the inspected data set needs to be conformant to all conformance classes in Part 1. The conformance class for overall conformity with the ISDSS regulation is identified by the URI http://inspire.ec.europa.eu/conformance-class/ir/lu/.

In order to be conformant with the Technical Guidelines, the dataset under inspection needs to be conformant to all conformance classes included both in Part 1 and 2. Chapter 8 describes in detail how to publish the result of testing regarding overall conformity and conformity with the conformance classes as metadata. The conformance class for overall conformity with the Technical Guidelines is identified by the URI http://inspire.ec.europa.eu/conformance-class/tg/lu/3.0.

It should be noted that data providers are not obliged to integrate / decompose the original structure of the source data sets when they deliver them for INSPIRE. It means that a conformant dataset can contain less or more spatial object / data types than specified in the ISDSS Regulation.

A dataset that contains less spatial object and/or data types can be regarded conformant when the corresponding types of the source datasets after the necessary transformations fulfil the requirements set out in the ISDSS Regulation.

A dataset that contain more spatial object and/or data types may be regarded as conformant when

  • all the spatial object / data types that have corresponding types in the source dataset after the necessary transformations fulfil the requirements set out in the ISDSS Regulation and

  • all additional elements of the source model (spatial object types, data types, attributes, constraints and code lists together with their values) do not conflict with any rule defined in the interoperability target specifications defined for any theme within INSPIRE.

Open Issue 2: Even though the last condition can be derived from Art. 8(4) of the Directive, the ISDSS Regulation does not contain requirements concerning the above issue. Therefore, no specific tests have been included in this abstract suite for testing conformity of extended application schemas. Annex F of the Generic Conceptual Model (D2.5) provides an example how to extend INSPIRE application schemas in a compliant way.

The ATS contains a detailed list of abstract tests. It should be noted that some tests in the Application schema conformance class can be automated by utilising xml schema validation tools. It should be noted that failing such validation test does not necessary reflect non-compliance to the application schema; it may be the results of erroneous encoding.

Each test in this suite follows the same structure:

  • Requirement: citation from the legal texts (ISDSS requirements) or the Technical Guidelines (TG requirements);

  • Purpose: definition of the scope of the test;

  • Reference: link to any material that may be useful during the test;

  • Test method: description of the testing procedure.

According to ISO 19105:2000 all tests in this ATS are basic tests. Therefore, this statement is not repeated each time.

Part 1 - (normative)
Conformity with Commission Regulation No 1089/2010

A.1. Application Schema Conformance Class

Conformance class:
http://inspire.ec.europa.eu/conformance-class/ir/lu/as/Land Use

A.1.1. Schema element denomination test

a) Purpose: Verification whether each element of the dataset under inspection carries a name specified in the target application schema(s).

b) Reference: Art. 3 and Art.4 of Commission Regulation No 1089/2010

c) Test Method: Examine whether the corresponding elements of the source schema (spatial object types, data types, attributes, association roles and code lists) are mapped to the target schema with the correct designation of mnemonic names.

NOTE Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

A.1.2. Value type test

a) Purpose: Verification whether all attributes or association roles use the corresponding value types specified in the application schema(s).

b) Reference: Art. 3, Art.4, Art.6(1), Art.6(4), Art.6(5) and Art.9(1)of Commission Regulation No 1089/2010.

c) Test Method: Examine whether the value type of each provided attribute or association role adheres to the corresponding value type specified in the target specification.

NOTE 1 This test comprises testing the value types of INSPIRE identifiers, the value types of attributes and association roles that should be taken from code lists, and the coverage domains.

NOTE 2 Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

A.1.3. Value test

a) Purpose: Verify whether all attributes or association roles whose value type is a code list take the values set out therein.

b) Reference: Art.4 (3) of Commission Regulation No 1089/2010.

c) Test Method: When an attribute / association role has an code list as its type, compare the values of each instance with those provided in the application schema. To pass this tests any instance of an attribute / association role

  • Shall take only values explicitly specified in the code list when the code list’s extensibility is "none".

  • Shall take only a value explicitly specified in the code list or shall take a value that is narrower (i.e. more specific) than those explicitly specified in the application schema when the code list’s extensibility is "narrower".

  • Any Land Use data sets shall assign to each polygon, pixel or location a land use type from the HILUCS at the most appropriate and detailed level of the hierarchy.

NOTE 1 This test is not applicable to code lists with extensibility "open" or "any".

NOTE 2 When a data provider only uses code lists with narrower (more specific values) this test can be fully performed based on internal information.

A.1.4. Attributes/associations completeness test

a) Purpose: Verification whether each instance of spatial object type and data types include all attributes and association roles as defined in the target application schema.

b) Reference: Art. 3, Art.4(1), Art.4(2), and Art.5(2) of Commission Regulation No 1089/2010.

c) Test Method: Examine whether all attributes and association roles defined for a spatial object type or data type are present for each instance in the dataset.

NOTE 1 Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

NOTE 2 For all properties defined for a spatial object, a value has to be provided if it exists in or applies to the real world entity – either the corresponding value (if available in the data set maintained by the data provider) or the value of void. If the characteristic described by the attribute or association role does not exist in or apply to the real world entity, the attribute or association role does not need to be present in the data set.

A.1.5. Abstract spatial object test

a) Purpose: Verification whether the dataset does NOT contain abstract spatial object / data types defined in the target application schema(s).

b) Reference: Art.5(3) of Commission Regulation No 1089/2010

c) Test Method: Examine that there are NO instances of abstract spatial object / data types in the dataset provided.

NOTE Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

A.1.6. Constraints test

a) Purpose: Verification whether the instances of spatial object and/or data types provided in the dataset adhere to the constraints specified in the target application schema(s).

b) Reference: Art. 3, Art.4(1), and Art.4(2) of Commission Regulation No 1089/2010.

c) Test Method: Examine all instances of data for the constraints specified for the corresponding spatial object / data type. Each instance shall adhere to all constraints specified in the target application schema(s).

Examine if the spatial object type CoverageByDomainAndRange is provided and if is a subtype of GridCoverage.

NOTE Further technical information is in the Feature catalogue and UML diagram of the application schema(s) in section 5.2.

A.1.7. This test should include

(2) The spatial object type CoverageByDomainAndRange must only be of subtypes of GridCoverage.

A.1.8. Geometry representation test

a) Purpose: Verification whether the value domain of spatial properties is restricted as specified in the Commission Regulation No 1089/2010.

b) Reference: Art.12(1), Annex IV Section 4 of Commission Regulation No 1089/2010

c) Test Method: Check whether all spatial properties only use 0, 1 and 2-dimensional geometric objects that exist in the right 2-, 3- or 4-dimensional coordinate space, and where all curve interpolations respect the rules specified in the reference documents.

NOTE Further technical information is in OGC Simple Feature spatial schema v1.2.1 [06-103r4].

A.2. Reference Systems Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/lu/rs

A.2.1. Datum test

a) Purpose: Verify whether each instance of a spatial object type is given with reference to one of the (geodetic) datums specified in the target specification.

b) Reference: Annex II Section 1.2 of Commission Regulation No 1089/2010

c) Test Method: Check whether each instance of a spatial object type specified in the application schema(s) in section 5 has been expressed using:

  • the European Terrestrial Reference System 1989 (ETRS89) within its geographical scope; or

  • the International Terrestrial Reference System (ITRS) for areas beyond the ETRS89 geographical scope; or

  • other geodetic coordinate reference systems compliant with the ITRS. Compliant with the ITRS means that the system definition is based on the definition of ITRS and there is a well-established and described relationship between both systems, according to the EN ISO 19111.

NOTE Further technical information is given in Section 6 of this document.

A.2.2. Coordinate reference system test

a) Purpose: Verify whether the two- and three-dimensional coordinate reference systems are used as defined in section 6.

b) Reference: Section 6 of Commission Regulation 1089/2010.

c) Test Method: Inspect whether the horizontal and vertical components of coordinates one of the corresponding coordinate reference system has been:

  • Three-dimensional Cartesian coordinates based on a datum specified in 1.2 and using the parameters of the Geodetic Reference System 1980 (GRS80) ellipsoid.

  • Three-dimensional geodetic coordinates (latitude, longitude and ellipsoidal height) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.

  • Two-dimensional geodetic coordinates (latitude and longitude) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.

  • Plane coordinates using the ETRS89 Lambert Azimuthal Equal Area coordinate reference system.

  • Plane coordinates using the ETRS89 Lambert Conformal Conic coordinate reference system.

  • Plane coordinates using the ETRS89 Transverse Mercator coordinate reference system.

  • For the vertical component on land, the European Vertical Reference System (EVRS) shall be used to express gravity-related heights within its geographical scope. Other vertical reference systems related to the Earth gravity field shall be used to express gravity-related heights in areas that are outside the geographical scope of EVRS.

  • For the vertical component in marine areas where there is an appreciable tidal range (tidal waters), the Lowest Astronomical Tide (LAT) shall be used as the reference surface.

  • For the vertical component in marine areas without an appreciable tidal range, in open oceans and effectively in waters that are deeper than 200 meters, the Mean Sea Level (MSL) or a well-defined reference level close to the MSL shall be used as the reference surface."

  • For the vertical component in the free atmosphere, barometric pressure, converted to height using ISO 2533:1975 International Standard Atmosphere, or other linear or parametric reference systems shall be used. Where other parametric reference systems are used, these shall be described in an accessible reference using EN ISO 19111-2:2012.

  • Member State shall define a projection or a set of projections suitable for working with the underlying cadastral parcels on national territory and cross-border areas where applicable for a SpatialPlan. This projection or set of projections must be well documented to allow the conversion from and to the common Coordinate Reference System. The documentation shall be provided according to ISO 19111, which states how a projected coordinate reference system must be described.

NOTE Further technical information is given in Section 6 of this document.

A.2.3. Grid test

a) Purpose: Verify that gridded data related are available using the grid compatible with one of the coordinate reference systems defined in Commission Regulation No 1089/2010

b) Reference: Annex II Section 2.1 and 2.2 of Commission Regulation 1089/2010.

c) Test Method: Check whether the dataset defined as a grid is compatible with one of the coordinate reference.

  • Grid_ETRS89_GRS80 based on two-dimensional geodetic coordinates using the parameters of the GRS80 ellipsoid

  • Grid_ETRS89_GRS80zn based on two-dimensional geodetic coordinates with zoning,

  • Plane coordinates using the Lambert Azimuthal Equal Area projection and the parameters of the GRS80 ellipsoid (ETRS89-LAEA)

  • Plane coordinates using the Lambert Conformal Conic projection and the parameters of the GRS80 ellipsoid (ETRS89-LCC)

  • Plane coordinates using the Transverse Mercator projection and the parameters of the GRS80 ellipsoid (ETRS89-TMzn)

NOTE Further technical information is given in Section 6 of this document.

A.2.4. View service coordinate reference system test

a) Purpose: Verify whether the spatial data set is available in the two dimensional geodetic coordinate system for their display with the INSPIRE View Service.

b) Reference: Annex II Section 1.4 of Commission Regulation 1089/2010

c) Test Method: Check that each instance of a spatial object types specified in the application schema(s) in section 5 is available in the two-dimensional geodetic coordinate system

NOTE Further technical information is given in Section 6 of this document.

A.2.5. Temporal reference system test

a) Purpose: Verify whether date and time values are given as specified in Commission Regulation No 1089/2010.

b) Reference: Art.11(1) of Commission Regulation 1089/2010

c) Test Method: Check whether:

  • the Gregorian calendar is used as a reference system for date values;

  • the Universal Time Coordinated (UTC) or the local time including the time zone as an offset from UTC are used as a reference system for time values.

NOTE Further technical information is given in Section 6 of this document.

A.2.6. Units of measurements test

a) Purpose: Verify whether all measurements are expressed as specified in Commission Regulation No 1089/2010.

b) Reference: Art.12(2) of Commission Regulation 1089/2010

c) Test Method: Check whether all measurements are expressed in SI units or non-SI units accepted for use with the International System of Units.

NOTE 1 Further technical information is given in ISO 80000-1:2009.

NOTE 2 Degrees, minutes and seconds are non-SI units accepted for use with the International System of Units for expressing measurements of angles.

A.3. Data Consistency Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/lu/dc

A.3.1. Unique identifier persistency test

a) Purpose: Verify whether the namespace and localId attributes of the external object identifier remain the same for different versions of a spatial object.

b) Reference: Art. 9 of Commission Regulation 1089/2010.

c) Test Method: Compare the namespace and localId attributes of the external object identifiers in the previous version(s) of the dataset with the namespace and localId attributes of the external object identifiers of current version for the same instances of spatial object / data types; To pass the test, neither the namespace, nor the localId shall be changed during the life-cycle of a spatial object.

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

NOTE 2 When using URI this test includes the verification whether no part of the construct has been changed during the life cycle of the instances of spatial object / data types.

NOTE 3 Further technical information is given in section 14.2 of the INSPIRE Generic Conceptual Model.

A.3.2. Version consistency test

a) Purpose: Verify whether different versions of the same spatial object / data type instance belong to the same type.

b) Reference: Art. 9 of Commission Regulation 1089/2010.

c) Test Method: Compare the types of different versions for each instance of spatial object / data type

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

A.3.3. Life cycle time sequence test

a) Purpose: Verification whether the value of the attribute beginLifespanVersion refers to an earlier moment of time than the value of the attribute endLifespanVersion for every spatial object / object type where this property is specified.

b) Reference: Art.10(3) of Commission Regulation 1089/2010.

c) Test Method: Compare the value of the attribute beginLifespanVersion with attribute endLifespanVersion. The test is passed when the beginLifespanVersion value is before endLifespanVersion value for each instance of all spatial object/data types for which this attribute has been defined.

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

A.3.4. Validity time sequence test

a) Purpose: Verification whether the value of the attribute validFrom refers to an earlier moment of time than the value of the attribute validTo for every spatial object / object type where this property is specified.

b) Reference: Art.12(3) of Commission Regulation 1089/2010.

c) Test Method: Compare the value of the attribute validFrom with attribute validTo. The test is passed when the validFrom value is before validTo value for each instance of all spatial object/data types for which this attribute has been defined.

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

A.3.5. Update frequency test

a) Purpose: Verify whether all the updates in the source dataset(s) have been transmitted to the dataset(s) which can be retrieved for the LU data theme using INSPIRE download services.

b) Reference: Art.8 (2) of Commission Regulation 1089/2010.

c) Test Method: Compare the values of beginning of life cycle information in the source and the target datasets for each instance of corresponding spatial object / object types. The test is passed when the difference between the corresponding values is less than 6 months.

NOTE 1 This test can be performed exclusively on the basis of the information available in the database of the data providers.

A.4. Metadata IR Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/lu/md

A.4.1. Metadata for interoperability test

  1. Purpose: Verify whether the metadata for interoperability of spatial data sets and services described in 1089/2010 Commission Regulation have been created and published for each dataset related to the LU data theme.

  2. Reference: Art.13 of Commission Regulation 1089/2010

  3. Test Method: Inspect whether metadata describing the coordinate reference systems, encoding, topological consistency and spatial representation type have been created and published. If the spatial data set contains temporal information that does not refer to the default temporal reference system, inspect whether metadata describing the temporal reference system have been created and published. If an encoding is used that is not based on UTF-8, inspect whether metadata describing the character encoding have been created.

  4. Inspect if the common metadata element "Spatial Resolution" is restricted to provide a resolution distance.

  5. Inspect if the following keywords in addition to the mandatory keywords are provided:

    (1) One of the following language-neutral keywords to describe the type of land use data set: ExistingLandUse, SampledExistingLandUse, GriddedExistingLandUse, PlannedLandUse.

    (2) If the data set contains SpatialPlan objects, one keyword describing the level of the administrative units covered by the plan, as defined in the LevelOfSpatialPlan code list.

NOTE Further technical information is given in section 8 of this document.

A.5. Information Accessibility Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/lu/ia

A.5.1. Code list publication test

a) Purpose: Verify whether all additional values used in the data sets for attributes, for which narrower values or any other value than specified in Commission Regulation 1089/2010 are allowed, are published in a register.

b) Reference: Art.6(3) and Annex IV Section 4.

c) Test Method: For each additional value used in the data sets for code list-valued attributes, check whether it is published in a register.

NOTE Further technical information is given in section 5 of this document.

A.5.2. CRS publication test

a) Purpose: Verify whether the identifiers and the parameters of coordinate reference system are published in common registers.

b) Reference: Annex II Section 1.5

c) Test Method: Check whether the identifier and the parameter of the CRS used for the dataset are included in a register. .

NOTE Further technical information is given in section 6 of this document.

A.5.3. CRS identification test

a) Purpose: Verify whether identifiers for other coordinate reference systems than specified in Commission Regulation 1089/2010 have been created and their parameters have been described according to EN ISO 19111 and ISO 19127.

b) Reference: Annex II Section 1.3.4

c) Test Method: Check whether the register with the identifiers of the coordinate reference systems is accessible.

NOTE Further technical information is given in section 6 of this document.

A.5.4. Grid identification test

a) Purpose: Verify whether identifiers for other geographic grid systems than specified in Commission Regulation 1089/2010 have been created and their definitions have been either described with the data or referenced.

b) Reference: Annex II Section 2.1 and 2.2

c) Test Method: Check whether the identifiers for grids have been created. Inspect the dataset and/or the metadata for inclusion of grid definition.

NOTE Further technical information is given in section 6 of this document.

A.6. Data Delivery Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/lu/de

A.6.1. Encoding compliance test

a) Purpose: Verify whether the encoding used to deliver the dataset comply with EN ISO 19118.

b) Reference: Art.7 (1) of Commission Regulation 1089/2010.

c) Test Method: Follow the steps of the Abstract Test Suit provided in EN ISO 19118.

NOTE 1 Datasets using the default encoding specified in Section 9 fulfil this requirement.

NOTE 2 Further technical information is given in Section 9 of this document.

A.7. Portrayal Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/ir/lu/po

A.7.1. Layer designation test

a) Purpose: verify whether each spatial object type has been assigned to the layer designated according to Commission Regulation 1089/2010.

b) Reference: Art. 14(1), Art14(2) and Annex IV Section 4.

c) Test Method: Check whether data is made available for the view network service using the specified layers respectively:

  • LU.ExistingLandUse

  • LU.SpatialPlan

  • LU.ZoningElement

  • LU.SupplementaryRegulation

NOTE Further technical information is given in section 11 of this document.

Part 2 - (informative)

Conformity with the technical guideline (TG) Requirements

A.8. Technical Guideline Conformance Class

Conformance class:

http://inspire.ec.europa.eu/conformance-class/tg/lu/3.0

A.8.1. Multiplicity test

a) Purpose: Verify whether each instance of an attribute or association role specified in the application schema(s) does not include fewer or more occurrences than specified in section 5.

b) Reference: Feature catalogue and UML diagram of the application schema(s) in section 5 of this guideline.

c) Test Method: Examine that the number of occurrences of each attribute and/or association role for each instance of a spatial object type or data type provided in the dataset corresponds to the number of occurrences of the attribute / association role that is specified in the application schema(s) in section 5.

A.8.2. CRS http URI test

a) Purpose: Verify whether the coordinate reference system used to deliver data for INSPIRE network services has been identified by URIs according to the EPSG register.

b) Reference: Section 6 of this technical guideline

c) Test Method: Compare the URI of the dataset with the URIs in the table.

NOTE 1 Passing this test implies the fulfilment of test A6.2

NOTE 2 Further reference please see http://www.epsg.org/geodetic.html

A.8.3. Metadata encoding schema validation test

a) Purpose: Verify whether the metadata follows an XML schema specified in ISO/TS 19139.

b) Reference: Section 8 of this technical guideline, ISO/TS 19139

c) Test Method: Inspect whether provided XML schema is conformant to the encoding specified in ISO 19139 for each metadata instance.

NOTE 1 Section 2.1.2 of the Metadata Technical Guidelines discusses the different ISO 19139 XML schemas that are currently available.

A.8.4. Metadata occurrence test

a) Purpose: Verify whether the occurrence of each metadata element corresponds to those specified in section 8.

b) Reference: Section 8 of this technical guideline

c) Test Method: Examine the number of occurrences for each metadata element. The number of occurrences shall be compared with its occurrence specified in Section 8:

NOTE 1 Section 2.1.2 of the Metadata Technical Guidelines discusses the different ISO 19139 XML schema.

A.8.5. Metadata consistency test

a) Purpose: Verify whether the metadata elements follow the path specified in ISO/TS 19139.

b) Reference: Section 8 of this technical guideline, ISO/TS 19139

c) Test Method: Compare the XML schema of each metadata element with the path provide in ISO/TS 19137.

NOTE 1 This test does not apply to the metadata elements that are not included in ISO/TS 19139.

A.8.6. Encoding schema validation test

a) Purpose: Verify whether the provided dataset follows the rules of default encoding specified in section 9 of this document

b) Reference: section 9 of this technical guideline

c) Test Method: Inspect whether provided encoding(s) is conformant to the encoding(s) for the relevant application schema(s) as defined in section 9:

NOTE 1 Applying this test to the default encoding schema described in section 9 facilitates testing conformity with the application schema specified in section 5. In such cases running this test with positive result may replace tests from A1.1 to A1.4 provided in this abstract test suite.

NOTE 2 Using Schematron or other schema validation tool may significantly improve the validation process, because some some complex constraints of the schema cannot be validated using the simple XSD validation process. On the contrary to XSDs Schematron rules are not delivered together with the INSPIRE data specifications. Automating the process of validation (e.g. creation of Schematron rules) is therefore a task and an opportunity for data providers.

A.8.7. Coverage multipart representation test

a) Purpose: Verify whether coverage data encoded as multipart messages comply with the multipart representation conformance class defined in GML Application Schema for Coverages [OGC 09-146r2].

b) Reference: OGC standard GML Application Schema for Coverages [OGC 09-146r2].

c) Test Method: Inspect whether coverage data encoded as multipart messages comply with the multipart representation conformance class defined in GML Application Schema for Coverages [OGC 09-146r2].

NOTE further information is provided in section 9.4 of this technical guideline.

A.8.8. Coverage domain consistency test

a) Purpose: Verify whether the encoded coverage domain is consistent with the information provided in the GML application schema.

b) Reference: Section 9.4.1.2 of this technical guideline.

c) Test Method: For multipart coverage messages compare the encoded coverage domain with the description of the coverage component in the GML application schema

NOTE 1 This test applies only to those multipart messages, where the coverage range is encoded together with the coverage domain (some binary formats).

NOTE 2 .This test does not apply to multipart messages where the coverage range is embedded without describing the data structure (e.g. text based formats).

A.8.9. Style test

a) Purpose: Verify whether the styles defined in section 11.2 have been made available for each specified layer.

b) Reference: section 11.2.

c) Test Method: Check whether the styles defined in section 11.2 have been made available for each specified layer.

Annex B: Use cases - (informative)

B.1. Introduction

The use cases section intends to sum up the understanding of the Thematic Working Group on Land Use after having reviewed 47 use cases and 26 reference materials provided by the SDICs and the LMOs and after having conducted interviews to ascertain the user requirements. The objective of a use case is to give a description of situations where land use datasets are required to perform a given task. These use cases are documented in order to understand how the requirements have been filtered in view of designing a conceptual model generic enough to cover potential use cases and simple enough to minimise the burden on the shoulder of data producers and uses.

Sections B2 to B5 identify the use cases considered relevant and express the requirements in broad terms. Four use cases have been selected as representative of those reported by SDICS and LMOs to the land use thematic working group:

  • land planning,

  • analysis of land consumption,

  • ecological network mapping,

  • greenhouse inventory reporting.

Users' information collection was sometimes heterogeneous, for these reason these four use cases have been fully documented using the INSPIRE template to reach a harmonization with other themes. Figure 31 provides an overview of the use cases regarding the type of land use that is required, the temporality of the required land use data, (either past, present of future land use) and the type of activities that requires land use data.

image

Figure 31 – Graphs of use cases study about lands involved, temporal dimension and context of use (framework).

Four other use cases are also presented although less detailed in section B6: Land Use for environmental impact assessment, Land Use for the flood directive, Statistics for Land Use, Land Use for soil management

Sections B7 to B8 sum up the data requirements as resulting from the use case analysis. They are presented for both existing and planned land use. It expresses the main requirements regarding the features that need to be taken into consideration, the nomenclature to be used, the temporal dimension, identifiers, portrayal, metadata and requirements for consistency with other themes. It also identifies requirements that have been omitted mainly due to expected difficulties in meeting them.

The previous 'use cases' presentation are based on the current process of data management, and the resulting requirements imperfectly reflect the real user needs. In practice the users handle the accessible data that are most suitable for their objectives but not necessarily the optimal data that best meet their requirements. In many cases optimal data are not available because they may not exist, have technical limitations or are unaffordable. So a complementary review of actual users' requirements has been used to improve the data specification: the detailed requirements inventory from ICT PSP HLANDATA[20] project about creation of value-added services based on Harmonized Land Use and Land Cover Datasets.

As an INSPIRE theme, Land Use belongs to a domain where little standardisation has occurred in Europe. Land Use is also often mixed with Land Cover both in term of available datasets and user requirements.

Land Use is perceived as the actual existing land use as it can be observed in reality as well as the intention of authorities for the future land use expressed via spatial plans.

The Nomenclature issue is one of the key requirements. It is felt important to: on the one hand make progress towards a simple but agreed nomenclature applicable throughout Europe; and on the other hand be able to accommodate local nomenclatures that correspond to local usage and culture.

B.2. Land Planning

B.2.1. Narrative description

Regional/spatial planning is a "scientific discipline, an administrative technique and a policy developed as an interdisciplinary and comprehensive approach directed towards a balanced regional development and the physical organisation of space according to an overall strategy[21]".

The spatial planning process produces Land Use regulation. Three main steps are usually defined:

  • the elaboration step which includes diagnostics of the current situation of a given area and proposed scenarios for its development

  • the adoption step that usually involves a democratic discussion on the selected scenario

  • the "opposition to third parties" step when the Land Use regulation comes into force and is applicable to any further changes to the physical organisation and use of space.

Once adopted, the Land Use regulation (Spatial Plan) is an instrument to implement the choices regarding the spatial-structural development of a certain area. It orders the land use and is composed of two binding parts: a graphic map that indicates on which area the plan is applied and the belonging textual planning requirements. For the majority of the European countries, with the notable exception of the Netherlands, the spatial plan printed on paper and signed by the appropriate authority is the only document that is "opposable to third parties" its digital form having no legal status.

As far as the elaboration step and the adoption step are concerned, the main Land Use requirement is related to the datasets that describe existing Land Use at present and in the past. The issue is related to the understanding of the driving forces that shaped the land, i.e. understanding why the land looks like it is in the reality. Having the trajectory of the land changes with time allows modelling what land tends to be in the future.

Planned Land Use is the result of the planning process. It provides the graphical and textual regulation that will control the future shaping of the land through the land uses that will be permitted or forbidden.

The usage of Planned Land Use is twofold:

  • On the one hand the "land law enforcement[22]" (or land right implementation) is the process of delivering the appropriate authorisation needed for constructing a building, a road, a railway, or any human built artefact. The full land use regulation (spatial plan) is required for the process to be fully legal and to minimize the number of disputes. Having access to the digital facsimile of the legal document may avoid going back to the paper. Users are to be identified as the citizen, the architect, the promoter, or any person or organisation that requests the authorisation to build something, but also the entity that instructs and delivers the authorisation.

  • On the other hand the "land monitoring study" is the process of understanding the land evolution through time and the effect of land policies on land. The full land use regulation (spatial plan) is not requested, only the graphic map is often required with some degree of simplification. Users are professionals such as land planners, geographers, and decision makers including the elected people.

B.2.2. Involved actors

image

B.2.3. Detailed description

Use Case Description

Name

Spatial planning documents

Priority

High

Description

Graphical representations of regulations that have a spatial extent, i.e. applicable to a piece of land, as well as facilities and constructions that pre-exist in the real world are needed to provide a map background for orientation and to understand spatial relationships.

It usually includes the representation of zoning elements, buffer zones around geographical objects that create restriction on neighbouring parcels as well as cadastral boundaries and topographic elements like e.g. hydrographical elements (surface waters), infrastructure, settlements, administrative units, geographical names, existing Land Use, etc.

One of the main purposes of maps is to communicate spatial information to the general public and/or experts in an understandable form and to support communication.

Pre-condition

Feature classification as reference data or defined rules to choose reference elements (features, dimensions).

Portrayal: Generalisation and symbol assignment rules for reference data and spatial planning related information

Another possibility could be to have a set of previous existing spatial plan as raster data.

Flow of Events – 1- Elaboration Path

Step 1.

Spatial planner request required geographical data from partners in order to create diagnostic map stating the current status of his area of interest, to devise scenarios for future development and to provide them to local government decision makers for comment

Step 2

Interested body to access proposed and preferred scenarios for future area development and provide comments

Step 3

Decision maker to provide selected development scenario for public hearing and interested parties in view of adopting final spatial plan that enter into force at a given date

Flow of Events – 2- entry into force Paths

Step 4

Landlords, mandated body, construction permit instructor to access enforced spatial plan in order to check compatibility between construction projects at a given address or on a given parcel and applicable regulation from the enforced spatial plan

Step 5

Any other interested body to access enforced spatial plans for spatial analysis

Step 6

Delivery of seamless and as far as possible harmonized requested spatial planning documents

Post-condition

Layers coming from different thematic DB must be merged into a seamless and harmonized way

Data source: Topographic Reference Data

Description

Topographic and cadastral reference data

There are 2 levels –or roles- in which topographical data are required:

Topographic data as a visual background. The aim is here to help locating any zone in its surrounding.

Topographic data as a tool for spatial analysis.

Data provider

Mapping and cadastral agency (national or local governments).

Geographic scope

Various (regional, local)

Thematic scope

Spatial information supporting orientation on maps and understanding of spatial relationships. The aim of topographic data is to help locate phenomena in its surrounding.

Scale, resolution

The scale of data depends on the spatial planning level. At the municipal level it ranges from 1:25 000 to 1:5 000. The data can be modelled in 2D geometry. There are no specific topological constraints on these data.

Delivery

GIS-Raster files, GIS-Vector-files

Documentation

Metadata

Data source: Thematic information

Description

Various sorts of thematic information such as census data, economic information

Data provider

Competent authorities including local governments

Geographic scope

Various (regional, local)

Thematic scope

Various (depends on the purpose)

Scale, resolution

Various (depends on the purpose)

Delivery

GIS-Raster files, GIS-Vector-files, GML-files, WFS

Documentation

Metadata, Model description

TWG

Affected

path

Datasets affected

Administrative Units (AU)

Yes

both

Boundaries of administrative units from the municipal to national borders, including geo-names.

Addresses (AD)

Yes

both

Address of entities

Area management/restriction/regulation zones and reporting units (AM)

Yes

both

Restriction zones
Regulation zones

Cadastral Parcels (CP)

Yes

both

Identification of properties

Coordinate reference systems

Yes

both

Local reference system enabling easy distance measurement

LandUse (LU)

Yes

both

residential areas / zones/districts // rural communities
industrial areas
agriculture
forest

Protected Sites (PS)

Yes

both

Ecologic landscape heritage

TransportNetwork (TN)

Yes

both

inland waterway (channels)
Roads
Railways

Orthoimagery (OI)

Yes

both

orthophotos
(Georeferenced) historical (ortho)photos

Agricultural and aquacultural facilities (AF)

Yes

1

with regards to adverse consequences for economic activities and environment (accidental pollution)
with regards to economic capacity

Bio-geographical regions Habitats and biotopes Species distribution (BR-HB-SD)

Yes

1

with regards to protection of the environment

Buildings

Yes

1

Contour, height, Use (e.g. agriculture, industrial, commerce, service, etc.)
Bridges, tunnels
levees, dikes, dams

Elevation (EL)

Yes

1

contour lines (lines that join points of equal elevation)
slope/hillside profile
fall/gradient of slope, base slope
coastline

Energy Resources

Yes

1

any

Geographical grid systems

Yes

1

Population density or similar coverage information

Geographical names (GN)

Yes

1

name of locations/areas

Geology Mineral resources (GE-MR)

marginal

1

geology: rock (Limestone, chalk, sandstone), Permeability
Landforms (geomorphology

Hydrography (HY)

Yes

1

Physical waters (watercourses, lakes)
dams

LandCover (LC)

Yes

1

All classes

Natural Risk Zones

Yes

1

Risk maps
Risk prevention plans

Production and industrial facilities (PF)

Yes

1

with regards to economic activities
with regards to economic assets

Statistical Units Population distribution, demography (SU-PD)

Yes

1

Census data (> population density etc.) and other population distribution data

Utility and governmental services (US)

Yes

1

Water supply
Sewerage system
Energy supply
Cable communication networks
Administration centres/infrastructure
Maintenance of supply and vulnerability

Soil (SO)

marginal

Permeability/Surface Sealing

B.3. Analysis of land consumption

B.3.1. Narrative description

The analysis of land consumption is required in many countries as the urban sprawl operates over the agricultural and natural areas. In some countries, municipalities will have to set objectives limiting the land consumption by urban area with mechanism to monitor the way the objectives are met. In the context of sustainable development where economic, social and environmental concerns are balanced, it is important to evaluate the justification of the land consumption by the urban sprawl. It is thus important to have knowledge of the existing land use and the area where the spatial plans project to open area for settlements and commercial or industrial activities and the like and for new communication links.

Urban sprawl is an intrinsic dimension of urbanization, which underlies the processes of spatial diffusion occurring in most developed countries. As modern cities become more complex also the phenomena of urban sprawl become increasingly faceted and diversified. One major aspect of novelty in the current trends is that sprawl does not only affect the use of land but has also an impact on the social, functional and economic spheres of urban life. It may also extend on different spatial levels, affecting not only cities and their surrounding areas but also whole metropolitan regions. Urban economists tend to examine urban sprawl as the aggregate extent of urban land use or as the average urban land use density. It has been shown that urban sprawl can increase the aggregate urban land use and lower the average land use density while at the same time lowering average commuting travel times and increasing discretionary mobility

In Europe several projects aim at detecting changes in existing land cover/use vector data (e.g. DeCOVER2 is a German project to develop algorithms in that area for updating the ATKIS-DLM digital landscape model of Germany, BNTK biotopes and land use map by the federal agency of environment in Germany). Remote sensing data is often used to do the change detection. Because the input and output datasets use different classifications interoperability knowledge on mapping between classifications using ontologies is required.

B.3.2. Involved actors

image

B.3.3. Detailed description

Use Case Description

Name

Land consumption mapping

Priority

High

Description

Land consumption monitoring enables to monitor the land parcels that change their usage. The issue is both to detect the changes and to understand for a given parcel from which usage it is turned into a new usage. It is thus an issue where comparison of land use maps over time at the parcel level is important.

Urban sprawl is considered acceptable when the rate of urban sprawling is similar to the population increase.

Pre-condition

Feature classification as reference data or defined rules to choose reference elements (features, dimensions).

Portrayal: Generalisation and symbol assignment rules for reference data and Land Use related information

Flow of Events – 1- Path

Step 1.

The user is requesting two existing land use datasets with their specific classification systems covering a given area but providing information at a different time. He may also requests recent orthophotos

Step 2

Based on the specific classification systems he groups the various classes into equivalent more generic classes as well as classes representing the urban nature of land use

Step 3

Applying the generic classes to each datasets and overlaying them on top of the orthophoto the user can then build a new dataset in which for each polygon the generic land use is attached at time T1 and at time T2. He can then produce a map and statistics showing how the land use has evolved between the two time slots. Based on the urban nature classes and the population information, the user can assess whether the area has been densified or sprawling regarding the change of population distribution and increase.

Post-condition

Layers coming from different thematic DB must be merged into a seamless and harmonized way

Data source: Land Use Data

Description

Existing land use data sets at two different dates are required. The scale range should be at the parcel level in order to draw an accurate urban extent. Key land classes must be considered such as agricultural use, forestry use, natural space, built-up area, etc.

Data provider

Mapping and cadastral agency (national or local governments).

Geographic scope

Various (regional, local)

Thematic scope

Land Use

Scale, resolution

For land consumption analysis the scale range is around 1:25.000, for the resulting urban sprawl map 1:100.000 may be preferred

Delivery

GIS-Raster files, GIS-Vector-files

Documentation

Metadata

Data source: Thematic information

Description

Population distribution and activity figures (such as local GNP measure or VAT figures)

Data provider

Competent authorities including local governments

Geographic scope

Various (regional, local)

Thematic scope

Various (depends on the purpose)

Scale, resolution

Various (depends on the purpose)

Delivery

GIS-Raster files, GIS-Vector-files, GML-files, WFS

Documentation

Metadata, Model description

TWG

Affected

Datasets affected

Administrative Units (AU)

Yes

Boundaries of administrative units from the municipal to national borders, including toponyms.

Buildings

Yes

Contour, height, Use

Cadastral Parcels (CP)

Yes

Identification of parcel limits

Elevation (EL)

Yes

slope/hillside profile

Geographical grid systems

Yes

Population density or similar coverage information

Land Cover (LC)

Yes

All classes

Land Use (LU)

Yes

residential areas / zones/districts // rural communities, industrial areas, agriculture, forest

Natural Risk Zones

Yes

Risk maps

Orthoimagery (OI)

Yes

orthoimages
(Georeferenced) historical orthophotos

Production and industrial facilities (PF)

Yes

with regards to economic activities

Protected Sites (PS)

Yes

Ecologic landscape heritage

Statistical Units Population distribution, demography (SU-PD)

Yes

Census data (> population density etc.) and other population distribution data

Transpor Network (TN)

Yes

inland waterway (channels), Roads, Railways, Bridges, tunnels

B.4. Ecological network map

B.4.1. Narrative description

Ecological network is a system of the most valuable sites, important for protection of threatened species, habitat types, ecological systems or landscapes. Ecological network sites must be relatively close to each other and connected with corridors, which allow them to communicate and exchange species.

In order for ecological network to function, all of its parts must be designated:

  • Core areas – areas with ecological conditions that enable preservation of important ecosystems, habitat types and species;

  • Corridors – features that connect core areas like "bridges", enabling species to migrate and communicate. There are 3 types of corridors:

    • Linear corridors – continuous elements distinctively different from the surrounding nature parts and not intensively used (rivers, tree lines, hedges etc.)

    • Landscape corridors – landscape belts connecting core areas

    • Stepping stone corridors – not continuous in structure but enabling ecological network to function (system of water habitat types important for migratory birds etc.)

  • Buffer zones – protecting ecological network from negative surrounding influences (pollution, drainage etc.);

  • Restoration areas – occasionally it is necessary to restore or re-establish degraded habitat types as parts of ecological network, in order for it to function

image

The legal basis of the ecological network programs includes

  • NATURA 2000 – Habitat Directive (Council Directive 92/43/EEC)

  • Emerald Network – The Convention on the Conservation of European Wildlife and Natural Habitats (Bern Convention)

  • National Ecological Network – national nature protection legislation

Ecological networks are structured hierarchically. That means its parts (core areas, corridors, buffer zones and restoration areas) can be distinguished on different levels: International, Regional, National, Local. Each part of the ecological network has a different role depending on the network level. For example, core areas of the local ecological network (small zoological reserve, forest etc.) can be only a part of the higher-level ecological network corridor.

The methodology for creating ecological network is based on the analysis of 'key' (usually threatened) species and habitat types distribution. Starting point for this analysis is a mapping process, which is best to be done using GIS technology. By overlapping species distribution maps, maps of habitat types and maps of protected areas, one can determine areas with highest density of priority species and habitats and evaluate those areas from the nature protection point of view. That way one can determine whether or not those areas are situated within existing boundaries of protected areas; if the boundaries of protected areas are appropriate for biological diversity protection or if they should be modified; if buffer zones around core areas are being created; if corridors for key species communication are being planned and eventually if restoration areas, where needed, are being established.

image

B.4.2. Involved actors

image

B.4.3. Detailed description

Use Case Description

Name

Ecological network mapping

Priority

High

Description

Determination of biodiversity reservoirs, corridors, buffer zones and restoration area

Pre-condition

analysis of 'key' (usually threatened) species and habitat types distribution. By overlapping species distribution maps, maps of habitat types and maps of protected areas, one can determine areas with highest density of priority species and habitats and evaluate those areas from the nature protection point of view.

Flow of Events – 1- Path

Step 1.

Determination of the biodiversity reservoirs (Forest environments, Xeric open habitats, Wetlands, Water bodies, Semi-extensive farming community, Coastal environments) and identification of corridors (agricultural areas and natural open space)

Step 2

Determination of geographical elements that fragment the corridors (built up areas, main linear transport network, dams) and determination of conflictual zones

Step 3

Identification of buffer zones (identifying the human pressure on land) and restoration area (area that require special attention to restore a more favourable condition for biodiversity)

Step 4

Mapping of the ecological network overlaid on a topographic elements and geonames

Post-condition

Layers coming from different thematic DB must be merged into a seamless and harmonized way

Data source: Land Use Data

Description

Existing land use data sets identifying the agricultural and forestry uses, and the usage that fragment the land (industrial area, services zones, residential area, networks) as well as the land not in use.

Data provider

Mapping and cadastral agency (national or local governments).

Geographic scope

Various (regional, local)

Thematic scope

Land Use

Scale, resolution

For ecological network analysis the scale range is around 1:100.000 for the a vision at regional scale that need to be taken into account in spatial planning documents at operational level,

Delivery

GIS-Raster files, GIS-Vector-files

Documentation

Metadata

Data source: reference information

Description

Topographic data

Data provider

Mapping agencies

Geographic scope

Various (regional, local)

Thematic scope

Various (depends on the purpose)

Scale, resolution

Various (depends on the purpose)

Delivery

GIS-Raster files, GIS-Vector-files, GML-files, WFS

Documentation

Metadata, Model description

TWG

Affected

Datasets affected

Elevation (EL)

Yes

slope/hillside profile
altitude

LandCover (LC)

Yes

All classes

LandUse (LU)

Yes

All classes

Production and industrial facilities (PF)

Yes

with regards to economic activities an pressure on the environment

Protected Sites (PS)

Yes

boundaries of protected areas appropriate for biological diversity protection

TransportNetwork (TN)

Yes

inland waterway (channels)
Roads
Railways
Bridges, tunnels

Agricultural and aquacultural facilities (AF)

yes

Area management/restriction/regulation zones and reporting units (AM)

yes

Bio-geographical regions Habitats and biotopes Species distribution (BR-HB-SD)

yes

Geographical names (GN)

yes

Hydrography (HY)

yes

B.5. Land Use and land-use change and forestry for greenhouse inventory reporting

B.5.1. Narrative description

This Use Case describes shortly the employment of National and International Land Cover and Land Use Changes databases, according to the obligations of UN’s FCCC[23] and Kyoto protocol, with the objective to calculate environmental indicators. LULUCF[24] is defined by the UN Climate Change Secretariat as "A greenhouse gas inventory sector that covers emissions and removals of greenhouse gases resulting from direct human-induced land use, land-use change and forestry activities".

Note: The term 'Land Use', here can be considered according to two Inspire themes: Land Cover and Land Use, because there is a mixture of land cover and land use concepts and terms in UN' FCCC and Kyoto protocol, especially when considering land 'use' changes categories.

Considering the different categories in land use and land use changes for GI according to IPCC[25], in each country it is necessary to select the most appropriate method for identifying and representing land areas as consistently as possible in inventory calculations. These categories and subcategories are described in the Good Practices guidelines for LULUCF and necessary for GHG[26] inventory reporting:

  • Forest land (F): All land with woody vegetation consistent with thresholds used to define forest land in the national GHG inventory, sub-divided into managed and unmanaged.

  • Cropland \(\C\): Arable and tillage land, and agro-forestry systems where vegetation falls below the thresholds used for the forest land category.

  • Grassland (G): Range lands and pasture land that is not considered as cropland. It also includes systems with vegetation that fall below the threshold used in the forest land category, without human intervention. It also includes all grassland from wild lands to recreational areas as well as agricultural and silvi-pastoral systems, managed and unmanaged.

  • Wetlands (W): Managed and unmanaged land that is covered or saturated by water for all or part of the year and that does not fall into the forest land, cropland, grassland or settlements categories. It includes reservoirs, rivers and lakes.

  • Settlements (S): All developed land, including transportation infrastructure and human settlements of any size.

  • Other land (O): It includes bare soil, rock, ice, and all unmanaged land areas that do not fall into any of the other five categories

And the subsequent subcategories defined for in Land Use Changes:

FF

forest land remaining forest land

LF

lands converted to forest land

GG

grassland remaining grassland

LG

lands converted to grassland

CC

cropland remaining cropland

LC

lands converted to cropland

WW

wetlands remaining wetlands

LW

lands converted to wetlands

SS

settlements remaining settlements

LS

lands converted to settlements

OO

other land remaining other land

LO

lands converted to other land

The way to proceed in each country will be (step by step)

  1. Choice of estimation method within the context of the IPCC Guidelines. Where three possible approaches can be identified, depending on availability and accuracy of National GI:

    • Use of Basic Land Use data, which can or can not cover the whole territory. It is recommended to have an account of the land data for the different Land Use categories, one for each reference year, but without further explanation of land use changes from one category to another. Only a global flow of gains and losses for each class can be estimated, but no inter-categories changes are identified.

    • Survey of Land Use and Land Use change provides a national or regional-scale assessment of inter-categories changes, not only gains and losses. Tracking land use changes in this explicit manner will normally require estimation of initial and final land use categories, as well as of total area of unchanged land by category. The final result of this approach can be presented as a non-spatially explicit land use change matrix.

    • Use of geographically explicit land use data. Approach 3 is comprehensive and relatively simple conceptually but data intensive to implement. The target area is subdivided into spatial units such as grid cells or polygons appropriate to the scale of land use variation and the unit size required for sampling or complete enumeration. The spatial units must be used consistently over time or bias will be introduced into the sampling. The spatial units should be sampled using pre-existing map data (usually within GIS[27]) and/or in the field and the land uses should be observed or inferred and recorded at the time intervals required. Observations may be from remote sensing, site visits, oral interviews, or questionnaires. Sampling units may be points or areas from 0.1 ha to a square kilometre or more, depending on the sample design. Units can be sampled statistically on a sparser interval than would be used for the complete coverage, chosen at regular or irregular intervals, and can be concentrated in areas where land use change is expected. Land Use recorded data could be at a point or within a sampling unit, but could also include land use change data within a sampling unit between the sampling years.

  1. LULUCF inventory compilation, according to the selected approach for each country. To estimate the land areas in each land use category for time period required, and with these values to assess which non-CO2 gases and carbon pools are significant, and prioritise such pools in terms of methodological choice. Obtaining as result a quantification of emissions and removals. There is abundant number of methods[28] to get these estimation values depending on LU categories and origin of changes, but as general approximation can be interpreted like product of covered surface by each LU category ij and rates of gains and losses.

image

  1. Quality assurance and quality control procedures to provide cross-checks during the inventory compilation. National inventories can have different level of precision, accuracy and levels of bias. Moreover, the estimates are influenced by the quality and consistency of data and information available in a country, as well as gaps in knowledge; the estimations can be affected by different sources of errors. It is good practice to execute quality control checks through Quality Assurance (QA) and Quality Control (QC) procedures. Agencies which collect data are responsible for reviewing the data collection methods, checking the data to ensure that they are collected and aggregated or disaggregated correctly, and cross-checking the data with other data sources and with previous years to ensure that the data are realistic, complete and consistent over time.

  1. Documentation of all data and information used, archived and reported to facilitate review and assessment of inventory estimates. Elaborations on pool definition should be reported, and definitions relevant to determining the extent of the managed land included in the inventory, together with evidence that these definitions have been applied consistently over time. Documentation is also needed for demonstrating completeness, consistency of time series data and methods for interpolating between samples and methods for interpolating between samples and years, and for recalculating, and avoidance of double counting as well as for performing QA/QC. The inventory should therefore include summaries of approaches and methods used, and references to source of data such that the reported emissions estimates are transparent and steps adopted in their calculation may be retraced.

  1. Quantification of uncertainties at the source or sink category level and for the inventory as a whole, so that resources available can be directed toward reducing uncertainties over time, and the improvement can be tracked.

In addition, GPG[29]-LULUCF provides guidance related to the specific features of the LULUCF sector on consistent representation of land areas, sampling for area estimates and for estimating emissions and removals, verification, and guidance on how to complement the Convention reporting for the LULUCF sector to meet the supplementary requirements under the Kyoto Protocol.

B.5.2. Involved actors

image

B.5.3. Detailed description

Use Case Description

Name

Use of LC and LU Changes data for Greenhouse Inventory Reporting obligations (UNFCCC & Kyoto Protocol)

Priority

High

Description

Employment of National and International Land Cover and Land Use Changes databases, according to the obligations of UN’s FCCC and Kyoto protocol, with the objective to calculate environmental indicators. LULUCF is defined by the UN Climate Change Secretariat as "A greenhouse gas inventory sector that covers emissions and removals of greenhouse gases resulting from direct human-induced land use, land-use change and forestry activities".

Pre-condition

Flow of Events – Basic Path

Step 1

Choice of estimation method

Step 2

LULUCF inventory compilation

Step 3

Quality assurance and quality control procedures

Step 4

Documentation

Step 5

Quantification of uncertainties

Data source: National LC/LU databases or inventories

Description

National Land Cover & Use, Forest, Crops Inventories; Agricultural and Forest Surveys

Data provider

Mapping Agencies, National Forest & Agriculture Institutions, NRC on Land Cover, NRC on Land Use & Spatial Planning.

Geographic scope

Global, National

Thematic scope

Land Cover, Land Use

Scale, resolution

1:100.000 to 1:10.000; MMU from 0,1 to 1 ha.
No geospatial information can be also managed, if theirs statistics are addressed to admissible administrative units for LULUCF computing and the accuracy principles are assured.

Delivery

Documentation reports

Documentation

Good Practice Guidance for Land Use, Land Use Change and Forestry
http://www.ipcc-nggip.iges.or.jp/public/gpglulucf/gpglulucf.html

B.6. Other use cases

B.6.1. Land Use for environmental impact assessment

An environmental impact assessment (EIA) is an assessment of the possible impact—positive or negative—that a proposed project may have on the environment, together consisting of the natural, social and economic aspects. The International Association for Impact Assessment (IAIA) defines an environmental impact assessment as "the process of identifying, predicting, evaluating and mitigating the biophysical, social, and other relevant effects of development proposals prior to major decisions being taken and commitments made."[30][1]. The International Organization for Standardization (ISO) Standard 14011 covers EIA and includes key steps for carrying out the assessment. As well as direct effects, developments cause a multitude of indirect effects through consumption of goods and services, production of building materials and machinery, additional land use for activities of various manufacturing and industrial services, mining of resources etc.

B.6.2. Land Use for the flood directive

The Floods Directive will be implemented by Member States at the level of River Basin districts/units of management as follows:

  • Art 4-5 (Preliminary Flood Risk Assessment) – provide maps of the river basin district at the appropriate scale including the borders of the river basins, sub-basins and, where existing, coastal areas, showing topography and land use (main classes);

  • Art 6 (Flood hazard and risk maps). Part of assessment and part of reporting. Maps to be produced at "the appropriate level", according previous assessment maps. Identifying: floods probability, flood extension and inhabitants affected

  • Art 7 – Flood risk management plans. Land Use to be taken into account. Measures could include: changed land use, spatial planning measures, set aside of lands

The floods directive requires data on the Existing Land Use relevant for identifying the stakes existing in the risks area, planned land use relevant for potential future stakes (art 4, 5 and 6) and management of risk (art 7). Flood risk management plans and maps may include zoning information but that may differ in member states. No minimum size is fixed. No European LU classification exists for the moment, and it will depend on MS national data.

Requirements include different types of economic activities (referring to NACE or national correlated equivalent codes), knowledge of areas used for flood water storage (temporarily used, permanently set aside for this purpose) and transport routes. Hydrography may include temporarily dry water courses.

For modelling purposes the complete Land Use coverage in a single layer is required (i.e. no overlaps, no gaps, no missing or duplicate polygons).

Temporal information such as the period of the land use plan is required. Land Use changes are useful information for modelling (for example to assess if there is a need to update results derived from modelling and associated risk maps etc.). In terms of degree of dependence it’s important to know the actuality of features (date of last update or date its represent the reality).

There is a requirement to relate Land Use elements to potential significant flood risk areas, flooded areas, flood extent areas included in flood maps and planned flood measures.

An identifier would be helpful, for example it should enable to identify which objects from detailed Land Use datasets (provided by mapping agencies) are aggregated to/are part of or are represented by which object(s) in less detailed Land Use dataset like CORINE Land cover.

Consistency with other themes such as Utility and Government Services, Production and Industrial Facilities, Agricultural and Aquaculture Facilities, Transport, Area management/restriction/regulation zones and reporting units should be achieved

Differentiating existing Land Use (that exists in reality) from the Planned Land Use (the one authorities are planning to develop) is required. In preliminary assessment of flood risk by determination of areas exposed to flood risk, the impact of future changes in land use in regional scale is taken into consideration in order to evaluate the potential increase/decrease of flood risk.

On flood hazard maps 8 categories of land use elements may be defined: "residential, industrial, communication, forests, parks and recreation, agricultural, water bodies, other". Two additional categories are required : buildings and address points.

The most wanted attribute is the number of people on specific area.

B.6.3. Statistics for land use

Regulation (EC) No 223/2009 of the European Parliament and of the Council of 11 March 2009 on European statistics constitutes the legal basis for the preparation of the European statistical programme, providing the framework for the development, production and dissemination of European statistics, the main fields and the objectives of the actions envisaged for a period not exceeding five years. The current programme covers the period 2008-2012. It was established by the Council Decision 1578/2007/EC of 11 December 2007. The five-year programmes are backed up by annual programmes that set more detailed objectives for each year. The following actors are involved: Eurostat (the Statistical Office of the European Commission), (Data provider, data co-ordinator, data user), DG Environment (Data user), DG Agriculture (Data User), DG Enterprise (Data user), European Environment Agency (Data user), Other European Commission services (Data user).

Eurostat collects land cover/use data mainly through the LUCAS survey, which is directly implemented by Eurostat. LUCAS stands for Land Use and Cover Area frame Survey. The aim of the LUCAS survey is to gather harmonised data on land use/cover in the EU countries. In addition the survey provides in-situ information facilitating the analysis of the interactions between land, environment and human activities. In the 2008/2009 LUCAS survey 265,000 geo-referenced points were visited by more than 500 field surveyors on the spot. The points were selected from a standard 2 km grid including in total around 1 million points all over the EU. Land cover and use data is collected from each point according to the LUCAS nomenclature, which consists of a separate land cover nomenclature and of a separate land use nomenclature. In addition the LUCAS database contains approximately 1 million landscape photos and data on agro-environmental features. The final database consists of all surveyed variables on all points. Harmonised land cover and land use statistics are based on this dataset. The data and results are published on Eurostat website and widely used by many Commission services. Eurostat also attempts to collect land cover/use data directly from the Member States. Due to different definitions, classification systems and nomenclatures in the 27 EU Member States this requires a lot of preparatory work in the field of definition and data harmonisation. This is the area where Eurostat will work intensively in the future.

B.6.4. Land Use for soil management

Soil is defined as the top layer of the earth’s crust. It is formed by mineral particles, organic matter, water, air and living organisms. It is in fact an extremely complex, variable and living medium. The interface between the earth, the air and the water, soil is a non-renewable resource which performs many vital functions: food and other biomass production, storage, filtration and transformation of many substances including water, carbon, nitrogen. Soil has a role as a habitat and gene pool, serves as a platform for human activities, landscape and heritage and acts as a provider of raw materials. These functions are worthy of protection because of their socio-economic as well as environmental importance.

Erosion, loss of organic matter, compaction, salinisation, landslides, contamination, sealing…​ Soil degradation is accelerating, with negative effects on human health, natural ecosystems and climate change, as well as on our economy. At the moment, only nine EU Member States have specific legislation on soil protection (especially on contamination).

The Commission adopted a Soil Thematic Strategy (COM(2006) 231) and a proposal for a Soil Framework Directive (COM(2006) 232) on 22 September 2006 with the objective to protect soils across the EU. The Strategy and the proposal have been sent to the other European Institutions for the further steps in the decision-making process. The proposed Directive will require Member States to identify risk areas on the basis of common elements to be taken into account, set risk reduction targets for those areas and establish programmes of measures to achieve them.

image

On the basis of a common definition of contaminated sites (i.e. sites which pose significant risk to human health and the environment), its application by the Member States, and a common list of potentially polluting activities, Member States will be required by the proposed directive to identify the contaminated sites on their territory and establish a national remediation strategy. In order to achieve a more rational use of soil, Member States will be required to take appropriate measures to limit sealing by rehabilitating brownfield sites and to mitigate its effects by using construction techniques that allow maintaining as many soil functions as possible.

Despite the efforts of several Presidencies, the Council has so far been unable to reach a qualified majority on this legislative proposal due to the opposition of a number of Member States constituting a blocking minority. In general terms, a majority of delegations support a Framework Directive on soil protection. They hold the view that it is needed in order to fill a gap in Union environmental legislation and to provide a more holistic approach to soil protection. This view is also upheld by the Commission. Several delegations, however, remain highly critical of the proposed Directive. These delegations oppose the proposal on grounds of the subsidiarity and proportionality principles, expected costs and administrative burden. Furthermore, they question its added-value in relation to existing Union law.

As far as land use is concerned, erosion, sealing and contaminated sites determination may require knowledge of the Existing Land Use at different time period.

B.7. Existing land use data requirements

The first step while designing data specifications or products is to identify the final users and their real requirements and needs. These should act as rules during the design phase because they will guarantee the final result usefulness.

The following chapter provides a set of requirements as derived from the INSPIRE users' information collection enriched with experiences gathered in the requirements repository of the ICT PSP HLANDATA project, from a modelling and data specification redaction point of view.

The main objective of the HLANDATA project was to demonstrate the feasibility of a European level harmonization of Land Use and Land Cover datasets taking into account both the data categorization and the data models, for any of their possible uses and users, through the development of user oriented value-added services. After the evaluation and comparison of users' information from HLANDATA project and INSPIRE, the results affirm that both initiatives share a similar users understanding and framework. HLANDATA users' requirements involve tasks carried out in the documented INSPIRE uses cases. This last section deals with HLANDATA requirements' collection and offers more detailed results about real users' preferences.

B.7.1. Features

Most of the use cases require a complete coverage of the area of interest with information regarding the use of land. The concept of dominant land use for each piece of land is acceptable although it may be often required to have information on other possible land uses. It is often required to identify the land use components over a user-defined area which has no connection to the limits of homogeneous land use area.

The intensity of use is also very important for many use cases in order to evaluate the human pressure on the environment (i.e. residential human density, intensity of crops production, etc.).

About scopes covered by data demanded by users, there is a preference for natural areas potentially regulated by environmental plans or risk zones, such as wetlands, waters or river shores.

Land Use and Land cover are nonetheless concepts on which the use cases have difficulties to differentiate. It comes from the actual databases where both concepts are mixed. INSPIRE Land Cover and Land Use data specification must reflect the independence between land use and land cover, but must not impose new data production.

Level of detail or minimum mapping unit (mmu) in existing land use data sets plays a crucial element for the data usability. Users choose or reject information based on it. After analysis it have been extracted that this factor also is related with the typology of user. Organizations with National territory competence requires data at around 1:25.000 scale (mmu 2ha), meanwhile Regional or Local institutions prefer more accurate data at around 1:5.000 scale (mmu 0.5ha).

For modelling purposes the complete land use coverage in a single layer is required (i.e. no overlaps, no gaps, no missing or duplicate polygons).

There is a requirement to relate land use elements to other geographical objects that are visible in the reality but it is seldom required to implement geometric relationships with these objects.

B.7.2. Nomenclature

No commonly agreed nomenclature has been identified during the use case analysis. Nonetheless there is a practical agreement to use a multi-level hierarchical nomenclature separating the land use from land cover. There is a requirement to refer to different types of economic activities (referring to NACE or national correlated equivalent codes).

Alternative modelling taking account more than one presence of land use category per piece of land (object oriented philosophy) is considered complex as a unique harmonization methodology.

B.7.3. Temporal dimension

Temporal information is often quoted as an important issue to be dealt with. Comparing the existing land use through time is important and raises the issue of solving inconsistencies between the respective geometries of LU data sets over the same area but at different dates (how to deal with slivers?). It has been thought that the issue needs to be solved either at the producer level (e.g. in providing existing land use datasets based on a stable geometric delineation of polygons) or at the user level in his information system (e.g. in considering the respective positional accuracy of the datasets.

A dataset providing only changes in land use between two dates has not been required by the analyzed use cases.

After a review of required update frequency, most of the users asked for a high updating frequency for land use databases because currently there are many land inventories that undertake yearly updates.

B.7.4. Quality control

It has been recognised that the issue needs to be solved either at the producer level (e.g. in providing existing land use datasets based on a stable geometric delineation of polygons) or at the user level in his information system (e.g. in considering the respective positional accuracy of the datasets

B.7.5. Identifiers

Identifiers would be helpful, for example they should enable to identify which objects from detailed Land Use datasets are aggregated to/are part of or are represented by which object(s) in less detailed Land Use dataset like CORINE Land Cover.

B.7.6. Portrayal

A consistent portrayal for Existing Land Use is often quoted as useful in case of visualisation of adjacent datasets provided by different producers, preferably based on a harmonized land use nomenclature for the entire Europe..

B.7.7. Metadata

Normal metadata are required such as who produced the data set, when and for what purpose, date of recording (remote sensing data) respectively date of data collection (surveying and mapping), etc. Metadata at feature level might be useful but it has been thought difficult to implement it in the proposed data specification.

In terms of degree of dependence it’s important to know the actuality of features (date of last update or date representing the reality).

B.7.8. Consistency with other themes

The consistency with other INSPIRE themes such as land cover, Utility and Government Services, Production and Industrial Facilities, Agricultural and Aquaculture Facilities, Transport, Area management/restriction/regulation zones and reporting units is important. But it seems that the models should not implement relationships between existing land use polygons and the geographical objects of other themes as the link can be computed using the geometry. Also the same geometry from National databases can serve to several INSPIRE data themes, for example a polygon in a National LC/LU database could be used for both INSPIRE themes.

B.7.9. Detailed user’s assessment from HLANDATA project

The first step of the HLANDATA project dealt with the assessment of the current European situation regarding the harmonization of the Land Cover and Land Use data. An assessment of the end users and their needs from the point of view of data harmonization was carried out [31]. In detail users' assessment report includes the catalogue of user requirements, involving information recompilation about: general and basic information about the user (i.e competence area, thematic ambit, legal frame, typology, etc.); current used databases and aspects related with acquisition, utilization, satisfaction or dissemination of data; current used webservices, distinguishing between type and frequency of service; and a detailed list of needed data.

Al project partners where requested to be involved in the collection through their particular knowledge of users and used databases in their countries. To obtain these information, a set of questionnaires were elaborated in order to gather all the information needed to carry out the LC/LU users assessments. Each questionnaire were filled by each partner as they were the only ones aware of the inside of the project. Due to the characteristics and level of detail of the forms, they had to be completed in close communication with involved users, via meeting or via telephone. All partners collaborated with questionnaires, so a global European overview was reached from national study evaluations, following bottom-up dimensioning.

As a summary of Requirements Inventory some key comments are given in the following. Analysed organizations can demand more than one requirement; especially there are organizations with 5-8 items and others with only 1 or 2, to reach a total of 216 needs. A better way to understand each concrete interest is to review numeric reports over filled questionnaires, and an overview on themes, frequency of update, scales or minimum mapping unit can be done to extract general considerations.

In a general view, Environmental lands predominate, 23 Wetlands (10,65%) and 23 Forests (10,65%); together with 20 Settlements (9,26%). The frequency for update required for users of 1 year (107, i.e. 49,54%). Concerning geometric aspects, the demanded scale is 1:25.000 for 113 cases (52,31%) and the minimum polygon size is 1 ha (89 i.e. 41,2%), vector information is the most commonly used (118 i.e. 54,63%) and shapefile the preferred format (106 i.e. 49,07%). Regarding land categories needed for the users in the catalogue the main groups of land type, which are mostly required, are given in the following table:

Land Theme

Users requiring

Update frequency (years)

Scale

MMU

Forest / Unique trees / Vegetation / Riverbank formation / others

13 / 1 / 1 / 2 ; and more

1 to 5, but mostly 1

1.25.000 (mostly) to 1:5.000

0,1 to 2,5 ha

Waters / Rivers / Hydrography resources / Water treatment plants / Hydrography / others

10 / 1 / 1 / 1 / 2 ; and more

1 to 5, but mostly 1

1.25.000 (mostly) to 1:5.000

2 to 0,5 ha

Settlements / Urban areas/ Artificial areas / others

9 / 3 / 6 ; and more

1 to 5, but mostly 1

1.25.000 (mostly) to 1:5.000

2 to 0,5 ha

Croplands / Agricultural areas / Irrigated crops / others

9 / 5 / 4 ; and more

1 to 5, but mostly 1

1.25.000 (mostly) to 1:5.000

2 (mostly) to 0,5 ha

Grasslands / others

8

1 year

1.25.000 (mostly) to 1:5.000

2 to 0,5 ha

Natural areas / others

3

2 to 5

1.25.000

2 ha

Table of required land information by users

B.8. Planned land use data requirements

B.8.1. Features

The use case imply to have access to the zoning elements and the areas where supplementary regulation that are present in spatial plans, as well as a graphic map that indicates on which area the plan is applied and the textual planning requirements. Geometric delimitation of zoning elements and supplementary regulation is given by spatial plan requirements, not by mapping rules.

When converted into a vector format, the requirements include the following layers:

  • A geometrically accurate polygon layer with polygons that are collectively exhaustive and mutually exclusive (over the area that is mapped), provides the information on zoning. Each polygon has an attribute which refers to the text of the zoning regulation. A direct link to the pdf-file may be available.

  • A geometrically accurate polygon layer, with possible overlapping geometry provides information on restrictions that affect land areas. Each polygon has an attribute which refers to the text of the constraint regulation. A direct link to the pdf-file may be required

  • A geometrically not accurate polygon layer provides complementary information on projected areas

  • A geometrically accurate line layer provides information on existing line infrastructure such as roads, railways

  • A geometrically not accurate line layer provides information on projected line infrastructure with its exact position being not yet known

  • A geometrically accurate point layer

  • A geometrically not accurate point layer

  • A polygon layer with the contour of the whole plan

  • A polygon layer with the contour of parts of the plan

In most of the European countries old plans are not always converted into polygon features. These plans are however (or most of them) required as a geo-referenced raster image.

Information on the step reached by the spatial planning process is often required, e.g. when a new plan has been ratified by the appropriate authority, when a plan has replaced another or when updates due to other reasons need to take place, or if a new plan is under preparation, scrutiny or approval.

B.8.2. Nomenclature

Some European countries have their national nomenclature for Planned Land Use, but for many of them, the nomenclature is standardised at the regional or municipal level. Examples of nomenclatures are provided in Annex C.

B.8.3. Temporal dimension

Temporal information is often required. Land predestinations and post destinations can be allocated to land portion, that is why overlapping polygons are required

B.8.4. Identifiers

A general unique code for each article of the textual regulation is requested, enabling to assign with no ambiguity which regulation apply on which polygon of the zoning. Identifiers for each polygon are not necessary.

B.8.5. Quality control

Stable geometric delimitation should be guaranteed in the spatial plan definition by competent planer administration.

B.8.6. Portrayal

A non geo-referenced legend file (tiff or pdf) must be exchanged for each plan, which enumerates all the used symbols on the plan and their title. For getting more detailed information on the meaning of the symbol set the textual part itself has to be consulted.

B.8.7. Metadata

Each individual plan must have a metadata fiche. This gives information about the contents, origins, projection system and quality.

B.8.8. Consistency with other themes

In case expropriation of owners of certain parcels, the exact parcel number and address is required.

Other rules and regulations that apply to that zone need to be considered with the zoning plan (Area management/restriction/regulation zones and reporting units).

Annex C: Code list values - (normative)

INSPIRE Application Schema 'Land Use Nomenclature'

Code List

HILUCSValue

HILUCSValue

Name:

HILUCS value

Definition:

List of land use categories to be used in INSPIRE Land Use and agreed at the European level.

Description:

This list is populated with the land use categories of the Hierarchical INSPIRE Land Use Classification System (HILUCS).

The elements of the list should be both applicable to existing land use and planned land use.

Extensibility:

none

Identifier:

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

Values:

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

INSPIRE Application Schema 'Planned Land Use'

Code List

LevelOfSpatialPlanValue

ProcessStepGeneralValue

RegulationNatureValue

SupplementaryRegulationValue

LevelOfSpatialPlanValue

Name:

level of spatial plan

Definition:

Territorial hierarchy of plan.

Extensibility:

none

Identifier:

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

Values:

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

ProcessStepGeneralValue

Name:

process step general

Definition:

General indication of the step of the planning process that the plan is undergoing.

Description:

NOTE This enumeration contains values that are common to most planning systems.

Extensibility:

none

Identifier:

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

Values:

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

RegulationNatureValue

Name:

regulation nature

Definition:

Legal nature of the land use indication.

Extensibility:

none

Identifier:

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

Values:

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

SupplementaryRegulationValue

Name:

supplementary regulation value

Definition:

Types of conditions and constraints in spatial plans.

Description:

This list is populated with the categories of the Hierarchical Supplementary Regulation Code List (HSRCL).

Extensibility:

any

Identifier:

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

Values:

The allowed values for this code list comprise any values defined by data providers. The INSPIRE Registry includes recommended values that may be used by data providers. Before creating new terms, please check if one of them can be used.

Annex D: Towards the Hierarchical INSPIRE Land Use nomenclature - (informative)

In order to determine the nomenclature that should be used in the data specifications of the INSPIRE theme land use several existing nomenclatures have been reviewed to evaluate if it is possible to adopt one of these existing nomenclatures or whether it is necessary to make a new one. The difficulty in composing a nomenclature for land use is the fact that the INSPIRE theme deals with two different views on land use; one deals with the existing land use including from a statistical point of view, while the other deals with the future land use from a planners point of view. This means that besides deciding which nomenclature should be used; there is also a decision about whether or not the same nomenclature for both types of land use should be adopted.

The list of nomenclatures below is not meant to be exhaustive. The choice of investigated nomenclatures is solely based on the fact that these nomenclatures were known by the members of the TWG or provided as reference material. For each classification system the main categories are mentioned to enable comparison.

D.1. Investigated classification systems

A.1.1 ISIC Rev.3 (International Standard Classification of All Economic Activities)

The ISIC classification was drawn up by the United Nations (approved by the Statistical Commission in 1989) and recommended for use throughout the world. The ISIC is intended to be a standard classification of productive economic activities. This classification is integrated in the sense that it ensures a full harmonization with another main branch of economic classifications: the classifications of products (ICPC Central Product Classification) which are fundamental for foreign trade statistics, statistics of production and consumption, energy statistics, etc. The ISIC classification may therefore be appropriate to characterise land use percentages for administrative units. The ISIC Rev. 3, is fully compatible with the EU NACE Rev. 1 (Nomenclature des Activités de la Communauté Européenne) system for the first two levels. (System replaced by 1.1.2008, see references). The ISIC Rev.3 uses 4 levels of classification: 17 sections, which are further divided into 62 divisions. The third level consists of groups, while the fourth level is further divided into classes.

The ISIC system is however not in use within the spatial planners community mainly because it does not provide entries for "residential area", "recreation areas", "mix residential-activity area" that are common in spatial planning documents.

SECTION A

Agriculture, Hunting and Forestry

SECTION B

Fishing

SECTION C

Mining and Quarrying

SECTION D

Manufacturing

SECTION E

Electricity, Gas and Water Supply

SECTION F

Construction

SECTION G

Wholesale and Retail Trade, Repair of motor vehicles, motorcycles and Personal and household goods

SECTION H

Hotels and Restaurants

SECTION I

Transport, Storage and Communication

SECTION J

Financial intermediation

SECTION K

Real estate, Renting and Business activities

SECTION L

Public Administration and Defence, Compulsory social security

SECTION M

Education

SECTION N

Health and Social work

SECTION O

Other Community, Social and Personal Service Activities

SECTION P

Private Households with Employed Persons

SECTION Q

Extra-territorial Organizations and Bodies

D.1.1. LUCAS (Land Use / Cover Area Frame Survey)

The LUCAS nomenclature used to be applied for surveys focused on agriculture. Since 2008 the scope has been enlarged to land cover/use in general. The main aim of the LUCAS survey is to gather harmonised information on land use/cover and their changes over time. In addition the survey provides territorial information facilitating the analysis of the interactions between agriculture, environment and countryside. The LUCAS nomenclature has separate classification systems for land cover and land use. Land cover is defined as the physical cover of the earth’s surface and land use is the socio-economic function of the land.. Land Use has 15 main categories. It has altogether 34 classes, which are indicated by the combination of the letter "U" and three digits. The same nomenclature is applied in all EU countries in the LUCAS survey. It also allows comparisons in time (since LUCAS 2006 survey). It is as much as possible compatible with the existing land cover/use systems (e.g. FAO, NACE and Farm Structure Survey).

The LUCAS classification is used for statistical purposes and is therefore more difficult to adopt for planned land use. The biggest problem seems to be the lack of mixed land uses.

U110

AGRICULTURE

U120

FORESTRY

U130

FISHING

U140

MINING AND QUARRYING

U210

ENERGY PRODUCTION

U220

INDUSTRY AND MANUFACTURING

U310

TRANSPORT, COMMUNICATION NETWORKS, STORAGE, PROTECTIVE WORKS

U320

WATER AND WASTE TREATMENT

U330

CONSTRUCTION

U340

COMMERCE, FINANCE, BUSINESS

U350

COMMUNITY SERVICES

U360

RECREATION, LEISURE, SPORT

U370

RESIDENTIAL

U400

UNUSED

D.1.2. Urban Atlas

The Urban Atlas is providing pan-European comparable land use and land cover data for Large Urban Zones with more than 100.000 inhabitants as defined by the Urban Audit. The GIS data can be downloaded together with a map for each urban area covered and a report with the metadata.

Earth observation data are the basis for interpretation. Topographic maps in digital form with precise geo-coding are used for interpretation of objects. Application of automatic classification routines, as segmentation and clustering are applied whenever appropriate: Automated segmentation and classification to achieve a first differentiation into basic land cover/land use classes (urban vs. forest vs. water vs. other land cover/land use).

The Urban Atlas nomenclature mixes land use classes with land cover classes. It has a hierarchical nature.

1

Artificial surfaces

1.1

Urban fabric

1.1.1

Continuous Urban fabric (soil sealing >80%)

1.1.2

Discontinuous urban fabric

1.1.2.1

Discontinuous dense urban fabric (soil sealing 50% - 80%)

1.1.2.2

Discontinuous medium urban fabric (soil sealing 30% - 50%)

1.1.2.3

Discontinuous low urban fabric (soil sealing 10% - 30%)

1.1.2.4

Discontinuous very low urban fabric (soil sealing <10%)

1.1.3

Isolated structure

1.2

Industrial, commercial, public, military, private and transports units

1.2.1

Industrial, commercial, public, military, private units

1.2.2

Road and rail network and associated units

1.2.2.1

Fast transit roads and associated land

1.2.2.2

Other roads and associated land

1.2.2.3

Railways and associated land

1.2.3

Port areas

1.2.4

Airports

1.3

Mine, dumps and construction sites

1.3.1

Mineral extraction and dump sites

1.3.3

Construction sites

1.3.4

Land without current use

1.4

Artificial non-agricultural vegetated areas

1.4.1

Green urban areas

1.4.2

Sport and leisure facilities

2

Agricultural areas, semi-natural areas and wetlands

3

Forests

4

Water

D.1.3. Plan4All

Plan4all is a European project co-funded by the Community programme eContentplus. The main aim of the project is to harmonise spatial planning data and related metadata according to the INSPIRE principles. The aim of work package 4 is to define data models for several INSPIRE themes including land use. First of all they have compared several different models from different countries. The second step was to make an overall data model including classifications. The data model for land use uses four different classifications: 'LUCAS', 'MacroClassificationOfLand, 'GeneralLandUseType and 'SpecificLandUseType'. 'LUCAS' uses the LUCAS classification, and the 'specific land use type' uses the classification used in each country/region. This classification should (if used) be uploaded into the model.

The Plan4all model is based on land use form a planner’s point of view, so it is less useful for the existing land use. Besides this it is also a complicated model with a lot of detailing.

Macroclassification:

Urbanised

ToBeUrbanised

Rural

Natural

Other

GeneralLandUseType:

Residential

IndustrialCommercial

ServicesOfGeneralInterest

Green

AreasOfNaturalInterest

Agriculture

Water

RoadTrafficInfrastructure

RailwayTrafficInfrastructure

OtherTrafficInfrastructure

SpecialDevelopmentZone

Mining

Quarrying

TechnicalInfrastructure

Other

D.1.4. FR-CNIG – Plan local d’urbanisme – Plan d’occupation des sols

The standard aims at defining a standard way of converting spatial planning documents at the parcel level into a digital form. It defines a nomenclature of planned land use that is applicable by all local governments. A fist version was finalised in 2006 and updated in 2010. The approach is significantly different to the approaches such as LBCS, NLUD or LUCAS as it provides a nomenclature for planned land use.

Two levels are defined:

  • a "simplified zone type" with only 5 main classes (built-up area, to be built-up area (divided into two sub-classes), agriculture area, natural area, natural area that can be built-up (divided into two sub-classes)

  • the dominant vocation of the area divided into 11 classes (not applicable, residential, activity, residential/activity mix, leisure and tourism, amenities, agriculture activity, natural space, remarkable space, quarrying, other)

The standard also provides a nomenclature for prescriptions that are superimposed on land-use area providing supplementary regulations on the possibility to change land-use. 25 categories are provided (e.g. classified woodland, sector with provision of reconstruction / demolition, specific limitation for building implementation, placeholder, area with development guidelines, etc.)

D.1.5. NL-BBG – Bestand Bodemgebruik

Since the 1940’s the statistics department of The Netherlands is periodically compiling an overview of the land use in The Netherlands. The geometry is based on the topographical map. The functional classification is made up out of two levels.

The classification seems to be quite generic, grouping residential areas, service oriented areas and industry into one category of built-up area. BBG also gives great attention to the main class of water.

1

Transport

2

Built-up area

3

Semi built-up area

4

Recreation

5

Agriculture

6

Woodland and nature

7

Inland water

8

Tidal waters

9

Foreign countries

D.1.6. UK-National Land Use Database: Land Use and Land Cover Classification

The NLUD classification is intended to provide in the United Kingdom a framework for harmonising existing classifications, to facilitate consistent collection and reporting of land use and land cover information, and to provide the basis for the creation of national data sets. It has been designed to serve as a standard classification available for adoption by bodies involved in the routine collection of land use and land cover data. NLUD definition of Land Use: "land use relates to the activity or socio-economic function for which land is used". An interesting aspect that is mentioned is 'mixing' or 'different combination of classes', which is divided into three different types: two dimensional (juxtaposition), three dimensional (superposition) and temporal. That implies a more complicated data model, may be using an object oriented data model, to assign different classes to polygons or parcels. This nomenclature uses a two-tier approach with the possibility to add third level tiers at local level.

This approach is similar to the LUCAS classification. It is also mainly used for statistical purposes and is therefore more difficult to adopt for planned land use. The biggest problem seems to be the lack of mixed land uses.

U010

U110 AGRICULTURE

U120

FORESTRY

U130

AQUACULTURE AND FISHING

U140

MINING AND QUARRYING

U210

ENERGY PRODUCTION

U220

INDUSTRY AND MANUFACTURING

U310

TRANSPORT, COMMUNICATION NETWORKS, STORAGE, PROTECTIVE WORKS

U320

WATER AND WASTE TREATMENT

U330

CONSTRUCTION

U340

COMMERCE, FINANCE, BUSINESS

U350

COMMUNITY SERVICES

U360

RECREATION, LEISURE, SPORT

U370

RESIDENTIAL

U400

UNUSED AND ABANDONED AREAS

D.1.7. US-LBCS (Land-Based Classification Standards)

In 1994, the American Planning Association (APA) reported on the findings of a survey of federal, state, regional, and local needs for an updated land-use classification standard in USA. Then, in May 1996, APA, along with the participation of six other federal agencies, initiated the Land-Based Classification Standards (LBCS) project. Through this project, APA and its partners produced a new land classification system to allow jurisdictions, agencies, and institutions at the local, regional, state, and national level to share land-based data. The first version of LBCS was released in 2000, and the standards have been updated periodically in the intervening years. The model extends the notion of classifying land uses by refining traditional categories into multiple dimensions. The 5 dimensions are: activity, function, structure, site and ownership. Each dimension has its own set of categories and subcategories, giving in total the possibility to use up to 4 levels of detail. These multiple dimensions allow users to have precise control over land use classifications

LBCS is an interesting model for land use classification. Because of the different dimensions a very detailed and accurate picture of the actual land use can be made. This provides the advantage of flexibility (one of the recommendations in D2.6) for the Member States to adapt to the data specifications. They will then have the choice which (combination) of dimensions they want to use or are compliant to their own data model. The dimension 'function' would be the most important (and maybe also most easy) to use because it is more similar to nomenclatures used by land use planners and also similar to the nomenclatures of LUCAS. It could therefore be an option to make this dimension mandatory and the other ones optional. On the other side of the coin, INSPIRE implementation rules should be careful in providing models that are too detailed or to complex to implement for the member states. As no new data will be collected by the Member States to be compliant with the data specifications, it is assumed that existing data will be transformed to the general model. LBCS model is a bit confusing and not simple in use.

Overall there is too much detail and the whole system is too complex.

1000

Residence or accommodation function

2000

General sales or services

3000

Manufacturing and wholesale trade

4000

Transportation, communication, information and utilities

5000

Arts, entertainment and recreation

6000

Education, public administration, health care and other institution

7000

Construction-related business

8000

Mining and extraction establishments

9000

Agriculture, forestry, fishing and hunting

D.2. Conclusions

For the INSPIRE Land Use theme it is desirable to work with one nomenclature for both the existing and the planned land use. For this reason it has been chosen to start from the LUCAS nomenclature, since this is the most widely spread used nomenclature and other classifications can be matched to the LUCAS classes. The Plan4All workgroup has also advised in its data model the use of LUCAS as one of the classifications. As stated above however there remains the difficulty of mixed zones for planned land use. This problem could be avoided if new classes would be added to the LUCAS nomenclature for the use in the INSPIRE land use theme. The TWG advises to adopt a hierarchical land use classification system for INSPIRE. It is further developed from the LUCAS classification and clearly more hierarchical.

The advantage of using the same nomenclature for both the existing and planned land use would be that it is possible to make comparisons between different years and between present and future. This comparison between existing and planned land use is not to be confused with temporal dimension: planned is the expected or foreseen land use (to be built), while existing is the real land use (past or present). The planned land use may not always become the existing land use, plans may not be executed or illegal activities may occur. The temporal dimension is used in the existing land use as time stamps for each data set. It will have versioning, change control and evolutions, used for study of temporal attributes with a unique identifier for polygons. An example of this is the CORINE 90-00-06 land cover.

For Land Cover, a density of buildings/trees is a physical characteristic, For Land Use density refers to the intensity of activities (agriculture, farming, manufacturing, services…​)

As a general guide, the identification and recording of land use should be at the smallest spatial unit that resources will permit. This provides the greatest flexibility and ability to aggregate to larger spatial units if required by other applications. Therefore the "minimum unit of interest" shall be documented.

D.3. HILUCS

The HILUCS code list is provided in Annex C.

D.4. Mapping HILUCS with LUCAS, NACE, SEEA and Urban Atlas

This section shows through examples how to map HILUCS with a specific classification system. LUCAS, NACE and Urban Atlas have been selected because they are European. The SYSTEM OF

ENVIRONMENTAL-ECONOMIC ACCOUNTS (SEEA) has been selected as it has been prepared under the auspices of the United Nations Committee of Experts on Environmental-Economic Accounting

Mapping from LUCAS to HILUCS

LUCAS code and Definition HILUCS code

U111

Agriculture (excluding fallow land, kitchen garden and personal consumption areas)

1_1

U112

Fallow land and abonded land in agriculture

1_1

U113

Kitchen garden

1_1

U120

Forestry

1_2

U130

Fishing

1_4

U140

Mining and Quarrying

1_3

U210

Energy Production

2_4

U221

Manufacturing of food, beverages and tobacco products

2_3_1

U222

Manufacturing of textile products

2_1_1
2_3_2

U223

Coal, oil and metal processing

2_1_4
2_1_6

U224

Production of non-metal mineral goods

2_1_7

U225

Chemical and allied industries and manufacturing

2_1_5

U226

Machinery and equipment

2_2_1
2_2_2

U227

Wood based products

2_1_2
2_1_3

U311

Railways

4_1_2

U312

Roads

4_1_1

U313

Water transport

4_1_4

U314

Air transport

4_1_3

U315

Transport via pipelines

4_3_1

U316

Telecommunication

3_2_3

U317

Storage

4_2

U318

Protection infrastructure

4_3_4

U321

Water supply and treatment

4_3_2

U322

Waste treatment

4_3_3

U330

Construction

6_1

U340

Commerce, Finance, Business

3_1
3_2

U350

Community services

3_3

U361

Amenities, museums, leisure

3_4

U362

Sport

3_4

U363

Holiday camps

3_1_3
5_3

U364

Nature reserves

Supplementary Regulation

U370

Residential

5_1

U400

Unused

6_3

Mapping from NACE (level 2) to HILUCS

TemplateCode Value HILUCS code

A

Agriculture, forestry and fishing

A1

Crop and animal production, hunting and related service activities

1_1
1_5_1

A2

Forestry and logging

1_2

A3

Fishing and aquaculture

1_4

B

Mining and quarrying

B5

Mining of coal and lignite

1_3_1

B6

Extraction of crude petroleum and natural gas

1_3_1

B7

Mining of metal ores

1_3_2

B8

Other mining and quarrying

1_3_3

B9

Mining support service activities

1_3_3

C

Manufacturing

C10

Manufacture of food products

2_3_1

C11

Manufacture of beverages

2_3_1

C12

Manufacture of tobacco products

2_3_1

C13

Manufacture of textiles

2_1_1

C14

Manufacture of wearing apparel

2_3_2

C15

Manufacture of leather and related products

2_3_2

C16

Manufacture of wood and of products of wood and cork, except furniture; manufacture of articles of straw and plaiting materials

2_1_2

C17

Manufacture of paper and paper products

2_1_2

C18

Printing and reproduction of recorded media

2_3_3

C19

Manufacture of coke and refined petroleum products

2_1_4

C20

Manufacture of chemicals and chemical products

2_1_5

C21

Manufacture of basic pharmaceutical products and pharmaceutical preparations

2_3_5

C22

Manufacture of rubber and plastic products

2_1_8

C23

Manufacture of other non-metallic mineral products

2_1_7

C24

Manufacture of basic metals

2_1_6

C25

Manufacture of fabricated metal products, except machinery and equipment

2_1_6

C26

Manufacture of computer, electronic and optical products

2_3_4

C27

Manufacture of electrical equipment

2_3_4

C28

Manufacture of machinery and equipment

2_2_1

C29

Manufacture of motor vehicles, trailers and semi-trailers

2_2_2

C30

Manufacture of other transport equipment

2_2_2

C31

Manufacture of furniture

2_3_5

C32

Other manufacturing

2_1_9
2_2_3
2_3_5

C33

Repair and installation of machinery and equipment

3_1_1

D

Electricity, gas, steam and air conditioning supply

D35

Electricity, gas, steam and air conditioning supply

2_4

E

Water supply; sewerage; waste managment and remediation activities

E36

Water collection, treatment and supply

4_3_2

E37

Sewerage

4_3_2

E38

Waste collection, treatment and disposal activities; materials recovery

4_3_3

E39

Remediation activities and other waste management services

4_3_3

F

Construction

F41

Construction of buildings

6_1

F42

Civil engineering

6_1

F43

Specialised construction activities

6_1

G

Wholesale and retail trade; repair of motor vehicles and motorcycles

G45

Wholesale and retail trade and repair of motor vehicles and motorcycles

3_1_1

G46

Wholesale trade, except of motor vehicles and motorcycles

3_1_1

G47

Retail trade, except of motor vehicles and motorcycles

3_1_1

H

Transporting and storage

H49

Land transport and transport via pipelines

4_1_1
4_1_2

H50

Water transport

4_1_4

H51

Air transport

4_1_3

H52

Warehousing and support activities for transportation

4_2

H53

Postal and courier activities

3_2_3

I

Accommodation and food service activities

I55

Accommodation

3_1_3

I56

Food and beverage service activities

3_1_3

J

Information and communication

J58

Publishing activities

3_2_3

J59

Motion picture, video and television programme production, sound recording and music publishing activities

3_2_3

J60

Programming and broadcasting activities

3_2_3

J61

Telecommunications

3_2_3

J62

Computer programming, consultancy and related activities

3_2_3

J63

Information service activities

3_2_3

K

Financial and insurance activities

K64

Financial service activities, except insurance and pension funding

3_2_1

K65

Insurance, reinsurance and pension funding, except compulsory social security

3_2_1

K66

Activities auxiliary to financial services and insurance activities

3_2_1

L

Real estate activities

L68

Real estate activities

3_1_2

M

Professional, scientific and technical activities

M69

Legal and accounting activities

3_2_2

M70

Activities of head offices; management consultancy activities

3_2_2

M71

Architectural and engineering activities; technical testing and analysis

3_2_2

M72

Scientific research and development

3_2_2

M73

Advertising and market research

3_2_2

M74

Other professional, scientific and technical activities

3_2_2

M75

Veterinary activities

3_3_3

N

Administrative and support service activities

N77

Rental and leasing activities

3_2_4

N78

Employment activities

3_2_4

N79

Travel agency, tour operator and other reservation service and related activities

3_2_4

N80

Security and investigation activities

3_2_4

N81

Services to buildings and landscape activities

3_2_4

N82

Office administrative, office support and other business support activities

3_2_4

O

Public administration and defence; compulsory social security

O84

Public administration and defence; compulsory social security

3_3_1

P

Education

P85

Education

3_3_2

Q

Human health and social work activities

Q86

Human health activities

3_3_3

Q87

Residential care activities

3_3_3
5_1

Q88

Social work activities without accommodation

3_3_3

R

Arts, entertainment and recreation

R90

Creative, arts and entertainment activities

3_4_1

R91

Libraries, archives, museums and other cultural activities

3_4_1

R92

Gambling and betting activities

3_4_2

R93

Sports activities and amusement and recreation activities

3_4_3

S

Other services activities

S94

Activities of membership organisations

3_2_4

S95

Repair of computers and personal and household goods

3_1_1

S96

Other personal service activities

3_1_4

T

Activities of households as employers; undifferentiated goods and services producing activities of households for own use

T97

Activities of households as employers of domestic personnel

3_1_4

T98

Undifferentiated goods- and services-producing activities of private households for own use

3_1_4

U

Activities of extraterritorial organisations and bodies

U99

Activities of extraterritorial organisations and bodies

3_2_4

Mapping from SEEA to HILUCS

SEEA code and definition

HILUCS code

LAND

Agriculture

1_1

Land under temporary crops

1_1

Land under temporary meadows and pastures

1_1

Land with temporary fallow

1_1

Land under permanent crops

1_1

Land under permanent meadows and pastures

1_1

Land under protective cover

1_1

Forestry

1_2

Forest land

1_2

Primary regenerated forest

1_2_3

Other naturally regenerated forest

1_2_2

Planted forest

1_2_1

Other wooded land

1_2

Land Used for aquaculture

1_4

Land Used for hatcheries

1_4

Managed grow-out sites on land

1_4

Use of built-up and related areas

Mining and quarrying

1_3

Construction

Tbd (6_1?)

Manufacturing

2
3

Technical infrastructure

4_3

Transport and storage

4_1
4_2

Commercial, financial and public services

3_1
3_2
3_3

Recreational facilities

3_4

Residential

5.

Land Used for maintenance and restoration of environmental functions

Supplementary regulation

Other uses of land n.e.c.

6_6

Land not in use

6_3_1

INLAND WATER

Inland waters used for aquaculture or holding facilities

1_4

Inland water used for maintenance and restoration of environmental functions

Supplementary regulation

Other uses of inland water n.e.c.

6_6

Inland water not in use

6_3_2

INTERNAL WATERS

Internal waters used for aquaculture or holding facilities

1_4

Internal waters used for maintenance and restoration of environmental functions

Supplementary regulation

Other uses of internal waters n.e.c.

6_6

Internal waters not in use

6_3_2

EXCLUSIVE ECONOMIC ZONE

EEZ areas used for aquaculture or holding facilities

1_4

EEZ areas used for maintenance and restoration of environmental functions

Supplementary regulation

Other uses of EEZ areas n.e.c.

6_6

EEZ areas not in use

6_3_2

Mapping from Urban Atlas to HILUCS

Urban Atlas code and definition HILUCS code

1.1.1

Continuous Urban fabric (soil sealing >80%)

5

1.1.2.1

Discontinuous dense urban fabric (soil sealing 50% - 80%)

5

1.1.2.2

Discontinuous medium urban fabric (soil sealing 30% - 50%)

5

1.1.2.3

Discontinuous low urban fabric (soil sealing 10% - 30%)

5

1.1.2.4

Discontinuous very low urban fabric (soil sealing <10%)

5

1.1.3

Isolated structure

5

1.2.1

Industrial, commercial, public, military, private units

2
3

1.2.2.1

Fast transit roads and associated land

4_1_1

1.2.2.2

Other roads ans associated land

4_1_1

1.2.2.3

Railways and associated land

4_1_2

1.2.3

Port areas

4_1_4

1.2.4

Airports

4_1_3

1.3.1

Mineral extraction and dump sites

1_3
4_3_3

1.3.3

Construction sites

6_1

1.3.4

Land without current use

6_3_1
6_3_2

1.4.1

Green urban ares

3_4_4

1.4.2

Sport and leasure facilities

3_4_3

2

Agricultural areas, semi-natural areas and wetlands

1_1
and several other classes

3

Forests

1_2

4

Water

several classes according to the use

D.5. HILUCS Frequently asked questions:

This list of questions and answers helps the HILUCS user to identify the proper class for rare, specific or borderline land use cases:

Q1: Under which class cemeteries belong?

A1: Cemeteries are part of class 3.3.5 'Other community services'

Q2: How can protected areas be classified?

A2: They are classified according to the land use (e.g. if forestry is allowed under 1.2). If no use is allowed they are classified under 6.3.1 'Land areas not in other use'. A supplementary regulation 'protected' is always needed.

Q3: Under which class irrigation ponds belong?

A3: They belong to class 1.1.1 'Commercial agricultural protection'.

Q4: How to classify industrial storage areas?

A4: They are part of the main industry branch, if adjacent to the industrial plant. Only pure storage and logistical services are classified under 4.2.

Q5: How to classify summer and other secondary residences?

A5: If they are privately owned they fall into 5.3 'Other residential use' if they are rented and linked to services they fall under class 3.1.3 'Accommodation services'.

Q6: where to map filling stations to

A6: filling station for vehicles will have two codes 3.1.1 because filling stations are wholesale and retail trade for fuel and 4.1.1. because they are road transport facilities (service station)

Q7: How to classify pedestrian zones, home zones or bikeways?

A7: They belong to class 4.1.5 'Other transport network'

Q8: How to classify areas for dumping of earth?

A8: They belong to class 6 'Other uses'

Q9: How to classify areas for mitigation and replacement measures as compensation for disturbance of a landscape area to restore or recreate the structural and functional character of the natural habitat and the necessary ecological balance?

A9: They belong to class 6.3 'Natural areas not in other economic use'

Q10:How to classify areas where occurs other primary productions which are not professional hunting, gathering of wild growing non-wood forestry products, or husbandry of migratory animals?

A10: They belong to class 1_5_OtherPrimaryProduction

D.6. Mapping HILUCS with some specific classification systems

Mapping from Flanders Codex RO categories to HILUCS

TemplateCode Value HILUCS code

WON = 'wonen' (cfr. Codex RO art. 2.2.3.§1, 1°)

5_1

WOO = 'woongebied' (cfr. Codex RO art. 2.2.3.§1, 1°, a )

5

WEL = 'gebied voor wonen en voor landbouw' (cfr. Codex RO art. 2.2.3.§1, 1°, b )

5_2

BED = 'bedrijvigheid' (cfr. Codex RO art. 2.2.3.§1, 2°)

2
3

REC = 'recreatie' (cfr. Codex RO art. 2.2.3.§1, 3°)

3_4

LDB = 'landbouw' (cfr. Codex RO art. 2.2.3.§1, 4°)

1_1

AGG = 'agrarisch gebied' (cfr. Codex RO art. 2.2.3.§1, 4°, a)

1_1

ABG = 'agrarische bedrijvenzone' (cfr. Codex RO art. 2.2.3.§1, 4°, b)

2_3_1

BAG = 'bouwvrij agrarisch gebied' (cfr. Codex RO art. 2.2.3.§1, 4°, c)

1_1

BOS = 'bos' (cfr. Codex RO art. 2.2.3.§1, 5°)

1_2

OVG = 'overig groen' (cfr. Codex RO art. 2.2.3.§1, 6°)

3_5

GOG = 'gemengd openruimtegebied' (cfr. Codex RO art. 2.2.3.§1, 6°, a)

3_5

PAG = 'parkgebied' (cfr. Codex RO art. 2.2.3.§1, 6°, b)

3_4_4

NAT = 'reservaat en natuur' (cfr. Codex RO art. 2.2.3.§1, 7°)

6_3

LNI = 'lijninfrastructuur' (cfr. Codex RO art. 2.2.3.§1, 8°)

4

GNV = 'gemeenschaps- en nutsvoorzieningen' (cfr. Codex RO art. 2.2.3.§1, 9°)

3_3
4_3

OWA = 'ontginning en waterwinning' (cfr. Codex RO art. 2.2.3.§1, 10°)

1_3

IDW = 'gebied voor infrastructuur voor duurzame watervoorziening' (cfr. Codex RO art. 2.2.3.§1, 10°, a)

4_3_2

ONT = 'gebied voor de winning van oppervlaktedelfstoffen' (cfr. Codex RO art. 2.2.3.§1, 10°,b)

1_3

GVO = 'gebied voor de verwerking van oppervlaktedelfstoffen' (cfr. Codex RO art. 2.2.3.§1,10°, c)

2_1

Mapping from CNIG (France) to HILUCS

Vocation principale d’une zone d’un document d’urbanisme de type POS et PLU.

CNIG Value HILUCS code

00 : sans objet

6_5

01 : habitat

5_1

02 : activité

2 and 3

03 : destination mixte

5_2

04 : loisirs et tourisme

3_4

05 : équipement

4.

07 : activité agricole

1_1

08 : espace naturel

1_2 and 6_3

09 : espace remarquable (littoral L146-6 / montagne L145-7)

6_3 with supplementary regulation

10 : secteur de carrière

1_3

99 : autre

6

Mapping from German 3A data model based on TN classification system to HILUCS. First a translation table from 3A-code to 3A-feature class is given. In the following table a mapping to HILUCS is given.

3A-code 3A-feature class

41001

AX_Wohnbaufläche

41002

AX_IndustrieUndGewerbeflaeche

41003

AX_Halde

41004

AX_Bergbaubetrieb

41005

AX_TagebauGrubeSteinbruch

41006

AX_FlaecheGemischterNutzung

41007

AX_FlaecheBesondererFunktionalerPraegung

41008

AX_SportFreizeitUndErholungsflaeche

41009

AX_Friedhof

42001

AX_Strassenverkehr

42006

AX_Weg

42009

AX_Platz

42010

AX_Bahnverkehr

42015

AX_Flugverkehr

42016

AX_Schiffsverkehr

43001

AX_Landwirtschaft

43002

AX_Wald

43003

AX_Gehoelz

43004

AX_Heide

43005

AX_Moor

43006

AX_Sumpf

43007

AX_UnlandVegetationsloseFlaeche

43008

AX_FlaecheZurZeitUnbestimmbar

44001

AX_Fliessgewaesser

44005

AX_Hafenbecken

44006

AX_StehendesGewaesser

44007

AX_Meer

Mapping from 3A-code to HILUCS

3A-code attribute 1:
attribute=value (meaning)		 attribute 2:

attribute=value (meaning)		 HILIUCS code

41001

5_1

41001

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

41001

ZUS=8000 (Erweiterung, Neuansiedlung)

6_1

41002

FKT=NULL

2

41002

FKT=1400 (Handel und Dienstleistung)

3

41002

FKT=1410 (Verwaltung, freie Berufe)

3

41002

FKT=1420 (Bank, Kredit)

3_2_1

41002

FKT=1430 (Versicherung)

3_2_1

41002

FKT=1440 (Handel)

3_1_1

41002

FKT=1450 (Ausstellung, Messe)

3_2_5

41002

FKT=1460 (Beherbergung)

3_1_3

41002

FKT=1470 (Restauration)

3_1_3

41002

FKT=1480 (Vergnügung)

3_4_2

41002

FKT=1490 (Gärtnerei)

3_1_1

41002

FKT=1700 (Industrie und Gewerbe)

2

41002

FKT=1701 (Gebäude- und Freifläche Industrie und Gewerbe)

2

41002

FKT=1710 (Produktion)

2

41002

FKT=1720 (Handwerk)

2

41002

FKT=1730 (Tankstelle)

3_1_1

41002

FKT=1740 (Lagerplatz)

LGT=NULL

2

41002

FKT=1740 (Lagerplatz)

LGT=NULL

4_2

41002

FKT=1740 (Lagerplatz)

LGT=1000 (Baustoffe)

4_2

41002

FKT=1740 (Lagerplatz)

LGT=2000 (Kohle)

1_3_1

41002

FKT=1740 (Lagerplatz)

LGT=3000 (Öl)

1_3_1

41002

FKT=1740 (Lagerplatz)

LGT=4000 (Erde)

1_3_3

41002

FKT=1740 (Lagerplatz)

LGT=5000 (Schutt)

1_3_3

41002

FKT=1740 (Lagerplatz)

LGT=6000 (Schlacke)

1_3_2

41002

FKT=1740 (Lagerplatz)

LGT=7000 (Abraum)

1_3_3

41002

FKT=1740 (Lagerplatz)

LGT=8000 (Schrott, Altmaterial)

4_2

41002

FKT=1740 (Lagerplatz)

LGT=9999 (Sonstiges)

4_2

41002

FKT=1750 (Transport)

2

41002

FKT=1760 (Forschung)

2

41002

FKT=1770 (Grundstoff)

2

41002

FKT=1780 (Betriebliche Sozialeinrichtungen)

3_3_3

41002

FKT=1790 (Werft)

2_2_2

41002

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

41002

FKT=2500 (Versorgungsanlagen)

4_3_1

41002

FKT=2501 (Gebäude- und Freifläche Versorgungsanlagen)

4_3_1

41002

FKT=2502 (Betriebliche Versorgungsanlage)

4_3_1

41002

FKT=2510 (Förderanlage)

FGT=1000 (Erdöl)

1_3_1

41002

FKT=2510 (Förderanlage)

FGT=2000 (Erdgas)

1_3_1

41002

FKT=2510 (Förderanlage)

FGT=3000 (Sole, Lauge)

1_3_3

41002

FKT=2510 (Förderanlage)

FGT=4000 (Kohlensäure)

1_3_3

41002

FKT=2510 (Förderanlage)

FGT=5000 (Erdwärme)

2_4_4

41002

FKT=2520 (Wasserwerk)

4_3_2

41002

FKT=2521 (Gebäude- und Freifläche Versorgungsanlage, Wasser)

4_3_2

41002

FKT=2522 (Betriebsfläche Versorgungsanlage, Wasser)

4_3_2

41002

FKT=2530 (Kraftwerk)

PEG=NULL

2_4

41002

FKT=2530 (Kraftwerk)

PEG=1000 (Wasser)

2_4_4

41002

FKT=2530 (Kraftwerk)

PEG=2000 (Kernkraft)

2_4_1

41002

FKT=2530 (Kraftwerk)

PEG=3000 (Sonne)

2_4_4

41002

FKT=2530 (Kraftwerk)

PEG=4000 (Wind)

2_4_4

41002

FKT=2530 (Kraftwerk)

PEG=5000 (Gezeiten)

2_4_4

41002

FKT=2530 (Kraftwerk)

PEG=6000 (Erdwärme)

2_4_4

41002

FKT=2530 (Kraftwerk)

PEG=7000 (Verbrennung)

2_4_2

41002

FKT=2530 (Kraftwerk)

PEG=7100 (Kohle)

2_4_2

41002

FKT=2530 (Kraftwerk)

PEG=7200 (Öl)

2_4_2

41002

FKT=2530 (Kraftwerk)

PEG=7300 (Gas)

2_4_2

41002

FKT=2530 (Kraftwerk)

PEG=7400 (Müll, Abfall)

2_4_2

41002

FKT=2531 (Gebäude- und Freifläche Versorgungsanlagen, Elektrizität)

4_3_1

41002

FKT=2532 (Betriebsfläche Versorgungsanlage, Elektrizität)

4_3_1

41002

FKT=2540 (Umspannstation)

4_3_1

41002

FKT=2550 (Raffinerie)

2_1_4

41002

FKT=2551 (Gebäude- und Freifläche Versorgungsanlage, Öl)

2_1_4

41002

FKT=2552 (Betriebsfläche Versorgungsanlage, Öl)

2_1_4

41002

FKT=2560 (Gaswerk)

4_3_1

41002

FKT=2561 (Gebäude- und Freifläche Versorgungsanlage, Gas)

4_3_1

41002

FKT=2562 (Betriebsfläche Versorgungsanlage, Gas)

4_3_1

41002

FKT=2570 (Heizwerk)

PEG=NULL

2_4

41002

FKT=2570 (Heizwerk)

PEG=1000 (Wasser)

2_4_4

41002

FKT=2570 (Heizwerk)

PEG=3000 (Sonne)

2_4_4

41002

FKT=2570 (Heizwerk)

PEG=4000 (Wind)

2_4_4

41002

FKT=2570 (Heizwerk)

PEG=5000 (Gezeiten)

2_4_4

41002

FKT=2570 (Heizwerk)

PEG=6000 (Erdwärme)

2_4_4

41002

FKT=2570 (Heizwerk)

PEG=7000 (Verbrennung)

2_4_2

41002

FKT=2570 (Heizwerk)

PEG=7100 (Kohle)

2_4_2

41002

FKT=2570 (Heizwerk)

PEG=7200 (Öl)

2_4_2

41002

FKT=2570 (Heizwerk)

PEG=7300 (Gas)

2_4_2

41002

FKT=2570 (Heizwerk)

PEG=7400 (Müll, Abfall)

2_4_2

41002

FKT=2571 (Gebäude- und Freifläche Versorgungsanlage, Wärme)

4_3_1

41002

FKT=2572 (Betriebsfläche Versorgungsanlage, Wärme)

4_3_1

41002

FKT=2580 (Funk- und Fernmeldeanlage)

4_3_4

41002

FKT=2581 (Gebäude- und Freifläche Versorgungsanlage, Funk- und Fernmeldewesen)

4_3_4

41002

FKT=2582 (Betriebsfläche Versorgungsanlage. Funk- und Fernmeldewesen)

4_3_4

41002

FKT=2600 (Entsorgung)

4_3_3

41002

FKT=2601 (Gebäude- und Freifläche Entsorgungsanlage)

4_3_3

41002

FKT=2602 (Betriebsfläche Entsorgungsanlage)

4_3_3

41002

FKT=2610 (Kläranlage, Klärwerk)

4_3_2

41002

FKT=2611 (Gebäude- und Freifläche Entsorgungsanlage, Abwasserbeseitigung)

4_3_2

41002

FKT=2612 (Betriebsfläche Entsorgungsanlage, Abwasserbeseitigung)

4_3_2

41002

FKT=2620 (Abfallbehandlungsanlage)

4_3_3

41002

FKT=2621 (Gebäude- und Freifläche Entsorgungsanlage, Abfallbeseitigung)

4_3_3

41002

FKT=2622 (Betriebsfläche Entsorgungsanlage, Abfallbeseitigung)

4_3_3

41002

FKT=2623 (Betriebsfläche Entsorgungsanlage, Schlamm)

4_3_3

41002

FKT=2630 (Deponie (oberirdisch))

4_3_3

41002

FKT=2640 (Deponie (unterirdisch))

4_3_3

41002

ZUS=8000 (Erweiterung, Neuansiedlung)

6_1

41003

LGT=NULL

4_2

41003

LGT=1000 (Baustoffe)

4_2

41003

LGT=2000 (Kohle)

1_3_1

41003

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

41003

LGT=4000 (Erde)

1_3_3

41003

LGT=5000 (Schutt)

1_3_3

41003

LGT=6000 (Schlacke)

1_3_2

41003

LGT=7000 (Abraum)

1_3_3

41003

LGT=8000 (Schrott, Altmaterial)

4_2

41003

ZUS=8000 (Erweiterung, Neuansiedlung)

6_1

41003

LGT=9999 (Sonstiges)

4_2

41004

AGT=NULL

1_3

41004

AGT=1000 (Erden, Lockergestein)

1_3_3

41004

AGT=1001 (Ton)

1_3_3

41004

AGT=1007 (Kalk, Kalktuff, Kreide)

1_3_3

41004

AGT=2000 (Steine, Gestein, Festgestein)

1_3_3

41004

AGT=2002 (Schiefer, Dachschiefer)

1_3_3

41004

AGT=2003 (Metamorpher Schiefer)

1_3_3

41004

AGT=2005 (Kalkstein)

1_3_3

41004

AGT=2006 (Dolomitstein)

1_3_3

41004

AGT=2013 (Basalt, Diabas)

1_3_3

41004

AGT=2021 (Talkschiefer, Speckstein)

1_3_3

41004

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

41004

AGT=3000 (Erze)

1_3_2

41004

AGT=3001 (Eisen)

1_3_2

41004

AGT=3002 (Buntmetallerze)

1_3_2

41004

AGT=3003 (Kupfer)

1_3_2

41004

AGT=3004 (Blei)

1_3_2

41004

AGT=3005 (Zink)

1_3_2

41004

AGT=3006 (Zinn)

1_3_2

41004

AGT=3007 (Wismut, Kobalt, Nickel)

1_3_2

41004

AGT=3008 (Uran)

1_3_1

41004

AGT=3009 (Mangan)

1_3_2

41004

AGT=3010 (Antimon)

1_3_2

41004

AGT=3011 (Edelmetallerze)

1_3_2

41004

AGT=4000 (Treib- und Brennstoffe)

1_3_1

41004

AGT=4020 (Kohle)

1_3_1

41004

AGT=4021 (Braunkohle)

1_3_1

41004

AGT=4022 (Steinkohle)

1_3_1

41004

AGT=4030 (Ölschiefer)

1_3_1

41004

AGT=5000 (Industrieminerale, Salze)

1_3_3

41004

AGT=5001 (Gipsstein)

1_3_3

41004

AGT=5002 (Anhydritstein)

1_3_3

41004

AGT=5003 (Steinsalz)

1_3_3

41004

AGT=5004 (Kalisalz)

1_3_3

41004

AGT=5005 (Kalkspat)

1_3_3

41004

AGT=5006 (Flussspat)

1_3_3

41004

AGT=5007 (Schwerspat)

1_3_3

41004

AGT=5011 (Graphit)

1_3_3

41004

ZUS=8000 (Erweiterung, Neuansiedlung)

6_1

41005

AGT=NULL

1_3

41005

AGT=1000 (Erden, Lockergestein)

1_3_3

41005

AGT=1001 (Ton)

1_3_3

41005

AGT=1002 (Bentonit)

1_3_3

41005

AGT=1003 (Kaolin)

1_3_3

41005

AGT=1004 (Lehm)

1_3_3

41005

AGT=1005 (Löß, Lößlehm)

1_3_3

41005

AGT=1006 (Mergel)

1_3_3

41005

AGT=1007 (Kalk, Kalktuff, Kreide)

1_3_3

41005

AGT=1008 (Sand)

1_3_3

41005

AGT=1009 (Kies, Kiessand)

1_3_3

41005

AGT=1011 (Farberden)

1_3_3

41005

AGT=1012 (Quarzsand)

1_3_3

41005

AGT=1013 (Kieselerde)

1_3_3

41005

AGT=2000 (Steine, Gestein, Festgestein)

1_3_3

41005

AGT=2001 (Tonstein)

1_3_3

41005

AGT=2002 (Schiefer, Dachschiefer)

1_3_3

41005

AGT=2003 (Metamorpher Schiefer)

1_3_3

41005

AGT=2004 (Mergelstein)

1_3_3

41005

AGT=2005 (Kalkstein)

1_3_3

41005

AGT=2006 (Dolomitstein)

1_3_3

41005

AGT=2007 (Travertin)

1_3_3

41005

AGT=2008 (Marmor)

1_3_3

41005

AGT=2009 (Sandstein)

1_3_3

41005

AGT=2010 (Grauwacke)

1_3_3

41005

AGT=2011 (Quarzit)

1_3_3

41005

AGT=2012 (Gneis)

1_3_3

41005

AGT=2013 (Basalt, Diabas)

1_3_3

41005

AGT=2014 (Andesit)

1_3_3

41005

AGT=2015 (Porphyr, Quarzporphyr)

1_3_3

41005

AGT=2016 (Granit)

1_3_3

41005

AGT=2017 (Granodiorit)

1_3_3

41005

AGT=2018 (Tuff-, Bimsstein)

1_3_3

41005

AGT=2019 (Trass)

1_3_3

41005

AGT=2020 (Lavaschlacke)

1_3_3

41005

AGT=2021 (Talkschiefer, Speckstein)

1_3_3

41005

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

41005

AGT=4000 (Treib- und Brennstoffe)

1_3_1

41005

AGT=4010 (Torf)

1_3_1

41005

AGT=4020 (Kohle)

1_3_1

41005

AGT=4021 (Braunkohle)

1_3_1

41005

AGT=4022 (Steinkohle)

1_3_1

41005

AGT=4030 (Ölschiefer)

1_3_1

41005

AGT=5000 (Industrieminerale, Salze)

1_3_3

41005

AGT=5001 (Gipsstein)

1_3_3

41005

AGT=5002 (Anhydritstein)

1_3_3

41005

AGT=5005 (Kalkspat)

1_3_3

41005

AGT=5007 (Schwerspat)

1_3_3

41005

AGT=5008 (Quarz)

1_3_3

41005

AGT=5009 (Feldspat)

1_3_3

41005

AGT=5010 (Pegmatitsand)

1_3_3

41005

ZUS=8000 (Erweiterung, Neuansiedlung)

6_1

41006

FKT=NULL

5_2

41006

FKT=2100 (Gebäude- und Freifläche, Mischnutzung mit Wohnen)

5_2

41006

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

41006

FKT=2110 (Wohnen mit Öffentlich)

5_2
5_1
3_3

41006

FKT=2120 (Wohnen mit Handel und Dienstleistung)

5_2
5_1
3_1

41006

FKT=2130 (Wohnen mit Gewerbe und Industrie)

5_2
5_1
3_1

41006

FKT=2140 (Öffentlich mit Wohnen)

3_3_1
3_3
5_1

41006

FKT=2150 (Handel und Dienstleistung mit Wohnen)

3
3_1
5_1

41006

FKT=2160 (Gewerbe und Industrie mit Wohnen)

2
2_3
5_1

41006

FKT=2700 (Gebäude- und Freifläche Land- und Forstwirtschaft)

1_1_2

41006

FKT=2710 (Wohnen)

5_2

41006

FKT=2720 (Betrieb)

1_1_2

41006

FKT=2730 (Wohnen und Betrieb)

5_2
5_1
1_1

41006

FKT=6800 (Landwirtschaftliche Betriebsfläche)

1_1_2

41006

FKT=7600 (Forstwirtschaftliche Betriebsfläche)

1_2

41006

ZUS=8000 (Erweiterung, Neuansiedlung)

6_1

41007

FKT=NULL

3

41007

FKT=1100 (Öffentliche Zwecke)

3_3_1

41007

FKT=1110 (Verwaltung)

3_3_1

41007

FKT=1120 (Bildung und Forschung)

3_3_2

41007

FKT=1130 (Kultur)

3_4_1

41007

FKT=1140 (Religiöse Einrichtung)

3_3_4

41007

FKT=1150 (Gesundheit, Kur)

3_3_3

41007

FKT=1160 (Soziales)

3_3_3

41007

FKT=1170 (Sicherheit und Ordnung)

3_3_1

41007

FKT=1200 (Parken)

4_1_1

41007

FKT=1300 (Historische Anlagen)

3_4_1

41007

FKT=1310 (Burg-, Festungsanlage)

3_4_1

41007

FKT=1320 (Schlossanlage)

3_4_1

41007

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

41007

ZUS=8000 (Erweiterung, Neuansiedlung)

6_1

41008

FKT=NULL

3_4

41008

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

41008

FKT=4001 (Gebäude- und Freifläche Sport, Freizeit und Erholung)

3_4_3

41008

FKT=4100 (Sportanlage)

3_4_3

41008

FKT=4101 (Gebäude- und Freifläche Erholung , Sport)

3_4_3

41008

FKT=4110 (Golfplatz)

3_4_3

41008

FKT=4120 (Sportplatz)

3_4_3

41008

FKT=4130 (Rennbahn)

3_4_3

41008

FKT=4140 (Reitplatz)

3_4_3

41008

FKT=4150 (Schießanlage)

3_4_3

41008

FKT=4160 (Eis-, Rollschuhbahn)

3_4_3

41008

FKT=4170 (Tennisplatz)

3_4_3

41008

FKT=4200 (Freizeitanlage)

3_4_2

41008

FKT=4210 (Zoo)

3_4_1

41008

FKT=4211 (Gebäude- u. Freifläche Erholung, Zoologie)

3_4_1

41008

FKT=4220 (Safaripark, Wildpark)

3_4_1

41008

FKT=4230 (Freizeitpark)

3_4_2

41008

FKT=4240 (Freilichttheater)

3_4_1

41008

FKT=4250 (Freilichtmuseum)

3_4_1

41008

FKT=4260 (Autokino, Freilichtkino)

3_4_2

41008

FKT=4270 (Verkehrsübungsplatz)

3_3_2

41008

FKT=4280 (Hundeübungsplatz)

3_4_3

41008

FKT=4290 (Modellflugplatz)

3_4_3

41008

FKT=4300 (Erholungsfläche)

3_4_4

41008

FKT=4301 (Gebäude- und Freifläche Erholung)

3_4_4

41008

FKT=4310 (Wochenend- und Ferienhäuser)

3_1_3

41008

FKT=4320 (Schwimmbad, Freibad)

3_4_3

41008

FKT=4321 (Gebäude- und Freifläche Erholung, Bad)

3_4_3

41008

FKT=4330 (Campingplatz)

3_1_3

41008

FKT=4331 (Gebäude- und Freifläche Erholung, Camping)

3_1_3

41008

FKT=4400 (Grünanlage)

3_4_4

41008

FKT=4410 (Grünfläche)

3_4_4

41008

FKT=4420 (Park)

3_4_4

41008

FKT=4430 (Botanischer Garten)

3_4_1

41008

FKT=4431 (Gebäude- und Freifläche Erholung, Botanik)

3_4_1

41008

FKT=4440 (Kleingarten)

3_4_4

41008

FKT=4450 (Wochenendplatz)

3_4_4

41008

FKT=4460 (Garten)

1_1_3

41008

FKT=4470 (Spielplatz, Bolzplatz)

3_4_4

41008

ZUS=8000 (Erweiterung, Neuansiedlung)

6_1

41008

FKT=9999 (Sonstiges)

3_4_5

41009

FKT=NULL

3_3_4

41009

FKT=9401 (Gebäude- und Freifläche Friedhof)

3_3_4

41009

FKT=9402 (Friedhof (ohne Gebäude))

3_3_4

41009

FKT=9403 (Friedhof (Park))

3_3_4

41009

FKT=9404 (Historischer Friedhof)

3_4_1

42001

FKT=NULL

4_1_1

42001

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

42001

FKT=2311 (Gebäude- und Freifläche zu Verkehrsanlagen, Straße)

4_1_1

42001

FKT=2312 (Verkehrsbegleitfläche Straße)

4_1_1

42001

FKT=2313 (Straßenentwässerungsanlage)

4_1_1

42001

ZUS=4000 (Im Bau)

6_1

42001

FKT=5130 (Fußgängerzone)

4_1_1

42006

FKT=NULL

4_1_1

42006

FKT=5210 (Fahrweg)

4_1_1

42006

FKT=5211 (Hauptwirtschaftsweg)

4_1_1

42006

FKT=5212 (Wirtschaftsweg)

4_1_1

42006

FKT=5220 (Fußweg)

4_1_1

42006

FKT=5230 (Gang)

4_1_1

42006

FKT=5240 (Radweg)

4_1_1

42006

FKT=5250 (Rad- und Fußweg)

4_1_1

42006

FKT=5260 (Reitweg)

4_1_1

42006

FKT=9999 (Sonstiges)

4_1_1

42009

FKT=NULL

4_1_1

42009

FKT=5130 (Fußgängerzone)

4_1_1

42009

FKT=5310 (Parkplatz)

4_1_1

42009

FKT=5320 (Rastplatz)

4_1_1

42009

FKT=5330 (Raststätte)

4_1_1

42009

FKT=5340 (Marktplatz)

4_1_1

42009

FKT=5350 (Festplatz)

3_4_2

42010

FKT=NULL

4_1_2

42010

BKT=NULL

4_1_2

42010

BKT=1100 (Eisenbahn)

4_1_2

42010

BKT=1102 (Güterverkehr)

4_1_2

42010

BKT=1104 (S-Bahn)

4_1_2

42010

BKT=1200 (Stadtbahn)

4_1_2

42010

BKT=1201 (Straßenbahn)

4_1_2

42010

BKT=1202 (U-Bahn)

4_1_2

42010

BKT=1300 (Seilbahn, Bergbahn)

4_1_2

42010

BKT=1301 (Zahnradbahn)

4_1_2

42010

BKT=1302 (Standseilbahn)

4_1_2

42010

BKT=1400 (Museumsbahn)

3_4_1

42010

BKT=1500 (Bahn im Freizeitpark)

3_4_2

42010

BKT=1600 (Magnetschwebebahn)

4_1_2

42010

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

42010

FKT=2321 (Gebäude- und Freifläche zu Verkehrsanlagen, Schiene)

4_1_2

42010

FKT=2322 (Verkehrsbegleitfläche Bahnverkehr)

4_1_2

42010

ZUS=4000 (Im Bau)

6_1

42015

FKT=NULL

4_1_3

42015

ART=NULL

4_1_3

42015

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

42015

ZUS=4000 (Im Bau)

6_1

42015

FKT=5501 (Gebäude- und Freifläche zu Verkehrsanlagen, Luftfahrt)

4_1_3

42015

ART=5510 (Flughafen)

4_1_3

42015

ART=5511 (Internationaler Flughafen)

4_1_3

42015

ART=5512 (Regionalflughafen)

4_1_3

42015

ART=5520 (Verkehrslandeplatz)

4_1_3

42015

ART=5530 (Hubschrauberflugplatz)

4_1_3

42015

ART=5540 (Landeplatz, Sonderlandeplatz)

4_1_3

42015

ART=5550 (Segelfluggelände)

4_1_3

42016

FKT=NULL

4_1_4

42016

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

42016

FKT=2341 (Gebäude- und Freifläche zu Verkehrsanlagen, Schifffahrt)

4_1_4

42016

ZUS=4000 (Im Bau)

6_1

42016

FKT=5610 (Hafenanlage (Landfläche))

4_1_4

42016

FKT=5620 (Schleuse (Landfläche))

4_1_4

42016

FKT=5630 (Anlegestelle)

4_1_4

42016

FKT=5640 (Fähranlage)

4_1_4

43001

VEG=NULL

1_1_1

43001

VEG=1010 (Ackerland)

1_1_1

43001

VEG=1011 (Streuobstacker)

1_1_1

43001

VEG=1012 (Hopfen)

1_1_1

43001

VEG=1013 (Spargel)

1_1_1

43001

VEG=1020 (Grünland)

1_1_1

43001

VEG=1021 (Streuobstwiese)

1_1_1

43001

VEG=1030 (Gartenland)

1_1_1

43001

VEG=1031 (Baumschule)

1_1_1

43001

VEG=1040 (Weingarten)

1_1_1

43001

VEG=1050 (Obstplantage)

1_1_1

43001

VEG=1051 (Obstbaumplantage)

1_1_1

43001

VEG=1052 (Obststrauchplantage)

1_1_1

43001

VEG=1200 (Brachland)

1_1_1

43002

VEG=NULL

1_2

43002

VEG=1100 (Laubholz)

1_2

43002

VEG=1200 (Nadelholz)

1_2

43002

VEG=1300 (Laub- und Nadelholz)

1_2

43002

VEG=1310 (Laubwald mit Nadelholz)

1_2

43002

VEG=1320 (Nadelwald mit Laubholz)

1_2

43003

VEG=NULL

1_2

43003

VEG=1400 (Latschenkiefer)

1_2

43004

6_3_1

43005

6_3_1

43006

6_3_1

43007

FKT=NULL

6_3_1

43007

FKT=1000 (Vegetationslose Fläche)

OFM=NULL

6_3_1

43007

FKT=1000 (Vegetationslose Fläche)

OFM=1010 (Fels)

6_3_1

43007

FKT=1000 (Vegetationslose Fläche)

OFM=1020 (Steine, Schotter)

6_3_1

43007

FKT=1000 (Vegetationslose Fläche)

OFM=1030 (Geröll)

6_3_1

43007

FKT=1000 (Vegetationslose Fläche)

OFM=1040 (Sand)

6_3_1

43007

FKT=1000 (Vegetationslose Fläche)

OFM=1110 (Schnee)

6_3_1

43007

FKT=1000 (Vegetationslose Fläche)

OFM=1120 (Eis, Firn)

6_3_2

43007

FKT=1100 (Gewässerbegleitfläche)

4_1_4

43007

FKT=1110 (Bebaute Gewässerbegleitfläche)

4_1_4

43007

FKT=1120 (Unbebaute Gewässerbegleitfläche)

4_1_4

43007

FKT=1200 (Sukzessionsfläche)

6_3_1

43008

6_6

44001

FKT=NULL

4_1_4

44001

ZUS=2100 (Außer Betrieb, stillgelegt, verlassen)

6_2

44001

ZUS=4000 (Im Bau)

6_1

44001

FKT=8200 (Fluss)

4_1_4

44001

FKT=8210 (Altwasser)

6_3_2

44001

FKT=8220 (Altarm)

6_3_2

44001

FKT=8230 (Flussmündungstrichter)

4_1_4

44001

FKT=8300 (Kanal)

4_1_4

44001

FKT=8400 (Graben)

6_3_2

44001

FKT=8410 (Fleet)

4_1_4

44001

FKT=8500 (Bach)

6_3_2

44005

FKT=NULL

4_1_4

44005

FKT=8810 (Sporthafenbecken)

4_1_4

44006

FKT=NULL

6_3_2

44006

FKT=8610 (See)

6_3_2

44006

FKT=8620 (Teich)

3_4_4

44006

FKT=8630 (Stausee)

4_3_2

44006

FKT=8631 (Speicherbecken)

4_3_2

44006

FKT=8640 (Baggersee)

1_3_3

44006

FKT=9999 (Sonstiges)

6_3_2

44007

FKT=NULL

6_3_2

44007

FKT=8710 (Küstengewässer)

4_1_4

Mapping from German XPlanGML standard to HILUCS

XPlanGML class HILUCSValue

BP_AufschuettungsFlaeche

6_OtherUse

FP_AufschuettungsFlaeche

6_OtherUse

BP_AbgrabungsFlaeche

1_3_Miningandquarrying

FP_AbgrabungsFlaeche

1_3_Miningandquarrying

BP_BodenschaetzeFlaeche

1_3_Miningandquarrying

FP_BodenschaetzeFlaeche

1_3_Miningandquarrying

BP_RekultivierungsFlaeche

6_OtherUse

BP_BaugebietsTeilFlaeche

 

Kleinsiedlungsgebiet

5_3_OtherResidentialUse

ReinesWohngebiet

5_1_PureResidentialUse

AllgWohngebiet

5_ResidentialUse

BesonderesWohngebiet

5_3_OtherResidentialUse

Dorfgebiet

5_3_OtherResidentialUse

 

1_1_2_FarmingInfrastructure

Mischgebiet

5_2_ResidentialUseWithOtherCompatibleUse

Kerngebiet

3_1_CommercialServices

 

3_2_FinancialProfessionalAndInformationServices

 

3_4_CulturalEntertainmentAndRecreationServices

Gewerbegebiet

2_3_LightEndProductIndustry

Industriegebiet

2_1_RawIndustry

SondergebietErholung

5_3_OtherResidentialUse

SondergebietSonst

3_5_OtherServices

Wochenendhausgebiet

5_3_OtherResidentialUse

Sondergebiet

3_5_OtherServices

SonstigesGebiet

3_5_OtherServices

FP_BebauungsFlaeche

 

allgArtDerBaulNutzung

 

WohnBauflaeche

5_ResidentialUse

GemischteBauflaeche

5_2_ResidentialUseWithOtherCompatibleUse

GewerblicheBauflaeche

2_SecondaryProduction

SonderBauflaeche

6_OtherUse

SonstigeBauflaeche

6_OtherUse

besondereArtDerBaulNutzung

 

Kleinsiedlungsgebiet

5_3_OtherResidentialUse

ReinesWohngebiet

5_1_PureResidentialUse

AllgWohngebiet

5_ResidentialUse

BesonderesWohngebiet

5_3_OtherResidentialUse

Dorfgebiet

5_3_OtherResidentialUse

 

1_1_2_FarmingInfrastructure

Mischgebiet

5_2_ResidentialUseWithOtherCompatibleUse

Kerngebiet

3_1_CommercialServices

 

3_2_FinancialProfessionalAndInformationServices

 

3_3_CommunityServices

Gewerbegebiet

2_3_LightEndProductIndustry

Industriegebiet

2_SecondaryProduction

SondergebietErholung

5_3_OtherResidentialUse

SondergebietSonst

3_5_OtherServices

Wochenendhausgebiet

5_3_OtherResidentialUse

Sondergebiet

6_OtherUse

SonstigesGebiet

6_OtherUse

BP_BesondererNutzungszwecke

6_OtherUse

Flaeche

 

BP_GemeinbedarfsFlaeche

3_3_CommunityServices

OffentlicheVerwaltung

3_3_1_PublicAdministrationDefenseAndSocialSecurityServices

BildungForschung

3_3_2_EducationalServices

Kirche

3_3_4_ReligiousServices

Sozial

3_3_3_HealthAndSocialServices

Gesundheit

3_3_3_HealthAndSocialServices

Kultur

3_4_1_CulturalServices

Sport

3_4_3_SportsInfrastructure

SicherheitOrdnung

3_3_1_PublicAdministrationDefenseAndSocialSecurityServices

Infrastruktur

4_3_Utilities

Sonstiges

3_5_OtherServices

FP_Gemeinbedarf

3_3_CommunityServices

OffentlicheVerwaltung

3_3_1_PublicAdministrationDefenseAndSocialSecurityServices

BildungForschung

3_3_2_EducationalServices

Kirche

3_3_4_ReligiousServices

Sozial

3_3_3_HealthAndSocialServices

Gesundheit

3_3_3_HealthAndSocialServices

Kultur

3_4_1_CulturalServices

Sport

3_4_3_SportsInfrastructure

SicherheitOrdnung

3_3_1_PublicAdministrationDefenseAndSocialSecurityServices

Infrastruktur

4_3_Utilities

Sonstiges

3_5_OtherServices

BP_SpielSportanlagenFlaeche

3_4_3_SportsInfrastructure

Sportanlage

3_4_3_SportsInfrastructure

Spielanlage

3_4_3_SportsInfrastructure

SpielSportanlage

3_4_3_SportsInfrastructure

Sonstiges

3_4_3_SportsInfrastructure

FP_SpielSportanlage

3_4_3_SportsInfrastructure

Sportanlage

3_4_3_SportsInfrastructure

Spielanlage

3_4_3_SportsInfrastructure

SpielSportanlage

3_4_3_SportsInfrastructure

Sonstiges

3_4_3_SportsInfrastructure

BP_GruenFlaeche

3_4_4_OpenAirRecreationalAreas

Parkanlage

3_4_4_OpenAirRecreationalAreas

Dauerkleingaerten

3_4_4_OpenAirRecreationalAreas

Sportplatz

3_4_3_SportsInfrastructure

Spielplatz

3_4_4_OpenAirRecreationalAreas

Zeltplatz

3_4_4_OpenAirRecreationalAreas

Badeplatz

3_4_4_OpenAirRecreationalAreas

FreizeitErholung

3_4_4_OpenAirRecreationalAreas

SpezGruenflaeche

3_4_4_OpenAirRecreationalAreas

Friedhof

3_5_OtherServices

Sonstiges

3_4_4_OpenAirRecreationalAreas

FP_Gruen

3_4_4_OpenAirRecreationalAreas

Parkanlage

3_4_4_OpenAirRecreationalAreas

Dauerkleingaerten

3_4_4_OpenAirRecreationalAreas

Sportplatz

3_4_3_SportsInfrastructure

Spielplatz

3_4_4_OpenAirRecreationalAreas

Zeltplatz

3_4_4_OpenAirRecreationalAreas

Badeplatz

3_4_4_OpenAirRecreationalAreas

FreizeitErholung

3_4_4_OpenAirRecreationalAreas

SpezGruenflaeche

3_4_4_OpenAirRecreationalAreas

Friedhof

3_5_OtherServices

Sonstiges

3_4_4_OpenAirRecreationalAreas

BP_Landwirtschaft

1_1_Agriculture

LandwirtschaftAllgemein

1_1_Agriculture

Ackerbau

1_1_1_CommercialAgriculturalProduction

WiesenWeidewirtschaft

1_1_1_CommercialAgriculturalProduction

GartenbaulicheErzeugung

1_1_1_CommercialAgriculturalProduction

Obstbau

1_1_1_CommercialAgriculturalProduction

Weinbau

1_1_1_CommercialAgriculturalProduction

Imkerei

1_1_1_CommercialAgriculturalProduction

Binnenfischerei

1_4_2_ProfessionalFishing

Sonstiges

1_1_Agriculture

FP_LandwirtschaftsFlaeche

1_1_Agriculture

LandwirtschaftAllgemein

1_1_Agriculture

Ackerbau

1_1_1_CommercialAgriculturalProduction

WiesenWeidewirtschaft

1_1_1_CommercialAgriculturalProduction

GartenbaulicheErzeugung

1_1_1_CommercialAgriculturalProduction

Obstbau

1_1_1_CommercialAgriculturalProduction

Weinbau

1_1_1_CommercialAgriculturalProduction

Imkerei

1_1_1_CommercialAgriculturalProduction

Binnenfischerei

1_4_2_ProfessionalFishing

Sonstiges

1_1_Agriculture

BP_WaldFlaeche

1_2_Forestry

Naturwald

6_3_1_LandAreasInNaturalUse

Nutzwald

1_2_Forestry

Erholungswald

3_4_4_OpenAirRecreationalAreas

Schutzwald

6_3_1_LandAreasInNaturalUse

FlaecheForstwirtschaft

1_2_Forestry

Sonstiges

1_2_Forestry

FP_Wald

1_2_Forestry

Naturwald

6_3_1_LandAreasInNaturalUse

Nutzwald

1_2_Forestry

Erholungswald

3_4_4_OpenAirRecreationalAreas

Schutzwald

6_3_1_LandAreasInNaturalUse

FlaecheForstwirtschaft

1_2_Forestry

Sonstiges

1_2_Forestry

BP_KleintierhaltungFlaeche

1_1_3_AgriculturalProductionForOwnComsumption

BP_Schutzgebiet

6_OtherUse

SO_SchutzgebietNaturschutzrecht

6_OtherUse

BP_SchutzPflege

6_OtherUse

Entwicklungsmassnahme

 

BP_AusgleichsMassnahme

6_OtherUse

BP_AnpflanzungBindungErhaltung

6_OtherUse

BP_SchutzPflegeEntwicklungs

6_OtherUse

Flaeche

 

BP_AusgleichsFlaeche

6_OtherUse

FP_AusgleichsFlaeche

6_OtherUse

FP_SchutzPflegeEntwicklung

6_OtherUse

BP_KennzeichnungsFlaeche

6_OtherUse

FP_Kennzeichnung

6_OtherUse

BP_GenerischesObjekt

6_OtherUse

BP_UnverbindlicheVormerkung

6_OtherUse

FP_UnverbindlicheVormerkung

6_OtherUse

FP_GenerischesObjekt

6_OtherUse

FP_VorbehalteFlaeche

6_OtherUse

FP_PrivilegiertesVorhaben

6_OtherUse

BP_VerEntsorgung

4_3_Utilities

Elektrizitaet

4_3_1_ElectricityGasAndThemalPowerDistributionServices

Gas

4_3_1_ElectricityGasAndThemalPowerDistributionServices

Erdoel

4_3_1_ElectricityGasAndThemalPowerDistributionServices

Waermeversorgung

4_3_1_ElectricityGasAndThemalPowerDistributionServices

Trinkwasser

4_3_2_WaterAndSewageInfrastructure

Abwasser

4_3_2_WaterAndSewageInfrastructure

Regenwasser

4_3_2_WaterAndSewageInfrastructure

Abfallentsorgung

4_3_3_WasteTreatment

Ablagerung

4_3_3_WasteTreatment

Telekommunikation

4_3_4_OtherUtilities

Sonstiges

4_3_4_OtherUtilities

FP_VerEntsorgung

4_3_Utilities

Elektrizitaet

4_3_1_ElectricityGasAndThemalPowerDistributionServices

Gas

4_3_1_ElectricityGasAndThemalPowerDistributionServices

Erdoel

4_3_1_ElectricityGasAndThemalPowerDistributionServices

Waermeversorgung

4_3_1_ElectricityGasAndThemalPowerDistributionServices

Trinkwasser

4_3_2_WaterAndSewageInfrastructure

Abwasser

4_3_2_WaterAndSewageInfrastructure

Regenwasser

4_3_2_WaterAndSewageInfrastructure

Abfallentsorgung

4_3_3_WasteTreatment

Ablagerung

4_3_3_WasteTreatment

Telekommunikation

4_3_4_OtherUtilities

Sonstiges

4_3_4_OtherUtilities

BP_Verkehrsflaeche

4_1_5_OtherTransportNetwork

BesondererZweckbestimmung

 

Parkierungsflaeche

4_1_5_OtherTransportNetwork

Fussgaengerbereich

4_1_5_OtherTransportNetwork

VerkehrsberuhigterBereich

4_1_5_OtherTransportNetwork

RadFussweg

4_1_5_OtherTransportNetwork

Radweg

4_1_5_OtherTransportNetwork

Fussweg

4_1_5_OtherTransportNetwork

Wanderweg

4_1_5_OtherTransportNetwork

Wirtschaftsweg

4_1_5_OtherTransportNetwork

FahrradAbstellplatz

4_1_5_OtherTransportNetwork

UeberfuehrenderVerkehrsweg

4_1_5_OtherTransportNetwork

UnterfuehrenderVerkehrsweg

4_1_5_OtherTransportNetwork

P_RAnlage

4_1_5_OtherTransportNetwork

Platz

4_1_5_OtherTransportNetwork

Anschlussflaeche

4_1_5_OtherTransportNetwork

LandwirtschaftlicherVerkehr

4_1_5_OtherTransportNetwork

Verkehrsgruen

4_1_5_OtherTransportNetwork

Sonstiges

4_1_5_OtherTransportNetwork

FP_Strassenverkehr

4_1_1_RoadTraffic

Autobahn

4_1_1_RoadTraffic

Hauptverkehrsstrasse

4_1_1_RoadTraffic

SonstigerVerkehrswegAnlage

4_1_1_RoadTraffic

RuhenderVerkehr

4_1_1_RoadTraffic

Sonstiges

4_1_1_RoadTraffic

SO_Strassenverkehrsrecht

4_1_1_RoadTraffic

Bundesautobahn

4_1_1_RoadTraffic

Bundesstrasse

4_1_1_RoadTraffic

LandesStaatsstrasse

4_1_1_RoadTraffic

Kreisstrasse

4_1_1_RoadTraffic

SonstOeffentlStrasse

4_1_1_RoadTraffic

BP_StrassenVerkehrsFlaeche

4_1_1_RoadTraffic

SO_Schienenverkehrsrecht

4_1_2_RailwayTraffic

Bahnanlage

4_1_2_RailwayTraffic

Bahnlinie

4_1_2_RailwayTraffic

OEPNV

4_1_2_RailwayTraffic

Sonstiges

4_1_2_RailwayTraffic

SO_Luftverkehrsrecht

4_1_3_AirTraffic

Flughafen

4_1_3_AirTraffic

Landeplatz

4_1_3_AirTraffic

Segelfluggelaende

4_1_3_AirTraffic

HubschrauberLandeplatz

4_1_3_AirTraffic

Ballonstartplatz

4_1_3_AirTraffic

Haengegleiter

4_1_3_AirTraffic

Gleitsegler

4_1_3_AirTraffic

Sonstiges

4_1_3_AirTraffic

BP_GewaesserFlaeche

6_3_2_WaterAreasInNaturalUse

Hafen

4_1_4_WaterTraffic

Wasserflaeche

6_3_2_WaterAreasInNaturalUse

Fliessgewaesser

6_3_2_WaterAreasInNaturalUse

Sonstiges

6_3_2_WaterAreasInNaturalUse

FP_Gewaesser

6_3_2_WaterAreasInNaturalUse

Hafen

4_1_4_WaterTraffic

Wasserflaeche

6_3_2_WaterAreasInNaturalUse

Fliessgewaesser

6_3_2_WaterAreasInNaturalUse

Sonstiges

6_3_2_WaterAreasInNaturalUse

BP_WasserwirtschaftsFlaeche

6_OtherUse

FP_Wasserwirtschaft

6_OtherUse

SO_Wasserrecht

6_OtherUse

Gewaesser1Ordnung

6_3_2_WaterAreasInNaturalUse

Gewaesser2Ordnung

6_3_2_WaterAreasInNaturalUse

Gewaesser3Ordnung

6_3_2_WaterAreasInNaturalUse

Ueberschwemmungsgebiet

6_OtherUse

Festgesetztes

6_OtherUse

Ueberschwemmungsgebiet

 

NochNichtFestgesetztes

6_OtherUse

Ueberschwemmungsgebiet

 

UeberschwemmGefaehrdetesGebiet

6_OtherUse

Sonstiges

6_OtherUse

SO_SchutzgebietWasserrecht

6_OtherUse

SO_Denkmalschutzrecht

6_OtherUse

SO_Forstrecht

6_OtherUse

SO_Bodenschutzrecht

6_OtherUse

SO_SonstigesRecht

6_OtherUse

Bauschutzbereich

6_OtherUse

Berggesetz

6_OtherUse

Richtfunkverbindung

6_OtherUse

Truppenuebungsplatz

3_3_1_PublicAdministrationDefenseAndSocialSecurityServices

VermessungsKatasterrecht

6_OtherUse

Sonstiges

6_OtherUse

SO_SchutzgebietSonstRecht

6_OtherUse

SO_Gebiet

6_OtherUse

Mapping from Dutch LGN to HILUCS

LGN: Code (Main class/Sub class) Class HILUCS code

1: (Agriculture) pasture

1_1_1

2: (Agriculture) maize

1_1_1

3: (Agriculture) potatoes

1_1_1

4: (Agriculture) sugar beet

1_1_1

5: (Agriculture) cereals

1_1_1

6: (Agriculture) other agricultural crops

1_1_1

61: (Agriculture) tree nurseries

1_1_1

62: (Agriculture) fruit cultivation

1_1_1

8: (Agriculture) greenhouses

1_1_1

9: (Agriculture) orchards

1_1_1

10: (Agriculture) flower bulbs

1_1_1

26: (Agriculture) built-up areas outside urban areas

5_1

11: (Forest) deciduous forest

1_2

12: (Forest) coniferous forest

1_2

16: (Water) fresh water

6_3_2
4_1_4

17: (Water) salt water

6_3_2

18: (Urban) urban built-up areas

5_1
3_2
3_1
2

19: (Urban) semi urban built-up areas

3_3
5_2
4_3

20: (Urban) forest in built-up areas

3_4_4
5_2

22: (Urban) forest in semi built-up areas

3_4_4
5_2

23: (Urban) grass in built-up areas

5_2
3_2
3_1
2

24: (Urban) bare soil in built-up areas

5_3

28: (Urban) grass in semi built-up areas

3_4_4
5_2
1_3_3
3_3
4_3

25: (Infrastructure) main roads & railways

4_1_1
4_1_2

30: (Natural/Coastal) mudflats

6_3_1

31: (Natural/Coastal) coastal sands

6_3_1

32: (Natural/Coastal) dune areas with low vegetation

6_3_1

33: (Natural/Coastal) dune areas with high vegetation

6_3_1

34: (Natural/Coastal) heathland in coastal areas

6_3_1

35: (Natural/Moors&heathland) drifting sands / river sandbanks

6_3_1

36: (Natural/Moors&heathland) heathland

6_3_1

37: (Natural/Moors&heathland) grassy heathland

6_3_1

38: (Natural/Moors&heathland) very grassy heathland

6_3_1

39: (Natural/Peat bogs) raised bogs

6_3_1

40: (Natural/Peat bogs) forest in raised bogs

6_3_1

41: (Natural/Swamp) other swamp vegetation

6_3_1

42: (Natural/Swamp) reeds

6_3_1

43: (Natural/Swamp)forest in swamp areas

6_3_1

45:natural grasslands

6_3_1

Mapping from Dutch BBG to HILUCS

TemplateCode Value HILUCS code

1 Transport

10: Railroad

4_1_2

11: Main road

4_1_1

12: Airport

4_1_3

 2 Built-up area 

20: Residential

5

21: Retail trade, hotel and catering

3_1_1

22: Public institutions

4_3_2
3_3_1
4_3_1

23: Socio-cultural facility

3_3_2
3_3_3
3_4_1
3_4_2

24: Industrial area and offices

3_2
2

 3 Semi built-up 

30: Dumping site

4_3_3

31: Car wreck site

4_3_3

32: Cemetery

3_3_5

33: Mining area

1_3_3

34: Building site

6_1

35: Other semi built-up area

6_5

4 Recreation 

40: Park and public garden

3_4_4

41: Sports ground (incl. car parks)

3_4_3

42: Allotment garden

3_4_4
1_1_3

43: Area for daytrips

3_4_4

44: Holiday recreation

3_4_5
5_3

5 Agriculture

50: Greenhouses

1_1_1

51: Other agricultural usage

1_1_1

6 Woodland and Nature 

60: Woodland

1_2

61: Dry natural area

6_3_1

62: Wet natural area

6_3_1

 7 Inland water

70: "IJsselmeer/Markermeer"

6_3_2

71: Enclosed estuary

6_3_2

72: "Rijn & Maas"

4_1_4

73: "Randmeer "

6_3_2

74: Water reservoir

4_3_2

75: Water with recreational usage

3_4_4

76: Water where minerals are extracted

1_3_3

77: Area for storing industrial water

4_3_3

78: Other inland water

6_3_2

 8 Tidal waters

80: "Waddenzee, Eems, Dollard"

6_3_2

81: "Oosterschelde"

6_3_2

82: "Westerschelde"

6_3_2

83: "Noordzee"

6_3_2

9 Foreign countries

90: Foreign countries

 

Mapping from SIOSE classes (Spain) to HILUCS

SIOSE Class (Español / English) HILUCS code

Cultivo de arroz / Rice

1_1_1_CommercialAgriculturalProduction

Cultivos herbaceos distintos de arroz / Herbaceous other than rice

1_1_1_CommercialAgriculturalProduction

Cultivos leñosos de frutales cítricos / Citrus fruit trees

1_1_1_CommercialAgriculturalProduction

Cultivos leñosos de frutales no cítricos / Non-citrus fruit trees

1_1_1_CommercialAgriculturalProduction

Viñedo / Vineyard

1_1_1_CommercialAgriculturalProduction

Olivar / Olive grove

1_1_1_CommercialAgriculturalProduction

Otros cultivos leñosos / Other woody crops

1_1_1_CommercialAgriculturalProduction

Prados / Pastures

1_1_1_CommercialAgriculturalProduction

Olivar y Viñedo / Olive grove-vineyard

1_1_1_CommercialAgriculturalProduction

Agrícola-Ganadero / Farming

1_1_2_FarmingInfrastructure

Asentamiento agrícola residencial / Agricultural settlement

1_1_3_AgriculturalProductionForOwnComsumption

Huerta familiar / Home orchard

1_1_3_AgriculturalProductionForOwnComsumption

Primario forestal / Logging

1_2_Forestry

Attribute: Función de cortafuegos / firebreak function

1_2_Forestry

Attribute: Cortas / clear cuts

1_2_Forestry

Minero-extractivo / Mining

1_3_Mining and quarrying

Piscifactoría / Fish farming

1_4_1_Aquaculture

Polígono industrial ordenado / Planned industrial park

2_SecondaryProduction

Polígono industrial sin ordenar / Non-planned industrial park

2_SecondaryProduction

Industria aislada / Isolated industry

2_SecondaryProduction

Nuclear / Nuclear

2_4_1_Nuclear

Térmica / Thermal

2_4_2_Fossil

Eólica / Wind power

2_4_4_Renewable

Solar / Solar

2_4_4_Renewable

Hidroeléctrica / Hydroelectric

2_4_4_Renewable

Comercial y oficinas / Commercial and business park

3_1_CommercialServices

Telecomunicaciones / Telecommunications

3_2_3_InformationAndCommunicationServices

Administrativo Institucional / Government

3_3_1_PublicAdministrationDefenseAndSocialSecurityServices

Penintenciario / Penitentiary

3_3_1_PublicAdministrationDefenseAndSocialSecurityServices

Educación / Educational

3_3_2_EducationalServices

Sanitario / Health

3_3_3_HealthAndSocialServices

Religioso / Religious

3_3_4_ReligiousServices

Cementerio / Cemetery

3_3_5_OtherCommunityServices

Cultural / Cultural

3_4_1_CulturalServices

Parque recreativo / Amusement park

3_4_2_EntertainmentServices

Deportivo / Sports

3_4_3_SportsInfrastructure

Campo de golf / Golf course

3_4_3_SportsInfrastructure

Camping / Campsite

3_4_4_OpenAirRecreationalAreas

Parque urbano / Urban park

3_4_4_OpenAirRecreationalAreas

Zona verde artificial / Green urban area

3_4_4_OpenAirRecreationalAreas

Complejo hotelero / Hotel resort

3_5_OtherServices

Red viaria / Road network

4_1_1_RoadTraffic

Vial, aparcamiento o zona peatonal / Roads, parking lots and other artificial surfaces

4_1_1_RoadTraffic

Red ferroviaria / Rail network

4_1_2_RailwayTraffic

Aeroportuario / Airport

4_1_3_AirTraffic

Portuario / Port

4_1_4_WaterTraffic

Eléctrica / Electric

4_3_1_Electricity_GasAndThemalPowerDistributionServices

Gaseoducto-Oleoducto / Pipeline

4_3_1_Electricity_GasAndThemalPowerDistributionServices

Depuradoras y potabilizadoras / Water treatment

4_3_2_WaterAndSewageInfrastructure

Conducciones y canales / Water supply network

4_3_2_WaterAndSewageInfrastructure

Desalinizadora / Desalination plant

4_3_2_WaterAndSewageInfrastructure

Vertederos y escombreras / Dump site

4_3_3_WasteTreatment

Plantas de tratamiento / Waste treatment plant

4_3_3_WasteTreatment

Depending on density(=percentage) of residential buildings and other uses' buildings:
Urbano discontinuo / Discontinuous

5_1_PureResidentialUse
5_2_ResidentialUseWithOtherCompatibleUse

Depending on density(=percentage) of residential buildings and other uses' buildings:
Ensanche urbano / Urban expansion area

5_1_PureResidentialUse
5_2_ResidentialUseWithOtherCompatibleUse

Depending on density(=percentage) of residential buildings and other uses' buildings:
Casco urbano / Town centre

5_1_PureResidentialUse
5_2_ResidentialUseWithOtherCompatibleUse

Attribute: En construcción / under construction

6_1_TransitionalAreas

Playas, dunas y arenales / Beaches, dunes and sand plains

6_3_1_LandAreasNotInOtherUse

Rambla / Dry riverbed

6_3_1_LandAreasNotInOtherUse

Zonas pantanosas / Marshes

6_3_1_LandAreasNotInOtherUse

Turberas / Peat bogs

6_3_1_LandAreasNotInOtherUse

Salinas continentales / Inland salines

6_3_1_LandAreasNotInOtherUse

Marismas / Coastal marshes

6_3_1_LandAreasNotInOtherUse

Salinas marinas / Coastal salines

6_3_1_LandAreasNotInOtherUse

Dehesa / Dehesa

6_3_1_LandAreasNotInOtherUse

Pastizal / Grassland

6_3_1_LandAreasNotInOtherUse

Frondosas caducifolias / Deciduous broad-leaved

6_3_1_LandAreasNotInOtherUse

Frondosas perennifolias / Evergreen broad-leaved

6_3_1_LandAreasNotInOtherUse

Coníferas / Coniferous

6_3_1_LandAreasNotInOtherUse

Matorral / Shrub

6_3_1_LandAreasNotInOtherUse

Suelo desnudo / Bare soil

6_3_1_LandAreasNotInOtherUse

Zonas quemadas / Burnt areas

6_3_1_LandAreasNotInOtherUse

Glaciares y nieves perpetuas / Glaciers and perpetual snow

6_3_1_LandAreasNotInOtherUse

Acantilados marinos / Sea cliff

6_3_1_LandAreasNotInOtherUse

Afloramientos rocosos y roquedo / Outcrop

6_3_1_LandAreasNotInOtherUse

Canchales / Scree

6_3_1_LandAreasNotInOtherUse

Colada lávica / Quaternary lava flow

6_3_1_LandAreasNotInOtherUse

Cursos de agua / Water courses

6_3_2_WaterAreasNotInOtherUse

Lagos y lagunas / Lakes and lagoons

6_3_2_WaterAreasNotInOtherUse

Embalse / Reservoir

6_3_2_WaterAreasNotInOtherUse

Lagunas costeras / Coastal lagoons

6_3_2_WaterAreasNotInOtherUse

Estuario / Estuaries

6_3_2_WaterAreasNotInOtherUse

Mares y océanos / Sea and ocean

6_3_2_WaterAreasNotInOtherUse

Edificación / Buildings

6_6_NotKnownUse

Lámina de agua artificial / Artificial water body

6_6_NotKnownUse

Otras construcciones / Other constructions

6_6_NotKnownUse

Suelo no edificado / Non-built soil

6_6_NotKnownUse

Zonas de extracción o vertido / Extraction and dumping

6_6_NotKnownUse

Mapping from MCA of Navarra (Spain) to HILUCS

MCA Class (Español / English) HILUCS code

Cultivos herbaceos / Herbaceous

1_1_1_CommercialAgriculturalProduction

Aromáticas/ Aromatics

1_1_1_CommercialAgriculturalProduction

Invernaderos/Forced crops

1_1_1_CommercialAgriculturalProduction

Albaricoque/Apricot tree

1_1_1_CommercialAgriculturalProduction

Almendro/Almond tree

1_1_1_CommercialAgriculturalProduction

Cerezo/Cherry tree

1_1_1_CommercialAgriculturalProduction

Ciruelo/Plum tree

1_1_1_CommercialAgriculturalProduction

Kiwi/Kiwi

1_1_1_CommercialAgriculturalProduction

Manzano/Apple Tree

1_1_1_CommercialAgriculturalProduction

Membrillo/Quince Tree

1_1_1_CommercialAgriculturalProduction

Melocotón/Peach Tree

1_1_1_CommercialAgriculturalProduction

Nogal/Walnut tree

1_1_1_CommercialAgriculturalProduction

Peral/Pear tree

1_1_1_CommercialAgriculturalProduction

Vivero viña/Vine nursery

1_1_1_CommercialAgriculturalProduction

Vivero forestal/Forestry nursery

1_1_1_CommercialAgriculturalProduction

Pacharán/Sloe bush

1_1_1_CommercialAgriculturalProduction

Viñedo / Vineyard

1_1_1_CommercialAgriculturalProduction

Olivar / Olive grove

1_1_1_CommercialAgriculturalProduction

Prados / Pastures

1_1_1_CommercialAgriculturalProduction

Agrícola-Ganadero / Farming

1_1_2_FarmingInfrastructure

Asentamiento agrícola residencial / Agricultural settlement

1_1_3_AgriculturalProductionForOwnComsumption

Huerta familiar / Home orchard

1_1_3_AgriculturalProductionForOwnComsumption

Primario forestal / Logging

1_2_Forestry

Minero-extractivo / Mining

1_3_Mining and quarrying

Piscifactoría / Fish farming

1_4_1_Aquaculture

Polígono industrial ordenado / Planned industrial park

2_SecondaryProduction

Polígono industrial sin ordenar / Non-planned industrial park

2_SecondaryProduction

Industria aislada / Isolated industry

2_SecondaryProduction

Nuclear / Nuclear

2_4_1_Nuclear

Térmica / Thermal

2_4_2_Fossil

Eólica / Wind power

2_4_4_Renewable

Solar / Solar

2_4_4_Renewable

Hidroeléctrica / Hydroelectric

2_4_4_Renewable

Comercial y oficinas / Commercial and business park

3_1_CommercialServices

Telecomunicaciones / Telecommunications

3_2_3_Information_and communication services

Administrativo Institucional / Government

3_3_1_PublicAdministrationDefenseAndSocialSecurityServices

Penintenciario / Penitentiary

3_3_1_PublicAdministrationDefenseAndSocialSecurityServices

Educación / Educational

3_3_2_EducationalServices

Sanitario / Health

3_3_3_HealthAndSocialServices

Religioso / Religious

3_3_4_ReligiousServices

Cementerio / Cemetery

3_3_5_OtherCommunityServices

Cultural / Cultural

3_4_1_CulturalServices

Parque recreativo / Amusement park

3_4_2_EntertainmentServices

Deportivo / Sports

3_4_3_SportsInfrastructure

Campo de golf / Golf course

3_4_3_SportsInfrastructure

Camping / Campsite

3_4_4_OpenAirRecreationalAreas

Parque urbano / Urban park

3_4_4_OpenAirRecreationalAreas

Zona verde artificial / Green urban area

3_4_4_OpenAirRecreationalAreas

Complejo hotelero / Hotel resort

3_5_OtherServices

Red viaria / Road network

4_1_1_RoadTraffic

Vial, aparcamiento o zona peatonal / Roads, parking lots and other artificial surfaces

4_1_1_RoadTraffic

Red ferroviaria / Rail network

4_1_2_RailwayTraffic

Aeroportuario / Airport

4_1_3_AirTraffic

Portuario / Port

4_1_4_WaterTraffic

Eléctrica / Electric

4_3_1_Electricity_GasAndThemalPowerDistributionServices

Gaseoducto-Oleoducto / Pipeline

4_3_1_Electricity_GasAndThemalPowerDistributionServices

Depuradoras y potabilizadoras / Water treatment

4_3_2_WaterAndSewageInfrastructure

Conducciones y canales / Water supply network

4_3_2_WaterAndSewageInfrastructure

Vertederos y escombreras / Dump site

4_3_3_WasteTreatment

Plantas de tratamiento / Waste treatment plant

4_3_3_WasteTreatment

Depending on density(=percentage) of residential buildings and other uses' buildings:
Urbano discontinuo / Discontinuous

5_1_PureResidentialUse
5_2_ResidentialUseWithOtherCompatibleUse

Depending on density(=percentage) of residential buildings and other uses' buildings:
Ensanche urbano / Urban expansion area

5_1_PureResidentialUse
5_2_ResidentialUseWithOtherCompatibleUse

Depending on density(=percentage) of residential buildings and other uses' buildings:
Casco urbano / Town centre

5_1_PureResidentialUse
5_2_ResidentialUseWithOtherCompatibleUse

Attribute: En construcción / under construction

6_1_TransitionalAreas

Salinas continentales / Inland salines

6_3_1_LandAreasNotInOtherUse

Pastizal / Grassland

6_3_1_LandAreasNotInOtherUse

Suelo desnudo / Bare soil

6_3_1_LandAreasNotInOtherUse

Zonas quemadas / Burnt areas

6_3_1_LandAreasNotInOtherUse

Glaciares y nieves perpetuas / Glaciers and perpetual snow

6_3_1_LandAreasNotInOtherUse

Acantilados marinos / Sea cliff

6_3_1_LandAreasNotInOtherUse

Afloramientos rocosos y roquedo / Outcrop

6_3_1_LandAreasNotInOtherUse

Canchales / Scree

6_3_1_LandAreasNotInOtherUse

Helechal/ (Pteridium aquilinum)

6_3_1_LandAreasNotInOtherUse

Brezal/Heather-Gorse

6_3_1_LandAreasNotInOtherUse

Bojeral/(Buxus sempervirens)

6_3_1_LandAreasNotInOtherUse

Carrizal/(Phragmites australis)

6_3_1_LandAreasNotInOtherUse

Coscojar/(Quercus coccifera)

6_3_1_LandAreasNotInOtherUse

Enebral/(Juniperus sp.)

6_3_1_LandAreasNotInOtherUse

Espartal/(Lygeum spartum)

6_3_1_LandAreasNotInOtherUse

Matorral mediterráneo/Mediterranean scrubland

6_3_1_LandAreasNotInOtherUse

Retamar/(Cytisus scoparius)

6_3_1_LandAreasNotInOtherUse

Matorral zarzas/Thornbush-Brambles

6_3_1_LandAreasNotInOtherUse

Pastos de alta montaña/High mountain pasture

6_3_1_LandAreasNotInOtherUse

Juncal/(Juncus sp.)

6_3_1_LandAreasNotInOtherUse

Cornejo/(Cornus sp.)

6_3_1_LandAreasNotInOtherUse

Lentisco/(Pistacia lentiscus)

6_3_1_LandAreasNotInOtherUse

Majuelo/(Crataegus sp.)

6_3_1_LandAreasNotInOtherUse

Otabera/(Genista occidentalis)

6_3_1_LandAreasNotInOtherUse

Zumaque/(Rhus coriaria)

6_3_1_LandAreasNotInOtherUse

Arce (Acer sp.)

6_3_1_LandAreasNotInOtherUse

Aliso (Alnus sp.)

6_3_1_LandAreasNotInOtherUse

Madroño (Arbutus unedo)

6_3_1_LandAreasNotInOtherUse

Abedul (Betula celtiberica, B.pendula)

6_3_1_LandAreasNotInOtherUse

Avellano (Corylus avellana)

6_3_1_LandAreasNotInOtherUse

Carpe (Carpinus betulus)

6_3_1_LandAreasNotInOtherUse

Espino (Crataegus sp.)

6_3_1_LandAreasNotInOtherUse

Castaño (Castanea sativa)

6_3_1_LandAreasNotInOtherUse

Fresno de hoja estrecha (Fraxinus angustifolia)

6_3_1_LandAreasNotInOtherUse

Fresno común (Fraxinus excelsior)

6_3_1_LandAreasNotInOtherUse

Haya (Fagus sylvatica)

6_3_1_LandAreasNotInOtherUse

Acebo (Ilex aquifolium)

6_3_1_LandAreasNotInOtherUse

Labiérnago (Phillyrea sp.)

6_3_1_LandAreasNotInOtherUse

Plátano (Platanus hybrida)

6_3_1_LandAreasNotInOtherUse

Chopo y álamo (Populus sp.)

6_3_1_LandAreasNotInOtherUse

Quejigo (Quercus faginea)

6_3_1_LandAreasNotInOtherUse

Encina (Quercus ilex)

6_3_1_LandAreasNotInOtherUse

Roble pubescente (Quercus pubescens)

6_3_1_LandAreasNotInOtherUse

Roble albar (Quercus petraea)

6_3_1_LandAreasNotInOtherUse

Marojo (Quercus pyrenaica)

6_3_1_LandAreasNotInOtherUse

Roble pedunculado (Quercus robur)

6_3_1_LandAreasNotInOtherUse

Carrasca (Quercus rotundifolia)

6_3_1_LandAreasNotInOtherUse

Roble americano (Quercus rubra)

6_3_1_LandAreasNotInOtherUse

Acacia (Robinia pseudoacacia)

6_3_1_LandAreasNotInOtherUse

Sauce (Salix sp.)

6_3_1_LandAreasNotInOtherUse

Tamariz (Tamarix sp.)

6_3_1_LandAreasNotInOtherUse

Tilo (Tilia platyph

6_3_1_LandAreasNotInOtherUse

Olmo (Ulmus sp.)

6_3_1_LandAreasNotInOtherUse

Serbal (Sorbus sp.)

6_3_1_LandAreasNotInOtherUse

Cerezo (Prunus sp.)

6_3_1_LandAreasNotInOtherUse

Nogal (Juglans regia)

6_3_1_LandAreasNotInOtherUse

Avellano/Hazlenut

6_3_1_LandAreasNotInOtherUse

Chopera/Poplar

6_3_1_LandAreasNotInOtherUse

Árbol del paraíso (Eleagnus angustifolia)

6_3_1_LandAreasNotInOtherUse

Almez (Celtis australis)

6_3_1_LandAreasNotInOtherUse

Abeto blanco (Abies alba)

6_3_1_LandAreasNotInOtherUse

Cedro (Cedrus sp.)

6_3_1_LandAreasNotInOtherUse

Ciprés de Lawson (Chamaecyparis lawsoniana)

6_3_1_LandAreasNotInOtherUse

Ciprés (Cupressus sp.)

6_3_1_LandAreasNotInOtherUse

Enebro común (Juniperus communis)

6_3_1_LandAreasNotInOtherUse

Enebro de la miera (Juniperus oxycedrus)

6_3_1_LandAreasNotInOtherUse

Sabina negra (Juniperus phoenicea)

6_3_1_LandAreasNotInOtherUse

Alerce (Larix sp.)

6_3_1_LandAreasNotInOtherUse

Abeto rojo (Picea abies)

6_3_1_LandAreasNotInOtherUse

Pino banksiana (Pinus banksiana)

6_3_1_LandAreasNotInOtherUse

Pino carrasco (Pinus halepensis)

6_3_1_LandAreasNotInOtherUse

Abeto Douglas (Pseudotsuga menziesii)

6_3_1_LandAreasNotInOtherUse

Pino laricio (Pinus nigra)

6_3_1_LandAreasNotInOtherUse

Pino piñonero (Pinus pinea)

6_3_1_LandAreasNotInOtherUse

Pino insigne (Pinus radiata)

6_3_1_LandAreasNotInOtherUse

Pino silvestre (Pinus sylvestris)

6_3_1_LandAreasNotInOtherUse

Picea de Sitka (Picea sitchensis)

6_3_1_LandAreasNotInOtherUse

Pino estrobus (Pinus strobus)

6_3_1_LandAreasNotInOtherUse

Pino negro (Pinus uncinata)

6_3_1_LandAreasNotInOtherUse

Tejo (Taxus baccata)

6_3_1_LandAreasNotInOtherUse

Sequoia (Sequoia sempervirens)

6_3_1_LandAreasNotInOtherUse

Criptomeria (Criptomeria japonica)

6_3_1_LandAreasNotInOtherUse

Cursos de agua / Water courses

6_3_2_WaterAreasNotInOtherUse

Lagos y lagunas / Lakes and lagoons

6_3_2_WaterAreasNotInOtherUse

Embalse / Reservoir

6_3_2_WaterAreasNotInOtherUse

Balsa de riego/irrigation pool

6_3_2_WaterAreasNotInOtherUse

Edificación / Buildings

6_6_NotKnownUse

Lámina de agua artificial / Artificial water body

6_6_NotKnownUse

Otras construcciones / Other constructions

6_6_NotKnownUse

Suelo no edificado / Non-built soil

6_6_NotKnownUse

Zonas de extracción o vertido / Extraction and dumping

6_6_NotKnownUse

Annex E: Hierarchical Supplementary Regulation Code List - (informative)

E.1. Introduction

During the consultation process, comments have been provided related to the possible values for the attribute supplementaryRegulation. In the testing material, CZ, FR and DE provided files showing the matching between national code list and the list provided in the LU data specification version 2.0. The analysis of the testing report also provides other input and the code list associated with the attribute zoneTypeCode of the feature ManagementRestrictionOrRegulationZone in the AM data specification influences the list philosophy.

The next section provides the first draft of the future INSPIRE Hierarchical supplementary Regulation code list provided in this LU data specification.

Three entries from the AM data specification have been set aside (riverBasinDistrict[multiblock footnote omitted], marineRegion[multiblock footnote omitted] and animalHealthRestrictionZone[multiblock footnote omitted]) as not being perceived as a supplementary regulation.

Two main categories of supplementary regulation can be defined from the current list:

  • Supplementary regulation that is imported in the spatial plan from regulations that externally condition the spatial plan often due to legislations other than spatial planning laws (1_ImpactOnEnvironement, 2_RiskExposure, 3_HeritageProtection, 4_GeneralInterest

  • Supplementary regulation that is defined within the spatial plan by the competent authority responsible for the spatial plan (5_LandPropertyRight, 6_RegulationsOnBuildings, 7_LocalRegionalStateDevelopmentPolicies, 8_SocialHealthChoices, 9_RegulatedActivities)

A last category 10_OtherSupplementaryRegulation is provided in order to enable room for supplementary regulation types that has not been foreseen.

Supplementary regulation that is inherited from spatial plan that have legal precedence (e.g. area of a zoning plan where restrictions are imposed by a structure plan) (previously 10_PlansWithLegalPrecedence in LU-DS 2.0) is now seen as a qualifier for any supplementary regulation. In the PLU data model a boolean attribute of the feature type "SupplementaryRegulation" called "inheritedFromPlanWithLegalPrecedence" implements the qualifier.

E.2. Proposed Hierarchical Supplementary Regulation Code List (HSRCL)

The code list is provided in Annex C.

E.3. Examples of mapping HSRCL with national coding systems

This section is a contribution of the experts of the TWG-LU. IT is their vision of how national code lists could be mapped with HSRCL. Note that the national terminology is kept in the national language as well as the definition of terms where applicable.

E.3.1. Mapping with CNIG (France) code list

Value Code Definition HSRCL code

PrescriptionUrbaType

Nature de la contrainte imposée par une prescription figurant dans un document d’urbanisme

 

espace boisé classé (R123-11 a)

1

.

1_4_3

secteur avec limitation de la constructibilité ou de l’occupation pour des raisons de nuisances ou de risques (R123-11b)

2

Secteurs où les nécessités du fonctionnement des services publics, de l’hygiène, de la protection contre les nuisances et de la préservation des ressources naturelles ou l’existence de risques naturels, tels que inondations, incendies de forêt, érosion, affaissements, éboulements, avalanches, ou de risques technologiques justifient que soient interdites ou soumises à des conditions spéciales les constructions et installations de toute nature, permanentes ou non, les plantations, dépôts, affouillements, forages et exhaussements des sols

2

secteur avec disposition de reconstruction /démolition (R123-1 10 et R123-11 f)

3

Secteurs dans lesquels la délivrance du permis de construire peut être subordonnée à la démolition de tout ou partie des bâtiments existants sur le terrain où l’implantation de la construction est envisagée

5_4

périmètre issu des PDU sur obligation de stationnement (R123-11 g)

4

Périmètres, tels que délimités par le plan de déplacements urbains en application de l’article 28-1-2 de la loi nº82-1153 du 30 décembre 1982 modifiée, à l’intérieur desquels les conditions de desserte par les transports publics réguliers permettent de réduire ou de supprimer les obligations imposées en matière de réalisation d’aires de stationnement, notamment lors de la construction d’immeubles de bureaux, ou à l’intérieur desquels le plan local d’urbanisme fixe un nombre maximum d’aires de stationnement à réaliser lors de la construction de bâtiments à usage autre que d’habitation

7_5_2

emplacement réservé (L123-1 8 et R123-11 d)

5

Emplacements réservés aux voies et ouvrages publics, aux installations d’intérêt général et aux espaces verts, en précisant leur destination et les collectivités, services et organismes publics bénéficiaires

7_3

secteur à densité maximale pour les reconstructions ou aménagements de bâtiments existants (L123-1-5 et R123-11 e)

6

Secteurs dans lesquels, pour des motifs d’urbanisme ou d’architecture, la reconstruction sur place ou l’aménagement de bâtiments existants peut être imposé ou autorisé avec une densité au plus égale à celle qui existait antérieurement, nonobstant le ou les coefficients d’occupation du sol fixés pour la zone ou le secteur

6_7

élément de paysage (bâti et espaces), de patrimoine, point de vue à protéger, à conserver (L123-1 9 et R123-11 h)

7

Éléments de paysage, les quartiers, îlots, immeubles, espaces publics, monuments, sites et secteurs à protéger ou à mettre en valeur pour des motifs d’ordre culturel, historique ou écologique, et notamment les secteurs dans lesquels la démolition des immeubles est subordonnée à la délivrance d’un permis de démolir

3

terrain cultivé à protéger en zone urbaine (L123-1 9 et R123-12 1a)

8

Terrains cultivés à protéger et inconstructibles délimités en application du 9º de l’article L. 123-1

1_4_4

emplacement réservé logement social/mixité sociale (L123-2b et R123‑12 1c)

9

Emplacements réservés en application du b de l’article L. 123-2 en vue de la réalisation, dans le respect des objectifs de mixité sociale, de programmes de logements en précisant la nature de ces programmes

8_2

pré-emplacement réservé pour des équipements (R123-11 d)

10

Terrains concernés par la localisation des équipements mentionnés au d de l’article L. 123-2

5_6

limitations particulières d’implantation des constructions (bande constructible, marge de recul, zone non aedificandi, alignement, emprise de construction…​)

11

Règles d’implantation issues de sources telles que les règlements de ZAC, les règles de réciprocité…​

6.

secteur de projet en attente d’un projet d’aménagement global (R123-2 a et R123-12 1b)

12

Secteurs délimités en application du a de l’article L. 123-2 en précisant à partir de quelle surface les constructions ou installations sont interdites et la date à laquelle la servitude sera levée

7_4

zone à aménager en vue de la pratique du ski (L123-1 6 et R123-11 i)

13

Zones qui sont ou peuvent être aménagées en vue de la pratique du ski et les secteurs réservés aux remontées mécaniques en indiquant, le cas échéant, les équipements et aménagements susceptibles d’y être prévus

7_2_3

secteur de plan de masse (R123-12 4)

14

Secteurs pour lesquels un plan de masse coté à trois dimensions définit des règles spéciales

6_3

règles d’implantation des constructions par rapport aux voies et limites séparatives (R123-9 6° et 7°, et R123‑11)

15

Implantation des constructions par rapport aux voies, emprises publiques et limites séparatives (R123-9 et R123-11)

6_1

bâtiment agricole susceptible de changer de destination (R123-12 2)

16

Bâtiments agricoles qui, en raison de leur intérêt architectural ou patrimonial, peuvent faire l’objet d’un changement de destination, dès lors que ce changement de destination ne compromet pas l’exploitation agricole

3_3

secteur à programme de logements mixité sociale en Zone U et AU et secteur soumis à un quota de logements locatifs (L123-1 16 et L123-2 d)

17

Secteurs délimités en application du d de l’article L. 123-2 dans lesquels, en cas de réalisation d’un programme de logements, un pourcentage de ce programme doit être affecté à des catégories de logements locatifs qu’il définit dans le respect des objectifs de mixité sociale

8_1

secteur comportant des orientations d’aménagement (L123-1 et R123-3 1)

18

Les orientations d’aménagement peuvent, par quartier ou par secteur, prévoir les actions et opérations d’aménagement

7_6

secteur protégé en raison de la richesse du sol et du sous-sol

19

Secteurs protégés en raison de la richesse du sol ou du sous-sol, dans lesquels les constructions et installations nécessaires à la mise en valeur de ces ressources naturelles sont autorisées

7_2_7

secteur à transfert de COS en zone N (L123-4 et R123-12 3)

20

Secteurs protégés en raison de la qualité de leur paysage où est applicable le transfert des possibilités de construction prévu à l’article L. 123-4

3_2

terrain concerné par la localisation d’équipements en zone U, voies, ouvrages publics, espaces verts (L123-2c et R123-12 1d)

21

Localisation et caractéristiques des voies et ouvrages publics, ainsi que les installations d’intérêt général et les espaces verts à créer ou à modifier (L123-2c et R123-12 1d)

4_2

secteur de diversité commerciale à protéger (L123-1 7bis)

22

Secteur délimitant les quartiers, îlots, voies dans lesquels doit être préservée ou développée la diversité commerciale, notamment à travers les commerces de détail et de proximité (L123-1-7bis)

7_1_3_2

secteur avec taille minimale des logements en zone U et AU (L123-1 15)

23

Secteurs, dans les zones urbaines ou à urbaniser, pour lesquels les programmes de logements doivent comporter une proportion de logements d’une taille minimale (L123-1-15)

6_8

voies, chemins, transport public à conserver et à créer (L123-1 6)

24

Localisation et caractéristiques des voies de circulation à conserver, à modifier ou à créer (L123-1-6)

7_3_1_1

autre

99

 

10

InformationUrbaType

Nature du périmètre d’information figurant dans un document d’urbanisme

secteur sauvegardé (L313-1 et R123-13 1)

1

Secteurs sauvegardés, délimités en application des articles L. 313-1 et suivants

3

zone d’aménagement concerté (R123-13 2)

2

Zones d’aménagement concerté ZAC

7_4_1

zone de préemption dans un espace naturel et sensible (R123-13 3)

3

Zones de préemption délimitées en application de l’article L. 142-1 dans sa rédaction antérieure à la loi nº85-729 du 18 juillet 1985 relative à la définition et à la mise en oeuvre de principes d’aménagement et de l’article L. 142-3 dans sa rédaction issue de la même loi

3_1

périmètre de droit de préemption urbain (R123-13 4)

4

Périmètres à l’intérieur desquels s’applique le droit de préemption urbain défini par les articles L. 211-1 et suivants

5_2

zone d’aménagement différé (R123-13 4)

5

Périmètres provisoires ou définitifs des zones d’aménagement différé ZAD

7_4_2

zone d’obligation du permis de démolir (R123-13 5)

6

Zones délimitées en application de l’article L. 430-1 à l’intérieur desquelles s’appliquent les dispositions relatives au permis de démolir prévues aux articles L. 430-2 et suivants

7_5_3

périmètre de développement prioritaire économie d’énergie (R123-13 6)

7

Périmètres de développement prioritaires délimités en application de la loi nº80-531 du 15 juillet 1980 relative aux économies d’énergie et à l’utilisation de la chaleur

7_5_4

périmètre forestier : interdiction ou réglementation des plantations (code rural), plantations à réaliser (R123-13 7)

8

Périmètres d’interdiction ou de réglementation des plantations et semis d’essences forestières, les périmètres d’actions forestières et les périmètres de zones dégradées à faible taux de boisement, délimités en application des 1º, 2º et 3º de l’article L. 126-1 du code rural

1_4_3

périmètre minier de concession pour l’exploitation ou le stockage (R123-13 8)

9

Périmètres miniers définis en application des titres II, III et V du livre Ier du code minier

7_2_7_1

zone de recherche et d’exploitation de carrière (R123-13 9)

10

Périmètres de zones spéciales de recherche et d’exploitation de carrières et des zones d’exploitation et d’aménagement coordonné de carrières, délimités en application des articles 109 et 109-1 du code minier

7_2_7_1

périmètre des zones délimitées - divisions foncières soumises à déclaration préalable (R123-13 10)

11

Périmètres des zones délimitées en application de l’article L. 111-5-2 à l’intérieur desquelles certaines divisions foncières sont soumises à déclaration préalable

5_3

périmètre de sursis à statuer (R123-13 11)

12

Périmètres à l’intérieur desquels l’autorité compétente peut surseoir à statuer sur les demandes d’autorisation en application de l’article L. 111-10

7_5

secteur de programme d’aménagement d’ensemble (R123-13 12)

13

Périmètres des secteurs dans lesquels un programme d’aménagement d’ensemble a été approuvé en application de l’article L. 332-9

7_4_3

périmètre de voisinage d’infrastructure de transport terrestre (R123-13 12)

14

Périmètres des secteurs situés au voisinage des infrastructures de transports terrestres, dans lesquels des prescriptions d’isolement acoustique ont été édictées en application de l’article L. 571-10 du code de l’environnement

6_2

zone agricole protégée (R123-14 8)

15

Zones agricoles protégées délimitées en application de l’article L. 112-2 du code rural

1_4_4

site archéologique

16

Sites contenant des vestiges archéologiques concernés par le décret n°2004-490 relatif aux procédures administratives et financières en matière d’archéologie préventive – art. 1 : « les opérations d’aménagement, de construction d’ouvrages ou de travaux qui, en raison de leur localisation, de leur nature ou de leur importance, affectent ou sont susceptibles d’affecter des éléments du patrimoine archéologique ne peuvent être entreprises que dans le respect de détection et, le cas échéant, de conservation et de sauvegarde par l’étude scientifique ainsi que des demandes de modification de la consistance des opérations.

3_4

zone à risque d’exposition au plomb (R123-13 14)

17

Périmètres des zones à risque d’exposition au plomb

2_2_1

zone humide (L 146-6 et R 146-1)

18

Espaces et milieux à préserver en fonction de l’intérêt écologique qu’ils présentent : les marais, les vasières, les zones humides et milieux temporairement immergés…​ (L 146-6 et R 146-1)

1_4_5

zone d’assainissement collectif / non collectif / eaux usées/eaux pluviales, schéma de réseaux eau et assainissement, systèmes d’élimination des déchets (L123-1 11 et R123-14 3)

19

Schémas de réseaux eau et zonages assainissement, systèmes d’élimination des déchets existants ou en cours de réalisation, en précisant les emplacements retenus pour le captage, le traitement et le stockage des eaux destinées à la consommation, les stations d’épuration des eaux usées et le stockage et le traitement des déchets (R123-14 3)

7_3_3

Zone de Protection Rapprochée-ZPétendue (R123-14 6)

20

Zones de publicité restreinte, zones de publicité élargie (R123-14 6)

2_2_4

projet de PPRN et PPRM (R123-14 7)

21

Projet de plan de prévention des risques naturels prévisibles en application de l’article L. 562-2 du code de l’environnement et les dispositions d’un projet de plan de prévention des risques miniers établi en application de l’article 94 du code minier (R123-14 7)

2.

protection des rives des plans d’eau en zone de montagne (L146-6 et R146-1)

22

Les parties naturelles des rives des plans d’eau naturels ou artificiels d’une superficie inférieure à mille hectares sont protégées sur une distance de trois cent mètres à compter de la rive ; y sont interdits toutes constructions, installations et routes nouvelles ainsi que toutes extractions et tous affouillements (L146-6 et R146-1)

1_6

arrêté du préfet coordonnateur de massif/zone unités touristiques nouvelles en zone de montagne (L145-5 et R123-14 9)

23

Par exception aux dispositions de l’alinéa précédent, des constructions et aménagements peuvent être admis, en fonction des spécificités locales, dans certains secteurs délimités avec l’accord du préfet, après avis de la commission départementale compétente en matière de nature, de paysages et de sites, et au vu d’une étude justifiant que l’aménagement et l’urbanisation de ces secteurs sont compatibles avec la prise en compte de la qualité de l’environnement et des paysages (R123-14 9 - L145-5)

1_8

document d’aménagement commercial (L123-1)

24

Dans les cas visés au cinquième alinéa du II de l’article L. 752-1 du code de commerce, les plans locaux d’urbanisme peuvent comporter le document d’aménagement commercial

7_2

périmètre de protection des espaces agricoles et naturels péri-urbains (L143-1 et R123-13 15)

25

Les périmètres d’intervention pour la protection et la mise en valeur des espaces agricoles et naturels péri-urbains permettent l’élaboration et la mise en oeuvre d’un programme d’actions qui précise des aménagements et des orientations de gestion des espaces agricoles, forestiers, naturels, paysagers.

1_4_4

lotissement (R123-14 2 et L 315-2-1)

26

Périmètres des lotissements dont les règles d’urbanisme ont été maintenues en application du deuxième alinéa de l’article L. 315-2-1

7_1_3_1

plan d’exposition au bruit des aérodromes (L147-1 à L147-6 et R123-13 4)

27

Plan d’exposition au bruit des aérodromes (PEB A)

1_1

autre

99

 

10

E.3.2. Mapping supplementary regulation in Germany with XPlanGML standard

XPlanGML class HSRCL code

BP_AufschuettungsFlaeche

10_OtherSupplementaryRegulation

FP_AufschuettungsFlaeche

10_OtherSupplementaryRegulation

BP_AbgrabungsFlaeche

10_OtherSupplementaryRegulation

FP_AbgrabungsFlaeche

10_OtherSupplementaryRegulation

BP_BodenschaetzeFlaeche

10_OtherSupplementaryRegulation

FP_BodenschaetzeFlaeche

10_OtherSupplementaryRegulation

BP_RekultivierungsFlaeche

10_OtherSupplementaryRegulation

BP_BesondererNutzungszweckFlaeche

10_OtherSupplementaryRegulation

BP_PersGruppenBestimmteFlaeche

8_2_PubliclySubsidisedHousingArea

BP_GebaeudeFlaeche

10_OtherSupplementaryRegulation

BP_FoerderungsFlaeche

8_2_PubliclySubsidisedHousingArea

BP_FirstRichtungsLinie

6_RegulationsOnBuildings

BP_BauLinie

6_1_BuildingLine

BP_BauGrenze

6_1_BuildingLine

BP_UeberbaubareGrundstuecksFlaeche

5_1_UsableBuildingArea

BP_AbstandsFlaeche

6_3_SpatialDesign

BP_SpezielleBauweise

6_3_SpatialDesign

typ

 

Durchfahrt

6_3_SpatialDesign

Durchgang

6_3_SpatialDesign

DurchfahrtDurchgang

6_3_SpatialDesign

Auskragung

6_3_SpatialDesign

Arkade

6_3_SpatialDesign

Luftgeschoss

6_3_SpatialDesign

Sonstiges

6_3_SpatialDesign

BP_NebenanlagenFlaeche

6_4_SecondaryStructuraArea

zweckbestimmung

 

Stellplaetze

6_4_SecondaryStructuraArea

Garagen

6_4_SecondaryStructuraArea

Spielplatz

6_4_SecondaryStructuraArea

Carport

6_4_SecondaryStructuraArea

Tiefgarage

6_4_SecondaryStructuraArea

Nebengebaeude

6_4_SecondaryStructuraArea

AbfallSammelanlagen

6_4_SecondaryStructuraArea

EnergieVerteilungsanlagen

6_4_SecondaryStructuraArea

AbfallWertstoffbehaelter

6_4_SecondaryStructuraArea

Sonstiges

6_4_SecondaryStructuraArea

BP_NebenanlagenAusschlussFlaeche

 

typ

6_4_SecondaryStructuraArea

Einschraenkung

6_4_SecondaryStructuraArea

Ausschluss

6_4_SecondaryStructuraArea

BP_GemeinschaftsanlagenFlaeche

6_5_CollectiveFacility

zweckbestimmung

 

Gemeinschaftsstellplaetze

6_5_CollectiveFacility

Gemeinschaftsgaragen

6_5_CollectiveFacility

Spielplatz

6_5_CollectiveFacility

Carport

6_5_CollectiveFacility

GemeinschaftsTiefgarage

6_5_CollectiveFacility

Nebengebaeude

6_5_CollectiveFacility

AbfallSammelanlagen

6_5_CollectiveFacility

EnergieVerteilungsanlagen

6_5_CollectiveFacility

AbfallWertstoffbehaelter

6_5_CollectiveFacility

Freizeiteinrichtungen

6_5_CollectiveFacility

Laermschutzanlagen

6_5_CollectiveFacility

AbwasserRegenwasser

6_5_CollectiveFacility

Ausgleichsmassnahmen

6_5_CollectiveFacility

Sonstiges

6_5_CollectiveFacility

BP_GemeinschaftsanlagenZuordnung

6_5_CollectiveFacility

FP_KeineZentrale

10_OtherSupplementaryRegulation

AbwasserBeseitigungFlaeche

 

BP_ErhaltungsBereichFlaeche

 

grund

 

StaedtebaulicheGestalt

3_3_BuiltHeritageProtection

Wohnbevoelkerung

8_1_CompositionOfLocalResidentialPopulation

Umstrukturierung

8_1_CompositionOfLocalResidentialPopulation

BP_DenkmalschutzEnsembleFlaeche

4_1_6_Historic_preservation_easement

BP_DenkmalschutzEinzelanlage

4_1_6_Historic_preservation_easement

FP_Gemeinbedarf

10_OtherSupplementaryRegulation

FP_SpielSportanlage

10_OtherSupplementaryRegulation

FP_Gruen

10_OtherSupplementaryRegulation

BP_Schutzgebiet

3_HeritageProtection

zweckbestimmung

 

Naturschutzgebiet

1_4_NatureProtection

Nationalpark

1_4_NatureProtection

Biosphaerenreservat

1_4_2_BiodiversityReservoir

Landschaftsschutzgebiet

3_2_LandscapeAreaProtection

Naturpark

3_1_2_GeodiversityProtection

Naturdenkmal

3_1_NaturalHeritageProtection

GeschuetzterLandschaftsBestandteil

3_2_LandscapeAreaProtection

GesetzlichGeschuetztesBiotop

3_1_1_BiodiversityProtection

Natura2000

1_4_NatureProtection

GebietGemeinschaftlicher- Bedeutung

1_4_NatureProtection

EuropaeischesVogelschutzgebiet

1_4_NatureProtection

NationalesNaturmonument

3_2_LandscapeAreaProtection

Sonstiges

3_HeritageProtection

SO_SchutzgebietNaturschutzrecht

3_HeritageProtection

artDerFestlegung

 

Naturschutzgebiet

1_4_NatureProtection

Nationalpark

1_4_NatureProtection

Biosphaerenreservat

1_4_2_BiodiversityReservoir

Landschaftsschutzgebiet

3_2_LandscapeAreaProtection

Naturpark

3_1_2_GeodiversityProtection

Naturdenkmal

3_1_NaturalHeritageProtection

GeschuetzterLandschaftsBestandteil

3_2_LandscapeAreaProtection

GesetzlichGeschuetztesBiotop

3_1_1_BiodiversityProtection

Natura2000

1_4_NatureProtection

GebietGemeinschaftlicherBedeutung

1_4_NatureProtection

EuropaeischesVogelschutzgebiet

1_4_NatureProtection

NationalesNaturmonument

3_2_LandscapeAreaProtection

Sonstiges

3_HeritageProtection

BP_SchutzPflege

9_2_PermittedActivities

Entwicklungsmassnahme

 

BP_AusgleichsMassnahme

1_8_OtherImpactofEnvironmemt

BP_Anpflanzung-BindungErhaltung

 

BindungErhaltung

3_1_NaturalHeritageProtection

Anpflanzung

9_2_PermittedActivities

BP_SchutzPflege- EntwicklungsFlaeche

9_2_PermittedActivities

BP_AusgleichsFlaeche

9_2_PermittedActivities

BP_EingriffsBereich

9_2_PermittedActivities

FP_AusgleichsFlaeche

9_2_PermittedActivities

FP_SchutzPflegeEntwicklung

9_2_PermittedActivities

BP_KennzeichnungsFlaeche

10_OtherSupplementaryRegulation

zweckbestimmung

 

Naturgewalten

2_RiskExposure

Abbauflaeche

2_3_Mining

AeussereEinwirkungen

2_RiskExposure

SchadstoffBelastBoden

2_2_2_RestrictedZonesAroundContaminatedSites

LaermBelastung

1_1_1_NoiseProtectionArea

Bergbau

2_3_Mining

Bodenordnung

5_3_AreaReservedForRestructuringParcels

AndereGesetzlVorschriften

10_OtherSupplementaryRegulation

FP_Kennzeichnung

10_OtherSupplementaryRegulation

zweckbestimmung

 

Naturgewalten

2_RiskExposure

Abbauflaeche

2_3_Mining

AeussereEinwirkungen

2_RiskExposure

SchadstoffBelastBoden

2_2_2_RestrictedZonesAroundContaminatedSites

LaermBelastung

1_1_1_NoiseProtectionArea

Bergbau

2_3_Mining

Bodenordnung

5_3_AreaReservedForRestructuringParcels

AndereGesetzlVorschriften

10_OtherSupplementaryRegulation

BP_Veraenderungssperre

9_3_ForbidenActivities

BP_FreiFlaeche

9_1_RestrictedActivities

BP_TextlicheFestsetzungsFlaeche

9_2_PermittedActivities

FP_TextlicheDarstellungsFlaeche

9_2_PermittedActivities

BP_AbstandsMass

6_RegulationsOnBuildings

BP_HoehenMass

6_6_BuildingHightRegulation

BP_Wegerecht

4_1_PublicEasement

typ

 

Gehrecht

4_1_PublicEasement

Fahrrecht

4_1_PublicEasement

GehFahrrecht

4_1_PublicEasement

Leitungsrecht

4_1_3_UtilityEasement

GehFahrLeitungsrecht

4_1_PublicEasement

BP_GenerischesObjekt

10_OtherSupplementaryRegulation

FP_GenerischesObjekt

10_OtherSupplementaryRegulation

BP_UnverbindlicheVormerkung

10_OtherSupplementaryRegulation

FP_UnverbindlicheVormerkung

10_OtherSupplementaryRegulation

FP_VorbehalteFlaeche

9_1_RestrictedActivities

BP_NutzungsartenGrenze

10_OtherSupplementaryRegulation

FP_PriveligiertesVorhaben

9_4_SuitableActivities

FP_NutzungsbeschraenkungFlaeche

9_1_RestrictedActivities

BP_LuftreinhalteFlaeche

1_2_1_AirQualityManagementZone

BP_ErneuerbareEnergieFlaeche

1_3_RewenableEnergyArea

BP_Immissionsschutz

1_5_ClimateProtection

BP_VerEntsorgung

10_OtherSupplementaryRegulation

FP_VerEntsorgung

10_OtherSupplementaryRegulation

BP_StrassenbegrenzungsLinie

6_2_BoundaryLine

BP_EinfahrtsbereichLinie

9_2_PermittedActivities

BP_BereichOhneEinAusfahrtLinie

9_1_RestrictedActivities

BP_EinfahrtPunkt

9_2_PermittedActivities

BP_Strassenkoerper

10_OtherSupplementaryRegulation

FP_Strassenverkehr

10_OtherSupplementaryRegulation

SO_Strassenverkehrsrecht

10_OtherSupplementaryRegulation

SO_Schienenverkehrsrecht

10_OtherSupplementaryRegulation

SO_Luftverkehrsrecht

10_OtherSupplementaryRegulation

FP_Gewaesser

10_OtherSupplementaryRegulation

FP_Wasserwirtschaft

2_RiskExposure

HochwasserRueckhaltebecken

2_RiskExposure

Ueberschwemmgebiet

2_1_FloodRisks

Versickerungsflaeche

2_RiskExposure

Entwaesserungsgraben

2_RiskExposure

Sonstiges

2_RiskExposure

BP_WasserwirtschaftsFlaeche

2_RiskExposure

HochwasserRueckhaltebecken

2_RiskExposure

Ueberschwemmgebiet

2_1_FloodRisks

Versickerungsflaeche

2_RiskExposure

Entwaesserungsgraben

2_RiskExposure

Sonstiges

2_RiskExposure

SO_Wasserrecht

10_OtherSupplementaryRegulation

Gewaesser1Ordnung

10_OtherSupplementaryRegulation

Gewaesser2Ordnung

10_OtherSupplementaryRegulation

Gewaesser3Ordnung

10_OtherSupplementaryRegulation

Ueberschwemmungsgebiet

2_1_FloodRisks

Festgesetztes-

Ueberschwemmungsgebiet

2_1_FloodRisks

NochNichtFestgesetztes-

Ueberschwemmungsgebiet

2_1_FloodRisks

UeberschwemmGefaehrdetesGebiet

2_1_FloodRisks

Sonstiges

10_OtherSupplementaryRegulation

SO_SchutzgebietWasserrecht

1_4_3_ProtectedWoodedArea

Wasserschutzgebiet

1_4_3_ProtectedWoodedArea

QuellGrundwasserSchutzgebiet

1_4_3_ProtectedWoodedArea

OberflaechengewaesserSchutzgebiet

1_4_3_ProtectedWoodedArea

Heilquellenschutzgebiet

1_4_3_ProtectedWoodedArea

Sonstiges

1_4_3_ProtectedWoodedArea

SO_Denkmalschutzrecht

3_HeritageProtection

DenkmalschutzEnsemble

3_HeritageProtection

DenkmalschutzEinzelanlage

3_HeritageProtection

Grabungsschutzgebiet

3_HeritageProtection

Sonstiges

3_HeritageProtection

SO_Forstrecht

9_RegulatedActivities

SO_Bodenschutzrecht

2_RiskExposure

SchaedlicheBodenveraenderung

2_RiskExposure

Altlast

2_RiskExposure

Altablagerung

2_RiskExposure

Altstandort

2_RiskExposure

AltstandortAufAltablagerung

2_RiskExposure

SO_SonstigesRecht

9_RegulatedActivities

Bauschutzbereich

6_RegulationsOnBuildings

Berggesetz

2_RiskExposure

Richtfunkverbindung

4_GeneralInterest

Truppenuebungsplatz

4_GeneralInterest

VermessungsKatasterrecht

5_LandPropertyRight

Sonstiges

10_OtherSupplementaryRegulation

SO_SchutzgebietSonstRecht

Laermschutzbereich

1_ImpactOnEnvironment

SchutzzoneLeitungstrasse

4_GeneralInterest

Sonstiges

SO_Gebiet

9_RegulatedActivities

Umlegungsgebiet

5_3_AreaReservedForRestructuringParcels

StaedtebaulicheSanierung

7_4_3_UrbanRehabilitationAndRestoration_

StaedtebaulicheEntwicklungsmassnahme

7_4_1_UrbanRenewal_

Stadtumbaugebiet

7_4_2_UrbanRegenerationAndRevitalisation_

SozialeStadt

8_SocialHealthChoices

BusinessImprovementDestrict

9_2_PermittedActivities

HousingImprovementDestrict

9_2_PermittedActivities

Erhaltungsverordnung-StaedebaulicheGestalt

3_3_BuiltHeritageProtection

 

9_1_RestrictedActivities

Erhaltungsverordnung-Wohnbevoelkerung

8_1_CompositionOfLocalResidentialPopulation

9_1_RestrictedActivities

Erhaltungsverordnung-Umstrukturierung

9_1_RestrictedActivities

Sonstiges

10_OtherSupplementaryRegulation

E.3.3. Mapping supplementary regulation on structure plan level in Germany with XPlanGML standard

XPlanGML Klasse HSRCL code

Klasse

SupplementrayRegulationValue

RP_NaturLandschaft

3_HeritageProtection

xplanNSM:RP_NSM_Naturschutz

 

GruenlandBewirtschaftungPflegeEntwicklung

1_4_NatureProtection

Natura2000

1_4_NatureProtection

NaturschutzLandschaftspflege

1_4_NatureProtection

NaturschutzLandschaftspflegeAufGewaessern

1_4_NatureProtection

xplanNSM:RP_NSM_Landschaftsschutz

 

VerbesserungLandschaftsstrukturNaturhaushalt

3_2_LandscapeAreaProtection

Biotopverbundachse

3_2_LandscapeAreaProtection

KompensationEntwicklung

3_2_LandscapeAreaProtection

RP_Wasserschutz

 

zone

 

Zone_1

9_3_ForbidenActivities

Zone_2

9_1_RestrictedActivities

Zone_3

9_1_RestrictedActivities

zweckbestimmungWA

 

Grundwasserschutz

1_6_5_DrinkingWaterProtectionArea

Trinkwasserschutz

1_6_5_DrinkingWaterProtectionArea

Heilquelle

1_6_5_DrinkingWaterProtectionArea

RP_Rohstoffsicherung

7_2_7_1_ProspectingAndMiningPermitArea

xplanNSM:RP_NSM_Oberflaechennahe

Bodenschaetze

 

xplanNSM:folgenutzung

 

Landwirtschaft

7_4_5_Post_Zoning

 

7_2_1_Agriculture

Forstwirtschaft

7_4_5_Post_Zoning

 

7_2_2_Forest

Gruenlandberirtschaftung

7_4_5_Post_Zoning

NaturUndLandschaft

7_4_5_Post_Zoning

 

3_2_LandscapeAreaProtection

Naturschutz

7_4_5_Post_Zoning

 

1_4_NatureProtection

Erholung

7_4_5_Post_Zoning

 

7_2_3_Recreation

Sonstiges

7_4_5_Post_Zoning

xplanNSM:zeitstufe

 

Zeitstufe_1

7_4_5_Post_Zoning

Zeitstufe_2

7_4_5_Post_Zoning

xplanNSM:RP_NSM_TiefliegendeRohstoffe

7_2_7_RawMaterials

RP_Windenergienutzung

1_3_RewenableEnergyArea

RP_Landwirtschaft

7_1_3_5_Agriculture

AufGrundHohenErtragspotentials

7_1_3_5_Agriculture

AufGrundBesondererFunktionen

7_1_3_5_Agriculture

Fischerei

7_1_3_5_Agriculture

RP_Forstwirtschaft

7_1_3_6_Forestry

Wald

7_1_3_6_Forestry

VergroesserungDesWaldanteils

7_1_3_6_Forestry

VonAuffortungFreizuhaltendesGebiet

7_1_3_6_Forestry

BesondereSchutzfunktionDesWaldes

7_1_3_6_Forestry

RP_FreizeitErholung

7_2_3_Recreation

xplanNSM:RP_NSM_Erholung

 

Erholung

7_2_3_Recreation

SchwerpunktbereichErholung

7_2_3_Recreation

KernbereichErholung

7_2_3_Recreation

RuhigeErholungInNaturUndLandschaft

7_2_3_Recreation

ErholungMitStarkerInabspruchnahme

DurchBevoelkerung

7_2_3_Recreation

BesondereEntwicklungsaufgabeErholung

7_2_3_Recreation

BesondereEntwicklungsaufgabeTourismus

7_2_3_Recreation

RegionalBedeutsamerErholungsschwerpunkt

7_2_3_Recreation

Erholungswald

7_2_3_Recreation

xplanNSM:RP_NSM_Regional

BedeutsameSportanlage

 

RegionalBedeutsameSportanlage

7_2_3_Recreation

RegionalBedeutsameSportanlage_Wassersport

7_2_3_Recreation

RegionalBedeutsameSportanlage_Motorsport

7_2_3_Recreation

RegionalBedeutsameSportanlage_Flugsport

7_2_3_Recreation

RegionalBedeutsameSportanlage_Reitsport

7_2_3_Recreation

RegionalBedeutsameSportanlage_Golfsport

7_2_3_Recreation

RegionalBedeutsameSportanlage_Sportzentrum

7_2_3_Recreation

xplanNSM:RP_NSM_Regional

BedeutsamerWanderweg

 

RegionalBedeutsamerWanderweg

7_3_1_4_OtherNetworkInfrastructure

RegionalBedeutsamerWanderweg_

Radwandern

7_3_1_4_OtherNetworkInfrastructure

RegionalBedeutsamerWanderweg_

Radwandern_geplant

7_3_1_4_OtherNetworkInfrastructure

Fernradweg

7_3_1_4_OtherNetworkInfrastructure

RegionalBedeutsamerWanderweg_Reiten

7_3_1_4_OtherNetworkInfrastructure

RegionalBedeutsamerWanderweg_Wandern

7_3_1_4_OtherNetworkInfrastructure

Fernwanderweg

7_3_1_4_OtherNetworkInfrastructure

RegionalBedeutsamerWanderweg_

Wasserwandern

7_3_1_4_OtherNetworkInfrastructure

xplanNSM:RP_NSM_Tourismus

 

TourismusErholung

7_1_3_4_Tourism

SchwerpunktbereichErholung

7_1_3_4_Tourism

EntwicklungsgebietTourismusErholung

7_1_3_4_Tourism

KernbereichTourismusErholung

7_1_3_4_Tourism

KernbereichTourismus

7_1_3_4_Tourism

TourismusKuestenraum

7_1_3_4_Tourism

RP_Bodenschutz

7_2_8_Recultivation

BeseitigungErheblicherBodenbelastungen

7_2_8_Recultivation

SicherungSanierungVonAltlasten

7_2_8_Recultivation

RP_VorbHochwasserschutz

2_1_FloodRisks

Sperrwerk

2_1_FloodRisks

Hochwasserrueckhaltebecken_Bauwerk

2_1_FloodRisks

Hochwasserrueckhaltebecken

2_1_FloodRisks

Kuestenhochwasserschutz

7_2_9_1_ CoastalZoneManagementArea

Deich

2_1_FloodRisks

Hochwasserschutz

2_1_FloodRisks

HochwGefaerhrdeteKuestenniederung

7_2_9_1_ CoastalZoneManagementArea

RP_Klimaschutz

1_5_ClimateProtection

RP_GruenzugGruenzaesur

7_2_6_GreenBreak

RP_SonstFreiraumstruktur

7_2_OpenSpaceStructure

RP_NaturschutzrechtlichesSchutzgebiet

 

Naturschutzgebiet

1_4_NatureProtection

Nationalpark

1_4_NatureProtection

Biosphaerenreservat

1_4_2_BiodiversityReservoir

Landschaftsschutzgebiet

3_2_LandscapeAreaProtection

Naturpark

3_1_2_GeodiversityProtection

Naturdenkmal

3_1_NaturalHeritageProtection

GeschuetzterLandschaftsBestandteil

3_2_LandscapeAreaProtection

GesetzlichGeschuetztesBiotop

3_1_1_BiodiversityProtection

Natura2000

1_4_NatureProtection

GebietGemeinschaftlicherBedeutung

1_4_NatureProtection

EuropaeischesVogelschutzgebiet

1_4_NatureProtection

NationalesNaturmonument

3_2_LandscapeAreaProtection

Sonstiges

3_1_NaturalHeritageProtection

xplanNSM:besondereZweckbestimmungNSG

 

Kernzone

9_RegulatedActivities

RP_Gewaesser

7_2_9_Water

RP_KulturellesSachgut

3_HeritageProtection

RP_Verkehr

 

Schienenverkehr

7_3_1_2_RailRoad

Strassenverkehr

7_3_1_1_Road

Luftverkehr

7_3_1_Network

Wasserverkehr

7_3_1_3_WaterInfrastructure

SonstigerVerkehr

7_3_1_Network

xplanNSM:RP_NSM_Strassenverkehr

 

Autobahn_sechsstreifig

7_3_1_1_Road

Autobahn_vierstreifig

7_3_1_1_Road

GrossraeumigesStrassennetz

7_3_1_1_Road

Hauptverkehrsstrasse_vierstreifig

7_3_1_1_Road

Hauptverkehrsstrasse

7_3_1_1_Road

UeberregionalesStrassennetz

7_3_1_1_Road

Hauptverkehrsstrasse_Problembereich

7_3_1_1_Road

StrasseVonRegionalerBedeutung

7_3_1_1_Road

RegionalesStrassennetz

7_3_1_1_Road

StrasseVonRegionalerBedeutung_

Problembereich

7_3_1_1_Road

BedeutsamesFlaechenerschliessendes

Strassennetz

7_3_1_1_Road

Faehrverbindung

7_3_1_1_Road

Anschlussstelle

7_3_1_1_Road

Strassentunnel

7_3_1_1_Road

xplanNSM:RP_NSM_Schienenverkehr

 

Haupteisenbahnstrecke

7_3_1_2_RailRoad

Haupteisenbahnstrecke_Zwei_Mehrgleisig

7_3_1_2_RailRoad

Haupteisenbahnstrecke_Eingleisig

7_3_1_2_RailRoad

GrossraeumigesSchienennetz

7_3_1_2_RailRoad

UeberregionalesSchienennetz

7_3_1_2_RailRoad

SonstigeEisenbahnstrecke

7_3_1_2_RailRoad

RegionalesSchienennetz

7_3_1_2_RailRoad

OhneBetrieb_Trassensicherung

7_3_1_2_RailRoad

Stadtbahn

7_3_1_2_RailRoad

xplanNSM:RP_NSM_Wasserverkehr

 

Seehafen_Binnenhafen

7_1_3_9_HarborActivities

HafenVonUeberregionalerBedeutung

7_1_3_9_HarborActivities

HafenVorRegionalerBedeutung

7_1_3_9_HarborActivities

Hafen

7_1_3_9_HarborActivities

Sportboothafen

7_1_3_9_HarborActivities

Umschlagplatz

7_1_3_9_HarborActivities

Schleuse_Hebewerk

7_3_1_3_WaterInfrastructure

Schifffahrt

7_3_1_5_ RegulatedFairwayAtSeaOrLargeInlandWater

Wichtiger_Schifffahrtsweg

7_3_1_5_ RegulatedFairwayAtSeaOrLargeInlandWater

Sonstiger_Schifffahrtsweg

7_3_1_5_ RegulatedFairwayAtSeaOrLargeInlandWater

UeberregionaleFaehrverbindung

7_3_1_5_ RegulatedFairwayAtSeaOrLargeInlandWater

Reede

7_3_1_5_ RegulatedFairwayAtSeaOrLargeInlandWater

xplanNSM:RP_NSM_Luftverkehr

 

Flughafen

7_1_3_1_0AirportActivities

Verkehrsflughafen

7_1_3_1_0AirportActivities

Regionalflughafen

7_1_3_1_0AirportActivities

Verkehrslandeplatz

7_1_3_1_0AirportActivities

Regionalflugplatz

7_1_3_1_0AirportActivities

SonstigerFlugplatz

7_1_3_1_0AirportActivities

Bauschutzbereich

6_6_BuildingHightRegulation

RP_Entsorgung

 

Abfallwirtschaft

7_3_3_Disposal

Abwasserwirtschaft

7_3_3_Disposal

SonstigeEntsorgung

7_3_3_Disposal

xplanNSM:RP_NSM_Abwasser

 

ZentraleKlaeranlage

7_3_3_Disposal

Grossklaerwerk

7_3_3_Disposal

Hauptabwasserleitung

7_3_3_Disposal

Abwasserverwertungsflaeche

7_3_3_Disposal

xplanNSM:RP_NSM_Abfallentsorgung

 

SicherungVonStandortenFuer

Siedlungsabfalldeponien

7_3_3_Disposal

ZentraleAbfallbeseitigungsAnlage

7_3_3_Disposal

ZentraleAbfallverwertung_Deponie

7_3_3_Disposal

ZentraleAbfallverwertung_

Siedlungsabfalldeponie

7_3_3_Disposal

ZentraleAbfallverwertung_

Mineralstoffdeponie

7_3_3_Disposal

ZentraleAbfallverwertung_

Kompostierung

7_3_3_Disposal

ZentraleAbfallverwertung_

Verbrennung

7_3_3_Disposal

ZentraleAbfallverwertung_

Behandlung

7_3_3_Disposal

ZentraleAbfallverwertung_

Untertageeinlagerung

7_3_3_Disposal

Sonderabfallbeseitigung

Sonderabfallbehandlung

7_3_3_Disposal

EntsorgungRadioaktiverAbfälle

7_3_3_Disposal

RP_Energieversorgung

 

Hochspannungsleitung

7_3_2_Supply

Pipeline

7_3_2_Supply

Kraftwerk

7_3_2_Supply

EnergieSpeicherung

7_3_2_Supply

Umspannwerk

7_3_2_Supply

SonstigeEnergieversorgung

7_3_2_Supply

Leitungstrasse

7_3_2_Supply

Leitungstrasse_110KV

7_3_2_Supply

Leitungstrasse_220KV

7_3_2_Supply

Leitungstrasse_380KV

7_3_2_Supply

Kabeltrasse_Netzanbindung

7_3_2_Supply

Rohrfernleitung_Erdoel

7_3_2_Supply

Rohrfernleitung_Gas

7_3_2_Supply

Rohrfernleitung_Fernwaerme

7_3_2_Supply

Rohrfernleitung_Kraftstoff

7_3_2_Supply

UebergabestationFerngas

7_3_2_Supply

Kraftwerk_Kohle

7_3_2_Supply

Kraftwerk_Gas

7_3_2_Supply

Kraftwerk_Erdoel

7_3_2_Supply

Kraftwerk_Wasser

7_3_2_Supply

Kraftwerk_Kernenergie

7_3_2_Supply

Kraftwerk_Reststoffverwertung

7_3_2_Supply

Grosskraftwerk

7_3_2_Supply

Grosskraftwerk_Kohle

7_3_2_Supply

Grosskraftwerk_Gas

7_3_2_Supply

Grosskraftwerk_Erdoel

7_3_2_Supply

Grosskraftwerk_Wasser

7_3_2_Supply

Grosskraftwerk_Kernenergie

7_3_2_Supply

Grosskraftwerk_Reststoffverwertung

7_3_2_Supply

Energiegewinnung

7_3_2_Supply

Energiegewinnung_Kohle

7_3_2_Supply

Energiegewinnung_Gas

7_3_2_Supply

Energiegewinnung_Erdoel

7_3_2_Supply

Energiegewinnung_Wasser

7_3_2_Supply

Energiegewinnung_Kernenergie

7_3_2_Supply

SpeicherungPrimaerenergie_Erdoel

7_3_2_Supply

SpeicherungPrimaerenergie_Gas

7_3_2_Supply

VerstetigungSpeicherungRegenerativeEnergie

1_3_RewenableEnergyArea

Untergrundspeicher

1_3_RewenableEnergyArea

Windenergienutzung

1_3_RewenableEnergyArea

ErneuerbareEnergien

1_3_RewenableEnergyArea

RP_Laermschutzbereich

 

Laermbereich

1_1_NoiseManagementZone

Laermschutzbereich

1_1_1_NoiseProtectionArea

Siedlungsbeschraenkungsbereich

1_1_NoiseManagementZone

Siedlungszaesur

1_1_NoiseManagementZone

RP_Wasserwirtschaft

 

Wasserleitung

7_3_2_Supply

Wasserwerk

7_3_2_Supply

TalsperreStaudammDeich

7_3_2_Supply

TalsperreSpeicherbecken

7_3_2_Supply

Rückhaltebecken

7_3_2_Supply

SonstigeWasserwirtschaft

7_3_2_Supply

RP_SozialeInfrastruktur

 

Kultur

7_3_5_OtherInfrastructure

Sozialeinrichtung

7_3_5_OtherInfrastructure

Gesundheit

7_3_5_OtherInfrastructure

Bildung

7_3_5_OtherInfrastructure

SonstigeSozialeInfrastruktur

7_3_5_OtherInfrastructure

RP_SonstigeInfrastruktur

7_3_Infrastructure_

RP_Raumkategorie

7_1_4_SpatialOrderCategories_

Ordnungsraum

7_1_4_7_PeriUrbanAreas

OrdnungsraumTourismusErholung

7_1_4_7_PeriUrbanAreas

Verdichtungsraum

7_1_4_3_CityAndOuterConurbationArea

LaendlicheRaum

7_1_4_1_RuralArea

StadtUmlandRaum

7_1_4_6_FunctionalUrbanArea

StadtUmlandBereichLaendlRaum

7_1_4_6_FunctionalUrbanArea

AbgrenzungOrdnungsraum

7_1_6_OtherSettlementStructureDevelopmentPolicies

Oberbereichsgrenze

7_1_6_OtherSettlementStructureDevelopmentPolicies

Mittelbereichsgrenze

7_1_6_OtherSettlementStructureDevelopmentPolicies

Nahbereichsgrenze

7_1_6_OtherSettlementStructureDevelopmentPolicies

DuennbesiedeltesAbgelegenesGebiet

7_1_6_OtherSettlementStructureDevelopmentPolicies

Umkreis_10_Km

7_1_6_OtherSettlementStructureDevelopmentPolicies

RP_Sperrgebiet

9_1_RestrictedActivities

SondergebietBund

9_1_RestrictedActivities

GrosseMilitaerischeAnlage

9_1_RestrictedActivities

Warngebiet

9_1_RestrictedActivities

RP_ZentralerOrt

 

Oberzentrum

7_1_1_4_HighOrderCentre

Mittelzentrum

7_1_1_3_MiddleOrderCentre

Grundzentrum

7_1_1_2_LowerOrderCentre

Kleinzentrum

7_1_1_1_Basic

SonstigeFunktion

7_1_1_CentralPlaces

GemeinsamesOberzentrum

7_1_1_4_HighOrderCentre

MittelzentrumMitOberzentralerTeilfunktion

7_1_1_3_MiddleOrderCentre

MittelzentrumImVerdichtungsraum

7_1_1_3_MiddleOrderCentre

GrundzentrumMitMittelzentralerTeilfunktion

7_1_1_2_LowerOrderCentre

Unterzentrum

7_1_1_1_Basic

UnterzentrumMitMittelzentralerTeilfunktion

7_1_1_1_Basic

Stadtrandkern_1_Ordnung

7_1_6_OtherSettlementStructureDevelopmentPolicies

Stadtrandkern_1_Ordnung

MitMittelzentralerTeilfunktion

7_1_6_OtherSettlementStructureDevelopmentPolicies

Stadtrandkern_2_Ordnung

7_1_6_OtherSettlementStructureDevelopmentPolicies

LaendlicherZentralort

7_1_6_OtherSettlementStructureDevelopmentPolicies

ZentralesSiedlungsgebiet

7_1_6_OtherSettlementStructureDevelopmentPolicies

RP_GemeindeFunktion

Siedlungsentwicklung

 

Wohnen

7_1_3_1_Housing

Arbeiten

7_1_3_2_CommerceIndustry

Landwirtschaft

7_1_3_5_Agriculture

Einzelhandel

7_1_3_3_Services

ErholungFrendenverkehr

7_1_3_4_Tourism

Verteidigung

7_1_3_AssignmentOfFunctions_

SonstigeNutzung

7_1_3_AssignmentOfFunctions_

xplanNSM:RP_NSM_ASM

 

Wohnfunktion

7_1_3_1_Housing

GewerbeDienstleistungsfunktion

7_1_3_2_CommerceIndustry

WohnGewerbeDienstLeistungsfunktion

7_1_3_1_Housing

UeberoertlVersorgungsfunktionLaendlRaum

7_1_3_3_Services

Baugebietsgrenze

7_LocalRegionalStateDevelopmentPolicies

Siedlungsgebiet

7_LocalRegionalStateDevelopmentPolicies

Siedlungsschwerpunkt

7_1_SettlementStructure

RP_Achse

 

Siedlungsachse

7_1_2_1_SettlementAxes

GrossraeumigeAchse

7_1_2_2_SupralocalAxes

SonstigeAchse

7_1_2_Axes

Siedlungsachse

7_1_2_1_SettlementAxes

Landesentwicklungsachse

7_1_2_2_SupralocalAxes

Annex F: Land Use and Land Cover Relations - (informative)

Land Cover and Land Use have been considered for decades as remarkable aspects for describing and understanding land’s physiognomy and utilization. Land Cover and Land Use information is important background information for environmental issues related to the land surface such as habitats, biodiversity, catchments hydrology, and climate change[multiblock footnote omitted]

The three main and essential features in the context of describing the interrelation between Land Cover and Land Use are: (1) the concepts of Land Cover and Land Use, (2) the questions of land units, and (3) the available sources of data for feeding such a component. The third feature will not be commented in the following paragraphs.

F.1. Land cover and land use definitions

Definition for Land Cover and Land Use concepts is widely known in many of land nomenclatures and projects, and INSPIRE 2007/2/CE Directive mainly defines them as bio-physical and functional range on land, respectively.

  • Land Cover: Physical and biological cover of the earth’s surface including artificial surfaces, agricultural areas, forests, (semi-)natural areas, wetlands, water bodies.

  • Land Use: Territory characterised according to its current and future planned functional dimension or socio-economic purpose.

There are also more definitions available from UN FAO, UE CORINE and LUCAS projects or national databases that complement and clarify in detail their definitions. In particular it is remarkable that both definitions are feasible for different scopes: 1) on, above or below of surface, and 2) terrestrial, marine and aerial areas.

The relation between Land Cover and Land Use is strong and indissoluble, because the existence of use implies causes and consequences on cover and vice versa. Land Cover and Land Use are essential components of the land as for each location one type of Land Cover and one type of Land Use can be identified. However, definitions of Land cover and Land Use in many existing information systems and nomenclatures are often mixed, they are even sometimes seen as the same phenomenon. Notwithstanding to reach a complete solution of both components, initially Land Cover and Land Use should be treated in parallel way for finally inferring the joint vision. They describe quite distinct dimensions of the land surface and should be separately defined and classified to prevent ambiguous interpretations.

Furthermore it is important to remind that, contrarily to Land Cover, many Land Uses cannot be directly extracted using land monitoring techniques such as aerial photography, and require direct field observation or the use of ancillary (planning) data.

There are various approaches that describe the concept of Land Use in different ways. In the literature the following aspects are often quoted

  • "Functional" corresponds to the description of land in terms of its socio-economic purpose (agricultural, residential, forestry etc.) and links with Land Cover are possible. It could be simply identified as "activities"

  • "Sequential" corresponds to a series of operations on land, carried out by humans, with the intention to obtain products and/or benefits through using land resources. It could be simply identified as "results form activities".

In the Land Use data specification three main aspects have been modelled as feature types:

  • "Existing" or material Land Use in the time of observation. Traditionally, activities effectively carried out are taken into consideration. These activities are collected from land observation and monitoring projects.

  • "Planned" Land Use regulated by spatial planning documents elaborated at various levels of administration.

  • "Supplementary regulations" are information and/or limitations on Land Use activities according to regulations. It restricts or conditions the exercise of the freedom to use one’s land property

The choice has been made to incorporate the "Functional" and "Sequential" aspects into the Land Use nomenclatures.

image

F.2. Dependencies and consequences between land cover and land use

Due to the close relation between Land Cover and Land Use the presence of a particular Land Cover often conditions the Land Use type and can prevent other land uses. Also the other way round is possible, the present Land Cover can be deduced or the future Land Cover can be predicted from a specific Land Use type. In this way, rules of inference could be established for different applications to identify trends or changes.

For example, a parcel of land covered by field crops can reasonably be associated with agricultural use, or a river area will only be used for transport and fishing. A residential area will be made up of a mosaic of land cover types including dwellings, other buildings, gardens, roads, paths, woodland and bare surfaces. Similarly, an area used for managed forestry would be expected to be covered by trees. If it were not, then it may be inferred that the woodland had been felled or the land was being prepared for forestation. Or a parcel designated in a plan to be urban park will contain vegetation coverage in the future instead artificial structures.

Another important aspect regarding Land Cover and Land Use is the thematic level of detail of each no-menclature. For reaching favourable results relating Land Cover and Land Use data, there have to be comparable classes with a similar level of thematic detail in each nomenclature.

F.3. Land unit

'Land' is a widely-used and often loosely-defined term, but classifications are closely tied to the uses which will be made of land data collected. Land Unit can be defined as "A delineable area of the earth’s terrestrial surface, embracing all attributes of the biosphere immediately above or below this surface, including those of the near surface climate, the soil and terrain forms, the surface hydrology including shallow lakes, rivers, marshes and swamps, the near-surface sedimentary layers and associated groundwater and geohydrological reserves, the plant and animal populations, the human settlement pattern and physical results of past and present human activity (terracing, water storage or drainage structures, roads, buildings, etc.)"[32]

However the delineation of Land Cover and Land Use types is often difficult as there are no easily identifiable natural 'units' or 'objects' that form the basis for identification of Land Cover and Land Use types. Where an object has a physical boundary (e.g. factory, dwelling, plot of grazing land) due to its man-made origin, it is easily identifiable. However, identifying objects and delineating boundaries in semi-natural environments or complex buildings is more intractable. Even more complicated is the delineation of objects with multiple uses to be identified vertically, i.e. use above and below ground level at the same location.

A spatial information system regarding Land Cover or Land Use needs spatial units that are represented by geometry like a polygon or a grid cell. For defining a Land Unit, two fundamental principles are important:

  • Land Units should represent homogeneous and continuous Land Cover or Land Use.

  • Land Units should be conformed to cartographic restrictions as Minimum Mapping Unit, and/or shape of land unit (e.g. minimum width).

When the complexity of the real world is simple both principles can be maintained to delineate the Land Cover or Land Use. However, when the reality is more complex the correct identification can’t meet both principles. Normally, for simplifying the management of information, the second principle takes preference over the first, resulting in mixtures of land use types in horizontal, vertical or temporal dimension.

Horizontal mixing by 'juxtaposition' is strongly dependant on the scale and unit of observation e.g. the mixing of sports facilities with other recreational areas within an outdoor amenity space or the assemblage of uses within a defined industrial site. These configurations are usually handled through definition and application of rules. Rules of 'preferences' usually are employed for Land Use,. An example is the 'main activity' rule which determines the activity on which other activities or uses depend and without which they would loose their purpose. This is illustrated by a manufacturing plant that accommodates several uses additional to, but dependent on, manufacturing, such as storage, car and lorry parking and offices.

image

Horizontal mixing 'juxtaposition'

Vertical mixing in the third dimension is caused by 'superposition' of different covers or uses. Mixing in the third dimension is independent of scale of observation and requires a rule so that elements are correctly identified and recorded. Blocks of offices and/or flats with shops at ground level provide a classic case of mixing by superposition. 'Mapping' rules such as 'majority use' or 'ground floor use' are sometimes used in land use surveys to cartographically depict Land Use. However, in both cases there is a loss of information which could be significant for user related purposes. Recording all uses at all levels provides a more generic approach that can serve multiple applications and still allows, if necessary, the subsequent application of a mapping rule to simplify the occurrence of multiple uses for display purposes.

image

Vertical mixing 'superposition'

Temporal mixing is used to describe instances where the land accommodates more than one cover or use and is highly dependent on the time of observation. Temporal mixing can be virtually simultaneous, for example, forestry and recreation, water storage and recreation, or can occur over longer cycles, for example, weekday car park and weekend market. Again the application of a 'mapping' rule such as 'primary use' that seeks to identify a single or primary use for each piece of land will result in a loss of information. Recording all instances of use is usually preferred.

image

Temporal mixing

With the previous definition of the Land Unit it is clear that different geometries for LU and LC exist. The relation between these geometries depends on the complexity of the land information system. The simplest relationship between the LC and LU is the superposition of both geometries that will not fit 1:1 in most cases.

Annex G: Proposed changes to D2.3 V3.0 - (informative)

There are two main land use definitions, a functional one and sequential one (Duhamel, 1998). The functional definition defines land use as the description of land in terms or its socio-economic purpose (agricultural, residential, forestry etc.). The sequential definition describes land use as a series of operations on land, carried out by humans, with the intention to obtain products and/or benefits through using land resources. However, examples given for the sequential definition of land use are limited to operation sequences decided by farmers over years: ploughing, seeding, weeding, fertilizing, weeding, harvesting for maize the first year, etc. This concept would need more clarification in non agricultural domain. This sequential approach is rather complex since the majority of attributes are not inherent features of land use, the proposed system is tailored uniquely towards agricultural uses and introduces a difficult component of time (reference period of observation and cycles). Providing such detailed information would raise many questions: who needs this information, how to design a cost-efficient system at such a detailed level? In addition, links with land cover classification could not be ensured.

Therefore the functional definition of Land Use will be used for defining the relevant INSPIRE theme. One of the key component of INSPIRE Land Use theme will be the nomenclature that defines the socio-economic purpose taken into consideration and the level of detail to be retained as well as the question of extensive use versus intensive use of land, e.g. regarding agriculture practices, level of social mix, or density of houses.

G.1. Land Use plans/land use regulation

The land use plans regulate actual and future use of areas. The land use plans commonly have significant textual regulations to each area/land category or specific areas. The land use plans are of varying detail; Municipal land use plans, detailed regulation plans for blocks or smaller areas within urban areas.

  • Land Use may be seen as divisions at a nationwide level, e.g. distinguishing between private and state owned land.

  • Land Use plan is commonly made at regional levels as kinds of master plans, e.g. covering the full extent of several municipalities, the borders of areas defined in the map being fuzzy

  • Land regulation plans at detailed low level may cover populated areas or areas of specific economic or social interest. The plans may direct utilization level, the % of building coverage within areas, height regulations or functional regulations, and maps produced apply to the cadastral,parcels.

It is a very diverse situation concerning land regulation/land use plans as these spatial data commonly are based on national or regional legislation or other kinds of regulation. The documents/maps are frequently seen as legal documents, and the categories remain for decades as rights directing use land and property. These documents are opposable to third parties in their paper form and their digital versions have no legal status in many European countries. Does INSPIRE have to deal with the textual regulation, necessarily written in the national languages? Focussing on the broader categories, but the option is left open for countries to add a hyperlink to the full land use regulation text. Categories of land use follow such regulations. Furthermore, operational plans may for some areas be old and based on older legislation, and their nomenclature may be obsolete. Operational land use plans may be as old as 100 years or more. Also plans being proposed and being in a process or public/sectoral hearing can be relevant for dissemination in the infrastructure. The time dimension is also related to the process of devising a spatial planning document as well as the relation between past land use zoning and the actual changes in the land use observed long time after plan is approved.

It is possible to allocate three different land uses to one parcel: the pre-destination, the destination and the after-destination. For example an agricultural area is allowed to keep on existing until 2012, after which it will be turned into a mining area, after the mining has finished the land will be converted into a nature reserve.

G.2. Functional land use – according to socio-economic purpose

Functional areas within urban or rural areas may be mapped through fieldwork, register information or through modelling using socio-economic input data in a GIS. A classification of the land use phenomenon may be based on the ISIC Rev.3 (International Standard Classification of All Economic Activities) classification drawn up by the United Nations (approved by the Statistical Commission in 1989) and recommended for use throughout the world. This classification is integrated in the sense that it ensures a full harmonization with another main branch of economic classifications: the classifications of products (ICPC Central Product Classification) which are fundamental for foreign trade statistics, statistics of production and consumption, energy statistics, etc. The ISIC classification may therefore be appropriate to characterise land use percentages for administrative units. The ISIC Rev. 3, is fully compatible with the EU NACE Rev. 1 (Nomenclature des Activités de la Communauté Européenne) system for the first two levels. (System replaced by 1.1.2008, see references). On the other hand the ISIC system is not in use within the spatial planers community mainly because is does not provide entries for "residential area", "recreation areas", "mix residential-activity area" that are common in spatial planning documents.

Whichever system will be recommended in the INSPIRE Context, member states will have to develop their own mapping from national classification to it. The question remains with the planners' usage regarding land use classes. Being contacted, the International Society of City and Regional Planners (ISOCARP) has not developed any such classification scheme.

G.3. Scope, use examples

Many of the management and planning activities at local level require detailed data. Proper location, the geographical position, is important. The level of accuracy needed in location varies, the need for (and will to produce) accurate data being higher in urban or built-up areas and lower in rural and natural/semi-natural environments. Data producers may be requested to provide information on the positional accuracy and the exhaustivity of their LU datasets. The concept of "minimum LU unit" questions the mandatory provision of the size of the MLU unit by the producer. Similarly, interest in frequent updating decreases with distance from central areas. The detailed area planning covers both land and sea/coastal areas including inland and some off shore water bodies.

Land Use is important for impact assessment and monitoring of implementation of policies and legal instruments for sustainable management of the environment, like Natura2000.

Policies:

6EAP, EIA guidelines. Several policies and strategies give highlight the value of regional approaches with integrated land/area management, such as the Integrated Coastal Zone Management, Communication on planning and environment, Water Framework Directive and the Communication on risk prevention.

Environmental Impact Assessments (EIAs) for projects and Strategic Environmental Assessment (SEAs) for policies, plans and programmes ensure that significant environmental impacts are identified, assessed and taken into account in decision-making process to which the public can participate.

Others European policies and issues including the climate change policy, sea level rise, Urban sprawl, soil directive, polluted soil, regional policies and related relevant national policies will require Land Use information.

G.4. Important feature types and attributes

Kinds of features depend on kind of land use and land use plan. A representation of a land use plan may be structured as a layered dataset.

  • boundary of plan/regulation

  • land use category area

  • land use regulation area or prescription regarding land use

  • land use restriction area or constraints regarding land use (in connection with the Area management/restriction/regulation zones and reporting units theme)

  • elements within a plan (road boundaries, building boundaries, forest/agricultural land boundaries etc.)

Does the "back-ground" or reference material over which the zoning map is created be part of the Land Use theme? Is it an information to be documented in the Metadata associated with LU datasets? This raise the issue of relative positional accuracy of two layers to be superimposed.

Important attributes

  • land use category

  • land use regulation category

  • land use restriction category

  • present/existing or proposed/planned/future

  • legal reference

  • date of entry into force

  • link to text regulations for each area

G.5. Links and overlaps with other themes

  • Cadastral parcels as a possible back-ground for a given Land Use datasets: relative positioning

  • Administrative units that are concerned with a given Land Use dataset: Geometric overlap

  • Statistical units that are concerned with a given Land Use dataset:: Geometric overlap

  • Geographical names associated with land use area: Geometric overlap

  • Hydrography as elements within a plan: Geometric overlap

  • Transport networks as elements within a plan: Geometric overlap

  • Protected sites as elements within a plan: Geometric overlap

  • Land cover as a possible back-ground for a given Land Use datasets: relative positioning

  • Buildings as elements within a plan: Geometric overlap

  • Human health and safety as elements within a plan: Sharing nomenclature and geometric overlap

  • Utility and governmental services as elements within a plan: Sharing nomenclature and geometric overlap

  • Production and industrial facilities as elements within a plan: Sharing nomenclature and geometric overlap

  • Agricultural and aquacultural facilities as elements within a plan: Sharing nomenclature and geometric overlap

  • Population distribution – demography as input to the spatial planing process:

  • Area management/restriction/regulation zones and reporting units as elements within a plan: Sharing nomenclature and geometric overlap

  • Natural risk zones as elements within a plan: Sharing nomenclature and geometric overlap

  • Habitats and biotopes as elements within a plan: Sharing nomenclature and geometric overlap

  • Energy resources as elements within a plan: Sharing nomenclature and geometric overlap

  • Mineral resources as elements within a plan: Sharing nomenclature and geometric overlap

G.6. Reference documents

Christophe Duhamel (1998) First approximation of a reference land use classification, Report to the FAO

CNIG: Annexe 5 – Liste des données géographiques de référence en domaine littoral (France)

CORINE as a European Land Use nomenclature (e.g. urban sprawl MOLAND).

Council Regulation (EEC) no. 3037/90 concerning the statistical classification of economic activities in the European Community (NACE rev.1) is repealed by Regulation (EC) no. 1893/2006 of the European Parliament and of the Council of 20 December 2006 establishing the statistical classification of economic activities NACE revision 2 and amending Council Regulation (EEC) No 3037/90 as well as certain EC Regulations on specific statistical domains. (NACE rev. 2) This Regulation shall apply from 1 January 2008. As a consequence NACE rev.1 as well as ISIC Rev. 3 is not applicable from 1 January 2008 onwards.

EuroGeographics: EuroRegionalMap Specification 4.0 and Data Catalogue

INTESA-GIS: 1n1007_1-2 - Specifiche per la realizzazione dei data base topografici di interesse generale. Il catalogo degli oggetti (v.3_3). (Italy)

Nomenclature statistique des Activités économiques dans la Communauté Européenne (NACE), revision 1.1, at : http://www.fifoost.org/database/nace/index_en.php

Norwegian feature catalogue including different chapters and UML models for land use planning/masterplan, land cover (with a land use component) See URLs: http://www.statkart.no/sosi/UMLfullmodell/Plan/Plan.htm

http://www.statkart.no/sosi/UMLfullmodell/Markslag/Markslag.htm

RAVI:NEN3610 by "Ministry of Housing, Spatial Planning and Environment (VROM), Information model Land Use plans (Informatiemodel Ruimtelijke Ordening), 2012,

http://ro-standaarden.geonovum.nl/2012/IMRO/1.2/IMRO2012-v1.2.pdf

United Nations, International Standard Industrial Classification (ISIC), Rev. 3, at: http://unstats.un.org/unsd/cr/registry/regcst.asp?Cl=2

Annex H: Ecological function of land - (informative)

According to the INSPIRE definition land use is described as a functional dimension or socio-economic purpose. This view on land use raises the question if nature / protecting biodiversity / the ecological function of land can be seen as a human activity and thus can be classified as land use. It is arguable that nature does not serve an economic function for humans. In this light, nature areas should be classified as areas with no use. There is however another view that should be taken into account, which defines land use as the description of land in terms of its socio-economic and ecological purpose.

Nature 2000 is a European agreement to create a European Ecological Network. In this agreement existing nature is protected and new nature is realized. To form this network ecological corridors and stepping stones are created in order to let species more easily spread from one area to another. The existing nature in Europe is however not something that just exists without interference of humans, this nature must be actively protected. Local, regional and national governments and associations try to enhance the biodiversity in those areas. New nature is created, for example by digging away fertile, overly fertilized top soils and revealing the poor soil underneath or by making sure the groundwater levels don’t fall beneath a certain level. By doing this environments are created to attract endangered species, to give them a place where a stable community can survive.

Nature management plans are made to provide the right circumstances for target species to keep on living in a specific area. Other areas can be modified to create conditions to attract new (endangered) species. Take the example of a grassland or meadow, to make sure that rare grass-species keep on existing it is essential that the grass is often and at the right time cut. Otherwise trees will start growing that will push away the grasses and flowers. Heath or moorland is also often a created 'natural area'. If the human activity that created it stops, heath will soon become forest.

And even if nothing had to be done to make sure nature thrives in nature areas, humans still need to actively protect these areas. Without the protection or legal regulation, other (economically more interesting) functions would soon take over. Biodiversity would be at risk.

Besides the dominant land use 'nature area' these sites are often also 'used' for other human activities. They can be used as recreation area or as places to educate people. Besides direct use green environments also have a positive influence on our health, physically and mentally. Finally, all these nature areas also have an (indirect) economic value: larger numbers of plant species means a greater variety of crops (possibly useful for people in the future)

Nature areas also influence the space next to it. Green environments have a proven positive effect on humans therefore increasing the 'livability' in areas adjacent to it. Besides the positive effect on residential areas it is also interesting for the economy, having nature or green areas in the neighborhood increases the value of the property next to it. Of course it can also devaluate the property next to it when strict regulations are in place to make sure other land uses do not have a negative effect on nature. As a final remark it can be stated that greater species diversity ensures natural sustainability for all life forms and healthy ecosystems can better withstand and recover from a variety of disasters.

If you take the definition of the FAO: Land Use is "the total of arrangements, activities, and inputs that people undertake in a certain land cover type", Nature or preserving nature, as argued above is definitely a form of land use.

Annex I: Use of PLU model for strategic planning in Germany - (informative)

In Germany the essential purposes of spatial planning on regional and state level are elaborated and implemented by a range of tools on three levels:

federal spatial planning,
state spatial planning,
regional spatial planning.

On federal spatial planning level there is no binding development plan provided for controlling and developing the national territory as a whole. The Federal Ministry of Transport, Building and Urban Affairs establish a development plan for the exclusive economic zone beyond coastal waters (200 mile zone).

State spatial planning addresses spatial development in the state as a whole, while regional planning is concerned with subdivisions of a state. State spatial planning authorities have to ensure that the goals and principles of national spatial planning and state spatial planning are respected and taken into account in local government planning. In a system of mixed top-down/bottom-up planning (principle of countervailing influence), they accept suggestions from local authorities and are required to coordinate local development goals with superordinate planning goals. The aim is to ensure that urban land-use planning does not cross the development aims of state spatial planning but supports them, thus avoiding investment mistakes. The function of these plans (name differ from state to state like state development plan or state development programme) is to coordinate the spatially relevant planning and projects of all competent organisational units and to tie them in with the conceptual aims of state spatial planning itself. In the city-states of Berlin, Bremen, and Hamburg a preparatory land-use plan pursuant to Section 5 of the Building Code can perform the same function.

Below state level of spatial planning, regional planning is concerned with the detailed elaboration, sectoral integration, and implementation of the goals of state spatial planning. It accordingly mediates between state spatial planning and local urban land-use planning. Regional planning must conform with federal and state spatial planning.

Municipalities are autonomous and responsible for spatial planning in their territory according to the principles and guidelines defined by higher levels.

Spatial plans on regional and state level should contain e.g. specifications concerning the spatial structure, especially with respect to:

  • the desired settlement structure (HSRCL code 7.1.) which may include

    • central places (HSRCL code 7.1.1.),

    • development axes (HSRCL code 7.1.2.),

    • assignment of functions (HSRCL code 7.1.3.),

    • spatial order categories (HSRCL code 7.1.4.),

  • the desired open space structure (HSRCL code 7.2.) which may include

    • inter-regionally significant open spaces (HSRCL code 7.2.1. – 7.2.6.),

    • uses of open space, such as sites designated to safeguard supplies of and

    • systematically search for and extract location-specific raw materials (HSRCL code 7.2.7.),

  • the desired infrastructure locations and routes (HSRCL code 7.3.) which may include

    • traffic infrastructure and installations for transfer of goods (HSRCL code 7.3.1.)

    • public utility and waste disposal infrastructure (HSRCL code 7.3.2.).

Using the state development plan of the northern German state of Schleswig-Holstein as an example the following pictures exemplarily illustrate a mapping from national spatial regulations (such as desired settlement structure) to the INSPIRE HSRCL codes.

7.1.1. CentralPlaces

image

7.1.2. Axes

image

7.1.3. AssignmentOfFunctions

image

7.1.4. SpatialOrderCategories

image
1. The common document template is available in the "Framework documents" section of the data specifications web page at http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2
2. For all 34 Annex I,II and III data themes: within two years of the adoption of the corresponding Implementing Rules for newly collected and extensively restructured data and within 5 years for other data in electronic format still in use
3. The current status of registered SDICs/LMOs is available via INSPIRE website: http://inspire.jrc.ec.europa.eu/index.cfm/pageid/42
4. Surveys on unique identifiers and usage of the elements of the spatial and temporal schema,
5. The Data Specification Drafting Team has been composed of experts from Austria, Belgium, Czech Republic, France, Germany, Greece, Italy, Netherlands, Norway, Poland, Switzerland, UK, and the European Environment Agency
6. The Thematic Working Groups have been composed of experts from Austria, Australia, Belgium, Bulgaria, Czech Republic, Denmark, Finland, France, Germany, Hungary, Ireland, Italy, Latvia, Netherlands, Norway, Poland, Romania, Slovakia, Spain, Slovenia, Sweden, Switzerland, Turkey, UK, the European Environment Agency and the European Commission.
7. For Annex IIIII, the consultation and testing phase lasted from 20 June to 21 October 2011.
8. Commission Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services, published in the Official Journal of the European Union on 8th of December 2010.
9. The framework documents are available in the "Framework documents" section of the data specifications web page at http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2
10. UML – Unified Modelling Language
11. Conceptual models related to specific areas (e.g. INSPIRE themes)
12. In the case of the Annex IIIII data specifications, the extracted requirements are used to formulate an amendment to the existing Implementing Rule.
13. SOER Synthesis, 2010. The European environment — state and outlook 2010: synthesis. European Environment Agency, Copenhagen.
14. The INSPIRE Glossary is available from http://inspire-registry.jrc.ec.europa.eu/registers/GLOSSARY
15. Slivers are small polygons generated by overlapping two adjacent plans where the same line in reality has a different geometry in each dataset.
16. OJ L 326, 4.12.2008, p. 12.
17. The Implementing Rules and Technical Guidelines on INSPIRE Network Services are available at http://inspire.jrc.ec.europa.eu/index.cfm/pageid/5
18. Further details and examples will be included in a future version of the Guidelines for the encoding of spatial data [DS-D2.7
19. OJ L 274, 20.10.2009, p. 9.
20. www.hlandata.eu
21. From the European Regional/Spatial Planning Charter adopted in 1983 by CEMAT the European Conference of Ministers responsible for Regional Planning
22. application du droit des dols
23. United Nations Framework Convention for Climate Change (UNFCCC)
24. Land Use and Land-Use Change and Forestry (LULUCF)
25. Intergovernmental Panel on Climate Change (IPCC)
26. Greenhouse Gas (GHG)
27. Geographic Information System
28. Methods documented in "IPCC Good Practice Guidance for LULUCF"
29. Good Practice Guidance
30. "Principle of Environmental Impact Assessment Best Practice." International Association for Impact Assessment. 1999.
31. Deliverables of Work Package 1 (Diagnostic of users and databases) at http://www.hlandata.eu/
32. IDWG-LUP at UN-FAO, 1994