GeoJason

GeoJSON to Lat/Long Extractor

Extract latitude and longitude coordinates from GeoJSON features into a table or CSV.

Skip to the tool

Sometimes the analysis happens in a spreadsheet, a Jupyter notebook, or an old desktop GIS that doesn't speak GeoJSON. The fastest way out of GeoJSON into a tabular format is to flatten every geometry to its coordinate pairs alongside the feature's properties — a plain CSV that any tool will read.

Paste a Feature or FeatureCollection on the left. The extractor walks every geometry, emits one row per coordinate (with feature index and vertex index columns so you can reassemble), and joins the parent Feature's properties onto each row. The result is downloadable as CSV or TSV, with a configurable coordinate order.

Below the extractor: how Polygons, MultiPolygons, and LineStrings flatten differently (rings repeat the start coordinate, holes get a flag column), how to choose between per-vertex and per-feature output (centroid vs. all coordinates), and the jq /ogr2ogr equivalents for batch use. For the reverse, see the lat/long to GeoJSON converter.

Watch out for: the closing vertex on every Polygon ring. RFC 7946 §3.1.6 requires that the first and last positions in a linear ring be identical, which means per-vertex flattening produces a row that exactly duplicates the first row. If you're feeding the CSV into a tool that doesn't expect that — clustering algorithms, density plots, leaflet heatmaps — the duplicate biases results. The extractor flags ring-closing rows in a separate column so you can WHERE is_ring_close = 0 them out cleanly, and emits a part_index column so you can tell exterior rings from holes within the same Polygon.

How Coordinate Extraction Works

This tool reads all Point geometries from your GeoJSON and outputs their coordinates as a CSV table with latitude and longitude columns. For non-point geometries (LineStrings, Polygons), vertex coordinates are extracted individually.

The output uses latitude, longitude order (the conventional format for spreadsheets and most non-GIS applications), reversing the [longitude, latitude] order used internally by GeoJSON.

Output Format

The result is a CSV with a header row followed by one coordinate pair per line:

CSVlatitude,longitude
40.7484,-73.9857
34.0522,-118.2437

You can download this as a .csv file and open it directly in Excel, Google Sheets, or any data analysis tool.

Common Use Cases

  • Exporting GeoJSON point data to a spreadsheet for reporting
  • Creating address lists from geocoded GeoJSON features
  • Feeding coordinates into geocoding or reverse-geocoding APIs
  • Sharing coordinate data with team members who do not use GIS tools

To convert coordinates back to GeoJSON, use the lat/long to GeoJSON converter.

Try It

Paste this GeoJSON FeatureCollection containing two US landmarks. The tool extracts each Point coordinate and outputs a CSV:

GeoJSON{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": { "name": "Empire State Building" },
      "geometry": {
        "type": "Point",
        "coordinates": [-73.9857, 40.7484]
      }
    },
    {
      "type": "Feature",
      "properties": { "name": "Hollywood Sign" },
      "geometry": {
        "type": "Point",
        "coordinates": [-118.3217, 34.1341]
      }
    }
  ]
}

The resulting CSV output:

CSVlatitude,longitude
40.7484,-73.9857
34.1341,-118.3217

The GeoJSON [longitude, latitude] order is reversed to the more common latitude-first order that spreadsheets and non-GIS tools expect.

How the Extraction Works

The tool iterates over every Feature in the input GeoJSON. For Point geometries, it reads the coordinate array and swaps the values to latitude-first order. For LineString and Polygon geometries, each vertex coordinate is extracted as a separate row. The output includes a header row (latitude,longitude) followed by one row per coordinate pair.

This tool pairs well with the GeoJSON viewer for verifying point locations before export. For details on coordinate ordering conventions, see the GeoJSON Specification Guide.