report - prbdb report.pdf · inception report digital maps of ... time counters 9. height of...

CENTRE FOR COMPUTATIONAL ENGINEERING PUNJAB ENGINEEING COLLEGE

October 10, 2007

INCEPTION REPORT

Digital Maps of Roads and Bridges of Punjab

Contents Page No.

1. Introduction 1

2. Project Appreciation 4

3. Professionals Staff Listing and Interaction with the Client /Various Agencies 10

4. Approach and Methodology 12

5. Design Standards 19

6. Work Programme, Manning Schedule and Task Assignment 24

7. Proforma for survey data collection 27

Inception Report Digital Maps of Roads and Bridges of Punjab

CCE Inception Report October 10, 2007 1

1. INTRODUCTION

1.1 PROJECT BACKGROUND

Government of Punjab through the Government of India has got the assistance of the World Bank for the improvement and efficient management of State Highways, and other District Roads. For this a Geographic information system development has been planned to facilitate a repository for hosting and dissemination of the data of roads and bridges network across the state of Punjab.

Punjab Roads and Bridges Development Board (PRBDB) has been entrusted with the implementation of the statewide project and is the executing agency for the consultancy services and the high standards of output is required from the appointed consultants within agreed time frame.

1.2 CONSULTANCY SERVICES

In pursuance of the above, Centre for Computational Engineering (CCE), Punjab Engineering college, Chandigarh have been appointed as Consultants to carry out the preparation of detailed project report for the development of GIS of roads and bridges. The agreement between PRBDB and the consultants was signed on 25th July 2007.The start up meeting between the team and the PRBDB was held on 2nd Aug 2007 and accordingly the services were commenced on 2nd Aug 2007.

The scope of consultancy services to be provided is contained in the Terms of Reference (TOR) of the consultancy which is part of the agreement.

The services are targeted to be completed in 6 months from commencement by 25th January 2008.

1.3 PROJECT DESCRIPTION

The consultancy services for preparation of GIS for roads and bridges network include the entire area of the state of Punjab:-

1. State Highways -1462.00

2. Major District Roads.- 1797.00

3. Other District Roads.- 4164.83

4. Junctions.

5. Bridges.



The Index Map showing the project roads is placed in Fig. 1.1.



Executive Summary

Chapter-1 : Introduction

Chapter-2 : Project Appreciation

Chapter-3 : Professionals Staff Listing and interaction With the Client/Various Agencies

Chapter-4 : Approach and Methodology

Chapter-5 : Design Standards

Chapter-6 : Work Programme, Manning Schedule and Task Assignment

Chapter-7 : Proforma for Data Collection

• • •



2. PROJECT APPRECIATION

PROJECT INFLUENCE AREA

The Project Digital Maps of Roads and Bridges area of interest is entire State of Punjab. Punjab is one of the most prosperous state of India. Situated in the north western corner of the country, Punjab is bound on the west by Pakistan, on north by Jammu and Kashmir, on north east Himachal Pradesh and on south by Haryana and Rajasthan.

Covering an area of 50, 360 sq km, Punjab has a population of 24.29 million as per 2001 census, of which 33% is urban. It is divided into 4 divisions, 17 districts, 72 sub divisions and 141 blocks. The famous and modern city of Chandigarh is its capital. The decadal growth rate of population between 1991 and 2001 is 20 per cent and is less than the national decadal growth of 21.34 per cent. The state has the population density of 482 persons per sq km and has a literacy rate of 69.95 per cent. Agriculture is the mainstay of Punjab’s economy. Nearly 86 per cent of the total geographical area of the State is under cultivation. Punjab alone contributes about 51 per cent of rice and wheat to the central pool. Punjab has the distinction of being the first few states to have achieved road connectivity to 100 percent villages. Punjab has developed a network of about 60000 km of roads, all of which are surfaced. District Jalandar has the highest road density (183 km per 100 sq km) while district Mansah as the lowest density of (79 km per 100 sq km). For better efficient management and seamless information dissemination the project Digital maps of roads and bridges of Punjab has been conceived.

