#maps

UK postcode and geography lookup as an API, built on the open postcodes.io dataset. Resolve any UK postcode to its latitude/longitude and full administrative hierarchy — district, ward, county, parish, parliamentary constituency, region, NHS health authority and statistical areas (LSOA, MSOA). Validate a postcode, reverse-geocode coordinates to the nearest postcodes (with distance), find postcodes near a given one, autocomplete a partial postcode for address forms, look up an outcode (the first half, e.g. SW1A) and fetch a random postcode. Real data, no key needed upstream. Ideal for checkout and address forms, delivery and logistics, store locators, and UK geo-analytics.

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

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

Encode and decode Google/Mapbox encoded polylines — the compact ASCII string used by the Google Maps Directions API, Mapbox, Valhalla, OSRM and GPX-style route geometry to pack a list of coordinates into a few bytes. Decode an encoded string into an array of latitude/longitude points, encode a coordinate list back into a polyline (precision 5, the Google default, or 6 for OSRM/Valhalla overview), and measure a path — point count, total length by the haversine great-circle formula in km and miles, and the bounding box. Perfect for drawing routes on a map, storing tracks compactly, computing trip distance and fitting a map viewport. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from coordinate-format conversion (Plus Code/MGRS/UTM) and geohash.

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

Driving routes with distance, duration and geometry, distance/duration matrices for up to 25 points, and nearest-road snapping — on the global OpenStreetMap road network. Coordinates are simple lat,lon pairs.

api.oanor.com/routing-api

Forward & reverse geocoding and OSM object lookup powered by OpenStreetMap: turn addresses/places into coordinates, coordinates into addresses, and look up OSM objects by id.

api.oanor.com/geocoding-api