UTM latitude band letter
Latitude 40.7128 is band T, which covers 40° to 48° north. Enter a latitude between 80° south and 84° north and get its letter, the edges of that band and whether it lies north or south of the equator. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Latitude
- 40.7128
- Letter
- T
- Band south
- 40
- Band north
- 48
- Hemisphere
- N
Universal Transverse Mercator grid references combine a numeric longitude zone with a single latitude band letter so field crews can read a short zone designator without spelling out full projected metres. This UTM latitude band letter calculator accepts one WGS84 latitude in decimal degrees and returns the letter from C near eighty degrees south through X near eighty-four degrees north, plus the southern and northern edges of that band and a simple N or S hemisphere flag. Survey students, GIS pipelines, and map-label tools need the same deterministic C-to-X table every time they check a textbook grid or a mobile pin.
How UTM latitude band letters C through X are defined
Universal Transverse Mercator divides the Earth into sixty six-degree longitude zones and, independently, into twenty latitude bands labelled with capital letters. Starting at eighty degrees south, each ordinary band is eight degrees tall: C covers minus eighty to minus seventy-two, D covers minus seventy-two to minus sixty-four, and the sequence continues through H, then jumps to J because the letter I is omitted to avoid confusion with the digit one.
After M (just south of the equator) comes N for the first northern eight-degree strip, then P through W, skipping O so the letter is never mistaken for a zero. The final band X is special: it is twelve degrees tall and runs from seventy-two degrees north to eighty-four degrees north so that standard UTM can cover the Arctic lands that still use UTM rather than polar stereographic UPS.
Hemisphere for display is simply north when latitude is greater than or equal to zero and south otherwise; that flag is not the same as the band letter, which already encodes latitude strip identity more finely than N versus S alone. This capability implements exactly that published table: index equals floor of latitude plus eighty divided by eight, with latitude eighty-four clamped onto letter X, and it never invents letters A, B, Y, or Z that appear only in other military or polar schemes.
Where the band letter comes in handy
Classrooms teaching map reading ask students to name the UTM band for cities from Sydney under H to London under U; a deterministic oracle marks answers without pulling a full projection library. Field apps that already store decimal degrees can stamp the letter onto a waypoint label before the heavier easting-northing step runs offline. Quality-control scripts that validate MGRS or truncated UTM strings can call this small parse path first to confirm the latitude letter portion before checking zone digits and metre digits.
Failed validation does not consume balance.
What you can do with it
Map-reading homework and exams
Give learners a latitude and check the UTM band letter C–X against the standard eight-degree (or twelve-degree X) table without a full projection stack.
Waypoint and grid labels
Stamp the latitude band letter onto field waypoints or sample UTM designators when you already have decimal degrees and only need the letter.
Pipeline validation of grid strings
Confirm the latitude letter portion of truncated UTM or teaching grids before heavier zone, easting, and northing checks run.
FAQ
How do I get the UTM latitude band letter from a latitude?
Send a finite lat (or latitude / y) in decimal degrees within −80 to 84.
Why are letters I and O missing?
Standard UTM omits I and O so band letters are not confused with the digits 1 and 0 in grid references. The twenty letters used are CDEFGHJKLMNPQRSTUVWX.
Why is band X wider than the others?
Bands C–W are eight degrees tall. Band X spans twelve degrees from 72°N to 84°N so standard UTM can cover high northern latitudes still mapped in UTM rather than UPS.
What latitudes are rejected?
Use a polar system such as UPS for those regions.
Does band letter S mean the southern hemisphere?
No. The letters do not stand for north and south: N is the first band above the equator, and every letter from N to X lies in the northern hemisphere, so S is a northern band. The separate hemisphere flag tells you north or south.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/geo/utm-zone-letter \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"lat":40.7128}'const res = await fetch("https://api.kit.forhosting.com/geo/utm-zone-letter", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"lat": 40.7128
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/geo/utm-zone-letter",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"lat": 40.7128
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/geo/utm-zone-letter", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"lat":40.7128}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"lat":40.7128}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/geo/utm-zone-letter", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"lat": 40.7128
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "geo.utm_zone_letter",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Standard UTM coverage stops at those latitudes; polar points belong to UPS and are rejected with a clear invalid_input error instead of a guessed letter.
Input contract, response fields, and error behaviour
Basic range checks allow any finite latitude between minus ninety and ninety, but a successful band lookup further requires the standard UTM coverage interval from minus eighty through eighty-four inclusive. String numbers are accepted when they match a strict finite numeric pattern so form posts and query adapters work without a separate parse step. POST a JSON body with one required finite number: lat (aliases latitude and y) in decimal degrees on the WGS eighty-four geographic system. On success the response echoes lat, sets letter to a single uppercase character from the set CDEFGHJKLMNPQRSTUVWX, sets band_south and band_north to the inclusive southern and exclusive-style northern edges in degrees for ordinary eight-degree bands (X uses seventy-two and eighty-four), sets hemisphere to N or S, and sets message to a short English summary such as which band covers which strip. Missing fields, empty strings, non-finite values, and latitudes outside the UTM coverage band fail with invalid_input and are not billed. Pair this endpoint with a longitude-zone calculator or a full lat-lon to UTM converter when you also need zone numbers, easting, and northing; this landing answers only the latitude band letter question that people type when they already know roughly where they are and need the letter for a grid designator or a teaching exercise.
Where a latitude band letter API earns its keep
Keep the request to a single latitude, pin the letter and band edges in tests, and you get reproducible band letters for homework, GIS helpers, and edge workers without standing up PROJ or a desktop GIS of your own.
Technical questions
What does the UTM latitude band letter tool cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.