1. Related Geospatial & JSON Tools
Work with spatial and structured files using our GPX / KML to GeoJSON Converter, JSON Formatter, JSONPath Evaluator, and JSON to TypeScript.
THE TOOLBOX / GIS & GEOSPATIAL DATA
Convert OGC WKT, PostGIS EWKT (SRID=4326), and TopoJSON to clean GeoJSON (and back) with an instant 2D SVG preview, vertex count, and bounding box—100% client-side.
{
"type": "Polygon",
"coordinates": [
[
[
-122.42,
37.78
],
[
-122.4,
37.78
],
[
-122.39,
37.76
],
[
-122.415,
37.755
],
[
-122.43,
37.77
],
[
-122.42,
37.78
]
]
]
}OGC WKT EXAMPLES
| Geometry Type | WKT Syntax | Notes |
|---|---|---|
| Point | POINT (-122.42 37.78) | Longitude first, then latitude (X Y) |
| LineString | LINESTRING (0 0, 10 10, 20 5) | Open polyline for roads, trails & rivers |
| Polygon | POLYGON ((0 0, 4 0, 4 4, 0 4, 0 0)) | First and last coordinates must close the ring |
Work with spatial and structured files using our GPX / KML to GeoJSON Converter, JSON Formatter, JSONPath Evaluator, and JSON to TypeScript.
Survey parcels, PostGIS query results, and private delivery zones stay strictly inside your browser memory.
Paste any WKT geometry (POINT, LINESTRING, POLYGON, MULTIPOLYGON) or PostGIS EWKT string with an SRID prefix (like SRID=4326;POLYGON(...)) into the input box. The tool strips and preserves the SRID badge, renders a 2D vector preview with bounding box, and outputs clean GeoJSON instantly.
Yes. Paste any GeoJSON Geometry, Feature, or FeatureCollection on the left and switch the output tab to WKT to get standard OGC Well-Known Text.
Yes. Paste a TopoJSON Topology object and it automatically extracts the primary object layer into standard GeoJSON using topojson-client locally in your browser.
OGC WKT stores pure geometry coordinates without coordinate-reference metadata. PostGIS EWKT (Extended Well-Known Text) prepends SRID=4326; (or another EPSG code) so spatial databases know which projection the coordinates belong to.
Both GeoJSON (RFC 7946) and standard PostGIS WKT use [longitude, latitude] (X, Y) order—unlike Google Maps URLs which typically display latitude first.
No. All WKT, TopoJSON, and GeoJSON parsing and SVG preview rendering execute 100% locally in your browser.