The International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences. Vol. XXXVII. Part B4. Beijing 2008
Entity Name
Geometry
Type
Field Name
Description
Data Type
Width
Key
Owner
Owner No
Ownership no.
Varchar
25
PK
Name
Name of land propriter
Varchar
25
IC No
IC no
Varchar
15
State
Name of state
Varchar
10
Mukim
Name of mukim
Varchar
10
District
Name of district
Varchar
10
Typeowner
Type of ownership
Varchar
10
3DParcel
Polygon
Owner No
Ownership no.
Varchar
25
PK
Area
Area of parcel
Number
10
Geometry
Column of geometry
Mdsvs. sdo .geometry
Lot No.
Lot number
Varchar
10
FK
LandParcel
Polygon
Lot No.
Lot number
Varchar
10
PK
Area
Area of parcel
Number
10
Geometry
Column of geometry
Mdsys. sdo .geometry
Table 2: Physical Development of 3D Cadastre Registration Database
The table recording table Owner include with the following
items:
• Owner No: the ownership number of particular registered
object
• Name: the name of the person who hold rights on the
registered parcel
• IC_No.: the identification number of the land owner.
• State: description name of the state for the registered
objects
• Mukim: the name of the mukim of the registered objects
• District: the name of district of the registered objects
• Typeowner: type of ownership referring to registered
object
4.3 Association of the Components Elements in DBMS
Table 2 show the physical development of the registration for
3D cadastre object. There are three main entities that are owner,
3DParcel and LandParcel.
The 3D cadastre registration system is developed to show
registration of 3D spatial objects and combine with the land
attributes. The linkage of these tables is base on ownerno
(field name) that being set as primary key (PK). The 3D Parcel
is located in the primary land of 2D parcel. Therefore, the
linkage between these tables is based on the lot no.
4.4 The Linkage of DBMS and CAD
The sample data of building as shown in Figure 8 has been
chosen for the experimental purposes. In the experiment, we
have chosen Autodesk Map 3D and Oracle database to visualize
the spatial objects. The interoperability of Map 3D and Oracle
is developed based on the schema that helps to connect the
software. The specification of the schema need to be fulfilled
before the connection can be done.
The visualization of 3D cadastre object is conducted via the
Map 3D schema administration. Here, the Map 3D requires user
to login the Oracle database login name, password and the
service name. Later, the interested table in the Oracle database
will be selected to visualize in the Map 3D.
The visualization of the 3D cadastre objects are shown in
Figure 9. The registered coordinates in the Oracle DBMS can
be listed base on the primary key of the table.
Figure 8: Sample building for the
experiment purposes
Figure 9: Visualization of 3DParcel in CAD
The query for the administrative purposes can be done via the
interface develop by creating a linkage to Oracle database. In
the interface, several functions have been setup to perform
some operations such as add, save, delete and update data. The
example of the query can be seen in figure 10 where the query
is based on owner_no. Figure 11 shows result of the query
together with the attributes of the registered 3D parcel object.
125