2010R1089 — EN — 31.12.2014 — 003.001

This document is meant purely as a documentation tool and the institutions do not assume any liability for its contents

Amended by:









▼B

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







THE EUROPEAN COMMISSION, Having regard to the Treaty on the Functioning of the European Union, Having regard to 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) ( 1 ), and in particular Article 7(1) thereof, Whereas: (1) Directive 2007/2/EC lays down general rules for the establishment of the Infrastructure for Spatial Information in the European Community. Within this infrastructure, Member States are required to make available data sets related to one or several of the Annexes in Directive 2007/2/EC and the corresponding spatial data services in conformity with the technical arrangements for the interoperability and, where practicable, harmonisation of spatial data sets and services. (2) The technical arrangements take into account relevant user requirements, which were elicited from stakeholders through a user requirements survey and by analysing the submitted reference material and relevant Union environmental policies and policies or activities which may have an impact on the environment. (3) The feasibility of the technical arrangements and their proportionality in terms of the likely costs and benefits were analysed by the Commission based on the testing results reported by the stakeholders, replies from Member States through the national contact points to a request for information on cost benefit considerations and evidence from studies conducted by Member States on the costs and benefits of spatial data infrastructures at regional level. (4) Representatives of Member States as well as other natural or legal persons with an interest in the spatial data, including users, producers, added value service providers or any coordinating body were given the opportunity to participate in the drafting of the technical arrangements through proposed experts and to evaluate the draft implementing rules through a stakeholder consultation and testing exercise. (5) In order to achieve interoperability and benefit from the endeavours of users’ and producers’ communities, when appropriate, international standards are integrated into the concepts and definitions of the elements of spatial data themes listed in the Directive 2007/2/EC Annex I, II or III. (6) In order to ensure interoperability and harmonisation across spatial data themes, the Member States should meet requirements for common data types, the identification of spatial objects, metadata for interoperability, generic network model and other concepts and rules that apply to all spatial data themes. (7) In order to ensure the interoperability and harmonisation within one spatial data theme, the Member States should use the classifications and definitions of spatial objects, their key attributes and association roles, data types, value domains and specific rules that apply to individual spatial data theme. (8) Since the code list values required for the implementation of this Regulation are not included in this Regulation, this Regulation should only become applicable once these are adopted as a legal act. It is therefore appropriate to defer the applicability of this Regulation. (9) The measures provided for in this Regulation are in accordance with the opinion of the Committee established by Article 22 of Directive 2007/2/EC, Whereas: HAS ADOPTED THIS REGULATION:







▼M3

Article 1

Subject Matter and Scope

1. This Regulation sets out the requirements for technical arrangements for the interoperability and, where practicable, harmonisation of spatial data sets and spatial data services corresponding to the themes listed in Annexes I, II and III to Directive 2007/2/EC.

2. This Regulation does not apply to the network services falling within the scope of Commission Regulation (EC) No 976/2009 ( 2 ).

▼B

Article 2

Definitions

▼M2

For the purposes of this Regulation, the following definitions as well as the theme-specific definitions set out in the Annexes shall apply:

▼B

1. ‘abstract type’ means a type that cannot be instantiated, but which may have attributes and association roles,

2. ‘association role’ means a value or object, to which a type has a relationship, as referred to in Article 8 (2b) of Directive 2007/2/EC,

3. ‘attribute’ means a characteristic of a type, as referred to in Article 8 (2c) of Directive 2007/2/EC,

▼M2 —————

▼B

5. ‘code list’ means an open enumeration that can be extended,

6. ‘data type’ means a descriptor of a set of values that lack identity, in accordance with ►M2 ISO/TS 19103:2005 ◄ ,

7. ‘enumeration’ means a data type whose instances form a fixed list of named literal values. Attributes of an enumerated type may only take values from this list,

8. ‘external object identifier’ means a unique object identifier which is published by the responsible body, which may be used by external applications to reference the spatial object,

9. ‘identifier’ means a linguistically independent sequence of characters capable of uniquely and permanently identifying that with which it is associated, in accordance with ►M2 EN ISO 19135:2007 ◄ ,

10. ‘instantiate’ means to create an object that is conformant with the definition, attributes, association roles and constraints specified for the instantiated type,

11. ‘layer’ means a basic unit of geographic information that may be requested as a map from a server in accordance with ►M2 EN ISO 19128:2008 ◄ ,

12. ‘life-cycle information’ means a set of properties of a spatial object that describe the temporal characteristics of a version of a spatial object or the changes between versions,

13. ‘metadata element’ means a discrete unit of metadata, in accordance with ►M2 EN ISO 19115:2005/AC:2008 ◄ ,

14. ‘package’ means a general purpose mechanism for organizing elements into groups,

15. ‘register’ means a set of files containing identifiers assigned to items with descriptions of the associated items, in accordance with ►M2 EN ISO 19135:2007 ◄ ,

16. ‘spatial object type’ means a classification of spatial objects,

17. ‘style’ means a mapping from spatial object types and their properties and constraints to parameterized symbols used in drawing maps,

18. ‘sub-type of’ means a relationship between a more specific type and a more general type, where the more specific type is fully consistent with the more general type and contains additional information, as adapted from ►M2 ISO/TS 19103:2005 ◄ ,

19. ‘type’ means spatial object type or data type,

20. ‘voidable’ means that, for an attribute or association role a value of ‘void’ may be made available if no corresponding value is contained in the spatial data sets maintained by the Member States or no corresponding value can be derived from existing values at reasonable costs. If an attribute or association role is not voidable, the table cell specifying its voidability is left blank,

▼M2

21. ‘property’ means attribute or association role,

22. ‘union type’ means a type consisting of one and only one of several alternatives (listed as member attributes), in accordance with ISO/TS 19103:2005,

23. ‘association class’ means a type that defines additional properties on a relationship between two other types,

24. ‘coverage’ means a spatial object that acts as a function to return values from its range for any direct position within its spatial, temporal or spatiotemporal domain, in accordance with ISO 19123:2007,

25. ‘domain’ means a well-defined set, in accordance with ISO/TS 19103:2005,

26. ‘range’ means a set of feature attribute values associated by a function with the elements of the domain of a coverage, in accordance with EN ISO 19123:2007,

27. ‘rectified grid’ means a grid for which there is an affine transformation between the grid coordinates and the coordinates of a coordinate reference system, in accordance with EN ISO 19123:2007,

28. ‘referenceable grid’ means a grid associated with a transformation that can be used to convert grid coordinate values into values of coordinates referenced to an external coordinate reference system, in accordance with EN ISO 19123:2007,

29. ‘tessellation’ means a partitioning of a space into a set of conterminous subspaces having the same dimension as the space being partitioned. A tessellation in a 2D space consists of a set of non-overlapping polygons that entirely cover a region of interest,

30. ‘narrower value’ means a value that has a hierarchical relationship to a more general parent value,

▼M3

31. ‘end point’ means the internet address used to directly call an operation provided by a spatial data service,

32. ‘access point’ means an internet address containing a detailed description of a spatial data service, including a list of end points to allow its execution,

33. ‘Invocable spatial data service’ means all of the following: (a) a spatial data service with metadata which fulfils the requirements of Commission Regulation (EC) No 1205/2008 ( 3 ), (b) a spatial data service with at least one resource locator that is an access point, (c) a spatial data service in conformity with a documented and publicly available set of technical specifications providing the information necessary for its execution,

34. ‘interoperable spatial data service’ means an invocable spatial data service which fulfils the requirements of Annex VI,

35. ‘harmonised spatial data service’ means an interoperable spatial data service which fulfils the requirements of Annex VII,

36. ‘conformant spatial data set’ means a spatial data set which fulfils the requirements of this Regulation,

37. ‘operation’ means an action supported by a spatial data service,

38. ‘interface’ means the named set of operations that characterise the behaviour of an entity as defined by ISO 19119:2005.

▼B

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.

Article 4

Types for the Exchange and Classification of Spatial Objects

▼M2

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, enumerations and code lists that are defined in Annexes II, III and IV for the themes the data sets relate to.

▼B

2. Spatial object types and data types shall comply with the definitions and constraints and include the attributes and association roles set out in ►M2 the Annexes ◄ .

▼M1

3. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in ►M2 the Annexes ◄ . ►M2 The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction. ◄

▼M1 —————

▼B

Article 5

Types

1. For all types defined in this Regulation, a language-neutral name for computers is given between parentheses in the title of the section specifying the requirements for that type. This language-neutral name shall be used for referring to the corresponding type in the definition of an attribute or association role.

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

3. Abstract types shall not be instantiated.

▼M2 —————

▼M2

Article 6

▼M3

Code Lists and Enumerations for Spatial Data Sets

▼M2

1. ►M3 Code lists shall be one of the following types, as specified in the Annexes I to IV: ◄

(a) code lists whose allowed values comprise only the values specified in this Regulation;

(b) code lists whose allowed values comprise the values specified in this Regulation and narrower values defined by data providers;

