ForHosting KIT · Developer Utilities

Great-circle path intersection

This great-circle path intersection calculator finds where two spherical courses meet when each path is defined by a start latitude and longitude plus an initial true bearing.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Aviation, sailing, and GIS work often describe a track as “from this fix, heading such-and-such degrees,” not as a pair of endpoints; the engine converts each point-plus-bearing into a great-circle plane on the unit sphere, intersects the planes, and returns both antipodal intersection coordinates. The classic check is 51.8853 north, 0.2545 east, bearing 108.547 degrees against 49.0034 north, 2.5735 east, bearing 32.435 degrees, which lands near 50.9078 north, 4.5084 east. Arithmetic is closed-form vector geometry with no network calls, no sampling, and no date-dependent shortcuts. Use it free in the browser for flight-planning drills and map QA, or call the API at $0.002 per successful request when you need reproducible intersection fixtures in CI, navigation software, or teaching demos.

How to use it

Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.

Check your inputs

Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.

Use it again or automate it

Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.

What you can do with it

Get an answer now

Enter one set of values and see the result without building a spreadsheet or script.

Compare scenarios

Change one value at a time and rerun the calculation to understand what affects the result.

Automate repeated work

Use the API when the same calculation needs to run inside your product or workflow.

FAQ

How do I use this capability?

Complete the fields above and run it on this page. The form highlights anything that needs attention.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/geo/great-circle-intersection

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/geo/great-circle-intersection \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"lat1":51.8853,"lon1":0.2545,"bearing1":108.547,"lat2":49.0034,"lon2":2.5735,"bearing2":32.435}'

const res = await fetch("https://api.kit.forhosting.com/geo/great-circle-intersection", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "lat1": 51.8853,
    "lon1": 0.2545,
    "bearing1": 108.547,
    "lat2": 49.0034,
    "lon2": 2.5735,
    "bearing2": 32.435
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/geo/great-circle-intersection",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "lat1": 51.8853,
    "lon1": 0.2545,
    "bearing1": 108.547,
    "lat2": 49.0034,
    "lon2": 2.5735,
    "bearing2": 32.435
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/geo/great-circle-intersection", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"lat1":51.8853,"lon1":0.2545,"bearing1":108.547,"lat2":49.0034,"lon2":2.5735,"bearing2":32.435}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"lat1":51.8853,"lon1":0.2545,"bearing1":108.547,"lat2":49.0034,"lon2":2.5735,"bearing2":32.435}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/geo/great-circle-intersection", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "lat1": 51.8853,
  "lon1": 0.2545,
  "bearing1": 108.547,
  "lat2": 49.0034,
  "lon2": 2.5735,
  "bearing2": 32.435
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "geo.great_circle_intersection",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

`lat_min`	-90
`lat_max`	90
`lon_min`	-180
`lon_max`	180
`bearing_min`	0
`bearing_max`	360

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Read the full KIT documentation →

Run — free