- 88 Views
- Uploaded on
- Presentation posted in: General

GeoUML a conceptual data model for geographical data conformant to ISO TC 211

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

GeoUML a conceptual data model for geographical data conformant to ISO TC 211

Main GeoUML constructs

Novembre 2004

Alberto Belussi

Profiling

Specializing

GeoUML is defined starting from ISO General Feature Model (19109) and from ISO Spatial Schema (19107) by applying the following approach:

General Feature Model (GFM) in UML

Spatial Schema in UML

Subset of the ISO constructs (UML classes)

Specialization of ISO constructs (UML classes + OCL)

Constraints templates and schema templates (UML classes + OCL)

GeoUML

“Segmented” Attribute

Spatial Schema

Geometric Classes in UML (GU_*)

Reference Set of Topological Relations

ISO TC 211

GeoUML

General Feature Model (GFM) in UML

General Feature Model (GFM) in UML

Layer

UML Classes (GM_*)

Structural Constraints

Relate Operators

Topological Constraints

Specialized constructs

DB Schema

DB Content

Feature types and their properties + constraints

Reality: phenomena

Feature instances

- GFM contains the following constructs:
- Feature Type: “a feature type is an abstraction of real world phenomena”
- Attribute: thematic and spatial attributes
- Association between feature types
- Generalization and specialization of feature types
- Constraint

- Basic Rules for representing GFM in UML
- Feature Type: it becomes a UML class
- Attribute:
- a thematic attribute becomes a UML attribute
- a spatial attribute becomes a UML attribute with a spatial type (or an association to a spatial type)

- Association between feature types: it becomes a UML association
- Generalization and specialization of feature types: it becomes a UML inheritance hierarchy
- Constraint: it becomes a OCL (Object Constraint Language) constraint

The formal definition of the GeoUML constructs follows a few general patterns:

- geometric types: specializations of ISO geometric types, adding OCL constraints that restrict the population (objects belonging to the type extension);
- structural constraints: logic formulas with parameters (constraint templates in OCL), that involve the Contains and the Complex association of GM_Complex;
- topological constraints: constraint templates, involving the Relate functions defined on the root class GM_Object of the ISO spatial types hierarchy.

Beyond geometric types, structural and topological constraints GeoUML contains the following additional constructs:

- Structural layers
- Enumerative domains
- Hierarchical enumerative domains
- Primay key constraints
- Segmented and subregion attributes

TP_Object

TP_Primitive

TP_Complex

Geometric types of the Spatial Schema (ISO TC 211)

GeoUML geo-types

GM_Object

GM_Primitive

GM_Complex

GM_Aggregate

GM_Point

GM_Curve

GM_Composite

GM_Surface

New types have been defined as specialization of the basic geometric types of the Spatial Schema (ISO 19107).

In particular, these new types aim to represent:

- homogeneous complexes: the new 2 types “ComplexCurve” and “ComplexSurface” are specializations of the ISO GM_Complex class;
- geometric objects embedded in 2D or 3D spaces: they are a specialization of geometric classes for dealing with the existence of 2D and 3D geometric objects.

GU_CXCurve2D

GM_Complex

GU_CXCurve3D

GU_CXSurface2D

- Motivation of GM_Complex specialization:
- In the IntesaGIS project it was necessary to represent geometries having a shape of dimensionally homogeneous complexes.
- Homogeneous complexes are necessary to express topological relations on complexes, since they admit the definition of a general boundary function.

In GeoUML three classes have been defined as specialization of the GM_Complex class of the Spatial Schema.

Spatial Integrity Constraints have been added to the model because the plain definition of the types of the geometric attributes does not sufficiently specify the spatial properties of the database.

- GeoUML predefines two template for spatial integrity constraints:
- Templates for Structural Constraints
- Templates for Topological Constraints

Structural Constraints rely on the sharing of primitives among complexes (the sharing is based on the Contains association of the GM_Complex class having roles subComplex and superComplex, and on the Complex association).

For example, the constraint

“for each COUNTY there must exist a REGION which contains it”

could be expressed as:

“for each COUNTY C there must exist a REGION R such that Supercomplex(C)=R”.

APPLICATION REQUIREMENT

A road network management system must be designed in which several different networks are defined; the networks can share some roads and can be integrated with some connecting paths which are not classified as roads.

The spatial representation of each network is a collection of curves usually connected in a graph. The roads are described in terms of their centre lines which are all used in building the spatial representation of the related networks.

linear geometry restriction

the instances of the class GM_Complex must be restricted to contain only 1-dimensional geometric objects. and 0-dimensional objects for their boundary.

spatial relationship enforcing: each composite curve representing the geometry of a road belonging to a network in the RoadInNetwork association must also be associated, through the Contains association, to the complex representing the geometry of its network

Pure ISO APPROACH

Pure ISO APPROACH + OCL formulas

GU_CXCurve

It is a specialization of the type GM_Complex that restricts the primitives to be only curves and points;

BelongsTo spatial association between a contained class C1 and a containing class C2,

it imposes to each road of the class Roadrelated to a network of the class RoadNetwork that the geometry of the road (path)is a subcomplex of the geometry of the network (extension).

+net

+roads

GeoUML APPROACH

Template of the BELONGS TO constraint

