CSV to GeoJSON Converter
Turns any spreadsheet of point locations — asset inventories, survey results, store locators — into something a web map can render.
Common issues converting CSV to GeoJSON
- Coordinate columns need explicit identification. Our mapper auto-detects common names (lat/latitude/y, lng/longitude/x) but always confirm before converting.
- If latitude values look like hundreds of thousands (e.g. 488432), your CSV is in a projected CRS (often UTM or State Plane), not WGS 84. Select the correct source CRS in the mapper to reproject.
- Semicolon-delimited CSVs (common in European locales) are treated as a single column by most parsers. Convert to comma-delimited first, or use our parser's delimiter option.
- Numeric-looking strings are auto-converted to numbers. If you need values like ZIP codes or phone numbers preserved as strings, prefix with a single quote in Excel before export.
Frequently asked questions
What latitude/longitude column names are recognized?
Any of lat, latitude, y, northing for latitude, and lng, lon, long, longitude, x, easting for longitude. Matching is case-insensitive. You can always override the detection manually.
Can I convert a CSV of addresses without coordinates?
No — this is a pure converter, not a geocoder. Run your addresses through Google Geocoding, Mapbox, or Nominatim first, then add the resulting lat/lng columns and re-run.
What happens to columns that aren't coordinates?
They ride along as properties on each resulting Feature, preserving data types (numeric columns become numbers, everything else stays as strings).
Can my CSV use a projected coordinate system?
Yes, if the source CRS is one we can reproject client-side (WGS 84, Web Mercator, common UTM zones, RD New, British National Grid, a handful of State Plane). Select it in the mapper and the output will be reprojected to WGS 84.