oanor
Sign up free
Marketplace Pricing Features Sign in

API · /wkt-api

WKT API

healthy 3,663 Subscribers

Convert geometry between WKT (Well-Known Text) and GeoJSON, in both directions. WKT is the textual geometry format used by PostGIS, Spatialite, GEOS, JTS, Shapely and the OGC Simple Features standard (POINT (30 10), LINESTRING (...), POLYGON ((...))); GeoJSON is what web maps and JavaScript expect. The to-geojson endpoint turns a WKT string into a GeoJSON geometry, and to-wkt does the reverse from a GeoJSON geometry or Feature. Supports Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Perfect for bridging a spatial database and a front-end map, importing and exporting geometry, and data-migration scripts. Pure local computation — no key, no third-party service, instant; send large geometries via POST. Live, nothing stored. 3 endpoints. Distinct from coordinate-format conversion, EPSG/CRS lookups, slippy map tiles and GeoJSON geospatial metrics.

#wkt #geojson #gis #postgis #geospatial #developer-tools
api.oanor.com/wkt-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/wkt-api/openapi.json
/api/wkt-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
97 ms
Server probes · 24h
Subscribers
3,663
active
Total calls
42
last 7 days
status Full status page → · 15 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 920 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 920 calls/month
  • 2 req/sec
  • WKT <-> GeoJSON both ways
  • No credit card
Sign in to subscribe

Starter

€1.90 /month

  • 7,700 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 7.7k calls/month
  • 8 req/sec
  • All geometry types
  • Email support
Sign in to subscribe

Pro

€20.60 /month

  • 133,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 133k calls/month
  • 20 req/sec
  • PostGIS / map bridge pipelines
  • Priority support
Sign in to subscribe

Mega

€56.60 /month

  • 685,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 685k calls/month
  • 50 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

GeoJSON API

Measure GeoJSON geometry on the surface of the earth. Compute the true area of a Polygon or MultiPolygon (in square metres, square kilometres, hectares, acres and square miles), find the centroid of any GeoJSON, get the bounding box (west/south/east/north) and its centre, measure the length of a LineString or MultiLineString (in kilometres, metres, miles and nautical miles), and test whether a latitude/longitude point falls inside a polygon. Accepts geometries, Features and FeatureCollections; coordinates follow the GeoJSON [longitude, latitude] order. Perfect for mapping apps, geofencing, territory and catchment analysis, route distances and spatial dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 6 endpoints. Distinct from abstract shape geometry, coordinate-format conversion, slippy map tiles and administrative-boundary data.

api.oanor.com/geojson-api

geoBoundaries API

Open administrative boundaries as an API, powered by geoBoundaries — the open database of political administrative boundaries built by the William & Mary geoLab. For more than 200 countries and every administrative level — ADM0 (national), ADM1 (states, provinces or regions), ADM2 (counties or districts) and on down to ADM4/ADM5 local units — get the boundary's metadata (official name, the source agency that produced it, the data licence, the year represented, the number of administrative units and the mean vertex count) together with direct download links to the geometry in full-resolution GeoJSON, a simplified GeoJSON, TopoJSON and a ZIP bundle; list every administrative level available for a country with its unit count and download link; and browse the full catalogue of countries that have boundaries. The geometry itself is delivered as standard GeoJSON/TopoJSON files at the returned URLs, ready to drop into Leaflet, Mapbox, QGIS, deck.gl or any GIS pipeline. Ideal for mapping and visualisation, choropleths, spatial joins, geofencing, election and census cartography and location analytics. ISO codes are 3-letter (DEU, USA, BRA); administrative levels are ADM0 to ADM5. Data from the geoBoundaries project (CC-BY 4.0).

api.oanor.com/geoboundaries-api

UTM Coordinate API

UTM ↔ geographic coordinate conversion as an API, computed locally and deterministically on the WGS84 ellipsoid. The from-latlon endpoint projects a latitude and longitude into the Universal Transverse Mercator grid — returning the zone (1–60), the hemisphere, the latitude band letter, and the easting and northing in metres — using the Snyder/USGS Transverse Mercator series, which is accurate to a few millimetres within a zone; New York (40.7128, −74.0060) maps to zone 18N at about 583960 E, 4507351 N, and the canonical 45°N on a central meridian gives a northing of exactly 4982950.40 m. The to-latlon endpoint inverts it, recovering the latitude and longitude from a zone, hemisphere, easting and northing. Each zone is 6° of longitude wide with a 500000 m false easting on its central meridian and a 10000000 m false northing in the southern hemisphere. Latitude is valid from −80° to 84°. Everything is computed locally and deterministically, so it is instant and private. Ideal for GIS, surveying, mapping, geospatial, drone-mapping and location app developers, coordinate-conversion and grid-reference tools, and spatial software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. This is UTM on WGS84; for the polar regions use UPS and for an EPSG-code lookup use an EPSG API.

api.oanor.com/utm-api

Geodesy API

Advanced geodesy beyond the simple great circle. The vincenty endpoint computes the distance between two latitude/longitude points on the WGS84 ellipsoid using Vincenty's inverse formula — accurate to within a millimetre, far better than the spherical approximation — plus the initial and final bearings, in metres, kilometres, miles and nautical miles. The rhumb endpoint computes the rhumb-line (loxodrome) distance and the single constant compass bearing that follows it — the path you steer by holding a heading, as used in marine and air navigation. The cross-track endpoint finds how far a point lies to the left or right of a great-circle path between two points (the cross-track distance) and how far along that path it is (the along-track distance). Everything is computed locally and deterministically, so it is instant and private. Ideal for marine and aviation navigation, surveying and GIS, route analysis, and precise mapping. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is advanced geodesy; for simple great-circle distance, bearing, midpoint and destination use a geo-distance API and for coordinate-format conversion use a geo-convert API.

api.oanor.com/geodesy-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for WKT API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call WKT API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for WKT API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does WKT API cost?
WKT API has a free tier with 100 calls / month. Paid plans start at €1.90 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is WKT API GDPR-compliant?
All requests to WKT API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/wkt-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/wkt-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/wkt-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/wkt-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.