Design Document - Landrecords Madhya Pradeshlandrecords.mp.gov.in/Circular08/cr0808_designdoc.pdf · Design Document 2008 Design Document ... • On sample basis, files of individual

Design Document 2008

Design Document“Creation of Spatial database (Digitization) for

Village Cadastral Maps”

07/07/2008

Project:-“Creation of Spatial database (Digitization) for Village Land Revenue Maps”

Ref: Tender No. K.E. 6256-A Design Specification

2

Table of Contents1. Project Over view

1.1.Scope of Work1.2.Output Format1.3.Software

2. Database Design & Standards2.1 Introduction2.2 Procedure for Building the Database2.3 Database Construction Guidelines2.4 Inputs for the Project2.5 Quality Assurance2.6 Standards for Data Structure

3. Process Methodology3.1. Collecting hardcopy map / sheets from District Land Records Office3.2. Indexing & Coding3.3.Scanning of Village Cadastral map sheets3.4.Digitization of scanned map sheets

4. GENERATION OF DIGITAL CADASTRAL MAP4.1 Tiling Scanned Map Using Grid/Mesh4.2 Digitisation Of Village Maps4.3 Attribute Data Attachment4.4 Hard Copy Output Generation4.5 Hard Copy Evaluation By LRD4.6 Database Generation in GIS Environment4.7 Softcopy Validation by LRD in GIS Environment4.8 Final Hard Copy Generation4.9 Final Hard Copy Validation4.10 Edgematching of Sheets within a Village4.11 Cleanup and Topology Building4.12 Data Translation4.13 Quality Control

5. Indicative Symbology for Cadastral Maps



3

1. Project Over view

Commissioner, Land Records and Settlements, Government of Madhya Pradesh, Gwalior, hasdecided to digitize the cadastral maps of all the villages and store it in the form of vector images witha view to preserve the data available in the documents, facilitate its easy storage, retrieval and greateraccess to the public and functionaries of the Department.

1.1.Scope of Work

With reference to Tender K.E. 6256 – A of CLR, M.P. for creation of Spatial database(Digitization) for Village Cadastral Map for the state of M.P which includes following majoractivities:-

§ Collecting hardcopy of map sheets from District Land Record Offices§ Scanning of Village Map sheets§ Image Cleaning, Indexing & generation of check prints on micro transparency with 100%

matching on 1:1 scale output.§ Digitization of scanned Village map sheets§ Edge matching of sheets within a village in vector format§ Providing Vector Data and hardcopy plots§ Imparting training of computer applications

1.2.Output Format

Data is to be supplied in the ARC .shp or ARC Geodatabase file format. Format dwg/ dxf/ ESRIetc. may be supplied in addition.

1.3.Software Standard GIS software compatible format or in the format desired by the project.



4

2 DATABASE DESIGN & STANDARDS

2.1 Introduction

A data design provides a comprehensive architecture for the database to be viewed in it’s entirely andevaluated how the various aspects of it need to interact. A good design results in a well constructed,functionally and operationally efficient database that –

• Satisfies the objectives and supports requirements• Contains required data without redundancy• Organizes data so that different users can access the same data• Accommodations of different versions of the data• Distinguishes applications that maintain data for those who use it.• Appropriately represents codes and organizes geographical features.

Database standards are an important element of the database design. Standards enable applications andtechnology to work together, they encourage efficiency and effectiveness, help reduce costs ininvestments, protect data against technological change and lead to availability of accurate, completeand current data. Tools, applications and data affect each other and standards are established withthis condition.

2.2 PROCEDURES FOR BUILDING THE DATABASE

The elements of the database are to be created as per the standards herein and scientists/consultants haveto take care that digitization is as per the standards. The inputs are subject to validation at each stage, andwill include qualitative as well as quantitative checks for input accuracy.

The creation of a clean digital database is the most important and complex task upon which the usefulnessof the database lies. Two aspects need to be considered here one is the geographic data necessary todefine where the parcel of land or for that matter any other feature is located and second is its uniqueidentification for associating attributes that link to the records.

At every stage, there should be necessary and proper data verification to ensure that the resultant databaseis as free as possible from error. Errors would generally be of the following types.

• Spatial data are incomplete or double

• Spatial data are in the wrong place

• Spatial data are at the wrong scale



5

• Spatial data are distorted

• Spatial data are linked to wrong attributes

• Non-spatial data are incomplete

For evaluating the digital data the following guidelines/parameters would be checked.

• Comparison of total area of the village by aggregating the parcels, etc. vis-à-vis the areareported available with Land Records Dept.

• Attribute verification providing the correctness of feature coding by listing it out andcomparing with the manuscript maps. Complete checking of all parcels for shape & form andlisting of polygons with zero/no attribute.

• Verification of co-ordinate system

• Verification of registration points and RMS error for the transformation model.

• Verification of edge match with adjacent maps by displaying them side-by-side.

• Checks for digitisation errors like slivers, dangles.

• Checks for mosaicing of maps.

2.3 DATABASE CONSTRUCTION GUIDELINESThe Commissioner Land Records & Settlement, is building village cadastral map database for

the entire state in GIS environment for planning and implementation of various projects at the micro-level. This document lists out in detail the various processes and specification based on the followingpoints.

• The village maps procured from Land Records Department will be traced where necessaryand scanned for further processing

• The scanned village maps will be vectorised and digitised.

• Village cadastral maps will be edge matched wherever required and mosaiced to form a layerin the GIS database at the village level.

• A primary key field will be generated which will be amenable to attribute data attachment.



6

2.4 INPUTS FOR THE PROJECT

• Hardcopies of cadastral maps• Meta data and general attributes

2.5 QUALITY ASSURANCE

The project will have well defined and set procedures for quality assurance of the database. The QCprocedures are both qualitative and quantitative. All coverages or hard copy maps submitted by thevendors/entrepreneurs will have to go through the quality check procedure before acceptance. Thefollowing aspects regarding quality assurance have to be adhered to by vendors/entrepreneurs:

