#coordinates

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

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

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

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