2.2 PROJECT ROADS and BRIDGES

Any project based on development of a GIS needs the geographic data first, being the backbone of the project. In the case of the state of Punjab the major part of the state falls under the category of restricted area (Fig -3). Therefore the permission for the data procurement and use has been requested from the Survey of India and various other legal bodies for granting the necessary permissions. Establishment of a centrally managed GIS repository for data integration and dissemination of a large area network of Roads (Fig -2) and Bridges of Punjab require a well developed system capable of holding and incorporating large geographical datasets. The project aims to develop a seamless Digital Map using the GIS technology. The Objective and scope of the Project are:-



Objective: Create a Digital base Map of Roads and Bridges in the State of Punjab for 9200 Kms approx:

• National Highways • State Highways • District Roads • And Other District Roads

Scope includes

• Spatial Data and • Aspatial data of Roads and Bridges for inputs to Road Information System

The GIS will be capable of holding large datasets and compatible with other existing GIS, if any in the Department. Also the Digital maps submitted on the project completion will be entirely compatible to be transformed to an Internet based GIS system. The Digital Map will consist of various Geospatial datasets procured from different governing bodies and overlayed on each other in a perfect overlay. The Perfect overlay will be achieved with the help of an accurately matched Projection system and coordinate system. The Projection system in this case will be UTM WGS84 thus following the guidelines of the Map Policy of Survey of India.

The combination of the various Geographic Datasets of the Different Layers in the GIS will be:-

1. Survey of India 1:25000 Digital Toposheets.

2. Cartosat Satellite Rectified Images of 2.5 Mtr PAN Sensor Datasets.

3. Updated vector Layers (several new digitized features, missing in the SOI digital sheets).

4. Attribute Data.

5. Field Survey tabular data.

6. Other Tabular Datasets from departmental registers.

The Project will be entirely developed on a ESRI ARCGIS software, six copies of this software is already with the department. Therefore all the information consisting of Spatial and Non-spatial Datasets will be bounded by a Topology. Also the datasets consisting of Tabular data, attained by Field survey or attached to the vector data will be stored in an ESRI Geodatabase. The Geodatabase being the central database (repository) of the entire Spatial and Non-spatial data of the Project. This Geodatabase can also be used for remote access and management through a remotely accessible RDBMS package.



The Geodatabase discussed here is a Personal Geodatabase. The various Attributes to be included for the –Roads are:- 1. Road Code 2. Name of road. 3. Length 4. Classification (category) 5. Carriageway width and Berms 6. Road condition (Roughness) 7. Soil Type (CBR) 8. Right of Way 9. Jurisdiction 10. No. of carriageways 11. Date and type of last improvement 12. Maintenance cost / year (previous FY) 13. Accident Data 14. No. of lanes 15. Paved Walkway / side-roads 16. Pavement Structure: depth of granular portion, depth of bituminous portion. The various Attributes to be included for the –Bridges are:- 1. Name of Bridge (Km / no. of structures) & local name, if any 2. Location / Chainage (with direction Up/Down) 3. Span arrangement 4. Carriageway / no. of lanes 5. Width of the Bridge and footpath 6. Type (Brick masonry, RCC, steel, wooden) 7. Condition of the Bridge 8. Name of stream or river or Railway line or Road 9. Type & condition of bearings 10. Type of expansion joints 11. Type of foundation 12. Type of Pavement (Raised kerb + footpath) 13. Type of Protection Works 14. Services being carried 15. Year of construction 16. Capital Cost incurred 17. Design loading 18. Jurisdiction details 19. Contractual agency + Execution Division 20. Maintenance cost / year (for previous year) 21. Type of Railing 22. Condition of Railing 23. City Drain details

1. Width of open channel or number and dia of pipes, 2. Condition, 3. Peak hours, 4. Highest level of flow reached in the past,



5. Associated junction (if any) The various Attributes to be included for the –Junctions are:- 1. Name of Junction & local name, if any 2. Level of Junction (Grade separator, same grade, level crossing, etc.) 3. Type of Junction (legs: two, four, staggered, rotaries, railway) 4. Location / Chainage (with direction Up/Down) 5. Traffic details 6. Electrification (Light masts / lighting) 7. Signalized 8. Time counters 9. Height of signals 10. Accident data



Fig .2 – Map showing the Major Road network of Punjab



Fig 3 – Map Showing the Survey of India (Unrestricted) 1:50k Toposheet Layout on the State of Punjab



3. PROFESSIONALS STAFF LISTING AND INTERACTION WITH THE CLIENT/VARIOUS AGENCIES

3.1 COMMENCEMENT

The agreement for the consultancy services was signed on 25/07/2007 and the consultancy services were commenced on 01/Aug/2007, the date on which the start up meeting between the team of the consultants and the officers of the Punjab Roads and Bridges Development Board (PRBDB) was held.

3.2 STAFFING

The following members of the consultant’s team have been finalized for the:

3.2.1 Key Professionals

Sl. No. Position Name Task

1. TEAM LEADER Dr. S.C DHAWAN Management, Design And Work Flow

2. PROJECT HEAD Mr. VINAY MEHTA Project Execution, Quality Checks, Delivery Checks

The following/Additional Professionals are proposed against following positions which were indicated as “to be named’.

3.2.2 Additional Professionals

Sl. No.

Position Name Qualification Experience

1. GROUP LEADER Mr. Vipul Soni M.Sc (c.s), PGD Geoinformatics

2.5 yrs

2. GIS ENGINEER Mr. Sunil Kumar M.Sc (Geog)

PGD RS & GIS

2 yrs

3. GIS ENGINEER Mr. Manu Sharma M.Sc (Geo), PGD Geoinformatics

2.5 yrs

4. GIS ENGINEER Mr. Kunal Gupta B.Sc (c.s), ESRI Trained

2.5 yrs



3.3 PROJECT OFFICE

The Project Execution office will be the GIS Lab of Centre for Computational Engineering (CCE), Punjab Engineering College, Chandigarh. All staff required working on the project directly and the support staff will be stationed here for the entire duration of the project completion.

3.4 INTERACTION WITH PRBDB

Interaction with PRBDB and PWD B&R branch offices will be done mainly by Mr. Vinay Mehta, Project Head.

• • •



4. APPROACH AND METHODOLOGY

4.1 GENERAL APPROACH

• Based on the objectives and scope of Consultancy Services, an appropriate approach and methodology was developed in the technical proposal. The same has been reviewed and updated based on contract negotiation and the site visit and reconnaissance and is discussed in the succeeding paras so as to address the various issues involved in the project.

• It has been proposed to adopt a TASK APPROACH to carry out the entire work comprehensively and accurately to the complete satisfaction of the Client

• The assignment has been broken in to different TASKS as indicated in

Table 4.1. The methodology of each task has been described in the Technical Proposal. The detailed methodology of principal activities only has been discussed subsequently.

Table 4.1: List of Tasks

Task No.

Description TOR

Reference

Task Group-I Awareness and Expectation Drive

101 CCE Team visit at the Field Offices for the Requirement Awareness to the Department Staff

II-3-I

102 Assessment of Department Staff Expectations with Project Deliverables

II-3-I

103 Conducting one-day workshops with department officers at 4-5 locations

II-3-I

Task Group-II : System Documentation

201 Preparation of Software Requirements Specifications

II-3-II

202 Preparation of Software Design Document II-3-II

203 Submission to the department for modifications

II-3-II

Task Group III : Digital Data Usage

301 Procurement of Survey of India Digital data of 1:25000 Sheets

II-3-III & IV

302 Procurement of Cartosat Satellite Images II-3-III

303 Arrive at a process to decrease the error between the Image and Survey of India digitized sheet

II-3-III

304 Arrive at a process to geo-reference the image using GPS data assuming Survey of India digitized sheet to be correct in

II-3-III



Task No.

Description TOR

Reference

coordinates

Task Group-IV : Digitization

401 Training to Field Office personnel for Ground Verification of actual condition and location of Roads and Bridges

III-3

402 Field Office personnel will be allotted 1:25k / 36 parts of Toposheet’s on A3 size for Field Verification and Map Marking of new features

III-3

403 Collating the Information received from PWD B&R

III-3

404 Updation and Addition of various other useful features not found in the Survey of India sheets but visible on the Cartosat Images

III-3

405 Resolving any Conflicts in the data received III-3

406 Quality Checks of the data received III-3

TASK GROUP V : Annotation Updation

501 Features extracted / digitized from Cartosat will be assigned Annotations according to the Survey of India standards

II-3-VI

502 Quality Checks on the Updation Process II-3-VI

TASK GROUP VI : Marking of Boundaries and Data Creation

601 Marking / Addition of new boundaries like Constituency , Block Boundaries from Village Boundaries

II-3-VII

602 Marking / Addition of new department zones from department maps

II-3-VII

603 Development of a small and easy Data Entry program for data Entry of Attributes

II-3-VIII

604 Quality Checks of the Data Entry done II-3-VIII

605 Addition or Updation of other additionally required Attribute Data

II-3-VIII

606 Develop / identify processes for regular updates

II-3-VIII

TASK GROUP VII : Dynamic Segmentation

701 Dynamic Segmentation of roads, the size of the road to be segmented to be decided after Requirement Analysis and the availability of the data with the Department

II-3-IX

702 Development of a program for data entry of dynamic segmentation of roads

II-3-IX

703 Analysis and Quality Checks of the data received from the data entry software, by the department

II-3-IX



Task No.

Description TOR

Reference

TASK GROUP VIII : Geocoding and Data Updation

II-3-X

801 Normalization of the tabular data received from the department

II-3-X

802 Geocoding of the data with the GIS data II-3-X

TASK GROUP IX : Query System Development and Training

901 Development of a Query System and Custom Report Generation Application integrated with a Primary GIS Software

III-1

902 Training of the Department Staff for software use and query the application

III-1

903 Final Updation Checks in the Data to be Supplied

III-1



4.2 METHODOLOGY

The detailed methodology of only principal activities is described below.

4.2.1 Process Brief

The processes related to the mapping component of the project are explained in brief here.

4.2.1.1 Data Procurement

o Procuring the Cartosat 2.5 m resolution PAN sensor data.

o Procuring the Survey of India digitized Toposheets for entire Punjab state.

4.2.1.2 Data Geo-Referencing and Survey of India Vector data usage

o Georeferencing and Rectification of the Cartosat Images.

o Use of Digitized roads, bridges and other required data from Digital Survey of India topo sheets.

4.2.1.3 Updation of the Survey of India Digital Data

o Rework on the spatial data to attach additional Attribute fields.

o Quality check at various known points on ground as per the department to see the relevance of the data.

4.2.1.4 Field Survey and Procurring Additional Attribute Data

o Survey of the field area to update the data with latest ground information.

o Procuring attribute data and dynamic segmentation data from the department for random checking and Updation.

4.2.1.5 Updation of the Data procured from field survey and additional attribute data supplied by the Department

o Dynamic segmentation of the roads data.

o Geo-Coding of the attribute data of roads and bridges with respective locations.

4.2.1.6 Development of a Query system and Software training

o Development of query system software running on the primary software for easy usage of maps created and custom queries on the attribute data fed.

o Training of PRBDB and other user staff on the use of Digital Maps and the custom Query System.

4.2.2 Work Flow

4.2.2.1 A brief Work Flow of the Entire process is given here –

a. Digitized Survey of India Topo Sheets

b. Taking Hard-Copy printouts on A3 size sheets as per Operating Procedure