• The quality assurance of the data will be carried out by CLR using automated routines as well asmanual checks as required.

• This will include checks for topological correctness, unique feature coding, completeness of data,naming conventions, accuracy and errors.

• The quality assurance form duly filled have to be submitted along with the soft copy data.

• Data not complying with the standards and accuracy specifications will be sent to vendors forcorrection and will have to be re-submitted after necessary corrections.

• If the data complies with the quality assurance standards and error limits are in the prescribed rangethe data will be accepted.

• The quality assurance should comply with the following aspects (1) positional accuracy, (2) Attributeaccuracy, (3) Logical consistency, (4) completeness and (5) mosaicing fit of the data.

• Quality assurance of database will be done within a specified time frame by CLR.

• On sample basis, files of individual villages and the mosaic will be digitally quality checked by CLR.

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

i. File naming 100%

ii. Directory structure 100%

iii. Data readability 100%

iv. Data structure 100%



7

v. Data format 100%

vi. Topology 100%

vii. Attribute correctness 100%

viii. Attribute completeness 100%

ix. Data mosaicing 100%

At each step of the process, adopted for computerization of the village map, quality check has tobe applied to ensure error free database generation. However, the following major quality checks aredesigned to ensure the project objectives:-

• Quality check on Merged product generation using 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 mosaic of village maps (QC 5)

• Quality check on final deliverables (QC 6)

2.6 STANDARDS FOR DATA STRUCTURE

Table 2.1: Codes of Polygon features (ADDTTRRPPPPPVVV)

S.No LAYERS SYM1 SYM2*

1 POLY_V_BOUND 01

2 POLY_STREAM 02

3 POLY_CANAL 03

4 POLY_EMBANK 04

5 POLY_FOREST 05

6 POLY_PIPE 06



8

7 POLY_RAIL 07

8 POLY_ROAD 08

9 POLY_WATER 09

10 POLY_ABADI 10

11 POLY_PARCEL 11

12 POLY_PARCEL_2 12

13 LINE_ARBITRARY 13

14 POLY_OTHERS 14

15 POLY_FOREST_BOUND_PARCEL 05 11

16 POLY_WATER_PARCEL 09 11

17 POLY_ROAD_PARCEL 08 11

18 POLY_RAIL_PARCEL 07 11

19 POLY_ROAD_RIVER 08 11

20 POLY_ABADI_PARCEL 10 11

21 … … …

.N0Field/Item

NameField/Item Width Field/Item description

1 SYM1 2, 2, C

2 SYM2 2, 2, C

NOTE :

* ‘SYM2’ Item will carry the information of the line associated with any other basic line/poly layers(examples . are given from 15 through 20). Additional combination of any two basic layers should



9

be represented as shown in the example keeping the non-parcel layers as the dominant layers inSYM1. Thus in the Rail-Parcel common line, the rail is the dominant layer and the parcel is thesecondary layer; this will have ‘07’ code in ‘SYM1’ and ‘11’ in ‘SYM2’.

Table 2.2: Codes of Line features (LDDTTRRPPPPPVVV)

S.No LAYERS LIN-CODE

1 LINE_ROAD_PAKKA 0101

2 LINE_ROAD_KACHHA 0102

3 LINE_CARTTRACK 0103

4 LINE_FOOTPATH 0104

5 LINE_RAIL(Narrow and others) 0201

6 LINE_BROAD_GAUGE 0202

7 LINE_RILLS 0301

8 LINE_WATER 0302

9 LINE_CANAL 0303

10 LINE_PIPE 0304

11 LINE_V_BOUND 0401

12 LINE_V_DIVIDE 0402

13 LINE_V_BOUND_STREAM_LINE 0403

14 LINE_TRAVERSE_STATION 0501

15 LINE_PADDY 0601

16 LINE_EMBANK 0701

17 LINE_MARGIN 0801



10

18 LINE_OTHERS 1000

S.N0Field/Item


1 LIN-CODE 4, 4, C Details of line eg. Roads, canal etc.

Note :

The line feature coverage contains the line features other than the parcel boundary

Table 2.3: Codes of point features (PDDTTRRPPPPPVVV)

S.No. CAD BLOCKNAME LAYERS PIN-CODE

1 ABADI SYM_ABADI 0101

2 ABADI-1 SYM_ABADI 0102

3 AIRPORT SYM_INFRASTRUCTURE 0201

4 INDUSTRY SYM_INFRASTRUCTURE 0202

5 BRIDGE SYM_INFRASTRUCTURE 0203

6 BRIDGE-1 SYM_INFRASTRUCTURE 0204

7 BAZARPETH SYM_AMMENITY 0301

8 COLLEGE SYM_AMMENITY 0302

9 FGUESTHOUSE SYM_AMMENITY 0304

10 GUESTHOUSE SYM_AMMENITY 0305

11 HOSPITAL SYM_AMMENITY 0306

12 HOTEL SYM_AMMENITY 0307



11

13 IGUESTHOUSE SYM_AMMENITY 0308

14 MARRIAGEHALL SYM_AMMENITY 0309

15 OFFICE SYM_AMMENITY 0310

16 PETROLPUMP SYM_AMMENITY 0311

17 POSTOFFICE SYM_AMMENITY 0312

18 POLICESTATION SYM_AMMENITY 0313

19 SCHOOL SYM_AMMENITY 0314

20 TANK_OVERHEAD SYM_AMMENITY 0315

21 TELEPHONEOFFICE SYM_AMMENITY 0316

22 THEATRE SYM_AMMENITY 0317

23 BUILDING SYM_CONSTRUCTION 0401

24 COMPOUND SYM_CONSTRUCTION 0402

25 WASAHATH SYM_CONSTRUCTION 0403

26 CHATTAN SYM_THEME 0501

