Code Lists and Enumerations
Article 1
Regulation (EU) No 1089/2010 is amended as follows: (1) Article 2 is amended as follows: (a) the introductory sentence is replaced by the following: ‘For the purposes of this Regulation, the following definitions as well as the theme-specific definitions set out in the Annexes shall apply:’ (b) point 4 is deleted; (c) in point 6, ‘ISO 19103’ is replaced by ‘ISO/TS 19103:2005’; (d) in point 9, ‘EN ISO 19135’ is replaced by ‘EN ISO 19135:2007’; (e) in point 11, ‘EN ISO 19128’ is replaced by ‘EN ISO 19128:2008’; (f) in point 13, ‘EN ISO 19115’ is replaced by ‘EN ISO 19115:2005/AC:2008’; (g) in point 15, ‘EN ISO 19135’ is replaced by ‘EN ISO 19135:2007’; (h) in point 18, ‘ISO 19103’ is replaced by ‘ISO/TS 19103:2005’; (i) the following points 21 to 30 are added: ‘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.’ (2) Article 4 is amended as follows: (a) Paragraph 1 is replaced by: ‘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) All references to ‘Annex II’ in points 2 and 3 are replaced by references to ‘the Annexes’. (c) In paragraph 3, the second sentence is replaced by the following: ‘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.’ (3) In Article 5, paragraph 4 is deleted. (4) Article 6 is replaced by the following: ‘Article 6 Code Lists and Enumerations 1. Code lists shall be of one of the following types, as specified in the Annexes: (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.’ (5) In paragraph 2 of Article 8 and in paragraph 1 of Article 11, the references to ‘Annex II’ are replaced by references to ‘the Annexes’. (6) Article 12 is amended as follows: (a) Paragraph 1 is replaced by the following: ‘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) Paragraph 2 is amended as follows: ‘SI units’ is replaced by ‘SI units or non-SI units accepted for use with the International System of Units’. (7) In Article 13, the following point 6 is added: ‘6. Spatial Representation Type: The method used to spatially represent geographic information.’ (8) Article 14 is amended as follows: (a) Paragraph 2 (b) is replaced by the following: ‘(b) the spatial object type(s), or sub-set thereof, that constitute(s) the content of the layer.’ (b) The following paragraph 3 is added: ‘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.’ (9) Annex I is amended as set out in Annex I to this Regulation. (10) Annex II is amended as set out in Annex II to this Regulation. (11) Annex III, as set out in Annex III to this Regulation, is added. (12) Annex IV, as set out in Annex IV to this Regulation, is added.