top of page

6 Checks to Do When You’re Stumped Converting Latitude/Longitude to Decimal Degrees|With Input Examples

By LRTK Team (Lefixea Inc.)

All-in-One Surveying Device: LRTK Phone
text explanation of LRTK Phone

In practical work handling latitude and longitude, even when you understand the meaning of the coordinates themselves, differences in notation often lead to input errors or conversion mistakes. Especially for many who search for “latitude longitude decimal conversion,” the typical situation is that coordinates given in degrees-minutes-seconds need to be correctly transcribed into maps, positioning devices, reports, or survey data. Even small-looking differences in appearance can cause large position shifts if you apply a single wrong conversion rule, resulting in rechecks on site, re-surveys, or report corrections.


Converting latitude and longitude is not just a math problem. It requires correctly reading the original notation, understanding sign conventions for north/south and east/west, choosing the number of decimal places to match the business purpose, and determining the format required by the target system after conversion. Only then does the conversion become practically useful. Knowing only the formula often causes problems in the field.


This article organizes and explains six points that practitioners should check when converting latitude and longitude to decimal degrees. It covers not only the idea behind the formulas but also input examples, common mistakes, verification procedures, and practical perspectives that you can use directly in work. If you want to develop a reproducible procedure rather than a makeshift conversion, this guide explains things clearly and carefully.


Table of contents

• What converting latitude/longitude to decimal degrees means

• Check 1: Distinguish DMS notation from decimal notation

• Check 2: Don’t concatenate minutes and seconds as a decimal

• Check 3: Handle signs correctly for south latitudes and west longitudes

• Check 4: Set the number of decimal places according to use

• Check 5: Don’t mix up latitude and longitude order

• Check 6: Confirm the converted format matches the target system’s requirements

• Input examples you can use for converting to decimal degrees

• Practical workflow to prevent conversion mistakes

• Summary


What converting latitude/longitude to decimal degrees means

Converting latitude and longitude to decimal degrees means replacing coordinates given in degrees-minutes-seconds (DMS) with a decimal format. For example, a value such as 35 degrees 39 minutes 30 seconds can be awkward to use directly in many mapping systems or position input fields. Therefore, it is converted to a decimal form such as 35.658333 for use. Although it looks simple, you must calculate taking into account that there are 60 minutes in a degree and 60 seconds in a minute.


In practice, coordinate information is passed around in many formats: paper drawings, notes on site photos, existing registers, positioning logs, reports, tender documents, inspection records, and so on. It is not uncommon for one source to use DMS while another uses decimal degrees. Even if they appear to indicate the same location, transcribing them without knowing the conversion rules may cause them to be treated as different places.


What’s particularly tricky is that latitude and longitude look like just numbers, making errors hard to notice. With measurement errors you might feel something’s off, but it’s easy to be unsure whether a value is 35.39 or 35.658333 unless you’re used to the notation. Moreover, even if the calculation is correct, misreading the original notation will produce a wrong result. That’s why, in practice, what you check before calculating is as important as how you calculate.


Decimal notation is widely used because it works well for input, calculations, and data linkage. Being expressible as decimals makes it easy to store and display in various systems, and simplifies handling across devices and software. At the same time, many legacy field documents still use DMS, so switching between both formats happens frequently. Thus, converting to decimal is not merely an auxiliary skill but a fundamental task for practitioners who handle position information.


If you keep the six checks introduced in this article in mind, you can greatly reduce not only simple calculation mistakes but also mismatches between source and destination formats that cause errors. First, as a foundation before conversion, let’s confirm how to distinguish different notation styles.


Check 1: Distinguish DMS notation from decimal notation

The first thing to verify for coordinate conversion is whether the value you have is really in degrees-minutes-seconds or already in decimal degrees. If you get this wrong, even the correct formula will produce a completely different result. In practice, you often receive numbers without degree, minute, or second symbols and may judge by appearance alone.


