@ THETGRNS FTE Digitization of Cadestrol Maps and Its Linkoges to Revenve Records in U.P. uftfirte-9 “Digitization of Cadastral Maps & Linking with RoR Data of Package----- of Uttar Pradesh” Ref: - Tender no-344/1-18-2014/ka cell/19/2005 Dated-16-07-2014 Data Design, Specification/ Structure & Format Document (A Format & Guidelines Document For Executing Agencies) Board of Revenue, Lucknow (Uttar Pradesh)aE TISTE ETF _pigiization of Cadestral Mapes and Its Linkoges to Revenue Records in UP. 3. 4, INDEX PROJECT OVERVIEW 1.1 Scope of work Data Design, Structure & Format 2.1 Introduction. 2.2 Procedure for building the database. 2.3 Database Construction guidelines. 2.4 Input for the Project. 2.5 Quality Assurance. Process Methodology 3.1 Collecting Hardcopy, maps/sheet 3.2 Indexing & Coding of cadastral maps 3.3 Scanning of village cadastral map sheets 3.4 Digitization of scanned Village map sheet, Standard for data structure 4.1 Various data folder nomenclature. 4.2 Each folder should contain the following files for each village 4.3 Standard DWG (Auto Cad Drawing File) Layer And the block name as part of digitization template, 4.4 Reference of standard symbols in use taken from U.P Revenue Manual. 4.5 Standard Legend 4.6 Field description of Line features in shape tables. 4.7 Codes of Line Feature in the line shape data base file. 4.8 Field description of Point features shape in tables. 4.9 Design and Structure of the POINT spatial topology. 4.10 Description of error code in the polygon feature tables 4.11 Description of parcel type code in the polygon feature, 4.12 Field description of polygon features shape in Database tables 4.13 Field deseription of polygon features shape in tables Database tables 5. Deliverables to be supplied by Service Provider. 5.1 Hard copy Prints 5.2 Soft copy on Hard disk. 5.3 support 6. INPUTS/SUPPORTS REQUIRED FROM THE DEPARTMENT 6.1 Hard copy original Maps 6.2 Details from NIC 6.3 Support1, Project Over view Board of Revenue, Govt. of Uttar Pradesh, Lucknow has decided to digitize the cadastral maps of all the villages and store it in the form of veetor Data with a view to preserve the deta available in the cadastral maps, to feclitate its casy storage, retrieval and easy access to the public and functionaries of the Department 1.1Scope of Work With reference to Tender no.344/1-18-2014lka ecll/19/2005, dated 16-07-2014 for Digitization ‘of Cadastral Maps & Integration with RoR data (With BHUNAKSHA software) in package which includes following major activities:- * The vendor shall deploy adequate hardware, software, manpower and other infrastructure to ensure the time bound completion of the project The vendor will be required to set up the complete environment (ic. power backup, furniture, TT hardware, paper & related supplies and manpower ete.) on vendor's premise at divisional headquarter. + The vendor shall deploy the things required for quality check at distrit level like light ables ete. in the beginning of the workljob. * The Board of Revenue or its representative reserves the right to conduet random checks for quality assessments of the sean. The digitization of cadastral maps will help to create database of revenue maps in digitized form and will get linked up with the existing database of land records BHULEKH. Creation of digitized maps will include the following activities:~ * Scanning of village Maps. + Indexing and Veetorization. Linking of revenue database with existing Bhulekh software. + The output of the whole process mentioned above should be GIS ready. ‘Training of staff at Board of Revenue and district level. + Scanning and Digitization Sr. Particulars Description inal Map Seale | 140007:3960 2 | Seanning 300 DPI black/white for normal & 300 DPT for damagedinot clear maps, image storage in .jpeg format, orientation upright, | image should be cleared and free from noise. Image should not | be skewed or warped. Tiling scanned maps using grid/mesh Final printout of digitized maps must be in color. For checking purposes it can be printed in black/white. 3° | Editing/Clearing | Relocation of misplaced features, removing undershoot Data overshoot, brighiness and contrast, color balance, 4 | Digitization of Tn layers —area, point and line. scanned eadastral | maps - eee‘Accuracy _7_| Database standards | Standard RDBMS 8 Significant features ona Fins should be marked by nodes labels | marking on the map, topological completeness. ‘Vector data and print should be exacily (1:1) matched with vith the _ original map. Spatial Database 2 Completion of — | Topology 10 | Quality, Inspection and Completeness 1 | Output format 12 Attribute Data attachment “14 Layers to be | computerized 16 | Sofiware 7 [ Outnut Format 18_|_ User Manual ' Grouping of various features in different classes! coveraxe. all control points, " Polygon closed properly, no undershoov overshoot, polygon should have individual and unique tabet Printout of digitized maps shall be handed over on regular basis | to the district authorities for 100% checking with the original cadastral map. Any deviation would be marked by the checking team and retumed to the Vendor for necessary conection. In shape file (*.shp), hx and .dbf, Non map feature sheet | heading plot sumer, legends, conventional signs, village code | __match with Bhulekh code. | Matching vector data with ROR data and quality mismatch plot area | Village-level mosaicing should be done by jeining the 7 | individual map sheets of the village to form a complete village i | |) [Diller faves Goin ine arene used Tor map ceinpOsTCN | Line layer arc required for the map composition past, while | area layers are mainly required for both map checking and | composition. | (ii) | All legends shown on map would be digitized layer wise | | like administrative boundaries of a revenue village with | name of village, tehsil and district ii) | Plot boundaries with plot numbers. Government land like Gaon Sabha, Chak Road, | ete Road yetwork along with fype of road. Railway network. Major water bodies ets, Scanned map on Portable USB Hard disk first & second printout on tracing papetishect 1:1 digitized map on USB Harddisk, databases of digitized maps, the final printout shall be made on 75 micron polyester transparent wet coated on both sides, digital map connectivity with BHULEKH (ROR | Sontware) = _ | Sofie fog sz 7 ia he | attribute data should be such i | __compitable with Bi Data is to be supplied in the ES mat mxdipdf efc. may be sup aplete in two seis printed and on Penidri 19 | Workshop/Training) | 19.1 Workshop at district level for accessing digitized cadastral | ‘Technical Support QS : maps along with the attribute data at district. 19.2 Cpesational training for 3 persons at Board of Revenue level for accessing digitized cadastral maps along with the attribute data at district.a TS ESE! pigitzation of Cadastral Maps and kts Linkages to Revenue Records in U.P. Operational training for 5 persons as a master trainer per district f or accessing digitized cadastral maps along with the ttribute data at district, 19.4 01 technical manpower at cach district level for technical support after completion of work and 01 technical manpower at Board of Revenue level for six months. 20 | Note .1 The scanning activity will need to be done in such a manner that all the contents of the original maps are clearly "legible" and "readable". 20.2 NLRMP technical manual of Department of Land Resource, GOI must be considered in Scanning & Digitization 2. DATA DESIGN, SPECIFICATION/STRUCTURE & FORMAT 2.1 Introduction A data design provides a comprehensive architecture for the database to be viewed in it's entirely and evaluate how the various aspects of it need to interact. A good design results in @ 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 date ‘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 and technology to work together, they encourage efficiency and effectiveness, help reduce costs in investments, protect data against technological change and lead to availability of accurate, complete and current data. Tools, applications and data aftect each other and standards are established with this 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 have to take care that digitization is as per the standards, ‘The inputs are subject to validation at each stage, and will include qualitative as well as quantitative checks for input accuracy The creation of a clean digital database is the most important ond complex task upon which the usefulness of the database lies. Two aspects need to be considered here; one is its unique identification for associating attributes that link to the records and second is the geographic data necessary 10 define where the parcel of land or for that matter any other features is located under present scope second component is not part of the scope of work. At every stage, there will be nevessary and proper data verification to ensure that the resultant database is as free as possible from error. Errors would generally be of the following types. ‘+ Spatial data is incomplete or double Khasra ID or missing/blank Khasra ID ‘* Spatial data is in the wrong place ‘© Spatial data is at the wrong scale& 24 25 FRE, SALE Dighization of Cadastral Mops and Its Linkoges to Revenue Records in U.P. © Spatial data is distorted ‘© Spatial data is linked to wrong attributes, ‘+ Non-spatial data is incomplete Spatial data on early mismatching w.rt. original Cadastral map prints. For evaluating the digital data the following guidelines/parameters would be checked © Attribute verification providing the correctness of feature coding by listing it out and comparing with the manuscript maps. Complete checking of all pareels for shape & form and listing of polygons with zero/no attribute, ‘© Verification of scale/units (i.e. wart input maps) Verification of registration points and RMS error for the transformation model. Checks for digitization errors like slivers, dangles, overlapping lines and Dimension errors. © Checks for mesaicing of maps and verification of edge matches with adjacent maps by displaying them side-by-side. DATABASE CONSTRUCTION GUIDELINES Building village cadastral map database in GIS environment for planning and implementation of various projects at the miero-level. This document lists out in detail the various processes and specifications based on the following points. The village maps received from district authorities will be scanned for further processing, + Generation of true copy(ie, |:1 replica or original hard copy map) ‘© Thon the approved scanned village maps will be vectorized / digitized, © Digitized village cadastral maps will be edge matched wherever required and mosaiced to form a layer in the GIS database at the village level. «A primary key field will be generated which will be amenable to attribute data attachment with RoR data. ‘© Final output hard copy prints generated as per documents defined under REP. © Generating analytical reports on area in the RoR with respect to the digital map so as to help in data correetion, both texts as well as map. INPUTS FOR THE PROJECT ‘¢ Hardcopies of cadastral maps + Meta data and general attributes RoR data ete. QUALITY ASSURANCE ‘The project will have well defined and set procedures for quality assurance of the database. The QC procedures are both qualitative and quantitative, All scanned & digitized output data or hard copy maps ‘generated from digitized data by the Vendor will have to go through the quality cheek procedure before acceptance. ‘The followi 1s regarding quality assurance have to be adhered to by Vendor and the 1g ap same are to be verified by the designated technical team from District Authorities «The quality assurance of the data will be carried out by using automated routines as well as manual checks, as required at Vendor end prior to generation of hard copy maps. This will include checks for topological correctness, unique feature coding, and completeness of data, naming conventions, accuracy and errors, + The quality assurance form duly filled has to be submitted along with the soft copy data geeTHEIEENS EEE Digitisation of Codastrol Mops and Its Linkages to Revenue Records in UP. ‘+ Data not complying with the standards and accuracy specifications will be rewmed back to Service Providers for necessary corrections 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 preseribed range, the data will be accepted. ‘+ The quality assurance should comply with the following aspects (1) positional accuracy, (2) Attribute accuracy, (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 District Authorities, + On sample basis, files of individual villages and the mosaic will be digitally quality checked by LR-Dept ‘The criteria and acceptance levels for various parameters are given below: i. File naming 100% Directory structure 100% iii, Data readability 100% iv, Data structure 100% ¥. Data format 100% vi. Topology 100% Vii. Auribute correctness 100% viii, Atribute completeness 100% ix. Data mosaicing 100% At each step of the process, adopted for computerization of the village map, quality cheek has to be applied to ensure error free database generation. ve eoDigitization of Cadastral Mops ond ts Linkages to Revercve Record i Phase-t Following process to be followed for digitization and digital database generation: Flow Chart [ vate of oiginal Map w rt pedeoad cif date by Revenve Oia ‘Acquistion of wlage maps (Tefs-wise) irom Revere Oeil by the BORNCY ‘Agensy to mske Inventory forall avaliable rape for feliowing: (a) Prysiel conden of maps ie toldentty made those are in Slaptated condtion (6) Coding /ndexing 26 per SODINIC-Code fat (6) Identity completaireamplatevilages ‘Agency te Report concerned Revenue Offs on bouesiiliied above, for ary ‘Scanning ofa idexea rao sheets (@) Tranofering lea! reference ras on maps wrt. digital gr {@) Scanning &ruboer-sheetng Yo manimae searing eer (©) Generate frst pit of ssanned map for verfizaton on tacingshect [awe ) “ary decrepaney noited by |) Revenue Ofteals in tat case | true ecanring prococe to repeat again by i agency “Aoproved print of seated map tebe gven bask to Agsney ‘Agency to ge prt of cigh'sed map fr verfeaton on tracing paper Ye ‘Revere Oftoelas{CRY Dightzation of Cadastral Maps and les Linkages to Revenue Records in UP. ssa Vlard copy evaluation by Revenue Oficls w.rt. crignal map prowded fer seanrirg Incorporation ofall emarkalerors -suggaeted by Revenue Ciel ‘Masaiceng of agrized data at viage: ‘neteut of Approved Digtize | fevalitrequrestnen prepare Stape [e— | Cadastral Map on stpulatec (Sip) fle a wilage vel | Materale Tinkina wan ROR using Bhu-Naksha sofware provided by NC (Generation of data mematzh repote using Bh Nakina software _—___+__. ‘Where ever required, correstone of mimatch reports wth due caroutation with Local Revenue Offvials |--[_ QA/QC-8 ‘Re-vaicaton of msmaich date by bath concerned revenue offciale & Agenoy Final test shecklacceotance fest of dgized data by Revenue OTs Final ard copy prints oF approved Updated datized (Gaeastral map on ttpulsted Matas ‘Submission of Fira Deliverables Ate: Vendors espnbe fr tcarperaten of information updsted by dts Revenue Oi 8 the aeeareenterubatuen vit besesedars ec ttre vv -9-D ceavive: FESS _ Digitization of Cadastre! Mops and ts Linkages to Revenue Records in UP. 3. Process Methodology The Village Cadastral Map sheets depicts field bunds, cart tracks, small Nala, tanks and other natural features like roads, railway network, canals & trees etc. After detailed analysis and study, a methodology has been developed. The sequence of steps includes: + Scanning of village cadastral maps. ‘+ Digitization of scanned cadastral maps. ‘+ Mosaicing up to village level and linking with RoR database © Quality checks © Rectify errors © Quality assurance Final deliverables 3.1 Collecting Hardcopy, maps/sheet Department of Revenue and local administration shall provide Latest Chakbandi/Bandobasti Cadastral map sheets to the Vendors at Vendor's Divisional/District Project Office for scanning and subsequent processing as per project plan submitted by the Vendor. AO or As per actual Map should be treated as one unit and thus any oversized maps should proportionately calculate to its next whole integer for billing purpose. 3.2. Indexing & Coding of cadastral maps: For scanned output * jpg will be coded as per standard naming convention Eg(DDDTTTTTVVVVVVNN) as refer below: DDD: District TITTT: Fahsil VVVVWV: Villoge ‘NN: Sheet Number Note: - Six digit village codes to be taken from census-2011 3.3. Scanning of Village Cadastral map sheets: Service Providers will use naming coding scheme or design MIS in such a way that the village maps can be indexed to the standard numbering/naming convention and the same would be used for scanning and further activities. This would enable to keep track of all sources in proper order. First of all visual inspection of supplied village maps fiom Revenue officials is to be done and inventory work for missing, problematic maps etc. is to be carried out. ‘The source condition, legibility and completeness would be checked. If any discrepancy is observed with source material, that would be referred back to District Revenue Officials for replacement or clarification. ‘The maps have to be scanned with the following specifications: -10-Dighization of Cedastral Maps and Its Linkages to Revenue Records in U.P. + Maps to be scanned at 300 dpi (color) © The image will be stored in JPG format * jpg © The image orientation will be upright. The image will be cleaned and despeckled to remove = Measured length and width within the bounding box of map will be +/- 0.1% of the map ‘manuscript measurements, + The image will not be skewed or warped. Afier scanning, alignment of image orientation (with North arrow)’ and cropping, cleaning ete, have to be done. Tiling map using GRID ‘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 in north orientation cic. To make the map planimetrically accurate, rectifying the map with the vector grid is suggested. A vector grid is generate digital environment. At least 9- control points will have to identify on the scanned map as well as on the corresponding vector grid. A transformation model will be developed to establish one-to-one correspondence between the vector grid and scanned raster map. ‘The scanned map has to be rectified using the transformation model. After rectifying, the veotor grid has to be overlaid on the rectified raster file to ensure that there are no gaps between the background grid lines and vector grid lines, Following steps have to be followed: i. Reference Veetor grid with known x-59 Jem, y- 44.5em - dimensions generated. ‘Then 4 points have to be marked at rectangle comer and then the rectangle is further divided to get S-other control points at the intersection points. $ 45ems. $ & aa 60ems. -l-rrr gees use coset eyo ms Later toon cr iicBefore scanning transfer the same reference points from the veetor grid on the cadastral maps ai proceed for seanning. | JF agr age gener eT® corse E_oypaeon ef ede! Mapa koe t Reena Recid lo UP Grid is then overlaid on the scanned Cadastral Map iv, Scanned map is then rectified jpeg grid with overlaid grid eens uDigitization of Codastiol Maps ond Its Linkoges to Revenue Records in U.P. 3.4 Digitization of scanned Village map sheets The aim of this task isto digitize al! the Khasra polygons & administrative boundaries fiom the villege maps. In this phase, data capture of points, lines, and polygons features will have to be done with respect to this document specification and the scanned images. Data capture is to be performed in GIS environment using internally developed menus with appropriate layer and symbology 3.4.1 Polygons, points, and lines have to be captured in their respective layers. 3.4.2. The coincident lines have to be digitized only once and used for both the polygons. 3.4.3 The data should be topologically correct for each of the layers. 3.4.4 The features such as wells, temples, trees, village trijunetions etc. have to he digitized as point features, 3.4.8 The features such as rivers and roads have to digitize as linear features. 34.6 Logical connectivity of the features have to be followed ie. a river will not join a road. The connectivity of the rivers/rvads has to be maintained except cases where a river feature is crossing a road feature. 3.4.7 Centre lines will not be digitized for the double tine features / polygons. 348 The digitized line will be followed in the centre of the raster data 3.4.9 If the shape of the parce! boundary is shown straight in the image, it should be digitized only with use of two nodes! vertices 3.4.10 There should not be any overshoot, undershoats and duplicate features, SAIL Appropriate symbols have to be used as per the source. 3.4.12 ‘The polygon features have to be closed! without any dangles or slivers 3413 Peature-specifie codes will be used for attribution, Each parcel polygon will have 2 waique Khasta number as per the provided coding scheme, 3.4.14 For Vectorization, an approved template has to be used with necessary legends, Title, scale har north arrow, different layers used for capturing various information, map text deiails and borders etc. The symbols, standard legend, and logo block for use in the Vectorization process ‘would be created as GIS blocks and used whenever necessary. 34.18 The required attribute information such as parcel / Khasra numbers available on the maps have to be assigned to the vectorized polygons 2s Unicode texts. The drawing file for each village has to be created in this tas. If village information is available in more than one map sheet, all the sheets have to be edge matched into one village drawing (Edge matching, removal of redundant / duplicate resvlabels, scale adjustments e(.) <14-DB ceragtee 4 _captanton of Gator! Mop and tinkaes to Revenue Recs nL Layout of Cadastral map as it is ie. as per original map es vel -15-Digitization of Cadostral Mops ond Its Linkages to Revenue Records in U.P. 4, STANDARDS FOR DATA STRUCTURE Table 4.1 : Various data folder nomenclature app VOLUWE NOwENeLATE r Tay sane DDD aor 1 Far ae HDD Velume be ‘Dppremnin eM TPETE i forth 3 eter Tbe onde & NNN 1 fe L eile’ Sarin rom 001 99) (kach HDD should contain the following foldervairectory/norkspace ] SeCDDBTHATT — | Scanned raster fies ‘Raw and aflerregisration with grid | + | pxrmapmemt | id oon Ca ae k , fe updation PLOT fies in) wrprappmmar | 22% apdaion FLOT Ai convereg int PDE fost ly | wssimmasinnn | Sirupearine Stops lesst | ntosac Shape at Vilage levels ater Updtin ‘Ait updtion PLOT fies Vv UPDEDPDITITE converted into PDF fosmat All pio fles as PDF format before updation Al pio les as PL P format after updosion ‘| ‘Table 4.2_: Fach FOLDER should contain the following files for each village TT ‘Shes wise seamed file (Raw oF IDDDTTTTTVVWWWWAN ipa, ‘all scanned files, wih oF witha seGpporrr’ | gid BDDDTTTTTVWWWNNivg ‘Sheotswtea grid cormeved ile Urge Boporrrrvvwwnne wth or without grid lines) iL} Shect-wise AutoCAD draasing file CW" as prefix) | Booorerrryyyywnn*.dwg, pwebopTTT 1 Moscie af drawing file a village level(WM as prefix) Witovorrrrrvwvvyv*.dwe, ‘Sheet-wise PLOT files converted ti] pprppprrr’_ | Rovorrrrrvvwvwwn* pat, to PDF format (Fos prefs) 7 = = «| @opprrrrrvev* Area shape at village level) Lv SHPDDDITT oT (ArcGIS feature fles-| Iborrrrtvwwwwv* Line shape at village level(L) envectiied) Bovpsrrrrevvww* Poin shape ot village leva?) * ss where te ep abet distro Tebel odes haste nse ‘this sore the mane oles of the esirc¥ Teh has oe Wed Tinig mage sal fe import in Shoe le ALP Forest. = 16+Digitization of Cadastral Mops and Its Linkoges to Revenuc Records in UP. Table 4,3: Standard DWG (AutoCAD Drawing File) layers and the block names as part of the digitization template. Standerd DWG (AutoCAD Drawing File) layers and the block names as part of the digitization template in CAD environment for digitization of Cadastral maps under Digitization of cadastral Maps Project, U.P. Layers Used for Digitization Different layers (point,ine,area)are used for map composition. Line layer are required for the map composition part, while arca layers are mainly required for both map checking and composition. Feature No. | Laver Name Color | Line Type Type Remarks 1 jo 7 Continuous Default layer (No Data) 2 | Grid 1 | Continuous Reference grid used for | 3. | image 134 | Continuous Scan Image 4 | Legend - 1 Continuous All template contents T|mesom | a0) Dastean [tine | temporary ote of map Une 6 as BOULD (Read & Blue) line | | Segment. 7 ume Rate [8 [Teck [te | Fak ne 8 Line Village_Div| 7 | Continuous | Line Village Dividing line (Width 0.5) ide | 9 | Poly Bandh | a0 | Continuous Polygon _| Bandh Polygon : 10 | Poly_Canal 4 Continuous | Polygon Canal Polygon 11 | Poly_Chak Road 30 Continuous | Polygon ‘Small/Thin Road | 12. Poly_Khasra © | Continuous | Polygon | Khasra Boundary Polygon \ B | Poly_ Margin 8 Dashed Polygon Temporary border line of maps in parts 14 | Poly. Nala 42 Continuous ‘Small water polygon: 15 | Poly_Nali 52 | Continuous Water polygon Smaller than Nala 16 oly _Other 7 ‘Continuous | Polygon Unidentified Polygon features 17 | Poly Rail 7 | Continuous | Polygon Rail polygon - be?@ cms mete Dititisotion of Cadastral Maps and Its Linkeges to Revenue Records in U.P. ig | Poly Rasta 14 | Continuous Polygon | Village Road polygon (Internal | Road) 19 | Poly River 5 | Continuous Polygon | River polygon go | Poly Road Pukta | 1 | Continuous | Polygon | Road polygon (Major Road) & Khamb Poly_Village 7 | Continuous | Polygon | village Boundary polygon(Width 21 | Boundary 0.5) Symbol 1 | Continuous | Symbol | all Symbols used for Unique identification except(RA, Ro, RI,& 2 a 93 | Symbol Blank T | 1 | Continuous | symbot_— | Blank_Khasra_symbal_ insert in ext Blank_Text Layer | Symbol Multiple | 4 — | Continuous | Symbol | Multiple Khasra symbol insert in 24 | Text | Multiple_Khasra Layer where inside - polygon multiple text are presents. Symbol_NotClear| 1 | Continuous | Symbol | Not Clear symbol insert in 25 Not_Clear_Text Layer Text Symbol Par Typ | 2 | Continuous | Symbol | Symbols used for Unique | e | identification Rail, Road, River & Canal (RA, Ro, Rl, & CA) Rail- - 26 | RoadPukta-Kham,Rasta — | Text_Pareel 7 | Continuous | Textteight | all parcel Text Present in the map | 1.6-1.5 | (Text style Khasra_Number & text 7 mle] mm | height 1.6) Number | Text_Village 7 | Continuous | Text All Village Text Present in the map Height 4 ExceRt Text Parcel 28 mm (Text. style Knasra Village & text khasca | nelgne 4) text 2 awe? 218+up. @D wee EY ytenaon of cadonr! Mops ond es Unkoes to Revenue Recordin ‘Text Used for Diaitization. al Sw SS) isu nese ‘iad Sh ‘sito air” nb a ur fwut wi Slur sai fina son sa ALL -19-DB wea 524 capinaion of Coder! Mop onde inkage to Revenue Recordin UP. 4.4 Reference of Standard Symbol Tar ae am ate, Fa te _ TA, STS WE oo 6 [ S Wiese) Ss | ee Tere, FAN, Bait peo ew ~ ae am | ter] TH 2 1 aa CH a Fat Tet ae 7a -20-@ eeseme TESST pigtization of Cadastral Maps and Its Linkages to Revenue Records in UP. Note-Symbol may be changed as per existing legend cadstral map. 4.5 Standard Legend -Using above symbols following blocks for legend are to be generated. b E RH wsae TAT are ge Seat aaeaT TaaesT feos oe fern eet saryaa arte qe ae aa ASST ‘aestter aeraterstFEETSRNG, FETE! pigitization of Cadastral Mops and its Linkoges to Revenue Records in U.P. Table 4.6 eld description of LINE features Shape in table (IDDDTTTTTVVVVVV.shp) Ficld/Item | Field/Item ” " SuNO | teamne Wine __Fisld/ltem description 1 | suucone: | isc | BDBFFFFIVYWVYY( wi be ols uid Ta Fok [2 | Hab_No 4c Hadbast number in english ~ ‘| 3 VILLLNAME) 50, Village name in HINDI | MAP Two digit MAP SHEET_NO ro. reference & per Caasial SHEFT_NO. | Code(NN) 5 | LIN_coDE “EC Line symbe code ofthe Tine earure | LeNeTH TC] Line length of te Tine Feature 7_| PAR TYPE 2,C__|_normation ofthe parcel types (As po the codes specified) | REMARKS 50,6 | Comments regarding the fecture Table 4.7: Codes of Line features in the line Shape data base (DDDITTTTVVVVVV) Note: The line feature Shape contains the line features other than the parcel boundary. Table 4.8: Field description of POINT features Shape in table IDDDTTTITVVVVVV.shp) SND eee biceisesl Field/Item description | pnucope® 15¢ | BBDEETTVVVWYY wie was unne Ink 2 | HAD No Ge | Fadbast number ia English — 3__| VILL_NAME 50,C Village name in English __| | MAP 5 Two digit MAP SHEET_NO no, Teterence ws per Cadseal SHEET_NO. 2 Cot) 3] SYM_cope a Point symbol code ofthe point feat 6 | PAR_TYPE 2c Information of the parcel types (As per the codes specified) STaEWanKS [90] Commence eesSD crests eB _openaen of coder Mapa Like fo eres Record ‘Table 4.9 : Design and structure of the POINT spatial topology database fite [sym cops "sac ‘Paint symbol code of the point feature 2—| RAE PE | soe haa aeeet aah Hts 50,50,C Comments rega syM10 syMit syMI2BD cre 8 cages of Colne Map ads Linge o Revenue Rect t Each village mosaic DWG/DXF file has to be generated and converied to the GIS data file, preferably in ArcGIS Shape data model. The features have to be separated in Separate polygon, fine and point entity, The Shape should have prefix of ‘a’. and ‘p’ for potrgon, line and point Shape, respectively. Each Shape should have the desired fields and codes as specified in the table 4.5 through 4.7. The polygon feature should have both polygon and line topology. The polygon Shape PAT file will have the attributes as specified in table 4.10, Proper bifurcation and allotment of parcel ‘numniber should be done as per the standard. The reporting of error in the PAR_ERK and assignment of the parcel land use in PAR_TTPE has to be properly executed (Table 4.8 and Table 4.9), ‘Table 4.10: Description of ERROR codes in the polygon festures under item PAR_ERR TEXT TOBE CODE a, l INSERT/LAYERS EON (in PAR ERR Det | 1 O/EXT PARCEL TAROLABEL oO 2 | TIENT PARCEL, DUPLICATE v 3) a pare or 2 part of = ‘CONTINUED PARCEL-1 P Table 4.10.1 : Font and Text Styles 1 ‘Txt Parcel Devlys050 Hindi Text 2. Tx REN Deviys050 Rendered Parcel Text 3 Tet_Mapin Deviys050 Hindi Test Z.[ Txt Mapout Deviys050_ Hindi Text 5 “Txt Part Deviys050. Hindi Text 6 Teng | Arial | Genera Purpore ‘Table 4.11 : Deseription of PARCEL TYPE codes in the polygon features under item PAR_TYPE. TEXT TO BE INSERT - CODE ON TEXT. STANDARD (nPAR_TYPE LAYER (Autocad) | fietd)** HILLY AREA SMASHAN, KABRISTHAN, FOREST ORCHARDS SCRUB PARCEL RVED PROTECTED FOREST (includes RFZPF area, brought-in around the scattered village to complete the village as | ‘one polygon) —_ a a Map details/ Information not available Na NOTE + Part of single khasra separated by other features (like road, pipeline, ete.)Th a z "8% Digitization of Cadastral Maps end Its Linkages to Revenue Records in UP. This isthe description of khasra for which a khasra id (parcel no) has already been given. Example, If the khesra is a water body, having a parcel no 43 in KIDE, then the code in the PAR_TYPE should be given WB. Ry default all polygons are parcels 'PA', unless otherwise defined in either of the classes given in the above table. Also consider the point artribuie information while assigning ihe Tandusefandcover ~ e.g. the Landuse leme symbols and amenity symbol kabaristhan, etc, should be considered while assigning the PAR_TYPE ues. z Description - TATE CODE DISTRICT CODE. corrections and finalization. oS ‘* Verification report for timely payment realization. \ “ -26-