Implementation guidance and support¶
General information ¶
As one of the follow-up actions to improve and target implementation of the INSPIRE Directive after the REFIT evaluation, the Commission selected reporting and monitoring under the environmental acquis as one (but not the only) important priority use case for the development of pan-European information products. Accordingly, and based on the Fitness Check evaluation of reporting obligations under the environmental legislation, a preliminary list of common datasets related to environmental reporting obligations has been prepared by the European Commission (DG ENV and DG JRC) and the EEA.
This list of environmental datasets is a rolling list now focused on environmental geospatial datasets, which will be further extended in view of tangible information needs. In particular, it could be widened to cover other EU or global spatial data priorities (e.g. Core Data defined under UN GGIM: Europe) or include other domains (e.g. transport, agriculture, energy) which are of relevance for environment policy as well. This would improve coherence and re-use of data as well as introduce a more domain-holistic approach to streamlining these information streams which can reduce the reporting burden and will also induce better integrated public eGovernment services.
Current status of the list¶
The list of priority data has been reviewed and further developed by the 2016.5 subgroup to provide clarifications and better guidance on both identification and metadata tagging of listed data in support of its implementation. Version 2.0 of the list is considered to be the stable reference version for implementation and replaces the one in the Annex II of the letter the European Commission send to the INSPIRE NCP’s on 21/12/2017. To avoid loss of work for ongoing implementations on the previous version of the list, the subgroup has guaranteed backwards compatibility with the previous released version of the list. The stable reference version of the priority list is available on this MIG 2016.5 collaboration wiki and the reference list of metadata keywords for tagging the data sets has been documented in the INSPIRE Registry (http://inspire.ec.europa.eu/metadata-codelist/PriorityDataset).
We are pleased to work closely with you towards a succesful implementation. For specific questions (e.g. on the list, metadata tagging, thematic viewer …) or further implementation guidance please use the issue tracker to contact the geoportal helpdesk.
Tagging of priority datasets for INSPIRE Thematic Viewer¶
Recently, the JRC has made available a "beta" version of the INSPIRE Thematic Viewer application.
The application represents a new direction of simplifying the monitoring of the availability and the use of the INSPIRE Geoportal – the single point of access to Member States’ data and services. The primary objective of the application (Figure 1) is to provide a tool to monitor the provision and use of priority datasets for e-Reporting. This application has been developed in full synergy with the work on the list of priority datasets under MIWP action 2016.5.
Figure 1: INSPIRE Thematic Viewer – Priority datasets application
Based on the agreement in the MIG sub-group 2016.5 and the MIG meeting on 7-8 December 2017, the system for finding, filtering and making available the priority datasets was modified to be fully based on a newly created controlled vocabulary ("INSPIRE priority data set" in INSPIRE Registry) for the list of Priority data set. Using this list of controlled values as keywords inside the obligatory Keyword INSPIRE metadata element to identify the relevant MS dataset is the easiest way to make sure that the “tagged” datasets are:
- the correct ones, i.e. those and only those identified by Member States (data providers) and
- can easily be selected by the Thematic Viewer – Priority dataset application (using standard INSPIRE metadata).
Note: The former version - used for feasibility testing - of selecting the Priority datasets related to “Nature & Biodiversity” by using specific text and spatial search methods is still available other that cluster. Despite the relatively high number of datasets found, the results should there should be seen as an indication only.
Simplified workflow for “tagging” of priority datasets¶
- Identify your priority dataset
- Check if the INSPIRE metadata for the dataset is already available via the national metadata catalogue (INSPIRE Discovery service).
- Add a descriptive keyword related to the Priority Dataset in the INSPIRE metadata:
- Select the relevant value from to the Priority Dataset controlled vocabulary in the INSPIRE Registry (http://inspire.ec.europa.eu/metadata-codelist/PriorityDataset)
- Add the selected value to the keywords section in the metadata of your priority dataset 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/PriorityDataset (only for encoding 1)
- Date type: publication
- Date: 2018-04-04
- Title of the vocabulary: INSPIRE priority data set
Here are the two supported options of encoding of selected keyword(s) and the used controlled vocabluary:
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/PriorityDataset/Agglomerations-dir-2002-49" >Agglomerations (Noise Directive)</gmx:Anchor> </gmd:keyword> <gmd:thesaurusName> <gmd:CI_Citation> <gmd:title> <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/PriorityDataset" >INSPIRE priority data set</gmx:Anchor> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2018-04-04</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>Agglomeration (Noise Directive)</gco:CharacterString> </gmd:keyword> <gmd:thesaurusName> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>INSPIRE priority data set</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2018-04-04</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 priority datasets following this approach, e.g. using the Geoportal metadata editor or GeoNetwork.
Should you have any query or doubt about how to “tag” priority datasets using the INSPIRE Registry controlled vocabulary, please let us know by using:
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.
The JRC Geoportal Team will be pleased to cooperate with you in order to make this task as easy as possible and at the same time make the INSPIRE implementation success.
3. Translation of labels in the INSPIRE Registry
Should you like to provide translations to the labels in the PDF list, a template fcan be found here (PriorityDataset_TemplateForTranslation_UpdatedV2.xlsx). Please be in touch with the JRC Geoportal Team on this.
 COM(2017)312 and SWD(2017)230