(c) code lists whose allowed values comprise the values specified in this Regulation and additional values at any level defined by data providers;

(d) code lists, whose allowed values comprise any values defined by data providers.

For the purposes of points (b), (c) and (d), in addition to the allowed values, data providers may use the values specified in the relevant INSPIRE Technical Guidance document available on the INSPIRE web site of the Joint Research Centre.

2. Code lists may be hierarchical. Values of hierarchical code lists may have a more general 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.

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

4. Attributes or association roles of spatial object types or data types whose type is a code list may only take values that are allowed according to the specification of the code list.

5. Attributes or association roles of spatial object types or data types that have an enumeration type may only take values from the lists specified for the enumeration type.

▼B

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.

Article 8

Updates

1. Member States shall make available updates of data on a regular basis.

2. All updates shall be made 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 ►M2 the Annexes ◄ .

▼M3

3. The updates of data shall be made available to all related spatial data services according to the deadline specified in paragraph 2.

▼B

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.

Article 10

Life-cycle of Spatial Objects

1. Different versions of the same spatial object shall always be instances of the same spatial object type.

2. The namespace and localId attributes of the external object identifier shall remain the same for different versions of a spatial object.

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

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 ( 4 ) shall be used, unless other temporal reference systems are specified for a specific spatial data theme in ►M2 the Annexes ◄ .

2. If other temporal reference systems are used, these shall be specified in the data set metadata.

Article 12

Other Requirements & Rules

▼M2

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.

▼B

2. All measurement values shall be expressed using ►M2 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.

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

4. In addition, all theme-specific requirements set out in Annex II shall apply.

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.

▼M2

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

▼B

Article 14

Portrayal

1. For the portrayal of spatial data sets using a view network service as specified in Commission Regulation No 976/2009 ( 5 ), the following shall be available:

(a) the layers specified in Annex II for the theme or themes the data set is related to;

(b) for each layer at least a default portrayal style, with as a minimum an associated title and a unique identifier.

2. For each layer, Annex II defines the following:

(a) a human readable title of the layer to be used for display in user interface;

▼M2

(b) the spatial object type(s), or sub-set thereof, that constitute(s) the content of the layer.

▼M2

3. 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, III and IV, all of the following requirements shall be fulfilled:

(a) the placeholder <CodeListValue> shall represent the values of the relevant code list, with the first letter in upper case;

(b) the placeholder <human-readable name> shall represent the human-readable name of the code list values;

(c) the spatial object type shall include the relevant attribute and code list, in parentheses;

(d) one example of a layer shall be given.

▼M3

Article 14a

Requirements for invocable spatial data services

Not later than 10 December 2015, Member States shall provide the invocable spatial data services metadata in conformity with the requirements set out in Annex V.

Article 14b

Interoperability arrangements and harmonisation requirements for invocable spatial data services

The invocable spatial data services relating to the data contained in at least one conformant spatial data set shall fulfil the interoperability requirements set out in Annexes V and VI and, where practicable, the harmonisation requirements set-out in Annex VII.

▼B

Article 15

Entry into force

This Regulation shall enter into force on the twentieth day following its publication in the Official Journal of the European Union.

It shall apply from 15 December 2010.

This Regulation shall be binding in its entirety and directly applicable in all Member States.









ANNEX I

▼M2

COMMON TYPES, DEFINITIONS AND REQUIREMENTS

1. TYPES DEFINED IN EUROPEAN AND INTERNATIONAL STANDARDS

The following common types, used in attributes or association roles of spatial object types or data types, are defined as follows:

(1) For the types Any, Angle, Area, Boolean, CharacterString, Date, DateTime, Decimal, Distance, Integer, Length, Measure, Number, Probability, Real, RecordType, Sign, UnitOfMeasure, Velocity and Volume, the definitions given in ISO/TS 19103:2005 shall apply.

(2) For the types DirectPosition, GM_Boundary, GM_Curve, GM_MultiCurve, GM_MultiSurface, GM_Object, GM_Point, GM_Primitive, GM_Solid, GM_Surface and GM_Tin, the definitions given in EN ISO 19107:2005 shall apply.

(3) For the types TM_Duration, TM_GeometricPrimitive, TM_Instant, TM_Object, TM_Period and TM_Position, the definitions given in EN ISO 19108:2005/AC:2008 shall apply.

(4) For the type GF_PropertyType, the definitions given in EN ISO 19109:2006 shall apply.

(5) For the types CI_Citation, CI_Date, CI_RoleCode, EX_Extent, EX_VerticalExtent, MD_Distributor, MD_Resolution and URL, the definitions given in EN ISO 19115:2005/AC:2008 shall apply.

(6) For the type CV_SequenceRule, the definitions given in EN ISO 19123:2007 shall apply.

(7) For the types AbstractFeature, Quantity and Sign, the definitions given in EN ISO 19136:2009 shall apply.

(8) For the types LocalisedCharacterString, PT_FreeText and URI, the definitions given in CEN ISO/TS 19139:2009 shall apply.

(9) For the type LC_LandCoverClassificationSystem, the definitions given in ISO 19144-2:2012 shall apply.

(10) For the types GFI_Feature, Location, NamedValue, OM_Observation, OM_Process, SamplingCoverageObservation, SF_SamplingCurve, SF_SamplingPoint, SF_SamplingSolid, SF_SamplingSurface and SF_SpatialSamplingFeature, the definitions given in ISO 19156:2011 shall apply.

(11) For the types Category, Quantity, QuantityRange and Time, the definitions given in Robin, Alexandre (ed.), OGC®SWE Common Data Model Encoding Standard, version 2.0.0, Open Geospatial Consortium, 2011 shall apply.

(12) For the types TimeValuePair and Timeseries, the definitions given in Taylor, Peter (ed.), OGC® WaterML 2.0: Part 1 – Timeseries, v2.0.0, Open Geospatial Consortium, 2012 shall apply.

(13) For the types CGI_LinearOrientation and CGI_PlanarOrientation, the definitions given in CGI Interoperability Working Group, Geoscience Markup Language (GeoSciML), version 3.0.0, Commission for the Management and Application of Geoscience Information (CGI) of the International Union of Geological Sciences, 2011 shall apply.

▼B

2. COMMON DATA TYPES

2.1. Identifier (Identifier)

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

Attributes of the data type Identifier







Attribute Definition Type Voidability localId A local identifier, assigned by the data provider. The local identifier is unique within the namespace, that is no other spatial object carries the same unique identifier. CharacterString namespace Namespace uniquely identifying the data source of the spatial object. CharacterString versionId The identifier of the particular version of the spatial object, with a maximum length of 25 characters. If the specification of a spatial object type with an external object identifier includes life-cycle information, the version identifier is used to distinguish between the different versions of a spatial object. Within the set of all versions of a spatial object, the version identifier is unique. CharacterString voidable

▼M2 —————

▼M2

2.2. Related Party (RelatedParty)

An organisation or a person with a role related to a resource.

Attributes of the data type RelatedParty







Attribute Definition Type Voidability individualName Name of the related person. PT_FreeText voidable organisationName Name of the related organisation. PT_FreeText voidable positionName Position of the party in relation to a resource, such as head of department. PT_FreeText voidable contact Contact information for the related party. Contact voidable role Roles of the party in relation to a resource, such as owner. PartyRoleValue voidable

Constraints of the data type RelatedParty

At least the individual, organisation or position name shall be provided.

2.3. Contact (Contact)

Communication channels by which it is possible to gain access to someone or something.

Attributes of the data type Contact







Attribute Definition Type Voidability address An address provided as free text. AddressRepresentation voidable contactInstructions Supplementary instructions on how or when to contact an individual or organisation. PT_FreeText voidable electronicMailAddress An address of the organisation's or individual's electronic mailbox. CharacterString voidable hoursOfService Periods of time when the organisation or individual can be contacted. PT_FreeText voidable telephoneFacsimile Number of a facsimile machine of the organisation or individual. CharacterString voidable telephoneVoice Telephone number of the organisation or individual. CharacterString voidable website Pages provided on the World Wide Web by the organisation or individual. URL voidable

2.4. Document Citation (DocumentCitation)

Citation for the purposes of unambiguously referencing a document.

Attributes of the data type DocumentCitation







Attribute Definition Type Voidability name Name of the document. CharacterString shortName Short name or alternative title of the document. CharacterString voidable date Date of creation, publication or revision of the document. CI_Date voidable link Link to an online version of the document URL voidable specificReference Reference to a specific part of the document. CharacterString voidable

2.5. Legislation Citation (LegislationCitation)

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

This type is a sub-type of DocumentCitation.

Attributes of the data type LegislationCitation







Attribute Definition Type Voidability identificationNumber Code used to identify the legislative instrument CharacterString officialDocumentNumber Official document number used to uniquely identify the legislative instrument. CharacterString dateEnteredIntoForce Date the legislative instrument entered into force. TM_Position dateRepealed Date the legislative instrument was repealed. TM_Position level The level at which the legislative instrument is adopted. LegislationLevelValue journalCitation Citation of the official journal in which the legislation is published. OfficialJournalInformation

