WKT Viewer & Converter

Field guide: WKT Viewer & Converter

WKT is what geometry looks like when a database talks: SELECT ST_AsText(geom) and out comes POLYGON((...)) — precise, portable, and completely unvisualizable in your SQL client. This viewer is the missing st_preview(): paste one geometry or a whole column's worth (one per line), and points, linestrings and polygons render instantly with vertex counts. The reverse direction works too — paste GeoJSON, export WKT for an INSERT statement.

It's the debugging tool for the classic spatial-SQL failure modes: the polygon that's invalid because the ring doesn't close, the geometry in the wrong hemisphere because axis order got swapped, the 'why is ST_Contains false' that becomes obvious the moment both shapes are visible. Everything parses locally — production data stays exactly as private as your psql session.

Field tips

• Paste straight from query output — one geometry per line; SRID= prefixes and trailing commas/quotes from result sets are tolerated poorly, so strip them.
• WKT axis order here is X Y (longitude latitude) matching PostGIS defaults — if your data lands in Antarctica, your columns are swapped.
• Round-trip trick: GeoJSON in → WKT out gives you copy-paste geometry literals for ST_GeomFromText() seeds and tests.

Records are stored only in this browser (localStorage) — export regularly. This tool aids field documentation; it does not replace your agency's official inspection procedures or engineering judgment.