Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Agenda itemNotes / Actions
Welcome and approval of the agenda The agenda was approved without modifications.
Minutes of the previous meetingThe minutes of the previous meeting were approved without change proposals.

INSPIRE 'Monitoring and Reporting' 2020

  • Process
  • Sneak preview of the final results
  • Preparation for M&R 2021
  • Q&A
  • The results of the annual Monitoring and Reporting exercise for 2020 were presented.
  • The preparation process was streamlined and implemented efficiently, with clear communication between the EC and MS, transparent release plans for the software used (Geoportal and Validator) and clear time windows where testing and reporting bugs was possible.
  • The JRC introduced a new way to visualise the Monitoring indicators, through: i) a star-based scoring system, in order to better focus on the overall performance instead of the exact indicator values; and ii) a direct comparison of results with those from 2019, in order not to restrict the focus to the 2020 performance.
  • In general, the situation with the availability, conformity and accessibility of INSPIRE data has improved compared to 2019. Still, significant implementation gaps exist, and the results clearly show substantial differences between individual MS.
  • DE raised the question on how to self-calculate the indicators on the conformity of metadata; the JRC suggests to deploy a local instance of the INSPIRE Reference Validator and use the bulk validation tool to automate validation.
  • NL reiterated the outstanding issue, about exposing 'as is' and 'harmonised' datasets through metadata and the impact that this has on the M&R results. The issue should be investigated and a pragmatic solution found within the context of the new INSPIRE Work Programme, and in particular the newly proposed envisioned subgroup dedicated to the development of a common simplification approach for data-service linking.
  • PL raised the concern that the values of the indicators on metadata conformity might be affected by a bug in the validator. The JRC is investigating the reasons of the validation errors, discussion to continue in the dedicated helpdesk issue.

Status update on Good Practices

  • Recap on rules
  • Status and next steps for Good Practices
    • Endorsement by the MIG
    • Validation
  • GeoPackage as INSPIRE encoding
  • The JRC provided in a synthetic manner an overview of the updated procedure for submission and endorsement of Good Practices, which now also includes an additional step (Legal scrutiny). In addition, an overview of the status of the different GP was included, as defined within the INSPIRE Knowledge Base (incl. the information on the formal endorsement by the 12th MIG meeting of SDMX, OGC API - Features and OGC SensorThings API).
  • The established GeoPackage working group summarised the findings on the use of GeoPackage as INSPIRE encoding. In accordance with the investigation of the group, multiple approaches are possible for the different data models (and MS), so an approach based on database views might provide a feasible approach for harmonising the way in which data is represented while preserving the source encoding in GeoPackage. More investigation on the topic is needed. Interested experts can join the discussion on the group's Github space.

Updates on central INSPIRE components

  • Geoportal
    • Mainstreaming backend infrastructure
  • Validator
  • Single Helpdesk
  • Re3gistry
    • Deployment of ver. 2 for INSPIRE
    • Codelists for IACS data sharing
  • Redirect from http to https - feedback


  • The JRC introduced the plan to improve the INSPIRE Geoportal backend infrastructure in the context of the sustainability of INSPIRE core infrastructure components.
    • migration to a cloud environment, backend based on GeoNetwork.
    • integration of the functionalities provided by GeoNetwork to support all the features required by INSPIRE (e.g. linkage checking)​.
    • harvesting dashboard (GeoNetwork based) protected with EU Login​.
    • implementing a micro-service based harvesting system.
    • configurable harvesting options (e.g. OGC filters)​.
    • integrating the linkage simplification approach to be agreed with MS​.
  • A call for tender to migrate the Geoportal backend infrastructure was launched. The announcement can be accessed here; the actual call is only accessible to tenderers who pre-registered and those who were directly invited to submit an offer.
  • The INSPIRE Geoportal helpdesk was migrated to the new GitHub organisation.


  • A new version of the Validator (v. 2021.0) was released on January 18, which includes non-breaking changes and also breaking changes occurred after the June 2020 release.
  • Development of ATS/ETS for Annex II/III data themes is progressing; the updated situation is available here. New ATS/ETS for OGC API - Features are in the pipeline.
  • The helpdesk of the INSPIRE Reference Validator was migrated to the new GitHub organisation.
  • Final developments for the User Interface of the INSPIRE Reference Validator after the feedback received by the community are undergoing.

Single Helpdesk


  • Registry 2 software was presented
    • Overview of the new version of the Re3gistry 2 software, released in summer 2020 on GitHub.
    • Presented the plan for the next activities:
      • publish the new INSPIRE registry service based on the Re3gistry 2.
      • release the improvements and bugfix on the Re3gistry 2 (e.g. new data formats, also requested on GitHub).
    • The INSPIRE registry helpdesk was migrated to the new GitHub organisation and is now available here.
    • Proposal for new code list(s) to support IACS data sharing will be submitted to the INSPIRE Registry control body

