Bounding box of a cell
API · /geohash-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 health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 75 ms
- Server probes · 24h
- Subscribers
- 3,542
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 8,000 calls / month
- 3 requests / second
- Hard cap (429 above quota, no overage)
- 8,000 requests/month, 3 req/s
- Encode, decode, neighbors & bbox
- Precision 1-12
- No credit card
Basic
€2.00 /month
- 150,000 calls / month
- 12 requests / second
- Hard cap (429 above quota, no overage)
- 150,000 requests/month, 12 req/s
- Bounding box & error margins
- 8-cell neighbour lookup
- Commercial use, email support
Pro
€6.00 /month
- 1,200,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,200,000 requests/month, 40 req/s
- High-volume spatial indexing
- Proximity & clustering at scale
- Priority email support
Mega
€16.00 /month
- 9,000,000 calls / month
- 120 requests / second
- Hard cap (429 above quota, no overage)
- 9,000,000 requests/month, 120 req/s
- IoT, fleet & map-tile scale
- Maximum concurrency
- Priority support
Built by
Related APIs
Other APIs with overlapping tags.
Observatory Codes API
The IAU Minor Planet Center list of observatory codes as an API — every site the MPC uses to identify a telescope when it publishes astrometric observations of asteroids and comets. For each of 2,700+ codes: the 3-character code, the observatory name, its east longitude and the parallax constants (rho·cos φ', rho·sin φ'). From those constants the API derives each site's geocentric latitude and a -180..180 longitude, so you can find the observatories nearest any point on Earth with a great-circle (haversine) search. Look one up by code, search by name, list them all, or find the closest sites to a latitude/longitude. Distinct from telescope-api (optics maths) — this is the registry of real observing sites and where they are. Served from memory — always fast.
api.oanor.com/observatories-api
WKT API
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.
api.oanor.com/wkt-api
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
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.oanor.com/geoconvert-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Geohash API?
What's the rate limit for Geohash API?
How much does Geohash API cost?
Can I cancel my subscription anytime?
Is Geohash 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/geohash-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/geohash-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/geohash-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/geohash-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.