27 GRASS SYM_THEME 0502

28 HILL SYM_THEME 0503

29 CHURCH SYM_WORSHIP 0601

30 GURUDWARA SYM_WORSHIP 0602

31 MOSQUE SYM_WORSHIP 0603

32 TEMPLE SYM_WORSHIP 0604

33 FB_S_STONECIR SYM_STONE 0701

34 FB_STONECIR SYM_STONE 0702



12

35 FB_STONESQ SYM_STONE 0703

36 STONESQ SYM_STONE 0704

37 TRI SYM_STONE 0705

38 STONE_CIRCLE SYM_STONE 0706

39 STONE_TEMPLE SYM_STONE 0707

40 HISTORICALPLACE SYM_TOURISM 0801

41 MONUMENT SYM_TOURISM 0802

42 STATION_TETRA SYM_TRAVERSE_POINT 0901

43 STATION_TRI SYM_TRAVERSE_POINT 0902

44 ITS(Internal Traverse Station) SYM_TRAVERSE_POINT 0903

45 TS(Traverse Station) SYM_TRAVERSE_POINT 0904

46 KABRISTAN SYM_SAMSHAN 1001

47 SAMSHAN SYM_SAMSHAN 1002

48 POLE_ELECTRIC SYM_COMMUNICATION 1101

49 POLE_TELE SYM_COMMUNICATION 1102

50 ARROW_RIVER SYM_ARROW 1201

51 ARROW_TEXT SYM_ARROW 1202

52 TREE_SINDHI SYM_TREE 1301

53 TREE_COCONUT SYM_TREE 1302

54 TREE_OTHERTREE SYM_TREE 1303

55 TREE_MANGO SYM_TREE 1304

56 TREE_B_SINGLE SYM_TREE 1305



13

57 TREE_B_UPVAN SYM_TREE 1306

58 TREE_IMLI SYM_TREE 1307

59 TREE_PADIT SYM_TREE 1308

60 TREE_S_JUNGLE SYM_TREE 1309

61 TREE_S_SINGLE SYM_TREE 1310

62 TREE_S_UPVAN SYM_TREE 1311

63 TREE_TAD SYM_TREE 1312

64 TREE_VAN SYM_TREE 1313

65 TREE_OTHER SYM_TREE 1314

66 WELL_BORE SYM_WELL 1401

67 WELL_DIESEL SYM_WELL 1402

68 WELL_DISUSED SYM_WELL 1403

69 WELL_ELECTRIC SYM_WELL 1404

70 WELL_KACHHA SYM_WELL 1405

71 WELL_MOT SYM_WELL 1406

72 WELL_OPEN SYM_WELL 1407

73 WELL_TUBE SYM_WELL 1408

74 WELL_STEP SYM_WELL 1409

75 WELL_PAKKA SYM_WELL 1410

76 PADDY SYM_OTHERS 2001

Table 2.4: Description of ERROR codes in the polygon features table ADDTTRRPPPPPVVV



14

S. No. TEXT TO BEINSERT/LAYERS

DESCRIPTION CODE (inPAR_ERR field)

1 TEXT_PARCEL ZERO LABEL (0) O

2 TEXT_PARCEL DUPLICATE U

3 1 part of 1, 2 part of 1* CONTINUED PARCEL-1 P

4 LONG PARCEL Z

Table 2.5: Description of PARCEL TYPE codes in the polygon features table ADDTTRRPPPPPVVV

S. No. TEXT TO BE INSERT ONTEXT_STANDARD

LAYER

DESCRIPTION CODE (inPAR_TYPE

field)**

1 GA GRAM ABADI GA

2 AB ABADI AB

3 RI RIVER RI

5 RO ROAD RO

7 WB WATER BODY WB

8 PL PIPE LINE PL

9 IS RIVER ISLAND IS

10 CA CANAL CA

11 RL RAILWAY RL

12 TB TANK BUND TB

13 MA MINING AREA MA

14 GR GRASS AREA GR



15

15 HI HILLY AREA HI

16 SK SMASHAN,KABRISTHAN

SK

17 FO FOREST FO

18 TO ORCHARDS TO

19 SC SCRUB SC

20 PA PARCEL PA

NOTE:

* Part of single khasra separated by other features (like road, pipeline, etc.)

** This is the description of khasra for which a khasra id (parcel no) has already been given. Example,.if the khasra is a water body, having a parcel no 45 in KIDE, then the code in the PAR_TYPEshould be given WB. By default all polygons are parcels 'PA', unless otherwise defined in either ofthe classes given in the above table.

Table 2.6: Field description of polygon features in table ADDTTRRPPPPPVVV

.N0Field/Item


1 CCODE91 18, 18, C 18 digit Census code as mentioned below(DDTTTBBBBRRRRVVVVV)*

2 CCODE01 18, 18, C 18 digit Census code as mentioned below(SSDDTTTTVVVVVVVVWW)*

3 BHUCODE 15, 15, C DDTTRRPPPPPVVV

4 PCODE 12, 12, C DDTTBBPPPVVV

5 KIDE * 20, 20, C Only Single Khasara number in English

6 KIDZ ** 100, 100, C Original parcel number in English



16

7 KIDH *** 100, 100, C Only Single Khasara number in Hindi

8 PAR_ERR 1, 1, C Comments about parcel no. character ex.Duplicate , Continued , Missing etc.

9 PAR_TYPE 2, 2, C Information of the parcel types (As per thecodes specified)

Abbreviation Description

SS STATE CODE

DD DISTRICT CODE

TT TAHSIL CODE

RR RI CIRCLE CODE

PPPPP PATWARI HALKA CODE

VVV VILLAGE CODE

* KIDE This contains the English font or number of khasra number. In case where there is multiplekhasra number separated by comma or forward slash or Hindi alphabet then it should be assignedunique number prefixed by 'Z'. The full number will be provided in KIDZ for Z number only. Ex.A number with 10 should be written as 10H and in the KIDE will be Z nnn.