For example, 35.658333 is a typical decimal notation. On the other hand, 35 39 30 or 35°39′30″ is easily interpreted as DMS because degrees, minutes, and seconds are separated. In reality, however, you might encounter variations like 35-39-30, 35:39:30, 35 39.500, or 35°39.5′ depending on the document. What matters here is not the visual symbols but reading which units the numbers are separated into.


A common source of confusion is degree-and-minute notation. This expresses degrees and minutes only, with seconds shown as a decimal of minutes. For example, 35°39.5′ means the same as 35 degrees 39 minutes 30 seconds. If you misread that as 35 degrees 39.5 seconds, you’ll end up with a completely different coordinate. Thus, identifying the notation format is the most important step before calculation.


A practical tip for distinguishing formats is to check whether the numbers fall into reasonable ranges. Minutes and seconds only go from 0 to the 50s or 59. If you see something like 35 82 14, the “82” is implausible as minutes. Also, decimal degrees tend to have many digits after the decimal point, while DMS often has integer separators. There are exceptions, so also check any legends on the original source or the name of the input field.


The magnitude of the latitude and longitude values also gives clues. Within Japan, latitude is typically in the 20s to 40s and longitude in the 120s to 150s. If you see values like “35.40, 139.45,” you can judge whether they make sense as decimal degrees. Conversely, a trio like 35 40 12 / 139 45 18 suggests DMS. Skipping this confirmation and starting conversion immediately can lead to mistakes such as dividing a value already in decimal degrees by 60, resulting in a point far away and making the cause hard to trace later. Determining the format of the input is the starting point for correct conversion.


Check 2: Don’t concatenate minutes and seconds as a decimal

One of the most common conversion mistakes is concatenating minutes and seconds as if they were decimals. For example, writing 35 degrees 39 minutes 30 seconds as 35.3930 is incorrect. It may look plausible, but minutes and seconds are base-60, not base-10, so you must convert them to decimal degrees.


The correct formula is: decimal degrees = degrees + minutes ÷ 60 + seconds ÷ 3600. For 35°39′30″, calculate 35 + 39 ÷ 60 + 30 ÷ 3600. Since 39 ÷ 60 = 0.65 and 30 ÷ 3600 = 0.008333..., the total is 35.658333.... The key point is that minutes are divided by 60 and seconds by 3600. Dividing seconds by 60 only converts seconds to minutes, not to degrees.


This conversion concept can be confusing at first because everyday decimal intuition makes people treat 39 minutes as 0.39 degrees or 30 seconds as 0.30 degrees. But DMS is like a clock: each lower unit increments by 60, not 100. One degree is 60 minutes, not 100; one minute is 60 seconds, not 100. If you don’t switch that assumption mentally, you’ll end up with a superficial and incorrect conversion like 35.3930.


The same idea applies when converting from degree-and-minute notation. For example, 35°39.5′ becomes 35 + 39.5 ÷ 60 = 35.658333.... The 39.5 minutes already include the equivalent of seconds, so you must not add more seconds. If you split 39.5 into 39 minutes 5 seconds incorrectly, you’ll double-count and produce an error.


Intermediate calculations can produce many digits, and rounding too early can accumulate small errors. For instance, truncating the results of minutes ÷ 60 or seconds ÷ 3600 prematurely will slightly shift the final value. In practice, it’s safer to keep precision until just before the final display rounding. First convert accurately, then round the final output according to the intended use.


To avoid conversion mistakes, think of the task as unit conversion rather than simply rearranging numbers. With that mindset, superficial errors like writing 35.3930 instead of converting units are greatly reduced. Correctly understanding units matters more than memorizing formulas for successful latitude/longitude decimal conversion.


Check 3: Handle signs correctly for south latitudes and west longitudes

