Question (NPOC)
When is a data set to be considered "compliant"?
Answer (EC Inspire Team)
A data set is to be considered "compliant" if it meets all the requirements set out in the Implementing Rules on interoperability of spatial data sets and services (1) and its amendment on code lists (2), including the following:
- The spatial object types specified for the spatial data theme(s) a data set relates to shall be used for the exchange and classification of spatial objects from that data set. Note that this does not mean that all of the specified spatial object types have to be included.
- Those spatial object types and data types that are used to make the data sets available shall comply with the definitions and constraints and include the attributes and association roles set out in Annex II of the Implementing Rules. Note that this includes all voidable attributes and association roles; these may, however, have the value "void". If, for a voidable attribute, a data set contains values or corresponding values can be derived from existing values at reasonable costs, these values have to be made available.
- Requirements on code lists and enumerations (article 6 and code list amendment (2))
- Requirements on metadata required for interoperability (see article 13)
- Requirements on portrayal (see article 14)
- Requirements on reference systems (see article 11 and Annex II, point 1)
- Requirements on encoding (see article 7)
- Other requirement (see articles 9, 10, 12 and theme-specific requirements in Annex II)
(1) Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
(2) Commission Regulation (EU) No 102/2011 of 4 February 2011 amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services