Public documentation

h1. EEA Metadata Profile v2.1, November 2020

{{>toc}}

h2. 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 data set and service metadata based on ISO/TS 19139:2007* ":https://inspire.ec.europa.eu/file/1705/download?token=iSTwpRWd which is the implementation specification for defining metadata for INSPIRE data sets 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). The 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:"eea_v_3035_100_k_cdda-poly_p_2018-2019_v17_r00.xml" which is compliant with the EEA metadata profile v2.0. This metadata refers to a data set containing the *Nationally designated areas (CDDA) polygons for public access - version 17, Jun. 2019* . 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":https://taskman.eionet.europa.eu/attachments/80866 is also available to facilitate the compliance with the EEA metadata profile. The wiki page "EEA SDI editor User Guide":https://taskman.eionet.europa.eu/projects/public-docs/wiki/SDI_editor_guidance 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, and how to validate it against the profile and against the INSPIRE Technical Guidance indicated above.  

Please note that not all the metadata elements in the profile are supposed to be directly edited by the data stewards - as indicated in the corresponding section, a few are already included in the EEA Template, others 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.1) has been made public in November 2020. In case you have any question, doubt or suggestion, please contact the EEA SDI team on *sdi@eea.europa.eu*.

h3. 1.1 EEA metadata profile version control

| *EEA metadata profile version* | *Publication date* | *Comments* |

|"v2.0":https://taskman.eionet.europa.eu/projects/public-docs/wiki/Cataloguemetadata_guidelines/141| December 2019| Significant changes to ensure alignment with the INSPIRE MD TG 2.0|

|v2.1| November 2020| Only minor additions (date of next update, EEA topic keywords)|

h2. 2. Analysis of EEA metadata profile elements

h2. MD_Metadata/fileIdentifier

h4. XML encoding

<pre>

<code class="xml">

 <gmd:fileIdentifier>

      <gco:CharacterString>50dd4172-ba90-4d6d-90ef-88f5d1d84795</gco:CharacterString>

  </gmd:fileIdentifier>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|||

|ISO19115:2003|B.2.1 p38|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** The file identifier in the EEA SDI will be created using Universal Unique Identifiers (UUIDs). 

** 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._

h2. MD_Metadata/language

h4. XML encoding

<pre>

<code class="xml">

    <gmd:language>

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

  </gmd:language>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0| C.2.27 p119|Mandatory|

|ISO19115:2003|B.2.1 p38|Conditional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** Metadata element used to document the language used in the metadata. 

** All metadata records shall be written in English (alpha-3 code "eng" in ISO639-2/B) therefore this element does not need to be edited.

** _This metadata element does not require any editing._

h2. MD_Metadata/characterSet

h4. XML encoding

<pre>

<code class="xml">

 <gmd:characterSet>

      <gmd:MD_CharacterSetCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_CharacterSetCode"

                               codeListValue="utf8"/>

  </gmd:characterSet>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|||

|ISO19115:2003|B.2.1 p38|Conditional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element describes the character coding standard used for the metadata set. 

** The character coding standard used for the metadata set shall be _utf8_ (8-bit variable size Universal Coded Character Set -UCS- transfer format specificed in ISO 106406:2014)

** _This metadata element does not require any editing._

h2. MD_Metadata/parentIdentifier

h4. XML encoding

<pre>

<code class="xml">

<gmd:parentIdentifier>

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

   </gmd:parentIdentifier>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|||

|ISO19115:2003|B.2.1 p38|Conditional|

h4. Status in EEA metadata

  *Conditional*: only for those data sets which belong to a data set series or are a subset from another data set existing in the SDI

h4. Important notes

** This metadata element allows the logical link between a data set metadata and the metadata of a data set of which the former is a subset (e.g. data sets within a series, public versions which are subsets of internal versions without restricted data). 

** A data set series is defined as a collection of data sets 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 data set series or parent resource to which the new metadata should be linked to. 

** The XML snippet provided as an example does not belong to the metadata used as an example in this profile. 

** _This metadata element requires *editing by the SDI Team*._

h2. MD_Metadata/hierarchyLevel

h4. XML encoding

<pre>

<code class="xml">

<gmd:hierarchyLevel>

      <gmd:MD_ScopeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_ScopeCode"

                        codeListValue="dataset"/>

  </gmd:hierarchyLevel>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.3 p103|Mandatory|

|ISO19115:2003|B.2.1 p38|Conditional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element refers to the scope to which the metadata applies, which values are defined by the code list MD_ScopeCode (e.g. dataset, series, service, feature, attribute, nonGeographicDataset - see ISO19115:2003 Sec. B5.25 p101)

** We are so far only considering metadata for data sets and series. By default the value shall be "dataset", since the series metadata are produced by the SDI Team, in collaboration with the thematic experts. 

** _This metadata element does not require any editing._

h2. MD_Metadata/contact

h4. XML encoding

<pre>

<code class="xml">

<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/iso/19139/resources/gmxCodelists.xml#CI_RoleCode"

                             codeListValue="pointOfContact"/>

         </gmd:role>

      </gmd:CI_ResponsibleParty>

  </gmd:contact>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0| C.2.25 p118|Mandatory|

|ISO19115:2003|B.2.1 p38 (ResponsibleParty data type in B.3.2.1 p85)|Mandatory|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This element refers to the party responsible for the metadata information.

** The default value for all metadata published in the SDI (with the unlikely exception of metadata not created or modified by EEA but still published in the SDI) will be the contact information of EEA SDI Team, to be provided as indicated above in the XML snippet. There could be more than one metadata point of contact but they are typically not expected.

** _This metadata element does not require any editing._

h2. MD_Metadata/dateStamp

h4. XML encoding

<pre>

<code class="xml">

  <gmd:dateStamp>

      <gco:DateTime>2019-11-27T12:53:17</gco:DateTime>

  </gmd:dateStamp>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.26 p119|Mandatory|

|ISO19115:2003|B.2.1 p38 (Date type in B.4.2 p91)|Mandatory|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This element refers to date that the metadata was created.

** 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._

h2. MD_Metadata/metadataStandardName

h4. XML encoding

<pre>

<code class="xml">

<gmd:metadataStandardName>

      <gco:CharacterString>ISO 19115/19139</gco:CharacterString>

  </gmd:metadataStandardName>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|||

|ISO19115:2003|B.2.1 p38|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element provides the name of the metadata standard (including profile name) used. 

** This metadata element is generated automatically by Geonetwork and any modification will be overwritten by GeoNetwork.

** _This metadata element does not require any editing._

h2. MD_Metadata/metadataStandardVersion

h4. XML encoding

<pre>

<code class="xml">

<gmd:metadataStandardVersion>

      <gco:CharacterString>1.0</gco:CharacterString>

  </gmd:metadataStandardVersion>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|||

|ISO19115:2003|B.2.1 p38 (modified in ISO 19115:2003/Cor.1:2006)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element provides the version (or profile) of the metadata standard used. 

** This metadata element is generated automatically by GeoNetwork and any modification will be overwritten by GeoNetwork.

** _This metadata element does not require any editing._

