+ 2 |
Select Insert Clear Field Update Delete
|
Thematic data management
(GIS Attribute)
| Classification ‘icon’
#
Controlpoinf
E 7 NS
Ve
Water Sys. | powerline | Phoneline building zone
Fig. 8 The classification of features in GIS
$ 1.3
or m s
Select || Insert Delete
ID
Holder
Built
Function
e eec Lm à
Factory Institute | School | Hospital Restaurant] Hotel
Fig. 9 Building Card
Sup.market
Bank
Controlpoint
Building Hotel
„---Di Operations I= inherit Operations
GIS Alt „Anherit E er Building
Cperation: * Properties: been” Properties
select Identifier Propenies: Employees
insert number Hotelname: properties:
dalete street manager
update E" phone number ,.]Employee No.
22% older »*' | name
lunctionm - cid position
business *
builtdate R salary
À properties ? Hired on
^ ( [Derive values Dept. No.
“Inhe rit nherit From Employ. |Aggr ate
t. ' [and room&bes:
LE
Room&bed
\
Postoffice s properties:
Item
“+ {rooms
beds
room price
left beds
atersystem
Fig.10 Relationship of various
feature classes in GIS
778
a ORACLE
: *[*| Hotel
Y GIS Att. Select | Insert
No. | : ID Hotel name Shohei
Sree! | Norrebrogade manager | jesper
city Copenhagen No. | 31908879
Holder| Elsebeth Leon
:| Built dote = - . Employees Rooms
; 14 400
INCOME
343565
m | [i E EL
building business Emp Room&Bed
Fig. 11 Hotel Card
4.3.4 Comment The object-oriented model
emphasizes the entity concept. A card in
HyperTalk is used to represent a complete object
including its attributes, operations and the
relationship between it and other objects. From
user view. the semantics of model is explicit and
clear. Here it has been investigated how the
Oracle system and HyperTalk programming can serve
as suitable tools for object-oriented models in
GIS. Though Oracle and HyperTalk are not real
object-oriented DBMS the integration of them can
realize the object-oriented database management
in GIS. Of course, some problems, such as the
lack of real class and inheritance in HyperTalk,
need to be overcome. Recently, research in non-
standard database environments promoted an
object-oriented model which looks promising to
overcome some problems that make conventional
database management systems unsuitable [Frank
1989b]. However, the realization of the real
object-oriented database management depends on
the powerful database management system and
object-oriented programming language. At present,
only a few languages support object-orientation
sufficiently [Frank 1989], and the OODBMS is
being studied.
REFERENCE
[1] Fritsch, D., 1989: "Acquisition, topology and
structuring of spatial data" 42 Photogrammetric
Week at Stutgart University.
[2] Egenhofer,Max J., Andrew U. Frank, 1989a:
"Object-oriented software engineering
considerations for future GIS". Second
International Geographic Informatio Systems
(IGIS) Symposium, Baltimore, MD.
[3] Egenhofer,Max J., Andrew U. Frank, 1989b:
"Object-orient modeling in GIS: Inheritance and
Propagation". AUTO-CARTO 9, Ninth International
Symposium on Computer-Assisted Cartographic,
Baltimore, MD.
[4] Egenhofer,Max J., Andrew U. Frand, 1989c:
"Inheritance vs. propagation". University of
Maine, USA.
[5] Frank,Andrew U., 1989: "Multiple inheritance
and genericity for the integration of a database
management system in an object-oriented
approach". The second International Symposium on
Object-oriented database, Bad Stein am Ebernberg,
Germany. September 27-29, 1988.
Dat
Arc
Was