INSPIRE-compliant and easy-to-use GeoModel Editor Jan Schulze Althoff Dr. Christine Giger Prof. Dr....

INSPIRE-compliant andeasy-to-use GeoModel Editor

Jan Schulze AlthoffDr. Christine Giger

Prof. Dr. Lorenz Hurni

Overview

• About Modelling• HUMBOLDT GeoModel Editor• INSPIRE GeoModel Editor• Linking Enterprise Architect

INSPIRE Conference Edinburgh, 27.6.-1.7.2011, Dr. C. Giger 2

About Modelling

• Why do we generate data models using a CSL (conceptual schema language), e.g. UML?1. Support of users/thematic experts:

Specify structure and content of the data independent from a specific implementation

2. Facilitate implementation:CSL elements to be used in all interfaces and subsequent processing software, e.g. for data harmonisation


HUMBOLDT Project: Problems in the Modelling Methodology

INSPIRE Conference Edinburgh, 27.6.-1.7.2011, Dr. C. Giger

INSPIRE /ISO

set of

Modelling

Elements

HUMBOLDT set of

Modelling Elements

Interfaces

support all

the

elements

Theory Reality

Software A

supports

subset ASoftware B

supports

subset B

Software C

supports

subset C

Mandatory for

all interfaces

One possible

solution

4

Small Snippet of UML Metamodel


Why it‘s so huge!

Current Modelling Environment for INSPIRE:•Includes ALL ISO-19xxx packages

– More than 40 Standards– More than 600 Packages– More than 2000 Classes/Types


The HUMBOLDT Metamodel

• Based on concepts of the INTERLIS conceptual schema language (Swiss Standard CSL: experiences from over 20 years of use for >>100 geodata models)

HUMBOLDT GeoModel Editor

• Process Optimisation for Spatial Modelling (for the HUMBOLDT Project)– Integration of Spatial Types– Differentiation of Data Types and Feature Types– Precise, yet flexible Type System– Limitation of Language Elements

• Tool Optimisation for Spatial Modelling– Specific Tool for HUMBOLDT Project– Integrated Validation– Open Processing Capabilities


HUMBOLDT GeoModel Editor

• Drawbacks & Problems– Not 100% interoperable to

ISO/TC-211 flavored UML• Different Concepts for Data Types• Slight differences in Geometry Types


Idea: INSPIRE GeoModel Editor

• Use technique of HUMBOLDT GeoModel Editor

• Adjust to INSPIRE needs• Check interoperability

• Look at Annex I data specs:– Which elements were really used?


Metamodel of INSPIRE GeoModel Editor based on used Elements in Annex I data specifications


Elements exposed to users


Stereotypes for Attributes/Associations


Hidden Primitive Type for Imports


Snapshot INSPIRE GeoModelEditor- INSPIRE Addresses Model

• Detail: Snapshot INSPIRE GeoModel Editor– Palette – Context Sensitive Menu only

allows to add valid elements in the concrete context

• in a package only „DataType“, „FeatureType“, „Enumeration“, „CodeList“ and „ApplicationSchema“

• in fact we should also disallow „ApplicationSchema“ as nesting is hard to implement for subsequent processes

Detail - Snapshot INSPIRE Editor - Context Menu is also working for associations (inheritance, associations, aggregations, compositions or simple text attachments)

Detail - Snapshot INSPIRE Editor - The predefined simple types from the ISO models can be accessed easily in dropdown menues)

Detail - Snapshot INSPIRE Editor - The predefined stereotypes for attributes and associations

Detail - Snapshot INSPIRE Editor - Reuse existing models by importing them into the model (here the AdministrativeUnits model is loaded)

Problem: Process Chain

Import Enterprise Architect UML for Processing with Eclipse Tools

1. Models are simply too large to be handled2. No real UML Profile is defined3. Enterprise Architect XMI is not directly

compatible with XMI for Eclipse based tools


The Integration – Step 1From Enterprise Architect to Eclipse


The Integration – Step 2From Eclipse UML to Inspire Editor

• Model-to-Model Transformation using Eclipse– UML::Package -> INSPIRE::Package

• <<ApplicationSchema>> -> INSPIRE::ApplicationSchema

– UML::Class• <<FeatureType>> -> INSPIRE::FeatureType• <<DataType>> -> INSPIRE::DataType• <<Enumeration>> -> INSPIRE::Enumeration• <<CodeList>> -> INSPIRE::CodeList


Other open Issues

•INSPIRE GeoModel Editor– Work on Model Validation– Include the basic Imports– Enhance Graphics


Conclusions• Was the effort of creating an “INSPIRE GeoModel Editor”

worthwhile?Answer: yes, because1. Support of users/thematic experts:

1. Enterprise Architect with full ISO stereotyping: ?2. HUMBOLDT/INSPIRE GeoModel Editor: easier to use!

2. Facilitate implementation:1. HUMBOLDT/INSPIRE GeoModel Editor: YES!

– Interfaces can easily be generated– Subsequent processing can be supported without any information loss

2. Enterprise Architect with full ISO stereotyping:all interfaces to be generated or direct links encounter the same or even more complexity as we did, when trying to link the two editors

➡ Consequence: nobody uses the UML definition!➡ Instead: the GML definition is used!

This is a fundamental information loss!All the original advantages of the (ISO-based AND IT mainstream) model-driven approach are lost


Some last aspects:

• The work on the HUMBOLDT and INSPIRE GeoModel Editors was carried out in the HUMBOLDT project (6th Framework Programme, www.esdi-humboldt.eu)

• HUMBOLDT and INSPIRE GeoModel Editors are specified on the ECLIPSE Framework

• The PDF Version contains more slides/additional details


http://www.esdi-humboldt.eu/

INSPIRE-compliant and easy-to-use GeoModel Editor Jan Schulze Althoff Dr. Christine Giger Prof. Dr....

Documents

Transcript of INSPIRE-compliant and easy-to-use GeoModel Editor Jan Schulze Althoff Dr. Christine Giger Prof. Dr....