GPS Coordinate Conversion Tips and Common Mistakes

The costliest coordinate mistakes are silent ones — a dropped negative sign, minutes read as seconds, or the wrong hemisphere — each of which can place a point tens or thousands of kilometres from where it belongs. Coordinate conversion is simple arithmetic, but the notation traps are easy to fall into. This guide covers the best practices that keep DD, DMS and DDM conversions accurate, and the errors that catch even experienced surveyors and pilots.

The mistakes that move points the furthest

• Losing the hemisphere sign. In decimal degrees the sign is the hemisphere: negative longitude is west of Greenwich, negative latitude is south of the equator. Drop the minus on New York's -74.0060 and you land in western China. Always confirm the sign, or keep the N/S/E/W letter until the last step.
• Confusing minutes and seconds. DMS splits each degree into 60 minutes and each minute into 60 seconds. Reading 40°26.767' (decimal minutes) as 40°26'767" is nonsense — seconds never exceed 60. Know which format you are holding before you convert.
• Swapping latitude and longitude. Web maps and GeoJSON often expect longitude first, while almost everyone speaks "lat, long." A reversed pair can put an ocean point on land. Latitude is capped at ±90; if a value exceeds that, it is your longitude.
• Ignoring the degree/minute markers. Pasting "40 26 46" without knowing the units invites guesswork. Keep the °, ' and " symbols so the parser and your reader both know the structure.

Get precision right — and don't overdo it

More decimals is not always better; it just implies accuracy you may not have. Match the precision to the job.

Decimal places	Approx. accuracy at equator	Good for
3	~110 m	Rough town/area location
4	~11 m	Street or building
5	~1.1 m	Most consumer GPS work
6	~0.11 m	Survey-grade detail

Consumer GPS is only accurate to a few metres, so five or six decimals is plenty. Reporting eight decimals from a phone reading is false precision — it looks exact but isn't.

Match the format to the tool you're feeding

Each domain expects a specific notation, and handing over the wrong one causes silent import failures:

• Web maps, GeoJSON, APIs: signed decimal degrees (no N/S/E/W letters).
• Aviation and marine GPS: degrees decimal minutes (DDM), e.g. 40°26.767'N.
• Legal land descriptions and surveys: degrees-minutes-seconds (DMS).

The ByteTools converter parses any of these — 40.7128, 40°26'46"N, 40 26 46 N or 40°26.767'N — and shows all three at once, so you can copy exactly the notation the target expects instead of hand-converting and risking a slip.

One more gotcha: datums

Converting between DD, DMS and DDM only changes notation, not the underlying reference frame. If your source uses a different datum than your destination (for example an old local datum versus WGS84), the numbers can still be off by many metres even after a perfect format conversion. When precision matters, confirm both systems use the same datum before trusting the result.

Try the Coordinate Converter — free and 100% in your browser.

FAQ

Why did my converted point end up in the wrong hemisphere?

Almost always a lost sign or a dropped N/S/E/W letter. West and South values must be negative in decimal degrees. Keep the hemisphere letter through the conversion and only drop it once the sign is applied.

How do I know if a value is decimal minutes or seconds?

Seconds never exceed 60 and DMS has three parts (degrees, minutes, seconds). Decimal minutes has two parts with a fractional minute, like 26.767'. If the last number has a decimal point and there's no seconds field, it's DDM.

Is more decimal precision always better?

No. Precision beyond your GPS's real accuracy is misleading. Five decimals (~1 m) suits most fieldwork; six is survey-grade. Reporting more than your source supports implies accuracy you don't actually have.

Does converting formats fix a datum mismatch?

No. Format conversion changes only how the numbers are written, not the geodetic datum. If source and destination use different datums, apply a proper datum transformation as well, or the point can still be metres off.

Related free tools

• Latitude Longitude Finder — pull exact coordinates from a map.
• Distance Calculator — measure between two points once converted.
• KML Circle Generator — build map overlays from a center point.
• Unit Converter — switch between metres, feet and nautical units.

Built by ByteVancer

ByteTools is a free product of ByteVancer, a software and web development studio building web apps, SaaS platforms and custom software — including mapping and geospatial features. If you're building something location-aware, see how ByteVancer can help.