h2. MD_Metadata/referenceSystemInfo/*/referenceSystemIdentifier

h4. XML encoding

<pre>

<code class="xml">

    <gmd:referenceSystemInfo>

      <gmd:MD_ReferenceSystem>

         <gmd:referenceSystemIdentifier>

            <gmd:RS_Identifier>

               <gmd:code>

                  <gmx:Anchor xlink:href="http://www.opengis.net/def/crs/EPSG/0/3035">EPSG:3035</gmx:Anchor>

               </gmd:code>

            </gmd:RS_Identifier>

         </gmd:referenceSystemIdentifier>

      </gmd:MD_ReferenceSystem>

  </gmd:referenceSystemInfo>

  </code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.3.1 p120|Mandatory|

|ISO19115:2003|B.2.7.3 p65 (modified in ISO 19115:2003/Cor.1:2006)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element describes the Coordinate Reference System(s) used in the data set. 

** The Coordinate Reference System shall be referred to with its EPSG - European Petroleum Survey Group -  code. See http://www.epsg-registry.org/ for more information on the EPSG codes and their values. 

** INSPIRE requires that the EPSG codes are encoded using URIs as defined in the "Annex D.5 of the INSPIRE metadata TG 2.0":https://inspire.ec.europa.eu/file/1705/download?token=iSTwpRWd.

** The SDI editor provides a list of the most common Coordinate Reference Systems to facilitate the encoding of this element. 

** In this example, the EPSG code used is _3035_ (http://www.opengis.net/def/crs/EPSG/0/3035) which corresponds to a Lambert Azimuthal Equal Area 52N 10E projection based on ETRS89 datum.

** In the unlikely event 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.

** _This metadata element *requires editing.*_

h2. MD_Metadata/identificationInfo/*/citation/*/title

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

      <gmd:MD_DataIdentification>

         <gmd:citation>

            <gmd:CI_Citation>

               <gmd:title>

                  <gco:CharacterString>Nationally designated areas (CDDA) polygons for public access - version 17, Jun. 2019</gco:CharacterString>

               </gmd:title>

                                     <!-- [.....................] -->

			</gmd:CI_Citation>

		</gmd:citation>

	</gmd:MD_DataIdentification>

</gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.1 p102|Mandatory|

|ISO19115:2003|B.2.2.1 p40 (Citation data type in B.3.2 p85)|Mandatory|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element includes the name by which the cited resource is known. 

** 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 data sets which have regular updates, the version number and the data set creation date shall be added at the end of the title. The public or internal nature of the data set should also be reflected in the title. More details about the recommended title convention [[Naming_conventions|here]].   

** _This metadata element *requires editing.*_

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

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

		<gmd:citation>

			<gmd:CI_Citation>

                                     <!-- [.....................] -->

				<gmd:date>

                  <gmd:CI_Date>

                     <gmd:date>

                        <gco:Date>2019-06-04</gco:Date>

                     </gmd:date>

                     <gmd:dateType>

                        <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_DateTypeCode"

                                             codeListValue="creation"/>

                     </gmd:dateType>

                  </gmd:CI_Date>

               </gmd:date>

                                     <!-- [.....................] -->

			</gmd:CI_Citation>

		</gmd:citation>

	</gmd:MD_DataIdentification>

</gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.16 p111|Conditional (at least temporal extent or one date of creation, publication or last revision shall be provided)|

|ISO19115:2003|B.2.2.1 p40 (Date data type in B.3.2.4 p88)|Conditional (but at least one of date of creation, publication or last revision shall be provided)|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element shall include the reference date of the creation of the related data set. 

** The date of creation shall be equal or prior to the date of publication for data sets published on the EEA website.

** For data sets 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 data set (metadata element https://taskman.eionet.europa.eu/projects/public-docs/wiki/EEA_Metadata_Profile_v20#MD_MetadatadateStamp). If no suitable creation date can be found, please contact the SDI Team. 

** _This metadata element *requires editing.*_

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

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

		<gmd:citation>

			<gmd:CI_Citation>

                                     <!-- [.....................] -->

				    <gmd:date>

                  <gmd:CI_Date>

                     <gmd:date>

                        <gco:Date>2019-06-04</gco:Date>

                     </gmd:date>

                     <gmd:dateType>

                        <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_DateTypeCode"

                                             codeListValue="publication"/>

                     </gmd:dateType>

                  </gmd:CI_Date>

               </gmd:date>

                                     <!-- [.....................] -->

			</gmd:CI_Citation>

		</gmd:citation>

	</gmd:MD_DataIdentification>

</gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.14 p110|Conditional (at least temporal extent or one date of creation, publication or last revision shall be provided)|

|ISO19115:2003|B.2.2.1 p40 (Date data type in B.3.2.4 p88)|Conditional (but at least one of date of creation, publication or last revision shall be provided)|

h4. Status in EEA metadata

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

h4. Important notes

* This metadata element shall include the reference date of the publication of the related data set.

* The date of publication shall be present at least for data sets which are published by the EEA. For internal or restricted data sets, it is expected that this element is not filled in.

* For data sets which are not published on the EEA website (e.g. Copernicus), please contact the SDI team.

* This metadata element requires editing or deletion.

h2. MD_Metadata/identificationInfo/*/citation/*/date (next update)

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

		<gmd:citation>

			<gmd:CI_Citation>

                                     <!-- [.....................] -->

				  <gmd:date>

                    <gmd:CI_Date>

                       <gmd:date>

                       <gco:Date>2026-01-01</gco:Date>

                        </gmd:date>

                        <gmd:dateType>

                     <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_DateTypeCode" codeListValue="nextUpdate"/>

                  </gmd:dateType>

              </gmd:CI_Date>

            </gmd:date>

                                     <!-- [.....................] -->

			</gmd:CI_Citation>

		</gmd:citation>

	</gmd:MD_DataIdentification>

</gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|||

|ISO19115-3:2018||Conditional (but at least one of date of creation, publication or last revision shall be provided)|

h4. Status in EEA metadata

  *Optional*: relevant information to be added for those datasets which are regularly updated or it is known when a next update will be made available 

h4. Important notes

** This metadata element shall include the reference date when the resource will be next updated. 

** It is an element not included in ISO 19115:2003 but in its update ISO 19115-3:2018.

** This metadata element is *NOT* included in the example provided

** _This metadata element *requires editing or deletion.*_

h2. MD_Metadata/identificationInfo/*/citation/*/edition

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

		<gmd:citation>

			<gmd:CI_Citation>

                                     <!-- [.....................] -->

			    <gmd:edition>

                  <gco:CharacterString>17.00</gco:CharacterString>

               </gmd:edition>

                                     <!-- [.....................] -->

			</gmd:CI_Citation>

		</gmd:citation>

	</gmd:MD_DataIdentification>

</gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|||

|ISO19115:2003|B.2.2.1 p40 (Citation data type in B.3.2 p85)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This element includes the version of the cited resource. In the EEA profile, this covers the version of the data set and its sub-version or revision if applicable.  

** The version and revision numbers of the data set should be consistent with this element. Version and revision should be encoded with two digits each, separated by a point (vv.rr).

** _This metadata element *requires editing*_

h2. MD_Metadata/identificationInfo/*/citation/*/identifier

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

		<gmd:citation>

			<gmd:CI_Citation>

                                     <!-- [.....................] -->

				 <gmd:identifier>

                  <gmd:MD_Identifier>

                     <gmd:code>

                        <gco:CharacterString>eea_v_3035_100_k_cdda-poly_p_2018-2019_v17_r00</gco:CharacterString>

                     </gmd:code>

                  </gmd:MD_Identifier>

               </gmd:identifier>

			</gmd:CI_Citation>

		</gmd:citation>

	</gmd:MD_DataIdentification>

</gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C2.5 p104|Mandatory|

|ISO19115:2003|.2.2.1 p40 (Identifier data type in B.2.7.3 p65)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element shall refer to a value uniquely identifying an object (e.g. dataset, series) within a namespace. 

** This identifier shall be unique and follow [[Naming_conventions|this convention]]. 

** This identifier shall be set to the directory name in which the data set 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.*_

h2. MD_Metadata/identificationInfo/*/abstract

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

                      <!-- [.....................] -->

				<gmd:abstract>

            <gco:CharacterString>The European inventory of Nationally designated areas (CDDA) holds information about designated areas and their designation types, which directly or indirectly create protected areas. The inventory is delivered by the Eionet partnership countries as spatial and tabular information.

