INSPIRE Data Specifications.pdf - INSPIRATION

INSPIRE Data Specifications

2 

Data Specifications 

11:00 - 13:00 

INSPIRE Data Specifications 

Detailed Introduction to the INSPIRE Data Specifications 

> general structure of the data specifications 

> the UML model and the GML-schemas 

> generic conceptual model and ISO 

Introduction of specific INSPIRE data specifications 

> Cadaster - Sören 

> Buildings - Christian 

© con terra GmbH, 2011

3 

Data Specifications 

14:00 - 15:30 


Practical example - Mapping Protected Sites 

> Defining the semantic mapping 

> Establishing the data transformation process (using FME) 

Publishing Services with ArcGIS for INSPIRE 

Demonstration – Mapping Administrative Units 

> Transforming data from shape files to an INSPIRE Database using 

FME 


4 

Short Introduction 

Sören Dupke 

> Diploma in Geoinformatics 

> 1 year at SDI Unit at the JRC 

> Since 2010 FME Professional Services 

> Training & Consulting 

> INSPIRE Solution Pack 

> FME Certified Trainer 

> Focus on INSPIRE data harmonization PSprojects 


INSPIRE Projekte in den letzten 6 Monaten

6 

5 

4,5 

4 

3,5 

3 

2,5 

2 

1,5 

1 

0,5 

0 

INSPIRE Mapping mit dem ISP4FME < 5 Consulting-Tage 

© con terra GmbH, 2011 

HY Hydrography 

TN Transportation Network 

HB Habitate 

BR Biographical Regions 

SD Species Distribution 

AD Adresses 

CP Cadastral Parcels 

PS Protected Sites 

AU Administrative Units

7 

con terra GmbH, Münster 

Since 1993 

Spin-off from University of 

Münster, Institute for 

Geoinformatics 

Since 2006 ESRI-DE main 

shareholder 

About 90 Employees 


100% GIS 

> Consulting and Services 

> Development of Standards, 

Services and Spatial Data 

Infrastructures 

> FME European Resource 

Center

8 

Overview INSPIRE Data Specifications 

QUESTIONS: 

> Whats part of the data specifications? 

> Whats important for the harmonization process? 

> How are the data specifications developed and maintained? 

> Relationship between GML, UML, XSD? 

Focus on data harmonization 


9 

Elements of the INSPIRE Data specifications 

Data models for the Annex Themes 

> UML-Models 

> GML-Application Schema 

Framework Documents 

> Generic Conceptual Model 

> Relevant for all Annex themes 

Guidance Documents 

> Textual descriptions of the Data Models (PDF-Documents) 

> Other Documents 

Available here: 

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


10 


11 

Which documents are relevant?sind relevant? 

Annex 1 Themes 

> Addresses Units 

> Cadastral Parcels 

> Geographical Names 

> Hydrography 

> Protected Sites 

> Transport Networks 

Additional Documents 

> Specification on coordinate reference systems and geographical grid 

systems 

> Generic Conceptual Model 

> Guidlines for the Encoding of Spatial Data 


12 

Generic Conceptual Model 

Contains components relevant for all Annex Themes 

> Identifier 

> Network Model 

> Life-Cycle aspects of spatial data 

> Gazetteer Model 

> Lists 

> z.B: Country Codes 

> Void Reason Values 

Defines Requirements for the annex theme data specifications 

> 76 requirements 

> 38 recommendations 


13 


Data harmonization aspects from the GCM 

14 



15 



16 



17 


18 



19 



20 



21 

Data specifications for the Annex Themes 

Describe the UML model which is the formal base 

Developed according to „Methodology for the development 

of data specifications“ togehter with the UML Model 


22 


23 

Requirements and Recommendations 

Requirements 

> Rules that have to be applied 

Recommendations 

> Non-mandatory recommendations 

Important: R&R from the GCM aply as well 


24 

Structure : INSPIRE Data specifications (1/3) 

Foreword 

General Executive Summary 

Theme specific executive summary 

1. Scope 

2. Overview (2.2 informal description) 

3. Specification Scopes 

4. Identification information 

5. Data content and structure 

> 5.1 Basic notations 

> 5.2 – 5.x Application schemas (UML diagrams and feature catalog) 

6. Reference Systems 


25 


7. Data quality 

> 7.1 DQ Elements 

> 7.2 minimum DQ elements 

8. Metadata 

> 8.1 Common MD elements 

> 8.2 MD elements for Data quality 

> 8.3 Theme specific MD elements 

> 8.4 Guideline for common elements 

9. Delivery 


26 


10. Data capture 

11. Portrayal 

Annex A: ATS 

Annex B: Use Cases 

Other Annexes 

> E.g.: Examples 


27 

Chapter 5 

Central Chapter of each specification 

Two parts 

> Basic notations 

> Detailed description of the Application Schema 


28 

5.1 Basic notions 

Repeat relevant parts of the Generic Conceptual Model 

> Voidable properties 

> CodeLists and Enumerations 

> Used Stereotypes 

> Placeholder and candidate types 


29 

5.2 Applikation Schemas 

Neccessary information to understand the formal UML 

Model 

UML Diagrams 

Textual Descriptions 


30 


31 


32 

Feature Catalog und Spatial Object Catalog 


33 

Annexes 

Examples 

Tests 

Prototypes of Annex II & III data models 

Use Cases 


34 


35 


36 


37 

How are the data specifications developed and maintained? 

Aim to achieve the right level of complexity.. 


38 

How are the data specifications developed and maintained? 


TWG TWG TWG 

INSPIRE DS Drafting Team 

Third parties: ISO, etc..

39 

Relationship between GML, UML, XSD? 

Encoding rule to 

create the GML application 

schema 


GML application 

schemas (XSD) 

Encoding when provided via Services 

INSPIRE 

Application 

schemas 

Other encoding rules to 

create e.g. geodatabase 

schema 

Geodatabase 

(GDB-XML) 

Workspace 

Document 

Encoding for Storage

40 

Conclusion 

Role during the harmonization process 

> Describe the target model 

> Additional requirements like data qulity and maintenence 

> Reference text 

> Provide orientation 

> Sometimes thid party information is needed 


INSPIRE Data Specification – Cadastral 

Parcels

42 

Data Specification – Cadastral Parcels 

11:00 - 13:00 


Detailed Introduction to the INSPIRE Data Specifications 

> general structure of the data specifications 

> the UML model and the GML-schemas 

> generic conceptual model and ISO 

Introduction of specific INSPIRE data specifications 

> Cadaster – Sören Dupke 

> Buildings – Christian Ansorge 


43 

Scope 

The scope of the cadastral information in the INSPIRE context is limited 

to the geographic side of the cadastral information systems (land 

administration) and does not cover the administrative or legal side, with 

objects such as rights and persons. However, a parcel has strong 

associations with these objects as its definition is based on this. 


44 

Background: all countries run a register 

> Usually a partition of the country with exceptions 

Basic unit of the system is the parcel 

the cadastral parcels should be, as much as possible, single areas of 

Earth surface (land and/or water) under homogenous real property 

rights and unique ownership, where real property rights and ownership 

are defined by national laws. 

Focus on geometries not on legal system 

INSPIRE data serves to locate information , referencing the national 

registers 


45 

Basic unit parcel 

Subdivision (municipalities,sections,districts,parishes,urban or 

rural blocks, etc) 

> Carry information for the parcels inside the subdivision: accuracy or 

scale 

Cadastral boundaries 

> Only neccessary if spatial accuracy is associated with them 


46 

Requirements on minimal data quality 

Rate of missing elements, accuracy and update frequency 

Accuracy on three levels possible: 

> Statement for the whole dataset 

> Attribute on the cadastral zonings or boundaries 


47 

Cadastral gap 

Cadastral overlap 

Topological gap 

Topological overlap 


48 

beginLifeSpanVersion – endLifespanVersion 

validFrom – validTo 

Feature Types: 

