european directive (2007/2/ec) inspire – sharing soil data in interoperable way · 2013. 1....

European Directive (2007/2/EC) INSPIRE – sharing soil data in interoperable way

EIONET Workshop on Soil, Ispra, 10th -12th December 2012

Serving society Stimulating innovation Supporting legislation

Robert Tomas, Ph.DEuropean Commission

Joint Research Centre

Digital Earth and Reference Data Unit

Why Europe needs a spatial data infrastructure (SDI)?• Natural Disasters and as well as

other environmental phenomena do not stop at national borders!

• 20% of the EU citizens (115 million) live within 50 Km from a border

• 70% of all fresh water bodies in Europe are part of a trans-boundary river basin !!

Building a European SDI is complex• Europe is a patchwork of several

countries with different traditions, cultures and socio- economic models

• This is reflected in the different ways in which geo- spatial data is managed

Infrastructure for Spatial Information in the European Community -INSPIRE Directive

INSPIRE lays down general rules to establish an infrastructure for spatial information in Europe for the purposes of Community environmental policies and policies or activities which may have an impact on the environment.

INSPIRE based on the infrastructures for spatial information established and operated by the Member States

INSPIRE is a distributed infrastructure.

INSPIRE does not require collection of new spatial data INSPIRE does not affect existing Intellectual Property Rights

Entry into force 15 May 2007

INSPIRE Components

• INSPIRE is a Framework Directive• Detailed technical provisions are laid down in

Implementing Rules on

• Metadata• Interoperability of spatial data sets and services• Network services (discovery, view, download, transform,

invoke)• Data and Service sharing (policy)• Coordination and measures for Monitoring & Reporting

• Once adopted, Implementing Rules become European legislative acts and national law in 27 Member States and in some EFTA countries

INSPIRE - current Legal framework•Directive 2007/2/EC of the European Parliament and of the Council (INSPIRE) 14.03.2007•INSPIRE Metadata Regulation 03.12.2008•Commission Decision regarding INSPIRE monitoring and reporting 05.06.2009•Regulation on INSPIRE Network Services 19.10.2009 (View and discovery)

•Corrigendum to INSPIRE Metadata Regulation 15.12.2009•Regulation on INSPIRE Data and Service Sharing 29.03.2010•Commission Regulation amending Regulation (EC) No 976/2009 as regards download services and transformation services 10.12.2010•COMMISSION REGULATION implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services 10.12.2010 (Annex I)

•COMMISSION REGULATION amending Regulation 1089/2010 as regards interoperability of spatial data sets and services 05.02.2011 (code lists)

Implementing Rules in preparation

2012-06 Submission for opinion of the INSPIRE committee of IR for the services allowing spatial data services to be invoked

2013-03 Submission for opinion of the INSPIRE committee of IRs for the interoperability of spatial data sets and services for Annex II and III spatial data themes

Implementation RoadmapWhat WhenMetadata available for Annex I+II spatial data

Discovery and view services IOC

Discovery and View Services operational

Download and Transformation Services IOC

Download and Transformation Services operational

Access to (newly collected / all) Annex I spatial data sets under harmonised conditions

Metadata available for Annex III spatial data

Access to (newly collected / all) Annex II+III spatial data sets under harmonised conditions

Dec 2010

May 2011

Nov 2011

June 2012

end 2012

end 2012 / 2017

Dec 2013

around Oct 2015 / 2020

http://inspire.jrc.ec.europa.eu/index.cfm/pageid/44


INSPIRE in a nutshell• Comprehensive data inventory (Monitoring & Reporting IR)• Facilitate data discovery through standardised discovery

services & metadata (IR on Network Services & Metadata)• Data sharing (IR on Data and Service Sharing)• Facilitate data access by allowing view, download and

transformation (IR on Network Services)• Facilitate data use and interoperability by adopting

common cross-domain models to exchange data (IR on Data Interoperability)

INSPIRE Thematic – Data Scope• Annex I

1. Coordinate reference systems

2. Geographical grid systems3. Geographical names4. Administrative units5. Addresses6. Cadastral parcels7. Transport networks8. Hydrography9. Protected sites

