Decimal Degrees vs Degrees, Minutes, and Seconds

Decimal degrees (DD) and degrees, minutes, and seconds (DMS) are two ways of writing the same angular coordinate. They do not describe different coordinate reference systems, and converting from one notation to the other should not move a location except for any rounding introduced during the conversion.

A longitude written as 9.708333 degrees can also be written as 9 degrees 42 minutes 30 seconds E. The difference is notation: decimal degrees express the whole angle as one decimal number, while DMS divides each degree into 60 minutes and each minute into 60 seconds.

For digital GIS, databases and APIs, decimal degrees are usually easier to store and calculate with. DMS remains common in navigation, field notes, surveying records, legal descriptions and human-facing coordinate displays.

The two notations represent the same angle

One degree contains 60 minutes, and one minute contains 60 seconds. That means:

1 degree = 60 minutes
1 minute = 60 seconds
1 degree = 3600 seconds

The DMS coordinate:

9 degrees 42 minutes 30 seconds E

therefore represents:

9 + 42/60 + 30/3600
= 9.708333... degrees E

Nothing geographic has changed; only the way the angle is written is different.

This distinction is useful because DMS can look like three separate values even though degrees, minutes and seconds together form one coordinate component. Treating the minutes or seconds as independent decimal fractions is a common source of conversion errors.

How to convert DMS to decimal degrees

For a positive north or east coordinate:

decimal degrees = degrees + minutes / 60 + seconds / 3600

For example:

4 degrees 15 minutes 0 seconds N
= 4 + 15/60
= 4.25 degrees N

South and west coordinates are normally negative under the common signed-decimal convention. A safe conversion is to calculate the magnitude first, then apply the direction once:

3 degrees 30 minutes 0 seconds S
= -(3 + 30/60)
= -3.5 degrees

Applying the sign once matters. A value such as -3 degrees 30 minutes S mixes two direction conventions and can be interpreted inconsistently by software or people.

How to convert decimal degrees to DMS

Start with the absolute decimal value.

For 9.708333:

The integer part is 9 degrees.
Multiply the remaining 0.708333 by 60 to get approximately 42.49998 minutes.
The integer part is 42 minutes.
Multiply the remaining fractional minute by 60 to get approximately 30 seconds.

The result is approximately:

9 degrees 42 minutes 30 seconds

The original sign determines the hemisphere. A negative longitude becomes west; a negative latitude becomes south.

Because decimal values are often rounded, a reverse conversion may produce 29.9988 or 30.0012 seconds rather than exactly 30. That is a numerical rounding issue, not evidence that the coordinate changed materially.

Why `4.30 degrees` does not mean 4 degrees 30 minutes

This mistake deserves special attention because it looks so plausible.

Decimal degrees use base-10 fractions. DMS uses base-60 subdivisions. Therefore:

4.30 degrees = 4 degrees + 0.30 degrees

and:

0.30 degrees x 60 = 18 minutes

So 4.30 degrees equals 4 degrees 18 minutes, not 4 degrees 30 minutes.

The DMS value 4 degrees 30 minutes is 4.5 decimal degrees.

If coordinates arrive in strings such as 4.30 without metadata, do not assume they are compact DMS. Establish the source convention before converting anything.

Direction can be encoded with signs or letters

DMS is often written with hemisphere letters:

N for north;
S for south;
E for east;
W for west.

Decimal degrees commonly use signed values:

north latitude positive;
south latitude negative;
east longitude positive;
west longitude negative.

The two conventions carry the same directional information, with problems arising only when they are mixed carelessly.

For example, -4 degrees latitude already expresses a southern latitude under the signed convention. Adding an S suffix may be redundant or may cause a parser to apply the direction twice. A robust data model should choose one internal convention and validate imported text before normalising it.

Why Are Some Coordinates Negative? explains the sign convention in more detail, including why projected coordinates can also be negative.

Decimal degrees are usually better for computation

A numeric decimal-degree field is straightforward to sort, compare, transform and pass to GIS libraries. That is why digital spatial data generally normalises geographic coordinates into numeric values rather than keeping DMS as free-form text.

DMS is more awkward because several representations can mean the same thing:

9 degrees 42 minutes 30 seconds E
9 42 30 E
9:42:30 E
E 9 42 30

Symbols may vary as well. Prime characters can be replaced with ordinary quotes, hemisphere letters can appear before or after the number, and seconds may include decimals.

If the original DMS expression has legal, historical or evidential value, keep it in a source field. Create separate validated numeric fields for analysis instead of overwriting the original text.

Conversion does not create accuracy

A coordinate written to whole seconds has a certain notation precision, but converting it to six or eight decimal places does not create a more accurate observation.

One second of latitude corresponds to roughly 31 metres, so if a source records latitude only to the nearest second, the converted decimal value may mathematically contain several decimal places even though most of those digits are consequences of base conversion rather than additional field measurement.

The reverse is also true. Rounding a precise decimal-degree observation to whole seconds throws away numeric detail even though the underlying measurement may have been more accurate.

This is why conversion and quality should be treated separately. Coordinate Precision vs Coordinate Accuracy explains why numeric detail and positional trustworthiness are different properties.

Coordinate order is a separate question

DMS versus decimal degrees tells you how each latitude or longitude value is written. It does not tell you whether latitude or longitude comes first in a coordinate pair.

A DMS source may list latitude first because that is common in human-readable notation. A GeoJSON coordinate uses longitude first regardless of whether you mentally think of the location as "latitude, longitude". A CSV can use either order according to its schema.

Do not use the presence of DMS or decimal degrees to infer axis order. The format, CRS and field definitions remain authoritative. Latitude vs Longitude: Which Comes First? is the canonical guide to that issue.

Which notation should you use?

Use decimal degrees when coordinates need to move through databases, APIs, GIS tools or analytical code. They are easier to validate as numbers and avoid the parsing complexity of DMS.

Use DMS when the source, audience or domain expects it. It can be more familiar in navigation and some field or legal contexts, and preserving the original notation may be important for traceability.

The important choice is not which notation is more "accurate". They are mathematically equivalent ways to express an angle. The practical question is which notation is least likely to be misread in the workflow you are building.

Convert deliberately, apply direction once, preserve the source where it matters, and round only after the conversion is complete.