UTM Zone India Guide: Finding the Right Zone for Your Site

Which UTM zone is India in?

No single one. The Universal Transverse Mercator system divides the world into 60 strips of 6° longitude, and India, spanning roughly 68° to 97° E, crosses six of them: 42N to 47N. Each UTM zone of India has its own central meridian and false easting, so coordinates are only meaningful with the zone written beside them.

Satellite-based positioning gives latitude and longitude first, and the receiver software then converts them to eastings and northings in the chosen zone. The zone has no effect on the GPS signals themselves; it belongs to the map grid. If a base station and rover are set to different zones, the stored points will not agree.

Zones, meridians and EPSG codes

All our drawings state the zone and EPSG code. If buried services must be scanned on the same job, try the rate calculator.

How do you find the zone for a site?

Take the longitude in decimal degrees, add 180, divide by 6 and round up. Faridabad at 77.3° E gives 257.3 / 6 = 42.9, so zone 43. Cities near a boundary need care: Agra sits at about 78.01° E, inside zone 44 near its edge, while its western outskirts fall in 43.

What if a project crosses a zone boundary?

Keep the whole project on one grid. A pipeline from Delhi to Kanpur, for example, crosses 78° E. Splitting it into two zones breaks continuity. The usual answer is to extend one zone a few degrees beyond its edge and accept the slightly larger scale distortion, or to define a project-specific transverse Mercator grid. Either way, the choice is written on every sheet.

Worked zone checks for some cities

The rounding formula agrees with the table above for every large city. Ranchi at about 85.33° E gives 265.33 / 6 = 44.2, rounded up to zone 45. Bhopal at about 77.41° E gives 42.9, zone 43. Nagpur at about 79.09° E gives 43.2, zone 44. The edge is what catches people: a site at 77.95° E is in zone 43 but only five kilometres or so from zone 44. A route that starts there and heads east will leave the zone within a few minutes' drive.

How much does a zone distort distance?

Least at the central meridian, most at the edges. UTM applies a scale factor of 0.9996 on the central meridian, so distances there are slightly shortened. Moving away, the factor rises: at Faridabad, about 2.3° from 75° E, it is about 1.0002. At a zone edge 3° out, at the latitude of Delhi, it is roughly 1.0007, about 67 cm per kilometre. Extending a zone well beyond its edge for a long project makes that figure grow, which is why some corridors use a dedicated grid instead.

Common zone mistakes

Three slips cause most zone problems, and two of them can throw a site hundreds of kilometres off.

• Choosing the southern hemisphere. Selecting 43S instead of 43N adds a false northing of 10,000,000 m and throws the site into the Indian Ocean.
• Trusting auto-detection near a boundary. Software may pick a different zone for each end of a route.
• Re-projecting twice. Converting zone 44 values to 43 and back with different tools can leave small but real shifts.

Every Mezux title block states the zone, its EPSG code and central meridian; on a route that crosses a boundary the chosen zone is written beside the north arrow. Codes come from the EPSG registry maintained by IOGP.

What happens on a corridor that crosses 78° E?

Pick one zone for the whole job, write it down, and keep it from the first differential global positioning system (DGPS) control to the as-built. A Delhi–Kanpur alignment starts in zone 43 and ends near 80.3° E, deep in zone 44. Carried entirely in zone 43, its eastern end lies over 2° beyond the zone edge and scale distortion climbs well above a thousand parts per million. Carried in zone 44, the western end suffers a similar, slightly smaller distortion. The usual compromise is a project transverse Mercator grid with its central meridian near the middle of the route, which keeps distortion small along the whole length. Whatever the choice, every party, including the crew at each reference station, must use the same definition, or chainages and coordinates will not agree between design and site.

Older Indian maps and revenue records

Not everything is in UTM. Survey of India's Open Series Maps, under the National Map Policy of 2005, use UTM on WGS84; older topographical sheets used a polyconic projection on the Everest ellipsoid. Village revenue maps in Haryana and Punjab were drawn in local units with no projection at all. Tying a field to UTM therefore means measuring its corners on the ground with a GPS receiver or total station; see Khasra and Killa Numbers. The datum underneath UTM is covered in WGS84 Datum.

Check total station survey for your site options, or book a site visit for your project.

Frequently asked questions

What UTM zone is Delhi in?

Zone 43N, EPSG 32643, with central meridian 75° E.

Is Chennai in zone 43 or 44?

Zone 44N; Chennai lies at about 80.3° E.

When do I need a DGPS survey in the right zone?

Whenever coordinates will be shared with an authority or GIS. The way DGPS works, corrections from ground-based reference stations fix each point, and the zone setting decides how it is stored. See when you need a DGPS survey.

What is the scale factor on a zone's central meridian?

0.9996. It rises towards the zone edges and reaches 1 about 180 km either side of the central meridian.

Is UTM suitable for a small plot?

Yes. Over a plot the distortion is negligible, and UTM coordinates let the plot be placed on any modern map.

Why does my software show zone 43S?

Because the hemisphere setting is wrong. Indian sites are all in the northern hemisphere, so the zone should end in N.

Can I mix zone 43 and 44 coordinates in one drawing?

Not safely. Convert everything to one zone first, otherwise points from the two zones will sit hundreds of kilometres apart on screen.

Written by Saniya Parveen · Technically reviewed by Rahul Rai · Updated 8 November 2026