Project

General

Profile

Actions
History

Wiki » EEA SDI »

EEA Metadata Profile v20 » History » Revision 6

« Previous | Revision 6/165 (diff) | Next »
Jose Rubio, 2019-11-21 10:53

EEA Metadata Profile (v2.0, December 2019) - DRAFT VERSION (NOT YET IN FORCE!)

1. Introduction

This wiki page provides the full description of the EEA Metadata profile, including all the compulsory and conditional metadata elements, their XML encoding, their mapping against the INSPIRE Metadata Technical Guidelines and ISO standards, their status as well as some important notes about their content.

The EEA metadata profile follows the *Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007* which is the implementation specification for defining metadata for INSPIRE datasets and services in ISO/TS 19139 based XML format in compliance with the INSPIRE IR for metadata and network services (Regulation 1205/2008 and Regulation 1089/2010). T he EEA metadata profile considers as compulsory all optional elements offered by ISO 19115 and INSPIRE which are regarded as useful for EEA activities.

This section reviews every single metadata element of the EEA profile. They feature here below following the order in which they appear in the file attachment:"xxx" which is compliant with the EEA metadata profile v2.0. This metadata refers to a dataset containing the xxx. Please note that a few conditional elements may not however appear in this file.

A metadata editor tool based on GeoNetwork is available on https://sdi.eea.europa.eu/editor-catalogue/, accessible only with EIONET account. A metadata template is also available to facilitate the compliance with the EEA metadata profile. The wiki page EEA SDI editor User Guide provides a detailed step-by-step description on how to create and edit metadata using the SDI Editor following the EEA metadata profile described here.

Not all the metadata elements in the profile are supposed to be edited by the data stewards - as indicated in the corresponding section, a few are to be edited by the SDI Team and some are automatically generated by (any) metadata editor tool.

The current version of the EEA metadata profile (v2.0) has been made public in December 2019. In case you have any question, doubt or suggestion, please contact the EEA SDI team on .

2. Analysis of EEA metadata profile elements

MD_Metadata/fileIdentifier

XML encoding

    <gmd:fileIdentifier>
          <gco:CharacterString>c6d98fda-796e-40c0-b953-d716a8db1df5</gco:CharacterString>
        </gmd:fileIdentifier>

References

INSPIRE Metadata TG v2.0.1
ISO19115:2003 Sec. B.2.1 p38 Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The file identifier value does not need to be edited manually as this identifier will be overwritten automatically at time of first import of the metadata file into GeoNetwork.
  • This metadata element does not require any editing.

MD_Metadata/language

XML encoding

        <gmd:language>
           <gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="eng"/>
        </gmd:language>

References

INSPIRE Metadata TG v1.3 Sec. 2.11.1 p60 Mandatory
ISO19115:2003 Sec. B.2.1 p38 Conditional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • All metadata records shall be written in English therefore this element does not need to be edited.
  • This metadata element does not require any editing.

MD_Metadata/characterSet

XML encoding

  <gmd:characterSet>
      <gmd:MD_CharacterSetCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_CharacterSetCode" 
                               codeListValue="utf8"/>
  </gmd:characterSet>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.1 p38 Conditional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The character coding standard used for the metadata set shall be utf8.
  • This element has been included in the INSPIRE metadata guidelines v2.0.1 (conditional)
  • This metadata element does not require any editing.

MD_Metadata/parentIdentifier

XML encoding

<gmd:parentIdentifier>
      <gco:CharacterString>53c161cf-235b-4647-9200-446b60c5f59c</gco:CharacterString>
   </gmd:parentIdentifier>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.1 p38 Conditional
ISO19139

Status in EEA metadata

Conditional: only for those datasets which belong to a dataset series or are a subset from another dataset existing in the SDI

Important notes

  • This metadata element allows the logical link between a dataset metadata and the metadata of a dataset of which the former is a subset (e.g. datasets within a series, public versions which are subsets of internal versions without restricted data).
  • A dataset series is defined as a collection of datasets which share the same product specification.
  • This element should be added whenever the related series or a parent resource has a metadata record in the EEA catalogue SDI.
  • The parent identifier value will be edited manually by the SDI Team. The Metadata editor should however inform the SDI Team of the existence of a dataset series or parent resource to which the new metadata should be linked to.
  • This metadata element requires editing by the SDI Team.

MD_Metadata/hierarchyLevel

XML encoding

  <gmd:hierarchyLevel>
      <gmd:MD_ScopeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_ScopeCode" 
                        codeListValue="dataset"/>
  </gmd:hierarchyLevel>

References

INSPIRE Metadata TG v1.3 Sec. 2.2.3 p20 Mandatory
ISO19115:2003 Sec. B.2.1 p38 Conditional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • We are so far only considering metadata of datasets (no services).
  • Dataset metadata series are produced by the SDI Team, in collaboration with the thematic experts.
  • This metadata element does not require any editing.

MD_Metadata/contact

XML encoding

    <gmd:contact>
        <gmd:CI_ResponsibleParty>
            <gmd:organisationName>
                <gco:CharacterString>European Environment Agency</gco:CharacterString>
            </gmd:organisationName>
            <gmd:contactInfo>
                <gmd:CI_Contact>
                    <gmd:address>
                        <gmd:CI_Address>
                            <gmd:deliveryPoint>
                                <gco:CharacterString>Kongens Nytorv 6</gco:CharacterString>
                            </gmd:deliveryPoint>
                            <gmd:city>
                                <gco:CharacterString>Copenhagen</gco:CharacterString>
                            </gmd:city>
                            <gmd:administrativeArea>
                                <gco:CharacterString>K</gco:CharacterString>
                            </gmd:administrativeArea>
                            <gmd:postalCode>
                                <gco:CharacterString>1050</gco:CharacterString>
                            </gmd:postalCode>
                            <gmd:country>
                                <gco:CharacterString>Denmark</gco:CharacterString>
                            </gmd:country>
                            <gmd:electronicMailAddress>
                                <gco:CharacterString>sdi@eea.europa.eu</gco:CharacterString>
                            </gmd:electronicMailAddress>
                        </gmd:CI_Address>
                    </gmd:address>
                </gmd:CI_Contact>
            </gmd:contactInfo>
                        <gmd:role>
                               <gmd:CI_RoleCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_RoleCode" 
                             codeListValue="pointOfContact"/>
                        </gmd:role>
        </gmd:CI_ResponsibleParty>
    </gmd:contact>

References

INSPIRE Metadata TG v1.3 Sec. 2.11.1 p58 Mandatory
ISO19115:2003 Sec. B.2.1 p32 (links to Sec. B.3.2 p85) Mandatory
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This element refers to the metadata point of contact.
  • We place as default value the responsible for metadata about spatial datasets newly published, the EEA SDI Team.
  • This metadata element does not require any editing.

MD_Metadata/dateStamp

XML encoding

  <gmd:dateStamp>
      <gco:DateTime>2017-12-14T11:10:17</gco:DateTime>
  </gmd:dateStamp>

References

INSPIRE Metadata TG v1.3 Sec. 2.11.2 p60 Mandatory
ISO19115:2003 Sec. B.2.1 p38 (links to Sec. B.4.2 p91) Mandatory
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This element refers to the metadata creation date.
  • As some metadata elements are updated automatically when the metadata record is inserted into the catalogue, this date is considered as being the date of insertion into our catalogue and will be generated automatically by GeoNetwork.
  • This metadata element does not require any editing.

MD_Metadata/metadataStandardName

