• Further investigation about the subject
• Active collaboration between initiatives

• INSPIRE: Consolidation Team, Drafting Team Data Specifications, relevant Thematic Working Groups
• GEOSS: ADC
• GMES: GMES In-Situ Coordination project (EEA), fast-track service Implementation Groups, ESA HMA project

Incoherencies in the ways each initiative views thematic aspects are an obstacle to interoperability. Therefore, such thematic views, specified in data specifications, should be developed in synchronisation and, where practicable, adopted jointly. Note that this covers a range of aspects - including common portrayal and thematic data delivery mechanisms.

The situation is different depending on the theme. In general, the initiatives have not adopted data specifications for theme already so there are opportunities that should not be missed.

For the INSPIRE Annex I themes data specifications are in the adoption process in INSPIRE; other initiatives should consider using or extending these INSPIRE specifications before developing their own specifications.

For the INSPIRE Annex II/III themes the process is just starting with the call for reference material and experts, so there is the opportunity to coordinate the specification development in particular with GMES, GEOSS and SEIS.

One specific INSPIRE connection to the other initiatives is through the Annex III theme 'Environmental Monitoring Facilities' - e.g. it concerns facilities collecting observations and measurements that constitute the GMES in-situ component; also it will be very relevant for SEIS. Thus a specific coordination around this theme could be useful.

For the GMES space component, several opportunities arise:

• engagement with the INSPIRE 'orthoimagery' theme should address satellite remote sensing data
• while the ESA HMA project currently addresses only product-level metadata through OGC document 06-080 (GML Application Schema for EO Products), there is an opportunity for it also to address a model for the data product itself - this would facilitate convergence with the INSPIRE architecture, e.g. for data specifications, and services (discovery, download, view). E.g. OGC document 06-080 could be extended to describing content and structure of data products themselves; then HMA collection-level metadata would correspond to INSPIRE discovery metadata, while HMA product-level metadata becomes part of the data specification.
• the INSPIRE encoding guidelines (D2.7) addresses file-based data, which is highly relevant to the GMES space component and ESA HMA activity (since these use file-based formats); this also requires a data specification (not just an EO metadata schema)

In addition, ISO and OGC have also started to develop thematic standards that should also be considered, at least if the standard is accepted by the relevant communities.

• Technology Watch Report - Data Interoperability [PDF]
• Comparative analysis report (version 2) [PDF]
• Comparative Analysis Report (version 2) - Annex Recommendations [PDF]
• Example of coordinated approach: INSPIRE-GMES workshop for land cover in June 2009

• incompatible schedules
• incompatible priorities
• incompatible thematic views
• commitment of the initiatives is required for the process and for applying the recommendations