CSV Lat/Lng Validator
Validate spreadsheet coordinate columns before you plot or geocode further.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, a 200-row event file with three rows whose latitude and longitude traded places gets flagged before the plot scatters those events across the southern ocean.
How to use CSV Lat/Lng Validator
The two columns everything depends on, checked:
The CSV Lat/Lng Validator validates spreadsheet coordinate columns before you plot them or spend geocoding effort. Paste the CSV and check each lat/lng pair for presence, numeric form and sane ranges — the fast pre-flight that keeps spreadsheet geography honest on its way to a map.
- 1Upload or paste CSV.
- 2Confirm lat/lng columns.
- 3Review points on the map.
What people use CSV Lat/Lng Validator for
1. Before plotting points
Every pin map starts as two columns. Validate them and the plot is about geography; skip it and the plot is about debugging. Plotting lives at CSV to Map.
2. Before geocoding spend
Rows whose pairs already validate need no geocoder. The validator sorts the file into ‘already located’ and ‘needs work’ before a single API credit burns.
3. Shared-spreadsheet hygiene
Files many hands edit accumulate creative coordinate formats. A validation pass after each workshop keeps the master sheet plot-ready.
4. Student and citizen data
Class projects and community surveys enter coordinates by hand — enthusiasm high, formatting wild. Validation is the kind gatekeeper.
Worked examples
Chicago written as lat −87.63, lon 41.88 is range-legal and geographically absurd (Antarctic waters). Pair validators catch form; the plot — or the CSV Coordinate Bounding Box — catches swaps. Know which gate you are standing at.
‘41.52.30’ typed from a GPS display is not a decimal and not valid input — it is degrees-minutes-seconds in disguise. Convert the column’s dress first (the coordinate converters), then validate.
Lat/lng column failure gallery
The usual suspects, in order of frequency.
| Symptom | Usual cause |
|---|---|
| Blank pairs | Rows never located — the geocoding queue |
| Text in numeric cells | Notes, units or ‘TBD’ parked in coordinate columns |
| |latitude| over 90 | Longitude filed first — the swap |
| Values in the thousands | Projected or pixel coordinates in a degree column |
| Six decimals everywhere, wrong by miles | Valid form, wrong source — a provenance problem, not a format one |
This validator judges pairs as they will be plotted: latitude first-class, longitude first-class, both numeric and in range. What it cannot judge is whether the pair is the right place — that is source-checking.
Validate coordinates before mapping so one bad column does not corrupt the whole dataset
Coordinate CSV files often fail for predictable reasons: latitude and longitude are swapped, western longitudes lose the minus sign, decimal separators change, headers are ambiguous, or text appears in numeric columns. A validator helps catch those problems before they turn into pins in the wrong country or rejected API requests.
Check plausible ranges as well as syntax. Latitude must fall between −90 and 90 and longitude between −180 and 180, but a value can still be valid numerically and wrong for your project. Plot a sample and compare expected geography before processing the full file.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for CSV Lat/Lng Validator:
- For big CSVs, fix the coordinate columns first and map a sample before mapping everything: auto-detection is good but not magical, and one swapped column renders a beautiful map of the wrong ocean.
- Keep the original file even after converting: GPX→GeoJSON drops timestamps' context, KML→GeoJSON drops styling, and every pipeline has a lossy edge. Originals are cheap; re-acquisition is not.
Limits & appropriate use
File formats support different combinations of geometry, timestamps, properties and styling. Converting between them can lose information, so keep the original and inspect the output before sharing or using it.
Capabilities differ by workspace: check the accepted format and the operations actually offered on this page. Some tools process files locally but may request map tiles or other services over the network; large or specialised datasets may require dedicated GIS software.
- Cadastral/legal formats → jurisdictional land-registry exports.
- Point clouds and rasters → desktop GIS with proper spatial indexes.
- Certified tracks (evidence, insurance) → chain-of-custody originals, untouched.
Data & methodology
The shared CSV workspace maps rows with usable latitude and longitude and reports the number skipped; it is not a complete schema or postal validation service.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- KML
- XML format from the Google Earth era, with styling and ExtendedData.
- GPX
- GPS exchange format: waypoints, tracks, routes, elevation, timestamps.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Map Files. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- The shared CSV workspace maps rows with usable latitude and longitude and reports the number skipped; it is not a complete schema or postal validation service.
- Before relying on the answer
- Inspect the accepted file format and the fields reported by this specific tool. Keep a copy of the original file before converting or editing it.
- What the result cannot establish
- File geometry and recorded timestamps can be incomplete. Verify row or point counts and inspect the exported file in your target application.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
Geocode addresses?
Use the batch geocoder when you have address text instead of coordinates.
Is my uploaded map file sent to a server?
Where a page says browser-first or local processing, the file is handled in your browser. Check the individual tool note for any external-service dependency.
What should I do if a file will not load?
Check that the file type is supported, the structure is valid and the file is within the stated size limits. Converting to GeoJSON, GPX, KML or CSV can also help.
Will converting a file preserve every property?
Not always. Geographic formats support different geometry, style and metadata features, so inspect the output before relying on it.
How is this different from the CSV Coordinate Validator?
Same family, different doorway: that page audits whole-file structure (columns, content classes); this one is the quick pair-focused pre-flight before plotting or geocoding. Files usually meet this one first.
Which column order?
Latitude and longitude columns are identified by their headers — order in the file does not matter, naming does. Rename exotic headers in your pasted copy.
Plus codes or DMS in the columns?
Not decimal pairs — the validator will fail them as non-numeric, correctly. Convert those formats to decimals with the site’s converters first.
What range is ‘sane’?
Latitude −90…90, longitude −180…180, both present and numeric. Beyond ranges, sanity is context (a Kansas file plotting in Kazakhstan is valid and wrong).
Does it plot the points?
Validation is the gate, plotting is the destination — CSV to Map draws the survivors. Keeping the gates separate is what makes each trustworthy.
Rows with addresses but no pairs?
They fail as unlocated — and they are exactly the geocoding queue. The validator’s failure list doubles as the work list.
Scientific notation?
Rare in spreadsheets, parseable where valid — 4.07e1 is 40.7. If your export writes coordinates that way, the export settings deserve the fix.
Related tools and resources
Full audit: the CSV Coordinate Validator; plot the survivors: CSV to Map; convert: the CSV to GeoJSON Converter.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our gis files hub
CSV Lat/Lng Validator sits in the gis files cluster, alongside 64 other tools that answer neighbouring questions with different methods or datasets. It also belongs to the CSV, KML & WKT family.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
KML vs. GeoJSON vs. GPX: Choosing the Right Map File Format — The practical differences between three common geographic file formats — when to use each, what can be lost in conversion, and how to move between them.