c. Verification of the Ground Information by PWD B&R

d. Collating the information received from PWD B&R

e. Resolving conflicts in the information received

f. Digitizing the information received with local coordinates provided by field staff

g. Taking the printout and final verification duly signed

h. Building up the sheet by sheet 1:25000

4.2.3 Operating Procedure

In a pilot study done by CCE, it has been found that one fourth of one block of 1:25000 sheet [one fourth of 2’30” x 2’30”] can be ground verified by the field staff in a day. The operating procedure developed to handle this work as follow:

1. Each 1:25000 Survey of India topo sheet shall be divided into 36 equal parts.

2. Each part will be printed on A3 Sheet with some overlap with the adjacent parts

3. The field staff shall be issued the necessary sheets for ground verification after proper training and instructions.

4. The ground data marked by the staff will be entered in to the separate copy of digitized Survey of India sheet

5. The differences in the alignment or data will be decided if the imagery scene is required for such blocks in each sheet

6. Accordingly the scenes shall be acquired

7. The data from the imagery , field and Survey of India sheet shall be recompiled and entered in to the system

8. This data shall be sent for final verification to the board.

9. The verified data shall be entered in the final digital maps being prepared.

4.2.4 Logistics Management

The entire logistics of getting the information procured to be verified on ground (15% of total) shall be done by the CCE with the reimbursable travel and loading cost as indicated in the cost & other terms indicated at the end of this proposal.

CCE expects the client to facilitate various steps involved in it in order to make the logistics functioning smoother with the objective that the data for the project has to be received and verified in a time-bound manner.

4.2.5 Quality Assurance – Quality Checks



All the work being carried out by CCE under this project will be submitted to various quality checks by the internal teams of CCE so that error if any can be brought within the minimal permissible limits.

Various other test cases will be done to check the software performance and reliability and these will be tested jointly by CCE and PRBDB.

Spatial data generated will be put to quality check at various steps of its generation and Updation thus complying with the quality assured to PRBDB.

The Quality of maps and the information contained therein shall be frequently checked to quantify the quality of the data being generated. The field checks, as indicated elsewhere in the report as well, shall be carried out on 15% of the data supplied by the department staff. This will ensure that the data being built in the system us dependable, reliable and can be used for planning and other purposes.

4.3 Support Services

4.3.1 Maintenance of the system and continuity management

The Digital Maps will be supplied in ESRI format compatible with the application software already available with the department (ESRI-ARCGIS). The client and PWD B&R are advised to get the latest version of the software at their end.

The digital map data has to be maintained and updated as required on a regular basis, the scope of which shall be finalized subsequently.

PRBDB should ultimately build on this data to develop a Road Management Information System (RMIS) so that the data can be put into a system of daily use and easy accessibility for frequent upgrade and suggestions for improvement through various default processes in the department.

4.3.2 Facilitating the Infrastructure / Capacity building within the client department

It has been known that most of the software projects are not frequently accessed for day to day information retrieval or Updation within the department due various factors like :- Insufficient infrastructure , Incomplete Training , Incompatibility with the working process of the department. In all of the cases mentioned the tool that can be used to rationally build up the planning process goes missing.

It is therefore the endeavour of CCE teams to encourage and facilitate the capacity building within the department so that the software is extensively used. In such a case CCE will help the client with a plan to enhance its infrastructure like setup of computer labs with components like plotter and printers especially for the requirements of making the digital maps and reports easily accessible in hardcopy after analysis. For these mentioned indications from CCE a report will be submitted.

4.4 Training Program

4.4.1 General

Training is a very fundamental aspect of project implementation in the department. CCE believes that an extensive training of the department staff



can help in making the project a huge success and also enhance and achieve the overall goals set by the department from the project implementation.

The people who maintain the system on a day to day basis shall be trained extensively on how to use the maps and query them for productive use in their day to day work. CCE plans to train 45 officers from PWD department so that they are able to use the Digital maps on a day to day basis.

