WKT to CSV Converter
Getting geometries out of a WKT list and into a tabular form for spreadsheets, BI tools, or a COPY into a database.
Common issues converting WKT to CSV
- The geometry lands in a single WKT column; spreadsheet apps won't render it as a map, but databases re-parse it with ST_GeomFromText.
- WKT strings contain commas — the column is quoted so the CSV stays valid; keep quoting on when you re-import.
- Pure WKT has no attributes, so the CSV is essentially a one-column geometry table unless your input paired attributes you supply separately.
- For point data you may prefer split lat/lng columns instead of a WKT column — convert via GeoJSON if you need that layout.
Frequently asked questions
Will Excel show the geometry on a map?
No — Excel treats it as text. Use the CSV for data pipelines, or convert to KML/GeoJSON for a visual.
Which column holds the geometry?
A column named wkt (or geometry) containing the original WKT string, quoted.
Can I bulk-load this into PostGIS?
Yes: COPY the CSV into a staging table, then UPDATE … SET geom = ST_GeomFromText(wkt, 4326).
Is the CRS recorded?
WKT and CSV don't embed CRS; document it alongside (WGS 84 unless you reprojected).