** KIDZ This item contains the extended khasra number, which cannot be represented in singleEnglish character (i.e. either separated by comma, slash or some Hindi alphabet) in KIDE. Thekhasra number which has an extension in Hindi alphabet should be written as 'H' in place of Hindialphabet

*** KIDH Full parcel number in Hindi. If the parcel number is separated by comma or forward slash,it should be represented in the same way.



17

3. Process Methodology

The Village Cadastral Map sheets depicts field bunds, cart tracks, small nullahs, tanks and other naturalfeatures like roads, railway network, canals & trees etc. After detailed analysis and study, a methodologyhas been developed. The sequence of steps includes:

• Creation of raster village cadastral images

• Digitization of scanned images

• Quality checks

• Rectify errors

• Quality assurance

• Final deliverables



18

Following process to be followed for Database generation:

Computerisation of village Maps

Acquisition of village maps from land record department

Hard copy outputGeneration – (first

Final Hardcopy evaluation &Acceptance

Hard copyevaluation By LRD

Edge matching with neighboring villages(Which is not isolated)

Validation of the individual village by Land Record Authority

Indexing, Coding & Scanning by the Vendor

Tiling cadastral map w.r.t GRID

Digitization (Cadastral sheet)

Attribute data attachment /correction

Softcopy evaluation of cadastral data by LRD

Mosaic & database generation for GIS

Submission ofDeliverables

QA/QC-1

QA/QC-3

QA/AC-4

QA/AC-5

QA/AC-6

QA/AC-2



19

• Making available the village maps

• Indexing, Coding & Scanning

• Tiling map using GRID

• Digitisation of village maps

• Attribute Data attachment

• Hard copy output generation

• Hard copy evaluation by LRD

• Database Generation in GIS environment

• Softcopy validation by LRD in GIS environment

• Final hard copy generation

• Final Hard copy validation

Table 3.1: Various data folder nomenclature for Digitisation of Cadastral Maps

Table3.1: Details of deliverables for each village

CD Volume Nomenclature

DDTTNNNDD* - District Name

TT * - Tehsil nameThe district & Tehsil short-form should beas per the standard list provided by CLR

CD Volumelabel

NNN - Volume label Sequential number starting from 001 to999

Each FOLDER will contain the following files for each village:



20

IDDTTRRPPPPPVVVNN♣.tifSheet-wise scanned file (Rawor where Grid lines NotAvailable)I TIFDDDTTT*

RDDTTRRPPPPPVVVNN♣.tifSheet-wise grid corrected file(Grid lines Available)

DDTTRRPPPPPVVVNN♣.dwgSheet-wise AutoCADdrawing file

IIDWGDDDTTT*

MDDTTRRPPPPPVVV♣.dwgMosaic of drawing file atvillage level

DDTTRRPPPPPVVVNN♣.tifSheet-wise AutoCAD-Arc/Info exchangeable file

III DXFDDDTTT*

DDTTRRPPPPPVVVNN♣.tifMosaic of DXF file at villagelevel

ADDTTRRPPPPPVVV♣ Polygon coverage at villagelevel

lDDTTRRPPPPPVVV♣ Line coverage at village level

IV COVDDDTTT*

(ArcGIS featurefiles unrectified)

PDDTTRRPPPPPVVV♣ Point coverage at villagelevel

V SHPDDDTTT SDDTTRRPPPPPVVV♣ Open GIS Shape files

VI MOSDDDTTRRPPPPPVVV MDDTTRRPPPPPVVV♣ Mosaic coverage at various

levels

* this is where the alphabetical district/tahsil codes has to be used.



21

♣ this is where the numeric codes of the district/tahsil has to be used

3.1 Collecting hardcopy maps/sheets from District Land Records Office

Hard copy village map sheets and other relevant source material are to be collected by vendorfrom the allotted Division/respective District Land Record Office. Vendor would maintainregister/record for receiving the village maps, scanning, digitizing, indexing and returning thesame to the department.

3.2. Indexing & Coding

For scanned output *.tif will be coded as per standard naming convention Eg:(DDTTVVVnn) asrefer below:

DD : District

TT : Tehsil

RR : Revenue Circle

PPPPP : Patwari Halka

VVV: Village

nn : Sheet

3.3. Scanning of Village Cadastral map sheets:

Vendor would design MIS in such a way that the village maps can be indexed to the standardnumbering/naming convention and the same would be used for scanning and further activities. Thiswould enable to keep track of all sources in proper order.

First of all visual inspection of supplied village maps from Department of Land Records is done andinventory work for missing, problematic etc. maps is being carried out.

The source condition, legibility and completeness would be checked. If any discrepancies are observedwith source material, they would be referred back to MP Land Records Department for replacement orclarification.The maps are to be scanned with the following specifications:

• Maps to be scanned at 600 dpi .• The image should be stored in TIFF format *.TIF• The image orientation should be upright.The image should be cleaned and despeckled to remove

noise.



22

• Measured length and width within the bounding box of map should be +/- 0.1% of the mapmanuscript measurements.

• The image should not be skewed or warped.

After scanning the alignment of image orientation (with North arrow)/ and cropping, cleaning etc. are tobe done. The check plot print output after above steps will be a map which will be an exact replica of theprovided paper maps.

3.4 Digitization of scanned Village map sheets

The aim of this task is to digitize all the Khasra & administrative boundaries from the village maps. Inthis phase, data capture of points, lines, and polygons would be done with respect to this documentspecifications and the scanned images.

Data capture would be performed in GIS using internally developed menus with appropriate layer andsymbology.

3.4.1 Polygons, points, and lines will be captured in different layers.

3.4.2 The coincident lines would be digitized only once and used for both the polygons.

3.4.3 The data would be topologically correct for each of the layers.

3.4.4 The features such as wells, temples, trees, village tri-junctions etc. would be digitized as pointfeatures.

3.4.5 The features such as rivers and roads would be digitized as linear features

3.4.6 Logical connectivity of the features would be followed i.e. a river would not join a road.

3.4.7 Centre lines would not be digitized for the double line features / polygons.

3.4.8 The digitized line would be followed in the centre of the raster data.

3.4.9 If the shape of the parcel boundary is shown straight in the image, it would be digitized only withuse of two nodes/ vertices.

3.4.10 There would not be any overshoots, undershoots and duplicate features.

3.4.11 Appropriate symbols would be used as per the source.

3.4.12 The polygon feature would be closed without any dangles or slivers.

3.4.13 The connectivity of the rivers/roads would be maintained except cases where a river feature iscrossing a road feature.

3.4.14 Feature-specific codes would be used for attribution. Each parcel polygon would have a uniqueKhasra number as per the coding scheme provided .



23

The required attribute information such as parcel / Khasra numbers available on the maps would beassigned to the vectorized polygons as unicode texts. The drawing file for each village would be createdin this task. If village information is available in more than one map sheet, all the sheets are edgematchedinto one village drawing (Edge matching, removal of redundant / duplicate text/labels, scale adjustmentsetc.,).

For Vectorization, an approved template would be used with necessary legends, Title, scale bar, northarrow, different layers used for capturing various information, map text details and borders etc. Thesymbols, standard legend, and logo block for use in the Vectorization process would be created as GISblocks and used whenever necessary.



24

4. GENERATION OF DIGITAL CADASTRAL MAPA methodology is developed for generating digital cadastral maps from hard copy maps. Thecomputerization of village maps covers the tasks of procuring, scanning, digitization of all the featuresfrom the village maps.

• Indexing, Coding & Scanning

• Tiling map using GRID

• Digitisation of village maps

• Attribute Data Attachment

• Hard copy output generation

• Hard copy evaluation by LRD

• Database Generation in GIS environment

• Softcopy validation by LRD in GIS environment

• Final hard copy generation

• Final Hard copy validation

4.1 TILING SCANNED MAP USING GRID/MESH

The scanned map might have carried forwarded the errors due to differential scanning, wear and tear,differential shrinkage / expansion. The net result is non-uniform scale at parts of the map, deflection innorth orientation etc. To make the map planimetrically accurate, rectifying the map with the vector grid issuggested.

A vector grid is generated in digital environment. At least 16 – 20 control points are identified on thescanned map as well as on the corresponding vector grid. A transformation model is developed toestablish one-to-one correspondence between the vector grid and scanned raster map. The scanned map isrectified using the transformation model. After rectifying, the vector grid is overlaid on the rectified rasterfile to ensure that there are no gaps between the background grid lines and vector grid lines.

4.2 DIGITISATION OF VILLAGE MAPS

Digitisation is carried out keeping the rectified raster file in the background along with the paper/filmmanuscript if required and any other source that may be of use to the consultant. The output required atthis stage would be the vectorised drawing export format file for each sheet and village level as per the



25

layering scheme, symbology, color coding specified below along with the metadata information andquality control forms.

4.2.1 Creation of template: Before starting of the digitization, a standard template is created. In thetemplate the layer name, line type and color for each feature present on the map is standardized. Thissystem helps where a number of village maps is needed to be mosaiced at village level. This processmaintains uniformity in all the maps, which are to be digitized.

4.2.2 Creation of symbols: A symbol library is made which contains the various symbols, and isshown in a village map. The main intention behind this is to keep its uniformity in all over the villagesthat has to be digitized. The Symbol library used for this project is attached under section 5..

4.2.3 Method of Digitization : This process can be done through 3 methods i.e. Manual method, Semi-automatic method and Automatic method. As per the condition of scanned map digitization method isadopted. In this process all the features are captured on the respective layers. After completion ofdigitization symbols are inserted as per their location on cadastral maps. Text is inserted for Parcel/KhasraNumber and for various other details present on the map, (such as village name, names of adjoiningvillages, scale etc.). As the text is in local language, gist supported font (DVB-TTSurekhEN) is used.

The following criteria is adopted for digitization:

• Digitization is done in unit as mentioned in map sheets.

• Digitization is done at a comfortable zoom level so that vector line follows through the center ofraster width.

• In the first step village boundary is digitized and it is seen that polygon is complete (as in case ofvillage having single sheet)

• In places where village boundary passes through river it is digitized on a layer‘Village_Boundary_Stream’.

• Utmost care is taken to see that linear features such as roads and rivers are continuous.

• Font size for parcel text is kept 1.8 mm where as for layers Text_Mapin and Text_Mapout it isbetween 2 mm – 4.5 mm.

• Utmost care is taken to maintain continuity of polygon and linear features.

• As parcel lines are usually straight there should be minimum nodes in a parcel edge.

• The map prepared should be free from dangles, overshoots, undershoots etc.



26

• Color-coding for the hatch pattern is given as provided on a village map and is provided byDistrict centres.

TEXT LAYERS

S.No

Layer Name Layer Description Color Size

1. TEXT_MAPIN All text inside village boundaryexcept khasara / Parcel nos.

7(White) 2mm

2 TEXT_MAPOUT All text outside village boundary,texts showing Road direction

7(White) 4.5mm

3. TEXT_PARCEL Parcel / Khasara text 7(White) 1.8mm

TEXT STYLESS.No

Style NameFont Height Remarks

1. TEXT_MAPIN DVB-TTSurekhEN

2mm Hindi Text

2 TEXT_MAPOUT DVB-TTSurekhEN

4.5mm Hindi Text

3. TEXT_PARCEL DVB-TTSurekhEN

1.8mm Hindi Text

4 TEXT_TS Times NewRoman

2.5mm General Purpose Englishtext



27

LINE LAYERS

S.No

Layer Name Layer Description Color?

Line type Size

1. LINE_CANAL Single Line Canal 4 Continuous

2. LINE_CARTTRACK Double Linecarttrack

232 Dashed LT scale = 5

3. LINE_EMBANK Embankment 7 Continuous

4. LINE_FOOTPATH Foot Path 1 Dashed LT scale = 5

5 LINE_OTHERS Other Lines 1 Dashed2 LT scale = 5

6 LINE_PADDY Paddy Lines 9 ACAD_IS003W100

LT scale =0.05Width=0.1

7 LINE_PIPE For pipe lines 5 Continuous

8 LINE_RAIL For railway lines. 1 Rail LT scale = 5

9 LINE_RILLS 5 Rills LT scale =0.05

10 LINE_TRAVERSE_STATION

Line connectingtraverse station

5 Continuous

11 LINE_STREAM Village boundarywhich passesthrough river

7 Dash dot Width = 0.5

LT scale =10

12 LINE_V_DIVIDE Extension of villageboundary line

7 Divide Width = 0.5

LT scale =10



28

13 LINE_V_BOUND Village boundaryline

7 Continuous Width = 0.5

14 LINE_WATER Single line Streams 5 Continuous

POLYGON LAYERS

S.No Layer Name Layer Description Color Line type

1 POLY_CANAL Double Line Canal 4 Continuous

2 POLY_ EMBANK Outside & Insideboundaries Of hatch

7 Continuous

3 POLY_FOREST For forest areapolygons

76 Continuous

4 POLY_HATCH For hatching hillyareas

5 Continuous

5 POLY_OTHERS Any other polygonFeatures

1 Continuous

6 POLY_PARCEL Parcel Lines 6 Continuous

7 POLY_PARCEL_2 Dashed Dot Lines 6 DashedDot (W=0.2,LT Scale=5)

8 POLY_FOREST_BOUND_PARCEL

Forest Boundary 76 Continuous

9 POLY_WATER_PARCEL

Common for Parcel& River

5 Continuous

10 POLY_ROAD_PARCEL Common for Parcel 1 Continuous



29

& Road

11 POLY_RAIL Polygon surroundingrail way lines

7 Continuous

12 POLY_PIPE Pipelines 5 Continuous

13 POLY_ROAD For Road Lines 1 Continuous.

14 POLY_ROAD_RIVER Common for Road &River

1 Continuous

15 POLY_ABADI_PARCEL For all AbadiPolygons

6 Continuous(W=0.4)

16 POLY_WATER For Double LineRivers

5 Continuous

17 POLY_RAIL_PARCEL Common for Rail &Parcels

7 Continuous

NOTE :

* The Lt Scale can vary according to length of the line.

OTHER LAYERS

S.No Layer Name Layer Description Color Line type

1. OFF Elements for completing the polygons 1 Continuous

2. SYM_LOGO Logo 1

3. LEGEND Legend 1 Continuous

4. IMAGE Layer for inserting scanned image 114 Continuous

5. JOIN_LINE Joining lines between sheets 40 Dashed2 (LTScale=5)



30

POINT LAYERS

S.No Block Name Layers PIN Color

1 ABADI SYM_ABADI 0101 16

2 ABADI-1 SYM_ABADI 0102 16

3 AIRPORT SYM_INFRASTRUCTURE 0201 1

4 INDUSTRY SYM_INFRASTRUCTURE 0202 1

5 BRIDGE SYM_INFRASTRUCTURE 0203 1

6 BRIDGE-1 SYM_INFRASTRUCTURE 0204 1

7 BAZARPETH SYM_AMMENITY 0301 174

8 COLLAGE SYM_AMMENITY 0302 174

9 FGUESTHOUSE SYM_AMMENITY 0304 174

10 GUESTHOUSE SYM_AMMENITY 0305 174

11 HOSPITAL SYM_AMMENITY 0306 174

12 HOTEL SYM_AMMENITY 0307 174

13 IGUESTHOUSE SYM_AMMENITY 0308 174

14 MARRIAGEHALL SYM_AMMENITY 0309 174

15 OFFICE SYM_AMMENITY 0310 174

16 PETROLPUMP SYM_AMMENITY 0311 174

17 POSTOFFICE SYM_AMMENITY 0312 174

18 POLICESTATION SYM_AMMENITY 0313 174

19 SCHOOL SYM_AMMENITY 0314 174



31

20 TANK_OVERHEAD SYM_AMMENITY 0315 174

21 TELEPHONEOFFICE SYM_AMMENITY 0316 174

22 THEATRE SYM_AMMENITY 0317 174

23 BUILDING SYM_CONSTRUCTION 0401 7

24 COMPOUND SYM_CONSTRUCTION 0402 7

25 WASAHATH SYM_CONSTRUCTION 0403 7

26 CHATTAN SYM_THEME 0501 84

27 GRASS SYM_THEME 0502 84

28 HILL SYM_THEME 0503 84

29 CHURCH SYM_WORSHIP 0601 7

30 GURUDWARA SYM_WORSHIP 0602 7

31 MOSQUE SYM_WORSHIP 0603 7

32 TEMPLE SYM_WORSHIP 0604 7

33 FB_S_STONECIR SYM_STONE 0701 14

34 FB_STONECIR SYM_STONE 0702 14

35 FB_STONESQ SYM_STONE 0703 14

36 STONESQ SYM_STONE 0704 14

37 TRI SYM_STONE 0705 14

38 STONE_CIRCLE SYM_STONE 0706 14

39 STONE_OTHERS SYM_STONE 0707 14

40 HISTORICALPLACE SYM_TOURISM 0801 7



32

41 MONUMENT SYM_TOURISM 0802 7

42 STATION_TETRA SYM_TRAVERSE_POINT 0901 5

43 STATION_TRI SYM_TRAVERSE_POINT 0902 5

44 ITS (Internal Traverse Station) SYM_TRAVERSE_POINT 0903 5

45 TS(Traverse Station) SYM_TRAVERSE_POINT 0904 5

46 KABRISTAN SYM_SAMSHAN 1001 10

47 SAMSHAN SYM_SAMSHAN 1002 10

48 POLE_ELECTRIC SYM_COMMUNICATION 1101 7

49 POLE_TELE SYM_COMMUNICATION 1102 7

50 ARROW_RIVER SYM_ARROW 1201 7

51 ARROW_TEXT SYM_ARROW 1202 7

52 TREE_SINDHI SYM_TREE 1301 7

53 TREE_COCONUT SYM_TREE 1302 7

54 TREE_OTHERTREE SYM_TREE 1303 7

55 TREE_MANGO SYM_TREE 1304 7

56 TREE_B_SINGLE SYM_TREE 1305 7

57 TREE_B_UPVAN SYM_TREE 1306 7

58 TREE_IMLI SYM_TREE 1307 7

59 TREE_PADIT SYM_TREE 1308 7

60 TREE_S_JUNGLE SYM_TREE 1309 7

61 TREE_S_SINGLE SYM_TREE 1310 7



33

62 TREE_S_UPVAN SYM_TREE 1311 7

63 TREE_TAD SYM_TREE 1312 7

64 TREE_VAN SYM_TREE 1313 7

65 TREE_OTHER SYM_TREE 1314 7

66 WELL_BORE SYM_WELL 1401 162

67 WELL_DIESEL SYM_WELL 1402 162

68 WELL_DISUSED SYM_WELL 1403 162

69 WELL_ELECTRIC SYM_WELL 1404 162

70 WELL_KACHHA SYM_WELL 1405 162

71 WELL_MOT SYM_WELL 1406 162

72 WELL_OPEN SYM_WELL 1407 162

73 WELL_TUBE SYM_WELL 1408 162

74 WELL_STEP SYM_WELL 1409 162

75 WELL_PAKKA SYM_WELL 1410 162

76 PADDY SYM_OTHERS 2001 1

4.3 ATTRIBUTE DATA ATTACHMENT

Attribute data for each parcel is attached in the text layer TEXT_PARCEL. All the outside villageboundary, text showing road direction are depicted in TEXT_MAPOUT layer and all text inside villageboundary except parcel number is depicted in TEXT_MAPIN.

4.4 HARD COPY OUTPUT GENERATION

Hard copy color output is generated using the template provided by CLR. The first hard copy is generatedat the original scale of input map for each sheet. Good quality paper is used for printing the digitized map.The color scheme and thickness should be according to the standards.



34

4.5 HARD COPY EVALUATION BY LRD

The officers from land records department validate the hard copy color output. The output will bevalidated completely by the LRD officers for physical dimensions, parcel size, shape, numbering, featurecoding etc. The corrections are marked on the output and will be provided back to the vendor toincorporate them in the digital data.

4.6 DATABASE GENERATION IN GIS ENVIRONMENT

Village level mosaic is done at village level to join two or more parts of village to form a completevillage. Edge Matching is done by bringing two different maps of same village into same file andmatching their edges with reference to grid and features on the maps. Continuity should be maintained forall the features at the edges. Care is taken to minimize dangles and label errors. On screen check is doneto check the common edge between the mosaic maps. One has to ensure the complete polygon featuressuch as parcels, continuity in line features such as river, roads etc. After incorporating the corrections, thedigital data will be converted into Arc .Shp or Arc GeoDatabase environment.

4.6.1 Map Cleanup and topology building:

Map cleanup at this stage is to be done to remove errors such as dangles, undershoots, duplicate objectsetc. If topology is being built in a s/w like AutoCAD maps then the layers have to be categorized into 3feature i.e. point, line and polygon. The specifications for each of the type of coverages are indicatedbelow.

4.6.2 Polygon Feature Specificationsa) The parcel boundary should be digitized in such a manner that the resulting vector line falls in