4.4.2 Application Operation

The Customized software interface shall be designed on the basis of ease of use and how much technology know-how the present staffs has. The operation of the software shall be put in the training manuals and used for training for the staff in the middle of the project and before hand-holding and closure period.

4.4.3 Digital Data Maintenance

As discussed above, the maintenance of the data is needed regularly to keep it clean and usable for effective decision making. Processes and access shall be mechanized in such a manner so as to follow a particular procedure to update the data contained in the digital maps. Extensive training shall be provided to the staff.

• • •



5. DESIGN STANDARDS

5.1 INTRODUCTION

5.1.1 General

The design of the project on the GIS software used will be based on some predefined principles. The GIS software used in this project is ARCGIS, hence the design standards to be followed will be based on the principles laid down by ESRI. These Specific guidelines will be followed for the data arrangement and layer management. ARCGIS facilitates a GIS expert in various methods for creation of perfect maps which are ready for implementation on various other platforms. 5.1.2 The various Map design parameters to be followed for Composition of the map elements are:-

1. Coordinate systems and specific projections. (in compliance to SOI-Map Policy guidelines)

2. Layer Management. 3. Creation of Topology. 4. Data joins and relations. 5. Cartographic Principles.

a. Symbology b. Annotation c. Thematic details d. Visual Balance e. Correct Map Elements f. Legend Symbology

6. Creation of a Personal Geodatabase. 5.1.2.1 Coordinate systems and Specific Projections In geographic information system data from different sources can be overlayed with one another graphically, and associations can be made across them or between them. This is made possible by spatial referencing systems such as Latitude and Longitude or projected coordinate systems. In our case the coordinate system adopted is UTM WGS 84 standard which is known world wide for its compatibility with on the fly reprojection techniques present in ARCGIS. 5.1.2.2 Layer Management Layers arrangement in GIS is the first step towards a specific theme of the map to be developed. The gis data has to be arranged in such a way that It facilitates easier access through custom queries and better data access. These layers in Arcmap (arcgis) reference to datasets residing in the computers file system. The layers are independent of datasets, they are simply linked through their Source property. In a sense, these layer files are another sort of metadata that helps us to explain data to others.



5.1.2.3 Creation of Topology Topology basically refers the relationship between things, and in the realm of GIS, Topology refers to the relationship between spatial features or objects. In terms of functionality, topology is important to GIS in (at least) three important ways:

• Topology is necessary for certain spatial functions such as network routing through linear networks. Here the idea is that if line features do not share common nodes, that routes can not be established through the network.

• Topology can be used to create datasets with better quality control and

greater data integrity. Topology rules can be created so that edits made to a dataset can be 'validated' and show errors in that dataset. An example would be the creation of a new manhole/sewer access feature outside a polygon dataset of road features.

• By creating topological relationships between feature classes, features can

be shared across feature classes. Thus helping in keeping the entire data in an Arcmap document synchronized. 5.1.2.4 Data Joins and Relations Tabular Datasets which are acquired from some field survey or are supplied from some accumulated log files and has to be attached to the GIS for query purposes can be connected to a GIS with the help of a Joins and Relations. Joining and Relating Tables in ArcGIS

• Join in ArcGIS appends the attributes of the non-spatial table to the spatial (layer) attribute table.

• Relate in ArcGIS does not append attributes; only establishes a logical

relationship so that when you select one record in one table you can see the matching records in the other table.

The use of Join and Relate in our case

• Relate is preferred if the non-spatial table is maintained and updated constantly while the spatial data is not. (e.g., Mass towns shapefile plus summary table with data for each town)

• Use relate when the relationship is many-to-many. • Use relate when you have a very large non-spatial table and you don't need

all the attributes in the table.

• In other situations, you could use either.



