MIWP-8 (D) Integrate metadata for interoperability into the Metadata TG

This section has now been locked for editing and a draft version have been moved into the draft document.
See page:
Further discussions and comments should be done on the draft




Ticket: https://ies-svn.jrc.ec.europa.eu/issues/2214


Article 13 of 1089/2010

Metadata required for Interoperability

The metadata describing a spatial data set shall include the following metadata elements required for interoperability:

1. Coordinate Reference System: Description of the coordinate reference system(s) used in the data set. 

See ticket https://ies-svn.jrc.ec.europa.eu/issues/2322


2. Temporal Reference System: Description of the temporal reference system(s) used in the data set.
This element is mandatory only if the spatial data set contains temporal information that does not refer to the default temporal reference system.


3. Encoding: Description of the computer language construct(s) specifying the representation of data objects in a record, file, message, storage device or transmission channel.


4. Topological Consistency: Correctness of the explicitly encoded topological characteristics of the data set as described by the scope.
This element is mandatory only if the data set includes types from the Generic Network Model and does not assure centreline topology (connectivity of centrelines) for the network.


5. Character Encoding: The character encoding used in the dataset.
This element is mandatory only if an encoding is used that is not based on UTF-8.


PLUS from current TG - Spatial representation type- The method used to spatially represent geographic information


******* Q.Spatial representation type is mandatory in the TG but not mentioned in 1089/2010 - are we including it ??? ************* 
Comment by Michael Östling.
The element is added in Amendment (M2)  to 1089 (Commission Regulation (EU) No 1253/2013 of 21 October 2013). So I think we can handle the element as the other 5.

The task is to describe in the TG how to handle these metadata elements.
It is important that these elements are clearly flagged as special type of metadata mainly for machine consumption.


Peter Kochmann
Lucie Kondrova
Javier Nogueras
James Reid         (Leader)
Antonio Rotundo
Michael Östling

Issue analysis

What problems causes current solution ?

The metadata elements for interoperability are mentioned in an informative annex to existing technical guidance. Thereby they will be considered quite poor. Nobody who is building metadata profiles expects additional mandatory elements without those being highlighted in the main body of the technical guidelines and implementing rules. 

NB - 3 are mandatory (including Spatial representation type) and 3 are conditionally mandatory

What can be a solution on current problem ?

Integration into the main mapping in chapter 2 considering the fact that these rules come from implementing rules concerning interoperability that do only apply data in focus of this implementing rule. Metadata for services are not involved.

Most of the mentioned metadata elements have a precise mapping to ISO 19115-elements that can be found in data specifications. Others can be derived from the given examples. We need to describe an exact mapping of the given metadata "information" to existing ISO 19115-elements. One possible way could be to make use of existing draft mapping tables and to transform these information into Technical Guidance "style".

Comment from Peter Kochmann (DE): Last year I built up a German draft mapping table assuming precise ISO 19115-elements (see attached file). Some of them do not match an element by now but a whole structure.



How does it relate to IR ?

IR metadata contains tables of metadata elements for data and services giving a multiplicity as well. In case of data regarding IR interoperability these additional metadata elements have to be considered in IR metadata too.


How will the solution affect existing tools ?


How will the solution affect existing metadata ?


What other issues in MIWG-8 is related to this change ?

It have relations to MIWP-8 (E-1) Integrate Theme specific metadata
The theme specific metadata are though mainly optional but it could maybe idea to handle these element in a common way.


What other groups within MIG-related workgroups could be linked to this issue ?


2013-06-17_themenspezifische_Metadaten_INSPIRE.xls (51 KB) Peter Kochmann, 01 Dec 2014 02:50 pm

2013-06-17_themespecic_metadata_INSPIRE.xlsx (26 KB) Peter Kochmann, 03 Dec 2014 02:36 pm

2014-12-03_themespecific_metadata_INSPIRE.xlsx (22.7 KB) Peter Kochmann, 04 Dec 2014 08:43 am

IT_MD4interoperability.pdf - Italian metadata for interoperability (17 KB) Antonio Rotundo, 04 Dec 2014 01:31 pm