the center of the raster data image element being vectorised.

b) The parcel boundaries are generally straight hence it should be digitised using only 2 nodes/vertices in keeping with the shape of the polygon.

c) The feature should be digitised such that there is no overshoot or undershooting of arcs orduplicate arcs.

d) The feature should be captured with specified symbol.

e) The feature should be digitised with minimal number of vertices while at the same timemaintaining the smoothness or angularity of the lines as the case may be.

f) The feature should be a closed polygon without any dangles or slivers.

g) Each polygon should have a unique PIN as per the coding scheme indicated below.



35

h) The tolerance values for arcs, node snapping and vertices should be such that the features snapwithin the pixels defining that feature and do not snap out side.

i) All features like parcels, roads, rivers, etc which form polygons are to be digitised and coded asper the coding scheme.

j) The connectivity of the rivers/roads is to be maintained and should not be disjointed asillustrated below except where a river feature is meeting a road feature, there should be nodangles or open ended polygons, especially at the boundaries.

k) One edge in such cases may be the parcel defining edge.

l) The label should be placed in the center of the feature.

m) All the polygons forming parcel features should be digitized with the symbols specified, as alsoother features like roads, rivers, etc. with symbols as specified below.

n) The centerlines of linear features are not to be digitized. Also single line feature cutting acrossparcels are to be ignored in the polygon feature class to maintain shape and area of parcel asshown below.

