ForHosting KIT · Travel & geography

Rhumb line destination point

Find the arrival point when you hold one compass course: 10 km at 45° from 51.4778, -0.0015 ends at 51.5413916406, 0.100674380088. Distances can be in metres, kilometres, statute miles or nautical miles. 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
Constant rhumb-line bearing
45
Distance
10,000
You get
Bearing normalized
45
Distance unit
M
Distance m
10,000
Earth radius m
6,371,000

A rhumb-line destination calculator answers the direct problem of constant-bearing navigation: given where you start, the true course you hold without turning, and how far you sail or fly, where do you arrive? Unlike a great-circle path, a rhumb line—also called a loxodrome—crosses every meridian at the same angle, so the compass course stays fixed from departure to arrival. This tool takes a start latitude and longitude in decimal degrees, a constant bearing clockwise from true north, and a distance in meters, kilometers, statute miles, or nautical miles, then returns the spherical rhumb destination on mean Earth radius or any positive custom radius you supply.

How the rhumb-line 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 constant true 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. Advance latitude with Δφ equals δ times cos θ so that pure east–west courses leave latitude unchanged and pure north–south courses change only latitude. Form the isometric latitudes ψ1 and ψ2 as the natural logarithms of the tangents of π over four plus half of each geodetic latitude; their difference Δψ scales longitude change along the Mercator strip.

When |Δψ| is appreciable, set the scale factor q to Δφ over Δψ; when the course is essentially east–west and Δψ vanishes, fall back to q equals cos φ1 so longitude steps correctly on a parallel. Then Δλ equals δ times sin θ over q and λ2 equals λ1 plus Δλ. Convert φ2 and λ2 back to degrees, keep latitude inside the closed range from negative ninety through positive ninety, and fold longitude into the open–closed range around the antimeridian so GIS layers plot cleanly.

Paths that would drive latitude past a pole are rejected rather than wrapped, because a true rhumb cannot cross the pole while holding a fixed azimuth.

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 constant rhumb true course 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 course for ten thousand meters, and verifying the destination sits northeast of the start on a track of constant azimuth.

Where rhumb-line destination calculators show up in real work

Maritime and aviation training constantly contrast rhumb-line sailing with great-circle flying, and students need a trusted oracle that returns destination lat/lon from a departure fix, constant true course, and distance without a chart protractor. Passage planners still plot many coastal and mid-latitude legs as rhumbs because the helm holds one compass heading, and logistics teams prototype ferry tracks, survey lines, and pipeline corridors the same way before committing to full ellipsoid libraries.

Orienteering curricula, hiking guides, and search-and-rescue grids often step waypoints by fixed distance on a fixed azimuth from a known trailhead. Game and simulation engines place entities on a spherical world with constant-heading motion so client and server stay aligned without shipping a heavy geodesic package.

If you later need the great-circle destination (shortest path with changing course), the inverse problem of distance and bearing between two fixed points, or full WGS84 Vincenty geodesics on the ellipsoid, treat those as separate search intents and landings—this page stays focused on the constant-bearing rhumb destination point.

Constant-course navigation training

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

Passage planning and survey lines

Project fixed-azimuth tracks from a departure coordinate for coastal routes, ferry legs, and grid survey corridors without a full geodesic stack.

Waypoint chains at constant heading

Build sequential waypoints by stepping fixed distances on a held bearing for hiking routes, SAR patterns, and simulation spawn rings.

What formula does this rhumb line destination calculator use?

The spherical loxodrome direct formula: Δφ = δ·cosθ, φ2 = φ1+Δφ, Δψ = ln(tan(π/4+φ2/2)/tan(π/4+φ1/2)), q = Δφ/Δψ (or cosφ1 for E–W), Δλ = δ·sinθ/q, λ2 = λ1+Δλ, with δ = d/R and longitude normalized to (−180, 180].

How is this different from a great-circle destination?

Great-circle tools solve the shortest path with a changing course; this tool solves constant-heading arrival.

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.

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/rhumb-destination

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/rhumb-destination \
  -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.rhumb_destination",
  "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.

The pipeline uses only elementary trigonometry and a logarithm of isometric latitude: convert degrees to radians, form angular distance as path length over radius, step latitude by δ times cos θ, form the Mercator isometric difference, recover longitude with δ times sin θ over the isometric scale factor, and fold longitude into the standard map range. Negative distances and out-of-range coordinates 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 equal to the constant course, the method tag rhumb_line_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 rhumb-line destination calculators show up in real work

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.

Read the full KIT documentation →