The inventory began in 1995 under the CORINE programme of the European Commission. The CDDA is now an agreed annual Eionet core data flow maintained by the European Environment Agency (EEA) with support from the European Topic Centre on Biological Diversity (ETC/BD). The data set is used by the EEA and e.g. the UNEP-WCMC for their main European and global assessments, products and services.

The CDDA is the official source of protected area information from the 39 European countries to the World Database of Protected Areas (WDPA).

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, North 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, Finland, Ireland and Turkey.

Two versions of the data set are provided. The full data set ("CDDA_2019_v01_public") includes the entire geographical coverage including nationally designated areas in overseas entities. The "CDDA_2019_v01_public_EuropeEPSG3035" version includes only continental Europe, i.e. excludes the overseas entities. Both versions are provided in GDB and GPKG formats.</gco:CharacterString>

         </gmd:abstract>

                      <!-- [.....................] -->

	<gmd:MD_DataIdentification>

<gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.2 p102|Mandatory|

|ISO19115:2003|B.2.2.1 p40|Mandatory|

h4. Status in EEA metadata

  *Mandatory*

h4. 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 data set, it is important to indicate as well the main changes on this new version.  

** _This metadata element *requires editing.*_

h2. MD_Metadata/identificationInfo/*/status

h4. XML encoding

<pre>

<code class="xml">

<gmd:status>

<gmd:MD_ProgressCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_ProgressCode" codeListValue="superseded"/>

</gmd:status>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|||

|ISO19115:2003|B.2.2.1 p40 |Optional|

h4. Status in EEA metadata

  *Conditional* - only for obsolete, archived or superseded data sets as well as data sets from completed projects

h4. 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 imported from ISO19115-1:2014):

**** completed: the production of the data set has been completed (this is to be used only for those data sets produced in the context of specific projects)

**** historicalArchive: to be used only for those data sets stored in an offline storage facility (this is unlikely to happen in the context of the EEA SDI)

**** obsolete: only for those data sets which are no longer relevant (only kept for historical purposes)

**** superseded: data set which has been replaced by a new one (this is to be used for data sets replaced by new versions)

** This means that by default, for currently "active" datasets (i.e. the most recent versions) this element is not filled in. 

** _This metadata element *requires editing by SDI Team*_

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

h4. XML encoding

<pre>

<code class="xml">

<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://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_OnLineFunctionCode"

                                                         codeListValue="information"/>

                           </gmd:function>

                        </gmd:CI_OnlineResource>

                     </gmd:onlineResource>

                  </gmd:CI_Contact>

               </gmd:contactInfo>

               <gmd:role>

                  <gmd:CI_RoleCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_RoleCode"

                                   codeListValue="pointOfContact"/>

               </gmd:role>

            </gmd:CI_ResponsibleParty>

         </gmd:pointOfContact>

                      <!-- [.....................] -->

	<gmd:MD_DataIdentification>

<gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.23 p117| Conditional (at least one responsible party is mandatory)|

|ISO19115:2003|B.2.2.1 p40 (ResponsibleParty data type in B.3.2.1 p85)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element provides the identification, and means of communication with, person(s) and organisation(s) that can provide us with knowledge about or acquisition of the data set.  

** The responsible party acting as Point of Contact shall be the EEA (using the public enquiries mailbox) for any data set owned by EEA.

** The responsible party acting as Point of Contact is the organization or company owning the data set 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, avoiding any unnecessary personal data. 

** _This metadata element *requires editing.*_

h2. MD_Metadata/identificationInfo/*/pointOfContact (custodian)

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

                      <!-- [.....................] -->

		  <gmd:pointOfContact>

            <gmd:CI_ResponsibleParty>

               <gmd:individualName gco:nilReason="missing">

                  <gco:CharacterString/>

               </gmd:individualName>

               <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://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_RoleCode"

                                   codeListValue="custodian"/>

               </gmd:role>

            </gmd:CI_ResponsibleParty>

         </gmd:pointOfContact>

                      <!-- [.....................] -->

	<gmd:MD_DataIdentification>

<gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.23 p117|Conditional (at least one responsible party is mandatory)|

|ISO19115:2003|B.2.2.1 p40 (ResponsibleParty data type in B.3.2.1 p85)|Optional|

h4. Status in EEA metadata

  *Conditional*: it shall be required at least for all data sets owned by EEA

h4. Important notes

** This metadata element provides the identification, and means of communication with, person(s) and organisation(s) that accepts accountability and responsibility for the data and ensures appropriate care and maintenance for the resource. 

** This metadata element shall be filled in at least for data sets owned by EEA.

** In case of doubts when the data set 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.*_

h2. MD_Metadata/identificationInfo/*/resourceMaintenance

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

                      <!-- [.....................] -->

		 <gmd:resourceMaintenance>

            <gmd:MD_MaintenanceInformation>

               <gmd:maintenanceAndUpdateFrequency>

                  <gmd:MD_MaintenanceFrequencyCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_MaintenanceFrequencyCode"

                                                   codeListValue="annually"/>

               </gmd:maintenanceAndUpdateFrequency>

            </gmd:MD_MaintenanceInformation>

         </gmd:resourceMaintenance>

                      <!-- [.....................] -->

	<gmd:MD_DataIdentification>

<gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.7.1 p136|Optional|

|ISO19115:2003|B.2.2.1 p40 (MaintenanceInformation data type in B.2.5 p57)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This element refers to the frequency with which changes and additions are made to the data after it is first produced. 

** The metadata element shall take one of these values of the code list "MD_MaintenanceFrequencyCode" (as listed in Sec. B.5.18 p99 of ISO19115:2003):

**** continual

**** daily

**** weekly

**** fortnightly

**** monthly

**** quaterly

**** biannually

**** annually

**** asNeeded

**** irregular

**** notPlanned

**** unknown

** 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*):

<pre>

<code class="xml">

<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>

</code></pre>

** This element can eventually include information about the scope of data to which the maintenance is applied (values ScopeCode) as well as specific requirements for the maintenance, but this is not required in the context of the EEA metadata. 

** _This metadata element *requires editing.*_

h2. MD_Metadata/identificationInfo/*/graphicOverview

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

                      <!-- [.....................] -->

                  <gmd:graphicOverview>

            <gmd:MD_BrowseGraphic>

               <gmd:fileName>

                  <gco:CharacterString>https://sdi.eea.europa.eu/public/catalogue-graphic-overview/50dd4172-ba90-4d6d-90ef-88f5d1d84795.png</gco:CharacterString>

               </gmd:fileName>

            </gmd:MD_BrowseGraphic>

         </gmd:graphicOverview>

                      <!-- [.....................] -->

	</gmd:MD_DataIdentification>

</gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.7.6 p140|Optional|

|ISO19115:2003|B2.2.1 p40 (BrowseGraphic data type in B.2.2.2 p42)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** This metadata element provides an illustration of the data set. 

** The image should be generated in PNG format, shall provide a clear overview of the whole data set 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.*_

h2. MD_Metadata/identificationInfo/*/descriptiveKeywords (EEA topics)

h4. XML encoding

<pre>

<code class="xml">

<gmd:descriptiveKeywords>

   <gmd:MD_Keywords>

    <gmd:keyword>

      <gmx:Anchor xlink:href="http://www.eea.europa.eu/portal_vocabularies/themes/landuse">Land use</gmx:Anchor>

    </gmd:keyword>

     <gmd:keyword>

         <gmx:Anchor xlink:href="http://www.eea.europa.eu/portal_vocabularies/themes/biodiversity">Biodiversity - Ecosystems</gmx:Anchor>

     </gmd:keyword>

     <gmd:type>

         <gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="theme"/>

     </gmd:type>

    <gmd:thesaurusName>

       <gmd:CI_Citation>

          <gmd:title>

             <gmx:Anchor xlink:href="https://www.eea.europa.eu/themes">EEA topics</gmx:Anchor>

          </gmd:title>

          <gmd:date>

             <gmd:CI_Date>

                <gmd:date>

                   <gco:Date>2020-09-24</gco:Date>

                </gmd:date>

                <gmd:dateType>

                     <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication"/>

                 </gmd:dateType>

             </gmd:CI_Date>

          </gmd:date>

         <gmd:identifier>

             <gmd:MD_Identifier>

                    <gmd:code>

                        <gmx:Anchor xlink:href="http://localhost:8080/geonetwork/srv/api/registries/vocabularies/external.theme.eea-topics">geonetwork.thesaurus.external.theme.eea-topics</gmx:Anchor>

                     </gmd:code>

              </gmd:MD_Identifier>

          </gmd:identifier>

       </gmd:CI_Citation>

    </gmd:thesaurusName>

   </gmd:MD_Keywords>

 </gmd:descriptiveKeywords>

<gmd:descriptiveKeywords>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.10 p107 and C.2.11 p108|Mandatory (at least to have one set of keywords)|

|ISO19115:2003|B.2.2.1 p40 (MD_Keywords data type in B.2.2.3 p43)|Optional|

h4. Status in EEA metadata

  *Conditional: obligatory if the dataset is published in the EEA website*

h4. Important notes

** The descriptive keyword element provides keywords which describe the data set, along with their type and the reference source (thesaurus). This particular element refers to the EEA topics or themes in the official website (https://www.eea.europa.eu/themes). 

** The EEA topics or themes have been defined by the EEA website team and their values shall be used without further editing. The thesaurus title and date information shall not be modified. 

** If a dataset is published on the EEA website, this keyword needs to be added into the metadata. More than one theme can be selected, but they shall be the same both in the catalogue and on the website. Other datasets may be also tagged with this keyword, but it is not mandatory. 

** _This metadata element *requires editing.*_

h2. MD_Metadata/identificationInfo/*/descriptiveKeywords (GEMET- INSPIRE themes)