o) Nodes are to be added wherever they are depicted on the map with ∇, Ο or any such symbolsdepicted on the parcel boundaries.

p) Whenever an area features cuts across a parcel, it should be digitized as it is and coded as perthe coding scheme.

4.6.3 Point Feature Specifications

The feature shown on maps as points like wells, temples, trees, etc. are to be digitized as point featuresthe digitising rules and coding scheme are given below:

• The feature should be digitized as a point placed at the center of the raster image defining it.

• There should only be one point at one location

• Each feature should have an unique id.

4.6.4 Line Feature Specifications

The linear features shown as single line arcs on the map as well as linear double line features like rivers,roads, pipelines, etc. are to be digitized and compiled into the line coverage for the village.



36

The single line arc features whether shown as continuous lines or broken lines are to be captured from themap image. In addition to this the double line roads, rivers, pipelines etc. from the polygon coverage arealso to be put into the line coverage.

The feature coding guidelines are given below:

1. The river/roads depicted on the image represent the outside edges in case of double line features andshould be digitized as such. The resulting vector should not deviate from the pixels defining it.These features should be captured only once and copied into the appropriate layers before buildingthe topological relationships.

2. The feature should be vectorised in such a manner that the shape is captured and retained as it is.

3. The feature should be vectorised using optimum member of nodes/vertices so that the shape isretained and does not appear jagged.

4. The connectivity of the features should be logical with respect to each other in a river should not endor join on to a road, etc.

5. At crossings the features should be digitized in such a manner that they do not cross over asillustrated below:

6. In case of single line features, they should be captured as a single continuous feature from one end ofthe feature to the other end without break.

7. In case of double line features the centerline should not be digitized.

8. There should not be any gap between two connecting features nor any over shoots, the features shouldbe snapped to connecting features.

4.7 SOFTCOPY VALIDATION BY LRD IN GIS ENVIRONMENT

Officers from Land Records Department using the customized package, developed by vendors, will carryout the soft copy validation. This validation is carried out to ensure the shape and number of therespective parcel and the total number of parcels & other features in the village.

To ensure there are no parcels with duplicate labels and zero labels, an A-4 size paper print of eachvillage depicting duplicate and zero labels is taken. Land records officers validate this map andcorrections are incorporated in the softcopy products.



37

4.8 FINAL HARD COPY GENERATION

After the softcopy validation by LRD, final hard copy color output is generated at 1:4,000 scale. Theoutputs are generated at sheet level as per specification to ensure the durability of the output and makingit convenient for cloth mounting or lamination.

4.9 FINAL HARD COPY VALIDATION

The final hard copy is validated by the LRD officers and after found suitable for use will be signed by theconcerned officer making it exact replica of the original map with value addition in digital environment.

