(3) data scope in inspire

(3) Data scope in INSPIRE

European Commission Joint Research Centre

Institute for Environment and Sustainability

Digital Earth and Reference Data Unit

www.jrc.ec.europa.eu

Serving societyStimulating innovationSupporting legislation

Vlado Cetl

2/29Training: INSPIRE BasicsEC JRC

Outline

• INSPIRE Data Themes• Data Interoperability• Data Specifications• Examples


INSPIRE components


INSPIRE data themes

Annex I1. Coordinate reference

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


• The INSPIRE working group on Reference Data and Metadata (RDM) (2002): Reference Data and Metadata Position Paper

• Provide an unambiguous location for a user's information• Enable the merging of data from various sources• Provide a context to allow others to better understand the

information that is being presented• INSPIRE Environmental Thematic Coordination Group (2002):

Environmental thematic user needs - Position Paper• a review of policy documents including existing and planned

environmental legislation;• a review of papers available from existing formal and informal

working groups;• consultation with stakeholders in different environmental policy

areas • expert judgement based on the experience of EEA staff and

EIONET

INSPIRE data themes


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

user user

... and what INSPIRE is aiming at

Data interoperability


INSPIRE IRs vs. TG


Why common Data Specifications?

• Member States should make available data within the scope of INSPIRE using

• the same spatial object types (and definitions)

• the same attributes (and definitions, types, code

lists) and relationships to other types, e.g.

BuildingHeight, BuildingSize

• a common encoding (GML application schemas)

• common portrayal rules

• This facilitates interoperability and pan-European/cross-border applications (e.g. information systems, reporting systems, forecasting models)


DS Development - Stepwise Approach

• Development of conceptual framework and specification methodology (by Data Specification Drafting Team)

• DS-D 2.3 Definition of Annex Themes and Scope• DS-D 2.5 Generic Conceptual Model (GCM)• DS-D 2.6 Methodology for Specification Development• DS-D 2.7 Guidelines for Encoding

• Development of data specifications for each spatial data theme (by different Thematic Working Group) based on the

• conceptual framework• common specification development methodology• and on the INSPIRE roadmap

• Preparation of the Implementing Rules based on data specifications (by the Commission)


Data interoperability – standards stack


Data interoperability – Stakeholders

• Thematic working groups – 19 TWGs for Annex II&III

• TWG Facilitators• TWG Editors• Domain experts

• EC INSPIRE Team (DG ENV, DG JRC, DG ESTAT)

• Technical coordination = JRC INSPIRE team

• Data Specifications Drafting Team (DS DT)

• Stakeholders• Legally mandated organisations (LMOs)• Spatial data interest communities (SDICs)


Finding the appropriate level of interoperability


Conceptual Framework

• To provide a repeatable data specification development methodology and general provisions for the data specification process, which is valid for all spatial data themes

• The GCM is using a set of interoperability elements

Fundamentals

Data Modelling

Data Management

Requirements Reference model Architectural support for

interoperability Terminology Multi-lingual text and cultural

adaptability Use of ontologies Coordinate referencing and

units of measurements Registers and Registires

Object referencing Spatial and temporal aspects Rules for application schemas

and feature catalogues Shared application schemas Consolidated model repository Multiple representation Extension points

Identifier management Consistency between data Data and information quality Metadata Conformance Data capturing rules Data transformation guidelines Rules for data maintenance Portrayal Data delivery


TG & IR


IR & TG development cycle


IR & DS development cycle


Cross-theme data interoperability

TN:Transport

networks

EL:Elevation

BU:Buildings

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

Waste

Reporting


Conceptual data models Registers

• objects types, properties & relationships

• cross-domain harmonization

• based on a common modelling framework

• managed in a common UML repository

Harmonised vocabularies

• to overcome interoperability issues caused by free-text and/or multi-lingual content

• allow additional terms from local vocabularies

Encoding