Constraints of the data type LegislationCitation

If the link attribute is void, the journal citation shall be provided.

2.6. Official Journal Information (OfficialJournalInformation)

Full citation of the location of the legislative instrument within the official journal.

Attributes of the data type OfficialJournalInformation







Attribute Definition Type Voidability officialJournalIdentification Reference to the location within the official journal within which the legislative instrument was published. This reference shall be comprised of three parts: — the title of the official journal — the volume and/or series number — Page number(s) CharacterString ISSN The International Standard Serial Number (ISSN) is an eight-digit number that identifies the periodical publication in which the legislative instrument was published. CharacterString ISBN International Standard Book Number (ISBN) is an nine-digit number that uniquely identifies the book in which the legislative instrument was published. CharacterString linkToJournal Link to an online version of the official journal URL

2.7. Thematic Identifier (ThematicIdentifier)

Thematic identifier to uniquely identify the spatial object.

Attributes of the data type ThematicIdentifier







Attribute Definition Type Voidability identifier Unique identifier used to identify the spatial object within the specified identification scheme. CharacterString identifierScheme Identifier defining the scheme used to assign the identifier. CharacterString

▼B

3. COMMON ENUMERATIONS

3.1. Vertical Position (VerticalPositionValue)

The relative vertical position of a spatial object.







Allowed values for the enumeration VerticalPositionValue Value Definition onGroundSurface The spatial object is on ground level. suspendedOrElevated The spatial object is suspended or elevated. underground The spatial object is underground.

4. COMMON CODE LISTS

▼M2

4.1. Condition of Facility (ConditionOfFacilityValue)

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

The allowed values for this code list comprise the values in the table below and narrower values defined by data providers.

Values for the code list ConditionOfFacilityValue







Value Name Definition functional functional The facility is functional. projected projected The facility is being designed. Construction has not yet started. underConstruction under construction The facility is under construction and not yet functional. This applies only to the initial construction of the facility and not to maintenance work. disused disused The facility is no longer used, but is not being or has not been decommissioned. decommissioned decommissioned The facility is no longer used and is being or has been decommissioned.

▼B

4.2. Country Code (CountryCode)

Country code as defined in the Interinstitutional style guide published by the Publications Office of the European Union.

▼M2 —————

▼M1

The allowed values for this code list are the two-letter country codes listed in the Interinstitutional style guide published by the Publications Office of the European Union.

▼M2

4.3. Legislation Level (LegislationLevelValue)

The level at which a legal act or convention has been adopted.

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

Data providers may use the values specified in the INSPIRE Technical Guidance document on the INSPIRE Generic Conceptual Model.

4.4. Party Role (PartyRoleValue)

Roles of parties related to or responsible for a resource.

The allowed values for this code list comprise the values of the following code lists or other code lists specified by data providers:

— Role Code (CI_RoleCode): Functions performed by a responsible party, as specified in EN ISO 19115:2005/AC:2008.

— Role of a Related Party (RelatedPartyRoleValue): Classification of related party roles, as specified in the table below.

Values for the code list RelatedPartyRoleValue







Value Name Definition authority authority A party legally mandated to supervise a resource and/or parties related to a resource. operator operator A party that runs a resource. owner owner A party that owns a resource, i.e., to which a resource belongs in a legal sense.

4.5. Climate and Forecast Standard Names (CFStandardNamesValue)

Definitions of phenomena observed in meteorology and oceanography.

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

Data providers may use the values specified in the INSPIRE Technical Guidance document on the INSPIRE Generic Conceptual Model.

4.6. Gender (GenderValue)

Gender of a person or group of persons.

The allowed values for this code list comprise only the values specified in the table below.

Values for the code list GenderValue







Value Name Definition female female A person or group of persons of female gender. male male A person or group of persons of male gender. unknown unknown A person or group of persons of unknown gender.

▼B

5. GENERIC NETWORK MODEL

5.1. Spatial Object Types

5.1.1. Cross Reference (CrossReference)

Represents a reference between two elements in the same network.







Association roles of the spatial object type CrossReference Association role Definition Type Voidability element The cross referenced elements NetworkElement

5.1.2. Generalised Link (GeneralisedLink)

Abstract base type representing a linear network element that may be used as a target in linear referencing.

This type is a sub-type of NetworkElement.

This type is abstract.

5.1.3. Grade Separated Crossing (GradeSeparatedCrossing)

Indicator which of two or more intersecting elements is/are below and which is/are above, to be used if elevation coordinates are not present or cannot be trusted.

This type is a sub-type of NetworkElement.







Association roles of the spatial object type GradeSeparatedCrossing Association role Definition Type Voidability element Sequence of crossing links. The order reflects their elevation; the first link is the lower link. Link

5.1.4. Link (Link)

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

This type is a sub-type of GeneralisedLink.

This type is abstract.







Attributes of the spatial object type Link Attribute Definition Type Voidability centrelineGeometry The geometry that represents the centreline of the link. GM_Curve fictitious Indicator that the centreline geometry of the link is a straight line with no intermediate control points – unless the straight line represents the geography in the resolution of the data set appropriately. Boolean







Association roles of the spatial object type Link Association role Definition Type Voidability endNode The optional end node for this link. The end node may be the same instance as the start node. Node startNode The optional start node for this link. Node

5.1.5. Link Sequence (LinkSequence)

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

This type is a sub-type of GeneralisedLink.

This type is abstract.







Attributes of the spatial object type LinkSequence Attribute Definition Type Voidability link The ordered collection of directed links that constitute the link sequence. DirectedLink

5.1.6. Link Set (LinkSet)

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

This type is a sub-type of NetworkElement.

This type is abstract.







Association roles of the spatial object type LinkSet Association role Definition Type Voidability link The set of links and link sequences that constitute the link set. GeneralisedLink

5.1.7. Network (Network)

A network is a collection of network elements.







Attributes of the spatial object type Network Attribute Definition Type Voidability geographicalName Geographical name for this network. GeographicalName voidable







Association roles of the spatial object type Network Association role Definition Type Voidability elements The collection of elements that constitutes the network. NetworkElement

5.1.8. Network Area (NetworkArea)

A 2-dimensional element in a network.

This type is a sub-type of NetworkElement.

This type is abstract.







Attributes of the spatial object type NetworkArea Attribute Definition Type Voidability geometry Represents the geometric properties of the area GM_Surface

5.1.9. Network Connection (NetworkConnection)

Represents a logical connection between two or more network elements in different networks.

This type is a sub-type of NetworkElement.







Attribute Definition Type Voidability type Categorisation of the network connection. ConnectionTypeValue voidable







Association role Definition Type Voidability element Network elements in different networks NetworkElement

All elements have to be in different networks

5.1.10. Network Element (NetworkElement)

Abstract base type representing an element in a network. Every element in a network provides some function that is of interest in the network.

This type is abstract.







Attributes of the spatial object type NetworkElement Attribute Definition Type Voidability beginLifespanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable endLifespanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable inspireId External object identifier of the spatial object. Identifier







Association roles of the spatial object type NetworkElement Association role Definition Type Voidability inNetwork The networks in which a network element is a member. Network voidable

5.1.11. Network Property (NetworkProperty)

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

This type is abstract.







Attributes of the spatial object type NetworkProperty Attribute Definition Type Voidability beginLifespanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable endLifespanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable inspireId External object identifier of the spatial object. Identifier networkRef Spatial reference of the network-related property. NetworkReference voidable

5.1.12. Node (Node)

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

This type is a sub-type of NetworkElement.

This type is abstract.







Attributes of the spatial object type Node Attribute Definition Type Voidability geometry The location of the node. GM_Point







Association roles of the spatial object type Node Association role Definition Type Voidability spokeEnd The links that enter the node. Link voidable spokeStart The links that leave the node. Link voidable

5.2. Data Types

5.2.1. Directed Link (DirectedLink)

A link either in its positive or negative direction.







Attributes of the data type DirectedLink Attribute Definition Type Voidability Voidability direction Indicates if the directed link agrees (positive) or disagrees (negative) with the positive direction of the link. Sign







Association roles of the data type DirectedLink Association role Definition Type Voidability Voidability link The link Link

5.2.2. Link Reference (LinkReference)

A network reference to a linear network element.

This type is a sub-type of NetworkReference.







Attribute Definition Type Voidability applicableDirection The directions of the generalised link to which the reference applies. In cases where a property does not apply to a direction along a link, but represents a phenomenon along a link, ‘inDirection’ refers to the right side in the direction of the link. LinkDirectionValue voidable

Linear reference targets must be linear network elements. That is, if linear referencing is used or direction is relevant, the target of the network reference shall be a link or a link sequence.

5.2.3. Network Reference (NetworkReference)

A reference to a network element.







Association roles of the data type NetworkReference Association role Definition Type Voidability element The referenced network element. NetworkElement

5.2.4. Simple Linear Reference (SimpleLinearReference)

A network reference that is restricted to part of a linear network element. The part is the part of the network element between fromPosition and toPosition.

