![]() |
![]() |
GI_Forum 2013, Volume 1Creating the GISociety – Conference Proceedings
|
![]() |
Verlag der Österreichischen Akademie der Wissenschaften Austrian Academy of Sciences Press
A-1011 Wien, Dr. Ignaz Seipel-Platz 2
Tel. +43-1-515 81/DW 3420, Fax +43-1-515 81/DW 3400 https://verlag.oeaw.ac.at, e-mail: verlag@oeaw.ac.at |
![]() |
|
DATUM, UNTERSCHRIFT / DATE, SIGNATURE
BANK AUSTRIA CREDITANSTALT, WIEN (IBAN AT04 1100 0006 2280 0100, BIC BKAUATWW), DEUTSCHE BANK MÜNCHEN (IBAN DE16 7007 0024 0238 8270 00, BIC DEUTDEDBMUC)
|
GI_Forum 2013, Volume 1, pp. 113-116, 2013/06/20
Creating the GISociety – Conference Proceedings
The most practical Geographical Information Systems provide the data based on spatial aspects. They define spatial feature classes with additional thematic attributes. That’s why in practice you find very often different feature classes for one real world object, e.g. one street both as line-object and as polygon-object – and the same attributes are saved two times with inconsistency. But UML (Unified Modelling Language) and all UML-based data structures (among others the INSPIRE data specifications) define an object oriented data management. That means e.g.: * one real object is one information object; * all objects can have more and different geometries; * the geometry is to handle like an attribute; * the handling of generalisations and heredities; * the need to manage versioning and historiography. And the practical use cases require that object oriented structures too. In the following the necessity and innovative solutions should be presented by 5 examples: