MODERNIZATION OF LAND RECORDS1.6 Easy Disaster Management - Identification of properties for crop compensation, crop insurance, encumbrances etc. as relief measure after natural calamities

MODERNIZATION OF LAND RECORDS

INCLUDING DIGITIZATION OF CADASTRAL MAPS, INTEGRATION WITH

RECORDS OF RIGHTS AND MANAGEMENT OF OLD REVENUE DOCUMENTS

UNDER NLRMP IN HARYANA

HARYANA SPACE APPLICATIONS CENTRE (HARSAC)

DST, GOH

&

DIRECTORATE OF LAND RECORDS

(GOVT. OF HARYANA)

National Land Record Modernization Programme-Haryana

1 | P a g e

Authorship

This document has been prepared by Haryana Space Applications Center, Department of

Science & Technology, and Government of Haryana in close consultation with Department

of Land Records (DLR), National Informatics Centre (NIC)-Haryana, Government of Haryana.

© HARSAC, 2011

This document may be reproduced in any media with information to HARSAC & DLR. If

referred to or produced as a part of another publication, the source of the material must be

appropriately acknowledged. The content of this document is not to be used in any

misleading or objectionable.

This document is also available in pdf format at

http://www.harsac.org/.........

The revenue village directory with location codes based on Census 2001/2011 is available on

the website http://www.harsac.org/.........

Chief Scientist

Haryana Space Applications Centers (HARSAC)

Department of Science & Technology Government of Haryana

Hisar, Haryana-125004

http://www.harsac.org/

http://www.harsac.org/


2 | P a g e

Disclaimer

While all possible care has been taken during the preparation of this document, possibility

of any inadvertent error having crept in cannot role out. Any such discrepancy should be

communicated at [email protected] .

Suggestions, comments and feedback for inclusion in the future versions of this document

shall be highly appreciated. All such suggestion & feedback may direct to the following

address:

Chief Scientist

Haryana Space Applications Centers (HARSAC)

Department of Science & Technology Government of Haryana

Hisar, Haryana-125004

mailto:[email protected]


3 | P a g e

CONTENT

Serial No. Content Page no.

Glossary 7-8

1.0 Introduction 9-10

2.0 Scope of Work 10-11

3.0 Recommended Software 11

4.0 Digitization of Cadastral Maps and Integration of Textural & Spatial Data 11

4.1 Input Data 11

4.2 Process Methodology 11

4.2.1. Geospatial Database Generation 11-12

4.2.2 Database Construction Guidelines 12

4.2.3 Evaluation of Database 12-13

4.3 Collection of Mussavies Tehsil wise from District Revenue Office 13

4.4 Indexing of Mussavies 13-14

4.5 Scanning of Musavi 14

4.6 Mussavies and Sajra Prints 14

4.7 Quality Approval and Acceptance of the Scanned Images 14

4.8 Updation of the Mussavies 14-15

4.8.1 Geo-linking 15

4.9 Digitization of the Mussavies 15-17

4.9.1 Spatial Data Model Structure 17

4.9.2 Parcel Division by Parallel lines 17

4.9.3 Bisecting Radius Method 18

4.10 Dimension Base Digitization of Road Feature 18-20

4.11 Quality Assessment and Check 20-21

4.12 Quality Assurance for Digitization 21

4.12.1 Validation Process 21-22

4.13 Geo-Rectification of Vector Data 22

4.14 Layout Generation 23

4.15 Seamless Data Generation 23

4.16 Procedure to Incorporate Parcel Division (mutation) in Digital Mussavies 24

4.17 Responsibility: As per RFP/Implementation Guideline/SLA 24

5.0 Survey / Resurvey And Updation of the Survey & Settlement Records 24

5.1 Updation of Maps Due to Transactions Including DGPS/ETS Survey 24

5.1.1 Schedule 25-34

5.1.2 Responsibility 34

5.2 Satellite Data Preparation/Processing as per TOR Requirement and Geo-referencing of Digitized Village Using HRSI.

34-35

5.2.1 Satellite Triangulation 35

5.2.1.1 Specifications of Block Triangulation 35

5.2.1.2 Input Data 35

5.2.1.3 Analyze Satellite Triangulation Results 35

5.2.1.4 Report 35

5.2.1.5 Accuracy 35-36

5.2.1.6 Quality Control and Assurance 36


4 | P a g e

5.2.1.7 Satellite Triangulation Quality Assessment 36-37

5.2.1.8 Delivery Contents 37

5.2.1.9 Responsibility 37

5.3 Digital Elevation Model Generation 37

5.3.1 Process 37

5.3.2 Deliverables 37

5.4 Ortho-rectification 37

5.4.1 Input 37-38

5.4.2 Workflow for Digital Ortho-rectification of Satellite Image 38

5.4.3 Quality Assurance / Quality Control 38

5.4.4 Deliverables 38

5.5 Geo-referenced Administrative Boundaries of Revenue Village with Name of Village/Tehsil/District

38-39

5.5.1 Responsibilities 39

5.6 Establishment of Ground Control Points (GCPs) using dual frequency DGPS for Geo-referencing of satellite image.

39

5.6.1 Scope 39

5.6.2 Input data 39

5.6.3 Generalized Planning Considerations for GPS Surveys 40

5.6.4 GPS Survey 40-42

5.6.5 QA & QC for Error Detection 42

6.0 Network Design Specification 43

6.1 Setting up the Ground Control Network 43

6.2 Primary Control Points 43

6.3 Secondary Control Points 44

6.4 Tertiary Control Points 44-45

6.5 Auxiliary Control Point 45

6.6 ETS Survey 46

6.7 Data Collection 46

6.7.1 Downloading the Data 47

6.7.2 Processing 47

6.7.3 Troubleshooting Problematic Baseline 47-48

6.7.4 Network Baseline 48

6.7.5 Accuracy Standards for Network Baseline 48

6.7.6 Responsibility 48

7.0 Document Retrieval Software 49

7.1 Code of scan document 49-57

7.2 Application Development for Document Management System 57

7.3 Application Prototype 57-58

7.4 Standards for Database Organization 59-60

7.5 Security of the Digital Database 61-62

7.6 Storage and Security of the Digital data 62-64

8.0 Standard Operating Procedure for Ortho Rectification 64-66

8.1 Standard Operating Procedure for Ortho Rectification recommended by NRSC

66-67


5 | P a g e

9.0 Deliverables 67

9.1 Village Maps 67

9.2 List of Khasra No. Mismatch with ROR 67

9.3 Tehsil Map 67

9.4 District Map 67

9.5 Revenue Document Scanning 67

9.6 Survey 68

9.7 Deliverables in Soft Copy Formats 68

9.8 Deliverables in Hard Copy Formats 68

9.9 Features Deliverables 69-71

10.0 List of the integration of associated consultant 71


6 | P a g e

ANNEXURE

Annexure -1 Description of Measurement units 72-74

Annexure -2 Format for Final Authorized vendors representative 75

Annexure -3 Format of Identity card 75

Annexure -4 List of District level contacts 76

Annexure -5 HARSAC’s authorized representatives at district level 76

Annexure -6 Map collection Format 77

Annexure -7 Format for the submission of the Printed scanned Mussavies. 78

Annexure -8 Format of the Acceptance Certificate 78

Annexure -9 Format for Scanned Mussavies updation 79

Annexure -10 Spatial Data Model structure: 80-82

Annexure -11A

Cadastral Map vs. Rectified Worldview data 83

Annexure -11B

Area Validation of individual parcel from different land records 84

Annexure -11C

Burji Length Verification with adjacent village 84

Annexure -12 Format for the Verification of Vector Data 85

Annexure -13 Approval for Executing Mussavies Regeneration Activity 86

Annexure -14 ETS Survey Monitoring and Completion for Musavi Regeneration 87

Annexure -15 Tehsil level data verification 88

Annexure -16 District level data verification 88

Annexure -17 QC/QA format for DGPS data processing 89

Annexure -18 Check list before starting of DGPS reading 90

Annexure -19 Control point codification 91

Annexure -20 Standards for horizontal accuracy 92

Annexure -21 Submission of DGPS Report of Primary/Secondary/Tertiary Control Point 93-96

Annexure -22 Certificate of Acceptance of DGPS Report of Primary/Secondary/Tertiary Control Point

97

Annexure -23 Symbolization for line features 98

Annexure -24 Symbolization for polygon Features 99

Annexure-25 Point feature 100-101

Annexure-26 Format for primary information and MIS 102

Annexure-27 List of the associated personnel from different organization 103

Annexure-28 FRS for Haryana Revenue Document Management & Retrieval System 104-138


7 | P a g e

GLOSSARY

AMC-Annual Maintenance Contract

AO-Absolute Orientation

BIOS-Basic Input/output System

CLR-Computerization of land Record

CSV-Comma Separated Value

DEM-Digital Elevation Model

DGPS-Differential Global Positioning System

DLR-H-Director Of Land Record, Haryana

DMRS- Document Management Retrieval System

DMS-Document Management System

DOP-Dilution of Precision

DRO-District Revenue Officer

DTM-Digital Terrain Model

ERDAS-Earth Resources Data Analysis System

ETS-Electronic Total System

FCC-False Color Composition

FDD-Floppy Disk Drive

GCP-Geo-Referenced Control Points

GDOP-Geometric Dilution Of Precision

GIS-Geographical Information System

GPS-Ground Positioning System

GSD- Global Spatial Data

GSM- Gram Square meter

HALRIS- Haryana Land Records Information System

HARIS- Haryana Registration Information System

HARSAC-Haryana Space Applications Center

HDOP-Horizontal Dilution Of Precision

HRSI- High Resolution Satellite Imagery

ITRF-International Terrestrial Reference Frame

LAN-Local Area Network

MSL- Mean Sea Level

NCC- Natural Color Composition

NIC-National Information Center

NLRMP-National Land Record Modernization Programme

NNRMS-National Natural Resources Management System

NRSC- National Remote Sensing Center

PDOP-Position Dilution Of Precision

QA-Quality Assurance

QC-Quality Check

RCC- Reinforced Cement Concrete

RFP- Request for Proposal

RMS- Root Mean Square

RMSE- Root Mean Square Error

RoR- Records of Rights


8 | P a g e

RPC-Rational polynomial coefficient

RRD-Reduced Resolution Data

S/W-Software

SDD-System Design Document

SLA-Service Level Agreement

SNR-Signal-To-Noise Ratio

SOI-Survey Of India

SQL-Structured Query Language

SRS-System Requirement Specification

ToR-Term Of Reference

UHF-Ultra-high frequency

UPS-Uninterrupted Power Supply

USB-Universal Serial Bus

UTM-Universal transverse Mercator VDOP-Vertical Dilution Of Precision

WGS-World Geodetic System/Survey


9 | P a g e

1.0 Introduction

Haryana has an integrated Department for the Property Registration and Land Records

Administration along with Disaster Management. Immense efforts have been made by Government

of Haryana in the computerization of the Land Record and Mutation procedure in Last two decades

under the Computerization Land Record(CLR)Programme of NIC Haryana with an ultimate aim to

develop transparent and authenticated system (as confidence building measure) among its citizens

and to reduce the ownership disputes in future to make available the computerized copies of

revenue records to the people of Haryana at tehsil and lower level in place of conventional method

of obtaining manual Nakal from the Patwari/Kanungo.

The Government of Haryana has appointed HARSAC as nodal agency for the generation of

Geospatial Data Base using Remote Sensing and GIS State of Art technology for the Project-

Modernization of land records (which includes digitization of cadastral maps, integration with

Records of Rights (RoR) and Management of Old Revenue Documents) under NLRMP in Haryana

with the following objectives:

1.1 To preserve the data available in the documents.

1.2 Electronic storage and facilitate its easy access to the users.

1.3 Easy retrieval to the public and user Department by obtaining the drawing of land along with

dimensions, area (as on ground and also as per (RoR), other attributes and Neighborhood

details.

1.4 Facilitate in prompt updating of digital land record so that modern land record system will

add value to a common man. Whenever there is a future updation /mutation the survey can

promptly upload the data from the field mobile device to enter the field data in to a

computer in office to update the land parcel simply.

1.5 Better resource planning and better monitoring of Govt. lands such as hamlet lands and easy

identification of encroachments on public/private properties using Geospatial data base and

Geo referenced satellite Image.

1.6 Easy Disaster Management - Identification of properties for crop compensation, crop

insurance, encumbrances etc. as relief measure after natural calamities

The project will facilitate easy updation of ground conditions / status after mutation and title change

in the land Record using Geo-referenced village/tehsil/district mosaic of cadastral maps comprising

of spatial information, dimensions as per RoR and as on ground holding reality.

Department of Revenue and Disaster Management (DLR-H) has implemented / standardized

the workflow based on dynamically integrated Property Registration Information System (HARIS-

Haryana Registration Information System) and Land Records Management System (HALRIS - Haryana

Land Records Information System) SRS of both these system are part of this document and it would

be provided by DLR/NIC. The Geospatial data base generated under this project will be integrated

with the RoR data in HALRIS software using Bhu-Naksha Software (developed by NIC-Haryana, The

SRS of which to be provided by DLR/NIC-Haryana) to develop the Integrated Land Management

Information System throughout Haryana State. NIC shall define required output format of spatial

data for integration with RoR data using their HARLIS software. DLR/NIC has to return integrated


10 | P a g e

Geo Spatial to HARSAC for geo-referencing. DLR/NIC has to specify format in which they will return

geo-spatial data to HARSAC for further rectification

The state of Haryana has the graphic land record depicted in Mussavies. Each musavi comprises of 16

murrba and each murrba comprises of 25 killas, where killa is represented by the positive integer

from 01 (one) to 25 (twenty five). And Killa is the smallest land parcel which can be further sub

divided due to title change and mutation. In such case, killa will be represented by BATA viz 23/1,

23/2, 23/3….. Etc. A total of 25killa constitute 1(one) murrba, which are also represented by positive

integer which will continue throughout the musavi. The total number of murabba in musavi will

depend on the area and shape of the hadbast. These killa and murrba are rectangular in shape of

fixed dimensions and area.

Standard Dimensions

The DLR-H, Government of Haryana has maps (musavi) representing the distribution of land parcels

on ground. These are called Mussavies. Each musavi comprises of 16 murrba naming 01 (One) to 16

(Sixteen) as shown in table 1.

Sr. No. Land Units

East to West Dimension

North to South Dimension

Units (01 karam = 66 inches (5.5 feet)

1 Killa 40 36 Karam

2 Murrba 200 180 Karam

3 Musavi 800 720 Karam

Detail see (Annuxere-1)

Table 1: Standard dimension of DLR, Haryana.

2.0 Scope of work

Scope of work for this project in order to attain the above said objectives are described below.

1. Cataloging, indexing and scanning of old land records (Mussavies, Field book, Misal Haqiyat,

Registered deed etc.).

2. Digitization of the Mussavies.

3. Updation of digitized Mussavies by incorporating all changes till date. Generation of missing

remaining Mussavies and updation during AMC.

4. Monumentation of the control points.

5. Integration of spatial data base with RoR data available in HARLIS using Bhu-Naksha s/w.

6. DGPS survey for establishment of Primary, Secondary and Tertiary control points.

7. Ortho-rectification of high resolution satellite images of World View-1 / World View-2.

8. Generation of missing data either by interpreting it from field book or any other revenue

records.

9. Survey/Resurvey through ETS for the unconsolidated areas, areas where data is missing and

areas where area discrepancy is observed and for areas defined by District Administration.

10. Validation of interpreted data through field survey.

11. Development of Document Management System.


11 | P a g e

12. The generation of seamless digital vector data & production of hard copy of village/tehsil /

District also.

13. Capacity building by imparting training for digital (spatial and non-spatial) data updation

during annual maintenance period (2 years).

14. Geo-referencing and mosaicking of village Mussavies.

15. Develop seamless geo-database for state.

3.0 Recommended Software

The following software’s are recommended to meet the quality standards of the project.

Geospatial data base generation software: ArcGIS and equivalent

ERDAS IMAGINE. and equivalent

Leica Photogrammetric Suite. and equivalent

(Note- The output formats will be produced in *.img, *.shp, *.mxd. &*.gdb i.e. file geo-

database for vector data)

Bhu-Naksha (Certification Required).

4.0 Digitization of Cadastral Maps and integration of Textual & Spatial Data

4.1 Input Data

The input data required for the successful implementation of project are as follows:

1. Original Musavi.

2. Records of Right (RoR data).

3. All old Documents.

4. Digital vector data and scanned Mussavies of different district-areas already completed by

HARSAC.

4.2 Process Methodology

The Detail activity involved for the geospatial data generation as per the scope of work and

specification mentioned in the ToR are as follows:

4.2.1 Geospatial Database Generation

The GIS experts will finalize the geospatial data modal on the following guidelines. The activity

involve are as follows:

i. Tehsil wise, collection of Mussavies& old revenue document by deputing specialized

revenue officer at each tehsil level.

ii. Indexing and cataloging of documents/maps followed by its safe storage and damp free

environment.

iii. Identification of missing Mussavies followed by generation of missing Mussavies using

Field book, Jamabandi , Misal Haqiyat, and Sajra map etc.

iv. Survey/Resurvey through ETS for the unconsolidated areas, areas where data is missing

and areas where area discrepancy is observed and for areas defined by District

Administration.

v. Scanning of the Mussavies & one print on 75 micron polyester matt film which will be

submitted to DLR as final delivery.

vi. Village wise numbering of the Mussavies.


12 | P a g e

vii. Grid generation (Murabba, Killa, and Mussavies and its attribution (Numbers)).

viii. Mussavies registration on Planimetric murrba grid.

ix. Digitization dimension based as per data modal.

x. Processing of scanned &digitized Mussavies followed by printing on 100 gsm paper for

updation.

xi. Updation from respective Patwari/Kanungo.

xii. Updated Mussavies incorporated by vendor for final updation.

xiii. In house quality assessment and layout generation for digital data validation from client.

xiv. Details study of the RoR data structure for integration, unique code incorporation in

spatial data base.

xv. Integration of spatial data base with RoR, by converting spatial data files into *.shp/*gdb

file format as per define requirements of Bhu-Naksha software.

xvi. Listing of the parcel numbers without RoR data and listing of the RoR data not attached

with any parcel will be identified its reason and resolution analysis and intimation to the

HARSAC.

xvii. Seamless data generation tehsil / district wise.

xviii. Final quality assessment in house of seamless data.

4.2.2 Database Construction Guidelines

The database construction guidelines can be divided into four major categories under

present scope of digitization of cadastral maps, overlay on the satellite data and integration

with textual data:

1. Digitization (analog to digital conversion) of cadastral village maps.

2. Codification of the scanned document for the indexing and retrieval through customized

software.

3. Satellite image database preparation.

4. Geo-referencing of digitized GIS data with HRSI.

4.2.3 Evaluation of Database

The following guidelines/parameters will be followed for the evaluation of the database:

1. Assuring that appropriate digitization methods with proper template, accuracy, precision

and quality check procedures are followed.

2. Verification of the co-ordinate system, projection and datum.

3. Checks for digitization errors like slivers, dangles, and topology rules.

4. Attribute verification providing the correctness of feature coding by listing it out and

comparing with the manuscript maps. Random checking of parcels for shape and form

listing of polygons with null and duplicate attributes.

5. Verification of edge-matched mosaic with adjacent sheets and villages by displaying them

side by side.

6. Comparison of the total area of the village by aggregating the parcels, etc. vis-à-vis the area

available with the Land Records Department in the RoRs.

7. Verification of geo-referenced control points (GCPs) and root mean square (RMS) error for

the transformation model.

8. Checks for mosaicing of maps and overlay on the satellite data.


13 | P a g e

9. Attachment of appropriate metadata at all stages of the database preparation.

10. Checking of the codification/ naming of scanned document.

4.3 Collection of Mussavies Tehsil wise from District Revenue Office

The Activity involved is as follows:

I. Authorized representative of vendor will collect tehsil wise maps. (Annexure-2).

II. Submission of the list of the authorized representative of vendor to DLR / HARSAC.

III. Authorization of the vendor representative by DLR/HARSAC.

IV. Issuing of identity cards to the authorized representatives of vendors (Annexure-3).

V. Finalization of the list of the authorized representative by DLR/HARSAC at district level,

tehsil wise with contact details (Annexure- 4&5).

VI. Scheduling of the maps collection activity from each district & tehsil wise.

a) The Mussavies of tehsil shall be provided in single lot (should be organized

village wise).

b) The date of the collection of Mussavies tehsil wise shall be intimated to the

concern officers (as the contact details provided in Annexxure-4&5) one week

prior to the date of collection.

c) Any change in the above schedule shall be intimated to the concern stake

holders two days in advance.

d) Maps collection activity shall be completed in the first months from the date of

the finalization of SDD.

VII. Process for maps collection: The collection of the Mussavies from each district.

Tehsil wise (to be organized village-wise) Mussavies collection shall be done by the

authorized representative of the vendor shall be tabulated in the format (Annexure-

6).

(a) List of Mussavies in triplet will be prepared village-wise comprising of the details

/ conditions of the collected map.

(b) Each village list shall be countersigned by the representative of vendor and DRO

in original. One copy each shall be retained by DRO, Vendor and HARSAC.

4.4 Indexing of Mussavies

a) The Annexxure-6 sheet shall be scanned and kept in *.tiff format.

b) Details of Mussavies collected from each district Tehsil wise shall be tabulated in *.xls by the

documentation officer of vendor to assist the project management team.

The format for the indexing of such information is shown in table 2.

Sr. No.

District Tehsil Village Sheet No.

Quantity Remaining sheet (if Any)

Hyperlinked Scanned Annexure-6

Table 2: Indexing format


14 | P a g e

The nomenclature of the scanned Mussavies will be done using the village, district and tehsil code as provided / approved by HARSAC/DLR, Haryana. The numeric code would be assigned to each Mussavies. Village with more than one scanned sheet would be having the code with sheet number. The final code will be as per the DMS document section 7.0.

4.5 Scanning of Mussavies

The scanning of the Mussavies has to be done considering the following parameters:

a) Maps should be scanned at 200 dpi color mode. If Mussavies are damaged/destroyed or boundaries are not clear then scanning should be done at 400 dpi on 24 bit color.

b) Images should be stored in tiff /geo-tiff and pdf format. c) The image orientation should be upright. d) Registration / Rectification of the Mussavies with the grid. e) The image should be cleaned and de-speckled to remove noise. f) Legibility of features should be good. g) Measured length and width within the bounding box of map should be +/‐ 0.1% of the

original maps. h) The image should not be skewed or wrapped. i) Scanned image will be approved by officer/ official designated.

4.6 Mussavies and Sajra Prints

a) Original scanned Mussavies prints on 75 micron polyester matt film delivered to DLR as final

delivery (Annexure-7).

b) Original digitized Mussavies prints in color on 100 gsm paper for updation.

c) Sajra map prints on 100 gsm paper for final acceptance by DRO.

d) Final digitized Mussavies prints on 75 micron polyester matt film (3 copies) as final delivery.

4.7 Quality Approval and Acceptance of the Scanned Images

After necessary correction like image orientation and skewing, cropping, cleaning etc., vendor will generate check plots for each Mussavies in monochrome/color as per original map on 75 micron transparency and get this checked / verified from the authorized official deputed by the HARSAC. The print should be on 1:1 plot scale. Format for the acceptance certificate (Annexure-8). Checking process will include the following steps:

a) Visual inspection of scanned maps for: i. Validation of errors during the scanning process.

ii. Ensuring correct nomenclature and file format. b. Ensure that each raster image should open in computer environment. c. Rescan of the original hardcopy musavi in case of any failure in quality check. d. Issuing an acceptance certificate to vendor to proceed with digitization work.

4.8 Updation of the Musavi

The digitized Mussavies will be printed on the 100 gsm paper on 1:1 plot scale for updation. The printed digitized Mussavies will be delivered to the DLR-H authorized representative (as shown in

format (Annexure-9)). The digitized musavi will be updated as per the record and latest status of mutation by the DLR-H and handed over to vendor for final updation.

Note:


15 | P a g e

1. Once the digitized map (musavi) is updated by the Patwari/Kanungo, the map will be considered

as final. After that, for any new corrections, the cost of print/plot will be borne by Patwari/Kanungo

only.

2. Further, any new updates on Sajra maps by Patwari/Kanungo shall be updated in digital data only

and no new printout shall be provided by vendor. In this case no further updation shall be

considered under this project and should be taken up during the AMC.

4.8.1 Geo-linking

RoR data consisting of Hadbast, NVCode, Murrba, Khasra no. and owner name shall be

provided by DLR/NIC through HARSAC. Vendor shall match the updated (by

Patwari/Kanungo) digital data with the RoR data. Any mismatch shall be listed out by vendor

and submitted to DLR. DLR will provide necessary resolution within two weeks.

4.9 Digitization of the Mussavies

Scanning, digitization of Mussavies and updation of digital Mussavies has to be done at space

provided by the Haryana Space Applications Centre at Hisar. Vendors should give an undertaking

that integrity, secrecy and security of data shall be maintained. All the necessary hardware/software,

LAN connectivity, UPS etc. for scanning the revenue documents at Land Records and Settlements

Offices (District/Tehsil) if required would be arranged by the vendor.

Digitization will be carried out by keeping the rectified / grid corrected cadastral image at the

background and using finalized layering scheme, symbology and color coding along with the quality

control norms.

District- wise grid generation:

The index map of each village will be carefully reviewed and killa grid or 40 karam x 36 karam

will be generated using ArcGIS software considering 01 karam = 66 inches (5.5 feet) (karam size

may differ according to land record). The line feature forming killa grid will be converted to

polygon feature and the label (1-25) of each killa will be placed at centroid. The sequence of the

labeling will be as shown in the figure 1 below.

Figure 1: Sequence of Labeling


16 | P a g e

Each murrba comprises of 25 killa (5x5). So each murrba will be of 200 karam x 180 karam. The

murrba grid will be generated using same origin as that of killa grid in Arc GIS software. The line

feature forming murrba grid will be converted to polygon feature and the label of each murrba will

be placed at its centroid. Each musavi will comprise of the 16 murrba as shown in figure 2. The index

map will be used as the referenced for the registration of the scanned Mussavies. The sequence of

the Mussavies of each village will be as shown in the Index map.

The standard template will be created by the vendors in consultation with HARSAC. In the template

the layer name, line type and color for each feature like road, railway, habitation, river, etc. will be

standardized. This process helps to maintain uniformity in all the maps that will be digitized,

especially in those cases where a number of village maps are needed to be mosaicked at village

level.

Figure 2: Musavi Template

Digitization has to be done in the GIS environment using defined layers (Para 9.9) and

symbology as indicated at Annexure 23, 24, 25.

The Digitization will be done at a comfortable zoom level to ensure that the vertices to avoid

undershoot and overshoot.

Polygons, Points, and Lines have to be captured in different layers.

The data should be topologically correct for each of the layers.


17 | P a g e

The features such as village tri-junctions, bi-junctions etc. have to be digitized as point

features.

The features such as rivers and roads have to be digitized as linear features.

Logical connectivity of the features have to be followed i.e. a river will not join a road.

The digitized line will be followed as per the dimension specified for each segment of killa

boundary on the map.

There should not be any overshoots, undershoots and duplicate features.

Appropriate symbols have to be used as per the source.

The polygon features have to be closed without any dangles or slivers.

The connectivity of the rivers/roads has to be maintained except cases where a river feature

is crossing a road feature.

Feature-specific codes as defined in Para9.9 will be used for attribution. Each parcel polygon

will have a unique Khasra number as specified on the scanned Mussavies

4.9.1 Spatial Data Model Structure

The tentative spatial data model for the generation of the geospatial database will be used as shown

in figure 3.

Figure 3: Spatial Data Model

The feature class will be defined as per the above data modal in ARC GIS Software. The rectified

scanned map will be kept in the back drop for the digitization of the features. The digitization of the

features will be done as per the dimension specified on the map. The bifurcated / Bata parcels will

be generated by splitting the Killa line boundary as per the distance / dimension specified in the

map. The line or the boundary of the Bata parcel will be generated by joining the corner of the

split/segment of killa boundary.

4.9.2 Parcel Division by Parallel lines

In Haryana the parcels may be updated or bifurcated by parallel division with respect to any side of

the older killa boundary using the dimension of AE or BE or FD or CF whichever is specified on the

musavi(Figure 4).

E A B

C F D


18 | P a g e

Figure 4: Parallel Division in Musavi

4.9.3 Bisecting Radius Method

In case the kink in the village boundary or the canal occurs at any point with in any killa then to

generate such point the said method will be used. The arc of the radius equal to the segment of the

road/village boundary/canal specified on the map will be drawn from the point of the intersection of

the killa boundary and linear feature. The point of intersection of the arc will represent the kinks in

the linear feature as shown in figure 5.

Figure 5: Bisecting Radius Method

4.10 Dimension Base Digitization of Different Feature

Each village will comprise of the habitation area. The parcels in the habitation will be very small and

hence have sub maps containing detailed information about the dimension and arrangement of

parcels (Figure 6). These sub maps will be referred during the digitization of such area. Figure7

shows the dimensioned based digitization of a parcel.

Figurte 6:Sub Map of Habitation parcels


19 | P a g e

Figure 7: Dimension Based Digitization of Parcels

Dimension base Digitization of Parcels

Figure 8: Dimension based Digitization of Village Boundary


20 | P a g e

Figure 9: Vector Layers

The required attribute information such as parcel/Khasra numbers available on the maps have to be

assigned to the vector polygons.

The each village may comprise of more than one musavi. Care should be taken during the

map rectification taking into consideration the sequence/arrangements of the Mussavies shown on

the Index map. This will be helpful in the seamless digital data generation of entire village. The single

file *.shp will be generated for each village. The nomenclature of the file (digital vector data) will be

done considering numeric code. The final code will comprise of the following code

1. District code: DD 2. Tehsil code: TTT 3 Village code: VVVVV (NV code)

The finalized digital musavi file name will be DDTTTVVVVV *.shp./*.gdb

The digitized file for each village has to be created under this task. If village information is available

in more than one map sheet, all the sheets have to be edge matched mosaicked into one village

(Edge matching, removal of redundant /duplicate text/labels, scale adjustments etc.,).

4.11 Quality Assessment and Check (Accuracy, Quality, Inspection and Completeness)

The project will have well defined and set procedures for quality assurance of the data base as

indicated at Annexure 11, 12&13. The quality check (QC) procedures are both qualitative and

quantitative. All coverage’s or hard copy maps submitted by the vendors will have to go through the

quality check procedure by HARSAC before acceptance. The following aspects regarding quality

assurance have to be adhered by vendors:

i) The quality assurance of the data will be carried out by HARSAC

ii) This will include checks for topological correctness, unique feature coding, and

completeness of data, naming conventions, and accuracy and RMS errors.

iii) The quality assurance form duly filled in as per the specified format has to be submitted

along with the soft copy data.


21 | P a g e

iv) Data not complying with the standards and accuracy specifications will be sent to vendor

for correction and will have to be re-submitted after necessary corrections.

v) If the data complies with the quality assurance standards and error limits are in the

prescribed range the data will be accepted.

vi) The quality assurance should comply with the following aspects

(1) Positional accuracy

(2) Attribute accuracy (attribute updated by DLR shall be considered as final)

(3) Logical consistency

(4) Completeness

(5) Mosaicing fit of the data.

vii) Quality assurance of database will be done within a specified time set by HARSAC.

On sample basis, the geo-referenced files of individual villages and the mosaic will be

digitally quality checked by HARSAC

4.12 Quality Assurance for Digitization

4.12.1 Validation process

The criteria and acceptance levels for various parameters are given below:

a) File naming 100%

b) Directory structure 100%

c) Data readability 100%

d) Data structure 100%

e) Data format 100%

f) Topology 100%

g) Attribute correctness 99-100%

h) Attribute completeness 100%

i) Data mosaicing 98-100%

At each step of the process, adopted for computerization and geo-referencing of the village map,

quality check will be applied to ensure error free database generation. However, the following major

quality checks are designed to ensure the project objectives:

• Quality check on merged product generation using satellite data (QC 0)

• Quality check for Inventory and coding of the maps (QC 1)

• Quality check on first hardcopy output (QC 2)

• Quality check on softcopy of village maps (QC 3)

• Quality check on final hardcopy output (QC 4)

• Quality check on geo-referenced village maps (QC 5) (Annexure-11)

• Quality check on mosaic of geo-referenced village maps (QC 6)

• Quality check on final deliverables (QC 7)

The following criteria for testing digital vector data for completion and accuracy may include, but not

limit the number:

1. Physical verification of test plot on tracing paper on random sample basis.

2. Random checking of features, during which, not more than 10% of points tested should

be +/‐ 0.1% of the original maps.

3. Verification of topological correctness by actually constructing the topology.


22 | P a g e

4. Verification of job requirements reflected in design document.

If any batch of job/ services performed & software copies/ CDs/ Hardware copies carrying digital

data do not match with approved specifications or approved samples and found inferior in quality,

the entire lot will be rejected and no payment will be made for such a supply. Format for the

verification of vector data is given in (Annexure-12).

4.13 Geo-Rectification of Vector Data:

Figure 10: Process Flow for Geo-Spatial data Generation

Geo-rectification / Transformation of vector data as per the ortho - rectified image is targeted in

process step 3 of above Figure 10.


23 | P a g e

4.14 Layout Generation

Sample template as commonly prepared by HARSAC and concerned Vendors is depicted in Figure 11

below those are designed as per the original Mussavies of Department of Revenue& Disaster

Management Haryana.

Figure 11: Sample Template

4.15 Seamless Data Generation

To generate the seamless data adjoining villages shall be overlaid over the ortho-rectified satellite

images in the editable environment in ArcGIS. A suitable snapping environment shall be created to

enable edge match. The edges of the village boundaries shall be verified if double lines are present

and correction of the same to be made. The mosaicing of data should be in file geo-database.


24 | P a g e

4.16 Procedure to Incorporate Parcel Division (mutation) in Digital Musavi (Done by DLR/NIC)

The non-rectified digital village mosaic database shall be used for the updation of parcel divisions.

Details of the division with dimensions shall be provided through ROR data using Bhu-Naksha,

dimension based editing parcel division shall be carried out and an A4 size printout shall be

generated for verification and approval. After approval the files should be saved in the record.

To incorporate the modified parcel in the tehsil/district and state level mosaic database, the

saved link file of the concerned village shall be used to migrate the modified parcel on the

mosaicked location after deleting the original parcel from the mosaicked location using Bhu-Naksha

or ArcGIS software.

4.17 Responsibility: As per RFP/Implementation Guideline/SLA

5.0 Survey/Resurvey and Updation of the Survey & Settlement Records (Including Ground Control

Network and Ground Trothing) using the modern technology

Survey need in project scope could be categorized into three major areas:

a) Dual frequency DGPS survey for establishment of new primary control bench marks and

secondary control points.

b) Dual frequency DGPS survey for tertiary and auxiliary control points.

c) ETS survey shall be carried out in case of unconsolidated villages /as per DLR/DC

requirement.

d) For ETS survey the reference shall be taken from nearest primary/secondary control point,

established using dual frequency DGPS survey.

5.1 Updation of Maps due to Transactions including DGPS/ETS Survey (for missing Mussavies /

data not available)

In parallel to the updation process of digitization of cadastral maps (Mussavies) if,

The physical condition of document is poor/damaged. (not feasible to scan or read),

Mussavies is missing in records,

One or more of the available Mussavies in records is not as per the updated data of last

consolidation year as of the remaining Mussavies of same village.

In any of above said circumstances a new Mussavies is to be recreated/ regenerated as per the ROR

data, Field book, Jamabandi and Sajra map data. NIC ROR data integrated with best suitable survey

technique (ETS/DGPS).

The regeneration of new Mussavies should be done only after proper approval for regeneration

work by DLR. (In case of missing Mussavies, vendor shall submit plot having dummy musavi with grid

to DLR. The same shall be updated by Patwari/Kanungo as per their record.)The approval should be

taken on a duly signed copy of Annexure-13 by concern DLR-H officer/Patwari/Kanungo of

respective village.


25 | P a g e

5.1.1 Schedule

The activity schedule for “Modernization of Land Records, Haryana” as shown in figure 12.


26 | P a g e


27 | P a g e


28 | P a g e


29 | P a g e


30 | P a g e


31 | P a g e


32 | P a g e


33 | P a g e


34 | P a g e

Figure 12: Activity Schedule

5.1.2 Responsibility

a) The list of missing maps (as per the village index map) shall be prepared and jointly signed by

client and vendor during the handling over procedure.

b) Vendor shall communicate the probable dates for ETS survey team mobilization to

authorized signatory authority at least 3 days prior of schedule mobilization of team.

c) DLR-H has to fix the schedule for the map updation activity at each village level in consent

with vendor team mobilization schedule within +/- 1 day of communicated dates(as in point

b).

d) The client shall ensure the availability of authorized signatory at field (at each village level)

during survey for decision making in identification of correct plots/ Killa of Mussavies under

investigation and also to verify the survey activity (Annexure-14).

e) NIC shall provide the latest ROR data to the vendor team related to said Mussavies.

5.2 Satellite Data Preparation/Processing as per TOR Requirement and Geo-referencing of

Digitized Village using HRSI.

The Stereo satellite image processing involves followings process

Satellite Triangulation


35 | P a g e

Digital Elevation Model generation

Ortho-rectification

5.2.1 Satellite Triangulation

5.2.1.1 Specifications of Block Triangulation

Block triangulation will be carried out by refinement of image geometry model (RPC) supplied with the imagery, with the help of GPS control points.

Minimum number of control points provided for a stereo-pair of imagery will be nine. GCPs falling in overlap zones (but not critically) will be accepted. The GCPs will be well distributed in a matrix of 3X3.

Absolute Orientation: RMSE on GCPs from Block Adjustment < GSD of satellite imagery.

Relative Block Accuracy: 0.5 X input pixel size.

Minimum 100 tie points will be generated automatically to ensure internal consistency.

Size of blocks will be made larger if overlap is available between 2 or more pairs of stereo-imagery (district level).

5.2.1.2 Input Data

The following input material/data will be received from DLR-H / HARSAC

Very high resolution stereo satellite imagery digital data

Description and co-ordinates of Primary Control point, Tertiary control Points and Auxiliary control points for connection of horizontal control points, provided for Block Triangulation.

Description and heights of benchmarks for connection of vertical control points provided for block triangulation.

Projection parameters

Points to be used as check points DEM report. 5.2.1.3 Analyze Satellite Triangulation Results

The following are the analysis to be carried out for the satellite triangulation results

Review reports to check

RMS, check point,

Control point The rational functions are generated for the modal after model adjustment is run. These

rational functions provide a real-time mathematical model that generates co efficient for

multiple images. The generation of rational functions coefficient prepares satellite imagery

for stereo feature collection and automatic DTM collection.

5.2.1.4 Report

Generate final report for satellite triangulation containing absolute orientation (AO) results.

The residuals of satellite triangulation should be at least 3 times better than the specified

accuracy. If this is not achieved repeat satellite triangulation iteration till accuracy is

achieved

The model is downloaded in the digital photogrammetric work station and an absolutely

oriented model will be obtained.

5.2.1.5 Accuracy

The satellite triangulation accuracy measures will be:


36 | P a g e

Relative Block Accuracy: 0.5 x input pixel size

5.2.1.6 Quality Control and Assurance

Quality process ensures the following:

The following input is desired for the high quality vector data

100 % screen/plot QC against existing data sources.

100 % Production Batch Assembly and Final QC.

100 % QC for verifying the validity of data which includes: Completeness of data No feature is without a unique identifier. Each feature is represented as per Project Data structure. No feature or object is duplicated. Ensuring data integrity by validating topology.

QA ensure final quality through data sampling technique.

The following input is desired for the high quality satellite triangulation.

Satellite imagery

Sensor data, Image support Data, metadata etc.

Ground Control Point Coordinates

Quality of the satellite triangulation will depend upon the following parameters:-

The quality of original satellite image

Block adjustment procedures and algorithms.

Analysis of adjustment results and the application of weights to photogrammetric control points.

The quality and density of ground control

Configuration of ground control

The quality of the point marking, transfer

Sensor data, Image support Data, metadata etc.

Adjustment for earth curvature, and map projection.

QA and QCs shall be performed at following levels

Automatic check by using software

Manual check

5.2.1.7 Satellite Triangulation Quality Assessment The following points will be considered as part of the: Horizontal & Vertical Control Points and Block Triangulation Quality Assessment Plan

Control points will be visible and measured in more than two photos.

Vertical control points would exist and be measured in strips overlaps.

Vertical Control points must comprise a chain across the flight direction.

Minimum number of control points required to be provided for a stereo-pair of imagery shall be 9


37 | P a g e

Horizontal and Vertical control points must exist, be perfectly visible and measured between and across adjacent Satellite Triangulation blocks.

Absolute Orientation: RMSE on GCPs from Block Adjustment < GSD of satellite Imagery.

Relative Block Accuracy : 0.5x input pixel size

Minimum 100 tie points shall be generated automatically to ensure internal consistency

The Primary, Tertiary and Auxiliary control points DGPS coordinate shall be used for the Horizontal and Vertical control. The Primary Control points can be easily identified over the satellite image while the Auxiliary and Tertiary points shall be selected such that they can easily be identified over the image. The Tertiary and Auxiliary control DGPS coordinate shall be in connection with the Primary and Secondary Control Network.

5.2.1.8 Delivery Contents

List of all adjusted coordinates for all ground control, pass points and tie points.

List of differences at ground scale between surveyed and adjusted coordinate values for ~ control points.

List of differences at ground scale between measured and adjusted tie photogrammetric points.

GCP’s measurement, adjusted, rejected (if any), highlights of adjustments to standard weights, methodology of measurements, shall be prepared.

Block Triangulation Report

5.2.1.9 Responsibility HARSAC has to review the Block triangulation report as per required accuracy

5.3 Digital Elevation Model Generation 5.3.1 Process

Identify Break lines viz. Toe and top edge of embankments and cuttings of roads, railway,

Canals, Slopes of valleys, foot of hills, mounds, Toe and top of tank bund, along limit of

water bodies, features with sudden change of slope, etc.

Capturing of Mass points at regular grid interval.

Capturing of Mass points in vegetation area, built-up area at ground level.

Spot elevations shall be captured, summits, Local low points, Saddle, Lowest points of quarry

pits, Lowest points of excavations, Along valley beds, Standing water bodies, Street

intersections, At the intersection of the centerline of roads, Center of every bridge.

Demarcation of dense vegetation, lakes, Pond etc.

In the automated mode of generation of mass points, the thorough check against 3D model

to be performed. Editing including adding and deleting of mass points and provision of break-lines

shall be carried out as required for correction due to vegetation, built-up area. Mass points from

water-body areas will be deleted.

5.3.2 Deliverables

3-D Shape file containing break lines and mass points

Quality Control Records 5.4 Ortho-rectification

5.4.1 Input: The following inputs are required for the generation of the Ortho-rectified image

Digital Satellite Images


38 | P a g e

Digital Elevation Model data

Foot Print Index

Adjusted Satellite triangulation parameters

RPC File

Description and co-ordinates of Primary Control point, Tertiary control Points and Auxiliary control points for connection of vertical control points

5.4.2 Workflow for Digital Ortho-rectification of Satellite Image:

Individual scene Ortho-rectification using the triangulated satellite imageries and DTM as per the defined GSD of sensor.

Verify the geometric accuracy of the Ortho using the available control points.

Seam line/cutline generation. Edit the seam lines ensuring that seem line does not cross important cultural features.

Selection the seam line along roads, rivers, streams.

Perform Mosaicing and automatic global tone balancing.

Review of tone balance in the mosaic.

5.4.3 Quality Assurance /Quality Control

Check for image completeness

Check for any bridge/building distortion & deformation

Critically examine features such as buildings for Orthogonality

Examine critically the features along the seam line; carry out tone balancing, where necessary.

Confirm the correct pixel size of Ortho-image

Measure accuracy of ortho-image by using check points and control points.

Check header information as per specification

Check for positional accuracy with the help of control points

5.4.4 Deliverables: - Ortho-rectified Imagery

Ortho-rectified Satellite Image 5.5 Geo-referenced Administrative Boundaries of Revenue Village with Name of Village/Tehsil/District (UTM Projection) This head covers one of the Final deliverables of Project. As using the Revenue maps / ETS Survey

each Mussavies of all villages will be mosaicked / merged to create cadastral map of entire village.

This Cadastral map of village will be Spatially Adjusted over the Rectified (Geo-referenced using

ortho-rectification technique) High Resolution Satellite image (Section 2.2) the spatially adjusted

vector thus derived should attain the accuracy of 98% - 100% in length and area parameters subject

to the same as per ROR Data. The village map thus created can be used to create a village boundary.

The above mentioned process will be repeated for all villages of Subject Tehsil / District. These

Village – Cadastral maps will finally be merged to build entire Tehsil and then District.

Edge matching of individual villages must further attain accuracy of 98% – 100%, measured on

length / area variations on plots / killa boundaries located at the boundary of individual village.


39 | P a g e

The entire process of creation of Administrative boundaries as explained above thus can be pointed

as below:

a) Edge matching and merging of all Mussavies / revenue maps (Updated digitized vectors) to

create a cadastral map of village.

b) Spatial adjustment (Transformation) of thus created village vector over the Ortho Rectified

High Resolution Satellite image. Ensuring length / area accuracy of individual plots / killa be

not less than 98%.

c) Deriving the village boundary from the cadastral map of village.

d) Merging of village boundaries of all villages in tehsil. For all tehsil in the district.

e) Deriving Tehsil boundary from the merged village boundaries.

f) Merging all tehsils of districts together.

g) Deriving District boundary from merged Tehsil boundaries.

5.5.1 Responsibilities 1) Vendor shall ensure accuracy achievement of 98% - 100% of length / area parameters of

individual land parcels after spatial adjustment of vectors over the rectified High Resolution

Satellite image.

2) Vendor shall submit the merged data of tehsil once all villages of Subject tehsil are

completed in all aspects of project and merged together to create Cadastral/village

boundary GIS data of subject tehsil.

3) HARSAC authorized signatory shall perform the QC of Tehsil level GIS data and shall give the

acceptance or rejection remark of same within 7 days of submission over the Annexure-15.

4) Vendor shall submit the tehsil wise merged data of a district once the process is complete in

all aspects of project. Assuring that tehsil level data of each individual tehsil is verified and

approved by HARSAC authorized signatory. Vendor shall also submit signed copy of approval

(Annexure-15) of data of each tehsil of subject district.

5) HARSAC authorized signatory shall perform the QC of district level GIS Data and shall give

the acceptance of rejection remark of same within 7 days of submission over the Annexure-

16.

5.6 Establishment of Ground Control Points (GCPs) using dual frequency DGPS for Geo-referencing of satellite image.

5.6.1 Scope

Establishment of survey control points

Dual Frequency DGPS survey at primary, secondary and tertiary control points 5.6.2 Input data It is planned to develop the ground control point network (For Primary & Secondary control point) in reference to the existing network of Survey of India. Hence, following category of SOI control points / benchmarks to be provided

Primary control points ( coordinates)

Precision Bench marks having height information in 3 decimal places with respect to Mean Sea Level (MSL) as datum.


40 | P a g e

5.6.3 Generalized Planning Considerations for GPS Surveys The following are the important points of consideration during DGPS survey Planning.

Establishing primary control for subsequent location for Land record Modernization General site plan with feature mapping Number of horizontal points or benchmarks required or to be occupied Datum -- Horizontal and Vertical

Accuracy Desired (as per RFP) Horizontal and vertical

Equipment Resources Management In-house Resource arrangement Identification of External Resource (if required) GPS receiver availability(Dual Frequency DGPS) Other auxiliary equipment availability

GPS Procedure (high, Medium, Low level accuracy as desired in RFP)

Network Design and Connections

Static baseline connections to National Network of GPS control points of Survey of India provided by Client

Data Collection and Adjustment Techniques Feature and format requirements Data collection session time GPS initialization and calibration requirements Multiple/repeat baseline requirements Loop requirements for Primary points Other quality control requirements Adjustment criteria and accuracy standards Final survey report format

Site Access and Restrictions Reconnaissance survey required Potential visibility restrictions or multipath problems

5.6.4 GPS Survey

1. Project Design: It involve the network design, considering primarialy accuracy requirement of NLRMP and density requirements, . In addition to it Network designers shouldconsider the productivity / economic considerations, standards / specifications.

2. Observation Schedule: This has to be followed as specified in the NLRMP guide lines and accordingly the requirement of number of GPS receivers, Man power and other resource requirement shall be worked out.

3. Instrumentation & Personnel:This parameter involve the evaluation of the inhouse availibility of the instrument, Type of Instrument required to meet the accuracy creteria of NLRMP, arrangement / procurement of the additional DGPS recievers .

4. Logistical Considerations:Transportation, power, intervisibility, receiver deployment pattern are analysed and finalized

5. Reconnaissance:Highly essential for the selection of the site for the Ground Control Point whcih could preferably be located in District administrative offices, / Schools etc before the DGPS survey and allocation of responsiability to the district authorized representative for the monitoring of DGPS survey activity and monumentation construction activity .

6. Ephemeris:Precise ephemeris can be obtained bydownloading from the internet and the same should be used in post-processing of GPS obervation data.

7. Satellite Geometry: Accuracy of the coordinates are the function of the following factors i) A function of the measurement precision

ii) Systematic errors present


41 | P a g e

iii) The processing strategy used iv) The receiver-satellite geometry during the observing session

The (ii) and (IV) are the most variable. The other point of consideration are

A minimum of five satellites are recommended.

The configuration of the visible satellites.

Satellite geometry is expressed as a numeric value known as Dilution of Precision (DOP). The other DOP are HDOP and VDOP, the horizontal and vertical DOP respectively, while PDOP and GDOPare output by GPS receivers could be used for accuracy assesment. The ideal satellite geometry is one which has the visible satellites distributed throughout the sky. Good satellite geometry will yield a higher precision. This factor invlove the consideration of

a) Number of satellites available

b) Minimum elevation angle above the horizon (Elevation Mask)

c) Obstructions limiting satellite visibility

d) Position Dilution of Precision (PDOP)

e) Vertical Dilution of Precision (VDOP)

f) Horizontal Dilution of Precision (HDOP)

Elevation Mask: lowest elevation above the observer’s horizon that a satellite’s data is recorded. The minmum 15 degree elevation mask (cut off angle) is specifiedas per the NLMP guideline and RFP specification to avoid the multipath . In addition the atmospheric noise can also be minimized in the data.

a) Satellites that are high in the sky will have less atmospheric noise than satellites low in the sky and very close to the observer’s horizon.

b) GPS processing software allows for the elevation mask to be raised while processing to minimize the atmospheric noise.

Weather Conditions: a) No GPS observations during an electrical storm, severe snow, hail and rain storms

Sunspots or magnetic storms as these can affect GPS observations. b) Significant changes in weather or unusual weather conditions to be documented. c) No GPS observation Sunspots or magnetic storms can affect GPS observations. d) Generally a five digit weather code is used to summarize the general weather

conditions.

B. Project Layout & Network Design During a network designing, it is important to obtain the most economical coverage to meet the

accuracy requirement. The optimum network design, therefore provides a minimum amount of

baseline / loop redundancy without an unnecessary amount of observation.

Horizontal Control establishment

The Control point site identification shall be done using the ancillary data such as ancillary map, /

available satellite image, District administrative boundary and village census maps, tehsil / district

head quarter locational data. After this preliminary network designing the survey team has to be

sent on the ground to check the location of the selected points and if required additional / substitute


42 | P a g e

location can be selected. All the available Control points of National grid (i.e. Precision Control Points

of Survey of India) for the project area will be used/ connected in the Primary Network for the

purpose of reference. Some of these High Precision Control Points will be used in adjustment while

others will be used as check points at the time of final Post Processing of GPS observation data.

Reconnaissance for the project will include the following:

1. The selection of the site for GPS observation will be done considering the following limitations

a) Locations near strong radio transmissions should be avoided as these may disturb satellite signal reception.

b) Stations should be situated in locations relatively free from horizon obstructions. As satellite signals do not penetrate metal, buildings, or trees and are susceptible to signal delay errors when passing through leaves, glass, plastic and other materials.

c) Avoid locating stations near large flat surfaces such as buildings, large signs, fences, to avoid multipath errors.

d) Four (or more) satellite coverage is the accepted norm for standard static GPS surveys. There are periods when many more satellites are visible.

e) The satellites' positions in the sky are predictable. They can be computed and output in a convenient graphical form, and taken out into the field during reconnaissance.

2. Locationof the monumentation shall be clearly marked and identified 3. Site conditions:

a) Power availability. b) No loose soil at location for the proper mounting of antenna tripod. c) Documentation of potential multipath causing structures. d) Avoid location in vicinity of UHF, TV, radio, microwave or radar transmitters. e) Obstruction clearance if any. f) Taking photographs of the surrounding area, including any tree cover.

4. Software : The primary control points should be post-processed with precise ephemeris adjusted with the help of Bernese or equivalent s/w to the ITRF (International Terrestrial Reference Frame) co-ordinate system (latest version).

5.6.5 QA & QC for Error Detection (Annexure 17) Prior Processing can be carried out in the field / immediately after the observation session/ day’s work.

a) Was the height of antenna measured? Was it checked (by double measurement / another person)?

b) Do the values appear reasonable? c) Was the correct phase Centre measured to? d) Does the station log indicate any instrument or power problems? Were the correct

satellites (as noted in the log) observed? Were the observation times as planned? e) Were all field procedures correctly carried out? Is there any evidence to suggest that the

data is in any way unreliable? f) Was the correct site occupied? (Check photo evidence, pencil rubbing of ground mark, etc.) g) Check system status via electronic bulletin board or information service.


43 | P a g e

6.0 Network Design Specification (Annexure-18)

Primary Grid / Primary Control Points: Each 20Km (16 to 22 km)/Tehsil Head quarter spacing.

Must be located in a secured Campus, a Government Office preferably a Tehsil Office or Block

Development office or any other government building in Tehsil Head quarter and Panchayat

Bhawan Government School or any other government property in a selected village for

fulfillment of 20 Km criteria.

Secondary Grid / Secondary Control Points: Each 10 Km (8-12 km) spacing again in a secured

campus as for primary grid.

Tertiary Grid / Tertiary Control Points: Each at 5 km spacing and / or seheda stone in of a village

boundary.

Auxiliary Grid/ Auxiliary Control Points.

The Tertiary and Auxiliary Control Points (applicable to those villages for which ETS survey will be

done) should be established on each and every seheda stone and one or two locations within

village/ Mussavies boundary so that satellite image can be geo-referenced within required

accuracy.

6.1 Setting up the Ground Control Network (Annexure-19) All the control points should be based on datum given below:

i) Horizontal Datum: WGS-84 (i.e., the latest version of the World Geodetic System standard for used in cartography) ii) Vertical Datum: MSL, i.e., the Mean Sea Level.

6.2 Primary Control Points Horizontal

The primary control points will be established by static GPS observation (each for 72 hours) with

dual frequency DGPS receivers. These should be post-processed with precise ephemeris adjusted

with the help of Bernese or equivalent s/w to the ITRF (International Terrestrial Reference Frame)

co-ordinate system. All the secondary and tertiary control points should be connected to the

primary control points of the NRSC/SOI, to ensure connection to the National Framework. . Every

primary control point should be fixed by observing two masters and one rover in triangle. The

loop closures of triangle should be less then 3cm.

Vertical The precision Bench Marks should be developed as primary vertical control. Monumentation Specification The pillar should have the following characteristics

i) Rock-stone or Sand-stone 24*24*100cm or RCC. ii) The control point should be 15 cm above the ground and 85 cm inside the Ground. iii) The control points should be fixed to the ground using at least 15 cm of cement block. iv) Monuments shall bear a triangle on top with a plummet hole in the middle and a 15 cm steel

rod inserted (flush with concrete surface). v) The control point number should be inscribed on the monument


44 | P a g e

6.3 Secondary Control Points Horizontal The secondary control points should be established. These should be provided 8-12 Km Network

i) Best places for affixation: In protected areas like premises of government buildings including

school buildings, veterinary hospitals, etc. and other protected structures, etc. The selected

site should be open and clear to sky with a cut off angle of 15º. High-tension power lines,

transformers, electric sub-stations, microwave towers, high-frequency dish antennas, radars,

jammers, etc., which interfere with GPS signals, should be strictly avoided.

ii) Densification: 10 km average

iii) Instrument to be used: Dual-frequency DGPS receivers

iv) Accuracy levels required: 1 cm as determined by the residuals of the network adjustment

with 95% confidence interval. (Annexure-20)

v) GPS network design: Secondary control points should be observed with a geometrically

sound network plan, connected to primary control points in triangle.

vi) Schedule of observations: Observations should be scheduled with proper mission planning,

considering the optimum availability and geometric dilution of precision (GDOP) of satellites

less than 3 (i.e., geometric strength of satellite configuration on GPS accuracy). Minimum

observation time should be 4 hours.

Vertical All the secondary control points should be connected by spirit-leveled heights. The leveling lines for

such connections should terminate at precision control points and all errors adjusted within them.

Permissible error for leveling line: 0.025 ♪k (in meters), where k is the length of leveling line in km.

Monumentation of Secondary Control Points The pillar should have the following characteristics

a) It should be light in weight.

b) It should be easy to install.

c) Material used should be fire resistant.

d) It should stand for at least 50 years, if metal is proposed, it should be rust proof as well as

should be difficult to uproot.

e) Should have provision of engraving/punching the name of organization.

f) Pillars/markers for sandy/swampy soil.

g) Sleeve length for Secondary Control point survey marker would be 1 meter (100 Cm) in case

of rocky/hard grounds where the 1 meter hammering is not feasible 60 cm shaft may be used.

6.4 Tertiary Control Points

i) Distribution: The distribution and location of horizontal, vertical and full control points should be decided after preparing with the help of input images (i.e. as per the requirement of stereo-photogrammetric). ii) GCP selection criteria: The selection of location for a control point will depend on the

identification of the image point and the measurement characteristics of the image point. But, at

the same time, they should also meet the horizon parameters (15º cut-off angle). Thus, the

criteria for selection of such points should be:

a) GCP should be precisely identifiable on imagery as well as on the ground.

b) GCP should be a sharp point on image and ground.


45 | P a g e

c) The selected GCP shall be open and clear to the sky, without any obstruction to the sky.

iii) Post-pointing: All tertiary control points should be post-pointed on imagery (i.e., the points

should be identified on the image), preferably in softcopy. If post pointing on hardcopy is to be

done, the control point should be post-pointed at full resolution. In addition, a sketch magnifying

the vicinity of control points and their detailed description should be prepared on the ground, to

aid the photogrammetric operator.

iv) Additional points: In addition, tertiary control points may be provided on structures like village

boundary tri-junction or bi-junction, existing govt./non govt. buildings like gram Panchayat

offices, school buildings, veterinary hospitals, etc., as per the field survey requirements.

v) Instrument: Single/Double-frequency GPS, Total Station

vi) Accuracy levels required: 5 cm

vii) GPS network design: Tertiary controls should be observed as triangular offsets. Single offset

will not be allowed.

viii) Schedule of observations: Observations should be carried out with proper mission planning.

Minimum observation time should be 45 min to 1 hour.

ix) Vertical control: Single GPS offset up to 5 km from secondary vertical control may be allowed

for connection of GPS heights in WGS 84 datum to MSL heights. However, such offsets should not

be extended.

6.5 Auxiliary Control Point

i) Best places for affixation: Each secondary and monumented tertiary control point shall be

paired with one auxiliary control point (Wherever required for ETS survey), which should be

located on permanent structures like bridges, culverts, permanent building corners, etc. The

auxiliary control points should be within the line of sight from the primary, secondary and

tertiary control points.

ii) Densification: There shall be one auxiliary point for each secondary and tertiary control

point, typically 200 m

iii) Instrument: Dual/Single-frequency GPS Receiver (as used for main control).

iv) Accuracy levels required: same as their respective primary, secondary and tertiary control

points.

Monumentation of Tertiary Point

The pillar should have the following characteristics

a) It should be light in weight.

b) It should be easy to install.

c) Material used should be fire resistant.

d) It should stand for at least 50 years, if metal is proposed, it should be rust proof as well as

should be difficult to uproot.

e) Should have provision of engraving/punching the name of organization.

f) Pillars/markers for sandy/swampy soil.

g) In case some modern technology develops later, the details will be circulated separately.

h) Sleeve length of Tertiary Control Points would be 60 Cm


46 | P a g e

6.6 ETS Survey Input:

Reference map/satellite map

Monument points with coordinates taken through primary/secondary/tertiary/soi/auxiliary points (minimum two points)

Output:

Raw output in CSV (Comma- separated values) format

Digitized parcel in shape format

Traverse details if applicable with closing error (to be decided)

Field book/sketch

Photographs of ETS survey Note:

1. Once parcel details are prepared, the same shall be provided to Patwari/Kanungo for Updation of Khasra number as well as length /dimensions and other details.

2. ETS should be limited to maximum 5% of total musavi in a district. Quality Control:

Check for Traverse: it should be stared from a known control point and closed at a known control point.

Random checking on field by authorized person shall be done at the time of ETSsurvey.

Corresponding Field Photographs: Field Reports to be verified by authorized person.

6.7 Data Collection The point of consideration is as follows:

The normal collection rate (epoch:- a particular moment in time)) is 5 seconds for static

observations but for long observation times of more than 3 hours, a collection rate of 30

seconds is acceptable.

Antenna setups will require a diagonal (slope) distance to be measured from the edge of the

ground plane to the monument. For Trimble antennas (with ground plane), the diagonal

measurement is made from a notch on the outer perimeter of the antenna and must be

noted as such on the log sheet.

There should be one log sheet per observation. At the end of the day or the end of the

project, the party chief, knowing the number of observations, must collect all of the

completed data sheets.

The elevation mask should not be set at less than 15 degrees. Data from satellites lower than

that is just about useless for surveying; it is too noisy going through the atmosphere.

All observers should be well aware of the scheduled start and stop times for each session

In some situations, time can best be utilized by observing the station’s azimuth mark (which

is usually about a half mile away and visible from the newly placed station) during the long

observation time. The azimuth mark generally only requires about 20 to 30 minutes.

However, users will probably not be able to safely leave the station setup unattended,

unless it is in a secure area such as a fenced in maintenance yard.


47 | P a g e

6.7.1 Downloading the Data The Trimble Programme for transferring the raw data files from the receivers to the laptop or PC is

called Data Transfer. Microsoft ActiveSync can also be used. One should never leave a project-site

where considerable travel is required, before downloading the files and matching the log sheets.

6.7.2 Processing Bernese or Equivalent s/w shall be used for the Processing of the data. Care should be taken that

each file includes the correct antenna type, antenna height, and type of measurement.

The processing will produce a “fixed” or a “float” solution and it could be determined using L1 only

or L1/L2. The fixed solution is considered best but for extremely long baselines the float solution

may be the only solution available. For very short (5 km and less) baseline, an “L1 Only” solution will

probably be the final solution. However, users should hope for L1/L2 (also called iono-free) on

baselines longer than approximately 5 or 10 km.

The processing will generate several other quality indicators. The RMS error estimate of the

vector is a good indicator. Performing loop closures on selected vectors will make blunders

apparent. It may take a few tries to determine which vector is at fault. Just as with a conventional

traverse, a ratio of precision or parts per million is the method of checking the closures.

6.7.3 Troubleshooting Problematic Baseline A problematic baseline can be defined as a line observed with two carrier-phase GPS receivers, L1 or

L1/L2, and the baseline solution does not meet the manufacturer’s specification for quality. In most

cases, the problematic baseline was observed with enough satellites for a long enough time period,

but the quality indicators show the line to be unacceptable. The following are suggestions on what

to look for when troubleshooting problematic baselines:

Look at the plot of all satellites during the observing session; there is a plot for each receiver.

Software packages differ, but common to most is a plot showing each satellite observed, one

below the other.

What to look for:

o When a cycle slip occurs, or there is a loss of lock due to obstructions, there will be a

break in the line on the graph for that particular satellite.

o A short break indicates a cycle slip, a longer break; an obstruction.

o If too many breaks have occurred, eliminate that satellite and try the baseline

solution again. In many cases, this solves the problem.

Look at the plot of satellites for both receivers.

o Was the start and stop time approximately the same, or did one receiver start or

stop too early or too late?

o Start and stop times can be changed to encompass only common observing times

and then re-observe the baseline.

Satellites with a high signal-to-noise ratio (SNR) can cause problems. In many cases, a high

SNR occurs when the satellite is close to the horizon. It is possible to have a satellite low on

the horizon for the entire session. In that case, the satellite should be eliminated from the

solution, then resolve the baseline.

Another way to eliminate high SNR on satellites low to the horizon is to raise the elevation

mask for the baseline solution.


48 | P a g e

If the length of the session is short, perhaps too short, try a baseline solution with a shorter

epoch than normal.

o If the default on the baseline solution is thirty (30) seconds, try fifteen (15) seconds.

This will increase the number of single, double, and triple differences needed to

resolve the baseline.

If all the above suggestions fail, resolve the baseline using a more precise ephemeris than

was started with.

As a last resort, the baseline must be re-observed. Be sure to select a time period different

from the original observed time. Look at sky plots and select a time with many satellites and

an area free of obstructions.

6.7.4 Network Baseline

For any given multiple receiver session, there are n (n-1)/2 total session possible, where n =

the number of GPS receivers observing simultaneously. The number of independent vectors

is n-1.

6.7.5 Accuracy Standards for Network Baseline

For a station to qualify for an accuracy classification, network or local, it must meet the

listed accuracy standards, relative to all other stations in the network and/or datum,

whether or not there was a direct connection between them.

6.7.6 Responsibility Vendor

Team deployment for establishment of control point as per the specification.

Conducting DGPS Survey - district wise and submission of data as per approved format. (Annexure-21).

HARSAC Approval of the Primary, Secondary and Tertiary Control Point DGPS

Network Design. Reconnaissance survey for the identification of location in field. Approval of the DGPS network. Coordination with DLR-H for the identification of the Authorized

representative for each primary secondary and Tertiary location for control point establishment monitoring.

Distribution of the Approved DGPS data to various vendors. Communication to the Vendor regarding the authorized representative of

DLR-H. Estimation and approval of revised rate due to variation in quantity and

deviation of the design specification.(Annexure-22) DLR-H

Finalization of the list of the Authorized Representative at all location of primary, secondary and tertiary control point Monumentation and verification of the DGPS data collection activity.

Verification of the DGPS survey data collection activity. Estimation and approval of revised rate due to variation in quantity and

deviation of the design specification.


49 | P a g e

7.0 Document Retrieval Software

Scope of Work The scope of work includes the collection of documents i.e. Mussavies, Jamabandi, Misal Haqiyat,

Field book and Registered deed and defining the responsibilities for availability of various documents

by the ( District/DLR/HARSAC/vendor). It also describes the format for receiving and returning of the

various documents. Also, it describes the format for submission and acceptance of all the

documents.

Process The process consists of finding the status of the document first. After this, a proper communication

should be in between the different persons involved in this project if the particular document is not

doable or there is of non-availability of some documents. Methodology for scanning/ methodology

for storage/methodology for printing/ methodology for binding (size & design)

Codification and Metadata generation- Need for codification and metadata- It is for the ease of document retrieval and inter linkage for

historical data fetching. NIC has the master tables or database for the Haryana. Codification should

be such that it can link our documentation with the codification used in NIC

I. Need for file based storage and benefits a) Usually, better performance, especially with an elevated number of documents. b) Database size is kept to a minimum, thus making it unlikely that the maximum database size

limitations are ever reached. c) The documents can be easily accessed by third party applications, such as indexing services,

search appliances and other programs. d) Increased complexity as the data is spread between two different places. e) All users must have read and write accesses to the directory or network share where the

documents are stored.

II. Need for metadata table- Query on one table to fetch the scan documents. III. Need to create web based viewing- With the web based application we can view document

from anywhere using internet that also helps to storage of database. Here we scan low size documents and separate original scan documents for record/printing.

7.1 Code of scan document File Naming Convention

Below is the File Naming Convention for all types of scanned document except Musavi, & Registered

Deed.

VVVVV_DT_YYYY-YYYY_PP.pdf

E.g.: - 02476_02_1963-1964_04.pdf

For Musavi

VVVVV_DT_YYYY-YYYY_NNN.pdf

E.g.: - 02476_01_1963-1964_122.pdf

For Registered Deed


50 | P a g e

VVVVV_DT_YYYY_RRRR_BB_PP.pdf

E.g.: - 02476_02_2006-2007_4157_01_01.pdf

Where RRRR - Register No. (4 Digit Varchar Cap), VV-Book No. (2 Digit Varchar Cap)

For Mussavies Index map

VVVVV_DT_YYYY-YYYY_TTT.pdf

VVVVV: 5 Digit Varchar Village Code (NVCODE”) as mentioned in RoR e.g. village code of Kurbanpur village is 02884. YYYY-YYYY: Period of Scanned Document e.g. (1963-1964). (1996-2001)

DT: 2 Digit Varchar Code for Document type

01 – Mussavies, 02 – Field book, 03 – Jamabandi, 04- Misal Haqiyat, 05- Mutation, 06 – Registered Deed 07- Intkal 08- Sajra Nasab, 09- Lalkitab 10-Girdhavari

PP: 2 Digit Varchar Code, if scanned document is large and spllited in multiple files.

NNN: 3 Digit Mussavies No. (Numeric) e.g. 122

TTT: 3 Digit text ex- “IN1”

Folder Structure to Store Scanned Document

Below is the Folder Structure to store all types of scanned documents on physical drive or network

drive.

Drive:\>HARYANA_DATA\VVVVV\DT\YYYY-YYYY\VVVVV_DT_YYYY-YYYY_PP.pdf

E.g.:- D:\HARYANA_DATA\02476\02\1963-1964\02476_02_1963-1964_04.pdf

Drive: Document can be stored on any Drive e.g. (d:) or network drive e.g. (z:).

There should be a folder on drive named as HARYANA_DATA.

VVVVV: 5 Digit Varchar Village Code (NVCODE”) as mentioned, in RoR e.g. village code of

Kurbanpur village is 02884.

YYYY-YYYY: Period of Scanned Document e.g. (1963-1964).

DT: 2 Digit Varchar Code for Document type

01 – Mussavies, 02 – Field book, 03 – Jamabandi, 04- Misal Haqiyat, 05- Mutation, 06 – Registered Deed 07- Intkal 08- Sajra Nasab, 09- Lalkitab 10-Girdhavari

PP: 2 Digit Varchar Code (01-99) if scanned document is large and spitted in multiple files.


51 | P a g e

Example of folder Structure Except for Girdhawari

Folder Structure for Girdhawari

Metadata

Metadata Table Structure for ROR except Registry

Hadbast nvcode period murrba khasra doctype Pdfno pageno path

Example of Field Book Metadata

Hadbast nvcode Period murrba khasra doctype Pdfno pageno path

259 02884 2005-2006 13 8/2 02 3 148 02884\02\2005-2006

259 02884 2005-2006 13 9/1 02 3 148 02884\02\2005-2006


52 | P a g e

Example of Jamabandi Metadata


259 02884 2005-2006 13 8/2 03 3 148 02884\03\2005-2006

259 02884 2005-2006 13 9/1 03 3 148 02884\03\2005-2006

Example of Misal Haqiyat Metadata


259 02884 2005-2006 13 8/2 04 3 148 02884\04\2005-2006

259 02884 2005-2006 13 9/1 04 3 148 02884\04\2005-2006

Example of Intkal Metadata


259 02884 2005-2006 13 8/2 07 3 148 02884\07\2005-2006

259 02884 2005-2006 13 9/1 07 3 148 02884\07\2005-2006

Metadata Table Structure for Register Deed

Tehsilcode Regno Period Book No pdfno pageno Path

Example

Tehsilcode Reg.no Period Book No pdfno Page no Path

001 4857 2001-2002 1 1 1 02884\03\2001-2002

001 2367 2005-2006 1 1 1 02884\06\2005-2006

Metadata Table Structure for Girdhawari

Hadbast

nvcode Period(start year-end year)

murrba khasra doctype Pdfno pageno path

259 02884 1996-2001 23 21 10 11 5 02884\10\1996-2001\02884_10_1996-2001_11.pdf


53 | P a g e

259 02884 1996-2001 23 22 10 11 5 \02884\10\1996-2001\02884_10_1996-2001_11.pdf

Metadata Table Structure for Missing Documents

Hadbast nvcode Period Doctype

Note: The above metadata to be stored in SQL server and dump to be delivered tehsil wise.

Description & Source of Each Field

S.N. Field Description Source

1 Hadbast Varchar (5) As provided by HARSAC

2 Nvcode Varchar (5) As provided by HARSAC

3 murrba Numeric (4) Manual entry from Scanned document

4 Khasra Varchar (255) Manual entry from Scanned document

5 Doctype Varchar (2) As described above in File Naming Convention.

6 Pdfno Varchar (2) As described above in File Naming Convention.

7 Path Varchar (255) As in Folder structure

8 tehsilcode Varchar (5) From ROR data

9 Regno Numeric (6) Manual entry from Scanned document

10 Period Varchar (9) Manual entry from Scanned document

11 Book No Varchar (5) Manual entry from Scanned document

12 Pageno Numeric(5) Manual/Automatic entry from Scanned document

Examples showing integration of scanned documents using codification


54 | P a g e

1. MUSAVI


55 | P a g e

IV. Register Deed

V. Girdhavari


56 | P a g e

Responsibility of Vendor related to the Meta Data Generation

Each Vendor has to ensure the accuracy and correctness of the Meta data generated by its team

related to the scanned documents.

Security of Scanned Documents:

There are many aspects to security, for example document can be deleted or edited by any person.

There should be only administrator to delete the document. For these application has login system

and, every user has defined its role, so that only authorized person can change the document.

Application has two security aspects: -

Issue of Security arises for editing or deleting of document and to restrict unauthorized access of a

document. For this, two levels of security will be integrated in windows based document retrieval

system application: -

a. User Login b. Windows File & Folder Security

a. User Login

Authentication and Authorization are two interrelated security concepts. Authentication is a process

of identifying a user, while authorization is the process of determining if an authenticated user has

access to the resource(s) they requested. Typically, authentication is achieved by the user

sharing credentials that somehow verify the user's identity.

There is administrator account in the application and administrator can create, delete, and edit a

user profile. Administrator need to control who is accessing the information from application.

Administrator can provide different permissions & right to each user of application. It is the

responsibility of administrator to whom he/she authenticate and authorize to use the application.

After creation of user, user can login to the application & use the application as directed by the

administrator. Whenever a user logs on to an application, the user is first authenticated and then

authorized. If the reading permission is allocated by the administrator the user cannot delete or edit

the document. If full rights are given to the user then user can delete or modify the document.

b. Windows File & Folder Security

Because files are securable objects, access to them is regulated by the access-control model that

governs access to all other securable objects in Windows. Windows provides a built-in way to access

information and check user privileges to decide who can and who cannot access a document/folder.

Each file/folder in Windows has security information. You can set security permissions on files and


57 | P a g e

folders. These permissions grant or deny access to the files and folders. You can view security

permissions for files and folders

Geocoding & Linking with ROR Data: A standard code as per the codification guideline is generated for each scanned document. This

standard code is also available in ROR Data, so while we retrieve any data from ROR data we will join

this scanned document’s code with ROR data & display the scanned document along with attribute

data present in ROR data.

7.2 Application Development for Document Management System:

An application is to be developed for easy indexing and retrieval of scanned documents along with drawing of land parcel with dimension (from map and RoR) attribute information, neighborhood details and printing the maps and data on existing HARLIS of NIC.

The application to be developed can be broadly categorized into two modules. a) Data Integration Module: There are three different data sets which are to be integrated

namely: a. The old records (scanned images). b. The RoR Data as in HALRIS (NIC) data base. c. The GIS Data – Vector Plot boundaries.

A unique primary key / index will be generated for the integration of above said three different data sets assuring:

i. Access to Scanned document from RoR data, ii. Access to Scanned Document from Map (Plot Boundary), iii. Access to RoR from Map (Plot Boundary), and iv. Access to Map from RoR.

b) Document Retrieval System: For retrieving / Printing of old records (Musavi, Jamabandi,

field book, Registry deed, Misal Hakiyat and others) from a single point interface. Also, depending on different user types (i.e., administrator, user, guest etc.) different rights of access will be provided for deleting old records, printing and viewing of Documents and Map.

7.3 Application Prototype

a) Data Integration Module: this module will be handled through Bhu-Naksha software at database level.

b) Document Retrieval System:

i. Control for accessing scanned document via map. ii. RoR Data Navigation Panel- once the entire GIS & RoR data be created and

integrated respective plot / area can be queried and zoomed to reach the location of interest in Map window.

iii. Control for accessing scanned documents via RoR Data- if Plot no. is known the scanned old records of revenue will be accessed directly from RoR Data Navigation Panel (ii), by selecting plot details and clicking the subject button.

iv. Legend / Layer Display Control- facility to switch on or switch off the visibility of layers in Map Window and also to control basic properties like visibility of labels of visible layers.


58 | P a g e

Query Module: based on user input and specific requirement a query module will be integrated with document retrieval system, similar, to RoR Data Navigation panel this will allow different stake holders to access the various Scanned Documents / GIS / RoR data base on basis of different criteria’s of selection. Sample Example of probable queries for document:

- Temporal Query: Time based Accessing of documents i.e., those which are created after/before a given date / year.

- Spatial Query: Spatially reaching the plot location on map and selected all documents related to the plot.

- Ownership based query: selecting documents in village owned by one particular. - Query on RoR Data: selecting documents using RoR data fields like mutation no., killa no.,

murrba no. etc. - Hybrid Query: selecting and viewing documents with more than two selection criteria as

explained above. Testing

A test case in software engineering is a set of conditions or variables under which a tester will

determine whether an application or software system is working correctly or not.

Testing Process:

The following represents the overall flow of the testing process:

1. Identify the requirements to be tested. All test cases shall be derived using the current Programme Specification.

2. Identify which particular test will be used to test each module.

3. Review the test data and test cases to ensure that the unit has been thoroughly verified and that the test data and test cases are adequate to verify proper operation of the unit.

4. Identify the expected results for each test.

5. Perform the test(s).

6. Successful unit testing is required before the unit is eligible for component integration/system testing.

Schedule: Software development activity shall run in parallel with the GIS data creation and scanning of revenue record. With data creation activity the updated ready data can be used for application building and testing. However the final deployment of application should be done only after completion of data creation activity. Responsibility

- HARSAC shall ensure that different vendors involved in GIS data creation activity shall be in sync and the data structures, created is common for all.

- HARSAC and DLR-H shall provide the platform form time to time for communication with NIC team for better understanding and query resolution of RAMTeCH Application Development team regarding HALRIS and RoR data available with NIC.

- DLR-H shall assign a representative to address queries of RAMTeCH Application Development team, for better understanding of Scanned documents.

- DLR-H, HARSAC, and NIC together in coordination with RAMTeCH Application Development team shall freeze the requirement and document the Requirement Definition.

- DLR-H/HARSAC and NIC shall approve the test case.


59 | P a g e

7.4 Standards for Database Organization

Various data folder nomenclature for project is as follows

The table 4 shows the CD/DVD/HDD Volume Nomenclature.

CD/DVD/HDD VOLUME NOMENCLATURE

CD/DVD/HDD Volume label DDTTTNNN Naming convention (DD stands for the 2 letter district code and TTT is for the 3 letter tehsil code &NNN is the sequential number starting from 001 to 999)

Table 4: Volume Nomenclature

The table 5 shows the nomenclature for the folders/directory/workspace in CD/DVD/HDD.

Each CD/DVD/HDD should contain the following folders/directory/workspace

1 TIFDDTTT

For scanned raster files in tiff format

Raw and after registration with grid

2 PDFDDTTT PLOT files converted into PDF format

All plot files as PDF format

3 PLADDTTT Un-rectified shape files at village level

Individual Planimetric ArcGIS shape files format

4 GEODDTTT Geo-referenced shape at village level

Individual, Geo-referenced ArcGIS Shape file format

5 MOSDDTTT Geo-referenced mosaic shape/geo-database at tehsil level

Mosaic Shape/geo-database at various levels

Table 5: Nomenclature for the folders/directory/workspace

The table 6 shows the each FOLDER should contain the following files for each village with their

nomenclature.

TIFDDTTT

IDDTTTVVVVV-NN.tif

Sheet-wise original scanned Mussavies in tiff format

RDDTTTVVVVV-NN.tif RDDTTTVVVVV-NN.tfw

Sheet-wise grid corrected Mussavies in tiff format (Planimetric)

GDDTTTVVVVV-NN.tif GDDTTTVVVVV-NN.tfw

Sheet-wise Geo reference original scanned Mussavies on satellite data in tiff format

PLADDTTT(ArcGIS feature files – unrectified)

aDDTTTVVVVV.shp/.gdb Planimetric Area shape/geo-database at village level

lDDTTTVVVVV.shp/.gdb

Planimetric Line shape/geo-database at village level


60 | P a g e

pDDTTTVVVVV.shp/.gdb

Planimetric Point shape/geo-database at village level

tDDTTTVVVVV.shp/.gdb

Planimetric text(Point) shape/geo-database at village level

GEODDTTT(Geo-referenced on HRSI ArcGIS feature files)

aDDTTTVVVVV.shp/.gdb

Geo-referenced area shape/geo-database at village level

lDDTTTVVVVV.shp/.gdb

Geo-referenced line shape/geo-database at village level

pDDTTTVVVVV.shp/.gdb

Geo-referenced point shape/geo-database at village level

tDDTTTVVVVV.shp/.gdb

Geo-referenced text (point) shape/geo-database at village level

MOSDDTTT(Mosaic of geo-referenced villages without edge matching at tehsil level.)

maDDTTT.gdb

Geo-referenced mosaic area geo-database at tehsil level

mlDDTTT.gdb

Geo-referenced mosaic line geo-database at tehsil level

mpDDTTT.gdb

Geo-referenced mosaic point geo-database at tehsil level

EMOSDDTTT(Mosaic of geo-referenced villages with edge matching village-wise at tehsil level.)

emaDDTTT.gdb

Geo-referenced mosaic area geo-database at tehsil level

emlDDTTT.gdb

Geo-referenced mosaic line geo-database at tehsil level

empDDTTT.gdb

Geo-referenced mosaic point geo-database at tehsil level

VMOSDD(Mosaic of village boundary at district level)

vaDD.gdb Geo-referenced mosaic area geo-database at district level. This layer can also be referred to as ‘VIL’ layer of NRIS.

vlDD.gdb Geo-referenced mosaic village boundary geo-database at district level.

MOSSSSDD(Mosaic at State level)

vaSSSSDD.gdb Geo-referenced mosaic village boundary geo-database at District level matched with the adjacent district.

Table 6: Nomenclature for files.


61 | P a g e

7.5 Security of the Digital Database

1. Any information that is sensitive or vulnerable will be encrypted. Standard algorithms will be

used for encryption.

2. For security and network maintenance purposes, authorized individuals within Vendor can

monitor equipment, systems and network traffic at any time.

3. All PCs, laptops and workstations will be secured with a password-protected screensaver

with the automatic activation feature set at 1 minute, or by logging-off (ctrl+alt+delete for

Win2K users) when the host is unattended.

4. All hosts used by the employee that are connected to the Vendor network will execute

approved virus-scanning software with a current virus database. All Vendor computers shall

be installed with Vendor standard, supported anti-virus software, which shall be scheduled

to run at regular intervals.

5. Only authorized staff members are allowed to take backup of any data. The backup media is

always kept at a place that is not accessible to any unauthorized staff. Data backup will be

done only on one system that will be accessible only to the project leader. All backup will be

encrypted.

6. No removable media, such as CD reader/writers & FDD, are installed in any of the systems.

Also, USB ports will be disabled in all the systems and wherever possible, the USB cables

shall be removed. It is ensured that all removable media is removed before the system is

sent for production.

7. All systems should have a BIOS system level password in order to prevent anyone from

changing the setup.

8. No remote access will be provided to any of the computer.

9. No data sharing will be allowed on any of the operators PC.

10. All data in paper/CD/DVD or in any other form shall be retained by HARSAC/DLR.

11. Audits will be performed on a regular basis by authorized organizations.

12. No Internet access shall be provided to any individual without prior permission from the

Project Coordinator.

13. E-mail access shall only be given to the Project Manager unless any requirement occurs.

14. Grant access or remove access to any individual shall be given with permission of the Project

Manager.

15. No shared user ids will be used.

16. All physical networks like cables, routers and switches shall be inside the project zone.

17. No sharing of password with anyone shall be allowed.

18. No wireless technology with data transfer capabilities inside the project zone shall be

allowed.

19. Server shall have password protected screen saver.

20. No writable media shall be found in the project zone except for the server where backup

tapes/disks or other essential writable media are handled.

21. Only authorized and licensed software shall be installed on workstations and servers and

those records shall be kept for all installed software.


62 | P a g e

22. No visitors shall be allowed in the production area. In case of a visitor, the security guard

informs the concerned person about the visitor. Under no circumstances is any visitor

allowed beyond the reception area.

23. It is mandatory for all employees to wear their Photo ID card at all times in the office.

24. No employee is allowed to enter the office without the Photo ID card. However, in case any

employee forgets to carry his Photo ID card, he shall be required to call the Supervisor/ Shift-

in-Charge.

25. No material is allowed in or out of the office unless a gate pass is issued and verified.

26. All the confidential documents, data backup of the organization are kept in a cabinet and the

keys are available with Project Manager.

27. No housekeeping personnel are allowed into these restricted areas without the permission

of the Project Manager and a log for their entry/ exit is maintained.

28. In case of a loss of Photo ID card, employee is instructed to immediately inform

Admin./concerned Supervisor and the lost card is then immediately disabled by Admin.

7.6 Storage and Security of the Digital data

Folder System for GIS data base

There will be four level data base

1. State level

2. District level

3. Tehsil level

4. Village Level

State , District, Tehsil level database shall be in form of ESRI*. gdb format

Village level database shall be in shape file format

1.0 State Level

Folder - Haryana

Shall contain ---- Haryana .gdb

1.1 District level

Folder- DD

Shall contain ---- DD.gdb

1.1.1 Tehsil level

Folder- TTT

Shall contain ---- TTT.gdb

1.1.1.1 Village Level

Folder- VVVVV

Shall contain ---- Layer .shp

Layer as defined in SDD

Note: State level folder shall contain

Haryana .gdb and folder as specified

in 1.1, 1.1.1

Where

DD stands for District Code

TTT stands for Tehsil code

VVVVV stands NV code


63 | P a g e

HARSAC has adopted multi faced security control to ensure that the data being generated under

NLRMP project is safe and secure. The details of the security policies implemented are as below:-

1. The “SEDULITY OPERATING SYSTEM.” To be deployed on all the computers, it is the one of

the Secured Operating System based on the Linux Kernel. (Patent Applied in India), Where

most of the security applications/ utilities are preloaded in it. As it is the Virus free Operating

System so the major issues of the data leakage/ Corruption was controlled by this Operating

System.

2. Certain Security policies implemented on all physical ports of data transmission like USB for

external Drives, networks etc. are blocked.

3. No CD/DVD device is attached. And if available that is also blocked.

4. BIOS (Basic input output system) are also secured by administrator.

5. The USB port is open for scanning purpose to interact the data with the Applications. There

is no provision to get the data outside. At the time of printing similar access shall be

provided on the identified machines.

6. All administrative privileges are secured by HARSAC. One standard user is provided to

vendors for working with limited privileges. With these limited privileges user cannot install

any other software into the systems.

7. In terms of Physical Security the system were sealed before delivery. The checklist was

followed for all the software and the Security policies/ admin rights implemented in the

systems.

8. In case if the hard disk is full because of scanning or scanning is completed at the remote

location, then the data shall be retrieved only by HARSAC Executive and stored in the

separate Sedulity OS (Server/ Client Editions) systems. So that the data should never get

corrupt while transferring of data because of any virus etc.

9. There is procedure to audit the systems. Incase if any hard disk or pen drive attached by the

vendor and they trying to give or copy the data in any external device, that is filtered by

SEDULITY OS.

10. All Vendors’ servers are also prepared on SEDULITY OS (server edition) or SEDULITY OS (64

bit client edition). For data centralization.

11. All clients’ machines of vendors are connected through the server.

12. At client side windows/ sedulity OS is installed. As per their comfortability of the

Applications used for their Work. And the above defined security policy implemented before

connected to the separate private network for them.

13. Data transmission is blocked in the external drives. Where all the systems are connected

with in their separate private network and connected with server. No provision is given to

add any extra PC to the vendor’s network.


64 | P a g e

14. As every vendor have their separate private network, so all the vendors cannot access the

data of each other.

15. Data input and output process is done at the server end only. In case of any further issue

related to Data transmission, Vendors need to take the permission from HARSAC

Administrator. So there is no provision to access data without permission.

16. All scanned data would be copied temporarily in the HARSAC SEDULITY OS based system.

At HARSAC side security system

All scanned data is copied at HARSAC SEDULITY OS based system also for backup purpose.

All Output data collects from all Vendors after final process and stores in Secured Sedulity based

work stations.

In this process there is no chance of virus. When any data through hard disk or pen drive is given by

vendor that is filtered by SEDULITY OS based system.

8.0 Standard Operating Procedure for Ortho Rectification

World View stereo imagery should be processed through photogrammetric technique for better

accuracy.

S.No Description Quality Control from HARSAC

1 A project (Project) needs to be created with

the following information.

Name of the project

World View Sensor Model need to be

selected

Projection and Datum parameters needs to

be inputted for both Horizontal and Vertical

Check for

Name of the Project

Whether right sensor model is chosen or not

Is the projection and datum parameters correct or not

2. Images in tiff format needs to be added to

the project

Multiple stereo images should be inputted to

process as project bundle adjustment (district

wise)

Is the project created with single pair or with multiple

pairs.

3. RRDs need to be generated Check for status of RRD

4. Input stereo supporting files which comes

with the tiff files

Check the status of stereo supporting files added to the

project


65 | P a g e

5. Input control points to the project and place

the control points on to the images

Whether the coordinates of the control points are

matching with projection/datum parameters defined

while creating the project

Check for description of the control points(id or name)

for validation purpose

Whether images points placed is with reference to control

points

6. Add tie points to images Does every image has tie points

Does tie points are well distributed

Does every images has enough tie points

7 Add check points Whether right GCP has been selected as check point

Whether image points are placed corresponding to each

check points

8 Triangulation Total RMSE(should be < half pixel)i.e. 0.5

Check for total GCP residual for X Y and Z(should be less

than 0.3 meter

Check for total Image points residual(should be less than

= half pixel) i.e. 0.5

Check the triangulation report

Printout of the triangulation report

Check for individual GCP residual(in X, Y and Z) in report

Correct the GCP which has maximum residual(should be

less than 1)

Check for individual Image points residual in report

Correct the point which has maximum image point

residual(should be less than 1)

9 Accept triangulation results Final RMSE, Control points residual, tie point residuals

and check point residuals

10 Stereo viewing of triangulated project Look for presence Y-parallelex, if yes, need for running

the triangulation process again by editing the points

Randomly check the X, Y and Z values at known locations

using stereo visualization and compare the results.


66 | P a g e

11 Generate DEM(automatic) at post spacing <=

2 meters(To be decided by HRSAC)

Open DEM to check any available anomalies in elevations

Generate DEM accuracy report with some known height

values

Check the DEM accuracy report

Check the projection of the DEM and Post Spacing

12 DEM editing Need to carry DEM editing in stereo mode.

The accuracy of DEM should be <= 1 meter

Do not generate any automatic TIN. Generate mass

points and measure Z value for each and every point and

add break lines.

Then generate the DEM using Mass points and Break lines

and use the DEM for ortho- rectification.

13 Ortho rectification All the images has to be ortho rectified

DEM to be inputted for ortho rectification process

Projection / Datum parameters to be checked

Quality of ortho rectified images

Edge matching between adjacent image

14 Ortho mosaics and custom tiling Cutlines

Color balancing

Tiled images should match with the customer grid of

HARSAC.

8.1 Standard Operating Procedure for Ortho Rectification recommended by NRSC

(1) State level block triangulation is suggested.

(2) A minimum of 25 tie points, manually collected/visited should be identified in each stereo pair.

(3) Concentration should be on 8 ray-points, followed by 6 rays and 4 rays.

(4) DEM should be generated in manual mode using break lines and height points.

(5) DEM posting should be 2m and ortho image 0.5m.


67 | P a g e

(6) Bare earth model, avoiding tree tops and building tops should be generated.

(7) The merged FCC as well as NCC should be generated.

(8) The outputs should be generated in WGS84 datum with (i) geographic and (ii) state projection,

suggested by NNRMS standards.

(9) The rms values of state level block, image, control and check points should be sub-pixel levels.

(10) DEM should be validated, both in absolute values, as well as relative values.

(11) Relatively, DEM will be validated using height values at a point in more than one stereo pair of

overlapping regions.

(12) DEM and ortho should be generated more than the state boundary, without cutting the scenes

along the state boundary. Later it can be extracted using the boundary condition.

Note: if any ambiguity arises, NRSC decisions should be final.

9.0 Deliverables

9.1 Village Maps

1. 75 micron polyester original scanned musavi – 1 copy

2. 100 GSM digitized original musavi in color for updation- 1 copy

3. 100 GSM Sajra map for final acceptance by DRO- 1 copy

4. 75 micron polyester final printout - 3 copies

5. Digital musavi, Sajra maps in shape file

6. Geo-referenced Digital musavi, Sajra maps in shape file

7. Scanned musavi in .tiff and .pdf file

9.2 List of Khasra No. Mismatch with ROR

1. Village wise list in .xls format showing following field

2. Murrba No.

1. Khasra No.

2. Hadbast No.

3. Missing Source (e.g. ROR , updated Mussavies)

9.3. Tehsil Map

1. 100 GSM paper color printout on A0 / A1 size paper- 1 copy

2. Mosaic Geo-referenced digital data in Shape format

9.4. District Map

1. 100 GSM paper color printout on A0 size paper- 1 copy

2. Mosaic Geo-referenced digital data in Shape format

9.5 Revenue Document Scanning

1. Scanned documents in defined folder structure ( codification guidelines)

2. Metadata in specified format as per codification guidelines in .mdb format

3. Printouts of the scanned revenue documents in binding- 1 copy


68 | P a g e

9.6 Survey

1. Primary Monumentation establishment and verification form in standard format

2. Secondary Monumentation establishment and verification form in standard format

3. Tertiary Monumentation establishment and verification form in standard format

4. Photographs of the monuments in softcopy

5. Post processing report of the DGPS points

6. GPS coordinates, defined codes and elevation in .xls

7. ETS 8. Raw output in CSV format 9. Digitized parcel in shape format 10. Traverse details if applicable with closing error (to be decided) 11. Field book/sketch 12. Image

(1) Geo-referenced PAN sharpened Ortho-Rectified image- scene wise

(2) DEM (format- .grd)

9.7 Deliverables in Soft Copy Formats

1. Digitized maps (Original Mussavies) of every village along with symbol library on point/Line/ Polygon layer on CD media as .shp, geotiff .gdb file & pdf file. 2. Digitized maps (Mussavies updated as on date) on CD media as .shp & .gdb file 3. Data base of digitized maps as database file. 4. Scanned final maps with complete indexing on CD media.

5. Ortho rectified Geo-referenced satellite Imagery(HRSI) in geotiff

6. Un-rectified Digital village data in approved format

7. Un-rectified Digital Mosaicked Tehsil data in approved format

8. Un-rectified Digital Mosaicked District data in approved format

9.8 Deliverables in Hard Copy Formats

The following printouts (1:1 scale) for validation / final submission.

a. First printout of scanned Original map on 75 micron transparency for validation

b. Second draft printout of corrected and updated digitized Mussavies at 75 micron

transparency.

c. Third printout of final updated and verified digitized Mussavies (3 Set) on 75 micron matt

polyester paper.

d. User Manual comprising of Software functionality (HARLIS,HARIS, Bhu-Naksha& DMRS),

And data generation / updation methodology

Digitized maps should be linked with RoR which is already computerized and available in

Client Server DLR/NIC.

Operationalization of the Document Management Software ( For easy indexing and retrieval

of scanned documents along with drawing of land parcel with dimension (from map and RoR)

attribute information, neighborhood details and printing the maps and data on existing

HARLIS & Bhu-Naksha of DLR/NIC.


69 | P a g e

9.9 Features Deliverables

Field description of POLYGON features Shape in table (aDDTTTVVVVV.shp/.gdb)

S. No. Field/Item

Name Field/Item

Width Field/Item Description

1 AREA_METER Double Polygon area in Sq. Meter

2 AREA_KARAM Double Polygon area in Sq. Karam

3 POLY_TYPE Text, 254 Information of the Khasra type (As per the specified in Annexure-10)

4 POLY_CODE Text, 254 Code of the Khasra type (As per the specified in Annexure-10)

5 DIST_NAME Text, 254 District name in English as per LRD

6 DIST_CODE Text, 254 Two digit district code as per LRD (DD)

7 TEH_NAME Text, 254 Tehsil name in English as per LRD

8 TEH_CODE Text, 254 Three digit tehsil code as per LRD (TTT)

9 VILL_NAME Text, 254 Village name in English as per Musavi

10 HADBAST_NO Text, 254 Hadbast number in English

11 NV_CODE Text, 254 National village code as per LRD (VVVVV)

12 MUSAVI_NO Text, 254 Two digit musavi number as per Musavi code (NN)

13 MURRBA_NO Text, 254 Murrba number as per given in Mussavies

14 KHASRA_NO Text, 254 Original parcel (Khasra) number in English

15 BADA_NO Text, 254 Bada number as per given in Mussavies

16 KHASRA_RoR Text, 254 Original parcel (Khasra) number in English given in RoR (Jamabandi)

17 UNIQUE_ID Text, 254 A unique ID for joining RoR data (Ex. DDTTTVVVVV Murrba No. & Original Khasra No. from RoR)

18 KHASRA_ERR Text, 254 Comments about parcel no. Joined Killa, Duplicate and Missing etc.

19 REMARK Text, 254 Comments regarding the feature of polygon

Field description of LINE features Shape in table (lDDTTTVVVVV.shp/.gdb)

S. No. Field/Item

Name Field/Item






5 VILL _NAME Text, 254 Village name in English as per Musavi



8 MUSCODE01 Text, 254 Two digit musavi number as per Musavi code (NN)

9 MUSCODE02 Text, 254 Two digit musavi number for common line in adjoining Mussavies

10 LEN_METER Double Line length in Meter

11 LEN_KARAM Double Line length in Karam

12 LEN_REAL Text, 254 Original line length displayed in musavi

13 LIN_TYPE Text, 254 Code of the line type (As per the specified in Annexure-10)

14 LINCODE01 Text, 254 Code of the line type (As per the specified in Annexure-10)


70 | P a g e

15 LINCODE02 Text, 254 Same Code of the line type for common line in adjoining

feature (As per the specified in Annexure-10)

16 OTHER Text, 254 Code of the line type (As per the specified in Annexure-10)

17 REMARK Text, 254

Comments regarding the feature of Line

Field description of POINT features Shape in table (pDDTTTVVVVV.shp/.gdb)

S. No. Field/Item Name Field/Item






5 VILL_NAME Text, 254 Village name in English as per Musavi




9 BURJI_CODE Text, 254 For Badi Burji (Seheda) = BB001 to N number, For Choti Burji = CB001 to N numbers.

10 SYM_TYPE Text, 254 Information of the symbol type (As per the specified in Annexure-10)

11 SYM_CODE Text, 254 Code of the symbol type (As per the specified in Annexure-10)

12 SYM_SIZE Text, 254 Size of Symbol

13 SYM_ANGLE Text, 254 Angle of Symbol

14 REMARK Text, 254 Comments regarding the feature of symbol

Field description of TEXT (POINT) Shape in table (tDDTTTVVVVV.shp/.gdb)

S. No. Field/Item Name Field/Item






5 VILL _NAME Text, 254 Village name in English as per Musavi




9 MURRBA_NO Text, 254 Murrba number as per given in Mussavies

10 PR_KHAS_NO Text, 254 Parent Khasra no. consists of Main Khasra no and its own no.

11 TXT_TYPE Text, 254 Information of the symbol type (As per the specified in Annexure-10)

12 TXT_CODE Text, 254 Code of the symbol type (As per the specified in Annexure-10)

13 TXT_SIZE Text, 254 Size of Symbol


71 | P a g e

14 TXT_ANGLE Text, 254 Angle of Symbol

15 TXT_HINDI Text, 254 All text given in Mussavies Like Reference text, Patwari Note and other outside & inside of Village Boundary text

16 TXT_ENG Text, 254 All text given in Mussavies Like Reference text, Patwari Note and other outside & inside of Village Boundary text

17 REMARK Text, 254 Comments regarding the feature of symbol

Every feature type (Poly_Type, Lin_Type and Sym_Type) described in above tables (contents 9.9)

along with their field/Item name should be given in individual layer and also gives village

boundary polygon.

Above list of feature in point, line, polygon feature class may extend based on the features

encountered during the project process. Vendors should inform HARSAC/DLR if any

additional feature is identified.

(Note: - The assigned symbol library will be followed throughout the project for three different

features i.e. line, polygon, point. ANNEXURE-23, ANNEXURE-24, ANNEXURE-25).

10. List of personnel associated from different organization for preparation of SDD (ANNEXURE-

27).


72 | P a g e

Annexure-1- Description of Measurement units

Length Measure as per Land Record Manual

Unit 66" Karam (Meter)

99" karam or Gatha (Meters)

60" Karam (Meters)

57.5" Karam (Meters)

57.157" karam or Gatha (Meters)

54" karam (Meters)

Karam 1.6764 2.5146 1.524 1.4605 1.4517878 1.3716

3.3528 5.0292 3.048 2.921 2.9035756 2.7432

5.0292 7.5438 4.572 4.3815 4.3553634 4.1148

6.7056 10.0584 6.096 5.842 5.8071512 5.4864

8.382 12.573 7.62 7.3025 7.258939 6.858

10.0584 15.0876 9.144 8.763 8.71077268 8.2296

11.7348 17.6022 10.668 10.2235 10.1625146 9.6012

13.4112 20.1168 12.192 11.684 11.6143024 10.9728

15.0876 22.6314 13.716 13.1445 13.0660902 12.3444

16.764 25.146 15.24 14.605 14.517878 13.716

33.528 50.292 30.48 29.21 29.035756 27.432

50.292 75.438 45.72 43.815 43.553634 41.148

60.3504 90.5256 54.864 52.578 52.2643608 49.3776

67.056 100.584 60.9 58.42 58.071512 54.864

83.82 125.73 76.2 73.25 72.58939 68.58

100.584 150.876 91.44 87.63 87.107268 82.296

117.348 176.022 106.68 102.235 101.625146 96.012

134.112 201.168 121.92 116.84 116.143024 109.728

150.876 226.314 137.16 131.445 130.660902 123.444

167.64 251.46 152.4 146.05 145.17878 137.16

301.752 452.628 274.32 262.89 261.321804 246.888

335.28 502.92 304.8 292.1 290.35756 274.32

Area Measure

66" Karam (Sq. meters)

60"Karam (Sq. Meter)

57.5" Karam (Sq. Meters)

54" Karam (Sq. Meters)

Sarsahis 2.81031696 2.322576 2.13306025 1.88128656

5.62063392 4.645152 4.2661205 3.76257312

8.43095088 6.967728 6.39918075 5.64385968

11.24126784 9.290304 8.532241 7.52514624

14.05515848 11.61288 10.66530125 9.4064328

16.86190176 13.935456 12.7983625 11.28771936

19.67221872 16.258032 14.93142175 13.16900592

22.48253568 18.580608 17.064482 15.05029248

Marla 25.29285264 20.903184 19.19754225 16.93157904

50.58570528 41.806368 38.3950845 33.86315808

75.87855792 62.709552 57.59262675 50.79473712

101.1714106 83.612736 76.790169 67.72631616

126.4642632 104.51592 95.98771125 84.6577952

151.7571158 125.419104 115.1852535 101.5894742


73 | P a g e

177.0499685 146.322288 134.3827958 118.5210533

202.3428211 167.225472 153.580338 135.4526323

227.6356774 188.128656 172.7778803 152.3832114

252.9285264 209.03184 191.9754225 169.3157904

278.221379 229.935024 211.1729648 186.2473694

303.5142317 250.838208 230.370507 203.1789485

328.8070843 271.741392 249.5680493 220.1105275

354.099937 292.644576 268.7655915 237.0421066

379.3927896 313.54776 287.9631338 253.9736856

404.6856422 334.450944 307.160676 270.9052646

429.9784949 355.354128 326.3582183 287.8368437

455.2713475 376.257312 345.5557605 304.7684227

480.5642002 397.160496 364.7533028 321.7000018

Kanal 505.8570528 418.06368 383.950845 338.6315808

1011.714106 836.12736 767.90169 677.2631616

1517.571158 1254.19104 1151.852535 1015.894742

2023.428211 1672.25472 1535.80338 1354.526328

2529.285264 2090.3184 1919.754225 1693.157904

3035.142317 2508.38208 2303.70507 2031.789485

3540.99937 2926.44576 2687.655915 2370.421066

Ghumaos 4046.856422 3344.50944 3071.60676 2709.052646

8093.712845 6689.01888 6143.21352 5418.105293

12140.56927 10033.52832 9214.82028 8127.157939

16187.42569 13378.03776 12286.42704 10836.21059

20234.28211 16722.5472 15358.0338 13545.26323

24281.13853 20067.05664 18429.64056 16254.31588

28327.99496 23411.56608 21501.24732 18963.36852

32374.85138 26756.07552 24572.85408 21672.42117

36421.7078 30100.58496 27644.46084 24381.47382

404068.5642 33445.0944 30716.0676 27090.52646

Bigha Measure

99" Gatha (Sq. Meters)

60" Karam (Sq. Meters)

57.157" Karam or Gatha Sq. Meters

Biswansi 6.32321316 2.322576 2.1076878

Biswansi 12.64642632 4.645152 4.2153756

18.96963948 6.967728 4.21553756

25.29285264 9.290304 8.4307512

31.6160658 11.61288 10.53843

37.93927896 13.935456 12.6461268

44.26249212 16.258032 14.7538146

50.58570528 18.580608 14.7538146

56.90891844 20.903184 18.9691902

63.2321316 23.22576 21.076878

69.55534476 25.548336 23.1845658


74 | P a g e

75.87855792 27.870912 25.2922536

82.20177108 30.193488 27.3999414

88.52498424 32.516064 29.507629

94.8481974 34.83864 31.615317

101.1714106 37.161216 33.7230048

107.4946237 39.483792 37.9383804

113.8178369 41.806368 37.9383804

120.14105 44.128944 40.0460682

Biswa 126.4642632 46.45152 42.153756

252.9285264 92.90304 84.307512

252.9285264 92.90304 84.307512

379.3927896 139.35456 126.461268

505.8570528 185.806 168.615024

632.321316 232.2576 210.76878

758.7855792 278.70912 252.922536

885.2498424 325.16064 295.076292

1011.714106 371.61216 337.230048

1138.178369 418.06368 379.383804

1264.642632 464.5152 421.53756

1391.106895 510.96672 463.691316

1517.571158 557.41824 505.845072

1644.035422 3.86976 547.998828

1770.499685 650.3218 590.152584

1896.963948 696.7728 632.30634

2023.428211 743.22432 674.460096

2149.892474 789.67584 716.613852

2276.356738 836.12736 758.763608

2402.821001 882.57888 800.921364

Bigha 2529.285264 929.0304 843.07512

5059.570528 1858.0608 1686.15024

7587.855792 2787.09128 2529.22536

10117.14106 3716.1216 3372.30048

12646.42632 4645.152 4215.37568

15175.71168 5574.1842 5038.45072

17704.99685 6503.2128 5901.52584

20234.28211 7432.2432 6744.60096

22763.56738 8361.2736 7587.67608

25292.85264 9298.304 8430.751264


75 | P a g e

Annexure -2- Format for Final Authorized vendors representative

Format for Final Authorized vendors representative

S.no Name of

Representative

Project

Designation

Company

Name

Company

Address

Mobile

No.

Responsibility Remarks

Annexure-3-Format of Identity card

The authorized representative of the Vendor shall be provided the Identity card for the Map

collections and field work.

Format of Identity Card

Project : Modernization of Land Record for 20 District of Haryana

Name :

Project Designation:

Company Name: _________________________________________________________

Address: _________________________________________ Mobile: _____________________

Responsibility:________________________________________________________________

Signature Signature

Vendor Project Coordinator HARSAC Project Coordinator

Photo


76 | P a g e

Annexxure-4-List of District level contacts

The DLR shall submit the List of the Authorized representative at District level, Tehsil wise with

contact details

S.no Name of

Tehsildar

Contact

Details with

Mobile no.

Name of

Kanungo

Contact

Details with

Mobile no.

Authorized

Rep. Name

Designation Contact

Details with

Mobile no.

Responsibility Remarks

Annexxure-5-HARSAC’s authorized representatives at district level

The HARSAC shall submit the List of the Authorized representative at District level, Tehsil wise with

contact details

S.no Authorized Rep. Name Designation Contact Details with Mobile no. Responsibility Remarks


77 | P a g e

Annexue-6-Map collection Format

Logo vendor

LOGO

DLR/ HARSAC

Project: Modernization of Land Record under NLRMP, Haryana

Work Order No:

District Name Place

Tehsil Name Village Name / Hadbast No.

Tehsildar Contact

Number

Kanungo Contact Number

DLR Authorized

Representative Contact

Name of vendor

Representative & Contact No.

HARSAC Representative contact No

S.No. Document

Type

Sheet

No.

Quantity

Maps

Date of

Issue

Signature

Vendor Rep.

Signature

DLR Rep.

Remarks

(Specify the condition of

each map )

Mussavies

Mussavies

Mussavies

Mussavies

Mussavies

Mussavies


78 | P a g e

Annexue-7- Format for the submission of the Printed scanned Mussavies.

LOGO vendor LOGO

HARSAC


Work Order No:

District Name Place

Tehsil Name Name of vendor

Representative &

Contact No.

Village Name /

Hadbast No.

HARSAC

Representative

and contact No.

S.No. Document

Type**

Sheet

No.

Quantity Date of

Submission

Signature

Vendor

Rep.

Signature

Reviewing

Officer

(HARSAC/DLR)

Remarks

(No. of CD

comprising

scanned

map )

* *Scanned Mussavies in tiff format and printout on 75 micron Polyester sheet Note: Validation/ Verification of the scanned Mussavies shall be conducted by reviewing officer with 7 days (Check reasonability of verification) of the submission Annexure-8- Format of the Acceptance Certificate

LOGO vendor LOGO

HARSAC / DLR

This is certified that the following Mussavies sheet ( Hard copy and soft copy) has been found as per

the technical specification and has been accepted as the final deliverable

District Name Tehsil Name

Village Name /

Hadbast

Sheet No.

CD No.:

Signature

HARSAC / DLR-H

* The Acceptance of the scanned Mussavies and its print out shall be conducted by HARSAC/ DLR within 7 days of submission


79 | P a g e

Annexure-9- Format for Scanned Musavi Updation

LOGO

DLR/ HARSAC


Work Order Number

Date of Submission Updation date**

District Name


Tehsildar Name &

Contact Number

Kanungo Name & Contact

Number

DLR Authorized

Representative Contact

Name of vendor

Representative & Contact

No.

HARSAC Rep Name &

contact No

S.No. Document

Type

Sheet

No.

Quantity

Maps

Date of

Submission

Signature

Vendor Rep.

Signature

DLR-H

Rep.

Remarks

Signature Vendor Rep. Signature DLR-H Rep.

Note :

Mutation up to the date of the Updation of the Mussavies shall be considered during the integration

of RoR data with spatial database. After that any updation shall be taken during AMC.

Patwari/Kanungo shall ensure updated musavi to be provided to the respective vendor within 7 days

of submission.


80 | P a g e

Annexure-10: Code for Polygon Feature

S.

No.

POLY_TYPE

POLY_CODE

REMARK

1 Khasra 00051

2 Plot 000511

3 Pond (Johar) 00052

4 UpranJohar 000521

5 Play Ground (Gora) 00053

6 Charagah

000531

7 Inhabited Area (Abadi Area) 00054

8 River 00055

9 Drain 000551

10 Canal 000552

11 Water Course(Khal) 000553

12 Road 00056

13 Cart Track (Kacche Raste) 000561

14 Rail 00057

15 Other 555555

Code for Point Feature

S.No. SYM_TYPE SYM_CODE REMARK

1 Badi Burji 00061

2 Choti Burji 000611

3 Railway Station 00062

4 Inhabited Area 00063

5 School / College 000631

6 Industry 000632

7 PanchayatGhar 000633

8 Rest House 000634

9 Charagah 000635

10 Garden 0006351

11 Public Toilet 000636

12 GadhaKhad 000637

13 Water Works 000638

14 Power House 000639

15 Temple 00064

16 Masjid 000641

17 Gurudwara 000642

18 Church 000643

19 Cremation Ground 00065


81 | P a g e

20 Kabristan 000651

21 Hadarodi 000652

22 Tube Well 00066

23 Well 000661

24 Hospital / Dispensary 00067

25 Veterinary Hospital 000671

26 Police Post / Police Station 00068

27 Hill / Hillock 00069

28 Other 666666

Code for Text

S. No.

TXT_TYPE

TXT_CODE

REMARK

1 Reference Text 00071

2 Murrba No 00072 For printing purpose

3 Patwari/Kanungo Note 00073 For printing purpose

4 Transportation text 00074 (Road, Rail, River etc.)

5 Parent no 00075

6 Add joining village name 00076

Other text 77777

Khasra Error Table S. No.

ERROR_TYPE

ERROR_CODE

REMARK

1 Duplicate DUPL

2 Joined Killa JOIN

3 Missing Khasra No. MISS

4 Miscellaneous MISC

Code for Line Feature

S. No.

LIN_TYPE

LINCODE01/ LINCODE02

REMARK

1 Village Boundary 00031

2 Musavi Line 00032

3 Musavi Grid In 000321 Grid Musavi inside of village boundary

4 Musavi Grid 000322

5 Murrba Line 00033

6 Murrba Grid In 000331

7 Murrba Grid 000332

8 Khasra Line 00034


82 | P a g e

9 Khasra Grid In 000341

10 Khasra Grid 000342

11 Plot Line 00035

12 Pond Line 00036 Johar

13 Upran Line 000361 Upran Johar

14 Gora Line 00037 Play Ground& Gora

15 Charagah Line

000371

16 Abadi Line 00038 Inhabited Area

17 River Line 00039

18 Drain Line 000391

19 Canal Line 000392

20 Khal Line 000393 Water Course

21 Road Line 00040

22 Cart Track Line 000401 Kacche Raste

23 Rail Line 00041

24 Reference Line 00042

25 Other Line 444444

Any other feature found during the process vendor should inform HARSAC about it.


83 | P a g e

Annexure-11(A)- Cadastral Map vs. Rectified Worldview data

Village:...................,Tehsil...................,District......................

GCP

ID

Ortho Rectified Image

Coordinate

(World view data)

Geo-Reference Vector

(Village/Cadastral Maps) Residual Error

X Y X Y X Y

1

2

3

4

5

6

7

8

9

10

11

Scale (X,Y) = Skew (degrees) = Rotation (degrees) = Translation = RMS Error (input, output) =

Affine X = Ax + By + C

Y = Dx + Ey + F A = B = C =

D = E = F =


84 | P a g e

Annexure-11(B)- Area Validation of individual parcel from different land records.

Annexure-11(C)- Burji Length Verification with adjacent village.

Submission Date: Receiving Date:

Village/HB No. Tehsil District Haryana *(Area should be in Kanal & Marla)

1 9 10 11 12 13 14

Killa No. K M Killa No. K M Killa No. K M Killa No. K M Killa No. K M Killa No. K M Killa No. K M

Prepared & Checked By Patwari Validated By Kanungo Verified By C.R.O. Prepared & Checked By Vendor's Field Staff Validated By Vendor's Revenue Expert Verified By Project Manager

Name: Name: Name: Name: Name: Name:

Mobile: Mobile: Mobile: Mobile: Mobile: Mobile:

Note- 1.) Column No. 1,2,3,and 14 are to be filled by the Vendor. 2.) Column No. 4 to 13 are to be filled by Patwaries and checked by concerned Kanungo. 3.) Vendor will have to give final observations with refrance to revenue requirment on

complete village. 4.) Respective Vendor will have to submit the Original copy with their Remarks.

Area

Comparisio

n (Mention

Column No.

Only for e.i.

2,3 & 5,6)

Annexure 11-B

Current & Updated

Area

Mutation nos

involves

where Area

Differs (If

Any)

Reason for

difference in

Area(in Col. 9)

Solution ( AS

per Revenue

System)

Remarks Observation

Incorporated

by vendor

(Y/N)

8

Sr#

Mu

rrab

a N

um

be

r

Computerized RoR Mussavi/Vector Manual Jamabandi

before

computerised

First Jamabandi

After Consolidation

Khasra & Area Verification Report

Misal Haqiyat Field Book

2 3 4 5 6 7

Submission Date: Receiving Date:

Village/HB No. Tehsil District Haryana

2 3 4 5 6 7 8 9

From To

1

2

3

4

5

6

Prepared & Checked By Patwari Validated By Kanungo Verified By C.R.O. Prepared & Checked By Vendor's Field Staff Validated By Vendor's Revenue Expert Verified By Project Manager

Name: Name: Name: Name: Name: Name:

Mobile: Mobile: Mobile: Mobile: Mobile: Mobile:

Annexure 11-C

Reason for difference

in Length

Solution ( AS per Revenue System) Remarks

Note- 1.) Column No. 1 and 9 are to be filled by the Vendor. 2.) Column No. 2 to 8 are to be filled by Patwaries and checked by concerned Kanungo. 3.) Vendor will have to give final observations with refrance to

revenue requirment on complete village. 4.) Respective Vendor will have to submit the Original copy with their Remarks.

Observation

Incorporated

(Y/N)

Sr# Burji Number

1

Length(In Karam) Adjacent Village Name Length(In

Karam)

Difference In

Length (if any)


85 | P a g e

Annexure-12- Format for the Verification of Vector Data

LOGO

DLR/ HARSAC


Work Order Number

Date of Submission

District Name Tehsil Name

Village Name /

HadBast No.

Name of vendor

Representative &

Contact No.

HARSAC Rep Name &

contact No

S.No Deliverable

format

Percentage

of errors

Acceptable

/ Not

Acceptable

Signature of

Approving

Authority

Signature

Of Vendor

representative

Remarks

Note:

Digital data shall be submitted in approved format village wise

Acceptance of the Digital data village wise shall be conducted within 7 days

Mosaicked digital data shall submitted tehsil and district wise


86 | P a g e

Annexure-13- Approval for Executing Mussavies Regeneration Activity

LOGO

DLR/ HARSAC


Work Order No:

District Name Place

Tehsil Name Village Name / HadBast No.

Tehsildar Name &

Contact Number

Kanungo name & Contact

Number

DLR Authorized

Representative Name &

Contact

Name of vendor


No.


S.No. Missing /

Invalid

Musavi

Index. No.

Reason (Mussavies

Unavailable / Poor

Condition/ Old

Consolidation/

Other)

Date of

Regeneration

Activity

Approval

Signature

Vendor

Rep.

Signature

HARSAC /

Dist. Adm./

DLR Rep.

Remarks


87 | P a g e

Annexure-14- ETS Survey Monitoring and Completion for Musavi Regeneration Activity

LOGO

DLR/ HARSAC


Work Order No:

District Name Place


Tehsildar Name & Contact

Number


Number

DLR Authorized


Contact

Name of vendor


No.


S.No. Mussavies

Index. No.

(Regenerated

Mussavies)

Suggested

Date for

Survey By

Vendor

Survey

Execution

Date

Decided By

Authorized

Signatory

Survey

Execution

initiation

date

Survey

Completion

Date

Signature

HARSAC /

Dist.

Adm./ DLR

Rep.

Remarks


88 | P a g e

Annexure-15- Tehsil Level Data Verification

LOGO

DLR/ HARSAC

District Name Place

Tehsil Name Name of vendor


HARSAC / District

Administration / DLR

Representative and contact No.

Certificate of Approval of Taluk Level Data (Cadastral / Village Boundary)

Average Accuracy % of Length

Average Accuracy % of Area

Edge Matching Status

Annexure-16-District Level Data Verification

LOGO

DLR/ HARSAC

District Name Place

Name of vendor


HARSAC / District

Administration / DLR

Representative and contact

No.

Certificate of Approval of Taluk Level Data (Cadastral / Village Boundary)

Average Accuracy % of Length

Average Accuracy % of Area

Edge Matching Status


89 | P a g e

Annexure-17- QC/QA Format for DGPS Data Processing

LOGO

DLR/ HARSAC


Work Order No:

District Name Place



Number


Number

DLR Authorized


Contact

Name of vendor



Primary / secondary / tertiary / code

Sl.No. DESCRIPTION CHECK REMARKS

1 Stored data downloaded properly

2 Downloaded data supported format?

3 Selection of height of receiver, point numbering, receiver

type selected as per field input

4 Geodetic-network adjustment completed

5 Post – processing reports acceptable

6 Results stored in specified output format

Vendor Operator Name Certified by Date/Time


90 | P a g e

Annexure-18- Check list before starting of DGPS reading

LOGO

DLR/ HARSAC


Work Order No:

District Name Place



Number


Number

DLR Authorized


Contact

Name of vendor



Primary / secondary / tertiary / code

Sl.No. DESCRIPTION CHECK

Correct/Incorrect

REMARKS

1 Monumentation done as per guidelines

2 Centering over nail

3 Leveling using circular level

4 Slant Height of receiver measured with measuring

tape?

5 Month/Date/Time of observation noted on field book.

6 Batteries fully charged/supplying power to receiver

7 GCP location free from HT lines/communication lines,

towers/multi path error sources.

8 Receiver parameters elevation mask/PDOP settled

9 Data captured stored

10 Proper field sketch prepared

Signature of Vendor Representative Signature of DLR/ HARSAC Representative Date/Time


91 | P a g e

Annexure-19- Control Point Codification.

The code structure for control points, for unique identification of each Primary / Secondary / Teratiary or

Auxiliary Control point will be as below:

1) Primary Control Point (Total Count 121):

• A 5-digit Sequential No.

• Range 10001 – 10121

• The first digit is used as Prefix differentiator of Control Point Type. For Primary Control

Point it is “1”.

Ex. 10003, (“1”in id 10003 signifies that the Control point is Primary control Point)

2) Secondary Control (Total Count Approx. 575):

• A 5-digit Sequential No.

• Range 20001 – 20575

• The first digit is used as Prefix differentiator of Control Point Type. For Secondary

Control Point it is “2”.

Ex. 20003, (“2” in id 20003 signifies that the Control point is Secondary control Point)

3) Tertiary / Auxiliary Control:

• A 7-digit Code.

• First Digit is Prefix differentiator for Tertiary Control point - 3 and for Auxiliary Control

Point - 4

• Next 2 Digits will be Census District Code. Ex. “01” for Tertiary point in Ambala

District.

• Next 4 Digits will be a sequence number ranging from 0000 – 9999.

3/4 XX XXXX

Tertiary / Auxiliary Point District Code Sequential Number

Ex, Tertiary – 3010001, Auxiliary - 4010001


92 | P a g e

Annexure-20- Standards for horizontal accuracy

SR.NO Map Scale Planimetric Accuracy (x or y)

(Limiting rms error in meters)

1 1:250,000 62.50

2 1:125,000 31.25

3 1:50,000 12.50

4 1:25,000 6.25

5 1:12,500 3.12

6 1:10,000 2.50

7 1:4,000 1.00

8 1:1500 0.25


93 | P a g e

Annexure-21- Submission of DGPS Report of Primary / Secondary /Tertiary Control Point


District Name Place

Tehsil Name Village Name

Name of DGPS Surveyor & Contact

No.

Name HARSAC / DLR

Representative & Contact No

Instrument Code Session No.

Name of the Station (Serial No. specified

in the Instrument Automatically)

Primary / Secondary / Tertiary /

code Under DGPS survey

Height of the Antenna (At least Three Time with mm accuracy)

1st 2nd 3rd 4th 5th

Description of Station (1. Specify Name of Building /

office/School/)

(2. Approach)

(3. Condition of the Monument )

Sketch of the Location

Details of the adjoining Location id Location Name


94 | P a g e

stations undergoing DGPS

observation

Location id Location Name




Status of GPS Observation

Starting Date Completion Date

Start Time (hh,mm)

Closing Time (hh,mm)

Satellite Observation Status

Hours No. of

Satellite

PDOP Hours

No. of

Satellite

PDOP Hours

No. of

Satellite

PDOP

2 28 54

4 30

56

6 32 58

8 34 60

10 36 62

12 38 64

14 40 66

16 42 68

18 44 70

20 46

22 48

24 50

26 52

Remarks: (Specify Weather condition its duration and start time and end Time, Condition of instrument / Observation breaks if

any along with its reason, any water logging in surrounding area if any also show in the sketch of the location)

54

Signature Signature

Name of the HARSAC/ DLR

representative

Name of the Vendor

representative

Remarks: The survey Marker has been installed and surveyed it is conformed.


95 | P a g e

Sl.

No.

DESCRIPTION Yes /No REMARKS

1 Was the correct site occupied? (Check photo evidence if any)

2 Centering of Instrument over Mark over Steel

Plate

3 Leveling using circular level

4 Slant Height of receiver measured with

measuring tape?

5 Was it checked by another person

6 Month/Date/Time of observation noted on

field book.

7 Batteries fully charged/supplying power to

receiver

8 Height of the instrument entered in

instrument

9 Proper field sketch prepared

10 Data captured stored

11 Satellite status recorded

12 Check system status via electronic bulletin

board or information service regularly

13 Power / connection problem (specify if any

along with time) (Mentioned the start time of the observation in Observation

sheet after rectification)

14 Weather Condition (Thick cloudy /

showering/ heavy Rain/ Thundering specify in

detail if any) In such case specify the duration

and time of such event in Remarks

15 Is there any evidence to suggest that the data

is in any way unreliable, considering water


96 | P a g e

logging condition in surrounding area,

Weather condition, interrupted power

supply, displacement of instrument, Damage

in instrument, etc. if yes specify it

16 In above case weather communicated at

other observation station

17 Equipment checked as per the checklist

before leaving the site

Signature of Vendor Representative Signature of DLR/ HARSAC Representative Date/Time

Remarks: The survey Marker has been installed and surveyed it is conformed.


97 | P a g e

Annexure-22- Certificate of Acceptance of DGPS Report of Primary / Secondary Tertiary Control Point

1

2

3

Name of Tehsil / Village

4

5

6

Monument Specification

As per the approved drawing

Name of Authorized person / Contact

Person at Tehsil / Village

Contact Number

Name of Project

RemarksMonumentation Site Inspection Detail

Monument Specification

Photograph Taken ( Panormic View) ( specify Number/ serial No. of Photograph in Camera)

Name of Department

Name of Building

Schematic Sketch of the Location/ Site

Contact Details of Contact / Authorized person

Designation

Date of Installation

From To

Name of District

Signature of Surveyor

Ramtech Software Solution Pvt Ltd

Signature of Authorized representative

(Name of department)

Alternate Contact Number

Establishment of Primary Control Monumentation

Yes / No

Name of the

Surveyor

Moderanization of Land Record for 20 District of Haryana

Locational Information

Primary Control Point Code:


98 | P a g e

Annexure-23

Color description of LINE feature

S. No. LIN_TYPE Color in RGB Line Type Line Width Remark

1 Village Boundary R-0, G-0, B-0 Continuous 2.5

2 Musavi Line R-248, G-93, B-79 Continuous 2.0

3 Musavi Grid In R-248, G-93, B-79 Continuous 2.0

4 Musavi Grid R-248, G-93, B-79 Continuous 2.0

5 Murrba Line R-248, G-93, B-79 Continuous 2.0

6 Murrba Grid In R-248, G-93, B-79 Continuous 2.0

7 Murrba Grid R-248, G-93, B-79 Continuous 2.0

8 Khasra Line R-0, G-0, B-0 Continuous 1.0

9 Khasra Grid In R-165, G-103, B-82 Dashed 1.0

10 Khasra Grid R-165, G-103, B-82 Dashed 1.0

11 Plot Line R-0, G-0, B-0 Continuous 1.0

12 Pond Line R-0, G-0, B-0 Continuous 1.0

13 Upran Line R-0, G-0, B-0 Continuous 1.0

14 Gora Line R-0, G-0, B-0 Continuous 1.0

15 Charagah Line R-0, G-0, B-0 Continuous 1.0

16 Abadi Line R-0, G-0, B-0 Continuous 1.0

17 River Line R-0, G-0, B-0 Continuous 1.0

18 Drain Line R-0, G-0, B-0 Continuous 1.0

19 Canal Line R-0, G-0, B-0 Continuous 1.0

20 Khal Line R-0, G-0, B-0 Continuous 1.0

21 Road Line R-0, G-0, B-0 Continuous 1.0

22 Cart Track Line R-0, G-0, B-0 Continuous 1.0

23 Rail Line R-0, G-0, B-0 Continuous 1.0

24 Reference Line R-0, G-0, B-0 Dashed 1.0

25 Other Line R-0, G-0, B-0 Continuous 1.0


99 | P a g e

Annexure-24 Color description of POLYGON features

S. No.

POLY_TYPE Color in RGB OUTER_LINE_TYPE OUTER_LINE_WIDTH Remark

1 Khasra R-255, G-237, B-255 Continuous 1.0

2 Plot R-255, G-190, B-190 Continuous 1.0

3 Pond (Johar) R-0, G-93, B-127 Continuous 1.0

4 UpranJohar R-19, G-76, B-0 Continuous 1.0

5 Play Ground (Gora) R-255, G-237, B-255 Continuous 1.0

6 Charagah R-255, G-237, B-255 Continuous 1.0

7 Inhabited Area (Abadi Area) R-255, G-191, B-0 Continuous 1.0

8 River R-0, G-127, B-255 Continuous 1.0

9 Drain R-0, G-127, B-255 Continuous 1.0

10 Canal R-0, G-127, B-255 Continuous 1.0

11 Water Course(Khal) R-0, G-127, B-255 Continuous 1.0

12 Road R-255, G-0, B-0 Continuous 1.0

13 Cart Track (Kacche Raste) R-255, G-0, B-0 Continuous 1.0

14 Rail R-255, G-237, B-255 Continuous 1.0

15 Other R-255, G-237, B-255 Continuous 1.0


100 | P a g e

Annexure-25 Color description of POINT features

S. No.

SYM_TYPE Fill Color in RGB

Outer Line Type

Outer Line Type Color

Outer Line Type

Width

Remark

1 Badi Burji R-255, G-0, B-0

Continuous R-0, G-0, B-0 1.5 Symbol's Shape as per Template

2 Choti Burji Hollow Continuous R-0, G-0, B-0 1.2 Symbol's Shape as per Template

3 Railway Station Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

4 Inhabited Area Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

5 School / College Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

6 Industry Hollow Continuous R-255, G-0, B-0 1.0 Symbol's Shape as per Template

7 PanchayatGhar Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

8 Rest House Hollow Continuous R-0, G-0, B-127 1.0 Symbol's Shape as per Template

9 Charagah Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

10 Garden R-0, G-76, B-0


11 Public Toilet Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

12 GadhaKhad Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

13 Water Works Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

14 Power House Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

15 Temple Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

16 Masjid Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

17 Gurudwara Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

18 Church Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

19 Cremation Ground Hollow Continuous R-255, G-0, B-0 1.0 Symbol's Shape as per Template

20 Kabristan Hollow Continuous R-255, G-0, B-0 1.0 Symbol's Shape as per Template

21 Hadarodi Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

22 Tube Well Hollow Continuous R-0, G-0, B-255 1.0 Symbol's Shape as per Template

23 Well Hollow Continuous R-0, G-0, B-255 1.0 Symbol's Shape as per Template

24 Hospital / Dispensary Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

25 Veterinary Hospital Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template

26 Police Post / Police Station

R-255,G-0,B-0 /R-0, G-0, B-255


27 Hill / Hillock Hollow Continuous R-0, G-76, B-38 1.0 Symbol's Shape as per Template

28 Other Hollow Continuous R-0, G-0, B-0 1.0 Symbol's Shape as per Template


101 | P a g e

Symbolization for Mussavies

Note: More Symbols may be added as per DLR Requirement.


102 | P a g e

Annexure-26-Format for primary information and MIS.

Salam Min Distinct Min

Numbers

Acre Kanal Marla

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

Tehsil/Subte

hsil

Village Name in

English

(spelling should

be proper )

Village

Name in

Hindi

Hadbast

Number

NVCODETehsil Code

(As per

HALRIS)

Sr. No. Total No. of parcels (Kitte)Patwari

Name

Mobile

Number

Kanungo

Name

Mobile

Number

Area in acresDistrict

Available in

Recordroom

Not

Available in

Recordroom

Collected Remaining Scanned Indexed Digitized Printed

Original

19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

Date

on w

hic

h

RoR

data

copie

d a

t

HA

RS

AC

RO

R d

ata

updating

sta

tus/d

ate

upto

RoR

is u

pdate

d

Usin

g H

ALR

IS

Tota

l N

o.

of

Big

Siz

e S

hedha

Un-c

onsole

d

No.

of

parc

el

Surv

ey-r

e

surv

ey r

equired

by E

lectr

onic

s

tota

l S

tation -

ET

S/D

iffe

rential

Glo

bal P

ositio

n

Syste

m-D

GP

S

Surv

ey a

rea

may g

ive in

acre

s v

illage

Tota

l N

o.

of

field

books

Tota

l N

o.

of

Sm

all

Siz

e

Shedha

Any o

ther

info

rmation

rela

ted t

o t

his

pro

ject

Tota

l N

o.

of

duple

x p

ages in

field

book

Tota

l N

o.

of

Mis

ale

Hakiy

at

books

Tota

l N

o.

of

duple

x p

ages in

Mis

ale

Hakiy

at

books

Date

upto

whic

h

RoR

data

Colle

cte

d

Total Number of Mussavies

Sr. No. District Tehsil/Subtehsil Year Book

Number

Total No. of

Pages

Any other

information

related to this

project

1 2 3 4 5 6 7

Registered Deed Details

Sr. No. District Tehsil/Subteh

sil

Village Name Jamabandi

Year

Book

Number

Total No. of

Simplex

Pages

Any other

information

related to this

project

1 2 3 4 5 6 7 8

Jamabandi Details


103 | P a g e

Annexure-27-List of the personnel associated from different organization for preparation of SDD.

Revenue & Disaster Management Department

1. Sh. Raj Kumar, FCR 2. Sh. Pankaj Yadav, DLR 3. Mr. K.L. Sharma, Astt. Director, DLR Office 4. Mr. RC Sharma, HCS Retd.

A. Haryana Space Applications Centre (HARSAC) 1. Sh. P.K. Das, FC S&T and Chairman HARSAC 2. Sh. Anurag Agarwal, Director HARSAC 3. Dr. R.S Hooda, Chief Scientist HARSAC 4. Dr. Sultan Singh, Sr. Scientist, HARSAC ([email protected]) 5. Mr. Jogender Panghal, HARSAC (SSA) ([email protected]) 6. Mr. Ankur Sharma, HARSAC (SSA) ([email protected]) 7. Mr. S.N. Nandy, HARSAC (SSA) 8. All Research Associate (R.A.), Project Fellow (P.F.) & Project Assistant (P.A.)

B. National Remote Sensing Centre (NRSC) 1. Dr. S. S. Rao, Scientist-SG, RRSC, NRSC 2. Dr. Venugopsal, Scientist-SG, Head of Urban Division, NRSC

C. National Informatics Centre, Haryana State Centre (NIC) 1. Mr. Ghan Shyam Bansal, SIO ([email protected]) 2. Mr. Pardeep Kaushal, NIC (GIS Coordinator) ([email protected]) 3. Mr. G.S Saini, NIC (Scientist C) ([email protected]) 4. Mr. Deepak Bhardwaj, NIC (Scientific Officer)([email protected]) 5. Mr. Harish Kumar, NIC/SIT, GIS Programmer

D. Survey of India, Dehradun 1. Mr. T.P.S. Chauhan, Head of Geodetic Data Centre

E. Vendors a. Ramtech

1. Mr. Ashoka Taomar Ramtech (PM), ([email protected]) 2. Mr. G.R. Rohilla, DRO Retd. Ramtech 3. Mrs. Nita Kumari, Ramtech ([email protected]) 4. Mr. Narendra Kashyap, Ramtech ([email protected]) 5. Mr. Kartikeya Tyagi, Ramtech ([email protected])

b. Rolta India 1. Mr. Herambh Kshirsagar, ROLTA ([email protected]) 2. Mr. Rajiv Sehdev, ROLTA ([email protected])

c. PAN India 1. Mr. K.D. Sood, PAN India (DGM) (PM) ([email protected]) 2. Mr. Naresh Agarwal, PAN India (DGM) ([email protected]) 3. Mr. Vinod Kumar Saini, PAN India (Project Coordinator)

([email protected]) d. Infotech

1. Mr. Uday Bhasker Rao, Infotech ([email protected]) 2. Mr. Ram Ambati Infotech (Software Expert) 3. Mr. B. Sreenivasan Rao, Infotech ([email protected])

mailto:[email protected]


104 | P a g e

Modernization of Land Record under NLRMP, Haryana

Doc. Title: Functional Requirement Study

H a r y a n a R e v e n u e D o c u m e n t M a n a g e m e n t & R e t r i e v a l S y s t e m

( H R - D M R S )

D o c u m e n t n o . : H a r y a n a / N L R M P / D L R / F R S - 1 . 4

Prepared By

RAMTeCH Software Solutions Pvt. Ltd.

Reviewed By Approved By

Administrator

Text Box

Annexure:28 FRS for Haryana Revenue Document Management & Retrieval System


105 | P a g e

Document Control:

Version History:

Version

Number

Issue Date Reasons for Change

1.1 02.12.2011 Incorporation of feedback from HARSAC, DLR, NIC

and vendors ( meeting held at 1st Dec 2011)

1.2 19.12.2011 Incorporation of performance related changes

1.3 6.1.2012 Incorporation of feedback after Comments from Harsac

and NIC

1.4 19.1.2012 Incorporation of changes during meeting with NIC &

Harsac at Chandigarh on 12th

Jan 2012 for changing

Desktop application to Intranet application and other

features.

Issued By Issue Date Revision/Version Reason for Issue

RAMTeCH 30.11.2011 1.0 Presentation to user for the feedback

and finalization

RAMTeCH 02.12.2011 1.1 Submission after incorporation of the

feedback at Requirement collection

meeting at HARSAC on 1st December

2011

RAMTeCH 19.12.2011 1.2 Addressed the performance of the

application at state level and district

level

RAMTeCH 6.1.2012 1.3 Address the issues of Login, Security.

RAMTeCH 19.1.2012 1.4 Address the issue of changing desktop

application to intranet application.


106 | P a g e

Table of Contents

TABLE OF CONTENTS ................................................................................ 106

LIST OF FIGURES ................................................................................. 108

LIST OF TABLES .................................................................................. 109

1 INTRODUCTION .................................................................................. 110

1.1 PURPOSE .................................................................................. 110

1.2 SCOPE .................................................................................... 110

1.3 ABBREVIATIONS .......................................................................... 110

1.4 SYSTEM OVERVIEW – .................................................................... 110

1.5 REFERENCES – ............................................................................ 111

2 OVERALL DESCRIPTION ....................................................................... 111

2.1 PRODUCT PERSPECTIVE .................................................................. 111

2.2 PRODUCT FUNCTIONS .................................................................... 111

2.3 USER CHARACTERISTICS ................................................................. 111

2.4 DEPENDENCIES ........................................................................... 111

2.5 CONSTRAINTS AND ASSUMPTIONS ....................................................... 112

3 SPECIFIC REQUIREMENTS ..................................................................... 112

3.1 SYSTEM DESIGN & APPLICATION PLATFORM. ........................................... 112 3.1.1 Application Platform .................................................................................... 112 3.1.2 Database Used ........................................................................................... 112 3.1.3 Application Access ....................................................................................... 112 3.1.4 Storage & Synchronization .............................................................................. 114

3.2 FUNCTIONAL REQUIREMENTS ............................................................ 115 3.2.1 Storage ................................................................................................... 115 3.2.2 Dynamic Retrieval ....................................................................................... 115 3.2.3 Updation ................................................................................................. 115 3.2.4 Printing ................................................................................................... 115 3.2.5 Application Usage Report Generation.................................................................. 116

3.3 DOCUMENT MANAGEMENT AND RETRIEVAL MODULE: .................................. 116 3.3.1 Login Module ............................................................................................ 116

3.3.1.1 Admin Module ............................................................................................................................... 116 3.3.1.2 User & Privilege Module:-............................................................................................................. 116

3.3.1.2.1 Users Level: ............................................................................................................................. 116 3.3.1.2.2 Type of Users: ......................................................................................................................... 117 3.3.1.2.3 Functionality of User: .............................................................................................................. 117 3.3.1.2.4 Privileges ................................................................................................................................. 118 3.3.1.2.5 Password policy ....................................................................................................................... 119

3.3.2 Document Management Module ........................................................................ 120 3.3.2.1 Codification Module ...................................................................................................................... 120

3.3.2.1.1 New entry ................................................................................................................................ 120 3.3.2.1.2 Folder Structure & Meta data creation for Indexing ................................................................ 121 3.3.2.1.3 Folder structure ........................................................................................................................ 121 3.3.2.1.4 Modify Metadata Module- ...................................................................................................... 123 3.3.2.1.5 Metadata: ................................................................................................................................. 125 3.3.2.1.6 Database Indexing ................................................................................................................... 128

3.3.3 Document Retrieval System ............................................................................. 128


107 | P a g e

3.3.3.1 Home Page: .................................................................................................................................... 128 3.3.3.2 Document view .............................................................................................................................. 128 3.3.3.3 Map view ....................................................................................................................................... 130 3.3.3.4 Document Retrieval System Tools ................................................................................................ 130

3.4 NON-FUNCTIONAL REQUIREMENTS ...................................................... 130

3.5 SECURITY................................................................................. 134 3.5.1 Access of the HR-DMS .................................................................................. 134 3.5.2 Windows File & Folder Security ........................................................................ 135 3.5.3 PDF security ............................................................................................. 135 3.5.4 Protection form Virus and Hacking- .................................................................... 135

3.5.4.1 Antivirus policy ............................................................................................................................. 135 3.5.5 Database Security ....................................................................................... 136 3.5.6 Disaster Recovery of database .......................................................................... 136 3.5.7 Backup policy – .......................................................................................... 136 3.5.8 Audit Logs ................................................................................................ 137

RESPONSIBILITY OF STAKE HOLDER ...................................................... 138


108 | P a g e

List of Figures

Figure

No.

Description Page No.

Fig-1 Application Access 10

Fig-2 Storage & Synchronization 11

Fig-3 Flow Diagram for Admin Module 13

Fig-4 Flow Diagram for User Management 14

Fig-5 Flow Diagram of Privileges 15

Fig-6 Codification module 18

Fig-7 Example of folder Structure 19

Fig-8 Flow Diagram showing codification sequence 20

Fig-9 Modify Metadata Module Form 21

Fig-10 Modify Metadata Module Form1 and Form2 22

Fig-11 State level User Symbolic 26

Fig-12 District Level User Symbolic 26

Fig-13 Tehsil Level User Symbolic 26

Fig-14 History of scanned documents Symbolic 27

Fig-15 Hardware Interfaces 29


109 | P a g e

List of Tables

Table

No.

Description Page

No.

Table-1 General PostgreSQL limits 9

Table-2 Privileges table 16

Table-3 Document Type and codes 19

Table-4 Metadata Table Structure for ROR except registry 22

Table-5 Example of Field book metadata 22

Table-6 Example of Jamabandi metadata 23

Table-7 Example of Misalhaqiyat metadata 23

Table-8 Example of Intekal metadata 23

Table-9 Metadata Table Structure for Girdhawari 23

Table-10 Metadata Table Structure for Missing Documents 23

Table-11 Metadata Table Structure for register deed 24

Table-12 Example of Registry deed Metadata 24

Table-13 Example of Newly Introduced Document Metadata 24

Table-14 Description & source of each field 24

Table-15 Few examples for major tools required in application 27

Table-16 Responsibility of Stake Holder 35


110 | P a g e

1 Introduction

1.1 Purpose

This FRS describes the requirements and specifications of DRS, a document retrieval

system. It explains the functional features of the DRS, along with interface details,

design constraints and related considerations such as performance characteristics. The

FRS is intended for Department of Land Revenue & Disaster Management and Haryana

Space Application & Research Center.

1.2 Scope

Under Project Titled “Modernization of Land Records under NLRMP, Haryana”

Document Retrieval System is a development requirement. The main scope is

retrieving/printing of old records (Musavi, Jamabandi, Field book, Registered deed,

Misalhakiyat, Mutation/Intekal and others) from a single point interface. Also,

depending on different user types (i.e., administrator, user, guest, etc.) different rights of

access will be provided access, view, print and update Documents. (Reference SDD-

p42).

1.3 Abbreviations

RFP – Request for proposal

DRS – Document Retrieval System

NIC – National Informatics Centre

FRS – Functional Requirements Specification

DMS – Document Management System

SRS – Software Requirements Specification

SDD- Software Design Document

NLRMP- National Land Record Modernization Programme

DLR-Department of Land Revenue

HARSAC- Haryana Space Application & Research Center

ROR-Record of Rights

LAN-Local Area Network

WAN-Wide Area Network

ACID-Atomicity Consistency Isolation Durability

SAN-Storage Area Network

NAS-Network Attached Storage

AMC-Annual Maintenance Contract

HRDMRS-Haryana Revenue Document Management & Retrieval System

1.4 System Overview –

The FRS is organized into two main sections.

The Overall Description

The Specific Requirements.


111 | P a g e

The Overall Description will describe the requirements of the DMS from a general high

level perspective. The Specific Requirements section will describe in detail the

requirements of the system.

1.5 References –

Official Website of Government of Haryana

RFP of Project “Modernization of Land Records under NLRMP, Haryana”

SDD of Project “Modernization of Land Records under NLRMP, Haryana”

Project Implementation Guidelines

Website of nlrmpportal.nic.in

2 Overall Description

2.1 Product Perspective

From single point, we can have access to scan copies of revenue records defined as

per SDD i.e. different records of different durations.

User can take printouts of the documents.

Records of outputs shall be maintained for all printouts/reports to support

authentication in future.

Provision to add scanned documents in future.

2.2 Product Functions

Storage.

Dynamic Retrieval.

Updation.

Printing.

Usage Report Generation.

2.3 User Characteristics

Department of Land Revenue and Disaster Management: Approval of Designed system.

Haryana Space Application and Research Center: Consultant for designing approval of

system and implementation of the project

2.4 Dependencies

Availability of different types of documents.

Condition of available documents.

Ease of readability of available documents.

Scanning of document.

ROR data availability.


112 | P a g e

2.5 Constraints and Assumptions

Output of the DMS will depend on the condition and readability of the Old revenue

Records

3 Specific Requirements

3.1 System Design & Application Platform.

3.1.1 Application Platform

Application will use Microsoft .Net Technology to develop the Document

Management & Retrieval System. Application will use.Net framework 3.5 version.

Data Retrieval System will be Intranet Application & installed in all Tehsil and States.

User shall access the application from Tehsil and State. Copy of all scanned

documents will be stored at Tehsils, Districts and States levels. Metadata of all

scanned document for document retrieval will be stored at all levels (Tehsil, District

and State) but edited at Tehsil level only.

3.1.2 Database Used

Application will use open source PostgreSQL 8.4 database server to store the data.

PostgreSQL is a powerful, open source object-relational database system. It is fully

ACID compliant, has full support for foreign keys, joins, views, triggers, and stored

procedures (in multiple languages). It includes most SQL: 2008 data types, including

INTEGER, NUMERIC, BOOLEAN, CHAR, VARCHAR, DATE, INTERVAL, and

TIMESTAMP. It also supports storage of binary large objects, including pictures,

sounds, or video. Metadata or Document Index stores all types of scanned document

path at Tehsil level. Some general PostgreSQL limits are mentioned below (Table-1)

Table-1: PostgreSQL Limits

Limit Value

Maximum Database Size Unlimited

Maximum Table Size 32 TB

Maximum Row Size 1.6 TB

Maximum Field Size 1 GB

Maximum Rows per Table Unlimited

Maximum Columns per Table 250 - 1600 depending on column types

Maximum Indexes per Table Unlimited

3.1.3 Application Access

Intranet Application will be installed separately at Tehsil and State level.(Fig-1).

Hierarchical data structure shall be deployed at State, District and Tehsil level and

scanned pdf files will be kept at State, District and Tehsil level. Different users based

on their defined privileges will be connected to the servers at State and Tehsil level.


113 | P a g e

Application Access

Fig-1

Tehsil user of same tehsil will have access to the application directly from the service

launched from the tehsil server. If tehsil level users having privilege of state level want

to view other tehsil/district then they can view data via access to the application at state

level.

Tehsil level users can have the privilege like view, edit, print and remarks submission

during application access. This shall be user specific.

District server will not contain the application. District level users shall access the

application with either district or state level data access privileges. The state level user

will access the application present at state level.

State and District level users will have privilege of view, print and submitting remarks

during application access

The main reason for keeping the application both at tehsil level and state level is that in

case of state LAN is down then tehsil user can work efficiently using application present

at tehsil level. Also, if tehsil level LAN is down, tehsil level users having state level

privilege can access the application present at state level and can perform view, print and

remark activities.


114 | P a g e

3.1.4 Storage & Synchronization

Fig-2

Database and scanned documents are kept at State, district and tehsil level for disaster

recovery. Metadata shall be updated from tehsil to District and State level using WAN

connectivity. The scanned documents shall be migrated to district and state level via

WAN.

State Server

Database

File

Application

Tehsil Server

Database

Application

File

District Server

Database

File

user user

Updation at Tehsil Level

Storage & Synchronization


115 | P a g e

The synchronization( from tehsil to district and State) will be maintained by raising flag

at Tehsil level, on every change in database a flag shall be put and once the changes are

replicated at District and State level, the flag will be removed. This shall ensure that

only updated data is migrated.

If the tehsil level user has done any addition/modification in metadata or scanned

documents, then synchronization of data updation will be done at state and district level

from the tehsil level. Before starting synchronization process, the WAN connectivity

between tehsil to district and from tehsil to state would be checked. If any one of the

WAN connection is not proper then synchronization process will not start at all. After

having all the WAN connections properly connected, the synchronization process will

start.

During the synchronization process, if the WAN got disconnected then after having the

proper WAN connection again, the synchronization process will start from the point

where the WAN was disconnected and synchronization process was stopped. The

synchronization will follow atomicity rule of ACID in database.

Atomicity states that database modifications must follow an “all or nothing” rule.

Note: Provision will also be provided for checking the state and district data versus

Tehsil data for ensuring and providing report to everyone that data is synchronized. This

will be an everyday activity for ensuring proper synchronization daily.

3.2 Functional Requirements

3.2.1 Storage

All documents in record of revenue are to be collected, scanned and stored in soft file

formats (pdf) in properly defined structure for managed retrieval as well as for Printing

as and when required.

3.2.2 Dynamic Retrieval

Application development for easy Searching, Querying, viewing History and Printing.

3.2.3 Updation

A procedure for storing new Documents and/or modifying the existing document’s

metadata and storage path. Provision shall be made to enter user comments for any

wrong codification of the scan documents. These comments shall be saved in user

logs for reference to correct the document location. There shall be provision to

upload any scanned document along with the remark for reference purpose.

3.2.4 Printing

A module for printing with following functionality’s:

a) Preview of document to be printed.

b) Printing on default paper size as defined in selected document type.

c) Printing on custom paper size as per user requirement.


116 | P a g e

d) Each printout shall have the user authentication details (bar code) to check its

validity.

3.2.5 Application Usage Report Generation

Time based (Between custom dates) and User Rights Based Application usage

Reports of following types can be generated:

a) Listing Documents viewed by a particular user – Usage log of particular user

will be stored for a defined time frame (customizable).

b) User usage report will be generated for a duration (From and To Date) as

requested by the user.

c) Listing user remarks of different authorized users for all / Particular

Document type. Functionality will be provided to user for commenting on

quality/correctness of document being viewed by a user. To enable the user to

enter the comments and attaching scan documents for uploading user need to

enter his/her identification details and proof.

d) Time based Listing of Documents Updated with the user details of user

involved in Updation process along with date and time.

e) Print Report for a duration (From and To Date) will be generated

f) Any other report from the data generated to be developed as per the user

requirement.

3.3 Document Management and Retrieval module:

3.3.1 Login Module

There will be two types of login modules Admin module and User & Privilege

Module.

3.3.1.1 Admin Module

Admin module will be used to create new users, enable or disable existing users

and manage / modify privilege rights of existing users.

Flow Diagram for Admin Module

Fig-3

3.3.1.2 User & Privilege Module:-

Application module can use the application as per the set privileges provided by

Admin.

3.3.1.2.1 Users Level:

Enable or Disable User

Set Privileges

Finish Admin User

Login

Change

Privileges

Create User


117 | P a g e

The Provisions shall be provided in the Application to define the User at

different level. The various level of user shall be as follows

State level

District Level

Tehsil Level

3.3.1.2.2 Type of Users:

Each of the above mentioned Users level shall comprise of different Type of

Users. The Type of Users at different level shall as follows

Admin User

Application User

3.3.1.2.3 Functionality of User:

The functionality of User shall be dependent on User level and User type. The

details of the functionality shall be as follows:

3.3.1.2.3.1 Admin User: - Admin user shall only manage the users at different level.

State Level Admin User: - User can create District Level Admin User

and State level Application User.

District Level Admin User: - User can create Tehsil Level Admin User

and District Level Application User.

Tehsil Level Admin User: - User can create Tehsil Level Application

User.

Flow Diagram of User Management

Fig-4

3.3.1.2.3.2 Application Users: - Application user shall have the rights to Access the

Application. It will operate the application for Codification, Validation and Serving

the Public.

State Level Application user: - User shall have right to access all districts

documents.

Super Admin

District Admin

User

State Application

User

Tehsil Application user

Tehsil Admin User District Application User


118 | P a g e

District Level Application user: - User shall access designated districts

documents.

Tehsil Level Application user: - User can access designated Tehsil

document.

3.3.1.2.4 Privileges

The Application shall have the provisions to define the following level of privileges

Document Level

Access Level

Flow Diagram of Privileges

Fig-5

The details of different levels of privileges has been defined below

3.3.1.2.4.1 Document Level Privileges:

These privileges shall be defined on the documents. There are seven types

of privileges to be defined on this level.

View: Document view access.

Print: Document print access.

Remark: Comment and attached the Reference document

Scan: Document scanning access.

Modify: - Metadata modify access.

Codify: - Document Codify access.

Validate: - Document Validation access.

3.3.1.2.4.2 Access Level

a) State Level Privileges: User shall view all district data as well as print the

desired document. The User shall have the rights to comments/ remarks on any

document for the purpose of corrections. The User can attach the reference

document for the support of their comments/remarks.

Tehsil District State

Privileges Type

Document Level Privileges Access Level Privileges

View Print Modify Scan Codify Validate Remarks


119 | P a g e

b) District Level Privileges: User shall view designated district data as well as

print the desired document. The User shall have the rights to comments/ remarks

any document for actions at Tehsil. The User can attach the reference document

for the support of their comments/remarks.

c) Tehsil Level Privileges: User shall have access to designated Tehsil

Document/data view, Print, Scan, Codify, Validate and Modify documents of its

tehsil.

3.3.1.2.4.3 Privileges Restrictions

The privileges restriction level wise shall be as follows –

Table-2: Privileges Table

Note:

a) Y stands for Rights available, from which admin can give any privileges to

the user.

b) N stands for Rights Not available.

If admin give the State level privileges to user then it has only view, print and

remark option only. Admin can give different combination of privileges to the

user.

3.3.1.2.5 Password policy

The password shall be alphanumeric. The password shall be a combination

of upper and lower case, shall have punctuation characters as well as letters,

for example the following characters can be used along with letters: 0-9,!@#$

%^&*()_+|~-=\`{}[]:";'<>?,./)

Privileges

State Level District Tehsil

Applicatio

n User

Administrat

or

User

Applicatio

n User

Administrat

or

User

Applicatio

n User

Administrat

or

User

View Y N Y N Y N

Print Y N Y N Y N

Remark Y N y N Y N

Scan N N N N Y N

Modify N N N N Y N

Codify N N N N Y N

Validate N N N N Y N

User

management N Y N Y N Y


120 | P a g e

The complexity of the password shall vary with the level of Information

that it is used to protect.

The length of the password shall be minimum eight (8) characters. It shall

not be any word from the dictionary or formed in any known pattern like a1b2

etc.

3.3.2 Document Management Module

3.3.2.1 Codification Module

A data entry tool will be made for entering the scanned documents information

into the metadata (Fig-6). User will select the document type, enter year of

document, select District, Tehsil and Village, enter Hadbast number and then

open the .pdf for which metadata information entry is to be done.

User will scan the document and store at any location through this module. User

shall go to the location and select the document.

Note: NIC has suggested for incorporation of the scanner (TWAIN

compatible) access with in this application. RAMTeCH is evaluating the

possibility of the integration of the same and if feasible it shall be made.

After the pdf is opened, user can enter the murabba and khasra information into

the metadata and after clicking on save button, the entered information will be

automatically saved into the metadata. The same process can be carried out for all

the pages of the pdf document.

After the completion and validation of the metadata entry, a provision will be

there to upload it to the server at Tehsil, District and State level.

Codification module

3.3.2.1.1 New entry


121 | P a g e

Fig- 6

3.3.2.1.2 Folder Structure & Meta data creation for Indexing

The documents scanned will be stored in proper folder structure. And metadata file will

be created with a vision to store path of stored documents with a unique index for

retrieving correct page of correct book/Document type being queried (Fig-7).

3.3.2.1.3 Folder structure

Below is the Folder Structure to store all types of scanned documents on physical drive

or network drive.

Drive:\>HARYANA_DATA\VVVVV\DD\YYYY-YYYY\VVVVV_DD_YYYY-

YYYY_PP.pdf Where description for abbreviations will be as below:

Drive: Document can be stored on any Root Directory e.g. (D:) or network drive e.g.

(Z:)

There should be a folder on drive named as HARYANA_DATA.

Drive:\>HARYANA_DATA shall be configurable and will be named based on

different drives present in the system.

VVVVV\DD\YYYY-YYYY\VVVVV_DD_YYYY-YYYY_PP.pdf will be fix and not

configurable for any system. VVVVV: 5 Digit VarChar Village Code (NVCODE”) as mentioned, in ROR

e.g. village code of Kurbanpur village is 02884.

YYYY-YYYY: 9 Digit Period of Scanned Document e.g. (1963-1964).

DD: 2 Digit VarChar Code for Document type

The Document code of different documents can be any of below mentioned list (Table-3).

Table-3: Document Type and codes


122 | P a g e

Sr. No. Digit Document Code Document Description

1 01 Musavi

2 02 Field Book

3 03 Jamabandi

4 04 Misalhaqiyat

5 05 Mutation/Intekal

6 06 Registered Deed

7 07 Sajra Nasab

8 08 Lal kitab

9 09 Girdhavari

10 -- Any New Document Introduced

Note: Any other document code can be introduced as and when defined by DLR. Admin

user can enter the document type and its attribute in the system using codification

module.

PP: 2 Digit Varchar Code (01-99) representing the Sr. no. of file if scanned document /

Book is stored in more than one .pdf files. This, Serial No. is the representation

sequential file no./ Count in which entire book is scanned and stored.

The path of this scanned document is stored in metadata (Table-4), which can be used

for easy and quick retrieval of any scanned document.

Example of folder Structure

Fig-7

Flow Diagram showing codification sequence.

Start

Access Scanned document

Make village code folder in drive


123 | P a g e

Fig-8

3.3.2.1.4 Modify Metadata Module-

If the user having write permission would like to modify metadata of a particular document

according to the remarks entered for that document, then after clicking on the “Document

Metadata Modification” button, the form for metadata modification will open. Here, the user

will select document type, year, district, tehsil, village and remarks for the document to be

modified in metadata entry.


124 | P a g e

Fig-9

After selecting value and clicking on “Show Metadata” button, Metadata Modification” form

for modifying the document metadata will be opened.

The metadata entry for the document to be modified will be displayed. The user will select

the field to be changed from the combo box and enter its modified value in the textbox. After

entering the modified at last at “MODIFY’ button, the metadata of the selected document

will be modified.


125 | P a g e

Fig-10

3.3.2.1.5 Metadata:

Metadata is generated to store path where scanned document is kept and to retrieve

scanned document very easily and quickly. It will be also used in various queries like

year based search. Table-3 to Table-13 shows the metadata structure for various types of

documents covered under DMS scope. Table-14 describes the details of the field names

used in the metadata.

Metadata Table structure

Table-4: Metadata Table Structure for ROR except registry

Hadbast NV

Code

Period Murabba

No

Khasra

No

Doc

Type

Pdf No. Page

No.

Path

Table-5: Example of Field book metadata

Hadbast NV

Code

Period Mur

abba

No

Khasra

No

Doc

Type

Pdf

No.

Page

No.

Path

259 02884 2005-2006 13 8/2 02 3 148 02884\02\2005-2006

259 02884 2005-2006 13 9/1 02 3 148 02884\02\2005-2006


126 | P a g e

Table-6: Example of Jamabandi metadata

Hadbast NV

Code

Period Mur

abba

No

Khasra

No

Doc

Type

Pdf

No.

Page

No.

Path

259 02884 2005-2006 13 8/2 03 3 148 02884\03\2005-

2006

259 02884 2005-2006 13 9/1 03 3 148 02884\03\2005-

2006

Table-7: Example of Misalhaqiyat metadata

Hadbast NV

Code

Period Mur

abba

No

Khasra

No

Doc

Type

Pdf

No.

Page

No.

Path

259 02884 2005-2006 13 8/2 04 3 148 02884\04\2005-

2006

259 02884 2005-2006 13 9/1 04 3 148 02884\04\2005-

2006

Table-8: Example of Intekal/Mutation metadata

Hadbast NV

Code

Period Mur

abba

No

Khasra

No

Mutatio

n No

Doc

Type

Pdf

No.

Page

No.

Path

259 02884 2005-2006 13 8/2 1453 07 3 148 02884\07\

2005-2006

259 02884 2005-2006 13 9/1 4532 07 3 148 02884\07\

2005-2006

Table- 9: Metadata Table Structure for Girdhawari

Hadbast NV

Code

Period(start

year-end

year)

Murabba

No.

Khasr

a No.

Doc

Type

Pdf

No.

Page

No.

Path

259 02884 1996-2001 23 21 10 11 5 02884\10\1996-

2001\02884_10_19

96-2001_11.pdf

259 02884 1996-2001 23 22 10 11 5 02884\10\1996-

2001\02884_10_19

96-2001_11.pdf

Table -10: Metadata Table Structure for Missing Documents

Hadbast NV Code Period Doc Type

Note:

The above metadata to be stored in PostgreSQL 8.4 database server.


127 | P a g e

The retrieval of registered deed will not be based on plot number. Provision will be given to

retrieve the registered deed based on period and registry no.

Table -11: Metadata Table Structure for register deed

Tehsil

Code

Reg No Period Book No Pdf No Path

Note: The Registry no. along with tehsil, period and book no shall be used for retrieval of the

registry documents. Provision shall be made for entering the Khasra no on the retrieved Reg no..

So that in future the registry shall be linked with Khasra no as well (Table 11).

Table-12: Example of Registry deed Metadata

Tehsil

Code

Reg No Period Book No Pdf No. Path

001 4857 2001-2002 1 1 02884\03\2001-2002

001 2367 2005-2006 1 1 02884\06\2005-2006

The fields(and data type of different fields) in metadata for newly introduced document type will

be finalized based on the information present in that new document.

Table-13: Example of Newly Introduced Document Metadata

Hadbast NV

Code

Period Field1 Field2 Doc

Type

Pdf No. Page

No.

Path

Table14: Description & source of each field

S.N. Field Description Source

1 Hadbast VarChar (5) As provided by DLR

2 Nvcode VarChar (5) As provided by NIC

3 murabba Numeric (4) Manual entry from Scanned document

4 Khasra VarChar (255) Manual entry from Scanned document

5 Doc Type VarChar (2) As described above in File Naming Convention.

6 pdf No. VarChar (2) As described above in File Naming Convention.

7 Path VarChar (255) As in Folder structure

8 Tehsil Code VarChar (3) From ROR data

9 Reg. No. Numeric (6) Manual entry from Scanned document

10 Period VarChar (9) Manual entry from Scanned document

11 Book No VarChar (5) Manual entry from Scanned document

12 Page no Numeric(5) Manual/Automatic entry from Scanned document

13 Mutation no Varchar(8) Manual/Automatic entry from Scanned document


128 | P a g e

3.3.2.1.6 Database Indexing

Scanned documents are stored with different attributes at the specified location in the

system. Various attributes like district code, tehsil code, nvcode, khasra number shall be

indexed to ensure faster retrieval of the file path for retrieval.

3.3.3 Document Retrieval System

Document Retrieval System will be an intranet application and will be deployed at Tehsil

level, District Level & State Level.. There will be provision for data integration at

District and State level. Updation will be done by migrating data from Tehsil level to

District and State level using intranet.

The Application interface and functioning of various modules of Document Retrieval

system is explained below. However, the Application behavior will be user login based.

Different rights and Privileges to different user types of application are explained under

the head “Login Module”

3.3.3.1 Home Page:

For all users irrespective of state, district and tehsil the home page address shall be the

same. Application based on the user login shall direct the user to tehsil server or state

server. Home page shall contain both the option, document view and map view of the

document.

3.3.3.2 Document view

In order to view a desired document, user shall drill down from district/ tehsil/ village/

doctype/ khasra no. /period etc.. Once selected, the required page shall open as pdf

document in the window. The view shall contain only one page at a time.

Privileged user shall be allowed to put remarks and attach any reference scan document

for the purpose of quality/correctness of the document.

Selection Criteria: (Note: The pictures (Fig-11 to Fig-14) are symbolic. Actual

figure shall be different.)

State level User: will be able to navigate all district, tehsil and villages of Haryana State.

Fig-11


129 | P a g e

District Level User: will be able to navigate & Retrieve documents of all Tehsils of

His/her district, tehsil.

Fig-12

Tehsil level User: Tehsil user will be able to navigate only through all villages present in

his/her Tehsil and depending on the user privileges. He/she will be able to perform

editing tasks. Tehsil level user need not to enter any district and tehsil.

Fig-13

History of scanned documents: Users will be able to view the history of a particular

document with a particular khasra number. Depending on the user level and his / her

rights of querying / selection of data / documents as explained above.


130 | P a g e

Fig-14

3.3.3.3 Map view

Map view facility will be available only to show the document associated with the

particular parcel.

Geo-referenced vector data for entire state shall be migrated into postgres database.

Application shall fetch the desired village from the selection module of document retrieval

system or by manually zooming the GIS database. The layers shall be scale dependent to

improve the performance of the system.

3.3.3.4 Document Retrieval System Tools

As the DMS shall use PDF documents for display all available tools from Adobe are available

for the required functions.

Table-15: Few examples for major tools required in application

S.N Tool Name Function

1 Print Print the pdf document

2 Save Save as pdf document in local machine

3 Navigation Go to desired page of pdf

4 Zoom Zoom to pdf document

3.4 Non-Functional requirements

a. External interfaces - The Document Retrieval System will use the standard

input/output devices for a personal computer. This includes the following:

Keyboard

Mouse

Monitor


131 | P a g e

Printer

Scanner machine

b. Software Interfaces

The system shall interface with PostgreSQL 8.4 database, Windows server 2008 R

Enterprize, IIS, ASP.net, .net framework 3.5, Mapwindow.

c. Hardware Interfaces

The system shall run on a Microsoft Windows based system. There shall be three type

of server at State and district level viz- application server, Database server and File

server. At district level only Database and File server shall reside.

State Server

Hardware Interfaces


132 | P a g e

Fig-15

(Note:- The detailed configuration of the hardware shall be finalized after expected

document sizing and GIS data sizing is completed)

d. Communication Interfaces All communication will done over standard communication protocol. The communication

goes through standard internet (LAN & WAN).

e. User documentation

Database+Backup File+Backup Application+Backup

Tehsil Server

Database+Backup Application+Backup File+Backup


133 | P a g e

To assist the user in understanding the product better and to assist them in better

utilization of the product and its features, we will be providing an online user manual (in

.pdf format).

f. Performance requirements

Performance requirements define acceptable response times for system functionality.

The load time for user interface screens shall be around 2 seconds.

Desired document will be retrieved less than 5 seconds (This shall depend on

LAN speed).

Queries shall return results within 5 seconds (This shall depend on LAN speed).

Note: The dedicated Wide Area Network (WAN) is desired for the operationalization of

said intranet application for document management and retrieval at Tehsil, district and

State level.

g. Logical database requirement –

Type of document

District name

Tehsil name

Village name

Year of the document

Murabba No.

Khasra No.

Musavi No.

Book No.

Registry No.

h. Design constraints

The Document Retrieval System shall be a web based application under WAN running in

a Windows environment. The system shall be developed using dot net and a PostgreSQL

8.4 database.

i. Standards Compliance

There shall be consistency in variable names within the system. The graphical user

interface shall have a consistent look and feel.

j. Reliability

Specify the factors required to establish the required reliability of the software system at

time of delivery.

k. Availability

There will be 24*7 availability.

l. Maintainability

The Document Retrieval System is being developed in dotnet. Dotnet is an object

oriented programming language and shall be easy to maintain.


134 | P a g e

m. Portability

The Document Retrieval System shall run in any Microsoft Windows environment that

contains .net framework and the PostgreSQL 8.4 database.

n. Service Delivery Module

NIC has suggested to incorporate service delivery module for taking user request for

printout and managing financial transaction. RAMTeCH has raised its reservation on this

module as neither RFP nor SDD has any reference about this module requirement. It was

agreed during the meeting that the present practice in DLR shall be studied and then final

decision shall be taken up about this requirement.

3.5 Security

The Security is desired at different levels for maintenance of confidentiality of the

document and to prevent misuse of the documents. The security are desired at following

levels.

Access of the DMS module

Window File Folder Security to prevent Deletions and modification of Scanned

Document in Data base

PDF security

Protection from virus and hacking

Data based Security to prevent Deletion and Modification of Scanned Document

Disaster recovery of database

Backup Policy

Audit logs

3.5.1 Access of the HR-DMS

User Login

The Provisions will be provided to restrict the accessibility of the HRDMRS by

unauthorized user. The concept of Authentication and Authorization will be collectively

used during the development of the Software. Through Authentication process the user

will be identified, while through authorization only authenticated user can have access to

the resources they requested. The Authentication will achieved by the user by sharing

credentials that somehow verify the user's identity.

There is administrator account in the application and administrator can create, enable or

disable user, and edit a user profile. Administrator need to control the access of the

information from application by the user. Administrator will provide different

permissions & right to each user of application. It is the responsibility of administrator to

whom he/she authenticate and authorize to use the said application.

After creation of user, user can login in the application & use the application as per its

privileges. Whenever a user logs on to an application, the user is first authenticated and

then authorized. If the view permission is allocated by the administrator the user cannot

edit the document but can get the printout of the document. If full rights are given to the

user then user can modify the document.


135 | P a g e

If the user authentication for password fails 3 times then the password for that user will

be locked and the user will have to request for new password for login into the

application.

Note: As suggested by the NIC regarding the incorporation of the Biometrics to access

the application, RAMTeCH has agreed to look for the feasibility of the same in the web

based platform.

3.5.2 Windows File & Folder Security

To prevent the deletion and modification of scanned document, windows file and folder

security is needed.

The files are securable objects; access to them is regulated by the access-control model

that governs access to all other securable objects in Windows. Windows provides a built-

in way to access information and check user privileges to decide who can and who cannot

access a document/folder. Each file/folder in Windows has security information. We will

set security permissions on files and folders in which the scanned documents will be kept.

These permissions grant or deny access to the files and folders.

3.5.3 PDF security

We will set permission for viewing, printing and saving the pdf based on different users

login into the HRDMRS application.These previleges are defined in the admin module.

3.5.4 Protection form Virus and Hacking-

Installation of proper antivirus will protect the system from virus.AMC of antivirus

software must be present.configuration of firewall settings on the system will reduce the

chances of hacking.

3.5.4.1 Antivirus policy

The anti-virus product should be operated in real time on all servers and client

computers. The product should be configured for real time protection.

The anti-virus library definitions should be updated at least once in 15 days.

Anti-virus scans should be done a minimum of twice per month on all

workstations and servers.

Virus threat analysis should be done before adopting any anti-virus solution.

Other sources of virus like floppy, CD, DVD, usb pendrive etc should be

carefully used and in an authorized manner. Every external storage device

must be scanned before use.


136 | P a g e

All the users must be made aware of threats resulting by virus outbreak and

awareness workshop should be carried out indicating use of antivirus solution.

3.5.5 Database Security

Database will be secured by setting permissions to different users at application level

only. Any application level user will not be authorized to view the database.The default

user of postgres will be the only user at the database level.the password of the database

will be known to the superadministrator of the HRDMRS application.He/She can take up

backup or restore the database if required.

3.5.6 Disaster Recovery of database

State Level

SAN will be adopted at state level. A storage area network (SAN) is a high-speed special-

purpose network (or sub-network) that interconnects different kinds of data storage

devices with associated data servers on behalf of a larger network of users.

SANs support disk mirroring, backup and restore, archival and retrieval of archived data,

data migration from one storage device to another and the sharing of data among different

servers in a network. SANs can incorporate sub-networks with network-attached storage

(NAS) systems.

The Provision will be desired to have the BACKUP server at State level. The data stored

at state level in database server will be uploaded to BACKUP Server periodically (as

Defined).

District Level

Database and file servers will be kept at district level for storage purpose only.

Tehsil Level

Database and file server in mirror will be kept at tehsil level for storage and editing

purpose.

3.5.7 Backup policy –

According to backup policy, the backup will be taken at tehsil level and this backup will

be replicated at district level and at the state level.

a) Full backup of Data on the servers present at tehsil level shall be taken once a week

and incremental backup shall be taken daily. Backup for system district server shall

be taken after 15 days and state, of servers, shall be taken once a month.

b) The backup data will be stored at a secured and secluded location and only authorized

people will have access to that location. The backup data media will not be stored in

the server room, it will be stored in other location.


137 | P a g e

c) DVD/CD will be used to store backup data. The back-up data will be password

protected and encrypted. A nomenclature– “District –<district Name> ,“Tehsil –

<tehsil Name>, <-Period of backup>” will be used to keep track of backup data for

any future reference.

d) A set of original disk of all the operating systems and application software will be

maintained at the district CLR office. The calling tree for availing the original disks

will be defined at each tehsil.

e) The backup of the database shall be verified to ensure that all tables and data of the

database are backed up every quarter.

f) The backup DVD/CD’s will be maintained for two quarters and the older backup

DVD/CD’s will be destroyed in the presence of the <Land Records Field Officer>.

The DVD/CD’s will be destroyed only after the above verification process is

complete. A register for the same will be maintained and the record for the same shall

be available for last 24 months.

g) An emergency repair diskette of the operating system shall be created and be

available at the tehsil server room.

h) Backup DVDs/CDs must have the following identifying criteria that can be readily

identified by labels:

System Name

Creation Date

Sensitivity Classification

District Name with code

Tehsil Name with code

Backup period From & To

i) It is the responsibility of the tehsil IS administrator for taking backup. There must be

another nominated person who can take care of the backup in the absence of the

administrator.

j) Regular tests of restoring data/software from the backup copies shall be undertaken,

to ensure that they can be relied upon for use in an emergency.

3.5.8 Audit Logs

Audit Logs shall be stored for the purpose of auditing the events in case of any

security related issues. Audit logs shall be enabled in Application, database and File

servers. Audit logs shall be retained for a period of 6 months or as desired by the DLR


138 | P a g e

Following events shall be recorded:-

User login, logoff

Access of all associated devices

Any change, addition or deletion of user accounts

Changes of access rights to system data resources

Shutdown and restart of the system

Responsibility of Stake Holder Table-16: Stake Holder Responsibility

S.No. Stake Holder Responsibility

1 All Vendor Meta data of all Scanned document shall be as per the

format specified format

Scanned document codified and saved as per the folder

system specified in FRS / SDD

2 DLR/NIC Confirmation regarding the integration of Bhu-Neksha

with HR-DMRS

WAN Compatibility for the Synchronization of Updated

Scanned data base

3 HARSAC Coordination between all stake holders

4 RAMTeCH Development of Application as per FRS