This type is a sub-type of LinkReference.







Attributes of the data type SimpleLinearReference Attribute Definition Type Voidability fromPosition The start position of the linear element, expressed as the distance from the start of the linear network element along its curve geometry. Length offset An offset from the centreline geometry of the generalised link, where applicable; a positive offset is to the right in the direction of the link, a negative offset is to the left. Length voidable toPosition The end position of the linear element, expressed as the distance from the start of the linear network element along its curve geometry. Length

5.2.5. Simple Point Reference (SimplePointReference)

A network reference that is restricted to a point on a linear network element. The point is the location on the network element at the position atPosition along the network.

This type is a sub-type of LinkReference.







Attributes of the data type SimplePointReference Attribute Definition Type Voidability atPosition Position of the point, expressed as the distance from the start of the linear network element along its curve geometry. Length offset An offset from the centreline geometry of the generalised link, where applicable; a positive offset is to the right in the direction of the link, a negative offset is to the left. Length voidable

5.3. Code Lists

5.3.1. Connection Type (ConnectionTypeValue)

Types of connections between different networks.

▼M2

The allowed values for this code list comprise only the values in the table below.

▼M1







►M2 Values for the code list ◄ ConnectionTypeValue Value Definition crossBorderConnected Connection between two network elements in different networks of the same type, but in adjacent areas. The referenced network elements represent the different, but spatially connected real-world phenomena. crossBorderIdentical Connection between two network elements in different networks of the same type, but in adjacent areas. The referenced network elements represent the same real-world phenomena. intermodal Connection between two network elements in different transport networks that use a different transport mode. The connection represents a possibility for the transported media (people, goods, etc) to change from one transport mode to another.

▼B

5.3.2. Link Direction (LinkDirectionValue)

List of values for directions relative to a link

▼M2

The allowed values for this code list comprise only the values in the table below.

▼M1







►M2 Values for the code list ◄ LinkDirectionValue Value Definition bothDirections In both directions. inDirection In direction of the link. inOppositeDirection In the opposite direction of the link.

▼M2

6. COVERAGE MODEL

The INSPIRE coverage model consists of the following packages:

— Coverages (Base)

— Coverages (Domain And Range)

6.1. Coverages (Base)

6.1.1. Spatial object types

The package Coverages (Base) contains the spatial object type Coverage.

6.1.1.1. Coverage (Coverage)

Spatial object that acts as a function to return values from its range for any direct position within its spatial, temporal or spatiotemporal domain.

This type is abstract.







Attribute Definition Type Voidability metadata Application specific metadata of the coverage. Any rangeType Description of the structure of the range values. RecordType

6.2. Coverages (Domain And Range)

6.2.1. Spatial object types

The package Coverages (Domain and Range) contains the following spatial object types:

— Coverage (Domain And Range Representation)

— Rectified Grid Coverage

— Referenceable Grid Coverage

6.2.1.1. Coverage (Domain And Range Representation) (CoverageByDomainAndRange)

Coverage which provides the domain and range as separate properties.

This type is a sub-type of Coverage.

This type is abstract.







Attribute Definition Type Voidability coverageFunction Description of how range values at locations in the coverage domain can be obtained. CoverageFunction domainSet Configuration of the domain of the coverage described in terms of coordinates. Any rangeSet Set of values associated by a function with the elements of the domain of the coverage. Any

The grid function shall only be valid for domains that are grids.

6.2.1.2. Rectified Grid Coverage (RectifiedGridCoverage)

Coverage whose domain consists of a rectified grid.

This type is a sub-type of CoverageByDomainAndRange.

The domain shall be a rectified grid.

Grid points of a RectifiedGridCoverage shall coincide with the centres of cells of the geographical grids defined in Section 2.2 of Annex II at any resolution level.

6.2.1.3. Referenceable Grid Coverage (ReferenceableGridCoverage)

Coverage whose domain consists of a referenceable grid.

This type is a sub-type of CoverageByDomainAndRange.

The domain shall be a referenceable grid.

6.2.2. Data types

6.2.2.1. Coverage Function (CoverageFunction)

Description of how range values at locations in the coverage domain can be obtained.

This type is a union type.







Attribute Definition Type Voidability ruleDefinition A formal or informal description of the coverage function as text. CharacterString ruleReference A formal or informal description of the coverage function as reference. URI gridFunction Mapping rule for grid geometries. GridFunction

6.2.2.2. Grid Function (GridFunction)

An explicit mapping rule for grid geometries.







Attribute Definition Type Voidability sequenceRule Description of how the grid points are ordered for association to the elements of the values in the range set of the coverage. CV_SequenceRule startPoint The grid point to be associated with the first record in the range set of the coverage. Integer

7. OBSERVATIONS MODEL

The INSPIRE observations model consists of the following packages:

— Observation References

— Processes

— Observable Properties

— Specialised Observations

7.1. Observation References

7.1.1. Spatial object types

The package Observation References contains the spatial object type Observation Set.

7.1.1.1. Observation Set (ObservationSet)

Links a set of Observations.







Attribute Definition Type Voidability inspireId External object identifier of the spatial object. Identifier extent Information about the spatial and temporal extent. EX_Extent







Association role Definition Type Voidability member One member of the ObservationSet. OM_Observation

7.2. Processes

7.2.1. Spatial object types

The package Processes contains the spatial object type Process.

7.2.1.1. Process (Process)

Description of an observation process.

This type is a sub-type of OM_Process.







Attribute Definition Type Voidability inspireId External object identifier of the spatial object. Identifier voidable name Name of the Process. CharacterString voidable type Type of process. CharacterString voidable documentation Further information (online/offline) associated with the process. DocumentCitation voidable processParameter Parameter controlling the application of the process and, as a consequence its output. ProcessParameter voidable responsibleParty Individual or organisation related to the process. RelatedParty voidable

7.2.2. Data types

7.2.2.1. Process Parameter (ProcessParameter)

Description of the given parameter







Attribute Definition Type Voidability name Name of the process parameter. ProcessParameterNameValue description Description of the process parameter. CharacterString

7.2.3. Code lists

7.2.3.1. Process Parameter Name (ProcessParameterNameValue)

A code list of names of process parameters.

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

7.3. Observable Properties

7.3.1. Data types

7.3.1.1. Constraint (Constraint)

A constraint on some property e.g. wavelength = 200 nm.







Attribute Definition Type Voidability constrainedProperty The property being constrained. e.g. ‘colour’ if the constraint is ‘colour = blue’. PhenomenonTypeValue label A human readable title for the constraint as a whole. CharacterString

7.3.1.2. Category Constraint (CategoryConstraint)

A constraint based on some qualifying category. e.g. colour = ‘red’.

This type is a sub-type of Constraint.







Attribute Definition Type Voidability comparison A comparison operator. In the case of a category constraint it should be ‘equalTo’ or ‘notEqualTo’. ComparisonOperatorValue value The value of the property that is constrained e.g. ‘blue’ (if the constrained property is colour). CharacterString

7.3.1.3. Range Constraint (RangeConstraint)

A numerical range constraint on some property e.g. wavelength ≥ 300 nm and wavelength ≤ 600 nm.

This type is a sub-type of Constraint.







Attribute Definition Type Voidability value The numerical value range of the property that is constrained. RangeBounds uom Units of measure used in the constraint. UnitOfMeasure

7.3.1.4. Range Bounds (RangeBounds)

The start and end bounding values of a numerical range (e.g. start ≥ 50, end ≤ 99).







Attribute Definition Type Voidability startComparison The comparator used for the lower range limit (e.g. greaterThanOrEqualTo). ComparisonOperatorValue rangeStart The lower limit of the range. Real endComparison The comparator used for the upper range limit (e.g. lessThan). ComparisonOperatorValue rangeEnd The upper limit of the range. Real

7.3.1.5. Scalar Constraint (ScalarConstraint)

A numerical scalar constraint on some property e.g. length ≥ 1 m.

This type is a sub-type of Constraint.







Attribute Definition Type Voidability value The numerical value of the property that is constrained. Real comparison The comparator to be used in the constraint e.g. greaterThan. ComparisonOperatorValue uom Units of measure used in the constraint. UnitOfMeasure

7.3.1.6. Other Constraint (OtherConstraint)

A constraint which is not modelled in a structured way but may be described using the freetext ‘description’ attribute.

This type is a sub-type of Constraint.







Attribute Definition Type Voidability description A description of the constraint. CharacterString

7.3.1.7. Statistical Measure (StatisticalMeasure)

A description of some statistical measure e.g. ‘daily maximum’.







Attribute Definition Type Voidability label A human readable title for the statistical measure. CharacterString statisticalFunction A statistical function e.g. mean. StatisticalFunctionTypeValue aggregationTimePeriod A temporal range over which a statistic is calculated. e.g. a day, an hour. TM_Duration aggregationLength A one dimensional spatial range over which a statistic is calculated, for example 1 metre. Length aggregationArea A two dimensional spatial range over which a statistic is calculated, for example 1 square metre. Area aggregationVolume A three dimensional spatial range over which a statistic is calculated, for example 1 cubic metre. Volume otherAggregation Any other type of aggregation. Any