h4. XML encoding

<pre>

<code class="xml">

    <gmd:descriptiveKeywords>

            <gmd:MD_Keywords>

               <gmd:keyword>

                  <gco:CharacterString>Protected sites</gco:CharacterString>

               </gmd:keyword>

               <gmd:type>

                  <gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.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/iso/19139/resources/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://sdi.eea.europa.eu/catalogue/srv/eng/thesaurus.download?ref=external.theme.httpinspireeceuropaeutheme-theme">geonetwork.thesaurus.external.theme.httpinspireeceuropaeutheme-theme</gmx:Anchor>

                           </gmd:code>

                        </gmd:MD_Identifier>

                     </gmd:identifier>

                  </gmd:CI_Citation>

               </gmd:thesaurusName>

            </gmd:MD_Keywords>

         </gmd:descriptiveKeywords>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0|C.2.10 p107 and C.2.11 p108|Mandatory (at least to have one set of keywords. INSPIRE theme keywords are mandatory)|

|ISO19115:2003|B.2.2.1 p40 (MD_Keywords data type in B.2.2.3 p43)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** The descriptive keyword element provides keywords which describe the data set, along with their type and the reference source (thesaurus). This particular element refers to INSPIRE themes keywords. 

** The INSPIRE spatial themes are defined in the INSPIRE Directive. Values from the GEMET - INSPIRE themes, version 1.0 thesaurus (http://inspire.ec.europa.eu/theme) shall be used without further editing. The thesaurus title "GEMET - INSPIRE themes, version 1.0 " and date information (dateTypeCode "publication" and date "2008-06-01") shall not be modified. 

** More than one theme can be selected, but there shall be one _keyword/characterString_ element per INSPIRE spatial theme to which the data set belongs.

** _This metadata element *requires editing.*_

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

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

                      <!-- [.....................] -->

  <gmd:descriptiveKeywords gco:nilReason="withheld">

            <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:keyword>

                  <gco:CharacterString>IDP_shortname_CDDA</gco:CharacterString>

               </gmd:keyword>

               <gmd:keyword>

                  <gco:CharacterString>IDP_reference</gco:CharacterString>

               </gmd:keyword>

               <gmd:keyword>

                  <gco:CharacterString>IDP_topics_Biodiversity</gco:CharacterString>

               </gmd:keyword>

               <gmd:keyword>

                  <gco:CharacterString>green infrastructure</gco:CharacterString>

               </gmd:keyword>

               <gmd:keyword>

                  <gco:CharacterString>BISE</gco:CharacterString>

               </gmd:keyword>

               <gmd:keyword>

                  <gco:CharacterString>HNV</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="http://standards.iso.org/iso/19139/resources/gmxCodelists.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>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0| 	C.2.10 p107 |Mandatory (at least to have one set of keywords)|

|ISO19115:2003|B.2.2.1 p40 (MD_Keywords data type in B.2.2.3 p43)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** The descriptive keyword element provides keywords which describe the data set, along with their type and the reference source (thesaurus). This particular element refers to a list which consists of EEA relevant keywords that are intended to be addressed to EEA users and Eionet partners.

** 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_)

** [[catalogueeea_keywords|Already existing keywords]] should be reused whenever possible.