• Annex II1. Elevation2. Land cover3. Ortho-imagery4. Geology

Annex III1. Statistical units2. Buildings3. Soil4. Land use5. Human health and safety6. Utility and governmental

services7. Environmental monitoring

facilities8. Production and industrial

facilities9. Agricultural and

aquaculture facilities10.Population distribution –

demography

11. Area management/ restriction/regulation zones & reporting units

12. Natural risk zones13. Atmospheric conditions14. Meteorological

geographical features15. Oceanographic

geographical features16. Sea regions17. Bio-geographical regions18. Habitats and biotopes19. Species distribution20. Energy Resources21. Mineral resources

user user

dataset dataset dataset

... ...

• Access to spatial data in various ways

• User has to deal with interpreting heterogeneous data in different formats, identify, extract and post-process the data he needs

lack of interoperability

Data interoperability

The starting point …

... ...

NetworkService

NetworkService

NetworkService

• Provide access to spatial data via network services and according to a harmonised data specification to achieve interoperability of data

! Datasets used in Member States may stay as they are

! Data or service providers have to provide a transformation between their internal data model and the harmonised data specification

dataset dataset dataset

user user

... and what INSPIRE is aiming at

Data interoperability

Cross-theme data interoperability

TN:Transport networks

EL:Elevation

BU:BuildingsSO:Soil

PF:Production and industrial facilities

AF:Agricultural and aquaculture facilities

ER:Energy Resources

HB:Habitats and biotopes

SD:Species distribution

AM:Area management/ restriction/ regulation zones & reporting units

PD: Population Distribution

US: Utilities and Governmental Services (Waste Management)

Urban Planning

Waste Management Plans

Environmental Impact Assessment

Risk Management

…

PRTR

SEVESO

WasteReporting

Development of data specification – step wise, managed process

Directive(2007)

Modelling Framework for INSPIRE data specifications(2008)

Data specifications for the 9 Annex I data themes(2009)

Data specifications for the 25 Annex II/III data themes(2012)

Interoperability of spatial data sets and services (Implementing Rule)(2009..2012)

Part of the legal framework

Implementation mandatory for European Member States

Impl. Rules vs. Technical Guidelines

DirectiveDirective

IRs

for Metadata,

Network Services

Interoperability

Spatial data sets

and services

IRs

for Metadata,

Network ServicesInteroperability

Spatial data sets

and services

CommissionRegulationCommissionRegulation

Technical

Guidance

Technical

Guidance

“What Member States

must implement”

(abstract

specification)

“How Member States

might implement it”(implementation

specification)

TG for the

Implementation of

Discovery Services

ImplementationRequirements &Recommendations

TG for the

Implementation of

Discovery Services


TG – Data

Specification on

Addresses


TG – Data

Specification on

Addresses


INSPIRE

Directive

2007/2/EC

INSPIRE

Directive2007/2/EC

legally binding

not legally binding

e.g.

Finding the appropriate level of interoperability

169 January 2013

WatercourseWatercourse

Water quality

measurements

Water quality

measurements

ReportReportGaugeGauge

Coordinate

Reference System

Coordinate

Reference System

Reference GridReference Grid

Referencesystems

Widely used

and widely

referencedspatial objects

Application‐

specific –

referenced and

referencing other

spatial objects

Mostly non‐spatial,but may containexplicit or implicit references to spatial objects

out of scopein scope

LakeLake SpringSpring

DischargeDischarge……

…… ……

Spatial data

“Business data”

Public consultation / testing of V2.0 6/2011 – 9/2011

6212 comments received5218 from review; 994 from testing

General Comments

• Data specifications too complex

Requests for simplification accepted, identified where complexity needs to be reduced and initiated ways to implement

INSPIRE should facilitate the obligations on environmental related policies as spatial data infrastructure, including reporting, but the content is defined by the thematic legislations and the associated Technical groups,

Full MS Support to the distinction between• core model to go into the legal act• extended application schema(s) to cover

different use cases

MS review of the 1st Draft of the IR 14.5.– 8.6./2012

455 comments received + generic overview statementsfrom 12 countries

IRs for interoperability of datasets and services Annex II-III

