Article 1F1Subject 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 F8Annexes 1, 2 and 3 to Commission Regulation (EC) No. 1205/2008.

2

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

Article 2Definitions

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

  1. 1.

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

  2. 2.

    ‘association role’ means a value or object, to which a type has a relationship F10between spatial objects,

  3. 3.

    ‘attribute’ means a characteristic F11which may have an impact on the environment,

  4. 4.

    F3...

  5. 5.

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

  6. 6.

    ‘data type’ means a descriptor of a set of values that lack identity, in accordance with F2ISO/TS 19103:2005,

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

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

  10. 10.

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

  11. 11.

    ‘layer’ means a basic unit of geographic information that may be requested as a map from a server in accordance with F2EN ISO 19128:2008,

  12. 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. 13.

    ‘metadata element’ means a discrete unit of metadata, in accordance with F2EN ISO 19115:2005/AC:2008,

  14. 14.

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

  15. 15.

    ‘register’ means a set of files containing identifiers assigned to items with descriptions of the associated items, in accordance with F2EN ISO 19135:2007,

  16. 16.

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

  17. 17.

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

  18. 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 F2ISO/TS 19103:2005,

  19. 19.

    ‘type’ means spatial object type or data type,

  20. 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 F12appropriate authority 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 blankF2,

  21. 21.

    F4‘property’ means attribute or association role,

  22. 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. 23.

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

  24. 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. 25.

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

  26. 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. 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. 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. 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. 30.

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

  31. 31.

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

  32. 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. 33.

    ‘Invocable spatial data service’ means all of the following:

    1. (a)

      a spatial data service with metadata which fulfils the requirements of Commission Regulation (EC) No 1205/20083,

    2. (b)

      a spatial data service with at least one resource locator that is an access point,

    3. (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. 34.

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

  35. 35.

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

  36. 36.

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

  37. 37.

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

  38. 38.

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

  39. 39.

    F9appropriate authority” means—

    1. (a)

      in relation to England and Wales and Northern Ireland, the Secretary of State;

    2. (b)

      in relation to Scotland, the Scottish Ministers;

  40. 40.

    any reference to a protected site designated under, or in relation to, Natura 2000 is to be read as a reference to a site which formed part of the Natura 2000 network immediately before exit day or which forms part of any similar or equivalent network under the legislation of any part of the United Kingdom after exit day.

Article 3Common Types

Types that are common to several of the themes listed in F13Annexes 1, 2 and 3 to Commission Regulation (EC) No 1205/2008 shall conform to the definitions and constraints and include the attributes and association roles set out in Annex I.

Article 4Types for the Exchange and Classification of Spatial Objects

F21

For the exchange and classification of spatial objects from data sets F14falling within regulation 4 of the INSPIRE Regulations 2009 or, as the case may be, regulation 5 of the INSPIRE (Scotland) Regulations 2009, public authorities 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.

2

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

F63

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 F2the Annexes. F2The 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.

F74

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Article 5Types

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.

F34

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Article 6F2F1Code Lists and Enumerations for Spatial Data Sets

1

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

Article 7Encoding

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 8Updates

1

F15The appropriate authority 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 F2the Annexes.

F53

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

Article 9Identifier 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 10Life-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 11Temporal Reference Systems

1

The default temporal reference system referred to in point 5 of part B of F16Annex 4 to Commission Regulation (EC) No 1205/20084 shall be used, unless other temporal reference systems are specified for a specific spatial data theme in F2the Annexes.

2

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

Article 12Other Requirements & Rules

F21

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.

2

All measurement values shall be expressed using F2SI 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 13Metadata 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.

F46.Spatial Representation Type

The method used to spatially represent geographic information.

Article 14Portrayal

1

For the portrayal of spatial data sets using a view network service as specified in Commission Regulation No 976/20095, 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;

F2b

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

F43

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.

F17Article 14aRequirements for invocable spatial data services

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Article 14bF5Interoperability 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.

F18Article 15Entry into force

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

F19...