Graduate Research Thesis Defense Presentation

DESIGN AND DEVELOPMENT OF CADASTRAL DATABASE IN THE CONTEXT OF PAKISTAN

JOHUMFATIMAH MIRZA2010-NUST-MS PhD-GIS-03

IGIS - NUST

Final Defense

Supervisor:

2/30

• DR. RIZWANBULBUL (IGIS, NUST)

Guidance & Examination Committee

• DR. HAMID MEHMOOD (IGIS, NUST)

• M. NABIAHMED (ICRAF)

• ENGRMUHAMMAD ZAHEER (IGIS, NUST)

Contents

3

• Introduction

• Scope

• Objectives

• Literature Review

• Research Methodology

• Objective 1: Study of Existing System

• Objective 2: Modelling of Entities and Relationships

• Objective 3: Mapping in ISO Cadastral standard

• Objective 4: Implementation of Prototype

• Prototype Demonstration

• Conclusions and Recommendations

Introduction-Cadastre

• FIG (International Federation ofSurveyors, 1995) provides acomprehensive definition of‘Cadaster’

▫ A parcel based, up-to-date landinformation system containing arecord of interests in land

▫ Contain Geometric and attributeinformation

▫ Established for various purposes

4

Land and Resources

Attribute Info. of Land

Ownership

Value

Land Use

Figure : Concept of Cadastre

Land and Resources

Introduction-Land Information System

• Cadastre-A type of informationsystem under the category of landinformation systems (LIS).

5

Figure : Cadastre as a part of Land Information System, Source: Land Information Management by Dale and McLaughin

Digital Cadastral DB

Visualization

• A country’s DCDB is its core information layer – stores informationabout the built environment.

• DCDBs store cadastres in the form of three basic components(Adeel.M., 2011):

▫ The cadastral parcel

▫ The cadastral record

▫ The parcel index

6

Geometry

Interests

Time

Components of DCDB

Digital Cadastral DB Examples

• ArcCadastre System - Sweden

• Cadastral Electronic Field Book (CEFB) – Florida

• Survey Record Information System (SRIS) – Cananda

• e-Taiwan - Taiwan’s Comprehensive cadastral Info. DB

• Digital Cadastral Data Base (DCDB)– Malaysia

• Digital Cadastral Data Base (DCDB) - Australia

7

• Land Online – New Zealand

• Cadastral Database – Montana

• Land Information System - Hawai

http://www.linz.govt.nz/

http://svc.mt.gov/msl/mtcadastral/

http://gis.hicentral.com/FastMaps/ParcelZoning/

http://www.linz.govt.nz/

http://svc.mt.gov/msl/mtcadastral/

http://gis.hicentral.com/FastMaps/ParcelZoning/

Existing Situation in Pakistan

• Pakistan has poorly functioning, inadequate, and duplicative systemsof :

▫ Land administration separate for urban and rural areas (USAID,2011)

• Traditional system of land records is organized:

▫ Land registers

▫ Cadastral maps in paper formats

▫ Archaic paper based system

• The complexity of the system, manual nature have given rise tonumber of problems (Ali.Z. and Nasir.A.,2010 , Qazi, M.U., 2005 , Raza,S.F., 2005) :

▫ Security

▫ Updating Issues

8

Continued…

• The system has become obsolete and opaque and has no. ofproblems as identified by numerous papers and reports:

▫ USAID Report (2011)

▫ Qureshi, F.M.(2010)

▫ Ali.Z., and Nasir.A. (2010)

▫ Ali.A.(2009)

▫ Qazi, M.U., (2006)

▫ Raza, Fawad, Almas (2005)

• Pakistan is still far behind in the international scenario ofdeveloping a digital cadastral system.

9

Existing Situation in Pakistan

Causes and Effects of Existing

System

10

Figure : Existing situation of Manual Cadastral System in Pakistan, Causes and Effects

Problem Statement

• Development of a conceptualschema for DCDB in thecontext of Pakistan and checkapplicability of ISO cadastralstandard.

• Scope: Research focus will beon DB organization andmodeling. Quality aspects willnot be addressed

11

Figure 6: Conceptual Diagram of Modeling of cadastres in Database

Objectives

• The overall objective of this research is:

▫ To understand the basic principles of existing cadastral system ofPakistan

▫ To design and model the basic entities of existing cadastral system.

▫ To model selected designed entities into a specific cadastral datamodel so as to make it standard compliant.

▫ To Implement adapted design in spatial DBMS software.

12

Literature Review

• Sukaya A.G.K (2009) and Sari K.W. (2010) carried out research to see applicability of Standard Cadastral Data Model in the context of Indonesia.

▫ PostGIS used for demonstration purpose as DBMS.Qgis,MapServerand Apache has been used for display

• Kabir K.H., (2009) investigated geospatial tools for development of multipurpose digital cadastre prototype in Bangladesh.

• Mohsesn S.K.S., (2008) developed a spatially referenced cadastral data model based in the Context of Australia.

• Logical model using C++, Visual Basic and Arc GIS EnvironmenMajidA.K., shah bin Sadiq (2006) developed an Automated Cadastral DBselection and visualization System for Malaysian Cadastral System.

▫ Arc Objects were used and development was done in VB

▫ Arc View was used for visualization

13

Literature Review

• Rutamu D.R., (2006) Designed an architecture for the integration ofdistributed cadastral DBs

▫ SQL Manager lite 2005 for Postgre SQL Editing.U Dig for editing andvisualization.Geoserver for WFS

• Már, Tryggvi (2005) carried out research to identify the applicability ofgeo-applications to cadastral registration in the context of Iceland.

▫ Postgres/PostGIS as DBMS.U Dig and QGIS for rendering

• Mutambo (2003) conducted research to explore how UML can beused in Cadastral System development.

▫ Zambian Cadastral system.Conclusion was drawn that UML can beused for spatial data handling through GIS Packages.

• Kocaman, Sultan (2001) developed a cadastral system using spatio-temporal modelling approach:

▫ Development of Conceptual , logical and physical design of cadastraldatabase system for Turkey .Oracle 8i as DBMS.MapInfo 6.0 GIS forimplementation

14

To understand the basic principles of existing cadastral system of Pakistan

Objective 1:

1.1 Introduction-Institutional Framework• Very Old land records management system – dates back to Sher Shah

Soori ( 1534-1545 )

• Colonial rule by the British implemented the system on scientific lineswhereby:

▫ Large scale cadastral surveys were conducted

▫ Classification of soil fertility

▫ Set up of a proper administrative hierarchy

• Pakistan has no comprehensive land administration for whole country,no agency at national level is responsible for land administration

17

Figure 8: Development of Land Administration , Source: Gauhar,S.(2004)

18Data Type

Responsible organization

Responsible Ministry

Analogue Data Digital DataUse of web for

Data dissemination

Level

Topographic Survey of Pakistan (SoP)

Defense Yes Yes No

Fed

eral

Rural Cadastral Data and Taxation

Board of Revenue (Separate for each

Province)

Respective Provincial Governments

yes

No* (Work to convert analogue data into digital

form is in progress)

No

Pro

vincial

Urban Cadastral,Property

Data and Urban Landuse

-Development Authorities (DA-in Metropolitan Areas)

-Town Municipal Administrations (TMA-In small urban settlements)

-Private and Semi Government Housing Authorities

-Cantonments (In Army regulated Housing Areas)

Planning and Development

authority at Provincial level for DAs and

TMAs, while Private and Semi Government Housing Authorities, Cantonments work

and collect information

independently about properties and

Houses.

YesYes* (Very Limited

and Sporadic)No

City

/ To

wn

/ Teh

sil

Urban Property/ Real State Taxation

Provincial Excise and Taxation Department

Excise and Taxation Yes Not known No

Pro

vincial

Table 1 : Organizations Responsible Land related or Cadastral Data, Source: Adapted from Asmat , (2009)

1.3 Current Cadastral System-Processes

1) Land Registration Process (Carried out after four years):

▫ Ownership in land is recorded and registered by government soas to provide evidence of ownership and to facilitate dealing

▫ Entries of ownership are added in Register Haqdarane Zameen(RHZ)

2) (Individual) Ownership Document Preparation Process:

▫ The document showing ownership of land of an individual iscalled the "Fard Malkiyat"

19

1.3 Current Cadastral System-Processes3)Mutation Process:

▫ A mutation is used to record any change in the land and entriesare added in register dakhil kharij/inteqalat

4) Error Correction Process:

▫ Whenever a clerical mistake is detected in land records, thePatwari makes the necessary entries about it in the columns ofthe Fard Badar Register

5) Binomial Inspection Process: (Carried out twice a year )

▫ Use to collect information of the type of crop sown by farmers, its area and kind of soil with reference to every parcel no.

6) Settlement Process: (Normally carried out after every 30-35 year)

▫ Detailed field survey with the results embodies in a map and fieldregister.A full inquiry into the right and liabilities of all personshaving interest in the land parcel

20

1.4 Current Cadastral System-Land Records

• Pakistan’s cadastre is composed of mainly two types of records:

▫ Cadastral Map (Parcel based map showing agriculture lands)

▫ Cadastral text document (17 Registers)

• Cadastral land record sets are developed at the time of settlement

• The land record data is maintained at Tehsil and District offices

21

1.4.1 Land Records-Geographic Data1. Masawi (Map)

• Paper based graphical representation of land parcels which are drawnat large scale: 1” = 40 karam = 200’-220’

• Land parcels are labeled with their Khasra Number(parcelidentification number) and dimension of each side.

• Subdivision lines(dotted lines) - use for the area calculation on themap.

• Whole village can be covered in a single map or there may be severalmaps of a single village covering specific portions of it.

• Variants of cadastral map:

22

Map

Masawi

ShajraParcha/Latha

Parat Tehsil Map/ Fair Copy

Shajra Tatima

23

Map part no.Survey Type

Village Name

Unique Village

No.

Tehsil and District NameDate of

Preparation of MapScale

Parcel Polygons

Parcel No.

Parcel Dimensions

Village Boundary

Adjacent Village Names

Survey Mark/Pillar

24

Legend Detail

25

Figure 11: Masawis of a Village surveyed on Rectangular system

Survey Type-Rectangular

26

1.4.2 Land Records-Attribute Data

1.5 Linkage of Registers in Existing System

27

Main Keys in the Existing Registers

• Owner ID (Khewat No.) - OID

• Parcel ID/ Survey No. (Khasra No.) - PID

• Farmer ID (Khatooni No.) - FID

Field Book

PID

FID

Masawi

PID

Shajra Tatima

PID

OID

Register DakhilKharij/Inteqal

Mutation No.

OID

PID

Shajra

Family No.

OID

Wajibularz

Village IDReg. Haqdarane

Zameen/Abadi/Naklistan

OID

PID

FIDChanges in kind of

soil

Village ID

Memorandum of transfer of rights

Mutation No.

Haqooq -e-Chahaat

PID

FID

Fard Taqseem Aab

