Nařízení Komise (EU) č. 1089/2010 ze dne 23. listopadu 2010, kterým se provádí směrnice Evropského parlamentu a Rady 2007/2/ES, pokud jde o interoperabilitu sad prostorových dat a služeb prostorových dat

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)OJ L 108, 25.4.2007, p. 1 . , and in particular Article 7(1) thereof,

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.

OJ L 108, 25.4.2007, p. 1 .

(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,

For the purpose of this Regulation, the following definitions as well as the theme-specific definitions set out in Annex II shall apply:

OJ L 326, 4.12.2008, p. 12 .

Article 1 Article 1 Subject Matter

Article 2 Article 2 Definitions

Article 3 Article 3 Common Types

Article 4 Article 4 Types for the Exchange and Classification of Spatial Objects 1.Member States shall use the spatial object types and associated data types, enumerations and code lists defined in Annex II for the exchange and classification of spatial objects from data sets meeting the conditions laid down in Article 4 of Directive 2007/2/EC. 2.Spatial object types and data types shall comply with the definitions and constraints and include the attributes and association roles set out in Annex II. 3.The enumerations 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 Annex II. The enumeration values are language-neutral mnemonic codes for computers. 4.The code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions set out in Annex II.

Article 5 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. 4.Candidate types shall be considered during the development of requirements for the spatial data theme they thematically belong to. During this development, the only allowed change to the specification of the candidate type is to extend it.

Article 6 Article 6 Code Lists and Enumerations 1.Code lists shall be of one of the following types, as specified in Annex II: (a) code lists that are managed in a common code list register and that shall not be extended by Member States;(b) code lists that may be extended by Member States. 2.Where a Member State extends a code list, the allowed values of the extended code lists shall be made available in a register. 3.Attributes or association roles of spatial object types or data types that have a code list type may only take values that are valid according to the register in which the code list is managed. 4.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.

Article 7 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 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 Annex II.

Article 9 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.

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

Article 10 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 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/2008OJ L 326, 4.12.2008, p. 12 . shall be used, unless other temporal reference systems are specified for a specific spatial data theme in Annex II. 2.If other temporal reference systems are used, these shall be specified in the data set metadata.

Article 12 Article 12 Other Requirements & Rules 1.The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined by EN ISO 19125-1, unless specified otherwise for a specific spatial data theme or type. 2.All measurement values shall be expressed using SI 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 Article 13 Metadata required for Interoperability

Article 14 Article 14 Portrayal 1.For the portrayal of spatial data sets using a view network service as specified in Commission Regulation No 976/2009OJ L 274, 20.10.2009, p. 9 . , 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;(b) the spatial object type(s) that constitute the content of the layer.

Article 15 Article 15 Entry into force

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,

4. candidate type means a type which is already used as part of the specification of a spatial data theme in Annex I of Directive 2007/2/EC, but which will be fully specified in the spatial data theme in Annex II or III of Directive 2007/2/EC where it thematically belongs,

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 ISO 19103,

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 EN ISO 19135,

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

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.

OJ L 274, 20.10.2009, p. 9 .

11. layer means a basic unit of geographic information that may be requested as a map from a server in accordance with EN ISO 19128,

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 EN ISO 19115,

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 EN ISO 19135,

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 ISO 19103,

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.

Member States shall use the spatial object types and associated data types, enumerations and code lists defined in Annex II for the exchange and classification of spatial objects from data sets meeting the conditions laid down in Article 4 of Directive 2007/2/EC.

Spatial object types and data types shall comply with the definitions and constraints and include the attributes and association roles set out in Annex II.

The enumerations 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 Annex II. The enumeration values are language-neutral mnemonic codes for computers.

The code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions set out in Annex II.

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.

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

Abstract types shall not be instantiated.

Candidate types shall be considered during the development of requirements for the spatial data theme they thematically belong to. During this development, the only allowed change to the specification of the candidate type is to extend it.

Code lists shall be of one of the following types, as specified in Annex II:

(a) code lists that are managed in a common code list register and that shall not be extended by Member States;

(b) code lists that may be extended by Member States.

Where a Member State extends a code list, the allowed values of the extended code lists shall be made available in a register.

Attributes or association roles of spatial object types or data types that have a code list type may only take values that are valid according to the register in which the code list is managed.

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.

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.

Every encoding rule used to encode spatial data shall be made available.

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

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 Annex II.

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.

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

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

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

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

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

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

The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined by EN ISO 19125-1, unless specified otherwise for a specific spatial data theme or type.

All measurement values shall be expressed using SI units, unless specified otherwise for a specific spatial data theme or type.

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

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

The metadata describing a spatial data set shall include the following metadata elements required for interoperability: 1.Coordinate Reference SystemDescription of the coordinate reference system(s) used in the data set.2.Temporal Reference SystemDescription 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.EncodingDescription of the computer language construct(s) specifying the representation of data objects in a record, file, message, storage device or transmission channel.4.Topological ConsistencyCorrectness 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 EncodingThe character encoding used in the data set. This element is mandatory only if an encoding is used that is not based on UTF-8.

For the portrayal of spatial data sets using a view network service as specified in Commission Regulation No 976/2009OJ L 274, 20.10.2009, p. 9 . , 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.

For each layer, Annex II defines the following:

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

(b) the spatial object type(s) that constitute the content of the layer.

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 .

HAS ADOPTED THIS REGULATION: