#gis

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

Geodesia avanzada más allá del círculo máximo simple. El endpoint vincenty calcula la distancia entre dos puntos de latitud/longitud en el elipsoide WGS84 utilizando la fórmula inversa de Vincenty — precisa hasta un milímetro, mucho mejor que la aproximación esférica — además de los rumbos inicial y final, en metros, kilómetros, millas y millas náuticas. El endpoint rhumb calcula la distancia de la línea loxodrómica y el rumbo constante de la brújula que la sigue — la ruta que se sigue manteniendo un rumbo, como se usa en navegación marítima y aérea. El endpoint cross-track encuentra a qué distancia se encuentra un punto a la izquierda o derecha de una trayectoria de círculo máximo entre dos puntos (distancia transversal) y a qué distancia a lo largo de esa trayectoria se encuentra (distancia a lo largo de la trayectoria). Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para navegación marítima y aérea, topografía y SIG, análisis de rutas y cartografía precisa. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada se almacena. 4 endpoints. Esta es geodesia avanzada; para distancia de círculo máximo simple, rumbo, punto medio y destino, use una API de geo-distancia y para conversión de formato de coordenadas, use una API de geo-conversión.

api.oanor.com/geodesy-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

Mida la geometría GeoJSON en la superficie de la tierra. Calcule el área real de un polígono o multipolígono (en metros cuadrados, kilómetros cuadrados, hectáreas, acres y millas cuadradas), encuentre el centroide de cualquier GeoJSON, obtenga el cuadro delimitador (oeste/sur/este/norte) y su centro, mida la longitud de una LineString o MultiLineString (en kilómetros, metros, millas y millas náuticas), y pruebe si un punto de latitud/longitud cae dentro de un polígono. Acepta geometrías, Features y FeatureCollections; las coordenadas siguen el orden [longitud, latitud] de GeoJSON. Perfecto para aplicaciones de mapas, geocercas, análisis de territorio y cuencas, distancias de rutas y paneles espaciales. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 6 endpoints. Distinto de la geometría de forma abstracta, conversión de formato de coordenadas, mosaicos de mapas móviles y datos de límites administrativos.

api.oanor.com/geojson-api

The maths behind every web map. Convert between latitude/longitude, slippy-map XYZ tile coordinates (the z/x/y scheme used by OpenStreetMap, Google Maps, Mapbox and Leaflet) and Bing/Azure quadkeys, and get the exact Web Mercator (EPSG:3857) bounding box and centre of any tile. Find which tile contains a point at a given zoom, expand a tile to its geographic bounds, translate a quadkey to z/x/y and back, and list a tile's eight neighbours (with correct antimeridian wrap-around and pole clamping). Perfect for tile servers and caches, pre-fetching map tiles, drawing tile grids and debugging map layers. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 5 endpoints. Distinct from coordinate-format conversion (Plus Code/MGRS/UTM), geohash and the encoded-polyline codec.

api.oanor.com/maptile-api

Convierte coordenadas geográficas entre todos los formatos comunes. Convierte un par de latitud/longitud en un Plus Code (Open Location Code, como el usado por Google Maps), una referencia MGRS (Sistema de Referencia de Cuadrícula Militar), una coordenada UTM (zona, hemisferio, este, norte) o una cadena DMS (grados-minutos-segundos) — y convierte cualquiera de esos de vuelta a latitud/longitud. El endpoint /v1/all devuelve todos los formatos a la vez. Cada conversión se ejecuta completamente local (sin servicio de terceros), por lo que las respuestas son instantáneas y siempre están disponibles. En vivo, sin caché. 6 endpoints. Diseñado para SIG, cartografía, topografía, logística, aviación, servicios de emergencia y cualquier aplicación que intercambie coordenadas entre sistemas. Complementa las búsquedas de geohash y CRS sin superposición. Sin clave upstream.

api.oanor.com/geoconvert-api

Map projections and coordinate reference systems as an API — the EPSG dataset made queryable. Every CRS, from geographic systems like WGS 84 (the GPS standard, EPSG 4326) to projected ones like Web Mercator (3857), the UTM zones and national grids, has an EPSG code. Search the dataset by name to find the code you need, then resolve any code to its full definition: name, kind (geographic, projected, …), area of use, scope, and — most usefully — the ready-to-paste PROJ.4 string and WKT definition that GIS libraries (GDAL, PROJ, PostGIS, Leaflet, OpenLayers, QGIS, GeoPandas) consume directly. Search comes from the official EPSG Registry maintained by IOGP; the PROJ.4/WKT exports come from epsg.io. A geodesy / coordinate-reference-system resource — distinct from geocoding (addresses to coordinates), geohashing and administrative-boundary APIs. Ideal for GIS, mapping, surveying, remote-sensing and spatial-data applications.

api.oanor.com/epsg-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

Classify any location's climate with the Köppen-Geiger system — the standard used across geography, ecology, agriculture and architecture. Provide a location's twelve monthly mean temperatures and precipitation totals and get back its climate code (for example Cfb or BWh), the climate group and full name, a description, and a block of derived statistics (annual mean temperature, annual precipitation, warmest and coldest month, driest month, months above 10 °C, summer-precipitation share and the aridity threshold). The hemisphere is auto-detected from the temperature curve, or you can set it explicitly. A reference endpoint returns all thirty Köppen-Geiger codes with names, groups, descriptions and example cities. Every endpoint accepts input via the query string or the request body and returns lean JSON. Pure server-side computation (no third-party upstream), so responses are instant and always available. Ideal for EdTech and geography tools, AgTech and crop-suitability apps, architecture and GIS pipelines.

api.oanor.com/climate-api