OID

Water Mills

PID

FID

Fard-e-Bdar

Sr.No.

OID

Taghurat

Date and Yr.

PID

Register Girdawari

PID

OID

FID

Dhal Bach

OID

PID

OID

PID

Mu

tati

on

No

Agriculture Records

Ownership and Rights

Village ID

Irrigation Source

• Study contributed to International FIG “Cadastral Template”initiative:

• Pakistan Country cadastral profile is available online at:http://www.cadastraltemplate.org/

28

1.6 Cadastral Template of Pakistan

To Model the Entities and Processes of Existing Cadastral System

Objective 2:

30

2.1-Modeling Entities of Existing Cadastral System

Entities

Study of Existing System

Literature Review

Relationships

Identify

Attribute

Type

KeyDet

erm

ine

Identify

Attribute

Optionality

Cardinality

Draw

Preliminary E/R Diagram

Ok?

Translated Tables

Graphical notation and diagramming

tools

Identify

No

Ver

ify

Yes E/R Diagram

Fig

ure

3:

Wo

rkfl

ow

of

ER

mo

de

lin

g

31

2.1.1 Translation of Tables

Tehsil

Former Present East West South North

Signature of Patwari Signature of Qanoongo Signature of Revenue Officer

District

Remarks/ConditionSurvey/Khasra Length and Breadth of Survey/Khasra no.

Calculation of Area Area and Soil ClassificationNo.Khatooni

Estate Book No./Leaf no.For the Year

32

2.1.1 Translation of Tables

33

Kharif Crop Rabi Crop

Changes of Rights,

cultivation, Possession

and rent with referene

to Mutation Register

Kharif Crop Rabi Crop

Changes of Rights,




Kharif CropRabi Crop

Changes of Rights,




Remarks

Rabi/Kharif Rabi/Kharif Rabi/Kharif

Survey/Khasra No.Name of Owner

and Khewat No.

Name of

Cultivator and

Khatuni No.

Area including

class of soil

Harvest Inspection - Girdawari

Name of

Crop

Date of

Harvest

Inspection

Khasra No.

Area of

Khasra Under

Cultivation

Entry in Last

Settlement

Entry in Current

Settlement

Signatre of

Ptwari Along

with Date

Signatre of

Grdawar

Qanoongo Along

with Date

Signatre of

Revenue Officer

Along with Date

Condition

Changes in Cultivation - Taghurat

No.Khewat Register HaqDaran-e-ZameenName of Owner

With Description

Name of

Cultivator With

Description

Survey/Khasra

No. with Name

Area and

kind of

soil

No. of Khewat which will

be substituted in the new

Register HaqDaran-e-

Zameen

Name of the owner with

description

Name of Cultivator

With Description

Survey/Khasra

No. with Name

Area and Kind of

Soil

Report and

Orders, Signature

of Witness

Entry in Register HaqDaran-e-Zameen or Last Entry in Register Dakhil Kharij which is Proposed to be Corrected New Entry which is Propsed to be substituted

Sr.No.

Nature and date of Mutations with price

in case of in case of sale and amount of

mortgage debt in case of mortgage

Land Revenue

and Dakhil

Kharij Fee

Mutation Register- Dakhil Kharij

34

Sr.No. Heading of Customs Information

Name of Khewat Owner Type of Ownership Right Share Owned Area of Share Owned Agriculture Pass Book No.

No. Khewat MalikOwner Prospectus/Details Name of Cultivator with

Description

Survey/Khasra no. and

Name (if any)

Area and Soil Classification Khewat

no.No. Khatuni Cultivator

Source of Irrigation

Including Name of Well

Rent Paid by the

Cultivator, Rate and

Demand

Demand with

Details of

revenue and

Cesses

Remarks Including:

Name of Lambardar

Rate of Land Revenue

In last Register

Haqdaran

Zamin

In new Register

Haqdaran

Zamin

No. of Khewat

Sr. No.Patwari’s/Tapedar

’s Report

Field

Kanungo’s/Superv

ising Tapedar’s

Report

Order of the

Revenue Officer

Source of Irrigation Serial No. Khewat No.Name of Owner with

DescriptionShare Remarks

Mutation Register- Dakhil Kharij

Ownership Register – Register Haqdaran-e-Zameen

Error Correction – Fard Badar

35

2.1.2 Entities and Relationships

Parcel ( Khasra)

Land Type

Block

Farmer/ Tenant (Khatooni)

Estate

Owner(Khewat)

Statement of customs

(Wajibularz)

District

Notes in Changes in kind of soil

Mutation (DakhilKharij)

Old entry

New Entry

Family/Cast/Tribe(Shajra)

Person

Belongs to

Belongs to

Belongs to

Ownedby

has

hasBelongs

to

Belongs to

Belongs to

has

has

Irrigation Source

has

Tax, Demands, Revenue

has

Obligations and

Liabilitieshas

Change enters in

Change enters in

Change enters in

has

has

Error(Farde Badar)

Wrong Entry

Corrected Entry

Mistakes rEntered in

Mistake rEntered in

hashas

AgricultureInfo.

(Tagyurat , Girdawari)

*

1

*

1

* 1

1

11

*

*

1*

* *

*

*

*

1 1

1

1

1

1

*

*

*

* *

1

*

*

1

1

*

*

*

**

*

*

*

*

36

2.1.3 Modeling Entities of Existing Cadastral System

Ok?

Conceptual to logical mapping

No Yes

Figure 4: Workflow for developing Logical Schema

E/R Diagram

Re-examination and decomposition of entities

Re-examine and define relationships

Define Keys

Normalize Table Structure

DB Implementation

Diagram

37

Parcel

PK Present_Servey_No

Field_Name East West North South Area Area_in_Words GeometryFK1 Remarks_IDFK2 Block_NoFK3 Village_ID

Remarks

PK Remarks_ID

RemarksFK1 Present_Servey_No

Former_Survey No. Detail

PK FSD_ID

Former_Survey_No

Block

PK Block_No

GeometryFK1 Present_Servey_No

Land_Type

PK Land_Type_ID

Land_Type Irrigation_Status Source_of_Irrigation Land_Part Extent_geom

Farmer

PK Farmer_ID

Farmer_Name

R_FormerSurveyNo_Parcel

PK,FK1 FSD_IDPK,FK2 Present_Servey_No

ID

R_LandType_Parcel

PK,FK1 Present_Servey_NoPK,FK2 Land_Type_ID

ID

R_Farmer_Parcel

PK,FK1 Present_Servey_NoPK,FK2 Farmer_ID

ID

Estate

PK Village_ID

Name_of_Village Geometry Common_LandFK1 Present_Servey_NoFK2 Tehsil_IDFK3 Serial_NoFK4 Kind_of_Soil_ID

Tehsil

PK Tehsil_ID

Name_of_Tehsil GeometryFK1 Village_IDFK2 District_ID

District

PK District_ID

Name_of_District GeometryFK1 Tehsil_ID


1)- Field Book Register

38


2)- Statement of Customs Register

3)- Register Changes in kind of soil

39


4)- Mutation Register

Mutation

PK Mutation_no

Nature_type_of_mutation Date Price_Amount_for_Sale_Mortgage Mutation_fee Current_status_accepted_or_rejected Mutation_attestation_statusFK1 Report_IDFK2 Order_Detail_IDFK3 Party_IDFK4 Evidence_No

Old_Parcel1


Field_Name East West North South Area Geometry Remarks_ID

Old_Land_Type1

PK Land_Type_ID


Old_Farmer1

PK Farmer_ID

Farmer_Name

Old_R_LandType_Parcel1


ID

Old_R_Farmer_Parcel1


ID

Old_Owner

PK Owner_ID

Owner_Name CNIC_no Fathers_name

Old_R_Owner_Parcel

PK,FK1 Present_Servey_NoPK,FK2 Owner_ID

Share Description

New_Parcel11


Field_Name East West North South Area Geometry Remarks_ID

New_Land_Type11

PK Land_Type_ID


New_Farmer11

PK Farmer_ID

Farmer_Name

New_R_LandType_Parcel11


ID

New_R_Farmer_Parcel11


ID

New_Owner1

PK Owner_ID

Owner_Name CNIC_no Fathers_name

New_R_Owner_Parcel1

PK,FK1 Present_Servey_NoPK,FK2 Owner_ID

Share Description

Old_R_Parcel_Mutation

PK,FK1 Present_Servey_NoPK,FK2 Mutation_no

Apply_Date_of_Mutation Type_of_Right Area_of_each_type_of_right Officers_order Right_description

New_R_Parcel_Mutation1

PK,FK2 Present_Servey_NoPK,FK1 Mutation_no

Date_of_transfer Contract_start_date Contract_end_date

Order_Detail_on_Foil_CounterFoil

PK Order_Detail_ID

PersonName_ReportedMutaion Place_Name DateFK1 Mutation_no

Report

PK Report_ID

Report_Description Negotiation_InformationFK1 Mutation_no

Party_Details

PK Party_ID

Name_of_Person_Party Present_or_Absent Share_of_Each CNIC_or_RegNo

Evidence_Details

PK Evidence_No

Type Date_of_ExecutionEvidence Posession_Status Date_of_TransferofPosessionFK1 Mutation_no

40


5)-Error Correction Register

6)-Pedigree Sheet Register

Family

PK Family_ID

Taraf_or_Pati Cast_or_Tribe Paimana_HaqiqatFK1 CNIC_No

Person

PK CNIC_No

First_Name Relationship Last_Name Alive_Dead Ocuupation Orphan Address Pass_Book_No Owner_IdFK1 Family_ID

41

7)- Ownership and Rights Register

Parcel12


Field_Name East West North South Area Area_in_Words GeometryFK1 Remarks_IDFK2 D_R_Id

Remarks11

PK Remarks_ID

Remarks Mutation_or_Correction_No Nature_of_Mutation_Correction Court_Order_NoFK1 Present_Servey_No

Former_Survey No. Detail12

PK FSD_ID

Former_Survey_No

Land_Type12

PK Land_Type_ID


Farmer1_or_Tenant1

PK,FK2 Present_Farmer_ID

Farmer_or_Tenant_Status Cultivating_Status Area_Land_Cultivated Share_Land_CultivatedFK1 CNICFK2 Order_NoFK2 Owner_ID

R_FormerSurveyNo_Parcel12

PK,FK1 FSD_IDPK,FK2 Present_Servey_No

ID

R_LandType_Parcel12


ID

R_Farmer_Tenant_Parcel12

PK,FK2 Present_Farmer_IDPK,FK1 Present_Servey_No

ID Share_in_Cultivation Start_Time End_Time Name_of_Manager Manager_CNIC Court_Order_No Court_Order_Name Agreement_Details

Owner1

PK,FK4 Owner_ID

NIC_No_or_Reg_No Status Farming_StatusFK1 Owner_NameFK1 Father/Husband_NameFK2 Company_IDFK3,FK4 Present_Farmer_IDFK4 Order_No

