WKT to KML Converter
The fastest way to visualise spatial database output for a stakeholder who lives in Google Earth.
Common issues converting WKT to KML
- One WKT statement per line, please. Multi-statement WKT files (one geometry per line) parse cleanly; SRID-prefixed WKT (`SRID=4326;POINT(...)`) is also accepted and the SRID is stripped.
- WKT carries no attributes, so the output Placemarks have no <ExtendedData>. If you have parallel attribute data, join after conversion in Google My Maps.
- EWKT extensions beyond Z (M, ZM) are accepted on parse but M values are dropped — KML has no equivalent measure-coordinate concept.
- Polygon rings in WKT must be closed (first point = last point). Open rings are auto-closed before emission; check the source if that surprises you.
Frequently asked questions
Does the output open in Google My Maps?
Yes — up to the My Maps free-tier 5 MB limit. For larger conversions, split into multiple files.
Can I include POINT Z elevations?
Yes — the output KML preserves altitude as the third coordinate value. Google Earth renders 3D points at the specified altitude when the layer is set to 'absolute' mode.
What about GEOMETRYCOLLECTION?
Emitted as a <MultiGeometry> container per OGC convention. Google Earth renders mixed geometry types but doesn't allow editing the collection as a unit.
Is SRID preserved?
No — KML is always WGS 84. If your WKT is in a projected CRS, reproject to EPSG:4326 first or the placemarks will land in the ocean off Africa.