XML encoding

  <gmd:metadataStandardName>
      <gco:CharacterString xmlns:gmx="http://www.isotc211.org/2005/gmx" 
                           xmlns:srv="http://www.isotc211.org/2005/srv">ISO 19115:2003/19139</gco:CharacterString>
  </gmd:metadataStandardName>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.1 p38 Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This metadata element is generated automatically by Geonetwork and any modification will be overwritten by GeoNetwork.
  • This metadata element does not require any editing.

MD_Metadata/metadataStandardVersion

XML encoding

    <gmd:metadataStandardVersion>
        <gco:CharacterString xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:srv="http://www.isotc211.org/2005/srv">1.0</gco:CharacterString>
    </gmd:metadataStandardVersion>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.1 p38 (modified in ISO 19115:2003/Cor.1:2006) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This metadata element is generated automatically by GeoNetwork and any modification will be overwritten by GeoNetwork.
  • This metadata element does not require any editing.

MD_Metadata/referenceSystemInfo/*/referenceSystemIdentifier

XML encoding

  <gmd:referenceSystemInfo>
    <gmd:MD_ReferenceSystem>
      <gmd:referenceSystemIdentifier>
        <gmd:RS_Identifier>
          <gmd:code>
            <gco:CharacterString>urn:ogc:def:crs:EPSG:7.1:3035</gco:CharacterString>
          </gmd:code>
          <gmd:codeSpace>
            <gco:CharacterString>OGP Surveying & Positioning Committee</gco:CharacterString>
          </gmd:codeSpace>
        </gmd:RS_Identifier>
      </gmd:referenceSystemIdentifier>
    </gmd:MD_ReferenceSystem>
  </gmd:referenceSystemInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.7.3 p65 (modified in ISO 19115:2003/Cor.1:2006) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The Coordinate Reference System shall be referred to with its EPSG code (the spatial reference website provides a search interface to the EPSG database).
  • When there is not any EPSG code to describe a CRS, the CRS shall be described in the metadata. Contact the SDI Team for further details.
  • In this example, the EPSG code used is 3035 (urn:ogc:def:crs:EPSG:7.1:3035) which corresponds to a Lambert Azimuthal Equal Area 52N 10E projection based on ETRS89 datum.
  • The INSPIRE Metadata TG 2.0.1 includes this (interoperability) element as mandatory.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/citation/*/title

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
        <gmd:citation>
            <gmd:CI_Citation>
                <gmd:title>
                    <gco:CharacterString>CDDA polygons for public access - version 15, Sept. 2017</gco:CharacterString>
                </gmd:title>
                                     <!-- [.....................] -->
            </gmd:CI_Citation>
        </gmd:citation>
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.2.1 p17 Mandatory
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.3.2 p85) Mandatory
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • In general, titles need to be self-explanatory and should not contain acronyms unless they are widely known. In any case, should an acronym be used in the title, it shall be made explicit in the abstract. For datasets which have regular updates, the version number and the dataset creation date shall be added at the end of the title. The public or internal nature of the dataset should also be reflected in the title. More details about the recommended title convention here.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/citation/*/date (creation)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
        <gmd:citation>
            <gmd:CI_Citation>
                                     <!-- [.....................] -->
                <gmd:date>
                        <gco:Date>2017-09-14</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="creation"/>
                     </gmd:dateType>
                  </gmd:CI_Date>
               </gmd:date>
                                     <!-- [.....................] -->
            </gmd:CI_Citation>
        </gmd:citation>
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.6.4 p41 Conditional (at least one of temporal extent, date of creation, publication or last revision)
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.3.2 p85) Conditional (at least one of date of creation, publication or last revision)
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The date of creation shall be equal to the date of publication for datasets published on the EEA website.
  • For datasets which are not published on the EEA website, this date might be retrieved from the metadata file generated by the metadata editor which could be available together with the dataset. If no suitable creation date can be found, please contact the SDI Team.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/citation/*/date (publication)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
        <gmd:citation>
            <gmd:CI_Citation>
                                     <!-- [.....................] -->
                 <gmd:date>
                  <gmd:CI_Date>
                     <gmd:date>
                        <gco:Date>2017-09-18</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"/>
                     </gmd:dateType>
                  </gmd:CI_Date>
               </gmd:date>
                                     <!-- [.....................] -->
            </gmd:CI_Citation>
        </gmd:citation>
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.6.2 p38 Conditional (at least one of temporal extent, date of creation, publication or last revision)
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.3.2 p85) Conditional (at least one of date of creation, publication or last revision)
ISO19139

Status in EEA metadata

Conditional: only for datasets published by the EEA, in particular on the EEA website (http://www.eea.europa.eu/data-and-maps/data)

Important notes

  • The date of publication shall only be present for datasets which are published by the EEA.
  • For datasets which are not published on the EEA website (e.g. Copernicus), please contact the SDI team.
  • This metadata element requires editing or deletion.

MD_Metadata/identificationInfo/*/citation/*/edition

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
        <gmd:citation>
            <gmd:CI_Citation>
                                     <!-- [.....................] -->
                <gmd:edition>
                    <gco:CharacterString>15-0</gco:CharacterString>
                </gmd:edition>
                                     <!-- [.....................] -->
            </gmd:CI_Citation>
        </gmd:citation>
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.3.2 p85) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The version and revision numbers of the dataset should be consistent with this element, separated by a point (VersionNumber.RevisionNumber).
  • This metadata element requires editing

MD_Metadata/identificationInfo/*/citation/*/identifier

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
        <gmd:citation>
            <gmd:CI_Citation>
                                     <!-- [.....................] -->
                <gmd:identifier>
                    <gmd:RS_Identifier>
                        <gmd:code>
                            <gco:CharacterString>eea_v_3035_100_k_cdda-poly-public_20160101-20170315_rev15-0</gco:CharacterString>
                        </gmd:code>
                    </gmd:RS_Identifier>
                </gmd:identifier>
            </gmd:CI_Citation>
        </gmd:citation>
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.2.5 p24 Mandatory
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.3.2 p85) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This identifier shall be unique and follow this convention.
  • This identifier shall be set to the directory name in which the dataset is contained.
  • In order to ensure consistency with the existing content of the SDI, the SDI Team will check and modify the identifier when necessary.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/abstract

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
        <gmd:abstract>
            <gco:CharacterString>The Common Database on Designated Areas (CDDA) is more commonly known as Nationally designated areas. It is the official source of protected area information from European countries to the World Database of Protected Areas (WDPA).
The inventory began in 1995 under the CORINE programme of the European Commission. It is now one of the agreed Eionet priority data flows maintained by EEA with support from the European Topic Centre on Biological Diversity.
The CDDA data can be queried online in the European Nature Information System (EUNIS).
Geographical coverage of GIS vector boundary data: Albania, Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Kosovo under UNSC Resolution 1244/99, Latvia, Liechtenstein, Lithuania, Luxembourg, the former Yugoslav Republic of Macedonia, Malta, Montenegro, the Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EEA does not have permission to distribute some or all sites reported by Estonia, Ireland, Romania and Turkey.When re-using the data, copyright is to be mentioned specifically for Estonia and for Finland: "Estonian Environmental Register 01.01.2017; "©Finnish Environment Institute, 2017".</gco:CharacterString>
        </gmd:abstract>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.2.2 p18 Mandatory
ISO19115:2003 Sec. B.2.2.1 p40 Mandatory
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This is a brief narrative summary of the content of the resource. The abstract provides a clear and concise statement that enables the reader to understand the content of the data or service. Ideally it should also contain information about the coverage (linguistic transcriptions of the extent or location), main attributes, data sources, legal references and importance of the work.
  • Acronyms should be written in full when first used.
  • When the metadata refers to a revision of an already existing dataset, it is important to indicate as well the main changes on this new version.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/status