> CadastralParcel (mandatory) 

> CadastralZoning (auxiliary) 

> CadastralBoundary (auxiliary) 

> BasicPropertyUnit (auxiliary) 


49 


50 

Core profile 


51 


52 


53 


54 


55 

CadastralParcel - Attributes 

areaValue 

beginLifespanVersion 

endLifespanVersion 

Geometry 

Inspireid 

label 

nationalCadastralReference 

referencePoint 


56 

Geometry 

0-, 1-,2-, 2.5 dimensional geometries 


57 


58 


59 


60 


61 

Data Quality 

Has to be documented 

Recommendations 

Positional Accuracy 

Completeness 


62 

Hitting the Target of INSPIRE complaint Services for “Protected Sites” 

State Office for Nature, Environment, and Consumer NRW 

con terra GmbH 


63 

Data Specification – Cadastral Parcels 

14:00 - 15:30 


Practical example - Mapping Protected Sites 

> Defining the semantic mapping 

> Establishing the data transformation process (using FME) 

Publishing Services with ArcGIS for INSPIRE 

Demonstration – Mapping Administrative Units 

> Transforming data from shape files to an INSPIRE Database using 

FME 


64 

North RhineWestphalia State Agency for Nature Environment 

and Consumer Protection 

Main activities… 

advise and support the state government and enforcement agencies 

cooperate with national and international scientific institutions 

keep the public informed 


65 

Project Goals 

PPP Project (public private partnership) 

Proof of concept of creating a INSPIRE ProtectedSites GML Dataset 

Describe the semantic mapping and a schema translation workflow 

Providing Data as a INSPIRE View and Download Service 


Project Approach 

66 

INSPIRE Solution Pack 

for FME 

Internal Information-/ 

Data Management System 


ETL 

ArcGIS for INSPIRE 

European 

SDI 


Data Models & Services 

Consumer

67 

Source: OSIRIS data 

ESRI Shapes files representing the geometry 

Non spatial data separated in 2 databases and about 200 tables 


68 


69 


70 


71 


Workflow 

72 


for FME 




ETL 


European 

SDI 



Consumer

73 

Geodatabase as Target Data model 

Encoding rule to 

create the GML application 

schema 


GML application 

schemas (XSD) 

Encoding when provided via Services 


Application 

schemas 

Other encoding rules to 

create e.g. geodatabase 

schema 

Geodatabase 

(GDB-XML) 

Workspace 

Document 

Encoding for Storage

74 

INSPIRE Geodatabase 

276 tables 

> 224 tables 

> 46 feature classes 

Why so many? 

> Geometry model 

> Object oriented vs. Relatinal model 


75 

Additional Tables for attribute with multiplicity > 1 

Multipliplicity in XML achieved by number of elements 


 

001 

Münster 

Muenster 

4thOrder 

 

 

002 

München 

Muenchen 

4thOrder 

76 

In the database 


1:1 

 

001 

Münster 

Muenster 

4thOrder 

 

 

002 

München 

Muenchen 

4thOrder 

 

1:n 

Table: AdministrativeUnit 

Id Level Attribut 

1 4thOrder … 

2 4thOrder … 

Table: AdministrativeUnit_Name 

ID RID Name 

1 1 Münster 

2 1 Muenster 

3 2 München 

4 2 Muenchen

77 

N:M Relations 


78 

N:M Relations 

 

001 

Münster 

Telgte 

… 

 

< AdmBoundary> 

002 

Münster 

Coesfeld 

… 

 


 

001 

Münster 

001 

002 

… 

 

 

002 

Telgte 

001 

004 

… 

79 

Relationship Tables 

 

001 

Münster 

Telgte 

… 

 

< AdmBoundary> 

002 

Münster 

Coesfeld 

… 

 


ID ID1 ID2 

1 1 1 

2 1 2 

3 2 1 

4 4 2 

 

001 

Münster 

001 

002 

… 

 

 

002 

Telgte 

001 

004 

… 

 

Table: adAdmBoundary_AdmUnit_RelationShip