** Keywords specific to EEA initiatives or applications (such as the [[Naming_conventions#4-Geospatial-Environmental-Accounting-related-keywords-IDP-keywords|Geospatial Environmental Accounting keywords]]) should also be included as EEA keywords. 

** The thesaurus title "EEA keyword list" and date information (dateTypeCode "creation" and date "2002-03-01") shall not be modified. 

** _This metadata element *requires editing.*_

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

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

                      <!-- [.....................] -->

		   <gmd:descriptiveKeywords gco:nilReason="withheld">

            <gmd:MD_Keywords>

               <gmd:keyword>

                  <gco:CharacterString>geospatial data</gco:CharacterString>

               </gmd:keyword>

               <gmd:type>

                  <gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_KeywordTypeCode"

                                          codeListValue="theme"/>

               </gmd:type>

               <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://standards.iso.org/iso/19139/resources/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://sdi.eea.europa.eu/catalogue/srv/eng/thesaurus.download?ref=local.theme.eea-categories">geonetwork.thesaurus.local.theme.eea-categories</gmx:Anchor>

                           </gmd:code>

                        </gmd:MD_Identifier>

                     </gmd:identifier>

                  </gmd:CI_Citation>

               </gmd:thesaurusName>

            </gmd:MD_Keywords>

         </gmd:descriptiveKeywords>

                      <!-- [.....................] -->

	</gmd:MD_DataIdentification>

</gmd:identificationInfo>

</code></pre>

h4. References

|INSPIRE Metadata TG v2.0| 	C.2.10 p107 |Mandatory (at least to have one set of keywords)|

|ISO19115:2003|B.2.2.1 p40 (MD_Keywords data type in B.2.2.3 p43)|Optional|

h4. Status in EEA metadata

  *Mandatory*

h4. Important notes

** The descriptive keyword element provides keywords which describe the data set, along with their type and the reference source (thesaurus). This particular element is used to discriminate between geospatial data sets, maps, figures, charts, etc.

** We are currently registering only geospatial data sets with an explicit or implicit spatial component, therefore this metadata element should be set to "geospatial data". 

** The thesaurus title "EEA categories" and date information (dateTypeCode "publication" and date "2010-07-06") shall not be modified. 

** The EEA Template already includes the "geospatial dataset" value by default, so it should not require any editing.

** _This metadata element does not require any editing._

h2. MD_Metadata/identificationInfo/*/descriptiveKeywords (GEMET)

h4. XML encoding

<pre>

<code class="xml">

<gmd:identificationInfo>

	<gmd:MD_DataIdentification>

                      <!-- [.....................] -->

   <gmd:descriptiveKeywords>

            <gmd:MD_Keywords>

               <gmd:keyword>

                  <gco:CharacterString>natural areas protection</gco:CharacterString>

               </gmd:keyword>

               <gmd:keyword>

                  <gco:CharacterString>natural area</gco:CharacterString>

               </gmd:keyword>

               <gmd:keyword>

                  <gco:CharacterString>protected area</gco:CharacterString>

               </gmd:keyword>

               <gmd:type>

                  <gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_KeywordTypeCode"

                                          codeListValue="theme"/>

               </gmd:type>

               <gmd:thesaurusName>

                  <gmd:CI_Citation>

                     <gmd:title>

                        <gco:CharacterString>GEMET</gco:CharacterString>

                     </gmd:title>

                     <gmd:date>

                        <gmd:CI_Date>

                           <gmd:date>

                              <gco:Date>2018-08-16</gco:Date>

                           </gmd:date>

                           <gmd:dateType>

                              <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/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://sdi.eea.europa.eu/catalogue/srv/eng/thesaurus.download?ref=external.theme.gemet">geonetwork.thesaurus.external.theme.gemet</gmx:Anchor>

                           </gmd:code>

                        </gmd:MD_Identifier>

                     </gmd:identifier>

                  </gmd:CI_Citation>

               </gmd:thesaurusName>

            </gmd:MD_Keywords>

         </gmd:descriptiveKeywords>

                      <!-- [.....................] -->

	</gmd:MD_DataIdentification>

</gmd:identificationInfo>

</code></pre>