When converting latitude and longitude to decimals, even if your arithmetic is correct, mishandling signs can send the coordinate to the opposite hemisphere. The usual convention is latitude: north is positive, south is negative; longitude: east is positive, west is negative. Overlooking this rule can lead to basically correct-looking numbers that are nonetheless hugely wrong as location data.


In Japan-centered work, you often deal with north latitudes and east longitudes and thus rarely think about signs. Indeed, if you handle only domestic data, you’ll mostly see positive values like 35.658333 or 139.745556. However, when dealing with overseas data, coordinates from foreign map services, international data exchange, or device testing with foreign samples, checking the sign becomes essential.


For example, if you convert 33 degrees 52 minutes south to decimal degrees, the numeric conversion alone gives 33.866667. But because it’s south latitude, you must input -33.866667. West longitudes are likewise negative. Entering values without the correct sign will cause the point to be placed in the northern or eastern hemisphere instead. Even with the correct conversion formula, the geographic context becomes inverted.


Note that notation varies across sources. You might see N, S, E, W, or the Japanese words 北緯, 南緯, 東経, 西経. Sometimes the numeric value already has a minus sign. People sometimes overthink and try to add another minus because they saw “south,” but ultimately only one correct sign should be reflected in the final numeric input. Thinking of sign handling as “one correct sign in the final numeric field” helps reduce confusion.


Some systems accept direction letters in a separate field instead of negative numbers. For instance, rather than inputting -35.658333 for north latitude, you might input 35.658333 and put N in another column. Whether to put a minus sign on the numeric field depends on the target system’s specification. Avoid entering both a sign and a direction letter that prescribe different meanings; check the spec to prevent misinterpretation.


Even in domestic-only workflows, don’t let your knowledge of signs grow vague. Data exchange or external sources can suddenly bring international formats into play. Make it a habit to check degrees-minutes-seconds conversion together with the north/south/east/west to sign mapping to avoid swapped locations.


Check 4: Set the number of decimal places according to use

After converting coordinates to decimal degrees, deciding how many digits to keep after the decimal point often causes uncertainty. For reports you might want shorter, more readable numbers, while for locating a site or managing positioning records you may need finer granularity. The important thing is that more digits are not always better, nor is fewer always more readable—the number of decimals should match the intended use.


The decimal places in decimal degrees relate to positional resolution. For rough location checks, a small number of decimals can suffice; but for reproducing inspection points, matching drawings, quality control, and sharing positioning logs—tasks requiring higher precision—insufficient decimals can produce unintended position differences. Conversely, adding unnecessary digits in internal presentation makes reports harder to read without improving communication.


For example, for site directions or broad location identification, about five decimal places can be practical. For more detailed location sharing, six or seven decimals may be used. However, increasing the number of display digits does not make coordinates more accurate than the source data. If the original DMS input is only precise to the second, the inherent information content is limited. Increasing displayed decimals beyond the source precision only gives a false appearance of accuracy.


Be mindful also of where you round during calculations. If you shorten minutes ÷ 60 or seconds ÷ 3600 too early, the final value will be slightly off. Decide whether to round only the final value for reports, while keeping more digits internally for system input. In practice, keep a little more precision for internal management and round for external submissions or readability.


When multiple people handle coordinates, consistency in decimal places is important. If one person uses five decimals and another uses seven, the same location may appear as slightly different numbers, causing unnecessary checks over which is “correct.” Establish rules such as: report values use X decimals, positioning logs keep Y decimals, map inputs use Z decimals. Such rules reduce operational confusion.


Decimal places are not just cosmetic; they express precision and affect operations. Don’t stop at conversion—consider where and how those coordinates will be used, and choose the number of decimals accordingly.


Check 5: Don’t mix up the order of latitude and longitude

A surprisingly common error with coordinate data is reversing latitude and longitude order. Even if the conversion calculations are correct, entering them in the wrong order at the destination causes large position errors. This is especially likely when working with plain-number lists, files with omitted column names, or repetitive copy-paste tasks.


