Implementation guidance and support
The Spatial scope code list aims to support the new Commission Implementing Decision replacing Commission Decision No 2009/442/EC of 5 June 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards monitoring and reporting (The final draft for the new reporting decision was supported by the MIG during 9th MIG expert group meeting 26-27 November 2018 in Brussels). In particular it aims to support new monitoring indicators related to the distribution of spatial data sets with regional and national coverage (DSi1,4 and DSi1,5). The following indicators shall be used to measure the number of the spatial data sets that respectively cover regional or national territory:
(a) the number of spatial data sets for which the metadata contains a keyword from a register provided by the Commission indicating that the spatial data set covers regional territory ("DSi1,4");
(b) the number of spatial data sets for which the metadata contains a keyword from a register provided by the Commission indicating that the spatial data set covers the national territory ("DSi1,5").
Member States are required to tag selected spatial data sets that respectively identify those spatial data sets that have regional or national coverage for the given theme or spatial object type(s). Depending on the constitutional setup in the Member State and the distribution of competences, we identified the following three main scenarios for tagging with regional/national keywords:
- Nationally organised data set (produced by a national administration) are available. These are tagged with the “national” keyword.
- Only regional data sets are available, but no national data set. For every region, the regional data set is tagged with the “regional” keyword.
- Both a nationally organised data set and regional data sets are available with the same level of detail. A Member State has regional data sets that are authoritative but also creates a national data set. The national data set is tagged with the “national” keyword, the regional data sets are tagged with the "regional" keyword.
Tagging of data sets
Tagging of data sets follows the similar approach as the Tagging of priority data sets
Spatial scope code list is implemented in INSPIRE metadata code list register
Definition: Administrative level that the data set intends to cover
Description: The spatial scope can be different from the actual geographical coverage, e.g. a national coastline data set may cover only a fraction of the full spatial extent of a country. The spatial scope of the data set does not necessarily reflect the administrative level responsible for collecting and maintaining the data, e.g. the responsibility for maintaining the data inside the national address data set can be at regional or local level.
The code list contains values governed at the level of INSPIRE legal acts (governance level: Legal (EU)) and values governed at the level of INSPIRE Technical Guidelines (governance level: Technical (EU)). The former directly support the INSPIRE Monitoring and Reporting Decision (values: National and Regional), while the latter provide additional options for tagging other data sets (values: Local, European and Global).
Simplified workflow for “tagging” of data sets
To tag a data set as "national" or "regional" (or, optionally, one of the other values included in the code list, e.g. "local" or "global") in the INSPIRE metadata.
- Identify your data set metadata in the national metadata catalogue (INSPIRE Discovery service)
- Add a descriptive keyword related to the data set in the INSPIRE metadata:
- Select the relevant value from to the Spatial scope controlled vocabulary in the INSPIRE Registry (http://inspire.ec.europa.eu/metadata-codelist/SpatialScope)
- Add the selected value to the keywords section in the metadata of your data set metadata using one of the two encoding options given below.
- Add the citation information for the used controlled vocabluary. For the citation, the following information shall be used:
- URI of the Code list: http://inspire.ec.europa.eu/metadata-codelist/SpatialScope (only for encoding 1)
- Date type: publication
- Date: 2019-05-22
- Title of the vocabulary: Spatial scope
Here are the two supported options of encoding of selected keyword(s) and the used controlled vocabulary:
Option 1: Using the gmx:Anchor element
<gmd:descriptiveKeywords> <gmd:MD_Keywords> <gmd:keyword> <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/SpatialScope/national">National</gmx:Anchor> </gmd:keyword> <gmd:thesaurusName> <gmd:CI_Citation> <gmd:title> <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/SpatialScope">Spatial scope</gmx:Anchor> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2019-05-22</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:thesaurusName> </gmd:MD_Keywords> </gmd:descriptiveKeywords>
Option 2: Using the gco:CharacterString element
<gmd:descriptiveKeywords> <gmd:MD_Keywords> <gmd:keyword> <gco:CharacterString>National</gco:CharacterString> </gmd:keyword> <gmd:thesaurusName> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>Spatial scope</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2019-05-22</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:thesaurusName> </gmd:MD_Keywords> </gmd:descriptiveKeywords>
Note: JRC is currently investigating the possibility to provide tool support for the process of tagging data sets following this approach, e.g. using the GeoNetwork.
Should you have any query or doubt about how to “tag” data sets using the INSPIRE Registry controlled vocabulary, please let us know by using the INSPIRE Geoportal Helpdesk issue-tracker system (NOTE: you can view any communication there, but if you want to raise an issue, you have to register using the EU Login (ECAS) authentication).