How to use the Coordinate Extractor
Paste text containing supported coordinate patterns into the input area, or use Upload. The file picker advertises .txt, .csv, .log, .kml, and .gpx; unsupported dropped files are rejected with an inline error before reading. Results update as you edit the input; there is no separate submit action.
- Paste your text or use Upload to choose a file; you can also drop a file into the input area.
- Review the results table as it updates.
- Use Valid only to hide flagged rows, or choose a value from Format to show one format.
- Use Copy or CSV to export the filtered results.
Review and filter the results
Each row shows Format, normalized Latitude and Longitude, Raw Match, Status, and Source Context. The result labels are DD, DMS, DDM, UTM, and MGRS. Latitude and longitude are displayed to six decimal places. Source Context is a short excerpt containing up to 40 characters before and after the match.
The Format selector includes All formats, Decimal degrees, DMS, DDM, UTM, and MGRS. If the current input or filters leave no rows, the table shows No coordinate pairs found.
Copy or download the extracted coordinates
- Copy places the filtered table data on the clipboard as tab-separated text.
- CSV downloads the filtered results as
coordinates.csv.
Exports include the detected format, normalized coordinates, raw match, validity, note, and source context. If filtering leaves no rows, Copy and CSV return without output.
Supported patterns and important limits
The parser looks for specific patterns rather than every number that resembles a coordinate:
- Signed decimal pairs need decimal points and comma, semicolon, or slash separators. Hemisphere-marked decimal patterns are also supported.
- DMS matches require hemisphere letters and degree/minute markers plus numeric seconds; the seconds marker is optional. DDM matches require hemisphere letters and degree markers; the minute marker is optional.
- UTM matches require a zone number and latitude-band letter, a six-digit easting, and a six- or seven-digit northing. Optional decimal suffixes are included in the coordinate conversion.
- MGRS matches use the implemented zone, grid-letter, and even-digit precision patterns. An unresolved grid square is flagged.
Flagged covers latitude or longitude range failures and unresolved MGRS grid squares. An ambiguous plain decimal pair, where both values are within ±90 and the order could be latitude-first or longitude-first, remains Valid and receives an ambiguity note; Valid only does not hide it. The status is not comprehensive validation of every DMS/DDM minute or second rule or every UTM/MGRS constraint. The tool extracts coordinates already present in the text; it does not geocode addresses, place names, or postal codes. UTM and MGRS conversion is implementation-derived and has no formal accuracy specification; MGRS uses the approximate center of the grid cell.
Browser-side processing and privacy scope
Parsing and coordinate conversion run in browser JavaScript. The tool code does not send pasted or uploaded content to a mapping or geocoding service. This statement covers the tool's input processing, not every script loaded by the surrounding page.
Frequently Asked Questions (FAQs)
What coordinate formats can this tool detect?
It detects supported patterns for decimal degrees, DMS, DDM, UTM, and MGRS. Examples include 40.7128, -74.0060, 40°42'46"N 74°0'21"W, 40°42.767'N 74°0.350'W, 18T 585628 4511322, and 18TWL8562811322 when the pattern can be resolved.
Does this tool geocode addresses or look up place names?
No. It extracts and normalizes coordinate pairs already present in the text. It does not resolve street addresses or place names and the tool code does not call an external mapping or geocoding service.
What does 'flagged' mean in the results?
A row is flagged when latitude or longitude is outside its allowed range or an MGRS grid square cannot be resolved. An ambiguous plain decimal pair remains Valid with an ambiguity note, so Valid only does not hide it. The status is not a complete validation of every coordinate rule.
Is my data safe when I paste it here?
The tool parses and converts input in browser JavaScript, and its tool code does not send pasted or uploaded content to a mapping or geocoding service. This statement covers the tool's input processing, not every script loaded by the surrounding page.