Sum-up of common issues from pilots Different types of exercises when joining statutory reporting & INSPIRE implementation: 1-To explain ‘INSPIRE fitting for purpose’; communication 2-To map INSPIRE and thematic requirements for monitoring programmes and reporting; joint analysis 3-To set-up a Pilot and to validate the results; joint project 4-To use results of Pilot at operational level- all MS, EC, EEA 5-To implement the results at National level: data, metadata, services for data flows at/between National public administration / private to prepare the final reporting, geoportal (National & European), to make visible at M&R None of the current pilot complete these steps yet

Sum-up of common issues from pilots Pilot is an opportunity to overcome the difficulties / complexity when mapping INSPIRE and other policy’s requirements: -saving resources -decreasing time need for implementation -getting agreed and harmonised results in all MS: need to make results available Repository for extended schemas necessary? - Re-usable tools when adequate and of schemas Need the involvement of Member States, Commission and EEA

Sum-up of common issues from pilots It takes time : Need to be planned considering the timeline of the monitoring programmes and reporting cycle: Action on MS, EC, EEA To consider meaningful steps and results when the next reporting exercise is too close for having full conformity with INSPIRE Overview of all reporting cycles is necessary (EC, MS) In particular if major changes on report content are already planned- from evaluation of reporting results or for policy evaluation / Refit: Action on Commission and EEA

Sum-up of common issues from pilots The content: Metadata and network services must be implemented, for raw and for conform data Data interoperability is the most complex INSPIRE component and risk heterogeneous / wrong / uncompleted solutions- sharing best practices: MIWP-14; 21 Not enough to map theme Area Management / restrictions/…(AM) or/ and EF All spatial objects belonging at different themes & described with INSPIRE data model should be considered; taking care of semantics

Sum-up of common issues from pilots The content: INSPIRE ID must be unique and persistent- need coordination at National level & EU level!!! When the statutory report do not ask all features, attributes, parameters, INSPIRE requirements, adding them anyway improves the information for reporting (often desirable/necessary for domain assessments) and it makes good INSPIRE implementation (conformity) INSPIRE Registers must be used; Link with MIWP

Thank you