XML encoding

<gmd:status><gmd:MD_ProgressCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_ProgressCode" codeListValue="obsolete"/></gmd:status>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.2.1 p40 Optional
ISO19139

Status in EEA metadata

Conditional - only for obsolete, archived or superseded datasets as well as datasets from completed projects

Important notes

  • This element describes the status of the resource.
  • The value of this element is established by the ISO19115 codelist MD_ProgressCode. The EEA metadata profile only considers the following values (including one from ISO19115-1):
    • completed: the production of the dataset has been completed (this is to be used only for those datasets produced in the context of specific projects)
    • historicalArchive: to be used only for those datasets stored in an offline storage facility (this is unlikely to happen in the context of the EEA SDI)
    • obsolete: only for those datasets which are no longer relevant (only kept for historical purposes)
    • superseded: dataset which has been replaced by a new one (this is to be used for datasets replaced by new versions)
  • The example above is not included in the metadata file used in these guidelines.
  • This metadata element requires editing by SDI Team

MD_Metadata/identificationInfo/*/pointOfContact (point of contact)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
        <gmd:pointOfContact>
            <gmd:CI_ResponsibleParty>
                <gmd:organisationName>
                    <gco:CharacterString>European Environment Agency</gco:CharacterString>
                </gmd:organisationName>
                <gmd:contactInfo>
                    <gmd:CI_Contact>
                        <gmd:address>
                            <gmd:CI_Address>
                                <gmd:deliveryPoint>
                                    <gco:CharacterString>Kongens Nytorv 6</gco:CharacterString>
                                </gmd:deliveryPoint>
                                <gmd:city>
                                    <gco:CharacterString>Copenhagen</gco:CharacterString>
                                </gmd:city>
                                <gmd:administrativeArea>
                                    <gco:CharacterString>K</gco:CharacterString>
                                </gmd:administrativeArea>
                                <gmd:postalCode>
                                    <gco:CharacterString>1050</gco:CharacterString>
                                </gmd:postalCode>
                                <gmd:country>
                                    <gco:CharacterString>Denmark</gco:CharacterString>
                                </gmd:country>
                                <gmd:electronicMailAddress>
                                    <gco:CharacterString>info@eea.europa.eu</gco:CharacterString>
                                </gmd:electronicMailAddress>
                            </gmd:CI_Address>
                        </gmd:address>
                        <gmd:onlineResource>
                            <gmd:CI_OnlineResource>
                                <gmd:linkage>
                                    <gmd:URL>http://www.eea.europa.eu</gmd:URL>
                                </gmd:linkage>
                                <gmd:protocol>
                                    <gco:CharacterString>WWW:LINK-1.0-http--link</gco:CharacterString>
                                </gmd:protocol>
                                <gmd:name>
                                    <gco:CharacterString>European Environment Agency public website</gco:CharacterString>
                                </gmd:name>
                                <gmd:function>
                                    <gmd:CI_OnLineFunctionCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#CI_OnLineFunctionCode" codeListValue="information"/>
                                </gmd:function>
                            </gmd:CI_OnlineResource>
                        </gmd:onlineResource>
                    </gmd:CI_Contact>
                </gmd:contactInfo>
                <gmd:role>
                    <gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#CI_RoleCode" codeListValue="pointOfContact"/>
                </gmd:role>
            </gmd:CI_ResponsibleParty>
        </gmd:pointOfContact>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.10 p55-57 Conditional (at least one responsible party is mandatory)
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.3.2.1 p85) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The responsible party acting as Point of Contact shall be the EEA (using the public enquiries mailbox) for any dataset owned by EEA.
  • The responsible party acting as Point of Contact is the organization or company owning the dataset when the latter is not owned by EEA. In case of doubts here please contact the EEA SDI Team.
  • It is recommended to use a functional mailbox instead of personal email address, and avoid any personal data.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/pointOfContact (custodian)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
        <gmd:pointOfContact>
            <gmd:CI_ResponsibleParty>
                <gmd:organisationName>
                    <gco:CharacterString>European Environment Agency</gco:CharacterString>
                </gmd:organisationName>
                      <gmd:contactInfo>
                    <gmd:CI_Contact>
                        <gmd:address>
                            <gmd:CI_Address>
                                <gmd:electronicMailAddress>
                                    <gco:CharacterString>info@eea.europa.eu</gco:CharacterString>
                                </gmd:electronicMailAddress>
                            </gmd:CI_Address>
                        </gmd:address>
                    </gmd:CI_Contact>
                </gmd:contactInfo>
                <gmd:role>
                    <gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#CI_RoleCode" codeListValue="custodian"/>
                </gmd:role>
            </gmd:CI_ResponsibleParty>
        </gmd:pointOfContact>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.10 p55-57 Conditional (at least one responsible party is mandatory)
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.3.2.1 p85) Optional
ISO19139

Status in EEA metadata

Conditional: it shall be required at least for all datasets owned by EEA

Important notes

  • This metadata element shall be filled in at least for datasets owned by EEA.
  • In case of doubts when the dataset is not owned by EEA please contact the EEA SDI Team.
  • It is recommended to use a functional mailbox instead of personal email address, and avoid any personal data.
  • This metadata element requires editing or deletion.

MD_Metadata/identificationInfo/*/resourceMaintenance

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
         <gmd:resourceMaintenance>
            <gmd:MD_MaintenanceInformation>
               <gmd:maintenanceAndUpdateFrequency>
                  <gmd:MD_MaintenanceFrequencyCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_MaintenanceFrequencyCode" 
                                                   codeListValue="annually"/>
               </gmd:maintenanceAndUpdateFrequency>
            </gmd:MD_MaintenanceInformation>
         </gmd:resourceMaintenance>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.2.5 p57 and B.5.18 p99) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This element refers to the frequency with which modifications and deletions are made to the data after it is first produced.
  • The metadata element shall take one of these values (as listed in Sec. B.5.18 p99 of ISO19115/2003):
    • continual
    • daily
    • weekly
    • fortnightly
    • monthly
    • quaterly
    • biannually
    • annually
    • asNeeded
    • irregular
    • notPlanned
    • unknown
  • By default the EEA template sets this element to "notPlanned".
  • In case no frequency from the list above is satisfactory, the following resourceMaintenance metadata element should be used instead, with the relevant frequency expressed as PeriodDuration (in this example, a frequency of 1 year and 6 months is expressed with P1Y6M0DT0H0M0S which stands for a period of @1Y@ear and @6M@onths):
    <gmd:resourceMaintenance>
    <gmd:MD_MaintenanceInformation>
        <gmd:maintenanceAndUpdateFrequency  gco:nilReason="inapplicable"/>
        <gmd:userDefinedMaintenanceFrequency>
            <gts:TM_PeriodDuration xmlns:gts="http://www.isotc211.org/2005/gts">P1Y6M0DT0H0M0S</gts:TM_PeriodDuration>
        </gmd:userDefinedMaintenanceFrequency>
    </gmd:MD_MaintenanceInformation>
</gmd:resourceMaintenance>
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/graphicOverview (Dataset thumbnail)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
                   <gmd:graphicOverview>
            <gmd:MD_BrowseGraphic>
               <gmd:fileName>
                  <gco:CharacterString>http://sdi.eea.europa.eu/public/catalogue-graphic-overview/c6d98fda-796e-40c0-b953-d716a8db1df5.png</gco:CharacterString>
               </gmd:fileName>
            </gmd:MD_BrowseGraphic>
         </gmd:graphicOverview>
                      <!-- [.....................] -->
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.2.2 p42 Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The image shall be generated in PNG format, shall provide a clear overview of the whole dataset and not be bigger than 1 MB.
  • The filename of the thumbnail shall follow a standardised naming convention: METADATA-UUID.png.
  • This metadata element requires editing by the SDI Team.

