GS SOIL METADATA

18
Co-funded by the community programme eContentplus GS SOIL METADATA Christian Ansorge Umweltbundesamt Tomáš Řezník Masaryk University Laboratory on Geoinformatics and Cartography GS Soil workshop, INSPIRE conference, 27 nd June 2011

description

GS SOIL METADATA. Christian Ansorge Umweltbundesamt Tomáš Řezník Masaryk University Laboratory on Geoinformatics and Cartography. Aspects of soil metadata Review on WP3 actions in 2010 Soil metadata profile Recent WP3 actions Best practice guidelines. Soil metadata profile. - PowerPoint PPT Presentation

Transcript of GS SOIL METADATA

Page 1: GS SOIL  METADATA

Co-funded by the community programme eContentplus

GS SOIL METADATA

Christian AnsorgeUmweltbundesamt

Tomáš ŘezníkMasaryk University

Laboratory on Geoinformatics and Cartography

GS Soil workshop, INSPIRE conference, 27nd June 2011

Page 2: GS SOIL  METADATA

• Aspects of soil metadata• Review on WP3 actions in 2010

– Soil metadata profile• Recent WP3 actions

– Best practice guidelines

2

Page 3: GS SOIL  METADATA

ISO 19115

INSPIRE

ISO CORE

Mandatory

ISO 19119

ISO 19139

SOIL PROFILE

Soil metadata profile

3

Page 4: GS SOIL  METADATA

WP connections for the metadata

4

WP2 WP3D3.1 & D3.2

WP4 WP5 WP6 WP7

Page 5: GS SOIL  METADATA

Review on WP3 actions in 2010

Development of soil metadata profile

Deliverable 3.1INSPIRE compatible metadata profile for soil geographic

datasets and dataset seriesDeliverable 3.2INSPIRE compatible metadata profile for soil geographic

data services Deliverable 3.3Preliminary best Practice Guidelines for creating and

maintaining metadata for soil database

5

Page 6: GS SOIL  METADATA

Purpose of D3.1 and 3.2 documents

• Primary requirement – INSPIRE compliant metadata profiles – therefore Commission Regulation No. 1205/2008 (including Corrigenda 1) and their Technical Guidelines as well as Commission Regulation No 976/2009 as basic stones.

• Therefore inspired by:– drafts of INSPIRE Annex I data specifications

(especially TN, HY, PS) – INSPIRE methodologies (generic conceptual model,

data specification development)– ISO, OGC and W3C standards to properly express

soil-specific issues within their standardization framework

6

Page 7: GS SOIL  METADATA

INSPIRE metadata (Commission Regulation No 1205/2008)

7Example of the printed map Sheet Freiburg-North(map representation acc. to the German topographic map 1:200.000)

Resource title

Resource abstract Resource type

Unique Resource Identifier

Key word

Topic Category

Geographic Bounding Box

Temporal Reference

Lineage

Conformity

Conditions applying to access and use

Limitations on public access

Responsible party

Page 8: GS SOIL  METADATA

Aspects of the Soil metadata profiles

• Two metadata profiles:– for datasets and dataset series– for services

• Compliant to the Commission Regulation No. 1205/2008• Added soil theme-specific metadata elements• Well-described structure according to the ISO 19100

series standards• Within ISO 19115 framework• Examples of the XML encoding• Registered as the INSPIRE Reference Material

8

Page 9: GS SOIL  METADATA

Added soil theme-specific metadata – – mandatory and conditional elements

9

• Coordinate Reference System [1]• Encoding [1..*]• Character Encoding [0..*]• Source title [0..1]• Source date of mapping [0..*]• Spatial Representation Type [0..*]• Online digital transfer options [0..1]• Topology level [0..*]• Source mapping scale [0..1]• Completeness – Ommission [0..*]• Positional Accuracy – Absolute or external accuracy [0..*]• Thematic Accuracy – Classification Correctness – Misclassification

rate [0..*]• Contains operations [0..*]• Service version [0..*]

Page 10: GS SOIL  METADATA

Recent WP3 actions

Development of soil metadata best practice guidelines

Deliverable 3.4Final best Practice Guidelines for creating and maintaining

metadata for soil database

10

Page 11: GS SOIL  METADATA

Best practice

Best practice in general- Generally accepted- Informally standardized techniques- methods or processes that have proven themselves over

time to accomplish given tasks- maintain quality- an extension or alternative to mandatory legislated

standards

11

Page 12: GS SOIL  METADATA

Purpose of D3.4 documents

• Soil data provider are unfamiliar with SDI– Support and guide soil data providers to fulfill their

obligations regarding the INSPIRE directive– Ensure a common understanding and a high quality of