R_Owner_Parcel2

PK,FK2 Owner_IDPK,FK1 Present_Servey_No

Share(units) Area_share

Owner_Personal_Details2

PK Owner_NamePK Father/Husband_Name

Title_Designation Father/Husband_NIC Cast/Tribe Village_Resident AddressFK1 Owner_ID

Owner_Company_Details2

PK Company_ID

Name_of_Company Address Share_Holder_Name Share_InfoFK1 Owner_ID

Obligations_and_Liabilities2

PK ID

Tax_Amount Status_GovtDues Status_Loan Collector_ID Collector_Name Lender_ID Lender_Name Lender_Address Obligator_ID Obligator_NameFK2 Transaction_IDFK1 Owner_IDFK3 Return_ID

Loan_Detail2

PK Transaction_ID

Funding_Date Total_Loan_Amount(taken) Loan_start_date Loan_End_date Loan_Interest_Rate Loan_Annuity Term Property_Type Loan_Type Obligation_TypeFK1 ID

H_LoanDetail2

PK ID

Date User_ID Action Old_InterestRate New_InterestRate Old_Loan_Annuity New_Loan_Annuity Old_TotalAmount New_totalAmount Old_EndDate New_EndDateFK1 Transaction_ID

Payment_Obligations_Liabilities_Taxes2

PK Return_ID

Return_Type Payment_Date For_TimePeriod Amount_Paid RemainderFK1 IDFK2 Transaction_IDFK3 D_R_Id

O_OasisDetail1

PK,FK1 Owner_ID

Male_DateTrees Female_DateTrees Eunch_DateTrees Total_Trees Mutation_Or_ErrorNo

Old_Farmer_or_Tenant_ID2

PK,FK1 Present_Farmer_IDPK Old_Farmer_orTenant_ID

Date_Start Date_End

Farmer_or_Tenant_Personal_Details1

PK CNIC

Title_Designatioon Name Adreress Father_or_Husband_Name Father_or_Husband_CNIC Cast_or_Tribe Village_Resident

Other_Persons2

Title Name Cast_or_Tribe Father_Name CNIC_No Status Start_Time End_Time Agreement_Details Order_No Time_PeriodFK1 Present_Farmer_ID

Rent_Amount_Paid/Recieved_Details1

PK Order_NoPK,FK1 Present_Farmer_IDPK,FK2 Owner_ID

Type_of_Rent Total_Rent_Paid Total_RentPaid_Units Rent_Rate Start_Time End_Time Time_Period Agreement_Details Amount_Recieved Rent_collector_Name Rent_Collector_charges

Demand_and_Revenue_Details2

PK D_R_Id

Type Time_Period Start_Date End_Date Local_Rate Units Total_Tax Collector_Name Collector_NICFK1 Return_ID

42


8)- Register Source of Irrigation

Parcel1


Field_Name East West North South Area Area_in_Words GeometryFK1 Remarks_IDFK2 D_R_IdFK3 WaterSource_ID

Source_of_Irrigation

PK WaterSource_ID

Irrigation_Source Name_of_Source Coordinates_Geom Excess_Water_Available Utilization_of_Excess_Water Water_Compensation Desilting_Mode Water_Storage_FacilityFK1 Present_Servey_NoFK2 Repair_IDFK3 WaterMill_ID

Specifications_and_Details

PK,FK1 WaterSource_ID

Date_Installed_or_Built Current_Status Expairy_Date Soil_Type Material_Specification Material_Details

Repair_Maintenance_Info

PK Repair_ID

Rapair_Reason Repair_Date Amount_on_Repair Name_of_Person/Org_Paid_Money Nature_of_PaymentFK1 WaterSource_ID

ShareHolder_Source_of_Irrigation

PK CNIC_No_Reg_No

Name_of_ShareHolder Father_Name Share_Source_of_Irrigation Owner_or_TenantID Share_WaterUsage Status

R_Source_ShareHolder

PK,FK1 CNIC_No_Reg_NoPK,FK2 WaterSource_ID

No_of_Hours Duration_Month_Week Date_Of_RightsAcquisition Order_No

Water_Mill_Info

PK,FK2 WaterMill_ID

Name Year_of_Construction Working_Status Construction_Expenditure Order_No Working_Days Govt_TaxFK2 CNIC_or_ Reg_NoFK1 WaterSource_ID

ShareHolders_WaterMill

PK CNIC_or_ Reg_NoPK,FK1 WaterMill_ID

Owner_Name Sharer_Name Father_Name Mill_Share Water_Share Asiban_Share Status

2.2 Current Cadastral System-Processes

43

• Main Processes identified:

Cadastral System Processes

Land Registration

Process

Ownership Document

Preparation Process

Mutation Process

Error Correction

Process

Binomial Inspection

Process

Settlement Process

• Work Product: A set if activity diagrams that captures the steps anddecision points in the business process

• Objective: is to gain understanding of the business process of thedomain

1) Error CorrectionProcess:Whenever a clericalmistake is detected in landrecords, the Patwari makesthe necessary entries aboutit in the columns of theFard Badar Register

44

Start of Business Process

Wrong Entry in Ownership Register (RHZ)

Report of error in Fard Bdar

Verification of report of error on foil and counterfoil

Counter checking and sanctioning of order

Rejected

Accepted

Fard Badar entry cancelled

Counter checking and sanctioning of order

Revenue Officer takes foil off and send it to tehsil/district record room after order has been passed

Accepted copies of fard badar should be attached to original copy of periodical record of estate

End

Top Package::Patwari

Top Package::Revenue Officer

Top Package::Qanoongo

B) Current Cadastral System-Processes

45

46

To model the designed entities and relationships into a ISO cadastral data

model so as to make it standard compliant

Objective 3:

48

Basic Classes of LADM

49

3.1 Land Administration Domain Model (ISO 19152)

• Countries not re-inventing the wheel:

▫ Cyprus- Implementation of LADM means adaption and extension of themodel to local needs.

▫ Portugal- an object-oriented, conceptual model for the LADM has beendeveloped for the Portuguese Cadastre and the Portuguese Real EstateRegister.

▫ Other countries include Queensland, Indonesia, Japan, Hungry,Netherlands, Vietnam

▫ SOLA project- The FAO Solutions for the Open Land Administration(SOLA) project started in June 2010. The structure of the SOLADatabase is based on the data storage requirements implied by theLADM

▫ European Land Parcel Identification Systems (LPIS) and Infrastructurefor Spatial Information in the European Community (INSPIRE)

50

3.2 LADM Classes and Corresponding Designed Entities in Cadastral System of Pakistan

• Methodology

51

3.3 Adaption of Spatial and Survey Package of LADM according to the Cadastral System of Pakistan

Formulation of rules, triggers and

constraints for historical data maintenance

Implementation in Postgres/Postgis

Preparation of Platform Specific Model (PSM)

Preparation of Platform Independent Model (PIM)

Selection of Packages to be implemented

Mapping of designed entities in correponding LADM classes

Study of ISO Model

• For mapping and implementation purpose spatial and surveypackage has been selected

• Software used : Enterprise Architect

• Adapted LADM ‘survey and spatial representation package‘ has beencreated based on the LADM Survey Package, extended and adaptedwith a number of classes, present in the existing cadastral data

• Adapted profile has ISO standard attributes and functions whereLADM has standard provisions.

52

3.3.1 Adaption of Spatial and Survey Package –Selection of Packages for Implementation

53

Figure 21: Content of Spatial Unit Package with associations to other basic classes

54

Figure 22: Content of Surveying and Representation Package with associations to other basic classes

class Pakistan

EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version






























































«featureType»

Party::Pk_Party

Each spatial unit has a dimension. There can be

a 2D spatial unit, or a 3D spatial unit, with a

spatial unit with dimension "liminal" in

between. See Annex B.

«featureType»

Administrative::Pk_RRR

«featureType»

Administrativ e::Pk_BAUnit

«featureType»

Spatial Unit::Pk_SpatialUnit

+ extAddressID :Oid [0..*]

+ area :Pk_AreaValue [0..*]

+ dimension :Pk_DimensionType [0..1]

+ label :CharacterString [0..1]

+ referencePoint :GM_Point [0..1]

+ suID_khasraNo :Oid

+ surfaceRelation :Pk_SurfaceRelationType [0..1]

+ n_LB_East :int

+ n_LB_West :int

+ n_LB_North :int

+ n_LB_South :int

+ n_fieldName :char [0..1]

+ n_remarks :char [0..*]

+ n_areaWritten :double [0..1]

+ n_status :boolean [0..1]

+ areaClosed() :Boolean

+ computeArea() :Area

+ createArea() :GM_MultiSurface

«featureType»

Spatial Unit::Pk_SpatialUnitGroup

+ hierachyLevel :Integer


+ name :CharacterString [0..1]


+ sugID :Oid

+ geometry :Pk_BoundaryFaceString

«featureType»

Spatial Unit::Pk_LegalSpaceBuildingUnit

+ buildingUnitID :Oid [0..1]

+ type :Pk_BuildingUnitType [0..1]

«featureType»

Spatial Unit::Pk_Lev el

+ extPhysicalNetworkID :Oid [0..1]

+ status [0..1]

+ type [0..1]

+ getGeometry() :GM_Geometry

«featureType»

Spatial Unit::

Pk_RequiredRelationshipSpatialUnit

+ lID :Oid


+ registerType

+ structure [0..1]

+ type [0..1]

«invariant»

{If structure = text then

geometry/topology is optional}

«invariant»

{If dimension = 3D than structure in

LA_Level can be toplogical,

polygon, unstructured or point}

«featureType»

Spatial Unit::Pk_AreaValue

+ relationship :ISO19125_Type [0..1]

Topology relationship ISO19125

_Type as defined ISO 19125

«invariant»

{if dimension=2D then volume not specified

if dimension=3D then area not specified}

«featureType»

Surv eying and Representation::Pk_BoundaryFaceString

+ bfsID :Oid

+ geometry :GM_MultiCurve [0..1]

+ locationByText :CharacterString [0..1]

constraints

{either geometry (2..* points) or locationByText (0 points)}

«featureType»

Surv eying and Representation::Pk_Point

+ estimatedAccuracy :Length

+ interpolationRole :Pk_InterpolationType

+ monumentation :Pk_MonumentationType [0..1]

+ originalLocation :GM_Point

+ pID :Oid

+ pointType :Pk_PointType

+ /productionMethod :LI_Lineage [0..1]

+ transAndResult :LA _Transformation [0..*]

+ GetTransResult() :GM_Point

«featureType»

Surv eying and Representation::

Pk_SpatialSource

+ measurements :OM_Observation [0..*]

+ procedure :OM_Process [0..1]

+ type :Pk_SpatialSourceType

+ pk_surveyorName :char

+ pk_designation :char [0..*]

+ tatimaShajra :binary

+ transactionType :Pk_transactionType

+ transactionName :Pk_transactionName