Many contexts use the “latitude, longitude” order, but some formats are defined as “longitude, latitude.” Don’t rely on intuition to decide which is correct. For domestic coordinates, latitude tends to be in the 20s–40s and longitude in the 120s–150s, so seeing 35 and 139 normally indicates 35 is latitude and 139 is longitude. But if the system expects longitude first, it will instead require 139, 35.


This order difference is easy to miss visually. In CSVs or tables where headers are abbreviated, inexperienced staff might swap them. Also, even if a document is labeled “latitude longitude,” the exported file might have a different column order. For transcription, always verify the order in both the source and the target.


Checking positions on a map helps detect order mistakes quickly. If you input a domestic location and the map shows it offshore or in another country, the first suspicion should be that latitude and longitude were swapped. While checking digit counts and conversion formulas is important, order mistakes are frequent and should be an early check.


Operationally, don’t omit column names. Simply labeling columns as “lat” and “lon” or “latitude” and “longitude” dramatically reduces transcription errors. Standardize templates and input formats so that staff don’t get confused when roles change. Rather than relying solely on individual vigilance for conversion tasks, design formats that make mistakes unlikely.


Because order mistakes are a different class of trap from calculation errors, don’t assume “value obtained = done.” Add a final step to confirm which value is latitude and which is longitude to reduce rework on site.


Check 6: Confirm the converted format matches the input destination’s requirements

The last thing to check in decimal conversion is whether the converted value matches the target system’s format. This is easily overlooked but critically important in practice because even within decimal notation, the expected formatting can differ subtly by destination. If you don’t match the required format, correctly converted values might not be recognized or could be misinterpreted.


For instance, an input field that expects a period as the decimal separator may fail to recognize numbers copied from another source if those numbers contain a different symbol. Also check whether the field expects only a numeric value, or requires inclusion of a direction letter (N/E), whether latitude and longitude are entered in separate fields or together as comma-separated values. Formatting issues during final structuring cause many problems despite correct conversions.


Some targets accept only DMS, while others require decimal but will error if degree symbols remain. Conversely, if the document is intended for human readers, decimal-only coordinates may be less intuitive than DMS, so including both formats can be more communicative. The correct format is not a matter of formula but of the target system’s specification and the business purpose.


Don’t treat conversion as an isolated task. Always prepare the output while keeping in mind “where will this be entered,” “who will read it,” and “what system will receive it.” If the destination is a system, check the spec; if it is a report, choose the reader-friendly format; if multiple uses exist, produce separate management and submission formats.


Also watch out for invisible issues from copy-paste: trailing or leading spaces, full-width characters, or embedded newlines can cause values not to be recognized. After conversion, verify not only that the numeric values are correct but also that the string contains no extraneous characters.


Converting to decimal degrees is only half the job when it comes to practical use. In practice, it is complete only when the value is usable in the next step. Habitually confirming the target system’s format helps ensure that correctly converted values lead to actual work outcomes.


Input examples you can use for converting to decimal degrees

Below are typical input formats and how to think about converting them to decimal degrees. First, a basic example: converting 35 degrees 39 minutes 30 seconds to decimal. The calculation is 35 + 39 ÷ 60 + 30 ÷ 3600. The result is 35.658333..., the most standard conversion example.


Next, converting 139 degrees 44 minutes 44 seconds: 139 + 44 ÷ 60 + 44 ÷ 3600, which is about 139.745556. Combining latitude and longitude, for example 35°39′30″ and 139°44′44″, gives decimal degrees of 35.658333 and 139.745556 respectively. Keep the latitude/longitude order consistent here.


Consider the degree-and-minute example: 35°39.5′ means divide 39.5 by 60: 35 + 39.5 ÷ 60 = 35.658333..., which equals 35°39′30″. Field documents sometimes omit seconds and express them as decimal minutes, so don’t assume missing seconds means missing information—check whether decimal minutes already include seconds.