Therefore in our case a Join is preferred to attach the data arriving from the field survey and departmental records. Since the records to be attached will satisfy the 1: Many relationships for Join condition, the Join method will be adopted. 5.1.2.5 Cartographic Principles. Implementation of Cartographic principles in a map helps in enhancing the ability to create a balanced and readable representation that is capable of communicating information effectively and quickly There are certain principles to be followed for a map to be cartographically correct:-

• Symbology • Annotation • Thematic Map • Visual Balance • Correct Map Elements • Legend Symbology • Map Scale

5.1.2.5.1 Symobology To correctly depict a feature in a map which is small enough for representation though a Point Feature may require a symbol for representation. There are two classes of Symobology:- Classes of symbols

• Qualitative Symbology Varying certain graphic characteristics can depict features that are qualitatively different (e.g., show different soil types or illustrate the extents of different regions in a state). The graphic characteristics that are responsible for such displays are color, shape, texture, orientation, and placement. The order of these characteristics is irrelevant.

• Quantitative Symbology Quantitative differences among features (e.g., different population densities or soil pH values) can be rendered on the map using other graphic characteristics. You can either use different graytone values (darker to lighter color) or different symbol sizes (larger to smaller circles or squares) to depict differences in population densities or pH values, and so on. 5.1.2.5.2 Annotation In cartography, text or graphics on a map that provide information for the map reader. Annotation may identify or describe a specific map entity, provide general information about an area on the map, or supply information about the map itself.



5.1.2.5.3 Thematic details A thematic map displays the spatial pattern of a theme or series of attributes. Thus a map designed to convey information about a single topic or theme, such as population density or geology. Thematic maps serve three primary purposes. First, they provide specific information about particular locations. Second, they provide general information about spatial patterns. Third, they can be used to compare patterns on two or more maps. 5.1.2.5.4 Visual Balance It has been known that people look at a point called the visual center when they first stare at a visual graphic. This point does not coincide with the geometric center of the map. In fact, it is higher than the geometric center by about five percent of the height of the map. This means that you should place the most important element of your map centered at that location. Visual balance is achieved by manoeuvring the positions of the different map elements, such as the north arrow, the scale bar, textual information, and so on, so the map generally looks visually balanced. So, if the map body is placed centred at the visual center, then the other map elements are placed around the map body and visually balanced. 5.1.2.5.5 Correct Map Elements Some map elements can be ignored in a map if other map elements or features can substitute for it. For example, a north arrow is redundant if you have neatlines shown with coordinate labels such as latitude and longitude; a north arrow and a scale bar are both redundant if you are depicting the population of the state of Punjab in, say, a book on demographic statistics; and a scale bar can be redundant if neatlines are shown with the proper coordinate system and units. 5.1.2.5.6 Legend Symbology Legend depicts the layers in a map, the arrangement of the layers and the Symobolgy they represent. Therefore a basic cartographic principle is to follow a specific legend Symobology in context to the Symbology adopted in the map windows. 5.1.2.5.7 Map scale Map scale is the relationship between distance on a map and the distance on the earth's surface. The map scale in this case will be the scale as per the data procured i.e 1:25000 this scale can in turn be dynamically changed by the software itself as the user needs. 5.1.2.6 Creation of a Personal Geodatabase. Geodatabase a term introduced in the geospatial community by ESRI for Geographical Database. ESRI Geodatabase provides the facility to store spatial and Aspatial data both in a central repository. Thus following a Topology and schema sets.



There are three types of Geodatabase namely:-

1. Personal Geodatabase – Personal Geodatabase are designed for a single user working with smaller datasets. They are built on a Microsoft Access file generated by the Microsoft Jet Engine that is included with ArcView, ArcEditor, and ArcInfo levels of ArcGIS Desktop. They have a maximum size limit of 2 GB but begin to have performance degradation between 250 and 500 MB of sizes.

2. Enterprise Geodatabase – Spatial data managed by ArcSDE in a DBMS

for an enterprise is called an Enterprise Geodatabase. In this case the data is stored in a 3rd party Enterprise RDBMS package. The enterprise Geodatabase system aims for a central enterprise level geographical data storage and management.