«featureType»

Surv eying and Representation::Pk_BoundaryFace

+ bfID :Oid

+ geometry :GM_MultiSurface [0..1]

+ locationByText :CharaterString [0..1]

constraints

{either geometry (3..* points) or locationByText (0 points)}

«featureType»

Pk_nLandAndSoilClassification

+ LandTypeID :int

+ soilClassification :Pk_nsoilClassification

+ landClasss :Pk_nlandClassIrrigated,Pk_nlandClassUnIrrigated

+ extent :Pk_BoundaryFaceString

«interface»

Interface Classes::

Pk_SpatialUnitOv erv iew

+ overviewId :Oid

+ overviewDate :DateTime

LA_RegionMap is an interface class, containing a

map representation (at mapDate) of all relevant

information concerning spatial units in a given

region of the specified levels (lId). If no level is

specified, then all spatial units are contained in

the map. As it is an interface object, it is more of

a view on aggregated data from other classes

than containing actual data itself.

«interface»

Interface Classes::

Pk_RegionMap

+ lID :Oid [0..*]

+ mapDate :DateTime

+ mapId :Oid

+ region :GM_Envelope

«featureType»

Special Classes::VersionedObject

+ beginLifespanVersion :DateTime

+ endLifespanVersion :DateTime [0..1]

+ quality :DQ_Element [0..*]

+ source :CI_ResponsibleParty [0..*]

constraints

{endLifespanVersion (n-1) = startLifespanVersion (n)}

«DataType»

Cl_ResponsibleParty

+ individualName :char [0..1]

+ organizationName :char [0..1]

+ positionName :char [0..1]

+ contactInfo :Cl_Contact

+ role :Cl_RoleCode

«DataType»

Cl_Contact

+ phone :int [0..1]

+ address :char [0..1]

+ onlineResource :char [0..1]

+ hoursOfService :char [0..1]

+ contactInstructions :char [0..1]

«codeList»

Cl_RoleCode

+ resourceProvider

+ custodian

+ owner

+ user

+ distributor

+ originator

+ pointofContact

+ principalInvestigator

+ publisher

+ processor

+ author

«DataType»

DQ_Element

+ nameOfMeasure :char [0..1]

+ measureIdentification :int [0..1]

+ measureDescription :char [0..1]

+ evaluationMethodType :DQ_EvaluationMethodTypeCode [0..1]

+ evaluationMethodDescription :char [0..1]

+ evaluationProcedure :Cl_Citation

+ dateTime :DateTime [0..*]

+ result :DQ_Result [1..2]

«codeList»

DQ_Ev aluationMethodTypeCode

+ directExternal

+ directInternal

+ inderict

«DataType»

Cl_Citation

+ title :char

+ alternateTitle :char [0..*]

+ date :Cl_date

+ edition :char [0..1]

+ editionDate :Date [0..1]

+ identifier :MD_Identifier [0..*]

+ citedResponsibleParty :char [0..*]

+ PresentationForm :char [0..*]

+ series :char [0..1]

+ otherCitationDetail :char [0..1]

+ collectiveTitle :char [0..1]

+ ISBN :char [0..1]

+ ISSN :char [0..1]

«codeList»

Spatial Unit::

Pk_RegisterType

+ urban

+ rural

+ mining

+ publicSpace

+ forest

+ all

«codeList»

Spatial Unit::

Pk_DimensionType

+ 0D

+ 1D

+ 2D

+ 3D

+ liminal

«featureType»

Pk_nFormerSurv eyID

+ id :Oid

+ formerSurveyNo :int

+ fieldName :char

«featureType»

Pk_nKhatooni

+ id :Oid

+ khatooniNo :int

«datatype»

Special Classes::Oid

+ localId :CharacterString

+ namespace :CharacterString

«codeList»

Pk_nsoilClassification

+ irrigated :int

+ unirrigated :int

«codeList»

Pk_nlandClassIrrigated

+ Barani

+ Sailabi

+ Abi

+ Rodkohi

+ Chahi

+ Nehri

+ Chahi-Nehri

+ NulChahi

«codeList»

Pk_nlandClassUnirrigated

+ BanjarJadid

+ Banjarqadim

+ GhairMumkin

+ Banjarkham

«featureType»

Pk_nSourceOfIrrigation

+ id :Oid

+ waterSourceID :int

+ nameIrrigationSource :Pk_nNameIrrigationSource

+ ownerID :int [0..*]

+ ownerName :char [0..*]

+ share :Pk_nShare [0..*]

+ timings :Time

+ dateAcquisiotionRights :Date

+ orderNo :char

+ coordinates :Pk_PointType

+ excessWaterAvaialbil ity :boolean

+ excessWaterUtil ization :char

+ waterCompensation :char

+ disil itingMode :char

+ waterStorageFacility :boolean

+ currentStatus :boolean

+ soilType :char

+ materialSpecification :char

+ repairDate :Date

+ repairReason :char

+ repairAmount :Money

+ payerName :char

+ paymentNature :char

«codeList»

Pk_nNameIrrigationSource

+ karezTazi

+ karezGulzar

+ vialaSamil

+ vialaKatir

+ chashmaBalei

«codeList»

Pk_nShare

+ oneShabanaroz

+ oneWali

+ twoSayas

+ oneGuki

Pk_nSourceofIrrigationWaterMill

+ id :Oid

+ currentStatus :int

+ constructionExpenditure :char

+ orderNo :char

+ timings :Time

+ govtTax :Money

+ ownerName :int [0..*]

+ sharerName :char [0..*]

+ millShare :char [0..*]

+ waterShare :char [0..*]

+ asbianShare :char [0..*]

«featureType»

Pk_nChangesInKindofSoil

+ c_Chahi :Rational

+ c_Nehri :Rational

+ c_Barani :Rational

+ c_Other :Rational

+ c_Total :Rational

+ c_dfrncPreviousYear :Rational

+ uc_BanjarKham :Rational

+ uc_BanjarJadid :Rational

+ uc_BanjarQadim :Rational

+ uc_Other :Rational

+ uc_Total :Rational

+ uc_dfrncPreviousYear :Rational

+ grandTotal :Rational

«featureType»

Pk_nStatementOfCustoms

+ id :Oid

+ typeCode :int

+ customHeading :Pk_nCustomHeading

+ customInformation :char

«codeList»

Pk_nCustomHeading

+ 1 Common land, its cultivation and management

+ 2 Rights of grazing in common land

+ 3 Rights to the enjoyment of produce

+ 4 Customs related to the irrigation of land

+ 5 Customs relating to mills, tanks, streams, naural drainage

+ 6 Customs of alluvion and dil luvion

+ 7 The rights to cultivators of all classes not expressly provided for by-law

+ 8 Customry dues payable to vil lage servant and the service to be rendered by them

+ 9 Rights of government to any Nazul property

+ 10 Rights of govt. in respect of fish and fishries

+ Other imporatant usage affecting the rights of land owners, cultivators or other person

«codeList»

Spatial Unit::

Pk_SurfaceRelationType

+ mixed

+ below

+ above

+ onSurface

«codeList»

Spatial Unit::

Pk_BuildingUnitType

+ shared

+ individual

«codeList»

Spatial Unit::

Pk_Lev elContentType

+ building

+ customary

+ mixed

+ network

+ primaryRight

+ responsibil ity

+ restriction

+ informal

«codeList»

Spatial Unit::

Pk_AreaType

+ officialArea

+ nonOfficalArea

+ calculatedArea

+ surveyedArea

«codeList»

Spatial Unit::

Pk_StructureType

+ point

+ polygon

+ text

+ topological

+ unstructuredLine

+ sketch

«featureType»

Special Classes::LA_Source

+ acceptance :DateTime [0..1]

+ extArchiveID :Oid [0..1]

+ lifeSpanStamp :DateTime [0..1]

+ maintype :CI_PresentationFormCode [0..1]

+ recordation :DateTime [0..1]

+ sID :Oid

+ submission :DateTime [0..1]

«invariant»

{if no link to ExtArchive then text in

LA_AdministrativeSource or

measurements in LA_SpatialSource}

«codeList»

Surv eying and Representation::

Pk_MonumentationType

+ MasonaryOrStonePillar

+ MudPillar

+ notMarked

+ TrijunctionPillars

«codeList»

Surv eying and

Representation::

Pk_SpatialSourceType

+ fieldSketch

+ gnssSurvey

+ relativeMeasurement

+ orthoPhoto

+ topoMap

+ video

«codeList»

Surv eying and

Representation::

Pk_InterpolationType

+ midArc

+ start

+ end

+ mid

+ isolated

«codeList»

Surv eying and

Representation::

Pk_PointType

+ source

+ control

+ noSource

«codeList»

Pk_transactionType

+ originalSurveyedParcel

+ mergingParcelTransaction

+ splittingParcelTransaction

+ addingParcelTransaction

+ updatingParcelTrasaction

«codeList»

Pk_transactionName

+ partition

+ sales

+ mortgageWithPosession

+ redemption

+ excahnge

+ gifts

+ nautor

+ conversionOfBaranFieldIntoIrrigatedLand

+ separateCultivationOfShareholders

+party 0..1+rrr

0..*

0..*

baunitAsParty

0..*

+rrr 1..*+baunit

1

0..*

0..*

0..*

0..*

+whole

0..*

+part

1..*

+element

1..*

+set

0..1

+level

0..1

+su

0..*

0..*

minus

0..*0..*

plus 0..*

0..1

referencePoint

0..1

0..*

0,2..*

{ordered}

0..*

0..*

+surveyor

1..*

0..*

+source

0..1

0..*

+sourcePoint

1..*

+source

1..*

1..*

1..*

0..*

plus

0..*

0..*0,3..*

{ordered}

+source

0..1 0..*

0..*

minus

0..*

+baunit 0..*

+overview 0..*

+rrr

0..*

+overview

0..*

+party

0..*

+overview 0..*

+overview 0..*

+spatialUnit

1

+spatialUnit

0..*

+map

0..*

+map

0..*

+level

0..*

+represented by 0..1

0..*

3.3.2 Iteration 1-PIM

55

56

3.3.2 Features of Designed PIM

1) Consists of 4 types of sub classesclass Pakistan

EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version







































«featureType»



+ areaType :Pk_AreaType [0..*]





+ sourceParcel :array

+ n_LB_East :int

+ n_LB_West :int

+ n_LB_North :int

+ n_LB_South :int



+ n_status :boolean




+ pk_spatialunit_current() :Pk_SpatialUnit

+ pk_spatialunit_update()

+ pk_spatialunit_del()

+ pk_spatialunit_insert()

«rule»


«trigger»


«featureType»


+ sugID :Oid

+ hierachyLevelID :Integer

+ hierarchyName :CharacterString [0..1]

+ labelName :CharacterString [0..1]


+ geometry :GM_Multisurface

constraints

{relavant spatial units within spatial unit group}

«featureType»




+ geometry :GM_Multicurve

«featureType»


