ISPRS, Vol.34, Part 2W2, “Dynamic and Multi-Dimensional GIS", Bangkok, May 23-25, 2001 
273 
¡ng curves and 
dations, conics, 
3 interfaces will 
:ing, accessing, 
DBMS: DATA 
VTURES 
capture the real 
¡rstanding of the 
is to develop a 
eal world. The 
l 2D (see Figure 
3. 
will be extended 
this. For this, a 
lext subsections 
to represent 2D 
• maintaining 3D 
nodel 
äl 
sical storage 
ral system (for 
legal status of 
sn (2001). The 
i the following, 
jsing geometric 
lition to the use 
information are 
:ral boundaries) 
tension of the 
idicated with a 
box covers a 
patially indexed 
3d on rectangle 
stric data type 
topologically in 
the so-called 
table contain 
winged edge 
m the complete 
ss of topology 
idaries to the 
iibility to relate 
. relation to the 
'ey, names of 
arcel would be 
represented in the DBMS by a closed polygon, it would be 
complicated to represent the basic object of cadastral surveying: 
one boundary between two neighbour parcels. Closed polygon 
representation would lead to double (or triple or even more) 
storage of all co-ordinates (except the territorial boundary), 
which complicates the data management in a substantial way. 
Closed polygon representation can result in the introduction of 
gaps and overlaps between parcels, which is not related to 
reality. One more reason for the boundary based approach is in 
the classification of boundaries: the administrative cadastral and 
political subdivision in sections (cadastral zones), municipalities 
and provinces is possible by classifying boundaries as ‘section 
boundary’, ‘municipal-boundary’, ‘province-boundary’ or ‘national 
boundary’. A ‘national boundary’ is by definition a ‘province 
boundary’ and a ‘municipal-boundary’ and a ‘section-boundary’ 
and a ‘parcel-boundary’ etc. 
A detailed overview of the parcel and boundary tables is given in 
Tables 1 and 2. 
The following attributes are included in the data model for all 
spatial features: 
• objectjd, a nation-wide unique feature identifier for all 
objects represented in the DBMS; 
• classif, classification code of the object, e.g. parcel 
boundary, parcel identifier, etc.; 
• location (of data type point) or shape is of data type 
line(50), a polyline up to 50 points, representing the 
cadastral boundaries, stored in a variable length way in the 
(object)/relational database; 
• sel_code, a selection code which indicates to which map 
type(s) a geographic object belongs, e.g. cadastral data 
and/or large scale topographic data; 
• source of data, which is a reference to the field documents 
and files from total stations, or to the id of the 
photogram metric project for large scale topographic 
mapping, etc; 
• quality, which is the mode of data collection, e.g. terrestrial, 
photogrammetric and includes an accuracy code which 
denotes the deviation from the ‘true 1 position; 
• vis_code, visibility code to classify less visible objects 
during photogrammetric data collection, e.g. because one 
road lies on top of another road; 
• Larea, official legal area, which is included in the official 
legal documents or deeds describing the transaction, in 
general this area is not equal to calculated area from the 
spatial cadastral boundary data; this attribute is introduced 
only for the parcel table. 
Attribute Attribute description 
Name 
Ogroup 
Objectjd 
Sic 
Classif 
Location 
DJocation 
Rotangle 
0_area 
Bbox 
Object_dt 
T_min 
T_max 
Sel_code 
Quality 
Vis_code 
Group Id (KEY. 1 j 
Text/polygon object id (KEY.2) 
Spatial location code, index 
Object classification 
x,y co-ordinate pair of centroide (parcel id) 
Delta x,y displacement of centroide (parcel id) 
Rotation angle of centroide (parcel id) 
Cadastral boundary based calculated parcel- 
area 
Bounding box covering the complete parcel 
Date of object creation; equal to t_min in this 
special case 
Date/time of parcel creation in the database 
Date/time of parcel deletion in the database 
(KEY.3) 
Selection code: object to be represented on 
cadastral and/or topographic data sets 
Quality label: collection mode & accuracy 
Visibility code; photogrammetric data collection 
L_area 
Official (legal) area of parcel 
Municip 
Municipality code, part of parcel identifier (ALT- 
KEY.1) 
Section 
Cadastral section code, part of parcel identifier 
(ALT-KEY.2) 
Sheet 
Sheet number of the original paper map, 
reference to paper archive 
Parcel 
Parcel id within cadastral section, part of parcel 
identifier (ALT-KEY.3) 
PpJJtr 
Part-parcel letter, in use to identify part of parcel 
before surveying 
PpJ_nr 
Part-parcel number, in use to identify part of 
parcel before surveying 
L_num 
Number of boundary references 
Linejdl 
Reference to objectjd of one surrounding 
boundary 
Linejd2 
Reference to objectjd of one boundary of the 
1 st enclavejif existing) 
Table 1: Definition of the parcel table 
Attribute 
Name 
Attribute description 
Ogroup 
Group Id (KEY.1) 
Object id 
Line object Id (KEY.2) 
Sic 
Spatial location code, index 
Classif 
Object classification 
lnterp_cd 
Line interpolation code, line/arc 
Shape 
Line co-ordinate pairs, compressed 
FIJineJd 
Object id of first line to the left side in begin 
point -> BOUNDARY 
Frjinejd 
Object id of first line to the right side in begin 
point -> BOUNDARY 
LIJineJd 
Object id of first line to the left side in end 
point -> BOUNDARY 
Lrjinejd 
Object id of first line to the right side in end 
point -> BOUNDARY 
L_objJd 
Objectjd of parcel on right side -> PARCEL 
R_objJd 
Objectjd of parcel on left side -> PARCEL 
Bbox 
Bounding box covering boundary between 2 
parcels 
Linejen 
Length of boundary 
Object_dt 
Date of survey of the boundary in the terrain 
T_min 
Date and time of boundary creation in the 
database 
T_max 
Date and time of boundary deletion in the 
database (KEY.3) 
Sel_code 
Selection code: object to be represented on 
cadastral and/or topographic data sets 
Source_cd 
Source of data, reference to field sketch, 
photogrammetric project 
Quality 
Quality label: collection mode & accuracy 
Vis_code 
Visibility code; photogrammetric data 
collection 
L_municip 
Municipality code, part of the parcel id to the 
left side-> ALT-PARCEL. 1 
L_section 
Cadastral section code, part of the parcel id to 
the left side -> ALT-PARCEL.2 
L_sheet 
Sheet number of the original paper map, part 
of the parcel id to the left side 
L_parcel 
Parcel id within cadastral section, part of the 
parcel id to the left side -> ALT-PARCEL.3 
R_municip 
Municipality code, part of the parcel id to the 
right side -> ALT-PARCEL. 1 
R_section 
Cadastral section code, part of the parcel id to 
the right side -> ALT-PARCEL.2 
R_sheet 
Sheet number of the original paper map, part 
of the parcel id to the right side 
R_parcel 
Parcel id within cadastral section, part of the 
parcel id to the right side -> ALT-PARCEL.3 
Table 2: Definition of the boundary table 
The text/label location-attribute in the parcel table is represented