Degrees, Radians and Gradians: Which Angle Unit and Why

Three units divide the circle differently, and choosing the wrong one in a calculation produces answers that are wrong by a factor of about 57 — large enough to notice, but only if you check.

Degrees: 360 and why

A full turn is 360 degrees. The choice is ancient, probably Babylonian, and its persistence is owed to arithmetic convenience: 360 has 24 divisors, so it divides evenly by 2, 3, 4, 5, 6, 8, 9, 10, 12, 15, 18, 20, 24, 30, 36, 40, 45, 60, 72, 90, 120 and 180.

Try that with 100. Thirds of a circle are 120 degrees exactly; in a decimal system they would be 33.33 recurring.

Subdivisions follow the sexagesimal pattern: 60 arcminutes to a degree, 60 arcseconds to an arcminute. Navigation and astronomy still use these, though decimal degrees are now more common in GPS data.

Radians: the mathematically natural unit

One radian is the angle subtended at the centre of a circle by an arc equal in length to the radius. A full turn is 2π radians, so one radian is about 57.2958 degrees.

The awkward number is the price of a property that matters enormously: radians make the calculus of trigonometry clean.

• The derivative of sin(x) is cos(x) — only in radians. In degrees an extra factor of π/180 appears.
• The small-angle approximation sin(θ) ≈ θ holds only in radians.
• Arc length is simply s = rθ, with no conversion constant.
• Taylor series for trigonometric functions assume radians.

Gradians: the metric attempt

A gradian (also gon or grade) divides a right angle into 100, giving 400 to a full turn. It emerged from the same French revolutionary metrication that produced the metre.

The appeal was decimal tidiness: a right angle is exactly 100 gon, and 50 gon is exactly half. It found genuine use in European surveying, where it persists, but never displaced degrees more broadly.

Most scientific calculators still offer a GRAD mode, which is chiefly notable for producing confusing results when switched on by accident.

The programming trap

This is where the distinction most often bites.

Nearly every programming language's trigonometric functions expect radians. Python's math.sin(), JavaScript's Math.sin(), C's sin() — all radians.

Passing degrees produces no error, just wrong answers. Math.sin(90) returns about 0.894, not 1, because it interprets 90 as 90 radians — roughly 14.3 full turns.

The conversions are:

radians = degrees × π / 180
degrees = radians × 180 / π

Most languages provide helpers: Python has math.radians() and math.degrees(). Use them rather than hard-coding the constant.

Spreadsheets are the same: Excel's SIN() takes radians, with RADIANS() and DEGREES() available for conversion. A great many spreadsheet errors come from feeding degrees straight in.

Other angular measures

• Turns / revolutions — one turn is 360°. Natural for rotational speed.
• Mil (NATO) — 1/6400 of a turn, used in artillery. Chosen because one mil subtends approximately one metre at one kilometre, making range estimation easy.
• Compass points — 32 to a circle, 11.25° each. Historical navigation.

Slope: a different quantity

Gradients quoted as percentages are not angles. A 100% gradient is 45°, not a quarter turn.

Percentage slope is rise over run: slope% = tan(θ) × 100. The relationship is non-linear, so a 10% grade is about 5.7°, and percentages cannot exceed a right angle no matter how large they get.

Our angle converter handles degrees, radians, gradians, turns, arcminutes, arcseconds and mils.

Arcseconds, coordinates and real-world precision

Angular precision translates directly into distance on the ground, which is why latitude and longitude are quoted so precisely.

One degree of latitude is about 111 km. Dividing down:

• 1 arcminute ≈ 1.85 km (one nautical mile, by definition)
• 1 arcsecond ≈ 31 m
• 0.1 arcsecond ≈ 3.1 m
• 0.001 arcsecond ≈ 3.1 cm

So a coordinate quoted to four decimal places of a degree locates a point to roughly 11 metres; six decimal places gets you to about 11 centimetres. Quoting more digits than your measurement supports is the angular version of false precision.

Astronomy pushes far further. Ground-based telescopes are typically limited to about 1 arcsecond by atmospheric turbulence, which is why adaptive optics and space telescopes exist. The Hubble Space Telescope resolves to roughly 0.05 arcseconds — equivalent to distinguishing two objects a few centimetres apart from 100 kilometres away.

Degrees, minutes, seconds versus decimal degrees

Two notations for the same coordinate are in common use, and mixing them produces errors that place you in the wrong country.

DMS format writes 40 ° 26′ 46″ N. Decimal degrees writes 40.4461 ° N. Converting is straightforward:

decimal = degrees + minutes/60 + seconds/3600

The trap is that 40 ° 26′ is not 40.26 °. It is 40.433 °, because minutes are sixtieths rather than hundredths. Reading a DMS value as decimal introduces an error of up to about 18 km in latitude.

Most GPS devices and mapping APIs use decimal degrees; most nautical and aviation charts use DMS. Anything crossing between the two needs an explicit conversion, not an assumption.