+ IID :Oid

+ name :char(50) [0..1]

+ registerType :Pk_RegisterType

+ structure :Pk_StructureType

+ type :Pk_LevelContentType [0..1]

+ status :boolean [0..1]


«featureType»

Spatial Unit::


+ lID :Oid



+ structure :Pk_StructureType [0..1]

+ contentType :Pk_LevelContentType [0..1]

«invariant»



+level

0..1

+su

0..*

+whole

*

+part

*

+element

1..*

+set

0..1

57


1) Consists of 4 types of sub classes

class Pakistan








































«featureType»









+ n_LB_East :int

+ n_LB_West :int

+ n_LB_North :int

+ n_LB_South :int



+ n_status :boolean








«rule»


«trigger»


«featureType»


+ sugID :Oid

+ hierachyLevelID :Integer

+ hierarchyName :CharacterString [0..1]

+ labelName :CharacterString [0..1]


+ geometry :GM_Multisurface

constraints

{relavant spatial units within spatial unit group}

«featureType»




+ geometry :GM_Multicurve

«featureType»


+ IID :Oid

+ name :char(50) [0..1]


+ structure :Pk_StructureType

+ type :Pk_LevelContentType [0..1]

+ status :boolean [0..1]


«featureType»

Spatial Unit::


+ lID :Oid



+ structure :Pk_StructureType [0..1]

+ contentType :Pk_LevelContentType [0..1]

«invariant»



+level

0..1

+su

0..*

+whole

*

+part

*

+element

1..*

+set

0..1

2) Standard LADM Attributes andSpecific attributes related to aparticular country.

3) Views

4) Inheritance

58

3.3.2 Features of Designed PIMclass Pakistan

EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version



































«featureType»









+ n_LB_East :int

+ n_LB_West :int

+ n_LB_North :int

+ n_LB_South :int



+ n_status :boolean








«rule»


«trigger»


«invariant»



class Pakistan

EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version




























«view»

Pk_currentSpatialUnit

«view»

pk__currentBoundaryeFace

class Pakistan





























«featureType»






constraints


class Pakistan































«featureType»

Special Classes::LA_Source

+ acceptance :DateTime [0..1]

+ extArchiveID :Oid [0..1]

+ l ifeSpanStamp :DateTime [0..1]

+ maintype :CI_PresentationFormCode [0..1]

+ recordation :DateTime [0..1]

+ sID :Oid

+ submission :DateTime [0..1]

«invariant»

{if no l ink to ExtArchive then text in

LA_AdministrativeSource or

measurements in LA_SpatialSource}

5) Special Classes

▫ Enumerations

▫ Code Lists

59


class Pakistan

EA 10.0 Unregistered Trial Version



























«enumaration»

Spatial Unit::


+ mixed

+ below

+ above

+ onSurface

class Pakistan






























«enumaration»

Spatial Unit::


+ building

+ customary

+ mixed

+ network

+ primaryRight

+ responsibil ity

+ restriction

+ informal

class Pakistan






























«enumeration»

Surv eying and

Representation::

Pk_SpatialSourceType

Attributes

+ fieldSketch

+ gnssSurvey

+ relativeMeasurement

+ orthoPhoto

+ topoMap

+ video

class Pakistan





























«enumeration»

Pk_nlandClassIrrigated

Attributes

+ Barani

+ Sailabi

+ Abi

+ Rodkohi

+ Chahi

+ Nehri

+ Chahi-Nehri

+ NulChahi

class Pakistan




























«codeList»

Spatial Unit::

Pk_AreaType

+ officialArea

+ nonOfficalArea

+ calculatedArea

+ surveyedArea

class Pakistan

EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version





























«codeList»

Pk_nCustomHeading

+ 1 Common land, its cultivation and management

+ 2 Rights of grazing in common land

+ 3 Rights to the enjoyment of produce

+ 4 Customs related to the irrigation of land

+ 5 Customs relating to mills, tanks, streams, naural drainage

+ 6 Customs of alluvion and dilluvion

+ 7 The rights to cultivators of all classes not expressly provided for by-law

+ 8 Customry dues payable to vil lage servant and the service to be rendered by them

+ 9 Rights of government to any Nazul property

+ 10 Rights of govt. in respect of fish and fishries

+ Other imporatant usage affecting the rights of land owners, cultivators or other person

class Pakistan





























«codeList»

Surv eying and

Representation::

Pk_InterpolationType

+ midArc

+ start

+ end

+ mid

+ isolated

60


class Pakistan

EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version

































«featureType»

Pk_nOtherGeneralFeatures

+ sugId :Oid

+ mapPartNo :int

+ vil lageNo :int

+ name :char(100)

+ description :char(1000)

+ geometry :geom

«featureType»

Pk_nMap

+ sugID :Oid

+ mapPartNo :int

+ surveyType :char(50)

+ vil lageName :char(50)

+ vil lageNo :int

+ districtName :char(50)

+ tehsilName :char(50)

+ dateofPreparationofMap :date

+ scale :char(50)

+ spatialRefSystem :char(500)

+ spatialUnitGroupSugID :Oid

+ map_masawi :binary

«featureType»

SatelliteImagery

+ MapSugID :int

+ satell iteImgNo :int

+ description :char(500)

+ satelliteImgDate :Date

+ spatialRefSystem :char(1000)

+ SatelliteImage :raster

6) Separate classes tostore map and satelliteimagery

61

class DDL

EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version
























































































«enumeration»

Pakistan::Cl_RoleCode

Attributes

+ resourceProvider

+ custodian

+ owner

+ user

+ distributor

+ originator

+ pointofContact

+ principalInvestigator

+ publisher

+ processor

+ author

«enumeration»

Pakistan::

DQ_Ev aluationMethodTypeCode

Attributes

+ directExternal

+ directInternal

+ inderict

«DataType»

Pakistan::Cl_Contact

+ phone :int [0..1]

+ address :char [0..1]

+ onlineResource :char [0..1]

+ hoursOfService :char [0..1]

+ contactInstructions :char [0..1]

«DataType»

Pakistan::Cl_Citation

+ title :char(100)

+ alternateTitle :char(100) [0..1]

+ date :DateTime

+ edition :char(50) [0..1]

+ editionDate :Date [0..1]

+ identifier :int [0..*]

+ citedResponsibleParty :char(100) [0..*]

+ PresentationForm :char(100) [0..*]

+ series :char(100) [0..1]

+ otherCitationDetail :char(500) [0..1]

+ collectiveTitle :char(100) [0..1]

+ ISBN :char(200) [0..1]

+ ISSN :char(200) [0..1]

Cl_Contact

«column»

phone :int

address :char

onlineResource :char

hoursOfService :char

contactInstructions :char

*PK cl_ContactID :Integer

«PK»

+ PK_Cl_Contact(smallint)

DQ_Element

«column»

nameOfMeasure :char

measureIdentification :int

measureDescription :char

evaluationMethodType :DQ_EvaluationMethodTypeCode

evaluationMethodDescription :char

evaluationProcedure :Cl_Citation

dateTime :DateTime

result :DQ_Result

*PK dQ_ElementID :Integer

«PK»

+ PK_DQ_Element(smallint)

«DataType»

Pakistan::Cl_ResponsibleParty

+ individualName :char [0..1]

+ organizationName :char [0..1]

+ positionName :char [0..1]

+ contactInfo :Cl_Contact

+ role :Cl_RoleCode

«DataType»

Pakistan::DQ_Element

+ nameOfMeasure :char [0..1]

+ measureIdentification :int [0..1]

+ measureDescription :char [0..1]

+ evaluationMethodType :DQ_EvaluationMethodTypeCode [0..1]

+ evaluationMethodDescription :char [0..1]

+ evaluationProcedure :Cl_Citation

+ dateTime :DateTime [0..*]

+ result :DQ_Result [1..2]

Cl_ResponsibleParty

«column»

individualName :char

organizationName :char

positionName :char

contactInfo :Cl_Contact

role :Cl_RoleCode

*PK cl_ResponsiblePartyID :Integer

«PK»

+ PK_Cl_ResponsibleParty(smallint)

VersionedObject

«column»

beginLifespanVersion :DateTime

endLifespanVersion :DateTime

quality :DQ_Element

source :CI_ResponsibleParty

*PK versionedObjectID :integer

«PK»

+ PK_VersionedObject(integer)

Pk_nParentCodeLists

«column»

codeListName :char(200)

codeListDescription :char(1000)

className :char(50)

tableName :char(50)

*PK pk_nParentCodeListsID :Integer

«PK»

+ PK_Pk_nParentCodeLists(smallint)

«index»

+ idx_Pk_nParentCodeLists()

Pk_nParentDataTypeList

«column»

dataTypeName :char(100)

dataTypeDescription :char(1000)

className :char(50)

tableName :char(50)

*PK pk_nParentDataTypeListID :Integer

«PK»

+ PK_Pk_nParentDataTypeList(smallint)

«index»

+ idx_Pk_nParentDataTypeList()

Pk_nParentEnumaration

«column»

enumerationName :char(200)

enumerationDescription :char(1000)

className :char(50)

tableName :char(50)

*PK pk_nParentEnumarationID :Integer

«PK»

+ PK_Pk_nParentEnumaration(smallint)

«index»

+ idx_Pk_nParentEnumaration()

Pk_SpatialUnit

«column»

*pfK suID_khasraNo :integer

FK pk_LevelID :integer

n_areaWritten :double

dimension :Pk_DimensionType

label :CharacterString

surfaceRelation :Pk_SurfaceRelationType

n_LB_East :int

n_LB_West :int

n_LB_North :int

n_LB_South :int

n_fieldName :char

n_status :boolean

referencePoint :GM_Point

«FK»

+ FK_Pk_SpatialUnit_Pk_SpatialUnit(integer)

+ FK_Pk_SpatialUnit_Pk_Leve()

«PK»

+ PK_Pk_SpatialUnit(integer)

«index»

+ idx_suID_khasraNo()

JoinPk_SpatialSourceToPk_SpatialUnit

«column»

FK pk_SpatialUnitID :Integer

FK pk_SpatialSourceID :Integer

«FK»

+ Pk_SpatialUnit(Integer)

+ Pk_SpatialSource(Integer)

JoinPk_SpatialUnitGroupToPk_SpatialUnit

«column»

*PK Id :integer

FK suID_khasraNo :integer

sugID :integer

«FK»

+ FK_JoinPk_SpatialUnitGroupToPk_SpatialUnit_Pk_SpatialUnit(integer)

+ FK_JoinTableToSpatialUnitGroup(integer)

«PK»

+ PK_JoinPk_SpatialUnitGroupToPk_SpatialUnit(integer)

plus

«column»


FK pk_BoundaryFaceID :Integer

«FK»

+ Pk_BoundaryFace(Integer)


minus

«column»


FK pk_BoundaryFaceID :Integer

«FK»


+ Pk_BoundaryFace(Integer)

minus

«column»

