GeoJSON to CSV Converter

Extract features and properties from GeoJSON into a flat CSV table with coordinate columns.

Tested tool guide Tested browser tools Checked August 16, 2026

What GeoJSON to CSV Converter does and how it behaves

Turn a GeoJSON feature collection into a table in which each feature is represented by a CSV row. Feature properties supply the descriptive fields, while values taken from the geometry appear in coordinate columns. This is useful when a spreadsheet, database import, or statistical program needs tabular records instead of GeoJSON objects. The main surprise is that GeoJSON can contain nested properties and multi-position geometries, but CSV is flat. Converting a file therefore does not guarantee that every part of a complex geometry can be represented as ordinary scalar cells.

How the result is produced

Feature-to-row mapping

The converter reads the features in the GeoJSON input and projects each feature into one flat record. Property names provide tabular fields, and geometry coordinates are exposed in coordinate columns rather than remaining only inside a geometry object. The resulting header identifies the available fields, followed by one comma-separated record for each converted feature.

Flattening boundaries

Scalar properties and Point coordinates fit naturally into CSV cells. Nested objects, property arrays, null values, and geometries containing several positions do not have one universal flat representation. Treat the CSV as a tabular export for inspection or downstream processing, not as a lossless replacement from which every original GeoJSON structure can necessarily be reconstructed.

Good uses

Export a collection of geocoded customers, facilities, or survey observations so their properties and point coordinates can be reviewed in a spreadsheet.
Prepare GeoJSON point features for a database import process that expects one CSV record per location rather than a FeatureCollection document.
Extract an attribute table from mapped observations before performing sorting, filtering, summary calculations, or joins in software that does not accept GeoJSON.

Limits and checks

GeoJSON geographic positions use longitude first and latitude second. Check the coordinate headers before importing the CSV into software whose forms or functions request latitude before longitude.
A LineString, Polygon, or multi-part geometry contains multiple coordinate positions. Simple coordinate columns cannot by themselves describe all vertices, rings, parts, or their nesting.
Features are allowed to have different property keys, and property values may be missing, null, nested, or arrays. Inspect the header and representative rows before assuming every CSV cell has the same meaning or data type.

Common questions

Does the CSV preserve enough information to recreate the original GeoJSON?

Not necessarily. CSV has no native equivalent for GeoJSON geometry objects, nested properties, or arrays. Point coordinates and scalar properties can be represented directly, but complex geometry structure may not survive as ordinary columns. Keep the source GeoJSON when exact geometry, feature structure, or later round-trip conversion matters.

Why does the first coordinate look like longitude rather than latitude?

GeoJSON geographic positions are ordered longitude, latitude, with an optional altitude after those values. That differs from interfaces that display or request latitude first. Compare the CSV coordinate headers with the source positions before plotting or importing them, and do not swap the values solely because another application presents latitude before longitude.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.