RFC 7946 · map-ready · no sign-up

Address in.
GeoJSON point out.

pointkit geocodes a plain address and hands back a GeoJSON Point object with correct [longitude, latitude] order per RFC 7946 — ready for Mapbox GL, Leaflet, Turf.js, or any API that speaks GeoJSON.

GeoJSON
{{ heroResultText }}
A bare Point geometry. Wrap it in { "type": "Feature", "geometry": ..., "properties": {} } if your library expects a Feature.
{{ heroErrorText }} Buy more credits →

What your map actually wants

GeoJSON is the format the frontend mapping world standardized on — Mapbox GL, Leaflet, Turf.js, and most geospatial APIs read and write it natively. A point is {"type":"Point","coordinates":[longitude,latitude]}: longitude first, per RFC 7946.

That order is the opposite of how people say coordinates out loud, and the opposite of MySQL's default SRID 4326 — two easy ways to end up with a pin on the wrong continent and no error to explain why. pointkit geocodes the address directly into the correct order, so there's no manual reordering step to get wrong.

GeoJSON FAQ

Does this output a Point geometry or a full Feature?
A bare Point geometry: {"type":"Point","coordinates":[longitude,latitude]}. If your map library or API expects a full Feature or FeatureCollection, wrap it yourself — { "type": "Feature", "geometry": <this>, "properties": {} } is a one-line wrap once you have the coordinates.
Is GeoJSON longitude-first or latitude-first?
Longitude first: [longitude, latitude], per RFC 7946. This is the reverse of how coordinates are usually spoken out loud, and the reverse of MySQL/MariaDB's default SRID 4326 order.
Will this work directly with Mapbox GL, Leaflet, or Turf.js?
Yes — all three consume standard GeoJSON coordinate order, so the Point object drops straight in wherever a geometry or coordinates array is expected.
Can I convert a whole file of addresses to GeoJSON at once?
Yes — export the addresses as a CSV and use pointkit's batch converter, which appends a GeoJSON column to the file.