pk_SpatialUnitID :Integer

plus

«column»


JoinPk_SpatialUnitToPk_RegionMap

«column»

*pfK pk_SuidKhasraNo :integer

*pfK pk_RegionMapID :integer

Id :integer


«PK»

+ PK_JoinPk_SpatialUnitToPk_RegionMap(integer, integer)

«FK»

+ Fk_Pk_RegionMap(smallint)

+ Fk_Pk_SpatialUnit(smallint)

+ Pk_RegionMap(integer)


JoinPk_SpatialUnitToLA_PartyPortfolio

«column»


JoinPk_SpatialUnitToPk_BAUnit

«column»


«codeList»

Spatial Unit::

Pk_RegisterType

+ urban

+ rural

+ mining

+ publicSpace

+ forest

+ all

«codeList»

Spatial Unit::

Pk_DimensionType

+ 0D

+ 1D

+ 2D

+ 3D

+ liminal

«datatype»

Special Classes::Oid

+ localId :CharacterString

+ namespace :CharacterString

«enumaration»

Spatial Unit::


+ mixed

+ below

+ above

+ onSurface

«enumaration»

Spatial Unit::

Pk_BuildingUnitType

+ shared

+ individual

«enumaration»

Spatial Unit::


+ building

+ customary

+ mixed

+ network

+ primaryRight

+ responsibil ity

+ restriction

+ informal

«codeList»

Spatial Unit::

Pk_AreaType

+ officialArea

+ nonOfficalArea

+ calculatedArea

+ surveyedArea

«codeList»

Spatial Unit::

Pk_StructureType

+ point

+ polygon

+ text

+ topological

+ unstructuredLine

+ sketch

Remarks

«column»

*PK Id :integer

reamarksDescription :char(1000)

areaType :char(10)


«FK»

+ FK_Remarks_Pk_SpatialUnit(integer)

«PK»

+ PK_Remarks(integer)

Pk_SpatialUnitGroup

«column»

*PK sugID :integer

hierachyLevelID :Integer

hierarchyName :CharacterString



geometry :GM_Multisurface

«PK»

+ PK_Pk_sugID(integer)

«index»

+ idx_Pk_sugID()

+ idx_Pk_geometry()


«column»

*PK pk_RequiredRelationshipSpatialUnitID :Integer

lID :Oid

name :CharacterString

registerType :Pk_RegisterType

structure :Pk_StructureType

contentType :Pk_LevelContentType

FK suId_khasraNo :integer

«FK»

+ FK_Pk_RequiredRelationshipSpatialUnit_Pk_SpatialUnit(integer)

«PK»

+ PK_Pk_RequiredRelationshipSpatialUnit(smallint)

JoinPk_RegionMapToPk_Lev el

«column»

*pfK LevelID :integer

*pfK RegionMapID :integer

* Id :integer

FK pk_LevelID :Integer

FK pk_RegionMapID :Integer

«PK»

+ PK_JoinPk_RegionMapToPk_Level(integer, integer)

«FK»

+ FK_Pk_Level(smallint)

+ FK_Pk_RegionMap(smallint)

+ Pk_Level(Integer)

+ Pk_RegionMap(Integer)

Pk_Lev el

«column»

*PK pk_LevelID :integer

IID :Oid

name :char(50)

registerType :Pk_RegisterType

structure :Pk_StructureType

type :Pk_LevelContentType

status :boolean

«PK»

+ PK_Pk_Level(integer)

Pk_LegalSpaceBuildingUnit

«column»

*PK pk_LegalSpaceBuildingUnitID :Integer

buildingUnitID :Oid

type :Pk_BuildingUnitType

geometry :GM_Multicurve

«PK»

+ PK_Pk_LegalSpaceBuildingUnit(smallint)

«trigger»

+ populateRegionMap()

JoinPk_LegalSpaceBuildingUnitToHUN_Building

«column»

FK pk_LegalSpaceBuildingUnitID :Integer

«FK»

+ Pk_LegalSpaceBuildingUnit(Integer)

Pk_nFormerSurv eyID

«column»

*PK ID :integer

formerSurveyNo :int

fieldName :char

FK pk_suID_khasraNo :integer

«FK»

+ FK_Pk_nFormerSurveyID_Pk_SpatialUnit(integer)

«PK»

+ PK_Pk_nFormerSurveyID(integer)

Pk_SpatialUnitOv erv iew

«column»

*PK pk_SpatialUnitOverviewID :Integer

overviewId :Oid

overviewDate :DateTime

suID_khasraNo :integer

«PK»

+ PK_Pk_SpatialUnitOverview(smallint)

JoinPk_RRRToPk_SpatialUnitOv erv iew

«column»

FK pk_SpatialUnitOverviewID :Integer

«FK»

+ Pk_SpatialUnitOverview(Integer)

JoinPk_PartyToPk_SpatialUnitOv erv iew

«column»


«FK»


JoinPk_BAUnitToPk_SpatialUnitOv erv iew

«column»


«FK»


Pk_RegionMap

«column»

lID :Oid

mapDate :DateTime

mapId :Oid

region :GM_Envelope

spatialUnitInfo :Array

*PK pk_RegionMapID :Integer

«PK»

+ PK_Pk_RegionMap(Integer)

«proc»

+ populateRegionMapTable()

LA_Source

«column»

*PK lA_SourceID :Integer

acceptance :DateTime

extArchiveID :Oid

lifeSpanStamp :DateTime

maintype :CI_PresentationFormCode

recordation :DateTime

sID :Oid

submission :DateTime

«PK»

+ PK_LA_Source(smallint)

Pk_SpatialSource

«column»

*PK pk_SpatialSourceID :Integer


measurements :OM_Observation

procedure :n_Pk_SurveyType

type :Pk_SpatialSourceType

n_pk_surveyorName :char

n_pk_designation :char

n_tatimaShajra :binary

n_Pk_TransactionType :n_Pk_transactionType

n_Pk_TransactionName :n_Pk_transactionName

«FK»

+ FK_Pk_SpatialSource_Pk_SpatialUnit(integer)

«unique»

+ UQ_Pk_SpatialSource_suID_khasraNo(integer)

«PK»

+ PK_Pk_SpatialSource(smallint)

JoinPk_PointToPk_SpatialSource

«column»


FK pk_PointID :Integer

Id

«FK»


+ Pk_Point(Integer)

JoinPk_PartyToPk_SpatialSource

«column»


«FK»


JoinPk_BAUnitToPk_SpatialSource

«column»


«FK»


Pk_Point

«column»

*PK pk_PointID :Integer

estimatedAccuracy :Length

interpolationRole :Pk_InterpolationType

monumentation :Pk_MonumentationType

originalLocation :GM_Point

pID :Oid

pointType :Pk_PointType

productionMethod :LI_Lineage

transAndResult :LA _Transformation


«FK»

+ FK_Pk_Point_Pk_SpatialUnit(integer)

«PK»

+ PK_Pk_Point(smallint)

JoinPk_BoundaryFaceToPk_Point

«column»

*PK pk_PointID :integer

*pfK pk_BoundaryFaceID :integer

Id :integer

«PK»

+ PK_JoinPk_BoundaryFaceToPk_Point(integer, integer)

«FK»

+ Pk_Point(integer)

+ Pk_BoundaryFace(smallint)

JoinPk_BoundaryFaceStringToPk_Point

«column»


«FK»

+ Pk_Point(Integer)

geometry

«column»


«FK»

+ Pk_Point(Integer)

Pk_BoundaryFace

«column»

*PK pk_BoundaryFaceID :Integer

bfID :Oid

geometry :GM_MultiSurface(simplePolygon or toplogicalPolygon)

locationByText :CharaterString

computedArea :ST_Area(Polygon)

FK Pk_SpatialSourceID :integer

FK suID_KhasraNo :integer

«FK»

+ FK_Pk_BoundaryFace_Pk_SpatialSource(integer)

+ FK_Pk_BoundaryFace_Pk_SpatialUnit(integer)

«PK»

+ PK_Pk_BoundaryFace(smallint)


«column»

*PK pk_nLandAndSoilClassificationID :Integer

FK suId_KhasraNo :integer

LandTypeID :int

soilClassification :Pk_nsoilClassification

landClasss :Pk_nlandClassIrrigated,Pk_nlandClassUnIrrigated

extent :Pk_BoundaryFaceString

«FK»

+ FK_Pk_nLandAndSoilClassification_Pk_SpatialUnit(integer)

«PK»

+ PK_Pk_nLandAndSoilClassification(smallint)

Pk_nSourceOfIrrigation

«column»

*PK pk_nSourceOfIrrigationID :Integer


id :Oid

waterSourceID :int

nameIrrigationSource :Pk_nNameIrrigationSource

ownerID :int

ownerName :char

share :Pk_nShare

timings :Time

dateAcquisiotionRights :Date

orderNo :char

coordinates :Pk_PointType

excessWaterAvaialbil ity :boolean

excessWaterUtil ization :char

waterCompensation :char

disil itingMode :char

waterStorageFacility :boolean

currentStatus :boolean

soilType :char

materialSpecification :char

repairDate :Date

repairReason :char

repairAmount :Money

payerName :char

paymentNature :char

«FK»

+ FK_Pk_nSourceOfIrrigation_Pk_SpatialUnit(integer)

«PK»

+ PK_Pk_nSourceOfIrrigation(smallint)

Pk_nSourceofIrrigationWaterMill

«column»

*PK pk_nSourceofIrrigationWaterMillID :Integer

FK pk_nSourceOfIrrigationID :Integer


id :Oid

currentStatus :int

constructionExpenditure :char

orderNo :char

timings :Time

govtTax :Money

ownerName :int

sharerName :char

millShare :char

waterShare :char

asbianShare :char

sourceOfIrrigationID :int

suid_KhasraNo :int

«FK»

+ FK_Pk_nSourceofIrrigationWaterMill_Pk_nSourceOfIrrigation(Integer)

+ FK_Pk_nSourceofIrrigationWaterMill_Pk_SpatialUnit(Integer)

«PK»

+ PK_Pk_nSourceofIrrigationWaterMill(smallint)

Pk_nChangesInKindofSoil

«column»

*PK pk_nChangesInKindofSoilID :Integer

FK sugId :integer

c_Chahi :Rational

c_Nehri :Rational

c_Barani :Rational

c_Other :Rational

c_Total :Rational

c_dfrncPreviousYear :Rational

uc_BanjarKham :Rational

uc_BanjarJadid :Rational

uc_BanjarQadim :Rational

uc_Other :Rational

uc_Total :Rational

uc_dfrncPreviousYear :Rational

grandTotal :Rational

«FK»

+ FK_Pk_nChangesInKindofSoil_Pk_SpatialUnitGroup(integer)

«PK»

+ PK_Pk_nChangesInKindofSoil(smallint)

Pk_nStatementOfCustoms

«column»

*PK pk_nStatementOfCustomsID :Integer

FK sugID :integer

id :Oid

