EEA SDI » History » Revision 42
Revision 41 (Jose Rubio, 2018-01-31 18:33) → Revision 42/387 (Jose Rubio, 2018-02-07 15:23)
h1. EEA SDI: The EEA catalogue of geospatial datasets
{{>toc}}
h2. 1. Why the SDI?
* Discover and access easily EEA data easily both from inside (EEA staff) and outside (ETC, contractors, general public)
* Maintain a reference version of datasets produced and/or published by the EEA
* Need to have a persistent archiving of the datasets not altered over time
* Ensure traceability from final products to source
* Identify what exists and what is missing
A presentation with all the details about the SDI, components, processes and outlook is available in the attachment:"20180125_SDI_Basics.pptx"
h2. 2. Overview of the SDI components
h3. Metadata catalogues
* The EEA SDI is based on a metadata catalogue service that facilitates the discovery of the datasets produced and/or published by the EEA.
* Through the metadata, users can access information on the content and quality of the datasets, and ultimately download the datasets.
* The SDI catalogues are accessible through http://sdi.eea.europa.eu/
* Two metadata catalogues describing spatial data published by the EEA:
> Internal catalogue: https://sdi.eea.europa.eu/internal-catalogue/
> Public catalogue: http://sdi.eea.europa.eu/catalogue/
> > The public catalogue is accessible by anyone, contains the same records as the internal but with less detailed information. The public catalogue does not provide either access to restricted use data. Names of individuals and file location are removed
* A metadata editor is available in order to help create metadata according to the EEA metadata guidelines (see 3).
> Metadata editor interface available on: https://sdi.eea.europa.eu/editor-catalogue/
* The SDI catalogues follows the OGC CSW 2.0.2 standard and INSPIRE Discovery services and are implemented using GeoNetwork. Metadata are compliant with ISO19115/19139 and INSPIRE Metadata Implementing Rules.
h3. CSW interfaces
* Internal Catalogue: http://sdi.eea.europa.eu/internal-catalogue/srv/eng/csw?
> Information about the internal catalogue service (GetCapabilities):https://sdi.eea.europa.eu/internal-catalogue/srv/eng/csw?service=CSW&version=2.0.2&request=GetCapabilities
* Public Catalogue: http://sdi.eea.europa.eu/catalogue/srv/eng/csw?
> Information about the public catalogue service (GetCapabilities):http://sdi.eea.europa.eu/catalogue/srv/eng/csw?service=CSW&version=2.0.2&request=GetCapabilities
* (A subset of) the public catalogue is harvested by the GEOSS (Global Earth Observation System of Systems) and available through the GEOSS portal www.geoportal.org
> Virtual CSW interface: http://sdi.eea.europa.eu/catalogue/srv/eng/csw-geoss?
> Information about the public catalogue service harvested by GEOSS (GetCapabilities): http://sdi.eea.europa.eu/catalogue/srv/eng/csw-geoss?service=CSW&version=2.0.2&request=GetCapabilities
> To be harvested by GEOSS it is necessary that the dataset metadata are tagged with the category *geodatacore*. Only *full, free and open datasets* can be tagged as geodatacore.
* An interface is available for INSPIRE
> Virtual CSW interface: http://sdi.eea.europa.eu:/catalogue/srv/eng/csw-inspire?
* RSS feeds are available both for internal and external catalogues:
> Internal RSS feed: https://sdi.eea.europa.eu/internal-catalogue/srv/eng/rss.search?sortBy=changeDate
> Public RSS feed: http://sdi.eea.europa.eu/catalogue/srv/eng/rss.search?sortBy=changeDate
> RDF interface: http://sdi.eea.europa.eu/catalogue/srv/eng/rdf.metadata.get?
* SDI API: https://sdi.eea.europa.eu/editor-catalogue/doc/api/
h3. Data storage
* Datasets are stored in a file system and a spatial database running on Linux.
> Spatial database: PostgreSQL and PostGIS
> File-based storage system accessible via CIFS (internally) and HTTPS, WebDavS and FTPS (externally).
* The metadata records point to the location of the dataset on the EEA SDI file system.
* This repository should contain the “reference” version of any EEA spatial dataset (published or not) used in EEA products.
* Datasets are to be versioned – not to be deleted or edited. Data are regularly backed-up.
h2. *3.Registration of datasets in the EEA SDI*
h3. *Which datasets to register in the SDI?*
Final versions of datasets that:
* Are requested for production under AMP.
* Used directly or indirectly in publications.
* Used for assessments and indicators.
To know more about the SDI, please consult our wiki page on [https://taskman.eionet.europa.eu/projects/datasets-for-sdi/wiki/EEA_SDI_-_The_basics]
h3. *Metadata Creation*
* EEA Metadata editor tool available on https://sdi.eea.europa.eu/editor-catalogue/ accessible using EIONET account.
* Metadata file should be created using the template called *EEA metadata template* which is available, under *Contribute*, when clicking on *Add New Record*.
* Using previous entries is acceptable +only+ in case we are creating a revised or an updated version of an existing metadata in the SDI.
* Follow helpers in the EEA metadata template and do not remove existing and pre-filled fields in the template. When creating the record, save the template as metadata and change its title to avoid duplicated names.
* There is only a 1:1 relation between metadata and datasets: several MD cannot point out at the same dataset – i.e. geodatabases should contain one dataset described by a metadata set. No possibility at this point in time to address specific feature classes.
* Whenever possible, metadata datasets need to be linked to the corresponding dataset series metadata.
h3. *Guidelines on metadata edition*
* Metadata shall comply with the "INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119 V. 1.3" available on http://inspire.ec.europa.eu/documents/Metadata/MD_IR_and_ISO_20131029.pdf.
* Metadata shall be ISO 19115:2003/19139 compliant.
* Metadata shall contain all optional elements offered by ISO 19115 and INSPIRE which are regarded as useful for EEA. Please also note that new elements will be added in the upcoming months in order to ensure the full alignment of the EEA Metadata profile with the INSPIRE Technical Guidelines v 1.3 and eventually 2.0 (available on https://inspire.ec.europa.eu/id/document/tg/metadata-iso19139).
* For detailed guidance on how to fill in specific metadata elements, consult EEA metadata guidelines on: https://taskman.eionet.europa.eu/projects/sdi/wiki/Cataloguemetadata_guidelines.
h3. *Registration Request*
* Request by issuing a ticket under the Taskman project “IDM » IDM4-Team » SDI » Datasets for SDI”
* The project is +only dedicated to SDI registration+.
* The ticket must contain the following information to be accepted by the SDI Team:
<pre>
Metadata (URL to the draft MD record in the Editor)
Dataset (Path to the dataset)
Thumbnail (PNG)
Web Map Service when available(Link to the WMS and REST service when available).
Whether it is an internal or a public dataset
Whether the dataset belongs to a dataset series (and name of the dataset series)
</pre>
* The title of the ticket should be identical to the title of the dataset to be registered.
* The category of the ticket should be “Pre-SDI check”
* Each dataset should be reported separately as a task in taskman to better follow up on the issues that may arise in each individual registration. Tickets referring to related datasets can be linked using "Related Task".
* The thumbnail shall be generated in PNG format by the data steward and be included in the SDI registration taskman request. The image shall provide a clear overview of the whole dataset and not be bigger than 1 MB.
* A checklist is under development which will have to be completed before a registration request can be accepted.
h3. *Quality Checks by SDI Team*
* SDI Team checks metadata quality
* SDI Team checks basic topological consistency rules
h3. *Publication and data archiving*
* Metadata is made available in the internal catalogue
* Data is stored in the SDI storage place
* Metadata is made available in the public catalogue (automated harvesting)
* Datasets may or may not be made available depending on their data policy
h2. *4. Detailed guidelines on the EEA Metadata profile*
For detailed guidance on how to create metadata according to the EEA metadata profile, please consult EEA metadata guidelines on: https://taskman.eionet.europa.eu/projects/sdi/wiki/Cataloguemetadata_guidelines.
h3. Naming conventions
For specific metadata elements some naming conventions are recommended. These are detailed [[Naming_conventions|here]]
In case you have any question, doubt or suggestion, please contact the EEA SDI team on *sdi@eea.europa.eu*
Go to top