• conceptual models independent of concrete encodings

• standard encoding: GML, but also possible to derive other encodings (e.g. based on RDF)

• provide unique and persistent identifiers for reference to resources

• allow their consistent management and versioning

Key pillars of data interoperability


Conceptual data models Registers

• objects types, properties & relationships

• cross-domain harmonization

• based on a common modelling framework

• managed in a common UML repository

Harmonised vocabularies

• to overcome interoperability issues caused by free-text and/or multi-lingual content

• allow additional terms from local vocabularies

Encoding

• conceptual models independent of concrete encodings

• standard encoding: GML, but also possible to derive other encodings (e.g. based on RDF)

• provide unique and persistent identifiers for reference to resources

• allow their consistent management and versioning

Key pillars of data interoperability

described in INSPIRE Conceptual Framework documents

D2.6:Methodology for Specification

DevelopmentD2.10.3: Common

data modelsD2.9: O&M Guidelines

D2.5: Generic Conceptual Model

D2.7: Guidelines for Encoding

How to read the data specifications

ForewordGeneral Executive SummaryTheme-specific Executive Summary1. Scope2. Overview (incl. 2.2 informal description)3. Specification scopes4. Identification information5. Data content and structure

5.2 Basic notions5.3 – 5.x Application schemas (incl. UML diagrams and feature catalogues)

6. Reference Systems


7. Data Quality7.1 DQ Elements7.2 Minimum DQ requirements and recommendations

8. Metadata8.1 Additional requirements and recommendations for MD elements defined in the MD Regulation 8.2 MD Elements for interoperability8.3 Recommended theme-specific MD elements

9. Delivery (incl. Encodings)10. Data Capture11. Portrayal (incl. layers, styles)

Annex A: Abstract Test SuiteAnnex B: Use casesAnnex C: Code list valuesOther Annexes (e.g. examples)



Data specification thematic extensions+ G

eoSc

iML

+ C

ityGM

L

INSPIRE Annex III Themes

INSPIRE data application schemas

INSPIRE Data specifications contain 138 Use cases138 Use cases

INSPIRE Data specifications contain 138 Use cases138 Use cases

+


UML class diagram: example

INSPIRE UML class diagram for administrative units

class Administrativ eUnits: Ov erv iew

«codeList»Administrativ eHierarchyLev el

+ 1stOrder+ 2ndOrder+ 3rdOrder+ 4thOrder+ 5thOrder+ 6thOrder

«featureType»Administrativ eBoundary

+ country :CountryCode+ geometry :GM_Curve+ inspireId :Identifier+ nationalLevel :AdministrativeHierarchyLevel [1..6]

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

«voidable»+ legalStatus :LegalStatusValue = "agreed"+ technicalStatus :TechnicalStatusValue = "edge-matched"

«featureType»Administrativ eUnit

+ country :CountryCode+ geometry :GM_MultiSurface+ inspireId :Identifier+ name :GeographicalName [1..*]+ nationalCode :CharacterString+ nationalLevel :AdministrativeHierarchyLevel

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

«voidable»+ nationalLevelName :LocalisedCharacterString [1..*]+ residenceOfAuthority :ResidenceOfAuthority [1..*]

constraints{CondominiumsAtCountryLevel}{AdmininstrativeUnitHighestLevel}{AdministrativeUnitLowestLevel}

«dataType»ResidenceOfAuthority

+ name :GeographicalName

«voidable»+ geometry :GM_Point

+admUnit«voidable»

1..*

+boundary«voidable»

1..*

+/administeredBy«voidable» 0..*

+coAdminister«voidable» 0..*

+lowerLevelUnit«voidable» 0..*

+upperLevelUnit«voidable» 0..1


• AU• CP• EL• …

INSPIRE Data specifications - examples


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

• Schemas

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


Thank you for your attention!

Vlado Cetl

[email protected]

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

(3) data scope in inspire

Documents