HUMBOLDT GeoModel Editor

advertisement
0
HUMBOLDT
Principles of Data Modeling and Harmonisation
in Connection with ISO/TC211 and INSPIRE requirements
Dr. Christine Giger (Swiss Federal Institute for Technology and Giger GeoIT)
HUMBOLDT Scientific Manager and Member of the Executive Board
Swiss National Contact Point for INSPIRE
Athens, Greece, March 28, 2011
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
1
HUMBOLDT and INSPIRE
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
2
HUMBOLDT activities in relation to INSPIRE processes
HUMBOLDT
is a registered SDIC
participates regularly in consultation and review processes
participated in the testing phase of Annex I specifications
provides input (e.g. example data specifications) through scenarios
provides knowledge on data harmonisation processes
INSPIRE
Relies on ISO/TC211 19100 standards series
 UML and OCL restricted to GML Schema
 OGC-based definitions for discovery, download and view services
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
3
HUMBOLDT components in INSPIRE
HUMBOLDT HUMBOLDT
CST
Mediator
HUMBOLDT
Alignment
Editor
HUMBOLDT
GeoModel
Editor
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
4
“Non-technical” Results of HUMBOLDT
“For Knowledge itself is power”
Francis Bacon, 1598
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
5
Knowledge and Experiences gathered in HUMBOLDT
Best practices and guidelines for the process of harmonisation of
data models (schema translation)
.
Testing and evaluation of existing approaches and tools for data
model creation (data specification) and harmonisation
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
6
HUMBOLDT’s notion of Geodata Harmonisation
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
7
Data harmonisation processes
Technical Process
Source
Source
Processing
Source
Processing
HUMBOLDT Framework
Processing
Target
Harmonised geodata
Target Definition
Decision-based
specifications
National Data Sources
Technical
specifications
Applications based on
different themes
on the same theme,
e.g. parcels
INSPIRE
HUMBOLDT Workshop HCMR, Athens, March, 2011
HUMBOLDT Scenarios
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
8
Implication for HUMBOLDT: Technical processing of data
Original data in
source model
Original data in
internal model
Goal:
Application expert is able to
specify the mapping
Goal:
HUMBOLDT Software is able to
Processed data in
target model
Processed data in
internal model
perform the processing automatically
based on the mapping specification
Processing chain
(edge matching, schema translation, coordinate transformation, etc.)
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
9
Requirements from
different sources
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
10
Data Harmonisation Issues in HUMBOLDT Scenarios
DHDN/GK Zone 3
1:25:000
DHDN/GK Zone 4
1:25:000
Different CRS,
data models and
Scales in the
Lake Constance
Region
Baden-Wuerttemberg
Bavaria
Vorarlberg
Switzerland
MGI (Ferro) Austria GK
West Zone
1:50:000
CH 1903 LV03
1:25:000
Data sources:
© Bayerische Vermessungsverwaltung
© Landesamt für Geoinformation und Landentwicklung Baden-Wüttemberg
© Land Vorarlberg
© swisstopo
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
11
Data Harmonisation Issues in HUMBOLDT Scenarios (III)
Multiple representation
(detail of image on previous
slide)
River Leiblach
Partly problem of coordinate
transformation
Partly offset correction
needed
Partly different geometry
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
12
Data Harmonisation Issues in HUMBOLDT Scenarios
Examples from the Scenarios’s requirements list
 geodata formats
 coordinate reference systems
 conceptual schemas (data models)
 classification schemes
 scales / resolutions / level-of-detail
 metadata profiles
 natural languages
 multiple representation of the ‘same’ spatial objects
 spatial consistency issues at the border (edge-matching etc.)
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
13
Introduction to
HUMBOLDT Approaches
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
14
Functionalities for covering the geodata harmonisation
process as a whole
Executed technical processes
Source
Schema
Transf.
Analysis of
sources
Edge
Matching
Input for
transformation
(mapping
rules)
…
Target
Creation
of target
User knowledge
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
15
Process Step: Creation of Target
Defining the information product (target schema, SRS, spatial extent, …) to
which the processed data needs to be transformed
Target
Creation
of target
User knowledge
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
16
Real World
HUMBOLDT
Spatial Modelling
Language
(restricted UML)
Conceptual
Model
derive
HUMBOLDT
GeoModel Editor
GML Schema
INTERLIS
Logical/Physical
XMI
Model
instantiate
Database/
Transfer Format
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
17
The problem in the
ISO/INSPIRE Modelling
Methodology:
Screenshot of Enterprise
Architect:
Choice of basic elements
for the definition of data
models
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
18
The Problem in the Modelling Methodology:
Theory
INSPIRE
/ISO set of
Modelling
Elements
Interfaces
support
all the
elements
Reality
HUMBOLDT
Approach
Software A
supports
subset A
Software B
supports
subset B
Software C
supports
subset C
Mandatory
for all
interfaces
HUMBOLDT set of
Modelling Elements
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
19
The HUMBOLDT Metamodel
HUMBOLDT
Modelling language
(HML) based on
concepts of the
INTERLIS
conceptual schema
language (experiences
from over 20 years of use
for >>100 geodata
models)
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
20
Screenshot of INSPIRE version of Geomodel Editor:
actually used elements (metamodel) for INSPIRE data
models
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
21
List of actually used elements for INSPIRE data models
Stereotypes
Types
• on Classes
• InspireID
• BeginLifespanVersion
• EndLifespanVersion
• NetworkModel (Link,
–DataType
–FeatureType
–Enumeration
–CodeList
• on Attributes
–Voidable
DirectLink, ...)
• on Relations
–voidable
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
22
List of actually used elements for INSPIRE data models
Datatypes from ISO
Datatypes from ISO
ISO-19107
ISO-19103
• GM_Object
• GM_Envelope
• GM_Primitive
• GM_Point
• GM_Curve
• GM_Surface
• GM_MultiSurface
HUMBOLDT Workshop HCMR, Athens, March, 2011
• Measure (Area, Length, Velocity)
ISO-19139
• LocalisedCharacterString
• MD_Metadata
• MD_Resolution
• CI_ResponsibleParty
• CI_Citation
• TM_OrdinalEra
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
23
Currently two versions of the GeoModel Editor
HUMBOLDT GeoModel Editor supports
•
•
•
HUMBOLDT Modelling Language HML
(horizontal) transformations HML  ISO/TC211 UML
(vertical) transformations HML  GML 3.2.1
HUMBOLDT INSPIRE Editor (current version of the GeoModel Editor on
the community website)
•
Supports INSPIRE UML (subset of UML as used in Annex I
specifications)
•
Allows transformations UML  GML 3.2.1
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
24
Process step 2: Schema to Schema Mapping
Source
?
Target
Input for
transformation
(mapping
rules)
User knowledge
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
25
Necessary Schema Mapping Operations
•
Filtering: conditional statements applied to source data to filter
features (extract sub-sets)
•
•
•
•
•
•
•
•
Reclassification of attribute values
Renaming of feature classes or attributes
Merge / split of features or attributes
Change of attribute order
Type conversions
Value conversions
Reclassification
Augmentation
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
26
Real World
Real World
Conceptual
Model A
Conceptual
Schema
Mapping
derive
Logical/Physical
Model A
derive
Schema
Transformation
instantiate
Database A/
Transfer Format A
HUMBOLDT Workshop HCMR, Athens, March, 2011
Conceptual
Model B
Logical/Physical
Model B
instantiate
Instance
Transformation
Database B/
Transfer Format B
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
27
Real World
Real World
HUMBOLDT Alignment Editor
use
Conceptual
Model
derive
Logical/Physical
Model
create
Conceptual
Schema
Mapping
derive
Schema
Transformation
instantiate
Database/
Transfer Format
HUMBOLDT Workshop HCMR, Athens, March, 2011
use
Conceptual
Model
derive
Logical/Physical
Model
instantiate
Instance
Transformation
Database/
Transfer Format
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
28
Real World
Real World
Conceptual
Model
Conceptual
Schema
Mapping
derive
Conceptual
Model
derive
use
Logical/Physical
Model
instantiate
Database/
Transfer Format
Schema
Transformation
derive
Instance
Transformation
Logical/Physical
Model
instantiate
Database/
Transfer Format
execute
HUMBOLDT Conceptual Schema Transformer
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
29
HUMBOLDT Components Development
•
Conceptual schema transformer (CST) is supposed to handle GML
input and output
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
30
HUMBOLDT Components Development
•
•
Originally based on GML 2.1.2 input and GML 3.1 output
Resulted in stable software (still some problems with vendor-specific
extensions of GML)
•
usage of GML 3.2.1 caused major problems in implementing reading
and writing functionality for HUMBOLDT mediator and CST
•
vast majority of existing GML 3.2.1 encodings are not valid
•
in many cases they are not even valid XML Schemas
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
31
HUMBOLDT Components Development
•
Solution for conceptual schema transformer
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
32
HUMBOLDT Components Development
Solution for the HUMBOLDT Alignment Editor HALE (status March 2011)
•
•
Own development for GML 3.2.1 input and output
Built-in functionality for the transformation execution
But HALE was designed for the specification of the transformation and
only for executing the transformation on a small amount of example
data
•
•
Huge datasets may not work with HALE as a stand-alone tool
A new version of CST with GML 3.2.1 input and output is still under
development
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
33
Metadata
•
In HUMBOLDT an INSPIRE-compliant profile of ISO19115/19139 was
created and used in all Scenarios
•
In many applications metadata exists, but is not INSPIRE-compliant
• HALE is also able to handle usual XML Schemas (not only GML) in order
to support Metadata transformations
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
34
Thank you for your attention!
HUMBOLDT Workshop HCMR, Athens, March, 2011
© 2011 HUMBOLDT Consortium Fraunhoferstraße 5 64283 Darmstadt http://www.esdi-humboldt.eu
Download