#geojson

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

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

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