MD_Metadata/identificationInfo/*/descriptiveKeywords (INSPIRE themes)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
 <gmd:descriptiveKeywords>
            <gmd:MD_Keywords>
               <gmd:keyword>
                  <gco:CharacterString>Protected sites</gco:CharacterString>
               </gmd:keyword>
               <gmd:type>
                  <gmd:MD_KeywordTypeCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#MD_KeywordTypeCode" 
                                          codeListValue="theme"/>
               </gmd:type>
               <gmd:thesaurusName>
                  <gmd:CI_Citation>
                     <gmd:title>
                        <gco:CharacterString>GEMET - INSPIRE themes, version 1.0</gco:CharacterString>
                     </gmd:title>
                     <gmd:date>
                        <gmd:CI_Date>
                           <gmd:date>
                              <gco:Date>2008-06-01</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"/>
                           </gmd:dateType>
                        </gmd:CI_Date>
                     </gmd:date>
                     <gmd:identifier>
                        <gmd:MD_Identifier>
                           <gmd:code>
                              <gmx:Anchor xmlns:gmx="http://www.isotc211.org/2005/gmx" 
                                          xlink:href="http://sdi.eea.europa.eu/internal-catalogue/srv/eng/thesaurus.download?ref=external.theme.inspire-theme">geonetwork.thesaurus.external.theme.inspire-theme</gmx:Anchor>
                           </gmd:code>
                        </gmd:MD_Identifier>
                     </gmd:identifier>
                  </gmd:CI_Citation>
               </gmd:thesaurusName>
            </gmd:MD_Keywords>
         </gmd:descriptiveKeywords>
                      <!-- [.....................] -->
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.4 p30-34 Mandatory
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.2.2.3 p43) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The INSPIRE spatial themes are defined in the INSPIRE Directive. Values from the INSPIRE Theme Register (http://inspire.ec.europa.eu/theme) shall be used without further editing.
  • More than one theme can be selected, but there shall be one keyword/characterString element per INSPIRE spatial theme to which the dataset belongs (as reflected in the example).

MD_Metadata/identificationInfo/*/descriptiveKeywords (EEA keywords list)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
 <gmd:descriptiveKeywords>
            <gmd:MD_Keywords>
               <gmd:keyword>
                  <gco:CharacterString>designated areas</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>protected areas</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>CDDA</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>ETC/BD</gco:CharacterString>
               </gmd:keyword>
               <gmd:thesaurusName>
                  <gmd:CI_Citation>
                     <gmd:title>
                        <gco:CharacterString>EEA keyword list</gco:CharacterString>
                     </gmd:title>
                     <gmd:date>
                        <gmd:CI_Date>
                           <gmd:date>
                              <gco:Date>2002-03-01</gco:Date>
                           </gmd:date>
                           <gmd:dateType>
                              <gmd:CI_DateTypeCode codeList="" codeListValue="creation"/>
                           </gmd:dateType>
                        </gmd:CI_Date>
                     </gmd:date>
                  </gmd:CI_Citation>
               </gmd:thesaurusName>
            </gmd:MD_Keywords>
         </gmd:descriptiveKeywords>
                      <!-- [.....................] -->
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.2.2.3 p43) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The EEA keywords list consists of EEA relevant keywords that are intended to be used only by internal EEA users (these keywords are NOT published in the public catalogue).
  • EEA keywords shall be short, meaningful and shall not duplicate other metadata elements which can act as keywords too (i.e. spatialRepresentationType, Inspire themes, EEA categories, topicCategory)
  • Already existing keywords should be reused whenever possible.
  • Keywords specific to internal projects (IDP) should also be included as EEA keywords.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/descriptiveKeywords (EEA data categories)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
        <gmd:descriptiveKeywords>
            <gmd:MD_Keywords>
                <gmd:keyword>
                    <gco:CharacterString>geospatial data</gco:CharacterString>
                </gmd:keyword>
                <gmd:thesaurusName>
                    <gmd:CI_Citation>
                        <gmd:title>
                            <gco:CharacterString>EEA categories</gco:CharacterString>
                        </gmd:title>
                        <gmd:date>
                            <gmd:CI_Date>
                                <gmd:date>
                                    <gco:Date>2010-07-06</gco:Date>
                                </gmd:date>
                                <gmd:dateType>
                                    <gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#CI_DateTypeCode" codeListValue="creation"/>
                                </gmd:dateType>
                            </gmd:CI_Date>
                        </gmd:date>
                    </gmd:CI_Citation>
                </gmd:thesaurusName>
            </gmd:MD_Keywords>
        </gmd:descriptiveKeywords>
                      <!-- [.....................] -->
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.2.2.3 p43) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This metadata element is used to discriminate between geospatial datasets, maps, figures, charts, etc.
  • We are currently reviewing only geospatial datasets with an explicit or implicit spatial component, therefore this metadata element should be set to "geospatial data". The EEA Template already includes this value by default, so it should not require any editing.
  • This metadata element does not require any editing.