metadata and their specific elements

• Therefore INSPIREd by:– INSPIRE Metadata Implementing Rules: Technical

Guidelines based on EN ISO 19115 and EN ISO 19119

– INSPIRE methodologies (generic conceptual model, data specification development)

12

Page 13: GS SOIL  METADATA

GS Soil metadata profiles

• D 3.4 Best Practice Guidelines for creating and maintaining metadata for soil database– Cook-book for metadata– Definition of metadata profiles

• For dataset and dataset series• For spatial data services• Including examples on conceptual (table) and

implementation (XML source-code) levels– Data quality measures and recommendations– Thesaurus information (very brief, link to D 3.5)– Multilinguality issues– Related SDI aspects (feature catalogue, catalogue

services, metadata connections from different levels)

13

Page 14: GS SOIL  METADATA

Changes in metadata profile

• Changes with respects to INSPIRE development– Technical guidelines on INSPIRE metadata v1.2– Commission Regulation No 1089/2010– Commission Regulation No 976/2009– Technical Guidelines to INSPIRE Discovery services– Added Coordinate reference system, Encoding, …

• Changes of GS Soil consortium opinions:– Added File identifier– Added Geometric object type metadata elements

14

Page 15: GS SOIL  METADATA

Example of metadata element structure

15

Metadata element name Resource locatorDefinition Location (address) for on-line access using a Uniform

Resource Locator address or similar addressing scheme.ISO 19115 number and name 397. linkage

INSPIRE obligation / condition Mandatory if a URL is available to obtain more information on the resources and/or access related services.

INSPIRE multiplicity 0..*Data type (and ISO 19115 no.) URLDomain URL (IETF RFC1738 and IETF RFC 2056)

Implementing guidelines

Specify Resource locator in all possible ways according to the following guidelines - see [19] and [29]: If View and/or Download service is available for accessing the

resource, specify link to the View and/or Download service and to the View and/or Download service metadata. See section 10.4 for forther information.

If direct link to the resource is available, specify it. Otherwise specify link to a contact point where more

information about the resource is available.

Example http://www.afbini.gov.uk/index/services/services-specialist-advice/soils-environment.htm

Example XML encoding

<gmd:MD_Metadata ……

<gmd:distributionInfo><gmd:MD_Distribution>…

<gmd:transferOptions><gmd:MD_DigitalTransferOptions>

<gmd:onLine><gmd:CI_OnlineResource>

<gmd:linkage><gmd:URL>http://www.afbini.gov.uk/index/services/services-specialist-advice/soils-environment.htm</gmd:URL>

</gmd:linkage></gmd:CI_OnlineResource>

</gmd:onLine></gmd:MD_DigitalTransferOptions>

</gmd:transferOptions></gmd:MD_Distribution>

</gmd:distributionInfo>…</gmd:MD_Metadata>

Page 16: GS SOIL  METADATA

Multilinguality issues

16

<gmd:identificationInfo><gmd:MD_DataIdentification>

<gmd:citation><gmd:CI_Citation>

<gmd:title xsi:type="gmd:PT_FreeText_PropertyType"><gco:CharacterString>Agregovaná půdní mapa</gco:CharacterString> <gmd:PT_FreeText>

<gmd:textGroup> <gmd:LocalisedCharacterString locale="#locale-en">Aggregated soil map</gmd:LocalisedCharacterString>

</gmd:textGroup><gmd:textGroup>

<gmd:LocalisedCharacterString locale="#locale-de">Aggregierte Bodenkarte</gmd:LocalisedCharacterString> </gmd:textGroup>

<gmd:textGroup><gmd:LocalisedCharacterString locale="#locale-el">Συνολικός Εδαφολογικός Χάρτης</gmd:LocalisedCharacterString>

</gmd:textGroup> </gmd:PT_FreeText>

</gmd:title>..</gmd:CI_Citation>

</gmd:citation>..

</gmd:MD_DataIdentification></gmd:identificationInfo>

Page 17: GS SOIL  METADATA

Best practice and beyond

• D3.4 were developed for and with soil data providers• Specific requirements as important part of metadata

profile and best practice document• Benefits for data provider

– Best practice document shall lead support them in fulfilling their INSPIRE obligations

– Soil specific requirements are considered– Tools for creating and managing metadata were

developed and provided to the data providers• Benefits for INSPIRE and SDI

– Metadata will be available in time– High quality of data is ensured through a common

understanding of metadata and data17

Page 18: GS SOIL  METADATA

What is next?

18

• Special thanks to Tomáš Řezník• Looking forward talking

with you about our soil metadata profile

Modified from http://urbanext.illinois.edu