Association role Definition Type Voidability derivedFrom One statistical measure may be derived from another, e.g. monthly maximum temperatures may be derived from daily mean temperatures. StatisticalMeasure

7.3.2. Enumerations

7.3.2.1. Comparison Operator (ComparisonOperatorValue)

An enumeration of comparison operators (e.g. greater than)







Value Definition equalTo exactly equal to notEqualTo not exactly equal to lessThan less than greaterThan greater than lessThanOrEqualTo less than or exactly equal to greaterThanOrEqualTo greater than or exactly equal to

7.3.3. Code lists

7.3.3.1. Phenomenon Type (PhenomenonTypeValue)

A code list of phenomena (e.g. temperature, wind speed).

The allowed values for this code list comprise the values of the following code lists or other code lists defined by data providers:

— Climate and Forecast Standard Names (CFStandardNamesValue): Definitions of phenomena observed in meteorology and oceanography, as specified in Section 4.5 of this Annex.

— Profile Element Parameter Name (ProfileElementParameterNameValue): Properties that can be observed to characterize the profile element, as specified in Section 3.3.8 of Annex IV.

— Soil Derived Object Parameter Name (SoilDerivedObjectParameterNameValue): Soil-related properties that can be derived from soil and other data, as specified in Section 3.3.9 of Annex IV.

— Soil Profile Parameter Name (SoilProfileParameterNameValue): Properties that can be observed to characterize the soil profile, as specified in Section 3.3.12 of Annex IV.

— Soil Site Parameter Name (SoilSiteParameterNameValue): Properties that can be observed to characterize the soil site, as specified in Section 3.3.13 of Annex IV.

— EU Air Quality Reference Component (EU_AirQualityReferenceComponentValue): Definitions of phenomena regarding air quality in the context of reporting under Union legislation, as specified in Section 13.2.1.1 of Annex IV.

— WMO GRIB Code and Flags Table 4.2 (GRIB_CodeTable4_2Value): Definitions of phenomena observed in meteorology, as specified in Section 13.2.1.2 of Annex IV.

— BODC P01 Parameter Usage (BODC_P01ParameterUsageValue): Definitions of phenomena observed in oceanography, as specified in Section 14.2.1.1 of Annex IV.

7.3.3.2. Statistical Function Type (StatisticalFunctionTypeValue)

A code list of statistical functions (e.g. maximum, minimum, mean).

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

7.4. Specialised Observations

7.4.1. Spatial object types

The package Specialised Observations contains the following spatial object types:

— Grid Observation

— Grid Series Observation

— Point Observation

— Point Observation Collection

— Multi Point Observation

— Point Time Series Observation

— Profile Observation

— Trajectory Observation

7.4.1.1. Grid Observation (GridObservation)

Observation representing a gridded field at a single time instant.

This type is a sub-type of SamplingCoverageObservation.

featureOfInterest shall be a SF_SamplingSolid or SF_SamplingSurface.

phenomenonTime shall be a TM_Instant.

result shall be a RectifiedGridCoverage or RefererencableGridCoverage.

7.4.1.2. Grid Series Observation (GridSeriesObservation)

Observation representing an evolving gridded field at a succession of time instants.

This type is a sub-type of SamplingCoverageObservation.

featureOfInterest shall be a SF_SamplingSolid.

phenomenonTime shall be a TM_Period.

result shall be a RectifiedGridCoverage or a ReferenceableGridCoverage.

7.4.1.3. Point Observation (PointObservation)

Observation that represents a measurement of a property at a single point in time and space.

This type is a sub-type of SamplingCoverageObservation.

featureOfInterest shall be a SF_SamplingPoint.

phenomenonTime shall be a TM_Instant.

7.4.1.4. Point Observation Collection (PointObservationCollection)

A collection of Point Observations.

This type is a sub-type of ObservationSet.

Each member shall be a PointObservation.

7.4.1.5. Multi Point Observation (MultiPointObservation)

Observation that represents a set of measurements all made at exactly the same time but at different locations.

This type is a sub-type of SamplingCoverageObservation.

featureOfInterest shall be a SF_SamplingCurve, SF_SamplingSurface or SF_SamplingSolid.

phenomenonTime shall be a TM_Instant

result shall be a MultiPointCoverage.

7.4.1.6. Point Time Series Observation (PointTimeSeriesObservation)

Observation that represents a time-series of point measurements of a property at a fixed location in space.

This type is a sub-type of SamplingCoverageObservation.

featureOfInterest shall be a SF_SamplingPoint.

phenomenonTime shall be a TM_Period.

result shall be a Timeseries.

7.4.1.7. Profile Observation (ProfileObservation)

Observation representing the measurement of a property along a vertical profile in space at a single time instant.

This type is a sub-type of SamplingCoverageObservation.

featureOfInterest shall be a SF_SamplingCurve.

phenomenonTime shall be a TM_Instant.

result shall be a ReferenceableGridCoverage or a RectifiedGridCoverage.

Spatial domain of the result shall contain one axis and that shall be vertical.

7.4.1.8. Trajectory Observation (TrajectoryObservation)

Observation representing the measurement of a property along a meandering curve in time and space.

This type is a sub-type of SamplingCoverageObservation.

phenomenonTime shall be a TM_Period.

result shall be a Timeseries.

each point in the result shall be a TimeLocationValueTriple.

featureOfInterest shall be a SF_Sampling Curve.

7.4.2. Data types

7.4.2.1. Time Location Value Triple (TimeLocationValueTriple)

A triple set of Time, location, value (measurement). For example, at a point along a trajectory.

This type is a sub-type of TimeValuePair.







Attribute Definition Type Voidability location Geographic location where value is valid. GM_Position

7.5. Requirements for Observations

Where the OM_Observation type or any sub-type thereof is used to make data available, the following requirements shall apply:

(1) The Process type shall be used to indicate the procedure used in an OM_Observation.

(2) Where reference is made to an EnvironmentalMonitoringFacility from an OM_Observation, a parameter attribute shall be provided, whose name attribute is ‘relatedMonitoringFeature’ and whose value attribute is of type AbstractMonitoringFeature.

(3) For all encodings that are used for all or part of an OM_Observation result, a public Application Programming Interface (API) shall be available to read the encoded file. This API shall be capable of exposing the information needed to realise INSPIRE spatial objects.

(4) If the processParameter attribute is present in the procedure property of an OM_Observation object, its value (a name) shall be included in the parameter attribute of the OM_Observation object.

8. ACTIVITY COMPLEX MODEL

The INSPIRE activity complex model contains the package Activity Complex.

8.1. Activity Complex

8.1.1. Spatial object types

The package Activity Complex contains the spatial object type Activity Complex.

8.1.1.1. Activity Complex (ActivityComplex)

A single unit, both technically and economically, under the management control of a legal entity (operator), covering activities as those listed in the Eurostat NACE classification established by Regulation (EC) No 1893/2006 of the European Parliament and of the Council ( 6 ). Activity Complex must represent the whole area, at the same or different geographical location, managed by the same operator including all infrastructure, equipment and materials.







Attribute Definition Type Voidability inspireId External object identifier of the spatial object. Identifier thematicId Thematic identifier of the activity complex. ThematicIdentifier geometry The geometry used to define the extent or position of the activity complex. GM_Object function Activities performed by the activity complex. Function is described by the activity and potentially complemented with information about inputs and outputs as result of it. Function name Descriptive name of the activity complex. CharacterString voidable validFrom The time when the activity complex started to exist in the real world. DateTime voidable validTo The time when the activity complex no longer exists in the real world. DateTime voidable beginLifespanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable endLifespanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable

8.1.2. Data types

8.1.2.1. Function (Function)

The function of something expressed as an activity and optional input and/or output.







Attribute Definition Type Voidability activity Categorized description of individual or organized set of technically related processes that are carried out by a economical unit, private or public, profit or non profit character. EconomicActivityValue input Any classified or registered material that enters a technical and economical unit according to its function. InputOutputValue voidable output Any classified or registered material that leaves a technical and economical unit according to its function. InputOutputValue voidable description A more detailed description of the function. PT_FreeText voidable

8.1.2.2. Capacity (Capacity)

A quantification of an actual or potential ability to perform an activity, that typically does not change, does not change often, or does not change to a significant degree.







Attribute Definition Type Voidability activity Categorized description of individual or organized set of technically related processes that are carried out by a economical unit, private or public, profit or non profit character. EconomicActivityValue input Measurable information about any classified or registered material that enters a technical and economical unit according to its function. InputOutputAmount output Measurable information about any classified or registered material that leaves a technical and economical unit according to its function. InputOutputAmount time The duration of time to which the specified capacity refers, such as 1 year for an annual capacity. TM_Duration description A description of the capacity. PT_FreeText voidable

8.1.2.3. Amount Of Input Or Output (InputOutputAmount)

