2004
with
orical
d the
04a)
g and
zation
cesses
ses in
iternet
user
E. üser
tabase
uages.
Ictions
nming
der to
paper
nth its
itory",
"face"
torical
tabase
data in
Ytation,
support
ng on
S data
et the
of art-
multi-
ow the
in the
1tations
]uate to
odeling
nce the
. Since
h a life
ect data
roposes
| of this
lity 10
queries
1 model
|; being
gement.
del for
[S data,
1g time.
mic SIS
istorical
] object-
emporal
International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences, Vol XXXV, Part B4. Istanbul 2004
This is the first version of the "GeoHistoryRepository" model,
which incorporates historical buildings, utilities, and people
such as the people had lived in the fortress and in the cemetery.
The model includes topology rules for each feature dataset
along with related domain value tables. The purpose behind this
design is to help "users manage these complicated,
interdependent datasets in one cohesive model using an
interface. SIS modelers in the project team produced several
questionnaires for project team members to identify
conceptually the key themes/data and primary issues to analyze
which will be designed in the data model as an initial task in
developing data model “GeoHistoryRepository”.
Figure 1 shows a part of the conceptual SIS data model for
Historic Architecture. The fundamental unit for historic
architecture is the "architectural changes", which is the first
type of feature described in a historic architectural survey.
Conceptual design was conducted with the "Sybase Power
Designer" graphical tool and "Unified Modeling Language
(UML)" was used as a modeling language. Some examples are
a residential place (within the fortresses and out of the
fortresses, settlement); a market (with its associated fields and
buildings); a war area (with its weapons and towers and bonets);
a religion lot (with its mosque and associated cemetery); a
cleaning complex (with its hamams).
"GeoHistory Repository" is being designed as a process-oriented
spatiotemporal data model based on three domains which
extends the concepts both of spatial and temporal data
modeling. Its general framework uses a set of geometry-based
spatial objects to represent reality (spatial modeling aspect).
Thematic characteristics are represented as attributes of spatial
objects (semantic modeling aspect). Temporal information is
associated with time-stamping events or processes (temporal
modeling aspect). Major advantage of this model is that threc
domain's objects dynamically link together with the aspects of
location, attribute and time centered. Spatiotemporal queries
and analytical methods are performed in this spatio-bitemporal
model which handles information about valid time and
transaction time in SIS and allows for retroactive as well as
post-active changes. (Guney et al., 2004)
Three domain-oriented spatio-bitemporal ^ data ^ model,
GeoHistoryRepository, is being developed to capture the discrete
changes of objects through time interval, from 17" century to
now. The discrete changes of a historical object during a time
interval can be seen as snapshots of that object, taken in time
points of this time interval. Versions of the same facade of
"Kumkale" in different time of the same period are shown in the
Figure 4. Changes occur to attributes of a phenomenon, behaviors
of an event, or mechanisms of a process.
Most of phenomena in the 17^ century Ottoman fortresses are
dynamic that has changed discretely over time. The value of
lime is represented by the number of years for example After
the World War I, the fortress was damaged and re-constructed.
The shape of most buildings within the border of the fortresses
architecturally changed. In this study, purposed spatiotemporal
applications based on the "GeoHistoryRepository" as follows:
* Geometrical (or topological) changes of historical objects
over time
Positional changes of historical objects over time
Change of historical object attribute (spatial attribute) over
time (variations in attributes over time)
Any combination of the above changes
The major drawback is the lack of a tool facilitating conceptual
data model design and its associated implementation. That
UML is a CASE tool used for designing an object-oriented data
model may provide new release for users to define their own
domain-specific classes and functions.
The goal is to develop a SIS data model for a 3D historical
documentation with spatial and non-spatial data under the same
architecture and to implement a complete database system based
on this data model. The next component explains a graphical
user interface which allows interaction with the data in
“GeoHistoryRepository”.
3.2 Visualization Component: GeoHistoryVirtualInterface
That “GeoHistoryVirtualInterface” is being developed to build
an architecturally-accurate 3D model in a computer-generated
environment which specifies 3D virtual re-construction of the
fortresses and the objects in the fortresses enables a user to
interact with the objects in the scenes. Virtual Tour Guide,
called GeoHistory tutor, in the "GeoHistory VirtualInterface" is
being designed to talk to visitors in English pointing out
historical, artistic and architectural facts of the objects.
“GeoHistoryVirtualInterface”, which is a Graphic User
Interface (GUI), uses 3D internet modeling language
VRML\GeoVRML to create and reproduce some accurately
modeled 3D scenes that could be viewed over the web and to
explore the potential of 3D visualization of reality. If the feature
selected by user has related image and/or sound data, they can
be displayed and played using the GUI. Some semantics such as
hierarchical transformations, light sources, viewpoints,
geometry, animation, fog, material properties, and texture
mapping are being integrated to the scenes of the fortresses and
the objects in the fortresses. Additionally, real time navigation
techniques through * 3eoHistoryVirtualInterface" such as fly-
over, walk through are being designed to promote the
interactivity. (Guney and Celik, 2004b)
“GeoHistoryVirtualInterace” uses programming Java in
combination with VRML for 3D modeling, rendering, and
dynamic interaction capabilities (provided by VRML), complete
programming capabilities, and network access (provided by
JAVA), which extends the ability to interact with the model and
to animate objects within the scene really only limited by the
creators imagination.
“GeoHistoryVirtualInterface”, which is an “External Authoring
Interface (EAI)” linking Java applets or applications to the 3D
VRML/GeoVRML scene, is an interactive user interface
between the encapsulating HTML browser and the embedded
VRML browser, and is used as a dynamic gco-visualization tool
through the Internet. It provides to access nodes and event
structure from outside of VRML browser instead of
comprehensive node access within VRML browser via a Script
node that is another alternative using “Script Authoring
Interface (SAI)". This interactivity enables Java applet to build
and update dynamically the data in VRML, and in turn, the
applet’s data can also be dynamically updated through the
VRML interface. (Guney and Celik, 2004b)
The connection between the data in Java applet and the nodes in
the geo-spatial world in VRML file is implemented by EAI. The
changes in Java applet can affects the 3D geo-spatial world built
in VRML file form. And the event occurred in VRML world
can be detected and processed in Java applet side. 3D spatial
analysis such as selection, 3D buffering, and near can be