3. File Geodatabase - File geodatabases can be used by a single editor and

many readers in a GIS project. They store folders in a file system and can be created with ArcView, ArcEditor, and ArcInfo levels of ArcGIS. There is no limit on geodatabase size. Inside the File geodatabase, each dataset is stored as a file that can scale up to 1 TB in size, but this limit can be extended to 256 TB if needed. Vector data in File geodatabases can be compressed into a read-only format. Long transactions and versioning are not supported.

This project aims to centralise all the information collected from various agencies in a central Geodatabase. The Geodatabase in this case will be a personal Geodatabase using an MS Office - Access based database file.



6. WORK PROGRAMME, MANNING SCHEDULE AND TASK ASSIGNMENT

6.1 GENERAL

In this chapter the Consultants proposes the main activities of the assignments, their content and duration, phasing and interrelation, milestones (including interim approvals by the Client), and delivery dates of reports. The proposed work plan is consistent with the technical approach and methodology, showing understanding of the TOR and ability to translate them into a feasible working plan. A list of the final documents, including reports and tables to be delivered as final output, is included here.

The Consultants have applied their own professional expertise and the knowledge gained during the detailed site visit and discussion held with PRBDB / PWD engineer’s in respect to the quantum of work involved in order to prepare the Work Plan presented in this chapter. This Work Plan will accomplish the objectives of the consultancy and the tasks described hereinafter.



6.2 WORK SCEHDULE

The project work in the centre starts the moment first set of data is received from NRSA and Survey of India. The work schedule is planned according to the data procurement and analysis for the project use. The project starts from the creation of the base map , the initial startup required for a GIS to be established.

The Proposed Work Schedule is given here in the Table.

Activity Month 1

Month 2

Month 3 Month 4 Month 5 Month 6

Creation of Base Maps _____ ___ Distribution and collection of data from Field dept staff

___ _____ ______

Creating attributes for roads and bridges & Geo-coding

_____ ______ ___

Development & testing of simple query system

______ ___

QA, testing and user- interface testing

______ ______ ______

Documentation: Installation and Operation Manual

______ ______

Training ___ ______ ______ Assessment & Facilitation of Dept Infrastructure Build up

___ ______ ______ ___

Department testing, deployment & hand holding

______ _____

Project Completion Report __



6.3 MANNING SCHEDULE

The overall duration for each team member has been maintained the same as proposed in the Technical Proposal and included in the Contract Agreement. The Manning Schedule is indicated in Fig. 6.2.

6.4 TASK ASSIGNMENT

A complete list of tasks is given in Chapter 4 ‘Approach and Methodology’.

The Tasks Assigned to each of the key personnel for the study is indicated in the work programme also includes Task Assignment (Fig. 6.1).

• • •

S.No

Position Name of Staff

Staff Input Total Staff-Month input

1 2 3 4 5 6 Office Field

1 Team Leader Dr. S.C Dhawan

__ _ _ __ __ __ 4.5 .5

2 Group Head Mr. Vinay Mehta

__ __ __ __ __ __ 5 1

3 Group Leader Mr. Vipul Soni __ __ __ __ __ __ 5 1

4 GIS Engr. Mr. Sunil Kumar

__ __ __ __ __ __ 6 0

5 GIS Engr. Mr. Manu Sharma

__ __ __ 2.5 1

6 GIS Engr. Mr. Kunal Gupta

__ __ __ 2.5 0

7 Data Staff TBS __ __ __ __ __ 5 0

Sub-Total

Total 33



7. PROFORMA FOR SURVEY DATA COLLECTION

7.1 PROFORMA FOR SURVEY DATA COLLECTION

Proforma for survey data collection have been included as Annexure-7.1 which will be adopted and handed over to the department officials during survey and Map creation.

• • •

report - prbdb report.pdf · inception report digital maps of ... time counters 9. height of...

Documents