Type and, where available, measurable amount of a classified or registered material that enters or leaves a technical and economical unit.







Attribute Definition Type Voidability inputOutput A classified or registered material that enters or leaves a technical and economical unit according to its function. InputOutputValue amount The amount (such as a volume or mass) of the classified or registered material that enters or leaves a technical and economical unit. Measure voidable

8.1.2.4. Permission (Permission)

Official Decision (formal consent) granting authorization to operate all or part of an Activity Complex, subject to certain conditions which guarantee that the installations or parts of installations on the same site operated by the same operator comply with the requirements fixed by a competent authority. A permit may cover one or more functions and fix parameters of capacity. The term could be extended to other kind of certificates or documents of special relevance depending of the scope (e.g. ISO, EMAS, National Quality Standards, etc).







Attribute Definition Type Voidability id Identifying reference to the permission. ThematicIdentifier relatedParty Parties related to the permission granted to the activity complex open to many different roles, such as Competent Authorities or Company among others RelatedParty voidable decisionDate Temporal reference that complements the definition of the permission. DateTime voidable dateFrom A date starting from which the permission applies and is valid. DateTime voidable dateTo A date up to which the permission applies and is valid. DateTime voidable description A description of the permission. PT_FreeText voidable permittedFunction Function/s to which the permission is granted. Function voidable permittedCapacity Maximum amounts of activity input and/or output according to the permission. Capacity voidable

8.1.2.5. Activity Complex Description (ActivityComplexDescription)

Additional information about an activity complex, including its description, address, contact details and related parties.







Association role Definition Type Voidability description A complementary definition of the ‘Activity Complex’ and its characteristics. PT_FreeText voidable address An address for the activity complex, i.e., an address where the activities occur. AddressRepresentation voidable contact Contact information for the activity complex. Contact voidable relatedParty Information of Parties related to the Activity Complex. It is open to many different roles, such as owners, operators or Competent Authorities. RelatedParty voidable

8.1.3. Code lists

8.1.3.1. Economic Activity (EconomicActivityValue)

Classification of economic activities.

The allowed values for this code list comprise the values of the following code lists or other code lists specified by data providers:

— EU Economic Activity Classification (EconomicActivityNACEValue): Economic activities according to Eurostat NACE Classification values, as specified in Regulation (EC) No 1893/2006 of the European Parliament and of the Council ( 7 ).

— EU Waste Statistics Economic Activity Classification (EconomicActivityWasteStatisticsValue): Classification of economic activities according to Section 8 of Annex I of Regulation (EC) No 2150/2002 ( 8 ).

— EU Waste Recovery Disposal Classification (WasteRecoveryDisposalValue): Classification of waste recovery and disposal operations according to Annexes I and II of Directive 2008/98/EC of the European Parliament and of the Council ( 9 ).

8.1.3.2. Input Or Output (InputOutputValue)

Classification of inputs or outputs.

The allowed values for this code list comprise the values of the following code lists or other code lists specified by data providers.

— EU Product Classification (ProductCPAValue): Classification of Products by Economical Activity according to Regulation (EC) No 451/2008 of the European Parliament and of the Council ( 10 ).

— EU Waste Classification (WasteValue): Classification of Wastes according to Decision 2000/532/EC ( 11 ).

8.2. Requirements for Activity Complexes

If a data provider uses a sub-type of ActivityComplex to make available information on the status, physical capacity, permissions and/or additional information, the relevant code lists and data types (ConditionOfFacilityValue, Capacity, Permission, ActivityComplexDescription) included in the package Activity Complex shall be used.

▼B









ANNEX II

REQUIREMENTS FOR SPATIAL DATA THEMES LISTED IN ANNEX I TO DIRECTIVE 2007/2/EC

1. COORDINATE REFERENCE SYSTEMS

1.1. Definitions

In addition to the definitions set out in Article 2, the following definitions shall apply:

— ‘datum’ means a parameter or set of parameters that define the position of the origin, the scale, and the orientation of a coordinate system, in accordance with EN ISO 19111,

— ‘geodetic datum’ means a datum describing the relationship of a coordinate system to the Earth, in accordance with EN ISO 19111,

— ‘coordinate system’ means a set of mathematical rules for specifying how coordinates are to be assigned to points, in accordance with EN ISO 19111,

— ‘coordinate reference system’ means a coordinate system which is related to the real world by a datum, in accordance with EN ISO 19111. This definition includes coordinate systems based on geodetic or Cartesian coordinates and coordinate systems based on map projections.

— ‘map projection’ means a change of coordinates, based on a one-to-one relationship, from a geodetic coordinate system to a plane, based on the same datum, in accordance with EN ISO 19111,

— ‘compound coordinate reference system’ means a coordinate reference system using two other independent coordinate reference systems, one for the horizontal component and one for the vertical component, to describe a position, in accordance with EN ISO 19111,

— ‘geodetic coordinate system’ means a coordinate system in which position is specified by geodetic latitude, geodetic longitude and (in the three-dimensional case) ellipsoidal height, in accordance with EN ISO 19111,

▼M2

— ‘mean sea level’ (MSL) means the average height of the surface of the sea at a tide station for all stages of the tide over a 19-year period, usually determined from hourly height readings measured from a fixed predetermined reference level (chart datum),

— ‘lowest astronomical tide’ (LAT) means the lowest tide level which can be predicted to occur under average meteorological conditions and under any combination of astronomical conditions.

▼B

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.

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. ▼M2 — 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. ▼M2 — 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. ▼B

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 in this Annex.

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

The geodetic codes and parameters needed to describe these coordinate reference systems and to allow conversion and transformation operations shall be documented and an identifier shall be created, according to EN ISO 19111 and ISO 19127.

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.

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.

2. GEOGRAPHICAL GRID SYSTEMS

2.1. Definitions

In addition to the definitions set out in Article 2, the following definitions shall apply:

— ‘grid’ means a network composed of two or more sets of curves in which the members of each set intersect the members of the other sets in an algorithmic way,

— ‘grid cell’ means a cell delineated by grid curves,

— ‘grid point’ means a point located at the intersection of two or more curves in a grid.

2.2. Grids

▼M2

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.

▼B

2.2.1. ►M2 Equal Area Grid ◄

▼M2 —————

▼B

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 52° N, 10° E and false easting: x0 = 4 321 000 m, false northing: y0 = 3 210 000 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, 1 000 m, 10 000 m and 100 000 m.

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.

▼M2 —————

▼B

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 1 000 m 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.

▼M2

2.2.2. Zoned Geographic Grid

1. When gridded data is delivered using geodetic coordinates as specified in Section 1.3 of this Annex the multi-resolution grid defined in this Section may be used as a geo-referencing framework.

2. The resolution levels are defined in Table 1.

3. The grid shall be based on the ETRS89-GRS80 geodetic coordinate reference system.

4. The origin of the grid shall coincide with the intersection point of the Equator with the Greenwich Meridian (GRS80 latitude φ=0; GRS80 longitude λ=0).

5. The grid orientation shall be south-north and west-east according to the net defined by the meridians and parallels of the GRS80 ellipsoid.

6. For grid referencing in regions outside of continental Europe data providers may define their own grid based on a geodetic coordinate reference system compliant with ITRS, following the same principles as laid down for the Pan-European Grid_ETRS89-GRS80zn. In this case, an identifier for the coordinate reference system and the corresponding identifier for the grid shall be created.

7. This grid shall be subdivided in zones. The south-north resolution of the grid shall have equal angular spacing. The west-east resolution of the grid shall be established as the product of angular spacing multiplied by the factor of the zone as defined in Table 1.

8. The grid shall be designated Grid_ETRS89-GRS80zn_res, where n represents the number of the zone and res the cell size in angular units, as specified in Table 1.



Table 1 Common Grid_ETRS89-GRS80: Latitude spacing (resolution level) and longitude spacing for each zone Resolution Levels LATITUDE SPACING (Arc seconds) LONGITUDE SPACING (Arc seconds) Cell size Zone 1 (Lat. 0°–50°) Zone 2 (Lat. 50°–70°) Zone 3 (Lat. 70°–75°) Zone 4 (Lat. 75°–80°) Zone 5 (Lat. 80°–90°) LEVEL 0 3 600 3 600 7 200 10 800 14 400 21 600 1 D LEVEL 1 3 000 3 000 6 000 9 000 12 000 18 000 50 M LEVEL 2 1 800 1 800 3 600 5 400 7 200 10 800 30 M LEVEL 3 1 200 1 200 2 400 3 600 4 800 7 200 20 M LEVEL 4 600 600 1 200 1 800 2 400 3 600 10 M LEVEL 5 300 300 600 900 1 200 1 800 5 M LEVEL 6 120 120 240 360 480 720 2 M LEVEL 7 60 60 120 180 240 360 1 M LEVEL 8 30 30 60 90 120 180 30 S LEVEL 9 15 15 30 45 60 90 15 S LEVEL 10 5 5 10 15 20 30 5 S LEVEL 11 3 3 6 9 12 18 3 S LEVEL 12 1,5 1,5 3 4,5 6 9 1 500 MS LEVEL 13 1 1 2 3 4 6 1 000 MS LEVEL 14 0,75 0,75 1,5 2,25 3 4,5 750 MS LEVEL 15 0,5 0,5 1 1,5 2 3 500 MS LEVEL 16 0,3 0,3 0,6 0,9 1,2 1,8 300 MS LEVEL 17 0,15 0,15 0,3 0,45 0,6 0,9 150 MS LEVEL 18 0,1 0,1 0,2 0,3 0,4 0,6 100 MS LEVEL 19 0,075 0,075 0,15 0,225 0,3 0,45 75 MS LEVEL 20 0,03 0,03 0,06 0,09 0,12 0,18 30 MS LEVEL 21 0,015 0,015 0,03 0,045 0,06 0,09 15 MS LEVEL 22 0,01 0,01 0,02 0,03 0,04 0,06 10 MS LEVEL 23 0,0075 0,0075 0,015 0,0225 0,03 0,045 7 500 MMS LEVEL 24 0,003 0,003 0,006 0,009 0,012 0,018 3 000 MMS FACTOR — 1 2 3 4 6 —