MD_Metadata/identificationInfo/*/descriptiveKeywords (GEMET concepts)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
<gmd:descriptiveKeywords>
            <gmd:MD_Keywords>
               <gmd:keyword>
                  <gco:CharacterString>natural area</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>natural areas protection</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>protected area</gco:CharacterString>
               </gmd:keyword>
               <gmd:type>
                  <gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_KeywordTypeCode" 
                                          codeListValue=""/>
               </gmd:type>
               <gmd:thesaurusName>
                  <gmd:CI_Citation>
                     <gmd:title>
                        <gco:CharacterString>GEMET - Concepts, version 3.0</gco:CharacterString>
                     </gmd:title>
                     <gmd:date>
                        <gmd:CI_Date>
                           <gmd:date>
                              <gco:Date>2011-07-13</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"/>
                           </gmd:dateType>
                        </gmd:CI_Date>
                     </gmd:date>
                  </gmd:CI_Citation>
               </gmd:thesaurusName>
            </gmd:MD_Keywords>
         </gmd:descriptiveKeywords>
                      <!-- [.....................] -->
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.4 p30-34 Mandatory
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.2.2.3 p43) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • There should be at least 3-4 GEMET concepts per dataset.
  • There shall be one keyword/characterString element per GEMET concept to which the dataset belongs.
  • GEMET concept names shall be retrieved from the English version of the GEMET - Concepts list without any further editing (no change in capitalization, etc.)
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/descriptiveKeywords (Location / coverage of the dataset)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                    <!-- [.....................] -->
            <gmd:descriptiveKeywords>
            <gmd:MD_Keywords>
               <gmd:keyword>
                  <gco:CharacterString>Albania</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>Kosovo</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>Montenegro</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>EFTA4</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>Bosnia and Herzegovina</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>Serbia</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>Macedonia</gco:CharacterString>
               </gmd:keyword>
               <gmd:keyword>
                  <gco:CharacterString>EU28</gco:CharacterString>
               </gmd:keyword>
               <gmd:type>
                  <gmd:MD_KeywordTypeCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#MD_KeywordTypeCode" 
                                          codeListValue="place"/>
               </gmd:type>
               <gmd:thesaurusName>
                  <gmd:CI_Citation>
                     <gmd:title>
                        <gco:CharacterString>Continents, countries, sea regions of the world.</gco:CharacterString>
                     </gmd:title>
                     <gmd:date>
                        <gmd:CI_Date>
                           <gmd:date>
                              <gco:Date>2015-07-17</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"/>
                           </gmd:dateType>
                        </gmd:CI_Date>
                     </gmd:date>
                     <gmd:identifier>
                        <gmd:MD_Identifier>
                           <gmd:code>
                              <gmx:Anchor xmlns:gmx="http://www.isotc211.org/2005/gmx" 
                                          xlink:href="http://sdi.eea.europa.eu/internal-catalogue/srv/eng/thesaurus.download?ref=external.place.regions">geonetwork.thesaurus.external.place.regions</gmx:Anchor>
                           </gmd:code>
                        </gmd:MD_Identifier>
                     </gmd:identifier>
                  </gmd:CI_Citation>
               </gmd:thesaurusName>
            </gmd:MD_Keywords>
         </gmd:descriptiveKeywords>
                    <!-- [.....................] -->
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.2.2.3 p43) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This metadata element is used to describe the intended spatial coverage of a dataset in text form.
  • Where appropriate, codes such as EEA32, EU27, EU28, EFTA4 should be used instead of listing all Member States.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/descriptiveKeywords (Temporal resolution of the dataset)

XML encoding

  <gmd:descriptiveKeywords xmlns:srv="http://www.isotc211.org/2005/srv" 
                                  xmlns:gmx="http://www.isotc211.org/2005/gmx">
            <gmd:MD_Keywords>
               <gmd:keyword>
                  <gco:CharacterString>Biannually</gco:CharacterString>
               </gmd:keyword>
               <gmd:type>
                  <gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_KeywordTypeCode" 
                                          codeListValue="temporal"/>
               </gmd:type>
               <gmd:thesaurusName>
                  <gmd:CI_Citation>
                     <gmd:title>
                        <gco:CharacterString>Temporal resolution</gco:CharacterString>
                     </gmd:title>
                     <gmd:date>
                        <gmd:CI_Date>
                           <gmd:date>
                              <gco:Date>2017-11-07</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"/>
                           </gmd:dateType>
                        </gmd:CI_Date>
                     </gmd:date>
                     <gmd:identifier>
                        <gmd:MD_Identifier>
                           <gmd:code>
                              <gmx:Anchor xlink:href="https://galliwasp.eea.europa.eu/editor-catalogue/srv/eng/thesaurus.download?ref=local.temporal.temporal-update">geonetwork.thesaurus.local.temporal.temporal-update</gmx:Anchor>
                           </gmd:code>
                        </gmd:MD_Identifier>
                     </gmd:identifier>
                  </gmd:CI_Citation>
               </gmd:thesaurusName>
            </gmd:MD_Keywords>
         </gmd:descriptiveKeywords>

References

INSPIRE Metadata TG v1.3
ISO19115:2003
ISO19139

Status in EEA metadata

Conditional: only for those datasets which belong to a time series

Important notes

  • Temporal resolution is a metadata element introduced in the ISO 19115-1:2014 (Geographic Information -- Metadata -- Part 1: Fundamentals)
  • ISO 19115-1 refers to Temporal Resolution as the smallest resolvable temporal period in a resource. Springer defines temporal resolution as the amount of time needed to revisit and acquire data for the exact same location. When applied to remote sensing, this amount of time depends on the orbital characteristics of the sensor platform as well as sensor characteristics.
  • As the EEA Catalogue has not yet implemented the standard ISO 19115-1, the information will be provided as a keyword to be selected from an already existing ISO Codelist (MaintenanceFrequencyCode).
  • This element is to added only when datasets belong to a time series.
  • The example above is not included in the metadata file used in these guidelines.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/resourceConstraints/*/useLimitation and */accessConstraints

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
             <gmd:resourceConstraints>
            <gmd:MD_Constraints>
               <gmd:useLimitation>
                  <gco:CharacterString>EEA standard re-use policy: unless otherwise indicated, re-use of content on the EEA website for commercial or non-commercial purposes is permitted free of charge, provided that the source is acknowledged (http://www.eea.europa.eu/legal/copyright). Copyright holder: European Environment Agency (EEA).</gco:CharacterString>
               </gmd:useLimitation>
            </gmd:MD_Constraints>
        </gmd:resourceConstraints>
         <gmd:resourceConstraints>
            <gmd:MD_LegalConstraints>
               <gmd:accessConstraints>
                  <gmd:MD_RestrictionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_RestrictionCode" 
                                          codeListValue="otherRestrictions"/>
               </gmd:accessConstraints>
               <gmd:otherConstraints>
                  <gco:CharacterString>no limitations</gco:CharacterString>
               </gmd:otherConstraints>
            </gmd:MD_LegalConstraints>
         </gmd:resourceConstraints>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.9 p51-55 Mandatory
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.2.3 p46) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • These two elements refer to any use limitation and access constraints that the dataset may have. The useLimitation element is free text, while the element accessConstraints shall use a value from the MD_RestrictionCode codelist. The EEA metadata editor includes a list with the different values to select.
  • In the useLimitation element and for datasets owned by EEA that can be freely distributed (default for EEA owned datasets) the following text shall be used: "EEA standard re-use policy: unless otherwise indicated, re-use of content on the EEA website for commercial or non-commercial purposes is permitted free of charge, provided that the source is acknowledged (http://www.eea.europa.eu/legal/copyright). Copyright holder: European Environment Agency (EEA)."
  • In the accessConstraints element and for datasets owned by EEA that can be freely distributed (default for EEA owned datasets), the value that needs to be selected is Other restrictions. When this value is selected, it is necessary to fill in as well the conditional element otherConstraints with the free text no limitations.
  • For datasets which are not owned by EEA but are distributed by EEA, contact the SDI Team.
  • For datasets which are protected by intellectual property rights (typically datasets acquired from external providers like Gisco), use the text License under useLimitation, select copyright from the list of accessConstraints and the value of license in the optional element useConstraints, as is detailed below:
<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
        <gmd:resourceConstraints>
            <gmd:MD_Constraints>
                <gmd:useLimitation>
                    <gco:CharacterString>License</gco:CharacterString>
                </gmd:useLimitation>
            </gmd:MD_Constraints>
        </gmd:resourceConstraints>
        <gmd:resourceConstraints>
            <gmd:MD_LegalConstraints>
                <gmd:accessConstraints>
                    <gmd:MD_RestrictionCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#MD_RestrictionCode" codeListValue="copyright"/>
                </gmd:accessConstraints>
                <gmd:useConstraints>
                    <gmd:MD_RestrictionCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#MD_RestrictionCode" codeListValue="license"/>
                </gmd:useConstraints>
            </gmd:MD_LegalConstraints>
        </gmd:resourceConstraints>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/aggregationInfo (revision of an existing resource)

XML encoding

         <gmd:aggregationInfo xmlns:srv="http://www.isotc211.org/2005/srv">
            <gmd:MD_AggregateInformation>
               <gmd:aggregateDataSetIdentifier>
                  <gmd:MD_Identifier>
                     <gmd:code>
                        <gco:CharacterString>1ca2125d-81db-488f-97ce-c4a0910b52c9</gco:CharacterString>
                     </gmd:code>
                  </gmd:MD_Identifier>
               </gmd:aggregateDataSetIdentifier>
               <gmd:associationType>
                  <gmd:DS_AssociationTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#DS_AssociationTypeCode" 
                                              codeListValue="revisionOf"/>
               </gmd:associationType>
            </gmd:MD_AggregateInformation>
         </gmd:aggregationInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.2.7 p45 Optional
