PostGIS-ready · SRID 4326 · no sign-up

Address in.
Postgres geometry out.

pointkit geocodes a plain address and hands back a ready-to-run ST_GeomFromText literal — correct longitude/latitude axis order, SRID 4326, no PostGIS extension required. Works with any Postgres geometry or geography column.

Also available: MySQL POINT · WKT · GeoJSON
Postgres · ST_GeomFromText
{{ heroResultText }}
INSERT INTO places (name, geom) VALUES ('example', {{ heroResultText }});
{{ heroErrorText }} Buy more credits →

Why axis order breaks silently

WKT, and therefore ST_GeomFromText, expects coordinates as (longitude, latitude). Most geocoders and mapping APIs return (latitude, longitude). Swap them by mistake and Postgres accepts the geometry without complaint — the row just lands somewhere on the other side of the equator from where it should. There's no error to catch it, only a support ticket weeks later when someone notices a customer's pin is in the ocean.

pointkit geocodes the address and outputs the literal in the order Postgres expects, every time, so this class of bug never ships.

Postgres & PostGIS FAQ

Does this require the PostGIS extension?
No. pointkit hands you a plain ST_GeomFromText(...) literal with SRID 4326, which works against any Postgres geometry or geography column whether or not PostGIS is installed. If you do have PostGIS, the same literal works unchanged with its fuller spatial function set.
geometry or geography column — does it matter?
The literal is the same either way. Cast it as needed: ST_GeomFromText(...)::geography if the column is geography, or leave it as-is for a geometry column. geography is usually the better default for real-world addresses since it accounts for the Earth's curvature in distance calculations.
What SRID does pointkit use?
4326 (WGS 84), the standard reference system for GPS and web-mapping coordinates, and PostGIS's default. Axis order is longitude, then latitude, matching what ST_GeomFromText and WKT expect.
Can I convert a whole table of addresses at once?
Yes — export the addresses as a CSV and use pointkit's batch converter, which appends a geometry column to the file so you can load it back in with COPY or an ORM import.