All formats at once
API · /geoconvert-api
Coordinate Conversion API
Convert geographic coordinates between every common format. Turn a latitude/longitude pair into a Plus Code (Open Location Code, as used by Google Maps), an MGRS reference (Military Grid Reference System), a UTM coordinate (zone, hemisphere, easting, northing) or a DMS string (degrees-minutes-seconds) — and convert any of those back to latitude/longitude. The /v1/all endpoint returns every format at once. Each conversion runs fully locally (no third-party service) so responses are instant and always available. Live, no cache. 6 endpoints. Built for GIS, mapping, surveying, logistics, aviation, emergency services and any app that exchanges coordinates between systems. Complements geohash and CRS lookups without overlap. No upstream key.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 84 ms
- Server probes · 24h
- Subscribers
- 4,692
- active
- Total calls
- 84
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 1,700 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 1,700 calls/month
- 2 req/sec
- Plus Code, MGRS, UTM, DMS
- No credit card
Starter
€8.50 /month
- 37,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 37k calls/month
- 8 req/sec
- Bidirectional + /all
- Email support
Pro
€27.50 /month
- 205,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 205k calls/month
- 20 req/sec
- GIS / mapping pipelines
- Priority support
Mega
€63.50 /month
- 1,020,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 1.02M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
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
Geohash API
Work with geohashes through a fast, fully-local API. Encode a latitude/longitude pair into a geohash at any precision (1–12), decode a geohash back to its centre coordinates with the exact bounding box and error margins, list the eight neighbouring geohash cells (north, north-east, east and so on), or get the bounding box, centre and dimensions of a cell. Geohashes turn coordinates into short sortable strings that are perfect for spatial indexing, proximity grouping and map tiling. Pure server-side computation with no third-party upstream, so responses are instant and the service is always available. Ideal for geospatial indexing and search, proximity and nearby queries, map tiles and clustering, IoT and fleet tracking, and location bucketing in databases.
api.oanor.com/geohash-api
Geo Distance API
A fast, fully-local great-circle geospatial toolkit: compute the haversine distance between two coordinates (in km, m, miles or nautical miles), the initial and final compass bearing, the geographic midpoint, the destination point reached from an origin on a bearing at a given distance, and a bounding box around a center for a radius. Pure server-side compute, no third-party upstream, so responses are instant and always available. Ideal for logistics, delivery and fleet apps, store locators, real-estate search, travel and mapping tools.
api.oanor.com/geo-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 Coordinate Conversion API?
What's the rate limit for Coordinate Conversion API?
How much does Coordinate Conversion API cost?
Can I cancel my subscription anytime?
Is Coordinate Conversion API GDPR-compliant?
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/geoconvert-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/geoconvert-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/geoconvert-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/geoconvert-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 inNew thread
·
-
Provider answer
🔒 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 inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.