Preparation draft IR v1 EC (with TWG support)

23 Apr – 11 May

Review IR v1 by MS MS 14 May – 8 Jun 2012

Preparation draft IR v2 (based on MS comments) EC 11 June – 9

July 2012Inter-service consultation (ISC) EC services 9 July – 3

August 2012Final draft IR (based on ISC comments) EC 3 Aug – 21

Sep 2012

Option: Translation in all EU official languages

EC (with MS support) 23.1.2013

IC meeting (opinion on IR) March 2013 orX+3weeks?

Updated roadmap

The Technical Guidelines V3.0 rc3 in the final stage of preparation!!

Definition: ” Soils and subsoil characterised according to depth, texture, structure and content of particles and organic material, stoniness, erosion, where appropriate mean slope and anticipated water storage capacity.” [Directive 2007/2/EC]

INSPIRE Soil data theme

To develop a specification of soil data to be shared, both within the soil domain and across domain borders for the Spatial Data Infrastructure of Europe.

Scope • Soil inventories, providing one-off assessments of soil

conditions and/or soil properties at certain locations and at a specific point in time, and allow soil monitoring, providing a series of assessments showing how soil conditions and/or properties change over time.

• Soil mapping, providing a spatial presentation of the properties linked to the soils, including soil types; typically, soil maps are derived with the help of data available in soil inventories. Also other soil related information derived from soil properties, possibly in combination with non-soil data are within the scope.

Methodology• INSPIRE methodology (D 2.6.) was followed -

analysis of reference material received from stakeholders (e.g. GS Soil, eSoter etc..)

• 15 Use cases were studied and are described in detail in the TG (annex B) covering:

• Agri-Environmental Indicators (3x)• Thematic maps derived from Soil information (7x)• Contaminated sites (4x)• Soil monitoring (1x)

So

il& EU

regu

lation

s

INSPIRE Soil data model• One soil data model defines following major

spatial object types:

• Soil profile (both observed and derived)• Profile element (including soil layer and soil horizon)• Soil Body• Soil Derived Object (including both representation types)• Soil Site • Soil Plot

• Extensions (in the TG Annex C,D):• Draft model for managing information related to contaminated sites

as a possible extension to the INSPIRE data model Soil (not to be part of legislation)

• Provision of soil thematic map – elaborated Use case how to provide soil organic carbon content by using the INSPIRE Soil data model

Monitoring

Soil profile

Soil map

Soil derived information

Soil data vectorsMonitoringMonitoringclass Soil: Ov erv iew

SoilPlot

+ inspireId :Identifier [0..1]+ soilPlotLocation :Location+ soilPlotType :SoilPlotTypeValue

«lifeCycleInfo, voidable»+ beginLifespanVersion :DateTime+ endLifespanVersion :DateTime [0..1]

SoilProfile

+ inspireId :Identifier [0..1]


«voidable»+ localIdentifier :CharacterString [0..1]+ otherSoilName :OtherSoilNameType [0..*]+ validFrom :DateTime+ validTo :DateTime [0..1]+ WRBSoilName :WRBSoilNameType

ProfileElement

+ inspireId :Identifier [0..1]+ profileElementDepthRange :RangeType


«voidable»+ particleSizeFraction :ParticleSizeFractionType [1..*]

Observ edSoilProfile Deriv edSoilProfile

SoilBody

+ geometry :GM_MultiSurface+ inspireId :Identifier [0..1]


«voidable»+ soilBodyLabel :CharacterString

Deriv edProfilePresenceInSoilBody

«voidable»+ derivedProfi lePercentageRange :RangeType

SoilSite

+ geometry :GM_Object+ inspireId :Identifier [0..1]+ soi lInvestigationPurpose :SoilInvestigationPurposeValue


«voidable»+ val idFrom :DateTime+ val idTo :DateTime [0..1]

SoilHorizon

«voidable»+ FAOHorizonNotation :FAOHorizonNotationType+ otherHorizonNotation :OtherHorizonNotationType [0..*]

SoilLayer

+ layerType :LayerTypeValue