▼B

3. GEOGRAPHICAL NAMES

3.1. Spatial Object Types

The following spatial object types shall be used for the exchange and classification of spatial objects from data sets that relate to the spatial data theme Geographical Names:

— Named Place

3.1.1. Named Place (NamedPlace)

Any real world entity referred to by one or several proper nouns.







Attributes of the spatial object type NamedPlace Attribute Definition Type Voidability beginLifespanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable endLifespanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable geometry Geometry associated to the named place. This data specification does not restrict the geometry types. GM_Object inspireId External object identifier of the spatial object. Identifier leastDetailedViewingResolution Resolution, expressed as the inverse of an indicative scale or a ground distance, above which the named place and its associated name(s) should no longer be displayed in a basic viewing service. MD_Resolution voidable localType Characterisation of the kind of entity designated by geographical name(s), as defined by the data provider, given in at least in one official language of the European Union. LocalisedCharacterString voidable mostDetailedViewingResolution Resolution, expressed as the inverse of an indicative scale or a ground distance, below which the named place and its associated name(s) should no longer be displayed in a basic viewing service. MD_Resolution voidable name Name of the named place. GeographicalName relatedSpatialObject Identifier of a spatial object representing the same entity but appearing in other themes of INSPIRE, if any. Identifier voidable type Characterisation of the kind of entity designated by geographical name(s). NamedPlaceTypeValue voidable

3.2. Data Types

3.2.1. Geographical Name (GeographicalName)

Proper noun applied to a real world entity.







Attributes of the data type GeographicalName Attribute Definition Type Voidability grammaticalGender Classes of nouns reflected in the behaviour of associated words. GrammaticalGenderValue voidable grammaticalNumber Grammatical category of nouns that expresses count distinctions. GrammaticalNumberValue voidable language Language of the name, given as a three letters code, in accordance with either ISO 639-3 or ISO 639-5. CharacterString voidable nameStatus Qualitative information enabling to discern which credit should be given to the name with respect to its standardisation and/or its topicality. NameStatusValue voidable nativeness Information enabling to acknowledge if the name is the one that is/was used in the area where the spatial object is situated at the instant when the name is/was in use. NativenessValue voidable pronunciation Proper, correct or standard (standard within the linguistic community concerned) pronunciation of the geographical name. PronunciationOfName voidable sourceOfName Original data source from which the geographical name is taken from and integrated in the data set providing/publishing it. For some named spatial objects it might refer again to the publishing data set if no other information is available. CharacterString voidable spelling A proper way of writing the geographical name. SpellingOfName

3.2.2. Pronunciation Of Name (PronunciationOfName)

Proper, correct or standard (standard within the linguistic community concerned) pronunciation of a name.







Attribute Definition Type Voidability pronunciationIPA Proper, correct or standard (standard within the linguistic community concerned) pronunciation of a name, expressed in International Phonetic Alphabet (IPA). CharacterString voidable pronunciationSoundLink Proper, correct or standard (standard within the linguistic community concerned) pronunciation of a name, expressed by a link to any sound file. URI voidable

At least one of the two attributes pronunciationSoundLink and pronunciationIPA shall not be void.

3.2.3. Spelling Of Name (SpellingOfName)

Proper way of writing a name.







Attributes of the data type SpellingOfName Attribute Definition Type Voidability script Set of graphic symbols (for example an alphabet) employed in writing the name, expressed using the four letters codes defined in ISO 15924, where applicable. CharacterString voidable text Way the name is written. CharacterString transliterationScheme Method used for the names conversion between different scripts. CharacterString voidable

3.3. Code Lists

3.3.1. Grammatical Gender (GrammaticalGenderValue)

The grammatical gender of a geographical name.

▼M2

The allowed values for this code list comprise only the values in the table below.

▼M1







►M2 Values for the code list ◄ GrammaticalGenderValue Value Definition common ‘Common’ grammatical gender (the merging of ‘masculine’ and ‘feminine’). feminine Feminine grammatical gender. masculine Masculine grammatical gender. neuter Neuter grammatical gender.

▼B

3.3.2. Grammatical Number (GrammaticalNumberValue)

The grammatical number of a geographical name.

▼M2

The allowed values for this code list comprise only the values in the table below.

▼M1







►M2 Values for the code list ◄ GrammaticalNumberValue Value Definition dual Dual grammatical number. plural Plural grammatical number. singular Singular grammatical number.

▼B

3.3.3. Name Status (NameStatusValue)

The status of a geographical name, that is the information enabling to discern which credit should be given to the name with respect to its standardisation and/or its topicality.

▼M2

The allowed values for this code list comprise only the values in the table below.

▼M1







►M2 Values for the code list ◄ NameStatusValue Value Definition historical Historical name not in current use. official Name in current use and officially approved or established by legislation. other Current, but not official, nor approved name. standardised Name in current use and accepted or recommended by a body assigned advisory function and/or power of decision in matters of toponymy.

▼B

3.3.4. Named Place Type (NamedPlaceTypeValue)

The type of a named place.

▼M2

The allowed values for this code list comprise only the values in the table below.

▼M1







►M2 Values for the code list ◄ NamedPlaceTypeValue Value Definition administrativeUnit Units of administration, dividing areas where Member States have and/or exercise jurisdictional rights, for local, regional and national governance, separated by administrative boundaries. building Geographical location of buildings. hydrography Hydrographic elements, including marine areas and all other water bodies and items related to them, including river basins and sub-basins. landcover Physical and biological cover of the earth's surface including artificial surfaces, agricultural areas, forests, (semi-)natural areas, wetlands. landform Geomorphologic terrain feature. other A spatial object not included in the other types of the code list. populatedPlace A place inhabited by people. protectedSite Area designated or managed within a framework of international, Community and Member States’ legislation to achieve specific conservation objectives. transportNetwork Road, rail, air, water and cable transport networks and related infrastructure. Includes links between different networks.

▼B

3.3.5. Nativeness (NativenessValue)

The nativeness of a geographical name.

▼M2

The allowed values for this code list comprise only the values in the table below.

▼M1







►M2 Values for the code list ◄ NativenessValue Value Definition endonym Name for a geographical feature in an official or well-established language occurring in that area where the feature is situated. exonym Name used in a specific language for a geographical feature situated outside the area where that language is widely spoken, and differing in form from the respective endonym(s) in the area where the geographical feature is situated.

▼B

3.4. Layers







Layer for the spatial data theme Geographical Names Layer Name Layer Title Spatial object type GN.GeographicalNames Geographical Names NamedPlace

▼M2

4. ADMINISTRATIVE UNITS

4.1. Structure of the Spatial Data Theme Administrative Units

The types specified for the spatial data theme Administrative Units are structured in the following packages:

— Administrative Units

— Maritime Units

4.2. Administrative Units

4.2.1. Spatial object types

The package Administrative Units contains the following spatial object types:

— Administrative Boundary

— Administrative Unit

— Condominium

4.2.1.1. Administrative Boundary (AdministrativeBoundary)

A line of demarcation between administrative units.







Attribute Definition Type Voidability beginLifespanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable country Two-character country code according to the Interinstitutional style guide published by the Publications Office of the European Union. CountryCode endLifespanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable geometry Geometric representation of border line. GM_Curve inspireId External object identifier of the spatial object. Identifier legalStatus Legal status of this administrative boundary. LegalStatusValue voidable nationalLevel The hierarchy levels of all adjacent administrative units this boundary is part of. AdministrativeHierarchyLevel technicalStatus The technical status of the administrative boundary. TechnicalStatusValue voidable







Association role Definition Type Voidability admUnit The administrative units separated by this administrative boundary. AdministrativeUnit voidable

4.2.1.2. Administrative Unit (AdministrativeUnit)

Unit of administration where a Member State has and/or exercises jurisdictional rights, for local, regional and national governance.







