September 20, 2026 · 7 min read · MapBench editorial
How to Find the Latitude and Longitude of Any Place
Latitude and longitude are the two numbers that pin a place to the globe. You need them when a form asks for coordinates, when you drop a point into GIS software, or when you want to share a location that has no reliable street address. The process is simple; the mistakes are repetitive: swapped order, too few decimals, or DMS pasted into a box that only accepts decimal degrees.
Three reliable ways to get coordinates
- Search: type the place name or address into a latitude/longitude finder and read the result
- Click: open the map, click the exact building or path, copy the numbers from the pin
- GPS: use ‘my location’ when you are physically there and the phone has a fix
Search is only as good as the gazetteer. Famous landmarks resolve cleanly; informal local names may not. Clicking the map is often more honest for ‘this corner of the car park.’ GPS is best when you are on site, not when you are planning from the sofa.
Decimal degrees, and how many places to keep
Most web tools and APIs want decimal degrees: 40.7128, −74.0060. Negative latitude is south; negative longitude is west. Five decimal places is about 1.1 metres of latitude — enough for everyday mapping. Six is finer than consumer GPS usually justifies. Writing seven or eight digits does not make a phone more accurate; it only pretends.
When you only have DMS or a different grid
Paper charts and older instruments often show degrees, minutes, and seconds. Convert them to decimal degrees before feeding web tools. UTM and MGRS are grid systems used in surveying and military maps; convert those when your source data is not lat/lng at all. Keep the original string in a note so you can audit later.
Going the other way: coordinates to an address
Reverse geocoding turns a point into the nearest labelled address or administrative names. Coverage is dense in well-mapped cities and thin in remote areas. A point in the water or on a large campus may return only a coarse region. That is a data limitation, not a failure of arithmetic.
The toolkit behind this post, in depth
Latitude and Longitude Finder
This is the platform's universal coordinate picker: click or drag on the map and the panel instantly shows the point in decimal degrees, degrees-minutes-seconds, UTM zone/easting/northing, MGRS grid reference and Open Location (Plus) Code — each with its own copy button. Zoom controls the precision you can read, and five decimals already lands within about a metre. It is the page to keep bookmarked whenever another system asks 'what are the coordinates of this spot?'
Everything converts locally in your browser using standard WGS84 geodetic formulas, including the official Norway/Svalbard UTM zone exceptions, so the numbers you copy are interoperable with GPS devices, GIS software and mapping APIs. The current point lives in the URL, making any lookup shareable and reproducible — useful for property notes, field reports and support tickets. Pair it with the reverse geocoder when you also need the address, or feed the copied pair into distance, radius and elevation tools for deeper analysis.
Address to Coordinates
Geocoding is the forward direction of the address/coordinate bridge: type any address, landmark or place name and receive precise decimal latitude and longitude, pinned on the map and ready to copy into GPS devices, spreadsheets or API calls. Suggestions stream in as you type from the Photon geocoder, an OpenStreetMap-based service tuned for fast type-ahead search, so typos and partial addresses still land on the right feature. Each result shows its full disambiguation line — street, city, country — so 'Springfield' never silently picks the wrong state.
Typical jobs include programming a satnav, anchoring a delivery note, tagging a property listing, planning a meet-up, or seeding the distance and radius tools with exact endpoints. Because results are coordinates on the WGS84 datum, they drop directly into every other MapForge tool and into consumer GPS ecosystems. Accuracy follows the query: house-number addresses usually resolve within tens of metres, city queries to the settlement centre. The service is free and keyless for interactive use; for production-scale geocoding the fair-use notes on our data sources page explain how to stay a good citizen.
Coordinates to Address
Every coordinate pair describes one unique spot on Earth, but humans think in addresses. This tool bridges the two: paste any latitude/longitude pair — decimal degrees like 40.7128, -74.0060 or DMS like 40°26'46"N — and it returns the closest postal address, displayed both as a full line and as structured components you can copy individually. The map recentres on your point so you can visually verify the result before trusting it, which is exactly the workflow photographers, drone pilots, field scientists and delivery dispatchers need when reconciling GPS records with paperwork.
Because the conversion is powered by OpenStreetMap's Nominatim engine, coverage is worldwide and continuously improved by mappers: street-level detail in cities, settlement-level in remote regions. The tool validates your input first — latitudes beyond ±90 or longitudes beyond ±180 are rejected with a clear message instead of a silent wrong answer — and the resulting link stores your coordinates in the URL so a colleague can reopen the exact same lookup. Nothing is uploaded or stored server-side; the only outgoing request carries the coordinates you asked about.
Decimal to DMS
Decimal 40.44611 becomes 40° 26' 46.00" N in one keystroke. This tool converts decimal degrees into degrees, minutes and seconds with hemisphere letters — the notation printed on nautical charts, used in astronomy circles, and required by legacy forms and some GPS devices. Two-decimal seconds preserve roughly a third of a metre, more precision than any consumer receiver can claim, and the display keeps both the pretty string and the raw values for copying.
Sign conventions are handled the way standards expect: negative latitudes become south, negative longitudes west, so there is never a minus sign and a letter competing. The converter runs entirely in your browser and pairs naturally with its inverse, the DMS-to-decimal tool, and with the all-format coordinate converter when UTM or MGRS outputs are also needed. A small reference on the page reminds you what each decimal place is worth in metres — the quickest way to choose sensible rounding for your use case.
DMS to Decimal
Degrees-minutes-seconds is the notation of paper charts, old surveys and many handheld GPS screens; decimal degrees is what every web map, API and spreadsheet wants. Paste values like 40°26'46"N 79°58'36"W — hemisphere letters, minus signs or mixed separators all accepted — and get clean signed decimal pairs ready to copy. The parser validates ranges (latitude ≤ 90, longitude ≤ 180) and explains failures instead of guessing.
The arithmetic is the classic sexagesimal expansion — degrees plus minutes over 60 plus seconds over 3600 — with south and west becoming negative, and the page shows the mapping explicitly so students learn rather than just copy. Precision is preserved to the sub-metre level your input carries. When the source is already decimal and the destination must be chart notation, the decimal-to-DMS tool runs the conversion in reverse; for UTM, MGRS or Plus Code targets, the all-in-one converter covers the rest of the family.
Coordinate Converter
Paste a coordinate in any supported notation — decimal degrees, DMS, UTM easting/northing with zone, MGRS grid reference or Plus Code — and this converter recognises the format and shows all the others simultaneously, updating on every keystroke. It is the Swiss-army page for anyone translating between worlds: GPS hobbyists (DMS), survey-adjacent work (UTM), military and search-and-rescue literature (MGRS), and shareable short codes (Plus Codes). The recognised source format is always labelled, so you know what the parser understood.
All math is local and standards-based: WGS84 throughout, official UTM zone exceptions included, MGRS precision following your digit count (10 digits ≈ 1 m). Clicking the map feeds coordinates back into the input, closing the loop between visual and textual workflows. Only the map preview needs a network connection; the conversions themselves work offline. For single-direction jobs the dedicated DMS and UTM pages are leaner, and for naming the point the reverse geocoder adds the address layer.
UTM Converter
Universal Transverse Mercator expresses position as zone, easting and northing in metres — the grid of field navigation, topographic sheets and much engineering work. This tool converts in both directions: paste lat/long to get zone, hemisphere, easting and northing on the WGS84 datum, or paste a UTM triple (like '32N 500000 4600000') to get decimal coordinates, with a map preview to verify visually. The full standard series is implemented, including the widened zones 31–37 around Norway and Svalbard.
Because both directions use the same reference ellipsoid (WGS84, the GPS datum), round-trips are exact at display precision; if your source material is on an older local datum such as NAD27, convert datums first — a mismatch there shows up as a consistent offset, and the page says so plainly. Survey-adjacent professionals, hikers reading topographic maps, and drone operators filing in grid references are the core users. MGRS, the letter-based cousin of UTM, has its own converter one link away.
MGRS Converter
MGRS encodes a UTM position as a short, unambiguous string — zone, band letters, grid square and numeric easting/northing — where the digit count sets precision: 4 digits ≈ 1 km, 6 ≈ 100 m, 10 ≈ 1 m. Paste a reference like 33UUP 05300 21500 and the tool decodes it to decimal latitude/longitude and pins it on the map; paste coordinates and it encodes MGRS at your chosen precision. Spaces are optional, case insensitive, validation strict.
The encoding implements the official column/row lettering schemes and latitude bands, so results interoperate with military, SAR and orienteering materials. The map preview is the safety net: a single mistyped letter moves you 100 km, and seeing the pin land wrong is how operators catch it. Because MGRS is notation on top of the UTM grid, the UTM converter sits one click away for the numeric view, and the coordinate converter bundles everything when you are unsure which system a source string uses.
The many languages of a single point
One physical spot on Earth can be written a dozen ways: decimal degrees for software, degrees-minutes-seconds for charts and handhelds, UTM eastings and northings for field work, MGRS lettered squares for military prose, Plus Codes for places without addresses. None is more 'true' — they are notations over the same WGS84 datum, the reference frame GPS itself speaks. Conversion between them is exact math, which is why it can run entirely in your browser with no service and no error creeping in.
The traps are human, not mathematical. Swapping latitude and longitude is the classic — GeoJSON stores [lng, lat] while most APIs expect (lat, lng), and an offshore point is usually that typo. Hemisphere letters and minus signs must never coexist. And precision has a physical meaning: each added decimal degree is roughly a tenfold shrink, so five decimals is about a metre, six is beyond what consumer GPS can claim. Choosing rounding deliberately is choosing honesty.
Datums are the deep end: coordinates are angles against a model of Earth's shape, and older local datums (NAD27 and friends) shift the same physical point by tens of metres relative to WGS84. A consistent, unexplained offset between an old survey and your GPS is usually that story. For everyday web mapping the datum is WGS84 end to end, and keeping everything in it — as these tools do — makes round trips exact.
Coordinate hygiene for people who reuse data
Coordinates are the one geographic asset that can be perfectly lossless — if you keep discipline. One datum (WGS84), one notation in storage (decimal degrees), one precision policy (five or six decimals), and conversions only at the display edge. Every deviation from that recipe taxes you later: mixed DMS strings in a column, NAD27 relics in an old shapefile, seven-decimal theatre in a CSV. The converters exist to absorb that variety at the border so your interior stays clean.
The second discipline is visual verification. A coordinate pair is two numbers; a pin on a map is a fact. Swapped axes, wrong hemispheres, degree/minute confusion — every classic error is instantly visible as a pin in the wrong ocean or the wrong hemisphere, and instantly invisible in a table. Professionals therefore make the map check a ritual: paste, look, then trust. At five decimals you are resolving metres; at that scale the eye, not the arithmetic, is the quality gate.
- Store decimal degrees, WGS84, signed; convert to DMS/UTM/MGRS only for the reader who needs them.
- Validate ranges on ingest (|lat| ≤ 90, |lng| ≤ 180) and reject, don't clip, out-of-range rows.
- Make the map-pin sanity check mandatory for any coordinate you didn't generate yourself.
- When receiving UTM or MGRS strings, record the original alongside the conversion — provenance prevents arguments.
Honest limits & when to escalate
Coordinates are lossless in principle and lossy in practice, and every loss is human: swapped axes, wrong hemispheres, datum relics, precision theatre. The converters eliminate the notation problem completely — DMS, UTM, MGRS and Plus Codes are exact translations on WGS84 — but they cannot eliminate the provenance problem: a number without its datum and its source is a rumour. Old NAD27-era documents, hand-typed sheets and seven-decimal CSVs each carry their own failure signature, and the honest tool answers with validation errors and visible pins rather than silent corrections.
The practical boundary is therefore organisational, not mathematical: teams that standardise storage (decimal, WGS84, sane precision) and ritualise the map check enjoy a lossless system; teams that don't accumulate expensive folklore. For work beyond consumer frames — control points, machine guidance, legal description — the escalation is geodetic: licensed surveyors, published transformations and national datums. Everything between a pasted waypoint and that door is exactly where this toolset lives.
- Datum-critical legacy data → published grid transformations (NTv2/HTDP).
- Control points and machine guidance → licensed geodetic survey.
- Aviation/marine charts → the chart's own datum and notation, verbatim.
- Massive pipelines → scripted validation with rejection, not clipping.