The International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences. Vol. XXXVII. Part B4. Beijing 2008 
346 
4. DATA STRUCTURE DESIGN OF OO-SOLID MODEL 
4.1 Redesigning topological relationships 
According to the requirement of geological modeling and 
updating, the topological relationships will be redesigned as 
following based on the improvement of the OO-Solid model. 1) 
node-arc-polygon; 2) polygon-region 3) node-region 4) 
region-component face-component; 5) nodes-point objects; 6) 
arcs-line object; 7) region-surface objects; 8) component-simple 
volume; 9) component-simple volume-complex volume; 10) 
simple-complex volume-composited volume . 
Because the first four kinds of topological relations 
corresponding to the six kinds of primitives, we can directly 
explicit store these topological relations into the data structure, 
rather than separately redesign topological relations table. The 
next six topological relations among geological objects used 
object-oriented approach (association or aggregation) also can 
be stored in the data structure and does not require separately 
design topological relations table. 
4.2 Redesigning data structure 
Data model is the general description of a group of entities and 
their relationship, and is the abstract of the real world (Li R X., 
1994.). Data structure is used to show data model and is the 
simplification of data model. The design of data structures 
commonly descript in relational database management system 
(RDBMS) in the data table or uses object-oriented methods. The 
following is the introduction of some data structure used in 
RDBMS. 
Name 
Type 
Description 
GM ID 
Int 
GM’s ID(PK) 
GM Name 
Varchar 
GM’s name 
GO Num 
Unsigned short 
Number of GO 
GOIDSequence 
Varchar 
Sequence of GO-ID 
GMAttrs 
Varchar 
Attribute description 
Table 1 Geological model data structure 
Note: GM—Geological Model; GO—Geological Object; 
GM-Attrs can be spitted into a number of fields. 
name 
type 
Description 
GOID 
Int 
GO’S ID(PK) 
GOType 
GO Attrs 
Unsigned short 
Varchar 
GO’s type 
(point, line, surface, volume) 
Attribute description 
Table 2 Geological Object data structure 
Note: GO-Attrs can be spitted into a number of fields. 
name 
tyP e 
description 
En_ID 
Int 
Entity’s ID 
VoType 
En Attrs 
Unsigned short 
Varchar 
Volume type 
(simple, complex, composited) 
Attribute description 
Table 3 Entity Object data structure 
Note: En-Attrs can be spitted into a number of fields. 
name 
type 
description 
COV ID 
Int 
COV’s ID(PK) 
COV Name 
Varchar 
COV’s name 
CLV Num 
Int 
Number of CLVs 
SLV Num 
Int 
Number of SLVs 
CLVIDSequence 
Varchar 
Sequence of CLVs’ ID(FK) 
SLV IDSequence 
Varchar 
Sequence of SLVs’ID(FK) 
name 
type 
description 
COV Attr 
Varchar 
Attribute description 
Table 4 Composite Volume data structure 
Note: COV—Composite Volume; CLV—Complex Volume; 
SLV—Simple Volume 
name 
type 
description 
CLV ID 
Int 
CLV’s ID(PK) 
CLV Name 
Varchar 
CLV’s name 
CoAttr 
CSV Num 
Varchar 
Int 
Common attributes of the SLVs 
contained in this CLV 
Number of SLVs’ID(FK) 
CSV IDSequence 
Varchar 
Sequence of SLVs’ ID(FK) 
CLV Attr 
Varchar 
Attribute description 
Table 5 Complex Volume data structure 
Note: Complex volume can be expressed as independent 
geological object; also can be included in the composited 
volume which expressed geological object. The topological 
relationships can be topologically reasoned from the topological 
relationships among components. 
name 
type 
description 
CSV ID 
Int 
SLV’s ID(PK) 
CSV_Name 
Varchar 
SLV’s name 
Common attributes of the 
COAttr 
Varchar 
components contained in this 
SLV 
CONum 
Int 
Number of Componets’ID(FK) 
CO IDSequence 
Varchar 
Sequence of componentsTD(FK) 
CSV Attr 
Varchar 
Attribute description 
Table 6 Simple Volume data structure 
Note: Simple volume can be expressed as independent 
geological object; also can be included in the composited 
volume or the complex volume which expressed geological 
object. The topological relationships can be topologically 
reasoned from the topological relationships among components. 
name 
type 
description 
CO ID 
Int 
Component’s ID(PK) 
CO Name 
Varchar 
Component’s name 
FP ID 
Varchar 
ID of fore-component-polygon 
MP ID 
Varchar 
ID of mid-component-polygon 
PPID 
Varchar 
ID of post-component-polygon 
CSFID 
Varchar 
IDs’ sequence of 
component-side-faces 
CUFID 
Varchar 
IDs’ sequence of 
component-up-faces 
CDFID 
Pn _IDJn_CO 
Varchar 
Varchar 
IDs’ sequence of 
component-down-faces 
IDs of the isolated-nodes in the 
component (sequence) 
CSV Attr 
Varchar 
Attribute description 
Table 7 Component data structure 
Note: 
1) The topological relationships of the components is the base 
of the topologically reason for complex volume, composited 
volume or simple volume. And his topological relationships 
reasons from the component-faces (regions) and nodes 
expressed the component. 
2) Component-face (includes component-side-face, 
component-up-down-face, and component-polygon) can be 
degraded line or point. 
3) The isolated-node in the component is mainly used for