«voidable»+ layerGenesisEnvironment :EventEnvironmentTerm [0..1]+ layerGenesisProcess :EventProcessTerm [0..1]+ layerGenesisProcessState :LayerGenesisProcessStateValue [0..1]+ layerRockType :LithologyTerm [0..*]

constraints{geogenicConstraint}

SoilDeriv edObject

+ geometry :GM_Object+ inspireId :Identifier [0..1]

+isBasedOnSoilBody«voidable»

0..*

+isBasedOnObservedSoilProfile«voidable»

0..*

+isDescribedBy«voidable» 1..*

+isPartOf1

+locatedOn«voidable»

0..1

+isObservedOnLocation«voidable»1..*

+isDescribedBy«voidable»

1..*

+observedProfile«voidable»

1

+location

1

+isDerivedFrom«voidable»

0..*

«voidable»

+isBasedOnSoilDerivedObject«voidable» 0..*

MonitoringMonitoringMonitoring


Monitoring


Monitoring


Monitoring

Soil map


Monitoring

Soil map


Monitoring

Soil profile

Soil map


MonitoringMonitoring

Soil profile

Soil map

MonitoringMonitoringMonitoringMonitoringMonitoringMonitoringMonitoringMonitoring

Soil map

Monitoring

Soil map

Monitoring

Soil profile

Soil map


Monitoringclass Soil: Ov erv iew

SoilPlot

+ inspireId :Identifier [0..1]+ soilPlotLocation :Location+ soilPlotType :SoilPlotTypeValue


SoilProfile

+ inspireId :Identifier [0..1]


«voidable»+ localIdentifier :CharacterString [0..1]+ otherSoilName :OtherSoilNameType [0..*]+ validFrom :DateTime+ validTo :DateTime [0..1]+ WRBSoilName :WRBSoilNameType

ProfileElement

+ inspireId :Identifier [0..1]+ profileElementDepthRange :RangeType


«voidable»+ particleSizeFraction :ParticleSizeFractionType [1..*]

Observ edSoilProfile Deriv edSoilProfile

SoilBody

+ geometry :GM_MultiSurface+ inspireId :Identifier [0..1]


«voidable»+ soilBodyLabel :CharacterString

Deriv edProfilePresenceInSoilBody

«voidable»+ derivedProfi lePercentageRange :RangeType

SoilSite

+ geometry :GM_Object+ inspireId :Identifier [0..1]+ soi lInvestigationPurpose :SoilInvestigationPurposeValue


«voidable»+ val idFrom :DateTime+ val idTo :DateTime [0..1]

SoilHorizon

«voidable»+ FAOHorizonNotation :FAOHorizonNotationType+ otherHorizonNotation :OtherHorizonNotationType [0..*]

SoilLayer

+ layerType :LayerTypeValue

«voidable»+ layerGenesisEnvironment :EventEnvironmentTerm [0..1]+ layerGenesisProcess :EventProcessTerm [0..1]+ layerGenesisProcessState :LayerGenesisProcessStateValue [0..1]+ layerRockType :LithologyTerm [0..*]

constraints{geogenicConstraint}

SoilDeriv edObject

+ geometry :GM_Object+ inspireId :Identifier [0..1]

+isBasedOnSoilBody«voidable»

0..*

+isBasedOnObservedSoilProfile«voidable»

0..*

+isDescribedBy«voidable» 1..*

+isPartOf1

+locatedOn«voidable»

0..1

+isObservedOnLocation«voidable»1..*

+isDescribedBy«voidable»

1..*

+observedProfile«voidable»

1

+location

1

+isDerivedFrom«voidable»

0..*

«voidable»

+isBasedOnSoilDerivedObject«voidable» 0..*

Soil thematic map - coverage

class Soil: Ov erv iew

SoilThemeCov erage

+ domainExtent :EX_Extent [1..*]+ soilThemeParameter :SoilThemeParameterType

«lifeCycleInfo»+ beginLifespanVersion :DateTime+ endLifespanVersion :DateTime [0..1]

«voidable»+ validTimeFrom :Date+ validTimeTo :Date [0..1]

constraints{rangeSetValuesConstraint}

Coverages (Base)::Coverage

+ metadata :Any [0..*]+ rangeType :RecordType

