GIS Survey and Mapping
A Geographic Information System links location to information. GIS survey and mapping work turns field observations, drawings, imagery and records into structured spatial layers in a defined coordinate reference system, so that organisations can see where their assets are, what condition they are in and how they relate to everything around them.
Overview
GIS is less a single survey technique than a way of organising spatial information. A GIS dataset combines geometry, meaning points, lines and polygons with coordinates, with attributes such as an asset's type, material, size, installation date or condition. When data from different sources shares a consistent coordinate reference system and a well-designed schema, it can be overlaid, queried and analysed in ways that separate drawings and spreadsheets cannot support.
GIS survey work usually involves several activities: field data collection of assets and features; georeferencing of scanned maps, drawings and imagery so that they align with real-world coordinates; digitisation of features from those sources; attribute capture; topology and quality checks; and delivery in formats the client's systems can use. The emphasis throughout is on data that is consistent, documented and fit for the purpose it will serve.
The quality of a GIS output depends on its inputs and the care applied to them. Source data may be of uneven accuracy, a drawing may be in an unknown local grid, imagery may be poorly orthorectified, and attribute records may be incomplete. Output quality therefore depends on the source data, the coordinate reference system and transformations used, the processing workflow and the validation carried out. Good practice is to record this lineage in metadata so users understand how much confidence the data deserves.
This page explains the core concepts of GIS mapping, including coordinate reference systems commonly used in India, data formats and quality control, to help clients specify GIS work clearly.
How it works
Every GIS dataset is defined in a coordinate reference system (CRS). Geographic systems such as WGS 84 store latitude and longitude in degrees and are the native system of GNSS positioning. Projected systems convert the curved earth to a flat grid in metres, which is necessary for accurate distance and area measurement. Universal Transverse Mercator (UTM) is widely used; mainland India falls within UTM zones 42N to 47N on the WGS 84 datum, with, for example, much of Uttar Pradesh in zone 44N. Projects may also use local grids or other national systems, and the correct CRS must be identified rather than assumed.
Mixing systems without proper transformation is one of the most common sources of error in GIS work. Data recorded in latitude and longitude, data in a UTM zone and data in an undocumented site grid will not align unless transformations are correctly defined. Where a drawing has no coordinate reference, it is georeferenced by matching identifiable points on the drawing with their surveyed or known coordinates, and the residual errors of that fit are recorded.
Field data collection captures the position and attributes of features. Depending on accuracy needs, positions may come from survey-grade GNSS, total station observations, mapping-grade receivers or digitisation from imagery. Attributes are collected against a predefined data dictionary so that values are consistent: a valve should be recorded with the same field names and permitted values everywhere.
Data is then structured into layers and stored in a suitable format. Common exchange formats include the shapefile, a long-established vector format consisting of several files; GeoJSON, a text-based format suited to web applications, normally in WGS 84; and the geodatabase, which stores multiple layers with domains, relationships and topology rules in one container. GeoPackage is another open, single-file alternative. Raster data, such as imagery or elevation models, is typically delivered as GeoTIFF.
Quality control checks geometry, topology and attributes. Geometric checks compare positions against higher-accuracy reference data. Topology checks look for gaps, overlaps, dangling lines and disconnected networks. Attribute checks confirm mandatory fields are filled and values fall within permitted domains. Metadata documents the CRS, sources, dates, methods and known limitations.
Applications
Asset mapping and registers
Mapping utility networks, street furniture, poles, valves and other assets with attributes for maintenance and planning.
Georeferencing legacy records
Bringing scanned maps and drawings into a common coordinate system so they can be compared with current data.
Infrastructure planning
Overlaying terrain, land use, utilities and constraints to support route selection and site planning.
Land and parcel mapping support
Organising parcel and land records spatially, subject to the authority and status of the source data.
Integration of survey data
Combining topographical, LiDAR and GPR outputs into a single spatial dataset.
Thematic and analytical mapping
Producing maps and analyses for reporting, decision-making and stakeholder communication.
Industries
- Utilities
- Telecom
- Power
- Water and sewerage
- Government
- Infrastructure
- Rail and metro
- Engineering consultants
Methodology
Requirements and schema design
Agree the purpose, layers, attributes, permitted values and target formats, and document them in a data dictionary.
CRS definition
Confirm the coordinate reference system, datum and any required transformations before data capture begins.
Source data review
Assess the accuracy, age and completeness of existing drawings, imagery and records.
Data capture
Collect field data, georeference sources and digitise features according to the schema.
Attribute population
Enter and validate attributes against domains and mandatory field rules.
Topology and QA checks
Run geometry, topology and attribute checks and correct issues.
Metadata and documentation
Record lineage, CRS, sources, dates and known limitations.
Delivery and handover
Deliver data in agreed formats with a summary of contents and quality results.
Equipment and technology
GIS mapping relies on desktop GIS software for editing, analysis and cartography; spatial databases for multi-user storage; and field data collection applications on mobile devices or dedicated receivers. Positional accuracy of field data depends on the positioning method, from survey-grade GNSS and total station to mapping-grade receivers or imagery digitisation. The tools used for a specific project are agreed in the scope.
Open standards and formats, such as GeoJSON, GeoPackage and those defined by the Open Geospatial Consortium, help ensure data remains usable across different software platforms over time.
Benefits and considerations
Benefits
- Brings information from many sources into one consistent spatial framework.
- Supports queries, analysis and reporting that drawings alone cannot.
- Well-designed schemas make data maintainable and reusable over the life of assets.
- Metadata makes data quality transparent to every user.
Considerations
- Output quality cannot exceed the quality of source data without additional survey.
- An incorrect or undocumented CRS can cause misalignment of tens or hundreds of metres.
- Schema decisions should be made early; changing them later is costly.
- Attribute completeness depends on the availability and reliability of records.
What to prepare
- Describe how the GIS data will be used and by which systems or teams.
- Share any existing schema, data standards or templates you need the data to follow.
- Provide source drawings, imagery and records, with any known coordinate system information.
- Confirm the required CRS, for example WGS 84 geographic or a specific UTM zone, and output formats.
- Identify the area or the number and type of assets to be mapped.
- Nominate a contact who can answer questions about attribute meanings and record sources.
Limitations
- GIS outputs are only as accurate as the source data, CRS handling, processing and validation allow. Digitised features inherit the accuracy of the source.
- Georeferencing of drawings without coordinates relies on identifiable common points, and residual errors are reported rather than eliminated.
- GIS mapping of land parcels organises existing records spatially and does not by itself confer legal status on boundaries.
- Attributes that are not recorded in available sources or observable in the field cannot be populated without further investigation.
Frequently asked questions
Which coordinate system should my GIS data use?
It depends on how the data will be used. WGS 84 latitude and longitude is common for web mapping and exchange, while a projected system such as the appropriate UTM zone is preferable for measurement. Many organisations also have their own standard. The CRS is agreed before work begins.
What is the difference between a shapefile and a geodatabase?
A shapefile stores a single layer of one geometry type across several files and has limits on field names and sizes. A geodatabase stores many layers with domains, relationships and topology rules in one container, which suits larger structured datasets.
Can you convert our CAD drawings to GIS?
CAD drawings can be converted when their coordinate system is known or can be established through georeferencing. Layers are mapped to the GIS schema and attributes are added where available.
How is GIS data quality checked?
Through positional comparison with reference data, topology checks for gaps, overlaps and connectivity, and attribute checks against domains and mandatory fields, all documented in metadata.
Can GIS data be used in web maps?
Yes. Formats such as GeoJSON and services based on open standards are widely used for web mapping. Delivery formats are agreed during scoping.