81 

Initial situation of INSPIRE schema mapping 

INSPIRE expert knowledge and domain expertise are required 

High complexity of the source data and the INSPIRE destination model 

It has to be accounted for local characteristics (quality, history, contents) 

- Internal data models 

- Meta data 

- Data history 

- Data quality 

- Expertise (Domain) 


INSPIRE Solution Pack for 

- INSPIRE data models 

- INSPIRE specifications 

- INSPIRE legislation 

- INSPIRE requirements 

- Expertise (Annex 1)

82 

ETL-Technology as a base for the INSPIRE Mapping 

FME Mapping Process 

Extract 

source data 

Example Mapping 


Transform to destination schema 

data fusion 

and restructuring 

plausibility checks 

Updating process 

and automation 

Load 


database

Data model as a common base 

83 

INSPIRE Solution Pack for FME 




ETL 



European 

SDI 

Consumer

INSPIRE ETL Workflow Description 

84 

Import 

source 

schema 

simplify INSPIRE mapping 


Use ESRI 

INSPIRE GDB 

schema 


Solution Pack 

Schema 

transformation 

and mapping 

Load data 

into ESRI 

INSPIRE GDB

85 

ETL with INSPIRE Solution Pack for FME 

Connection Predefined INSPIRE to individual template source Workspaces data situation per Annex theme 


individual mapping 

predefined mapping

89 

INSPIRE Protected Sites – Full Schema (Template) 


90 

Main Mapping Challenges 

Complex Source Data Modell 

> Domain knowledge from the customer (LANUV) needed 

> INSPIRE GDB knowledge from con terra 

Complex Destination Modell 

> INSPIRE Protected Sites full 

Information Exchange 

> simple excel sheet with attributes 

> many iterations 


91 

Attribute Mapping (domain knowledge exchange) 


INSPIRE OSIRIS mapping with FME 

92 

Aufgrund der vielen Quelldaten komplex 


93 

Mapping in Two Steps 

Custom OSIRIS Reader >>> restructure and fusion of source data 

> Result: feature structure close to INSPIRE 

Mapping with INSPIRE Solution Pack for FME template >>> attribute 

and value Mapping 

> Result: INSPIRE compliant data 

Custom Reader 

for OSIRIS FFH 


Mapping for 

INSPIRE GDB 

Modell

94 

INSPIRE Mapping with Template Workspace 

Lower Complexity of FME Workbench 

Reusable OSIRIS reader 


95 

Result: Filled ArcGIS for INSPIRE GDB 


96 

1 

„3 Steps“ to create a INSPIRE View and Download Service… 

Define 

ANNEX-Theme Layer 

ArcMap 


2 3 

Create Map 

Document (mxd /msd) 

ArcMap 

ArcCatalog/ 

ArcGIS Server 

Publish Map Document 

INSPIRE View Service

Complex Relational Model in ArcGIS Desktop Environment 

97 


98 

Reference Object used in ArcGIS Desktop 


Workflow 

99 


for FME 




ETL 



European 

SDI 


Consumer

100 

Result from INSPIRE-Download Service (Filter Operation) 


101 


ProtectedSites View Service Geoportal of it.nrw 

Film

104 

The tip of the iceberg Model 

XML 

Validation 

existing 

Feature 

UML / GML 


XSD 

Schema 

FME feature based mapping 

complex things are hidden 

INSPIRE Solution Pack for FME 


Data Validation 


Feature 

Feature 

Relations 

Database 

Design

105 

Thank you for your attention! 

con terra – 

Gesellschaft für Angewandte 

Informationstechnologie 

Martin-Luther-King-Weg 24 

48155 Münster 

Telefon +49 251 747 45 0 

Telefax +49 251 747 45 2111 


Nyon 

Bonn 

Burgdorf 

Münster 

Wiesbaden 

Zürich 

Hamburg 

Hannover 

Kranzberg 

Leipzig

INSPIRE Data Specifications.pdf - INSPIRATION

Create successful ePaper yourself

Delete template?

Save as template?