Coordinate systems

UTM zone by city

The zone for a city is a one-line fact: Mumbai is 43N, EPSG:32643. The useful question is the one after it - how close is that city to the edge of its zone, because a site a few kilometres the wrong way belongs in the next zone along and will not line up if you assume otherwise. London sits 9 km from the zone 31 boundary, so a single survey across greater London crosses it.

On this page
  1. How the zone is worked out
  2. Why the distance to the edge is the column that matters
  3. Two places where the formula is wrong
  4. When a site crosses two zones
  5. Your site is not the city centre
  6. Zone and EPSG code for 75 cities
  7. Try these codes on your own coordinates
  8. Questions people ask

How the zone is worked out

UTM divides the world into 60 strips of longitude, each 6 degrees wide. The number is floor((longitude + 180) / 6) + 1, counting east from the antimeridian, so zone 1 starts at 180 degrees west and zone 60 ends back at it.

The EPSG code then follows from the hemisphere. On WGS 84 the northern zones are EPSG:326 followed by the two-digit zone, and the southern ones are EPSG:327 followed by it. Zone 43 north is EPSG:32643 and zone 43 south is EPSG:32743. They are different coordinate systems, not two views of one.

Each zone has its own central meridian, three degrees in from the western edge, where the scale factor is 0.9996. Scale is slightly too small there and slightly too large at the edges, which is the deliberate trade. On the central meridian that is one part in 2500, roughly 40 cm per kilometre; toward the edge the scale passes back through unity and reaches about one part in 1000 near the equator.

Why the distance to the edge is the column that matters

A zone is about 670 km wide at the equator and much narrower further north: at 52 degrees it is only around 410 km. Plenty of cities sit close enough to an edge that an ordinary project crosses it.

London is the clearest case in the table. It sits at 0.13 degrees west, which is about 9 km from the zone 30 and 31 boundary running down the prime meridian. Greenwich is in zone 31. A borough-wide survey that assumes zone 30 throughout is working across a zone edge, and eastings restart at each one.

Hyderabad is 52 km from the 44 and 43 boundary, and Delhi 77 km. Those are comfortable for a single site and tight for a corridor. The number is worth checking before the flight rather than after the processing.

Two places where the formula is wrong

The standard carries two exceptions, and a surprising number of online calculators implement only the formula and return the wrong zone for both.

Southwest Norway: between 56 and 64 degrees north, zone 32 is widened westward to start at 3 degrees east rather than 6, taking three degrees from zone 31 so the mainland coast stays in one zone. Bergen sits at 5.32 degrees east. The formula says zone 31; the correct answer is zone 32, EPSG:32632.

Svalbard: between 72 and 84 degrees north the odd zones are widened and zones 32, 34 and 36 are not used at all. Zone 31 covers 0 to 9 degrees east, zone 33 covers 9 to 21, zone 35 covers 21 to 33 and zone 37 covers 33 to 42. Ny-Alesund sits at 11.92 degrees east, so the formula says zone 32 - a zone that does not exist at that latitude - while the correct answer is zone 33.

The table below applies both exceptions, and the zone finder applies them to any point you give it.

When a site crosses two zones

Eastings restart in every zone, so two points in different zones can carry almost identical coordinates while being hundreds of kilometres apart. Nothing in a coordinate file warns you about this; the data simply folds over itself.

There are three honest ways out. Extend one zone past its nominal edge and accept the growing distortion, which is normal practice for a few tens of kilometres as long as it is written down. Split the deliverable at the boundary and hand over two datasets. Or use a national grid designed to span the whole country, which is exactly why the British National Grid, Lambert-93 and their equivalents exist.

What you must not do is let half the data sit in one zone and half in the other without saying so.

Your site is not the city centre

Every row here is a city centre, which is the right answer for the question people type and the wrong answer for a survey ten kilometres out of town. A city close to an edge may well have its suburbs on the other side.

Use the table to orient yourself, then put your actual coordinates into the zone finder. It takes a map click, typed coordinates or your current location and returns the zone, the EPSG code, the central meridian and the MGRS grid square for that exact point, exceptions included.

UTM zone and EPSG code for 75 cities

City-centre coordinates. The city name opens the zone finder on that point so you can move the pin to your actual site; the EPSG code opens the converter with that system selected.

Closest to a zone boundary. Under 40 km, a project of any size is likely to cross into the next zone: Stockholm (4 km from zone 33), London (9 km from zone 31), Dublin (17 km from zone 30), Hong Kong (17 km from zone 49), Atlanta (36 km from zone 17), Tromso (37 km from zone 33).