ISO19139

Status in EEA metadata

Conditional: Only for datasets that are a revision of datasets referenced in the EEA SDI Catalogue

Important notes

  • This metadata element allows the logical link between a dataset metadata and the metadata of a dataset with which the new resource is associated. While there are several association types, we are only going to consider the association type "RevisionOf" as defined in the codelist DS_AssociationTypeCode of ISO 19115-1. RevisionOf association describes the association of a resource with another resource of which the former is a revision.
  • This element should be added whenever the associated resource is available in the SDI.
  • While this association (with the corresponding UUID of the metadata) will be included by the SDI Team, it is recommended that during the registration the data steward points out to the dataset in the SDI which this resource is a revision of (this shall be naturally reflected with the dataset identifier "revision" component).
  • The example above is not included in the metadata file used in these guidelines.
  • This metadata element requires editing by the SDI Team.

MD_Metadata/identificationInfo/*/spatialRepresentationType

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
        <gmd:spatialRepresentationType>
            <gmd:MD_SpatialRepresentationTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_SpatialRepresentationTypeCode" 
                                                  codeListValue="vector"/>
         </gmd:spatialRepresentationType>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.5.26 p102) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The spatial representation type must have one of these values (subset of corresponding ISO code list):
    • vector
    • grid
    • textTable
    • tin
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/spatialResolution

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
     <gmd:spatialResolution>
            <gmd:MD_Resolution>
               <gmd:equivalentScale>
                  <gmd:MD_RepresentativeFraction>
                     <gmd:denominator>
                        <gco:Integer>100000</gco:Integer>
                     </gmd:denominator>
                  </gmd:MD_RepresentativeFraction>
               </gmd:equivalentScale>
            </gmd:MD_Resolution>
         </gmd:spatialResolution>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.7.2 p44 Conditional
ISO19115:2003 Sec. B.2.2.1 p40 Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • Although it is possible to specify several spatial resolutions, we require to have only one (smallest scale or coarsest resolution).
  • The example refers to a spatial resolution expressed as a scale of 1:100000, to express a spatial resolution as a ground sampling distance of 100m, use the following example (unit expressed in ML_gmxUom.xml#m):
    <gmd:spatialResolution>
    <gmd:MD_Resolution>
        <gmd:distance>
            <gco:Distance uom="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/uom/ML_gmxUom.xml#m">100</gco:Distance>
        </gmd:distance>
    </gmd:MD_Resolution>
</gmd:spatialResolution>
  • In order to add some specific comments or description to the spatial resolution field, it is suggested to use the field Supplemental Information under "Identification Info" to add this information (as ISO 19115-3, which has a specific element for this, has not yet been implemented in the EEA Catalogue):
    <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
<gmd:supplementalInformation>
      <gco:CharacterString>Spatial Resolution information: The Minimum Mapping Width is 100 m</gco:CharacterString>
</gmd:supplementalInformation>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/language

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
<gmd:language>
            <gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="eng"/>
         </gmd:language>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.2.7 p26 Conditional
ISO19115:2003 Sec. B.2.2.1 p40 Mandatory
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This element is required under ISO even if the resource does not include any textual information.
  • This metadata element does not require any editing.

MD_Metadata/identificationInfo/*/topicCategory

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
        <gmd:topicCategory>
            <gmd:MD_TopicCategoryCode>environment</gmd:MD_TopicCategoryCode>
        </gmd:topicCategory>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.3.1 p27 Mandatory
ISO19115:2003 Sec. B.2.2.1 p40 (links to Sec. B.5.27 p102) Mandatory
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The current example indicates that the dataset belongs to one topic: "environment". There may be more than one topic category (there must be one per topicCategory metadata element).
  • The topic categories shall be taken in the following list (copied from Sec.B.5.27), which is also available in the EEA metadata editor. This is a high-level classification scheme defined in Part D 2 of the INSPIRE Metadata Regulation 1205/2008/EC and are derived directly from the topic categories defined in MD_TopicCategoryCode (B.5.27) of ISO 19115:
    • farming
    • biota
    • boundaries
    • climatologyMeteorologyAtmosphere
    • economy
    • elevation
    • environment
    • geoscientificInformation
    • health
    • imageryBaseMapsEarthCover
    • intelligenceMilitary
    • inlandWaters
    • location
    • oceans
    • planningCadastre
    • society
    • structure
    • transportation
    • utilitiesCommunication
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/extent (spatial)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
         <gmd:extent>
            <gmd:EX_Extent>
               <gmd:geographicElement>
                  <gmd:EX_GeographicBoundingBox>
                     <gmd:westBoundLongitude>
                        <gco:Decimal>-64.5</gco:Decimal>
                     </gmd:westBoundLongitude>
                     <gmd:eastBoundLongitude>
                        <gco:Decimal>78.5</gco:Decimal>
                     </gmd:eastBoundLongitude>
                     <gmd:southBoundLatitude>
                        <gco:Decimal>-50</gco:Decimal>
                     </gmd:southBoundLatitude>
                     <gmd:northBoundLatitude>
                        <gco:Decimal>84.5</gco:Decimal>
                     </gmd:northBoundLatitude>
                  </gmd:EX_GeographicBoundingBox>
               </gmd:geographicElement>
            </gmd:EX_Extent>
         </gmd:extent>
                      <!-- [.....................] -->
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.5.1 p35 Mandatory
ISO19115:2003 Sec. B.2.2.1 p42 (links to Sec. B.3.1.2 p82 modified in ISO 19115:2003/Cor.1:2006) Mandatory
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This is the actual geographic extent of the resource, represented by the minimum rectangle which encompasses all features in the dataset.
  • Coordinates are expressed in decimal degrees with positive east and north, with a precision of at least 2 decimals.
  • When rounding up decimal values, make sure to do it in such a way that the bounding box gets larger and not smaller:
    • westBoundLongitude = -33.90432 rounded up to two decimals becomes westBoundLongitude = -33.91
    • westBoundLongitude = 3.4262 rounded up to two decimals becomes westBoundLongitude = 3.42
    • eastBoundLongitude = 38.1471 rounded up to two decimals becomes eastBoundLongitude = 38.15
    • eastBoundLongitude = -1.2156 rounded up to two decimals becomes eastBoundLongitude = -1.21
    • same principle apply by analogy for north and south latitudes.
  • The coordinates of the bounding boxes shall be expressed in any geodetic coordinate reference system with the Greenwich Prime Meridian.
  • For datasets including overseas territories, it is advised to split the overall geographic extend into several bounding boxes.
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/extent (temporal)

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
        <gmd:extent>
            <gmd:EX_Extent>
               <gmd:geographicElement>
                  <gmd:EX_GeographicDescription/>
               </gmd:geographicElement>
               <gmd:temporalElement>
                  <gmd:EX_TemporalExtent>
                     <gmd:extent>
                        <gml:TimePeriod gml:id="d94721e513a1050910">
                           <gml:beginPosition>2016-01-01</gml:beginPosition>
                           <gml:endPosition>2017-03-15</gml:endPosition>
                        </gml:TimePeriod>
                     </gmd:extent>
                  </gmd:EX_TemporalExtent>
               </gmd:temporalElement>
            </gmd:EX_Extent>
         </gmd:extent>
    <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.6.1 p37 Conditional (at least one of temporal extent, date of creation, publication or last revision)