NEM_recommendation_pagesRelatedTo_interoperabilityElements.pdf - NEM recomendations for Spanish core metadata, it includes some metadata interoperability elements (321 KB) Javier Nogueras Iso, 04 Dec 2014 03:31 pm

NEM_recommendation_pagesRelatedTo_interoperabilityElements.pdf - (updated version) NEM recommendations for Spanish core metadata, it includes 5 metadata interoperability elements (347 KB) Javier Nogueras Iso, 04 Dec 2014 03:54 pm

2014-11-04_Entwurf_Metadatenprofil_NRW_2.0_Struktur_aufgeloest_Daten.xlsx - German draft of metadata profile considering elements for interoperability (118 KB) Peter Kochmann, 16 Dec 2014 10:14 am

2014-12-16_metadata_interoperability_INSPIRE.xlsx - draft mapping table metadata interoperability with ISO considering current release of data specifications (21.9 KB) Peter Kochmann, 16 Dec 2014 02:02 pm

MIG-MWG-Issue8-template.doc - a very hast attempt to complete a template based on et existimg TG format. NB some of this is wrong and needs correcting!! (17.5 KB) James Reid, 16 Dec 2014 03:40 pm

MIG-MWG-Issue8-template-1_maintained_characterSet.doc - I tried to maintain the template and fill in information on element characterSet (35.5 KB) Peter Kochmann, 08 Jan 2015 11:32 am

MIG-MWG-Issue8-template-1_maintained_characterSet_revised.doc - I have revised the example of XML encoding in order to not confuse with the equivalent metadata element in MD_Metadata class (36 KB) Antonio Rotundo, 08 Jan 2015 11:58 am

MIG-MWG-Issue8-template-1_maintained_characterSet_revised.doc - Sorry, the correct file (36 KB) Antonio Rotundo, 08 Jan 2015 12:02 pm

MIG-MWG-Issue8-template-all-elements-stubbed.doc - template now inclides stubs for all 6 elements. requires completing and checking (45 KB) James Reid, 09 Jan 2015 12:51 pm

MIG-MWG-Issue8-template-all-elements-stubbed_revised.doc - A first attempt to fill in the template with reviews, comments, and suggestions (108 KB) Antonio Rotundo, 20 Jan 2015 01:15 pm

2015-01-20_metadata_interoperability_INSPIRE.xlsx - For Topological consistency I considered 19115 now instead of 19157. But there's no way for descriptive results! (22.4 KB) Peter Kochmann, 20 Jan 2015 01:24 pm

MD_IR_and_ISO_20131029_Copy_for_editing_in_MIWP8-UKEDIT.doc - First attempt to add additional items into existing TG template using suggested structure (1.38 MB) James Reid, 28 Jan 2015 12:43 pm

2015-01-29_metadata_interoperability_INSPIRE_19115.xlsx - For Topological consistency I considered 19115 only. Please look at the ticket for further information! (22.8 KB) Peter Kochmann, 29 Jan 2015 01:16 pm

MD_IR_and_ISO_20131029_Copy_for_editing_in_MIWP8-UKEDIT-12022015.odt - Latest version with Encoding:specification treated (355 KB) James Reid, 12 Feb 2015 10:21 am

2015-03-09_metadata_interoperability_INSPIRE_19115.xlsx - using lineage for descriptive results in data quality; please look at the ticket for further information (21.4 KB) Peter Kochmann, 10 Mar 2015 11:41 am

2015-03-24_metadata_interoperability_INSPIRE_19115.xlsx - I tried to integrate the XPaths for metadata for interoperability. Please tell me if there are any suggestions. (21.8 KB) Peter Kochmann, 24 Mar 2015 02:13 pm

2015-03-27_metadata_interoperability_INSPIRE_19115_rev.xlsx - I revised the Excel file, using a new element in the class DQ_Element for descriptive elements of topological consistency. Look at the ticket for further information (22.2 KB) Antonio Rotundo, 27 Mar 2015 01:13 pm