CityCountryZoneEPSGCentral meridianTo zone edge
MumbaiIndia43NEPSG:3264375°E92 km
DelhiIndia43NEPSG:3264375°E77 km
BengaluruIndia43NEPSG:3264375°E44 km
ChennaiIndia44NEPSG:3264481°E246 km
KolkataIndia45NEPSG:3264587°E168 km
HyderabadIndia44NEPSG:3264481°E52 km
PuneIndia43NEPSG:3264375°E196 km
AhmedabadIndia43NEPSG:3264375°E59 km
JaipurIndia43NEPSG:3264375°E220 km
LucknowIndia44NEPSG:3264481°E293 km
SuratIndia43NEPSG:3264375°E86 km
KochiIndia43NEPSG:3264375°E190 km
KarachiPakistan42NEPSG:3264269°E101 km
DhakaBangladesh46NEPSG:3264693°E42 km
ColomboSri Lanka44NEPSG:3264481°E206 km
New YorkUnited States18NEPSG:3261875°W169 km
Los AngelesUnited States11NEPSG:32611117°W162 km
ChicagoUnited States16NEPSG:3261687°W196 km
HoustonUnited States15NEPSG:3261593°W61 km
PhoenixUnited States12NEPSG:32612111°W179 km
DenverUnited States13NEPSG:32613105°W256 km
SeattleUnited States10NEPSG:32610123°W175 km
San FranciscoUnited States10NEPSG:32610123°W213 km
MiamiUnited States17NEPSG:3261781°W220 km
BostonUnited States19NEPSG:3261969°W77 km
AtlantaUnited States16NEPSG:3261687°W36 km
DallasUnited States14NEPSG:3261499°W75 km
TorontoCanada17NEPSG:3261781°W111 km
VancouverCanada10NEPSG:32610123°W209 km
MontrealCanada18NEPSG:3261875°W122 km
Mexico CityMexico14NEPSG:3261499°W301 km
LondonUnited Kingdom30NEPSG:326303°W9 km
ParisFrance31NEPSG:326313°E172 km
BerlinGermany33NEPSG:3263315°E95 km
MadridSpain30NEPSG:326303°W195 km
RomeItaly33NEPSG:3263315°E41 km
AmsterdamNetherlands31NEPSG:326313°E74 km
ZurichSwitzerland32NEPSG:326329°E192 km
StockholmSweden34NEPSG:3263421°E4 km
WarsawPoland34NEPSG:3263421°E204 km
DublinIreland29NEPSG:326299°W17 km
LisbonPortugal29NEPSG:326299°W248 km
IstanbulTurkey35NEPSG:3263527°E86 km
MoscowRussia37NEPSG:3263739°E101 km
OsloNorway32NEPSG:326329°E70 km
BergenexceptionNorway32NEPSG:326329°E128 km
TromsoNorway34NEPSG:3263421°E37 km
Ny-AlesundexceptionSvalbard33NEPSG:3263315°E62 km
DubaiUnited Arab Emirates40NEPSG:3264057°E128 km
RiyadhSaudi Arabia38NEPSG:3263845°E134 km
TehranIran39NEPSG:3263951°E236 km
CairoEgypt36NEPSG:3263633°E119 km
LagosNigeria31NEPSG:326313°E290 km
NairobiKenya37SEPSG:3273739°E91 km
JohannesburgSouth Africa35SEPSG:3273527°E195 km
Cape TownSouth Africa34SEPSG:3273421°E39 km
TokyoJapan54NEPSG:32654141°E149 km
SeoulSouth Korea52NEPSG:32652129°E86 km
BeijingChina50NEPSG:32650117°E206 km
ShanghaiChina51NEPSG:32651123°E140 km
Hong KongHong Kong50NEPSG:32650117°E17 km
SingaporeSingapore48NEPSG:32648105°E203 km
BangkokThailand47NEPSG:3264799°E162 km
JakartaIndonesia48SEPSG:32748105°E128 km
ManilaPhilippines51NEPSG:32651123°E106 km
SydneyAustralia56SEPSG:32756153°E112 km
MelbourneAustralia55SEPSG:32755147°E85 km
BrisbaneAustralia56SEPSG:32756153°E294 km
PerthAustralia50SEPSG:32750117°E176 km
AucklandNew Zealand60SEPSG:32760177°E68 km
Sao PauloBrazil23SEPSG:3272345°W139 km
Buenos AiresArgentina21SEPSG:3272157°W148 km
LimaPeru18SEPSG:3271875°W104 km
SantiagoChile19SEPSG:3271969°W124 km
BogotaColombia18NEPSG:3261875°W230 km

Rows marked exception are decided by the standard's Norway or Svalbard rules rather than the formula, which is where calculators that implement only the formula go wrong. The UTM zone finder applies both to any point, and returns the MGRS grid square with it.

Try these codes on your own coordinates

Each one opens the converter with that system already selected. Nothing is uploaded; the projection runs in your browser.

Questions people ask

What UTM zone is Mumbai in?

Mumbai is in UTM zone 43 north, EPSG:32643, with a central meridian of 75 degrees east. It sits about 92 km from the zone 42 boundary to the west, so a normal city project stays inside one zone.

What UTM zone is Delhi in?

Delhi is in UTM zone 43 north, EPSG:32643, the same zone as Mumbai, Bengaluru, Pune and Ahmedabad. It lies about 77 km west of the boundary with zone 44, which is where Hyderabad, Chennai and Lucknow fall.

How do I find the zone for a place that is not in the table?

Use the UTM zone finder: click the map, type coordinates or use your current location. It returns the zone, EPSG code, central meridian and MGRS grid square, and it applies the Norway and Svalbard exceptions. For a rough answer by hand, the zone is floor((longitude + 180) / 6) + 1.

Why do some calculators give Bergen a different UTM zone?

Because they implement the formula and skip the exceptions. Between 56 and 64 degrees north, zone 32 is widened west to 3 degrees east so that southwest Norway stays in one zone. Bergen at 5.32 degrees east is therefore zone 32, not the zone 31 the formula produces.

Is the zone number the same north and south of the equator?

The number is the same because it depends only on longitude, but the coordinate system is not. Northern zones are EPSG:326xx and southern zones EPSG:327xx, and the southern ones add a 10,000,000 m false northing so values stay positive. Zone 43N and zone 43S are different systems.

My site crosses two UTM zones. What should I do?

Pick one zone and extend it past its edge, documenting the choice, if the overrun is a few tens of kilometres. Otherwise split the deliverable at the boundary, or move to a national grid built to span the country. Do not mix zones silently in one dataset, because eastings restart in each zone.

Need the zone for a specific place? The UTM zone finder gives the zone, EPSG code and MGRS grid square from a map click.