ForHosting KIT · Travel & geography

Destination point calculator

Leave 51.4778° N, 0.0015° W on a bearing of 45° for 10000 m and you arrive at 51.5413472357° N, 0.100745643529° E. Enter a start, a course and a distance in metres, kilometres, miles or nautical miles to get the destination and the final bearing. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Latitude
51.4778
Longitude
-0.0015
Initial great-circle bearing
45
Distance
10,000
You get
Bearing normalized
45
Distance unit
M
Distance m
10,000
Earth radius m
6,371,000

A destination-point calculator answers the spherical direct problem of navigation: given where you stand, the true course you leave on, and how far you travel, where do you arrive? This tool takes a start latitude and longitude in decimal degrees, an initial bearing clockwise from true north, and a distance in meters, kilometers, statute miles, or nautical miles, then returns the great-circle destination on a sphere of mean Earth radius—or any positive custom radius you supply. The formula uses only elementary trigonometry: convert degrees to radians, form the angular distance as path length over radius, evaluate the classic asin and atan2 destination identities, and normalize longitude into the open–closed range around the antimeridian.

How the great-circle destination formula works

Treat the Earth as a sphere of radius R—by default the conventional mean radius of six million three hundred seventy-one thousand meters—and convert the start latitude φ1 and longitude λ1 from degrees into radians. Convert the initial bearing θ the same way, measuring clockwise from true north so that zero is due north, ninety is due east, one hundred eighty is due south, and two hundred seventy is due west. Convert the travel distance into meters if needed, then form the angular distance δ equals d over R in radians.

The destination latitude is the arcsine of sin φ1 times cos δ plus cos φ1 times sin δ times cos θ. The destination longitude is λ1 plus the two-argument arctangent of sin θ times sin δ times cos φ1 over cos δ minus sin φ1 times sin φ2, which preserves the correct quadrant when the course crosses meridians or poles.

After converting φ2 and λ2 back to degrees, clamp latitude naturally through arcsine into negative ninety through positive ninety and fold longitude into the range from negative one hundred eighty through positive one hundred eighty so map layers and GIS tools can plot the point without a second normalization pass. Zero distance returns the start point with a well-defined final bearing; distances that wrap the globe many times remain mathematically valid on the sphere though they may not match ellipsoid geodesics used by high-precision surveying.

What you send and what you get back

Send four required finite numbers under the fields latitude, longitude, bearing, and distance. Latitude must lie in the closed interval from negative ninety to positive ninety degrees with north positive. Longitude must lie in the closed interval from negative one hundred eighty to positive one hundred eighty degrees with east positive.

Bearing is the initial great-circle azimuth in degrees; values outside zero to three hundred sixty are accepted when finite and then normalized into that half-open range for computation and reporting. Classic checks include leaving Greenwich near fifty-one point four seven seven eight north, zero point zero zero one five west, on a forty-five degree bearing for ten thousand meters, and verifying the destination sits northeast of the start.

Where destination-point calculators show up in real work

Aviation and maritime training constantly assign rhumb-line versus great-circle drills, and students need a trusted oracle that returns destination lat/lon from a departure fix, true course, and distance without a chart protractor. Search-and-rescue planning, hiking guides, and orienteering curricula build waypoints by projecting a bearing and distance from a known trailhead. Game and simulation engines place entities on a spherical world using the same closed form so client and server stay aligned without shipping a heavy geodesic package.

If you later need the inverse problem of distance and bearing between two fixed points, rhumb-line sailing, or full WGS84 Vincenty geodesics on the ellipsoid, treat those as separate search intents and landings rather than overloading this spherical destination-point page.

Navigation training and exam keys

Generate destination lat/lon for great-circle legs from a start fix, true course, and distance so instructors and auto-graders share one ground truth.

Search patterns and waypoint chains

Build sequential waypoints by stepping fixed distances on successive bearings for SAR grids, hiking routes, and simulation spawn rings.

What formula does this destination point calculator use?

The spherical great-circle direct formula: angular distance δ = d/R, φ2 = asin(sinφ1·cosδ + cosφ1·sinδ·cosθ), λ2 = λ1 + atan2(sinθ·sinδ·cosφ1, cosδ − sinφ1·sinφ2), with longitude normalized to (−180, 180].

What happens if distance is negative?

Travel distance must be zero or positive. Reverse travel is modeled by adding 180° to the bearing, not by a negative distance.

Which units can I use for distance?

Meters (m, default), kilometers (km), statute miles (mi), or nautical miles (nmi). Values are converted to meters before dividing by the sphere radius.

Is this WGS84 ellipsoid Vincenty?

For high-precision surveying on the ellipsoid, use a dedicated geodesic library and a separate landing.

What does it cost?

The browser tool is free and runs 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/destination-point

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/destination-point \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"latitude":51.4778,"longitude":-0.0015,"bearing":45,"distance":10000}'
{
  "latitude": 51.4778,
  "longitude": -0.0015,
  "bearing": 45,
  "distance": 10000
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "geo.destination_point",
  "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.

Negative distances and out-of-range latitudes or longitudes fail with a clear invalid_input message instead of inventing a silent wrap.

What you send and what you get back

Distance must be zero or positive in the chosen unit—negative travel distance is rejected with invalid_input and is not charged. Optionally set distance_unit to m, km, mi, or nmi (default meters) and earth_radius_m to any finite positive sphere radius when you model another planet or a textbook radius. On success the response echoes cleaned inputs, the normalized bearing, the distance in meters, the radius used, the angular distance in degrees, a destination object with latitude and longitude, a final_bearing at the arrival end of the arc, the method tag great_circle_spherical, and a compact formula string for documentation. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.

Where destination-point calculators show up in real work

GIS and logistics teams prototype geofence centers, service radii, and corridor endpoints by stepping along bearings from a depot before committing to full ellipsoid libraries. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.

GIS service radii and corridor endpoints

Project depot bearings and range rings into coordinate pairs for geofences, delivery corridors, and map prototypes without a full geodesic stack.

Read the full KIT documentation →