CSV to WKT Converter
Bulk-load a point inventory into a spatial database without writing an ETL pipeline.
Common issues converting CSV to WKT
- Output is one POINT(x y) per source row, one per line. Attribute columns are dropped — WKT carries geometry only.
- Lat/lng column detection is case-insensitive (lat/latitude/y for latitude; lng/lon/longitude/x for longitude). Override the detection if your CSV uses unusual names.
- If lat values look like hundreds of thousands (488432), your source is in UTM or State Plane, not WGS 84. Reproject before conversion — or accept that ST_GeomFromText will treat the values as raw coordinates.
- Empty / null coordinates produce an empty line. Filter out rows without coordinates in the source spreadsheet to avoid downstream parse errors.
Frequently asked questions
How do I bulk-load to PostGIS?
`COPY points (geom) FROM stdin;` with the WKT-per-line format works directly. Wrap each line in `ST_GeomFromText(...)` if your destination is a typed geometry column.
Can I preserve CSV columns alongside geometry?
Not in WKT — it's geometry-only. Use the Shapefile, GeoParquet, or FlatGeobuf target instead, which carry both.
Does the output include an SRID?
Plain OGC WKT, no SRID. Set SRID at INSERT time: `ST_SetSRID(ST_GeomFromText('POINT(...)'), 4326)`.
What if my coordinates have more than 2 dimensions?
If a Z column is present (alt/elevation/z), output uses POINT Z(x y z). Specify the Z column name in the converter UI.