Skip to content
GET /v1/meta

Spec

Try it live

10 free calls per day — no sign-up, no API key. Goes through the oanor gateway.

Custom headers (optional)
api.oanor.com/geodesy-api

It works. Grab an API key and use it in your project.

Get an API key

Code snippets

curl "https://api.oanor.com/geodesy-api/v1/meta" \
  -H "x-oanor-key: oanor_test_..."
await fetch("https://api.oanor.com/geodesy-api/v1/meta", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
$ch = curl_init("https://api.oanor.com/geodesy-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);
import requests
requests.get(
    "https://api.oanor.com/geodesy-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Example response

A real response from this endpoint, captured by the latest health check.

{
    "data": {
        "name": "Geodesy API",
        "notes": "Vincenty uses the WGS84 ellipsoid; rhumb and cross-track use a spherical earth (R = 6371008.8 m). Bearings are degrees clockwise from north. Nothing is stored.",
        "version": "v1",
        "endpoints": [
            {
                "path": "/v1/vincenty",
                "params": {
                    "lat1": "",
                    "lat2": "",
                    "lon1": "",
                    "lon2": ""
                },
                "returns": "the precise ellipsoidal distance and bearings"
            },
            {
                "path": "/v1/rhumb",
                "params": {
                    "lat1": "",
                    "lat2": "",
                    "lon1": "",
                    "lon2": ""
                },
                "returns": "the rhumb-line distance and constant bearing"
            },
            {
                "path": "/v1/cross-track",
                "params": {
                    "lat1": "path start",
                    "lat2": "path end",
                    "lat3": "the point",
                    "lon1": "",
                    "lon2": "",
                    "lon3": ""
                },
                "returns": "cross-track and along-track distance"
            },
            {
                "path": "/v1/meta",
                "params": [],
                "returns": "this document"
            }
        ],
        "description": "Advanced geodesy beyond the simple great circle. The vincenty endpoint computes the distance between two latitude/longitude points on the WGS84 ellipsoid using Vincenty's inverse formula — accurate to within a millimetre, far better than the spherical approximation — plus the initial and final bearings, in metres, kilometres, miles and nautical miles. The rhumb endpoint computes the rhumb-line (loxodrome) distance and the single constant compass bearing that follows it — the path you steer by holding a heading, as used in marine and air navigation. The cross-track endpoint finds how far a point lies to the left or right of a great-circle path between two points (the cross-track distance), and how far along that path it is (the along-track distance). Everything is computed locally and deterministically, so it is instant and private. Ideal for marine and aviation navigation, surveying and GIS, route analysis, and mapping. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is advanced geodesy; for simple great-circle distance, bearing, midpoint and destination use a geo-distance API and for coordinate-format conversion use a geo-convert API."
    },
    "meta": {
        "timestamp": "2026-06-03T17:42:05.228Z",
        "request_id": "caf21f23-7a27-4ba2-9a56-a241a4f61238"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}