Rectifying latitude calculator
Turn a geodetic latitude into its rectifying latitude on WGS-84: 45° becomes 44.855682294117°, the angle that makes the true distance from the equator behave like an arc on a sphere. You also get that meridian arc in metres. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Latitude
- 45
- Rectifying latitude deg
- 44.8556822941
- Rectifying latitude rad
- 0.7828793443
- Geodetic latitude rad
- 0.7853981634
- Difference deg
- -0.1443177059
Rectifying latitude is the auxiliary angle used when map projections and geodesy treat meridian arc length as if it were a spherical polar angle. On the WGS-84 ellipsoid the ground distance from the equator to a geodetic latitude φ is not exactly a times φ; the true meridian arc M grows with a series of eccentricity terms. The rectifying latitude μ is defined so that M equals R prime times μ, where R prime is the radius of a sphere that has the same total meridional perimeter as the ellipsoid. Surveyors, GIS engineers, Transverse Mercator implementers, and students of conformal map projections need μ when checking textbook tables, validating projection libraries, or teaching why auxiliary latitudes exist. This capability accepts a single geodetic latitude in decimal degrees, evaluates the standard Snyder e-one series with fixed WGS-84 constants, and returns μ in degrees and radians, the difference from φ, the meridian arc in metres, and the rectifying radius. Latitudes outside minus ninety to ninety fail with invalid input.
What rectifying latitude means and how to supply geodetic latitude
Geodetic latitude φ is the angle between the equatorial plane and the normal to the ellipsoid surface—the latitude GPS and most GIS layers report. Meridian arc distance from the equator to φ is an elliptic integral of the second kind; in closed form it is expressed as a trigonometric series in φ and the first eccentricity. Rectifying latitude μ is the unique angle on a sphere of radius R prime such that the spherical arc R prime times μ matches that ellipsoidal meridian distance M.
Equivalently, μ equals M divided by R prime, with R prime chosen so the quarter-meridian of the ellipsoid equals R prime times pi over two. Practitioners meet μ in Snyder’s Map Projections manual, in EPSG guidance notes for Transverse Mercator, and in any library that builds a conformal projection by first mapping the ellipsoid to a sphere of equal meridional length. Latitude must lie between minus ninety and ninety inclusive.
What you can do with it
Transverse Mercator and projection libraries
Validate μ intermediate steps when implementing or testing conformal projections that map the ellipsoid to a sphere of equal meridian arc before spherical formulas apply.
Meridian arc distance tables
Survey and navigation notebooks need the equator-to-latitude arc in metres on WGS-84 without integrating elliptic integrals by hand or spinning up a desktop GIS.
FAQ
What happens if latitude is out of range?
Missing or non-finite latitude fails the same way.
Is rectifying latitude the same as geodetic latitude?
Only at the equator and poles (to series accuracy).
Is the rectifying latitude calculator free?
The browser tool runs free on your device.
Why do map projections need rectifying latitude?
Conformal projections such as Transverse Mercator first map the ellipsoid onto a sphere with the same meridian length. Rectifying latitude is the angle on that sphere that keeps the true north-south distance from the equator, so spherical formulas can then be applied.
How far is it from the equator to 45° along the meridian?
Just under five thousand kilometres on WGS-84. The calculator returns this meridian arc in metres next to the rectifying latitude, so you can read the distance without integrating it by hand.
Related tools
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
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/rectifying-latitude \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"latitude":45}'const res = await fetch("https://api.kit.forhosting.com/geo/rectifying-latitude", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"latitude": 45
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/geo/rectifying-latitude",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"latitude": 45
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/geo/rectifying-latitude", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"latitude":45}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"latitude":45}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/geo/rectifying-latitude", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"latitude": 45
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "geo.rectifying_latitude",
"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
Published price — no tokens, no invented credits. A failed task is never charged.
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. |
Technical notes
What rectifying latitude means and how to supply geodetic latitude
This endpoint evaluates the classical e-one series: e squared equals f times two minus f; e-one equals one minus square root of one minus e squared, all over one plus that square root; then μ equals φ minus a coefficient times sin of two φ, plus terms in sin of four φ, six φ, and eight φ through order e-one to the fourth. Send the required field latitude as a JSON number or numeric string in decimal degrees; aliases lat, phi, and geodetic_latitude are accepted. Values outside that closed interval, missing fields, non-finite numbers, and non-numeric strings raise invalid_input with a message that names the field. Identical inputs always produce identical JSON because the path is pure series arithmetic with fixed WGS-84 constants—no wall clock, no random seed, and no external geodetic service.
Reading degrees, radians, meridian arc, and datum fields
On success the response echoes latitude, then reports rectifying_latitude_deg as μ in decimal degrees and rectifying_latitude_rad as the same angle in radians. geodetic_latitude_rad is the input converted by pi over one hundred eighty so callers can compare φ and μ in a single unit system without converting again. difference_deg is μ minus φ in degrees; on WGS-84 the magnitude is typically a few hundredths of a degree at mid-latitudes and vanishes at the equator and the poles where the series terms cancel or sin of multiples of pi over two become zero. meridian_arc_m is the north–south ground distance from the equator to the given latitude in metres, computed as rectifying_radius_m times μ in radians. rectifying_radius_m is R prime, the radius of the sphere of equal meridional perimeter, derived from the semi-major axis and powers of e squared. ellipsoid is always the string WGS-84; a_m is six million three hundred seventy-eight thousand one hundred thirty-seven metres; f is the flattening one over two hundred ninety-eight point two five seven two two three five six three; e2 and e1 are the first eccentricity squared and the rectifying series parameter, rounded for stable goldens. method is always snyder_e1_series. Prefer degrees when teaching or matching published tables; prefer radians and meridian_arc_m when wiring a projection pipeline; use difference_deg to sanity-check that μ and φ stay close on Earth-like ellipsoids. Validation failures are not charged under the prepaid API.
API usage, pricing, projection workflows, and practical limits
Send a JSON body with the required latitude field, then call the free in-browser rectifying latitude calculator for homework checks, lecture demos, and quick projection debugging without installing PROJ, GeographicLib, or a full GIS stack. Use the prepaid API when a mapping platform, curriculum generator, or coordinate-conversion pipeline needs a stable contract under KIT balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with degree-of-latitude length tools when you need local meridional scale, or with a full Transverse Mercator product when the next step is easting and northing rather than the auxiliary angle alone. This product does not convert to authalic, conformal, isometric, or geocentric latitude—those auxiliary angles serve area, angle preservation, or radius-of-curvature problems and are separate search intents. It also does not invert μ back to φ; inversion needs a different series or Newton iteration.
Integration use cases
Classroom geodesy and exam oracles
Students convert textbook geodetic latitudes to rectifying latitude; graders pin deterministic JSON for μ, difference, and meridian arc from the same φ used in the problem set.
Technical questions
How do I convert geodetic latitude to rectifying latitude?
Send JSON with latitude set to a decimal degree value between −90 and 90. The response includes rectifying_latitude_deg, rectifying_latitude_rad, difference_deg, and meridian_arc_m on the WGS-84 ellipsoid.
Which datum and formula are used?
Always WGS-84 with the Snyder e1 series through order e1^4 (method snyder_e1_series). The response echoes a_m, f, e2, e1, and rectifying_radius_m on every success.