Convert WKT (PostGIS, databases) to GeoJSON locally - for web maps and tools. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
WKT (Well-Known Text) often comes from a database query (PostGIS, SpatiaLite) or a GIS export - a geometry as plain text like POINT (13.4 52.5). Web maps (Leaflet, Mapbox, OpenLayers) and most developer tools, by contrast, expect GeoJSON. This tool reads your WKT geometries and writes a clean GeoJSON FeatureCollection.
All common types are recognised: POINT, LINESTRING, POLYGON (with holes), MULTIPOINT, MULTILINESTRING, MULTIPOLYGON and GEOMETRYCOLLECTION - in upper or lower case, with or without a space before the parenthesis. Several geometries (one per line) become several features; a geometry wrapped across multiple lines is read correctly too. The Z tag (elevation) is carried over; an M tag (measure) has no counterpart in GeoJSON and is dropped.
Everything runs entirely locally in the browser - your possibly sensitive location data never leaves your device. Honestly framed: WKT carries geometry only, so the generated features have empty properties. The coordinate order stays longitude then latitude. Invalid or empty WKT text is rejected with a clear message instead of faking an empty output.
| Input formats | WKT, TXT |
|---|---|
| Output format | GEOJSON |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Converts WKT into a GeoJSON FeatureCollection: POINT, LINESTRING, POLYGON with holes, multi variants and GEOMETRYCOLLECTION; several geometries (one per line) become several features. Z (elevation) is carried over, M (measure) dropped. Since WKT has no properties, the properties are empty. Coordinates WGS84 (longitude, latitude). Invalid WKT text is rejected with an error.
From spatial databases like PostGIS (function ST_AsText) or from GIS exports. As GeoJSON you then use these geometries in web maps and scripts.
Yes. Several WKT lines become several features; a geometry wrapped across several lines is read correctly too.
No, since WKT carries no attributes; the features have empty properties. For attributes KML, GPX or GeoJSON itself are suitable.
A measure (M) has no counterpart in GeoJSON and is dropped; the Z elevation is kept.
No, the conversion happens entirely locally in the browser; location data never leaves your device.