Examples with south latitudes and west longitudes are also important. South 12°30′00″ converts to 12 + 30 ÷ 60 = 12.5, and because it’s south, the final value should be -12.5. West 77°2′11″ converts to 77 + 2 ÷ 60 + 11 ÷ 3600 ≈ 77.036389, and because it’s west, it should be -77.036389. It helps to separate numeric conversion from sign handling.


When working with examples, practitioners should aim not to memorize one example but to be able to interpret any incoming format using the same logic. Check in order: is it DMS, degree-and-minute, or already decimal? Is the direction expressed with a letter or a sign? What is the order? By following unit, sign, order, and output format checks in sequence, you can handle most patterns. Rather than being confused by the digits themselves, go through units, sign, order, and output format.


When rushed on site, it helps to verbalize the conversion steps once: “This is 35°39′30″, so add 39/60 and 30/3600 to 35” and “This is south, so make it negative.” Speaking the steps reduces input errors. With practice you’ll do this mentally, but at first checking step-by-step is most reliable.


Practical workflow to prevent conversion mistakes

To correctly perform latitude/longitude decimal conversions, don’t rely solely on personal calculation or vigilance. In practice you often process many points under time pressure, transcribe from different sources, or divide work among people, so understanding alone won’t eliminate errors. Standardizing the procedure is effective.


First, clearly record the original notation: DMS, degree-and-minute, or decimal. This prevents confusion later. Next, check north/south and east/west information and clarify sign rules if necessary. Apply the conversion formula, then adjust order and decimal places. Finally, format according to the destination and validate plausibility on a map. This flow—identify format, determine sign, convert, set order and decimals, match target spec, and verify on a map—is ideal.


Of these steps, final validation is particularly effective. Checking the converted coordinate on a map to see if it points near the intended site will catch many mistakes. Even if the calculation is right, order swaps, wrong signs, or excessive rounding are easily spotted visually. Don’t stop at checking numbers; mapping the point often reveals issues.


When processing multiple points, set minimal internal rules so different operators don’t vary in their decisions. For example, decide how many decimals to keep in management data, which format to use in reports, and a consistent column order. Such rules reduce the burden of handover and help prevent repeated errors.


Also remember that the true value in handling coordinates isn’t just conversion itself but how the coordinates are used afterward. Surveying, inspection, construction staking, maintenance, photo cataloging, and reporting all require quick and accurate linking of coordinates to the field. That’s why converting must not remain an individual skill but should be integrated into a reusable operational flow.


Conversion to decimal degrees is the entry point to working with coordinates. If people are uncertain here, the same checks will be repeated downstream. If you clearly define the checks, the flow from input to sharing to site confirmation becomes smooth. Though conversion seems minor, it fundamentally affects the accuracy and efficiency of the entire workflow.


Summary

When you’re stuck converting latitude and longitude to decimal degrees, don’t jump straight to the formula—first identify what the input actually is. Confirm whether it’s DMS, degree-and-minute, or already decimal; convert minutes and seconds as base-60 units; apply signs for south latitudes and west longitudes; set decimal places according to use; verify the latitude/longitude order; and ensure the final format matches the input destination. Only then will the coordinates be practically usable. The six checks introduced here are each important individually but are best applied as a continuous flow. Omitting any step tends to cause rework later, so make the sequence a habitual part of your procedure.


When handling position data in the field, you should consider not only conversion but how the coordinates will be used on site. If you can correctly convert coordinates and then record, share, verify, and apply them without hesitation, the accuracy of inspections, positioning, staking, and reporting improves markedly. If you want to increase speed and reliability in handling position data, consider integrating conversion with the entire chain from acquisition to utilization. LRTK, for example, attaches to an iPhone to make high-precision positioning easier to handle, helping practical positioning, recording, and sharing on site. Once you’ve mastered the basics to avoid confusion in latitude/longitude conversion, LRTK may be a natural next option to streamline coordinate use in the field.


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.

bottom of page