typeCode :int

customHeading :Pk_nCustomHeading

customInformation :char

«FK»

+ FK_Pk_nStatementOfCustoms_Pk_SpatialUnitGroup(integer)

«PK»

+ PK_Pk_nStatementOfCustoms(smallint)

Pk_nCustomHeading

«column»

1 Common land, its cultivation and management

2 Rights of grazing in common land

3 Rights to the enjoyment of produce

4 Customs related to the irrigation of land

5 Customs relating to mills, tanks, streams, naural drainage

6 Customs of alluvion and dil luvion

7 The rights to cultivators of all classes not expressly provided for by-law

8 Customry dues payable to vil lage servant and the service to be rendered by them

9 Rights of government to any Nazul property

10 Rights of govt. in respect of fish and fishries

Other imporatant usage affecting the rights of land owners, cultivators or other person

*PK pk_nCustomHeadingID :Integer

«PK»

+ PK_Pk_nCustomHeading(Integer)

+FK_Remarks_Pk_SpatialUnit

0..*

(suID_khasraNo = suID_khasraNo)

«FK»

+PK_Pk_SpatialUnit

1

+F

K_

Pk_

Re

qu

ired

Re

latio

nsh

ipS

pa

tialU

nit_

Pk_

Sp

atia

...

0..*

(su

Id_

kha

sra

No

= s

uID

_kh

asr

aN

o)

«FK»

+P

K_

Pk_

Sp

atia

lUn

it

1

+FK_JoinTableToSpatialUnitGroup 0..*

(suID_khasraNo = sugID)

«FK»

+PK_Pk_sugID

1

+FK_JoinPk_SpatialUnitGroupToPk_SpatialUnit_Pk_S...

0..*


«FK»

+PK_Pk_SpatialUnit

1

+FK_Pk_SpatialUnit_Pk_SpatialUnit

0..*


«FK»

+PK_Pk_SpatialUnit

1

+FK_Pk_SpatialUnitGroup_Pk_SpatialUnitGroup0..*

(sugID = sugID)

«FK»

+PK_Pk_sugID

1

+FK_Pk_nFormerSurveyID_Pk_SpatialUnit

0..*

(pk_suID_khasraNo = suID_khasraNo)

«FK»

+PK_Pk_SpatialUnit

1

+FK_Pk_SpatialUnit_Pk_Level 0..*

«FK»

+PK_Pk_Level 1

*1

+FK_JoinPk_RegionMapToPk_Level_Pk_RegionMap

*

«FK»

+PK_Pk_RegionMap

1

+FK_JoinPk_SpatialUnitToPk_RegionMap_Pk_RegionMap*1

1

+FK_Pk_SpatialSource_Pk_SpatialUnit 0..*


«FK»

+PK_Pk_SpatialUnit 1

+FK_Pk_Point_Pk_SpatialUnit

0..*


«FK»


+FK_Pk_BoundaryFace_Pk_SpatialUnit

0..*

(suID_KhasraNo = suID_khasraNo)

«FK»

+PK_Pk_SpatialUnit

1

+FK_Pk_BoundaryFace_Pk_SpatialSource

0..*

(Pk_SpatialSourceID = pk_SpatialSourceID)

«FK»

+PK_Pk_SpatialSource 1

+FK_Pk_nLandAndSoilClassification_Pk_SpatialUnit0..*

(suId_KhasraNo = suID_khasraNo)

«FK»

+PK_Pk_SpatialUnit

1

+FK_Pk_nSourceOfIrrigation_Pk_SpatialUnit

0..*


«FK»

+PK_Pk_SpatialUnit

1

+FK_Pk_nSourceofIrrigationWaterMill_Pk_nSourceOf... 0..*

(pk_nSourceOfIrrigationID = pk_nSourceOfIrrigationID)

«FK»

+PK_Pk_nSourceOfIrrigation

1

+FK_Pk_nSourceofIrrigationWaterMill_Pk_SpatialUnit 0..*

(pk_SpatialUnitID = suID_khasraNo)

«FK»


+FK_Pk_nChangesInKindofSoil_Pk_SpatialUnitGroup

0..*

(sugId = sugID)

«FK»

+PK_Pk_sugID

1

+FK_Pk_nStatementOfCustoms_Pk_SpatialUnitGroup 0..*

(sugID = sugID)

«FK»

+PK_Pk_sugID 1

3.3.3 Iteration 2 - PSM

• Transformation from object oriented UML model (PIM) to aPlatform Specifc Model, targeting an object relational PostgreSQLdatabse, with a PostGIS extension for spatial data and functions

• Transformation will convert:

▫ Classes = Tables

▫ Attributes = Columns

▫ Association = Relationship Tables (in case of RDBMS relationships and intersection tables to represent many to many associations)

▫ Generate primary and foreign keys

▫ Code Lists = Look up tables

▫ ISO 19107 data types GM_Point, GM_Multisurface = PostGIS geometry data type.

▫ Generate simple and geometry indices

62

3.3.3 Features of Designed PSM

• Composite spatial unit id= SUGId(VillageID) + ParcelNo(KhasraNo)

• 0 -* attributes were broken down into separate tables

• Primary and Foreign key constraints, indexes

• The "Transformation from PSM to DDL (PostgreSQL/PostGIS)" (section 7.3), resulting in Data Definition Language (DDL) and Data Manipulation Scripts (DML) scripts to create the PostgreSQL/PostGIS database.

63

3.3.3 Features of Designed PSMclass DDL







































Pk_SpatialUnit

«column»

suID_khasraNo :Oid

areaType :Pk_AreaType

FK pk_LevelID :integer

n_areaWritten :double

dimension :Pk_DimensionType


surfaceRelation :Pk_SurfaceRelationType

sourceParcel :array

n_LB_East :int

n_LB_West :int

n_LB_North :int

n_LB_South :int

n_fieldName :char

n_remarks :char

n_status :boolean



FK pk_nLandAndSoilClassificationID :Integer

FK pk_nSourceOfIrrigationID :Integer

*PK pk_SpatialUnitID :Integer

FK level :Integer

«FK»

+ FK_Pk_SpatialUnit_Pk_SpatialUnit(integer)

+ FK_Pk_SpatialUnit_Pk_Leve()

+ referencePoint(Integer)

+ FK_Pk_SpatialUnit_Pk_nLandAndSoilClassification(Integer)

+ FK_Pk_SpatialUnit_Pk_nSourceOfIrrigation(Integer)

+ FK_level(Integer)

+ FK_Pk_SpatialUnit_VersionedObject(Integer)

+ FK_Pk_SpatialUnit_Pk_SpatialUnit(Integer)

+ FK_Pk_SpatialUnit_Pk_Level(integer)

«PK»

+ PK_Pk_SpatialUnit(Integer)

+ PK_Pk_SpatialUnit(integer)

«index»

+ idx_suID_khasraNo()

class DDL































EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version Pk_SpatialSource

«column»

*PK pk_SpatialSourceID :Integer


measurements :OM_Observation

procedure :n_Pk_SurveyType

type :Pk_SpatialSourceType

n_pk_surveyorName :char

n_pk_designation :char

n_tatimaShajra :binary

n_Pk_TransactionType :n_Pk_transactionType

n_Pk_TransactionName :n_Pk_transactionName

«FK»

+ FK_Pk_SpatialSource_Pk_SpatialUnit(integer)

«unique»

+ UQ_Pk_SpatialSource_suID_khasraNo(integer)

«PK»

+ PK_Pk_SpatialSource(smallint)

class DDL































«column»

*PK pk_nLandAndSoilClassificationID :Integer

FK suId_KhasraNo :integer

LandTypeID :int

soilClassification :Pk_nsoilClassification

landClasss :Pk_nlandClassIrrigated,Pk_nlandClassUnIrrigated

extent :Pk_BoundaryFaceString

«FK»

+ FK_Pk_nLandAndSoilClassification_Pk_SpatialUnit(integer)

«PK»

+ PK_Pk_nLandAndSoilClassification(smallint)

64

3.3.4 Generation of DDL Scripts

• Actual implementation in PostgreSQL/PostGIS:

1) Create enumerations and Data Types - For example Pk_DimensionType.

2) Create Tables

3) Create Geographic Columns

4) Create Primary Key Constraints Primary key constraints.

5) Create Constraints The non-primary key base table constraints are generated (Unique key [uk], Check [check], and Foreign key [fk] constraint).

6) Create Indexes

7) Create Views

8) Populate Look-up Tables <<CodeList>> tables will be populated with a DML insert script

65

3.3.4 Implementation of the Adapted LADM Packages in PostgreSQL

3.3.5 Historical Data Maintenance Through Adaptive LADM Survey Package

• Class VersionedObject : To manage and maintain historicaldata in the database.

66

class Pakistan





























«featureType»






constraints


1) Adding versioned object id in the spatialUnit Table:

ALTER TABLE "public"."pk_spatialunit" DROP CONSTRAINT "pk_pk_spatialunit", ADD PRIMARY KEY ("versionedobjectid");

2) Creating view on spatial unit table to see only current parecls:

CREATE VIEW "public"."pk_spatialunit_current" AS SELECT "beginlifespanversion","endlifespanversion","quality","source","versionedobjectid","suid_khasrano","pk_levelid","n_areawritten","dimension","parcellabel","surfacerelation","n_lb_east","n_lb_west","n_lb_north","n_lb_south","n_fieldname","n_status","geom" FROM "public"."pk_spatialunit" WHERE "endlifespanversion" IS NULL;

67

3.3.5 Implementation Code (Example-SpatialUnit)

3) Creating function to return only current spatial units in the table:

CREATE OR REPLACE FUNCTION"public"."pk_spatialunit_at_time"(timestamp)RETURNS SETOF "public"."pk_spatialunit_current" AS$$SELECT"beginlifespanversion","endlifespanversion","quality","source","versionedobjectid","suid_khasrano","pk_levelid","n_areawritten","dimension","parcellabel","surfacerelation","n_lb_east","n_lb_west","n_lb_north","n_lb_south","n_fieldname","n_status","geom"FROM "public"."pk_spatialunit" WHERE (SELECT CASE WHEN "endlifespanversion"IS NULL THEN ("beginlifespanversion" <=$1) ELSE ("beginlifespanversion" <= $1AND "endlifespanversion" > $1) END );$$LANGUAGE 'SQL';

68

4) Creating function to invoke an insert trrigerwhen called:

CREATE OR REPLACE FUNCTION "public"."pk_spatialunit_insert"()

RETURNS trigger AS

$$

BEGIN

if NEW."beginlifespanversion" IS NULL then

NEW."beginlifespanversion" = now();

NEW."endlifespanversion" = null;

end if;

RETURN NEW;

END;

$$

LANGUAGE 'plpgsql';


69

5) Creating function to invoke an update trriger when called:

CREATECREATE OR REPLACE FUNCTION "public"."pk_spatialunit_update"()

RETURNS TRIGGER AS

$$