ISO19115:2003 Sec. B.2.2.1 p42 (links to Sec. B.3.1.3 p84) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • This element describes the time period covered by the content of the dataset
  • When the dataset refers to a (specific) full year, Begin Date should be set to 1st January of that year and End Date should be set to 31st December of that year.
  • In case a time should be specified in addition to a date, time should be expressed as GMT and the following format should be used: 1977-03-10T11:45:30
  • For time series with today as end date, the <gml:TimePeriod>...</gml:TimePeriod> element should contain:
            <gml:begin>
          <gml:TimeInstant gml:id="tstart">
            <gml:timePosition>2011-04-01T00:00:00</gml:timePosition>
          </gml:TimeInstant>
        </gml:begin>
        <gml:end>
          <gml:TimeInstant gml:id="tend">
            <gml:timePosition indeterminatePosition="now"/>
          </gml:TimeInstant>
        </gml:end>
  • This metadata element requires editing.

MD_Metadata/identificationInfo/*/supplementalInformation

XML encoding

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
                      <!-- [.....................] -->
                <gmd:supplementalInformation>
                       <gco:CharacterString>Spatial Resolution information: The Minimum Mapping Width is 100 m</gco:CharacterString>
                </gmd:supplementalInformation>
         <gmd:MD_DataIdentification>
<gmd:identificationInfo>

References

INSPIRE Metadata TG v1.3 Annex B.2 p96 Optional
ISO19115:2003 Sec. B.2.2.1 p42 Optional
ISO19139

Status in EEA metadata

Optional

Important notes

  • This element is used in the EEA metadata profile to include additional information on the spatial resolution of the datasets (e.g. minimum mapping width) as ISO 19115:2003 does not allow to include additional information linked to the spatial resolution element.
  • This is only optional and will be included by the SDI Team. This is not included in the XML provided as example in this website.
  • This metadata element requires editing by the SDI Team.

MD_Metadata/distributionInfo/*/distributionFormat

XML encoding

<gmd:distributionInfo>
    <gmd:MD_Distribution>
     <gmd:distributionFormat>
            <gmd:MD_Format>
               <gmd:name>
                  <gco:CharacterString>SHP</gco:CharacterString>
               </gmd:name>
               <gmd:version>
                  <gco:CharacterString>1</gco:CharacterString>
               </gmd:version>
            </gmd:MD_Format>
         </gmd:distributionFormat>
         <gmd:distributionFormat>
            <gmd:MD_Format>
               <gmd:name>
                  <gco:CharacterString>SQLite</gco:CharacterString>
               </gmd:name>
               <gmd:version>
                  <gco:CharacterString>1</gco:CharacterString>
               </gmd:version>
            </gmd:MD_Format>
         </gmd:distributionFormat>
                      <!-- [.....................] -->
    </gmd:MD_Distribution>
</gmd:distributionInfo>

References

INSPIRE Metadata TG v1.3
ISO19115:2003 Sec. B.2.10.1 p73 (links to Sec. B.2.10.4 p75) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • The format in which the resource is stored and distributed should be expressed using a code from this list which is derived from the codes used by the libraries GDAL and OGR (if a format is missing, contact SDI Team):
  • Raster
    AAIGrid Arc/Info ASCII Grid
    AIG Arc/Info Binary Grid (.adf)
    CEOS CEOS format (used by some satellite image providers)
    DIMAP DIMAP format (used by some satellite image providers)
    ECW ERMapper Compressed Wavelets (.ecw)
    EHdr ESRI .hdr Labelled
    ENVI ENVI .hdr Labelled Raster
    GRASS GRASS Rasters
    GTiff TIFF / BigTIFF / GeoTIFF (if no georeferencing information is available in the TIFF file itself, an ESRI world file [.tfw] must be present)
    HDF Hierarchical Data Format Release (specify the version number [4 or 5] in the metadata element version)
    HFA Erdas Imagine (.img)
    LAN Erdas 7.x .LAN and .GIS
    MrSID Multi-resolution Seamless Image Database
    netCDF NetCDF
    XYZ ASCII Gridded XYZ
  • Vector
    AVCBin Arc/Info Binary Coverage
    AVCE00 Arc/Info .E00 (ASCII) Coverage
    CSV Comma Separated Value (.csv)
    FGeo ESRI File GeoDatabase
    GML Geography Markup Language
    GRASS GRASS vector
    KML Keyhole Markup Language
    MIF !MapInfo File
    PGeo ESRI Personal GeoDatabase
    SHP ESRI Shapefile
    Postgis Postgresql/Postgis database
    Spatialite SQLite/SpatiaLite database
  • We remind that use of unpublished formats should be avoided as much as possible to ensure the best possible interoperability.
  • When several versions of a format exist, the version number shall be specified.
  • This metadata element requires editing.

MD_Metadata/distributionInfo/*/transferOptions

XML encoding

<gmd:distributionInfo>
    <gmd:MD_Distribution>
                      <!-- [.....................] -->
         <gmd:transferOptions>
            <gmd:MD_DigitalTransferOptions>
               <gmd:onLine>
                  <gmd:CI_OnlineResource>
                     <gmd:linkage>
                        <gmd:URL>https://www.eea.europa.eu/data-and-maps/data/nationally-designated-areas-national-cdda-12</gmd:URL>
                     </gmd:linkage>
                     <gmd:protocol>
                        <gco:CharacterString>WWW:LINK-1.0-http--link</gco:CharacterString>
                     </gmd:protocol>
                     <gmd:function>
                        <gmd:CI_OnLineFunctionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode" 
                                                   codeListValue="download"/>
                     </gmd:function>
                  </gmd:CI_OnlineResource>
               </gmd:onLine>
               <gmd:onLine>
                  <gmd:CI_OnlineResource>
                     <gmd:linkage>
                        <gmd:URL>/continental/europe/natural_areas/cdda/eea_v_3035_100_k_cdda-poly-public_2017_rev15-0/CDDAPolygon/CDDA_v15.shp</gmd:URL>
                     </gmd:linkage>
                     <gmd:protocol>
                        <gco:CharacterString>EEA:FILEPATH</gco:CharacterString>
                     </gmd:protocol>
                     <gmd:name>
                        <gco:CharacterString>CDDAPolygon</gco:CharacterString>
                     </gmd:name>
                     <gmd:description gco:nilReason="missing">
                        <gco:CharacterString/>
                     </gmd:description>
                  </gmd:CI_OnlineResource>
               </gmd:onLine>
               <gmd:onLine>
                  <gmd:CI_OnlineResource>
                     <gmd:linkage>
                        <gmd:URL>/continental/europe/natural_areas/cdda/eea_v_3035_100_k_cdda-poly-public_2017_rev15-0/CDDASqlite/CDDA_v15.sqlite</gmd:URL>
                     </gmd:linkage>
                     <gmd:protocol>
                        <gco:CharacterString>EEA:FILEPATH</gco:CharacterString>
                     </gmd:protocol>
                     <gmd:name>
                        <gco:CharacterString>CDDASqlite</gco:CharacterString>
                     </gmd:name>
                     <gmd:description gco:nilReason="missing">
                        <gco:CharacterString/>
                     </gmd:description>
                  </gmd:CI_OnlineResource>
               </gmd:onLine>
               <gmd:onLine>
                  <gmd:CI_OnlineResource>
                     <gmd:linkage>
                        <gmd:URL>http://bio.discomap.eea.europa.eu/arcgis/services/ProtectedSites/CDDA_Dyna_WM/MapServer/WMSServer?request=GetCapabilities&amp;service=WMS</gmd:URL>
                     </gmd:linkage>
                     <gmd:protocol>
                        <gco:CharacterString>OGC:WMS</gco:CharacterString>
                     </gmd:protocol>
                     <gmd:name gco:nilReason="missing">
                        <gco:CharacterString/>
                     </gmd:name>
                     <gmd:description gco:nilReason="missing">
                        <gco:CharacterString/>
                     </gmd:description>
                     <gmd:function>
                        <gmd:CI_OnLineFunctionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode" 
                                                   codeListValue="information"/>
                     </gmd:function>
                  </gmd:CI_OnlineResource>
               </gmd:onLine>
               <gmd:onLine>
                  <gmd:CI_OnlineResource>
                     <gmd:linkage>
                        <gmd:URL>http://bio.discomap.eea.europa.eu/arcgis/rest/services/ProtectedSites/CDDA_Dyna_WM/MapServer</gmd:URL>
                     </gmd:linkage>
                     <gmd:protocol>
                        <gco:CharacterString>ESRI:REST</gco:CharacterString>
                     </gmd:protocol>
                     <gmd:name gco:nilReason="missing">
                        <gco:CharacterString/>
                     </gmd:name>
                     <gmd:description gco:nilReason="missing">
                        <gco:CharacterString/>
                     </gmd:description>
                     <gmd:function>
                        <gmd:CI_OnLineFunctionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode" 
                                                   codeListValue="information"/>
                     </gmd:function>
                  </gmd:CI_OnlineResource>
               </gmd:onLine>
            </gmd:MD_DigitalTransferOptions>
         </gmd:transferOptions>
    </gmd:MD_Distribution>
</gmd:distributionInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.2.4 p21 Conditional
ISO19115:2003 Sec. B.2.10.1 p73 (links to Sec. B.2.10.2 p74) Optional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • If the dataset has already been published, the link to the resource on the EEA website shall be provided in the linkage element with WWW:LINK-1.0-http--link as related protocol.
  • The (internal) filepath which needs to be used in order to access the resource shall be provided in the linkage element with EEA:FILEPATH as related protocol.
  • Link to the web map service: When available, please add the link to the WMS GetCapabilities using “OGC:WMS” protocol or to the corresponding layer when there are several in the same service.
  • Link to rest web services: When available, please add the link to the ESRI Rest service using the “ESRI:REST” protocol.
  • This metadata element requires editing.

MD_Metadata/dataQualityInfo/*/lineage

