GeoJSON to CSV Converter
When you need geospatial data in a spreadsheet, BI tool, or SQL COPY statement — the fastest path off the GeoJSON island.
Common issues converting GeoJSON to CSV
- Polygon and line geometries don't have a single lat/lng — they're collapsed to a representative point (centroid for polygons, midpoint for lines). Use GeoJSON→WKT instead if you need full geometry preserved per row.
- Features with heterogeneous property sets produce a CSV header that's the union of all keys; missing cells are left blank. Re-check downstream tools that don't tolerate sparse columns.
- Nested JSON properties are serialized to a single JSON-string column so no data is lost, but you'll need to re-parse them downstream.
- Multi-geometry features (MultiPoint, MultiPolygon) collapse to one representative point. Explode them to one feature per sub-geometry before conversion if each should be a row.
Frequently asked questions
Will my CSV open cleanly in Excel?
Yes. The output uses UTF-8 with a BOM so Excel on Windows renders accented characters correctly on double-click.
How are coordinates represented in the output?
Two columns: 'latitude' and 'longitude'. For non-point features the values are the geometry's representative point (centroid for polygons, midpoint-on-line for lines).
Can I preserve the full polygon geometry per row?
Not in a clean CSV — a polygon's coordinates are a nested array. Convert to WKT format instead to get one text-representable geometry per row.
Are timestamps preserved?
Yes. ISO 8601 timestamp strings in properties pass through unchanged. Excel may reformat them on open — use a text-import flow if you need the original strings.