Application of the BELONGS TO constraint Template

GU_Complex2D

self.CRS = GU_CRS-2D

GM_Complex

GU_Complex3D

self.CRS = GU_CRS-3D

OCL formulas

GeoUML

- each GeoUML schema contains the definition of at least 2 objects of the class SC_CRS (Coordinate Reference System) of ISO 19111 “Spatial Referencing by coordinate”: one for 2D space (GU_CRS-2D) and one for 3D space (GU_CRS-3D).
- In GeoUML for each class imported from the Spatial Schema, two separate classes has been defined, one for each SC_CRS.

GU_Object::planar( ): GU_Object

self.planar() = self.transform(GU_CRS-2D)

OCL formulas

Since it is necessary to express relations between geometric objects embedded in 2D space and geometric objects embedded in 3D space, in each geometric type of GeoUML the method planar is defined. It produces the projection in 2D of the geometric object.

Why is it necessary to predefine a reference set of topological relations?

- very often spatial constraints in an application schema are based on topological relations

- ISO Spatial Schema proposes the “Relate” functions to define topological relations between geometric objects but they cannot be applied to generic complexes.

- OCL expressions using the “Relate” functions are complex and they may depend on the geometric classes of the objects participating to the constraint.

GeoUML contains the set of topological relations defined by Clementini et. al. since:

- this set contains a reduced number of relations,
- these relations are very clear for the end user, since they represent spatial properties that can be found in any natural language
- their definition does not depend on the geometric classes of the objects participating to the constraint.

RELtopo= { disjoint (DJ), touch (TC), in (IN), contains (CT), equal (EQ), cross (CR), overlap (OV) }

Given two geometric values A and B, for which we can compute the interior (A° e B°), the following topological relations can be defined:

- (A Disjoint B) def (A B = )
- (A Touch B)def (A° B° = ) and (A B )
- (A In B)def (A B = A) and (A° B° ) and (A B B )
- (A Contains B)def (B In A)
- (A Equal B)def (A B = A) and (A B = B)
- (A Overlap B)def (A° B°) and (A B A) and (A B B)
where indicates the set intersection between two point sets.

Other relations:

(A Cross B) def (A Overlap B) and (dim(A)=1) and (dim(B)=1) and (dim(A° B°)= 0)

(A Intersects B) def (A B ) and not (A Equal B)

cRelate (a, b, M(a,b)): boolean

M(a,b) =

Definition of the set RELtopo using OCL + cRelate

- Problems:
- cRelate can be appled to primities, composites and to homogeneous complexes, as stated explicitly in the standard documents,
- the function boundary for the GM_Complex has not been defined in details by the standards,

we introduced an explicit set of classes for representing homogeneous complexes and we gave the formal definition of boundary for these classes.

for each object c, instance of class C,

there must exist an object d, instance of a class D, such that

the topological relation R(c,d) is true

The basic idea of a topological constraint applied to a class C is to express the fact that:

for each object d, instance of a class D,

For example, the constraint

“for each PROVINCIA there must exist a REGIONE which contains it”

could be expressed as

“for each PROVINCIA P there must exist a REGIONE R such that CONTAINS(R,P)”

- The variety of constraints is determined by:
- the set of topological relations

- different possibilities of selecting the objects of C and the objects of D

- the possibility to refer to geometric functions, like boundary and planar, in the expression of the relation (e.g. dam.planar in lake.boundary)

- the possibility to couple a constraint with an association between the classes that participate to the constraint

- the possibility of computing the union of the geometric objects of D before testing the relation
- the possibility of substituting the existential quantifier with a universal quantifier

Town

Traffic Element

Traffic Area

Railway Station

Example

OVERVIEW OF GeoUML

- Specialization of the geometric types of the Spatial Schema
- Structural constraints
- Definition of topological relations also for complexes (dimensionally homogeneous complexes)
- Topological constraints
- “Segmented” attributes and “Subregion” attributes
- Layers

- GeoUML contains two kinds of predefined schemas for representing “segmented” attributes:
- structural segmented attributes: in this case the geometry of each homogeneous segment is explicitly generated; homogeneous segments are segments with the same value with respect to the segmented attributes of the class that we choose to represent together;
- dinamic segmented attributes: in this case, in the class where the attribute is defined, a linear reference system is generated and the values of the segmented attributes can be defined on this linear reference system by means of linear or point events.

Structural segmented attributes:

Dinamic segmented attributes:

Primitives are geometric objects representing OPEN connected pointsets. GM_Primitive is the parent node of three classes: GM_Point, GM_Curve and GM_Surface.

GM_Point

GM_Curve

GM_Surface

Composite objects are set of primitives representing a primitive decomposed in its components (structure).

They represent CLOSE connected pointsets. They are always dimensionally homogeneous.

GM_CompositeCurve

GM_CompositeSurface

- Complex objects are set of primitives satisfying the following spatial constraints:
- the primitives belonging to a complex are disjoint
- if a primitive belongs to the complex also its boundary belongs to the complex

- They allow the sharing of geometry.

Aggregate objects are sets of primitives with no constraints.

non dimensionally homogeneous

dimensionally homogeneous

GU_CXCurve2D

GM_Complex

GM_CompositeCurve

GU_CXSurface2D

GU_CXCurve2D