XML encoding

<gmd:dataQualityInfo>
      <gmd:DQ_DataQuality>
         <gmd:scope>
            <gmd:DQ_Scope>
               <gmd:level>
                  <gmd:MD_ScopeCode codeListValue="dataset" 
                                    codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_ScopeCode"/>
               </gmd:level>
            </gmd:DQ_Scope>
         </gmd:scope>
         <gmd:lineage>
            <gmd:LI_Lineage>
               <gmd:statement>
                  <gco:CharacterString>Production process is explained in the document CDDA_version_15.pdf available together with the data set.</gco:CharacterString>
               </gmd:statement>
            </gmd:LI_Lineage>
         </gmd:lineage>
      </gmd:DQ_DataQuality>
</gmd:dataQualityInfo>

References

INSPIRE Metadata TG v1.3 Sec. 2.7.1 p42 Mandatory
ISO19115:2003 Sec. B.2.4.2 p 48 Conditional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • All relevant steps taken in order to create the datasets shall be described here (process history) while addressing version specificities where suitable.
  • If too long, the statement can reference an already existing document made available together with the dataset.
  • Source datasets referred to in the lineage statement, and available in the SDI, should be included in the metadata whenever possible, see here.
  • The overall quality of the dataset should also be included in this metadata element.
  • This metadata element requires editing.

MD_Metadata/dataQualityInfo/*/lineage/*/source

XML encoding

  <gmd:DQ_DataQuality>
      <gmd:lineage>
         <gmd:LI_Lineage>
            <gmd:statement>
                  <!-- [.....................] -->
            </gmd:statement>
            <gmd:source uuidref="8c2a3ded-9ccb-472d-99d2-30f11107b10c">
               <gmd:LI_Source/>
            </gmd:source>
         </gmd:LI_Lineage>
      </gmd:lineage>
  </gmd:DQ_DataQuality>

References

INSPIRE Metadata TG v1.3 Annex B.2 p96 Optional
ISO19115:2003 Sec. B.2.4.2.1 p48 Conditional
ISO19139

Status in EEA metadata

Conditional: Only for datasets which dataset sources are referenced in the EEA SDI Catalogue

Important notes

  • This metadata element allows the logical link between a dataset metadata and the metadata of the corresponding source dataset(s).
  • When the source dataset(s) used to generate the current dataset are referenced in the EEA catalogue, their UUIDs should be listed as shown in the example above.
  • There must be as many <gmd:source>...</gmd:source> elements as there are of source datasets referenced (i.e. [0..n])
  • This value will be edited by the SDI Team. The data steward should however inform the SDI Team of the existence of a dataset source in the SDI to which the new metadata should be linked to.
  • The example above is not included in the metadata file used in these guidelines.
  • This metadata element requires editing by the SDI Team.

MD_Metadata/dataQualityInfo/*/DQ_ConformanceResult (INSPIRE IR conformity statement)

XML encoding

         <gmd:report xmlns:gn="http://www.fao.org/geonetwork" 
                     xmlns:gmx="http://www.isotc211.org/2005/gmx" 
                     xmlns:srv="http://www.isotc211.org/2005/srv">
            <gmd:DQ_DomainConsistency>
               <gmd:result>
                  <gmd:DQ_ConformanceResult>
                     <gmd:specification>
                        <gmd:CI_Citation>
                           <gmd:title>
                              <gco:CharacterString>Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services</gco:CharacterString>
                           </gmd:title>
                           <gmd:date>
                              <gmd:CI_Date>
                                 <gmd:date>
                                    <gco:Date>2010-12-08</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"/>
                                 </gmd:dateType>
                              </gmd:CI_Date>
                           </gmd:date>
                        </gmd:CI_Citation>
                     </gmd:specification>
                     <gmd:explanation>
                        <gco:CharacterString>See the referenced specification</gco:CharacterString>
                     </gmd:explanation>
                     <gmd:pass gco:nilReason="unknown"/>
                  </gmd:DQ_ConformanceResult>
               </gmd:result>
            </gmd:DQ_DomainConsistency>
         </gmd:report>

References

INSPIRE Metadata TG v1.3 Sec. 2.8 p48 Mandatory
ISO19115:2003 Sec. B.2.4 p 48 Conditional
ISO19139

Status in EEA metadata

Mandatory

Important notes

  • Any dataset published in the EEA catalogue has to include at least a conformity statement with respect to the INSPIRE IR as regards interoperability of spatial datasets and services. The template provides already by default the values with whom to fill in the corresponding metadata elements: title, date, explanation:

The title of the specification should be: "COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services"
The date corresponding to this specification is: "2010-12-08" with dateType "publication"
The explanation by default is: See the referenced specification

  • Depending on whether the dataset has been evaluated or not, and if evaluated, whether is conformant or not to the INSPIRE IR, the element <gmd:pass> will have to be edited accordingly. The only possible values are:

true if conformant
false if non conformant
unknown if not evaluated (by default in the EEA template)

  • If a dataset is produced or transformed according to an external specification that includes specific quality assurance procedures, the conformity with this specification should be documented using also this metadata element (although this is only optional in the EEA metadata profile).
  • The example above is not included in the metadata file used in these guidelines.
  • This metadata element requires editing.

Updated by Jose Rubio over 1 year ago · 6 revisions

Go to top

Taskman Changelog | Systems Status | Helpdesk | Data Protection Notice