Why coordinates are rejected as invalid
A coordinate is "invalid" when the tool receiving it cannot interpret the input as a recognisable location. This does not necessarily mean the coordinate is wrong. It often means the coordinate is written in a way the parser cannot handle.
The most common structural problems are: extra text mixed in with the numbers, wrong or missing symbols (degree signs, quote marks, hemisphere letters), values outside the valid range for the format, incomplete coordinates with missing components, and format ambiguity where the tool cannot determine which format the input belongs to.
Fix 1: Remove extra text and labels
Coordinates copied from reports, emails, PDFs, and spreadsheets often arrive with labels, notes, or descriptions attached. "Lat: 51.5074 N (GPS)" contains a valid coordinate, but the surrounding text prevents most parsers from extracting it.
The fix is simple: strip everything except the coordinate itself. Remove words like "Latitude:", "Easting:", row numbers, unit labels, and trailing comments. If you are working with bulk data, do this for every line before pasting into the converter.
- Remove "Lat:", "Long:", "E:", "N:", and similar labels.
- Remove brackets, parentheses, and any text in parentheses.
- Remove unit labels like "m", "metres", "degrees".
- If copied from a spreadsheet, paste into a plain text editor first to strip hidden formatting characters.
Fix 2: Replace wrong or missing symbols
DMS and DDM coordinates use degree symbols (°), single quotes for minutes ('), and double quotes for seconds ("). If these are replaced with look-alike characters, the parser will reject the input. Word processors often auto-correct straight quotes into curly ("smart") quotes, and the degree symbol may be replaced with the masculine ordinal indicator (º) or other Unicode characters.
| Problem | Wrong character | Correct character |
|---|---|---|
| Degree symbol | º (ordinal) | ° (degree) |
| Minutes | ‘ or ’ (smart quote) | ' (straight quote) |
| Seconds | “ or ” (smart double) | " (straight double quote) |
| Decimal separator | , (comma) | . (period) |
| Negative sign | en dash or em dash | - (hyphen-minus) |
Fix 3: Check values are within valid ranges
Latitude must be between -90 and +90. Longitude must be between -180 and +180. DMS minutes and seconds must each be between 0 and 59. If any value exceeds its valid range, the coordinate is rejected.
The most common cause of out-of-range values is reversed latitude and longitude. If one value is larger than 90, it is almost certainly the longitude and should come second. Swapping the two values often solves the problem immediately.
For UTM coordinates, check that the easting is between 100,000 and 900,000 and the northing is between 0 and 10,000,000. For UK Grid references, check that the grid square letters are valid and the digit count is even.
Fix 4: Complete the missing parts
Coordinates need all their components to work. A latitude without a longitude, a UTM easting without a zone, or a UK Grid reference without its two-letter square are all incomplete and cannot be plotted.
- For lat/long: make sure both values are present, separated by a comma or space.
- For UTM: include the zone number and hemisphere letter (e.g. "30N") before the easting and northing.
- For UK Grid: include the two-letter grid square at the start.
- For DMS: make sure degrees, minutes, and seconds are all present for both latitude and longitude.
Fix 5: Clarify the format
If the tool cannot determine which format the input belongs to, it may reject it as ambiguous. This is common with values like "51 29 19 0 0 52" which could be DMS without symbols, or two sets of three numbers with an unclear meaning.
Adding the appropriate symbols, hemisphere letters, or separators usually resolves the ambiguity. For DMS, add degree, minute, and second symbols. For DD, make sure there are only two decimal numbers separated by a comma. For UTM, include the zone prefix.
If the ambiguity is that you genuinely do not know what the numbers are, run one pair through the Coordinate Format Identifier first. Once you know the system, you know which parts are missing and what needs adding.
Cleaning invalid coordinates in bulk
When working with a dataset of many coordinates, it is common for most lines to parse correctly while a few fail. Rather than abandoning the whole batch, isolate the failing lines and fix them individually.
- Paste the full dataset into CoordinateMapper and note which lines fail.
- Check whether the failing lines share a common problem (e.g. all have extra text, or all are missing the hemisphere letter).
- Fix the common problem across all failing lines at once.
- Re-paste and verify that all lines now parse correctly.
- If different lines have different problems, fix them one category at a time.
When coordinates are genuinely wrong
Sometimes a coordinate is not just badly formatted but actually incorrect. The numbers may have been corrupted, truncated, or entered from memory rather than copied from a reliable source. In these cases, no amount of formatting cleanup will produce the right location.
If a coordinate parses successfully after cleaning but plots in a clearly wrong location, the problem is likely with the data itself rather than the formatting. Go back to the original source and verify the values before relying on the converted output.
Takeaway
Most invalid coordinates are valid locations written in a way the parser cannot handle. The five most common fixes are: removing extra text, replacing wrong symbols, checking value ranges, completing missing parts, and clarifying the format. Working through these in order resolves the vast majority of parsing failures. For bulk data, isolate the failing lines and fix them by category rather than one at a time.