Redirect from http to https

  • The JRC reminds that the exception (schemas still reachable through http requests) will be kept in place until the end of February 2021. Starting from March 1, https-https redirection will be the default. Member States shall make sure (including through interaction with their solution providers) that their resources will still be reachable after the end of February.

Debriefing, ICF Workshop

The ICF workshop was held on 11 December 2020 with more than 150 participants. The workshop was co-organised by the ICF facilitators, JRC and ENV.  Presentations and audio recordings are available here.

Final facilitators reports (December 2020) are also available on Wiki.

Allowed CRS in INSPIRE

  • Horizontal and vertical CRS used in DK were presented. The horizontal CRS is aligned with INSPIRE provisions. Orientation of axes is allowed and only conversion should be done is needed. Vertical CRS needs transformation to EVRS for which parameters should be published.
  • The ongoing IR amendment envisages the establishment of a CRS registry in INSPIRE, which in the future will help manage similar issues.

Overview of the GO-PEG CEF project

 The GO-PEG CEF Project was presented with achievements so far and future planning. MS are encouraged to engage in the harmonisation and data sharing activities implemented by the project. The JRC is in the Advisory Board of the project.

New Work Programme (2020 - 2024) and MS involvement

  • Action 1.1. Towards a digital ecosystem for the environment and sustainability
  • Action 2.1. Need-driven data prioritisation
  • Action 2.2. Roadmap for priority-driven implementation
  • Action 2.3. Simplification of INSPIRE implementation
  • Action 2.4. Central infrastructure components
  • Action 3.1. GreenData4All initiative
  • Action 1.1
    • A JRC science for policy report on the vision for the future of the technologies under INSPIRE is being prepared. In addition, lessons learned from the study of the ASTEROID project on data ecosystems (implemented for the JRC by the Luxembourg Institute for Science and Technology) will be released shortly.
  •  A workshop on the possible role of the GAIA-X initiative for modernising data sharing in INSPIRE is to be organised in Q1 of 2021.
  • Action 2.1
    • The purpose of this action is to drive INSPIRE implementation based on a real demand and tangible use cases, but also on the new political agenda and other European initiatives. A subgroup will be created as a follow-up of the former subgroup 2016.5. A new helpdesk focused on priority datasets might be added.
  • Action 2.2
    • This action builds on the previous one and defines maturity levels in addition to implementation levels. A new subgroup will be created to help with this action, which already started in the previous MIWP.
  • Action 2.3 envisages the establishment of two new subgroups:
    • a subgroup to support the action on change management of INSPIRE artefacts (TG, UML models, XML application schemas) which will have duration for the hole period of the MIWP (until 2024). INSPIRE helpdesk facilitators will be part of this subgroup (see below).
    • a subgroup to develop a common simplification approach for data-service linking and update the existing metadata TG accordingly. This subgroup will have limited duration (less than a year, so that the new approach will be integrated in the Geoportal before the next Monitoring and Reporting round) and concrete task(s).
    • Call for nominations for both subgroups will be published soon.
  • Action 2.4
    • The JRC is already working on the sustainability of the different components and the establishment of governance mechanisms for them (see e.g. the work on the Geoportal above and the governance of INSPIRE artefacts below).

Proposed approach for governance of INSPIRE Artefacts

  • General approach
  • Application schemas
  • Q&A
  • The JRC presented a proposal for a new governance process of INSPIRE artefacts (UML models, XSD application schemas, TG and IR) defining roles, rules, responsibilities and timelines. The purpose is to clarify and streamline the process.
  • A workflow is presented for the case of INSPIRE schemas (UML models and XSD application schemas), which identifies the actors involved and their tasks. A similar workflow will be proposed for TG.
  • The document will be complemented by a release plan, the establishment of a sub-group under MIWP Action 2.3 and a description of the practical tools (based on GitHub) to be used in the different stages of the process.
  • The process applies to the newly collected change proposals. Many change proposals collected in the past were already endorsed and are currently under legal scrutiny for the amendment of IR: these will not follow the new procedure.
  • NL asked whether artefacts produced by good practice will undergo the same process. JRC responded, that priority is currently on covering the already existing issues (incl. those identified in the INSPIRE Community forum). Once this is done, depending also on the input of the new sub-group, the materials from good practices can be addressed.
Update on Commission initiatives 
  • Due to the uncertainty related to COVID-19, most probably the INSPIRE 2021 Conference will be held online and the face-to-face conference will be moved to 2022.
Wrap up of the meeting
  • A poll was run using to gather some general feedback on the meeting and the approaches for M&R and governance of artefacts. The results are available here.