Attribute Definition Type Voidability beginLifespanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable country Two-character country code according to the Interinstitutional style guide published by the Publications Office of the European Union. CountryCode endLifespanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable geometry Geometric representation of spatial area covered by this administrative unit. GM_MultiSurface inspireId External object identifier of the spatial object. Identifier name Official national geographical name of the administrative unit, given in several languages where required. GeographicalName nationalCode Thematic identifier corresponding to the national administrative codes defined in each country. CharacterString nationalLevel Level in the national administrative hierarchy, at which the administrative unit is established. AdministrativeHierarchyLevel nationalLevelName Name of the level in the national administrative hierarchy, at which the administrative unit is established. LocalisedCharacterString voidable residenceOfAuthority Center for national or local administration. ResidenceOfAuthority voidable







Association role Definition Type Voidability administeredBy Administrative unit established at same level of national administrative hierarchy that administers this administrative unit. AdministrativeUnit voidable boundary The administrative boundaries between this administrative unit and all the units adjacent to it. AdministrativeBoundary voidable coAdminister Administrative unit established at same level of national administrative hierarchy which is co-administered by this administrative unit. AdministrativeUnit voidable condominium Condominium administered by this administrative unit. Condominium voidable lowerLevelUnit Units established at a lower level of the national administrative hierarchy which are administered by the administrative unit. AdministrativeUnit voidable upperLevelUnit Unit established at a higher level of national administrative hierarchy that this administrative unit administers AdministrativeUnit voidable

Association role condominium applies only for administrative units which nationalLevel=‘1st order’ (country level).

No unit at lowest level can associate units at lower level.

No unit at highest level can associate units at a higher level.

4.2.1.3. Condominium (Condominium)

An administrative area established independently to any national administrative division of territory and administered by two or more countries.







Attribute Definition Type Voidability beginLifespanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable endLifespanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable geometry Geometric representation of spatial area covered by this condominium GM_MultiSurface inspireId External object identifier of the spatial object. Identifier name Official geographical name of this condominium, given in several languages where required. GeographicalName voidable







Association role Definition Type Voidability admUnit The administrative unit administering the condominium AdministrativeUnit voidable

4.2.2. Data Types

4.2.2.1. Residence Of Authority (ResidenceOfAuthority)

Data type representing the name and position of a residence of authority.







Attribute Definition Type Voidability geometry Position of the residence of authority. GM_Point voidable name Name of the residence of authority. GeographicalName

4.2.3. Enumerations

4.2.3.1. Legal Status (LegalStatusValue)

Description of the legal status of administrative boundaries.







Value Definition agreed The edge-matched boundary has been agreed between neighbouring administrative units and is stable now. notAgreed The edge-matched boundary has not yet been agreed between neighbouring administrative units and could be changed.

4.2.3.2. Technical Status (TechnicalStatusValue)

Description of the technical status of administrative boundaries.







Value Definition edgeMatched The boundaries of neighbouring administrative units have the same set of coordinates. notEdgeMatched The boundaries of neighbouring administrative units do not have the same set of coordinates.

4.2.4. Code Lists

4.2.4.1. Administrative Hierarchy Level (AdministrativeHierarchyLevel)

Levels of administration in the national administrative hierarchy. This code list reflects the level in the hierarchical pyramid of the administrative structures, which is based on geometric aggregation of territories and does not necessarily describe the subordination between the related administrative authorities.

This code list shall be managed in a common code list register.

4.3. Maritime Units

4.3.1. Spatial object types

The package Maritime Units contains the following spatial object types:

— Baseline

— Maritime Boundary

— Maritime Zone

4.3.1.1. Baseline (Baseline)

The line from which the outer limits of the territorial sea and certain other outer limits are measured.







Attribute Definition Type Voidability inspireId External object identifier of the spatial object. Identifier beginLifespanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable endLifespanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable







Association role Definition Type Voidability segment Segment of a baseline. BaselineSegment

4.3.1.2. Maritime Boundary (MaritimeBoundary)

A line depicting the separation of any type of maritime jurisdiction.







Attribute Definition Type Voidability inspireId External object identifier of the spatial object. Identifier geometry Geometric representation of the maritime boundary. GM_Curve country The country that the maritime zone of this boundary belongs to. CountryCode legalStatus Legal status of this maritime boundary. LegalStatusValue voidable technicalStatus The technical status of the maritime boundary. TechnicalStatusValue voidable beginLifespanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable endLifespanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable

4.3.1.3. Maritime Zone (MaritimeZone)

A belt of sea defined by international treaties and conventions, where coastal State executes jurisdictional rights.







Attribute Definition Type Voidability inspireId External object identifier of the spatial object. Identifier geometry Geometric representation of spatial area covered by this maritime zone. GM_MultiSurface zoneType Type of maritime zone. MaritimeZoneTypeValue country The country that this maritime zone belongs to. CountryCode name Name(s) of the maritime zone. GeographicalName voidable beginLifeSpanVersion Date and time at which this version of the spatial object was inserted or changed in the spatial data set. DateTime voidable endLifepanVersion Date and time at which this version of the spatial object was superseded or retired in the spatial data set. DateTime voidable







Association role Definition Type Voidability baseline Baseline or baselines used for the delineation of this maritime zone. Baseline voidable boundary The boundary or boundaries of this maritime zone. MaritimeBoundary voidable

4.3.2. Data types

4.3.2.1. Baseline Segment (BaselineSegment)

Segment of the baseline from which the outer limits of the territorial sea and certain other outer limits are measured.







Attribute Definition Type Voidability geometry Geometric representation of the baseline segment. GM_Curve segmentType The baseline type used for this segment. BaselineSegmentTypeValue

4.3.3. Code lists

4.3.3.1. Baseline Segment Type (BaselineSegmentTypeValue)

The types of baselines used to measure the breadth of the territorial sea.

The allowed values for this code list comprise only the values specified in the table below.







Value Name Definition normal normal The normal baseline for measuring the breadth of the territorial sea is the low-water line along the coast as marked on large-scale charts officially recognized by the coastal State. straight straight The baseline for measuring the breadth of the territorial sea is the straight baseline established by joining the appropriate points. archipelagic archipelagic The baseline for measuring the breadth of the territorial sea is the straight baseline joining the outermost points of the outermost islands and drying reefs of the archipelago.

4.3.3.2. Maritime Zone Type (MaritimeZoneTypeValue)

Type of martime zone.

The allowed values for this code list comprise only the values specified in the table below.







Value Name Definition internalWaters Internal Waters The waters on the landward side of the baselines of the territorial sea of the coastal State. territorialSea Territorial Sea A belt of sea of a defined breadth not exceeding 12 nautical miles measured from the baselines determined in accordance to the United Nations Convention of Law on the Sea. contiguousZone Contiguous Zone A zone contiguous to a territorial sea of a coastal State, which may not extend beyond 24 nautical miles from the baselines from which the breadth of the territorial sea is measured. exclusiveEconomicZone Exclusive Economic Zone An area beyond and adjacent to the territorial sea of a coastal State, subject to the specific legal regime under which the rights and jurisdiction of the coastal State and the rights and freedoms of other States are governed by the relevant provisions of the United Nations Convention on Law of the Sea. continentalShelf Continental Shelf A maritime zone beyond and adjacent to the a territorial sea of a coastal State whose outer boundary is determined in accordance with Article 76 of the United Nations Convention on the Law of the Sea.

4.4. Theme-specific Requirements

1. Each instance of spatial object type AdministrativeUnit, except for the country level unit representing a Member State and co-administered units, shall refer exactly to one unit at a higher level of administrative hierarchy. This correspondence shall be expressed by the upperLevelUnit association role of AdministrativeUnit spatial object type.

2. Each instance of spatial object type AdministrativeUnit, except for those at the lowest level, shall refer to their respective lower level units. This correspondence shall be expressed by the lowerLevelUnit association role of AdministrativeUnit spatial object type.

3. If an administrative unit is co-administered by two or more other administrative units the association role administeredBy shall be used. The units co-administering this unit shall apply inverse role coAdminister.

4. Administrative units at the same level of administrative hierarchy shall not conceptually share common areas.

5. Instances of the spatial object type AdministrativeBoundary shall correspond to the edges in the topological structure of the complete (including all levels) boundary graph.

6. The spatial extent of a condominium may not be part of the geometry representing the spatial extent of an administrative unit.

7. Condominiums can only be administered by administrative units at country level.

4.5. Layers

Layers for the spatial data theme Administrative Units







Layer Name Layer Title Spatial object type AU.AdministrativeUnit Administrative unit AdministrativeUnit AU.AdministrativeBoundary Administrative boundary AdministrativeBoundary AU.Condominium Condominium Condominium AU.Baseline Baseline Baseline AU.<CodeListValue> (1) Example: AU.ContiguousZone <human readable name> Example: Contiguous Zone MaritimeZone (zoneType: MaritimeZoneTypeValue) AU.MaritimeBoundary Maritime boundary MaritimeBoundary (1) One layer shall be made available for each code list value, in accordance