INSPIRE-compliant and easy-to-use GeoModel...

INSPIRE-compliant and

easy-to-use GeoModel Editor

Jan Schulze Althoff

Dr. 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 A

Software 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 geodatamodels)

HUMBOLDT GeoModel Editor

• Process Optimisation for Spatial Modelling (for theHUMBOLDT 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?


Simplified UML – GFM

• Only simplified UML Class Diagrams– No Interfaces

– No Functions

– Only single Inheritance

– No Association Classes

– No „Realize“ Association

– Limited Package Nesting

• Including the Stereotypes of ISO/TC-211– FeatureType / DataType

– Enumeration /Codelist /…

• Including Stereotypes of INSPIRE– voidable

– lifeCycleInfo


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


Simplified Imports

• Used Imports / External Types (Annex I)

– Standards ISO-19103, 19107, 19108, 19111, 19115,

19133, 19139

– Only around 25 Types used

– „Exotic“ TM_OrdinalEra (ISO-19108),

LR_PositionExpression (ISO-19133)


Simplified Imports

• Suggested List of External Types

– ISO-19103 „Schema Languge“

• 26 elements of „Basic Types – Primitives“ (Decimal, Integer,

DateTime, CharacterString, …)

• 29 elements of „BasicTypes – Derived“ (Units of Measure –

Angle, Area, Distance, …)

• 9 elements of „BasicTypes – Implementation“ (Names –

GenericName, LocalName, …)


Simplified Imports

– ISO-19107 „Spatial Schema“

• GM-Object, Direct Position

• GM_Primitive, GM_Point, GM_Curve, GM_Surface, GM_Solid

• GM_Aggregate, GM_MultiPoint, GM_MultiCurve,

GM_MultiSurface, GM_MultiSolid

• GM_Complex, GM_Composite

– ISO-19108 Temporal Schema

• TM_Primitive, TM_Period, TM_Duration, TM_PeriodDuration


Simplified Imports

– ISO-19115 „Metadata“

• MD_Metadata

• Extent Information: EX_GeographicExtent,

EX_TemporalExtent, EX_VerticalExtent

• Citation: CI_Citation, CI_ResponsibleParty, CI_ Contact,

CI_Address, URL

– ISO-19133 „Tracking & Navigation“

• Linear Referencing: LR_PositionExpression

– ISO-19139 „Metadata XML Implementation“

• LocalisedCharacterString, PT_FreeText, URI


Snapshot

INSPIRE

GeoModel

Editor

- 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)


- The predefined simple types from the ISO models can be accessed easily in

dropdown menues)


- The predefined stereotypes for attributes and associations


- 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 handled

2. No real UML Profile is defined

3. Enterprise Architect XMI is not directly compatible

with XMI for Eclipse based tools


Problem: The Integration

Models are simply too large

to be handled

• Reducing the „Foundation

Schemas“ to a minimum



No real UML Profile is

defined

• Defining a profile

• Applying each stereotype

manually



Enterprise Architect XMI is not directly compatible with XMI for Eclipse based tools

• Using Eclipse Modelling Project (Model Transformation)

• Utilising UML2EA Tools (http://uml2ea.blogspot.com/)

-> works, but complex to configure


The Integration – Step 1

From Enterprise Architect to Eclipse


The Integration – Step 2

From 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


Open Issues

• Transformations

– Simple Enterprise Architect – Eclipse Process

– Enhance Eclipse UML – INSPIRE Model Editor

– Reverse Transformation INSPIRE Model Editor – Eclipse

UML

– Methods to synchronise Model Elements


Open Issues

• Usability

– Tool Integration

– Create Help

– Create Documentation

– Create «Cheat Sheets»

– Model Versioning


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


INSPIRE-compliant and easy-to-use GeoModel...

Documents

Transcript of INSPIRE-compliant and easy-to-use GeoModel...