ForHosting KIT · Developer Utilities

Final bearing at destination

A great-circle route usually changes compass direction as it crosses the curved surface of Earth.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

This calculator finds the final bearing at the destination: the direction in which the path is pointing when it arrives, measured clockwise from true north. Enter the starting and destination coordinates in decimal degrees to receive a normalized arrival azimuth and a familiar sixteen-point compass label. The calculation is deterministic spherical trigonometry, with no map lookup, network request, magnetic model, or hidden route service involved.

Understand the bearing reported at arrival

Final bearing is the forward direction of travel at the destination of a great-circle path. Imagine following the shortest arc over a globe from the first coordinate to the second. Your heading when you depart is the initial bearing, but the meridians beneath the route converge and diverge as you move, so the local angle against true north generally rotates. The value returned here is that angle at the instant the route reaches the second coordinate. It is measured clockwise: zero degrees is north, ninety is east, one hundred eighty is south, and two hundred seventy is west. The numeric answer is normalized from zero inclusive to three hundred sixty exclusive and rounded to six decimal places. A sixteen-point compass label is included for readable summaries, but the degree value should be used for calculations and drawing. This is not the bearing from the destination back to the start. That reverse bearing points along the same arc in the opposite travel direction; rotating it by one hundred eighty degrees produces the forward arrival bearing reported by this capability.

Enter coordinates and interpret the calculation

Provide lat1 and lng1 for the start, followed by lat2 and lng2 for the destination. All four inputs use signed decimal degrees. Northern latitudes and eastern longitudes are positive, while southern latitudes and western longitudes are negative. Latitude must remain between minus ninety and ninety, and longitude between minus one hundred eighty and one hundred eighty. The two coordinate pairs must identify different locations because a zero-length route has no meaningful direction of arrival. The calculator converts both points to radians, computes the initial azimuth of the same great-circle arc when viewed from destination back toward start, adds a half turn, and normalizes the result. This reverse-then-rotate method is mathematically equivalent to following the initial course through its spherical arc rotation. The response echoes both points, making logs and batch results easy to audit. It also returns the unit as deg and a compass sector such as NW or SSE. Coordinates are treated as positions on a sphere, and the bearing is referenced to geographic true north rather than a magnetic compass reading.

Choose the right navigation model for your work

Use a final great-circle bearing when a map, route summary, simulation, or waypoint system needs to show the direction of arrival rather than the direction of departure. Airline route diagrams are a classic example: a long flight can leave on one heading and approach its destination on a visibly different heading even though it follows one continuous shortest-path arc. Maritime planning, educational globes, logistics dashboards, and geographic data pipelines use the same idea. The spherical model is fast, transparent, and consistent with common great-circle calculations, but it is an approximation of Earth. It does not account for the ellipsoidal reference surfaces required by precision geodesy, local terrain, roads, currents, wind, restricted areas, or a vehicle's actual maneuvers. It also does not apply magnetic declination, so do not compare its true bearing directly with an uncompensated magnetic compass. For ordinary geographic visualization and planning, the closed-form result is usually the useful answer. For cadastral surveys, safety-critical navigation, or centimeter-level positioning, use a vetted ellipsoidal geodesic system and the applicable operational data. Automated API calls cost $0.002 per item, while identical pure computation can run in the browser.

Label a route's arrival direction

Display the true-north heading at the endpoint of a great-circle line on a map or geographic dashboard.

Prepare waypoint summaries

Add an arrival azimuth and readable compass sector to flight, marine, or expedition waypoint records.

Check spherical navigation exercises

Generate a deterministic final bearing for lessons and calculations that compare departure and arrival headings.

What is a final bearing?

It is the forward azimuth of a great-circle path at its destination, measured clockwise from true north.

Is final bearing the same as initial bearing?

Usually not. A great-circle heading generally changes along the route because its angle relative to local meridians changes.

Is this the reverse bearing back to the start?

No. The reverse initial bearing is rotated by 180 degrees to express the original route's forward direction at arrival.

Does the calculator use magnetic north?

No. It reports a geographic true-north bearing and does not apply magnetic declination.

How much does an API request cost?

Each successful API item uses the published base price of $0.002; the browser path can perform the same deterministic calculation locally.

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.

POSThttps://api.kit.forhosting.com/geo/final-bearing

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.

curl -X POST https://api.kit.forhosting.com/geo/final-bearing \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"lat1":51.5074,"lng1":-0.1278,"lat2":40.7128,"lng2":-74.006}'
{
  "lat1": 51.5074,
  "lng1": -0.1278,
  "lat2": 40.7128,
  "lng2": -74.006
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "geo.final_bearing",
  "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.

Per request$0.002

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

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →