CSV to GeoJSON

Address lists, sensor logs and exports from spreadsheets often live in a CSV with coordinate columns. Web maps (Leaflet, Mapbox) and most geo tools, however, expect GeoJSON. This tool reads your CSV and writes a clean GeoJSON FeatureCollection you can drop straight onto a map.

The geometry is detected automatically: if the CSV has a geometry or wkt column, it is parsed as WKT (any geometry type); otherwise a latitude column (lat, latitude or y) and a longitude column (lon, lng, longitude or x) build Point features. All other columns are carried over as feature properties, with numbers parsed as numbers.

Everything runs entirely locally in the browser - your possibly sensitive location data never leaves your device. Honestly framed: a CSV without a usable geometry or coordinate columns is rejected with a clear message rather than producing an empty map. Column names are matched case-insensitively.

A common pitfall in the result: GeoJSON always writes coordinates in the order [longitude, latitude] - that is lon before lat, the reverse of the spoken 'lat/long' habit - and always in the WGS84 reference system (EPSG:4326). The tool follows that standard so your points land in the right place in Leaflet, Mapbox and QGIS.

Specifications

In 3 steps

1. Drop your CSV file.
2. The conversion runs automatically.
3. Download the GeoJSON (e.g. for Leaflet).

Limitations: Converts a CSV table to a GeoJSON FeatureCollection: a geometry/WKT column is parsed as WKT, otherwise latitude + longitude columns (lat/latitude/y, lon/lng/longitude/x) build Point features. Remaining columns become properties. Coordinates WGS84. An invalid or empty CSV, or one without geometry columns, is rejected with a clear error.

FAQ

Related tools

GeoJSON to CSV · WKT to GeoJSON · KML to GeoJSON · NDJSON to GeoJSON · KML to GPX · GPX to KML · CSV to ICS · CSV to SQL · CSV to VCF · CSV to XML