How to Convert Latitude and Longitude to Decimal Degrees | 5 Steps to Avoid Confusion from Degrees, Minutes, and Seconds
By LRTK Team (Lefixea Inc.)
Table of Contents
• First understand what decimal degrees for latitude and longitude mean
• Basic formula to convert from degrees, minutes, seconds to decimal degrees
• 5 steps to convert latitude and longitude to decimal degrees
• Step 1: First confirm which part of the DMS is degrees
• Step 2: Divide minutes by 60 to convert to degrees
• Step 3: Divide seconds by 3600 to convert to degrees
• Step 4: Add degrees and the converted minutes and seconds
• Step 5: Check the sign for north/south latitude and east/west longitude
• Verify the decimal conversion with an actual input example
• Three common misunderstandings in conversion
• Also organize the difference between latitude and longitude
• How many decimal places are necessary
• How to check to avoid mistakes in manual calculation and data entry
• Benefits of remembering decimal conversion for latitude and longitude
• Summary
When working with latitude and longitude, it is common to get confused by different notations when you want to record a point on a map correctly. A frequent case is wanting to convert coordinates written in degrees, minutes, and seconds into decimal degrees but not knowing exactly how to calculate it. For people who use location information on site, check drawings or survey data, or enter data into mapping services, converting latitude and longitude is an unavoidable basic task.
In practice, people sometimes input values with an unclear understanding of degrees, minutes, and seconds, calculate without considering the sign for north/south or east/west, or mishandle decimal points, resulting in an unintended location being displayed. While the formula itself is not difficult, skipping intermediate checks makes errors easy to occur, which is what makes this task tricky.
This article explains how to convert latitude and longitude from degrees, minutes, and seconds to decimal degrees in five clear steps so you won't get lost. It does more than just present the formula: it explains what decimal degrees are, why conversion is necessary, where people tend to get stuck, and how to verify using input examples. By the end, even someone encountering coordinate conversion for the first time should be able to calculate and use coordinates correctly.
First understand what decimal degrees for latitude and longitude mean
First, keep in mind that latitude and longitude can be written in multiple formats. The most commonly seen format is degrees, minutes, and seconds. For example: north latitude 35 degrees 40 minutes 30 seconds, east longitude 139 degrees 45 minutes 15 seconds. This format is human-readable and has been widely used historically.
On the other hand, mapping systems and location input fields often use decimal degrees such as 35.675000, 139.754167. This expresses degrees with minutes and seconds combined as a decimal fraction of degrees. In other words, it's easy to think of decimal degrees as compressing the DMS components into a single numeric value.
The reason this conversion is needed is that digital data processing is easier with decimal degrees. Many operations—comparing locations, calculating distances, plotting on maps, registering with external systems—assume decimal degrees. In practice, you often need to convert coordinates written in DMS on paper or existing forms into decimal degrees for system input.
It's important to realize that DMS and decimal degrees are not different coordinates—they simply represent the same location in different formats. They may look different, but if you follow the conversion rules they point to the same place. Understanding this will reduce reluctance toward conversion work.
Basic formula to convert from degrees, minutes, seconds to decimal degrees
The conversion method is very simple. The basic idea is to divide minutes by 60, divide seconds by 3600, and add those to the degrees. In formula form, the decimal degree value equals degrees plus minutes divided by 60 plus seconds divided by 3600.
For example, for 35 degrees 40 minutes 30 seconds you add to 35 the result of 40 divided by 60, and the result of 30 divided by 3600. 40 ÷ 60 = 0.666666…, and 30 ÷ 3600 = 0.008333…. Adding these to 35 gives 35.675 as the decimal degrees.
Similarly, for 139 degrees 45 minutes 15 seconds you add to 139 the result of 45 ÷ 60 = 0.75 and 15 ÷ 3600 = 0.004166…. That yields 139.754166…. If rounded to about six decimal places, this becomes 139.754167.
From these calculations you can see that 60 minutes make 1 degree, and 60 seconds make 1 minute, so 3600 seconds make 1 degree. With this relationship you can convert any values using the same rule. There are no complicated special calculations. What matters is carefully separating the numbers so you don't mistake degrees, minutes, and seconds.
Also note that the decimal result is rarely an integer. Unless minutes and seconds are zero, you naturally get a decimal. A decimal result is not an error—it is the correct conversion. The fractional part after the decimal point represents positional precision.
5 steps to convert latitude and longitude to decimal degrees
From here, the practical steps are organized into five steps to avoid confusion. Following this order helps prevent calculation and data-entry mistakes.
Step 1: First confirm which part of the DMS is degrees
The first thing to do is correctly separate the given coordinate numbers into degrees, minutes, and seconds. For example, if written as 35°40′30″, 35 is degrees, 40 is minutes, and 30 is seconds. This looks simple, but source documents can omit symbols, use space separation, or compress digits.
A common mistake at this stage is treating 40 as 0.40. Forty minutes is not 0.40 degrees. Forty minutes is 40 out of 60, which equals 0.666666… degrees. Getting this wrong causes a large positional error.
If the coordinate is simply written 35 40 30, it's usually read from left to right as degrees, minutes, seconds. However, always prioritize any description in the original data. Some field data or forms may show only degrees and minutes with seconds omitted; in that case treat seconds as 0.
Before calculating, confirm you can distinguish degrees, minutes, and seconds. This initial organization affects everything that follows.
Step 2: Divide minutes by 60 to convert to degrees
Next, convert minutes into degrees. Since 1 degree equals 60 minutes, divide the minutes value by 60 to find how many degrees it represents. For example, 40 minutes is 40 ÷ 60 = 0.666666… degrees. Fifteen minutes is 15 ÷ 60 = 0.25 degrees.
This step is simple but is the part most often mistaken in decimal conversion. People tend to treat minutes as if they were already decimal fractions. For instance, misreading 20 minutes as 0.20 degrees instead of 20 ÷ 60 = 0.333333… causes a significant error. Because small numerical differences can translate to large positional shifts, this error cannot be ignored.
Coordinates may sometimes be given with minutes containing a decimal, such as 35 degrees 40.5 minutes. In that case divide 40.5 by 60 to get 0.675, then add to 35 to get 35.675. The same approach applies whether minutes are integer or fractional.
Converting minutes is the foundation of the whole conversion. Treat the rule "divide minutes by 60" mechanically to avoid confusion.
Step 3: Divide seconds by 3600 to convert to degrees
Next, convert seconds into degrees. Since 1 degree equals 3600 seconds, divide the seconds value by 3600. For example, 30 seconds is 30 ÷ 3600 = 0.008333… degrees, and 15 seconds is 15 ÷ 3600 = 0.004166… degrees.
Seconds are a smaller unit than minutes, so their numeric contribution is small. However, when precision matters, seconds are very important. Omitting seconds reduces the precision of the result and, in fine-position checks, can produce a value close to a different point.
Again, do not treat seconds as 0.30 or 0.15 as if they were decimal degrees. Seconds are 1/3600 of a degree and must always be divided by 3600.
If seconds include decimals, for example 30.5 seconds, the calculation is unchanged: divide 30.5 by 3600 and add the result to the degrees. Fractional seconds in coordinate data indicate finer precision and should not be rounded away unless the required precision calls for it.
Step 4: Add degrees and the converted minutes and seconds
Once you have degrees, the converted minutes, and the converted seconds, add them together. That yields the decimal degree coordinate. For example, 35 degrees 40 minutes 30 seconds becomes 35 + 0.666666… + 0.008333… = 35.675.
The key idea here is that you are adding quantities expressed in the same unit. Originally they were in degrees, minutes, and seconds, but converting minutes and seconds to degrees lets you sum them as like units. Understanding this makes clear why the formula works.
When using a calculator, keep parentheses in mind to avoid mistakes. For example, entering 35 + 40 ÷ 60 + 30 ÷ 3600 works, but entering values in a wrong order can yield a different result. Writing down intermediate values as you go can also help.
Also convert latitude and longitude separately. One common oversight is converting latitude but forgetting to do the same for longitude; a location requires both values. Always verify both numbers as a pair.
Step 5: Check the sign for north/south latitude and east/west longitude
Finally, don't forget to check the sign according to direction. For coordinates in Japan, north latitudes and east longitudes are typically used and treated as positive values, so everyday work may not require thinking about signs.
However, when dealing with global coordinates, it is standard to use negative for south latitudes and negative for west longitudes. That is: north is positive, south is negative; east is positive, west is negative. If you only look at the numeric result and enter it without the sign, you can lose this information.
For example, south latitude 35 degrees 40 minutes 30 seconds should become -35.675. West longitude 139 degrees 45 minutes 15 seconds should become -139.754167. It helps to think of appending the sign after computing the DMS total.
If you only work domestically you may often have positive values, but when working with overseas data, nautical charts, aviation data, or international geospatial information, this check is essential. A correct numeric conversion with the wrong sign points to a completely different location. Always recheck this at the end.
Verify the decimal conversion with an actual input example
Now let's verify with an actual example. Convert north latitude 35 degrees 40 minutes 30 seconds, east longitude 139 degrees 45 minutes 15 seconds to decimal degrees.
First, latitude. For 35 degrees 40 minutes 30 seconds, degrees = 35, minutes = 40, seconds = 30. Minutes ÷ 60 = 0.666666…, seconds ÷ 3600 = 0.008333…. Adding these gives 35.675. So the latitude is 35.675.
Next, longitude. For 139 degrees 45 minutes 15 seconds, degrees = 139, minutes = 45, seconds = 15. Minutes ÷ 60 = 0.75, seconds ÷ 3600 = 0.004166…. Adding these gives 139.754166…. Rounded to the necessary precision this becomes 139.754167.
So the decimal degrees for this point are 35.675, 139.754167. Many input fields expect latitude first then longitude, but some systems use a different order, so after conversion verify you haven't swapped latitude and longitude.
By carefully separating and calculating each value, you can convert to decimal degrees without special expertise. The important points are not to confuse degrees, minutes, and seconds and not to make assumptions during conversion.
Three common misunderstandings in conversion
Errors in converting latitude and longitude to decimal degrees arise more from assumptions than from the formula itself. Here are three common misunderstandings.
First is treating minutes as a plain decimal. For example, writing 35 degrees 40 minutes as 35.40 looks natural but is incorrect. Forty minutes is not 0.40 degrees; it's 40 ÷ 60 = 0.666666…. There is a large difference between 35.40 and 35.666666….
Second is ignoring seconds. Because seconds are small numbers people sometimes assume they have negligible effect and omit them. While numerically smaller than degrees and minutes, seconds can still change positional accuracy materially. For high-precision applications, seconds cannot be ignored.
Third is failing to confirm sign or hemisphere. If you don't check whether the coordinate is north or south, east or west, and just enter the converted number, you may point to a completely different region. The more accustomed you are to domestic data, the more likely you are to overlook this.
These misunderstandings are not about calculation skill; they stem from skipping verification steps or relying on appearance. That's why following a consistent order is more important than simply doing the math fast.
Also organize the difference between latitude and longitude
One reason conversion can be confusing is mixing up latitude and longitude. Latitude indicates north or south relative to the equator, while longitude indicates east or west relative to the prime meridian.
Generally, latitude ranges within ±90 degrees and longitude within ±180 degrees. Therefore, if a decimal result exceeds 100 and you expect it to be latitude, you may have swapped latitude and longitude. Conversely, longitudes near Japan are in the 100s, so if you see a longitude-like value in the 30s or 40s, that should raise suspicion.
After conversion, checking whether the numeric magnitude makes sense is effective. For example, latitudes in Japan are around the mid-30s and longitudes around the 139 range; these feel plausible. If latitude is 139 and longitude is 35, you probably swapped the order.
Coordinate conversion doesn't end after the calculation. Confirming the meaning of latitude and longitude, their valid ranges, and their order completes the verification needed for correct use.
How many decimal places are necessary
Many people wonder how many decimal places to keep after converting to decimal degrees. This depends on the use. For rough location checks, about four decimal places may be enough. For finer work, five or six decimal places—or more in some cases—may be necessary.
What's important is not to display more precision than the source data supports. If the original DMS are given only to integer seconds, adding excessive decimal digits gives only the appearance of precision. Conversely, if the receiving system expects six decimal places, you should round accordingly to match that format.
For example, 35.675 can be shown as 35.675000. This doesn't change the value but standardizes the number of displayed decimals. Many systems prefer consistent decimal places for handling.
When choosing how many digits to keep, consider both the precision of the source data and the purpose of the converted values. Don't keep more digits just for the sake of it; tailor precision to your practical needs.
How to check to avoid mistakes in manual calculation and data entry
You can do these conversions by hand, but in practice you often handle multiple entries, so data entry verification matters more than the calculation itself. Even comparing the original data and the converted data item by item helps prevent many mix-ups.
A helpful check is to confirm the integer part still matches the degrees. For a latitude in the 35-degree range, the integer part of the decimal result should be 35. For a longitude in the 139-degree range, the integer part should be 139. If these don't match, there is likely a calculation or ordering problem.
Also, note that larger minute values produce larger fractional parts. For instance, 40 minutes naturally corresponds to a fractional part in the 0.6 range. If you see only about 10 minutes but a fractional part of 0.8, that should feel wrong.
When dealing with multiple nearby points, check that values don't suddenly jump unexpectedly. If adjacent points show drastically different latitudes or longitudes, either the conversion or data entry may be wrong.
In short, knowing the formula isn't enough—you also need a sense for reading the results and spotting anomalies. Developing this intuitive check will significantly reduce simple errors.
Benefits of remembering decimal conversion for latitude and longitude
Being able to convert yourself increases flexibility when working with location data. You can instantly interpret coordinates in a document and calmly handle different input formats. If you know the conversion rules, you can adapt to various system or device formats.
Another benefit is being able to judge whether an input value is correct. Coordinate typos often pass unnoticed by people unfamiliar with the formats. But if you understand the relationship between DMS and decimal degrees, you will notice something off at a glance. This improves accuracy and shortens verification time.
Additionally, the skill applies across mapping, surveying, inspections, asset management, field checks, and other geospatial tasks. Conversion may seem trivial, but it is a highly versatile fundamental skill on site. Because it's a basic skill, it's worth organizing and learning rather than leaving it vague.
Summary
Converting latitude and longitude from degrees, minutes, and seconds to decimal degrees is not as hard as it looks. The basic procedure is to divide minutes by 60, divide seconds by 3600, and add those values to degrees. The formula itself is simple, but common errors arise from confusing degrees, minutes, and seconds, misreading minutes as decimals, omitting seconds, or overlooking hemisphere signs.
To avoid confusion, follow these five ordered steps: correctly separate degrees/minutes/seconds, divide minutes by 60, divide seconds by 3600, add them together to get decimal degrees, and finally check the sign for north/south and east/west. Following this flow gives reproducible conversion even for first-timers.
Converting coordinates is not just calculation—it's a basic skill for handling location information correctly. When transferring from paper to digital, standardizing different notations, or checking if an input is correct, this knowledge is useful. Use the approach presented here as your standard when you handle coordinates so you can confidently convert DMS to decimal degrees without hesitation.
Next Steps:
Explore LRTK Products & Workflows
LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.
LRTK supercharges field accuracy and efficiency
The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.