BEGIN

IF OLD."endlifespanversion" IS NOT NULL THEN

RETURN NULL;

END IF;

IF NEW."endlifespanversion" IS NULL THEN

INSERT INTO "public"."pk_spatialunit" ("beginlifespanversion","endlifespanversion","quality","source","versionedobjectid","suid_khasrano","pk_levelid","n_areawritten","dimension","parcellabel","surfacerelation","n_lb_east","n_lb_west","n_lb_north","n_lb_south","n_fieldname","n_status","geom", "beginlifespanversion", "endlifespanversion") VALUES (OLD."beginlifespanversion",OLD."endlifespanversion",OLD."quality",OLD."source",OLD."versionedobjectid",OLD."suid_khasrano",OLD."pk_levelid",OLD."n_areawritten",OLD."dimension",OLD."parcellabel",OLD."surfacerelation",OLD."n_lb_east",OLD."n_lb_west",OLD."n_lb_north",OLD."n_lb_south",OLD."n_fieldname",OLD."n_status",OLD."geom", OLD."beginlifespanversion", current_timestamp);

NEW."beginlifespanversion" = current_timestamp;

END IF;

RETURN NEW;

END;

$$

LANGUAGE 'plpgsql';


6) Creating rule to set endlifspanversion attribute in case of delete:

CREATE RULE "pk_spatialunit_del" AS ON DELETE TO "public"."pk_spatialunit“ DO INSTEAD UPDATE "public"."pk_spatialunit" SET "endlifespanversion" = current_timestamp WHERE "versionedobjectid" = OLD."versionedobjectid" AND "endlifespanversion" IS NULL;

70

7) Creating triggers to call update and insert function upon each row update or insert:

CREATE TRIGGER "pk_spatialunit_update" BEFORE UPDATE ON "public"."pk_spatialunit"FOR EACH ROW EXECUTE PROCEDURE "public"."pk_spatialunit_update"();

CREATE TRIGGER "pk_spatialunit_insert" BEFORE INSERT ON "public"."pk_spatialunit"FOR EACH ROW EXECUTE PROCEDURE "public"."pk_spatialunit_insert"();


8) Creating 3 rules on view"public"."pk_spatialunit_current" formed in the 2nd

step:

i) Delete rule on view

CREATE OR REPLACE RULE "_DELETE" AS ON DELETETO "public"."pk_spatialunit_current" DO INSTEADDELETE FROM "public"."pk_spatialunit" WHERE"suid_khasrano" = old."suid_khasrano";

ii) Delete rule on view

CREATE OR REPLACE RULE "_INSERT" AS ON INSERT TO "public"."pk_spatialunit_current" DO INSTEAD

INSERT INTO "public"."pk_spatialunit" ("beginlifespanversion","endlifespanversion","quality","source","versionedobjectid","suid_khasrano","pk_levelid","n_areawritten","dimension","parcellabel","surfacerelation","n_lb_east","n_lb_west","n_lb_north","n_lb_south","n_fieldname","n_status","geom") VALUES (NEW."beginlifespanversion",NEW."endlifespanversion",NEW."quality",NEW."source",NEW."versionedobjectid",NEW."suid_khasrano",NEW."pk_levelid",NEW."n_areawritten",NEW."dimension",NEW."parcellabel",NEW."surfacerelation",NEW."n_lb_east",NEW."n_lb_west",NEW."n_lb_north",NEW."n_lb_south",NEW."n_fieldname",NEW."n_status",NEW."geom");

71

iii) Update rule on view

CREATE OR REPLACE RULE "_UPDATE" AS ON UPDATE TO "public"."pk_spatialunit_current" DO INSTEAD

UPDATE "public"."pk_spatialunit" SET "beginlifespanversion" = NEW."beginlifespanversion","endlifespanversion" = NEW."endlifespanversion","quality" = NEW."quality","source" = NEW."source","versionedobjectid" = NEW."versionedobjectid","suid_khasrano" = NEW."suid_khasrano","pk_levelid" = NEW."pk_levelid","n_areawritten" = NEW."n_areawritten","dimension" = NEW."dimension","parcellabel" = NEW."parcellabel","surfacerelation" = NEW."surfacerelation","n_lb_east" = NEW."n_lb_east","n_lb_west" = NEW."n_lb_west","n_lb_north" = NEW."n_lb_north","n_lb_south" = NEW."n_lb_south","n_fieldname" = NEW."n_fieldname","n_status" = NEW."n_status","geom" = NEW."geom" WHERE "suid_khasrano" = NEW."suid_khasrano";


72

3.3.5 Implementation Code (Example-Pk_BoundaryFace)

To Implement the Adapted Design

Objective 4:

74

4.1 Geo-referencing of Masawis

75


76


• Issue: ▫ Maps made in local scale▫ Old manual maps and new satellite image

• Possible methodologies:▫ Field survey ▫ Image to map geo-referencing

• Identification of 29 common points/ parcels through pattern matching and visual interpretation

• 1st order polynomial (Affine transformation) ▫ Selection of control points▫ Apply Affine transformation and examine RMS▫ Rectification

77

Ist Masawi

78

2nd Masawi

79

3rdMasawi

80

4th Masawi

81

Final Output

82

• Importing digitzed shape files into there respective tables in PostGIS usingto shptopgSQL tool:

▫ Mauza Parcels -> Surveying and Representation:: Pk_Boundary Face

▫ Parcel Nodes -> Surveying and Representation:: Pk_Point

▫ Parcel Edges -> Surveying and Representation:: Pk_BoundaryfaceString

▫ Water Source -> Pk_nSourceOfIrrigation and Pk_nSourceOfIrrigationWaterMill

▫ Survey Marks -> Pk_Point

▫ Mauza boundary -> Pk_SpatialUnitGroup

▫ Other Features(Roads, Urban area) - > Pk_nOtherGeneralFeatures

▫ Masawi and satellite imagery -> Pk_nmap and satelliteImagery

83

4.2 Importing Geometry into DB

4.3 Forming Topology

• PostGIS topological data structure was selected to store parcels

▫ Topological Integrity-Intersections are nodes and edges areshared rather than separate entities

▫ Reduction in storage size

• Code

84

85

Parcel Edge Count = 8428

Parcel Node Count = 9925

Total Face Count = 956

4.5)Non Spatial Type Cadastral Parcel Transactions

1)Regular Transactions: Ownership of parcelchanges with no geometry change

▫ Status: Not implemented

▫ Classes Involved: Party and Administrative classes of LADM.

2)Other Type Of Parcel Transactions: Changes in other attributesrelated to land e.g. Irrigation source, changes in type of soil, statementof customs etc.

▫ Status: Implemented

▫ Classes Involved: Pk_nLandAndSoilClassification,Pk_nSourceOfIrrigation, Pk_nSourceOfIrrigationwaterMill,Pk_nChangesInKindOfSoil

▫ Functions used: Regular functions of DBMS like insert, updateand delete

86

1) Splitting Parcel Transaction: Splitting of parcels in two or moreparts


▫ Classes Involved: Pk_SpatialUnit, Pk_RequiredRelationshipSpatialUnit,Pk_boundaryFace, Pk_SpatialSource, Pk_Level

▫ Functions used:

▫ ST_AddEdgeNewFaces: Add a new edge and, if in doing so it splits a face, delete theoriginal face and replace it with two new faces.

▫ ST_AddEdgeModFace: Add a new edge and, if in doing so it splits a face, modify theoriginal face and add a new face.

▫ Updates all existing joined edges and relationships accordingly.

▫ Parent parcel information can be stored in sourceParcel attribute of table Pk_spatialUnit

87

4.6) Spatial Type Cadastral Parcel Transactions

88


89

2) Merging Parcel Transaction: When two or more parcels adjacent parcels are owned by same person and merged to one.


▫ Classes Involved: Pk_SpatialUnit, Pk_RequiredRelationshipSpatialUnit,Pk_boundaryFace, Pk_SpatialSource, Pk_Level

▫ Functions used:

▫ ST_RemEdgeNewFace: Removes an edge and, if the removed edge separated two faces,delete the original faces and replace them with a new face.

▫ ST_RemEdgeModFace: Removes an edge and, if the removed edge separated two faces,delete one of the them and modify the other to take the space of both.

▫ Updates all existing joined edges and relationships accordingly.

▫ Parent parcel information can be stored in sourceParcel attribute of table Pk_spatialUnit

90

3)Adding Parcels: When parcelsare brought sporadically into thesystem. Most of them alreadyestablished in land registration DB


▫ Classes Involved: Pk_SpatialUnit,Pk_RequiredRelationshipSpatialUnit, Pk_boundaryFace,Pk_SpatialSource, Pk_Level

▫ Functions used:

▫ CreateTopoGeom : Creates a new topogeometry object from scratch

91


4)Updating Parcels: Manipulating either boundary or attribute,updating its quality.


▫ Classes Involved: Pk_boundaryFace, Pk_SpatialSource

▫ Functions used:

▫ ST_ChangeEdgeGeom – Changes the shape of an edge without affecting the topologystructure.

92


93


4.7) Prototype Demonstration

94

Loading layers from PostGIS database

4.7) Prototype Demonstration

95

Adding vector layer joins with attribute table

96

Edit widget and choose a fixed set of values that can be chosen

97

Edit widget and choose a fixed set of values that can be chosen

4.8 Conclusions

• The adaption of ISO standard in case of Pakistan is technicallypossible.

• Existing manual system can be mapped into various packages ofLADM by using the existing contents of the standard and also byaddition of new attributes and classes.

• PostGIS topological data structure can be used to store parcelrelated data with in a digital cadastral system. More over problemsrelated to geometry such as undershoots, overshoots, and slivers willnot exist and data will be clean and free from geometrical errors.

98

• To validate the history maintenance capabilities of adapted LADMmodel through class Pk_versionedObject, various rules, triggers andfunctions have been formulated which gets activated when anymodification is being performed on the underlying data. Thisdemonstration shows that adapted model has an effectivefunctionality to maintain and store historical data which is differentfrom data versioning concept of ArcGIS.

• The research also shows that open source applications can be usedin the design and development of digital cadastral system butfurther research is needed.

99

4.8 Conclusions

• This research can be expanded to adapt other non-spatial classessuch as person and Rights Restrictions and Responsibility classes ofLADM according to the existing cadastral system of Pakistan.

• Procedures to maintain and update the parcel polygons and otherattribute related information should be researched and designed.

• Creation of web enabled cadastral system providing variousinterfaces to the users .

• Testing of complete application schema (logical design proposed inresearch) should be performed according to the conformance testsin final ISO draft international standard (FDIS).

100

4.9 Recommendations

• Efficiency and effectiveness of open source tools in cadastral system development can further be explored.

• It is recommended to implement LADM in several real life situations by implementing a pilot project in two different types of villages .

• Development of urban cadastral component based on LADM.

101

4.9 Recommendations

102

103

Technology

Graduate Research Thesis Defense Presentation