Coverages (Domain and Range)::CoverageByDomainAndRange

+ coverageFunction :CoverageFunction [0..1]+ domainSet :Any+ rangeSet :Any [0..*] {ordered}

constraints{gridFunctionRequiresGridDomain}

Cov erages (Domain and Range)::RectifiedGridCov erage

constraints{domainIsRectifiedGrid}

SoilThemeDescriptiv eCov erage

+ domainExtent :EX_Extent [1..*]+ soilThemeDescriptiveParameter :SoilThemeDescriptiveParameterType

«lifeCycleInfo»+ beginLifespanVersion :DateTime+ endLifespanVersion :DateTime [0..1]

+isDescribing

1

{equalDomain}+isDescribedBy«voidable»

0..*

Soil thematic maps coverage

Generic ISO 19123 Coverage classes

Semantic interoperability • WRB (World reference base for soil resources 2006,

first update 2007 ) is used as standard soil type classification system; however it is made possible to use national classification systems (additional)

• FAO (Guidelines for soil description, 4th edition, Food and Agriculture Organization of the United Nations, Rome, 2006, pp. 67-77.) is used for Soil horizon classification

• Re-using of classification schemas from geology related to the Soil layer rock and genesis descriptions

Soil parameters in the modelImportant parameters in the model due to adopted EU

Regulations:• Soil profile: WRB name (or national soil type), potential root depth,

available water capacity, carbon stock, water drainage• Profile element: particle size fraction, organic carbon content, N, pH,

Cd, Cr, Cu, Pb, Hg, Ni • Soil derived object: potential root depth, available water capacity,

carbon stock, water drainage, particle size fraction, organic carbon content, N, pH, Cd, Cr, Cu, Pb, Hg, Ni, Zn

• Soil site: any chemical, biological, physical properties

The integration – specialisation of the generic O&M ISO standard to provide soil measurement information

Development of the INSPIRE Soil data specification covers:

• 11 TWG-SO members• 3 years – 2010-2012• 65+ teleconferences• 7 Face to face meetings• 3 cross-theme workshops• 3 major versions of the document• 190 pages in version 1.0• 196 pages in version 2.0• 372 pages in version 3.0• 15 Use cases• 240 received comments on version 2.0• 4 recieved comments on the 1st Draft of the IR• 3 INSPIRE conferences

The people behind…TWG INSPIRE Soil:

• Arnold Arnoldussen (TWG Facilitator), • Stijn Keijers (TWG Editor), • Jandirk Bulens (TWG co-editor),• Christine Le Bas, • Edoardo Costantini, • Einar Eberhardt, • Marc van Liedekerke, • Stephan Marahrens, • Ainara Senar, • Kees Versluijs, • Robert Tomas (JRC contact point).

The faces behind..(2010)

The faces behind..(2012)

In Summary• INSPIRE is now! MSs are implementing Inspire

compliant services.• The 2012, 2015, 2017 and 2020 deadlines for Annex I,

II & III mean that work to comply with INSPIRE needs to be starting now.

• INSPIRE is an opportunity - widens the use of data held by thematic environmental communities.

• INSPIRE is a multi-purpose infrastructure• Activities on-going to re-use INSPIRE in other

policy areas (Digital Agenda for Europe, WFD…)• INSPIRE facilitates the use of international

standards (ISO, CEN, OGC, WRB, FAO) as well as taking active part in their development – e.g. OGC GWML 2.0 Interoperability experiment

Coordination• Transparency and

inclusiveness • Stakeholder consultations • Support to Member States

on the implementation• Extend INSPIRE to and ensure

consistency of different policy domains

• Promote INSPIRE in international standardisation

More information:

• INSPIRE• http://inspire.jrc.ec.europa.eu/

• INSPIRE data specifications• Overview

http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2• Data models

http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2/list/d atamodels

• Schemas

http://inspire.ec.europa.eu/schemas/

http://inspire.jrc.ec.europa.eu/


http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2/list/datamodels

http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2/list/datamodels

http://inspire.ec.europa.eu/schemas/

european directive (2007/2/ec) inspire – sharing soil data in interoperable way · 2013. 1....

Documents