The uniformity in layers, line type, color, units etc. during digitization will be maintained and for this thestandard template to be used and the entire feature are to be captured in their respective layers as pertemplate.

Vendors have to provide one hard copy (sheet wise) to CLR for QAS and on these hard copy prints errorswill be highlighted as shown below:



38

4.10 Edgematching of sheets within a village

On the above check plot prints the concerned LRD Office will provide the QAS1 feedback andvendors have to incorporate all remarks/ feedback and do the all-necessary corrections in the digitaldata. Once all corrections at individual sheet level are incorporated then edgematching the individualsheets to get a village level output as shown :

4.10.1 The village map sheets would be edge-matched based on the village index map.



39

4.10.2 If the displacement is more than 5 mm, then the feature would not be edge matched. Insuch cases, vendor would place a flag and intimate to the department for theirclarification to such queries. Upon receiving the resolution, vendor would incorporate thesame in the data.

4.10.3 Care would be taken to eliminate duplicate features, dangles, slivers, text and labels.

4.10.4 If the feature boundary is common to road and river, care to be taken that there would notbe any sliver polygon / gap.

4.11 Cleanup and topology building

4.11.1 All the logical checks would be performed on seamless data. Use suitable (like AutoCad)map functionalities to fix the topological errors such as dangles, duplicates, pseudo nodes,intersection errors, overlap errors and slivers. The fuzzy tolerance and dangle lengthrequired would be used for cleaning the data.

4.11.2 Upon execution of data cleanup tool the following type of sample errors would beidentified and corrected manually.

4.11.3 Topology which will be built after completion of cleaning is as below:

Polygon topology: Parcel, Village boundary, river, road etc.

Linear topology: Stream, cart track etc.

Point topology: Tri-Junction, grass, trees, wells, traverse points etc.

4.12 Data Translation

4.12.1 The graphical data would be converted from GIS software into the personal geodatabaseby using data migration tools.

4.12.2 The list of records/files will be verified to make sure that all the data is convertedsuccessfully. As soon as the migration is finished, the created error logs would be fixed.Also check the completeness of the data translation through internally developed softwareroutines.

4.12.3 These routines would ensure that all the features are translated by comparing the sourceand the target data. After the successful completion of the migration process, it can benoted that all the data is present in the geodatabase without losing any information.

Feature coding for polygons i.e .,preparation of coding scheme for different features present in maps,generation of code for whole tehsil and structure for respective table will be built accordingly. For eachparcel unique ID will be given keeping in view of their use for different application.

4.13 Quality Control

4.13.1 Visual checks include verifying each tile of digital data with reference to the source databy one-to-one comparison. Missing / extraneous features would be identified andcorrected with reference to the source data.



40

4.13.2 Quality control checks will include edge matching, topology checks, outside neat linecheck, incorrect extent check, double point check, pseudo/dangle node check etc. Theerrors identified in the data would be corrected accordingly.

4.13.3 Plot QC will be basically concentrating on identifying any errors related to below aspects:

• Missing features

• Additional features

• Wrong placement of features

• Placement of features in wrong scale

• Wrong shape of features

• Incorrect attributes

• Incomplete attributes

4.13.4 The digital data would be evaluated using the following guidelines / parameters.

4.13.5 Checking for zero/no attribute

4.13.6 Checking the Vectorization errors like slivers and dangles.

4.13.7 Verification of edge matching between adjacent maps

4.13.8 Upon receiving the resolutions from District office of MP Land Records Department,required corrections would be incorporated in the digital data.



41

5. INDICATIVE SYMBOLOGY FOR CADASTRAL MAPS



42



43



44



45



46



47



48



49

Documents

Design Document - Landrecords Madhya Pradeshlandrecords.mp.gov.in/Circular08/cr0808_designdoc.pdf · Design Document 2008 Design Document ... • On sample basis, files of individual