# Convert GeoJSON, WKT, and WKB Geometries

Convert geometries between GeoJSON, WKT/EWKT, and WKB/EWKB with SRID, precision, endian, and multi-feature controls.

## Run it

- **CLI:** `gizza tool geojson-wkt '{"type":"Point","coordinates":[30,10]}'`
- **Web:** https://gizza.ai/tools/geojson-wkt/
- **Agents:** machine-readable descriptor (parameters JSON Schema) at https://gizza.ai/tools/geojson-wkt/tool.json

## Inputs

- `input` — Input geometry _(field)_
- `from` — Input format _(field)_
- `to` — Output format _(field)_
- `multi` — Multiple geometries _(field)_
- `srid` — SRID to write _(field)_
- `precision` — Coordinate precision _(field)_
- `wkb_encoding` — WKB text encoding _(field)_
- `wkb_endian` — WKB byte order _(field)_
- `pretty` — Pretty-print GeoJSON _(field)_

## Output

- Converted geometry (text)

## Query parameters

Open the tool pre-filled and auto-run via URL:

- `input` — Input geometry
- `from` — Input format
- `to` — Output format
- `multi` — Multiple geometries
- `srid` — SRID to write
- `precision` — Coordinate precision
- `wkb_encoding` — WKB text encoding
- `wkb_endian` — WKB byte order
- `pretty` — Pretty-print GeoJSON

Example: `https://gizza.ai/tools/geojson-wkt/?input=%7B%22type%22%3A%22Point%22%2C%22coordinates%22%3A%5B30%2C10%5D%7D&from=auto&to=wkt&multi=collection&srid=0&precision=-1&wkb_encoding=hex&wkb_endian=little&pretty=true`

---

## About this tool

`geojson-wkt` converts simple-feature geometries between GeoJSON, WKT/EWKT, and WKB/EWKB. It is meant for GIS debugging, PostGIS copy/paste workflows, API payload cleanup, and format handoffs where you need the geometry itself rather than a full map or database.

The converter accepts GeoJSON `Geometry`, `Feature`, `FeatureCollection`, `GeometryCollection`, or arrays of those. WKT input may include an `SRID=4326;` EWKT prefix. WKB input may be hex or base64 text, one geometry per line. Output can be a single geometry or one geometry per line when a FeatureCollection contains several features.

### Worked example

Input GeoJSON:

```json
{"type":"Point","coordinates":[30,10]}
```

Default output:

```text
POINT(30 10)
```

With `to=geojson`, `input=SRID=4326;POINT Z (30 10 5)`, and pretty output enabled, the result is:

```json
{
  "type": "Point",
  "coordinates": [
    30,
    10,
    5
  ]
}
```

### Options and limits

- **Input format** can be auto-detected or forced to GeoJSON, WKT/EWKT, or WKB/EWKB.
- **Output format** can be WKT/EWKT, GeoJSON, or WKB/EWKB.
- **Multiple geometries** either wrap into a `GEOMETRYCOLLECTION` or emit one converted geometry per line.
- **SRID to write** adds EWKT/EWKB metadata. Coordinates are not reprojected.
- **Coordinate precision** rounds coordinates from 0 to 15 decimals; `-1` keeps full shortest-round-trip formatting.
- **WKB text encoding** chooses hex or base64; **WKB byte order** chooses little-endian/NDR or big-endian/XDR.
- The input limit is 2 MB, and nested GeometryCollections are limited to 32 levels.
- Supported geometry types are Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection, including `EMPTY`, 2D, Z, M, and ZM forms.
- Curved or surface extensions such as `CIRCULARSTRING`, `TIN`, and `TRIANGLE` are rejected with a clear error instead of being approximated.

## FAQ

<details>
<summary>Does this reproject coordinates between coordinate systems?</summary>

No. An SRID is metadata only here. `SRID=4326;POINT(30 10)` stays at the same numeric coordinates; the tool does not apply EPSG transformations or use a projection database.

</details>

<details>
<summary>What happens to GeoJSON feature properties?</summary>

WKT and WKB are geometry-only formats, so feature properties are not represented in those outputs. A GeoJSON FeatureCollection is converted from its `geometry` members, and features with `geometry: null` are skipped.

</details>

<details>
<summary>Can it read and write WKB?</summary>

Yes. Paste hex WKB/EWKB or base64 WKB/EWKB as text. For output, choose `to=wkb`, then choose hex or base64 and little-endian or big-endian byte order.

</details>

<details>
<summary>Why do M values disappear in GeoJSON output?</summary>

GeoJSON positions are longitude/latitude plus optional elevation. There is no standard M ordinate, so WKT/WKB `M` values are dropped when producing GeoJSON. Z values are kept as the third coordinate.

</details>

<details>
<summary>Is the input uploaded?</summary>

No. The Rust converter runs locally in WebAssembly on the page and locally in the CLI. It does not fetch map tiles, call a geocoder, or send your geometry anywhere.

</details>

## Related tools

- [Point in Polygon Checker](https://gizza.ai/tools/geofence-check/): Test latitude/longitude points against a polygon geofence. Paste GeoJSON or lat,lon lines, choose boundary handling, and export text, CSV, or JSON.
- [Query GeoJSON Features](https://gizza.ai/tools/geojson-query/): Filter, project, sort, page, and aggregate GeoJSON features with property predicates, bbox filters, and simple spatial functions.
- [Beancount to CSV Converter](https://gizza.ai/tools/beancount-to-csv/): Flatten Beancount or Ledger journal postings into spreadsheet-ready CSV, then rebuild a simple journal from that flat CSV schema.
- [Convert BibTeX to CSV](https://gizza.ai/tools/bibtex-to-csv/): Paste BibTeX and get CSV, one row per entry. Choose columns, delimiter and header, decode LaTeX accents, reformat author names, sort rows and add an Excel BOM.
- [MongoDB Extended JSON Converter](https://gizza.ai/tools/bson-extended-json-converter/): Convert MongoDB Extended JSON ($oid, $date, $numberLong) to and from plain JSON, with canonical or relaxed output, in your browser.