Degrees decimal minutes to decimal degrees converter
Type 40° 26.767′ N and get 40.44611666666667: the minutes are divided by 60 and added to the degrees, and south or west makes the result negative, ready for a map or a spreadsheet. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Text
- 40° 26.767′ N
- Decimal degrees
- 40.4461166667
- Degrees
- 40
- Decimal minutes
- 26.767
- Hemisphere
- N
Convert a latitude or longitude written in degrees and decimal minutes into one signed decimal-degree value. Enter a coordinate such as 40° 26.767′ N or 79 58.933 W. The converter identifies latitude or longitude from the hemisphere, validates the correct geographic range, divides the decimal minutes by sixty, and applies a negative sign for south or west. The response also preserves the parsed components and supplies a normalized coordinate for straightforward checking.
Recognize a degrees and decimal minutes coordinate
Degrees and decimal minutes, commonly abbreviated DDM, represents one geographic axis with an integer degree component, a decimal minute component, and a hemisphere letter. A latitude might be written as 40° 26.767′ N, while a longitude might appear as 79° 58.933′ W. The hemisphere is essential because it establishes both the axis and the sign: N and S indicate latitude, whereas E and W indicate longitude.
This converter accepts the hemisphere at either the beginning or the end, and it accepts a degree symbol or whitespace between the two numeric components. A straight apostrophe, a typographic prime, or the English word minute may follow the minute value. Do not include a latitude-longitude pair, seconds, a negative degree sign, or a bare number without a hemisphere.
Those forms represent different contracts or leave the sign ambiguous. Decimal minutes must be at least zero and strictly less than sixty, just as the minutes on a clock cannot reach sixty without carrying into the next degree. Keeping these components explicit makes field notes and navigation exports easy to inspect before conversion.
Understand the conversion and geographic limits
The arithmetic is direct: decimal degrees equal degrees plus decimal minutes divided by sixty. The converter first calculates that positive magnitude, then makes it negative when the hemisphere is south or west. For example, a western longitude with seventy-nine degrees and 58.933 decimal minutes becomes the negative of seventy-nine plus 58.933 divided by sixty.
North and east remain positive. This sign convention is widely used by mapping databases, GeoJSON workflows, spreadsheets, and spatial APIs. Validation depends on the axis inferred from the hemisphere.
Latitude cannot exceed ninety degrees, and longitude cannot exceed one hundred eighty degrees. At exactly a pole or the antimeridian limit, the minute component must be zero because any additional fraction would cross the valid range. The implementation does not silently wrap an excessive longitude or carry sixty minutes into another degree; it rejects malformed values so an upstream data problem remains visible.
Use the result safely in mapping workflows
Use this converter when a GPS receiver, aviation record, marine log, survey note, or geocaching listing provides a single coordinate in DDM but your destination expects decimal degrees. Convert latitude and longitude separately, then keep their axis labels attached until you assemble a pair. Many geographic formats name latitude first and longitude second, while GeoJSON coordinate arrays conventionally place longitude first; conversion does not resolve that ordering difference for you.
Preserve enough decimal places for the accuracy of the source rather than treating a long floating-point result as newly created precision. One thousandth of a minute corresponds to roughly a couple of metres in latitude, though longitude distance varies with latitude. The tool performs no datum transformation, geocoding, map lookup, or coordinate-system inference beyond the N, S, E, and W letters.
It assumes the DDM numbers already refer to the datum required by your workflow. Invalid input is rejected without inventing a location, which is especially important in emergency, surveying, and asset-management pipelines where a plausible but incorrect sign can move a point across the world.
What you can do with it
Normalize GPS field notes
Turn one DDM latitude or longitude from a receiver or notebook into the signed decimal value required by a GIS table.
Prepare navigation data
Convert hemisphere-based marine or aviation coordinates before importing them into software that accepts signed decimal degrees.
Validate coordinate migrations
Use the returned components, axis, normalized form, and formula to audit a DDM-to-decimal data conversion.
FAQ
How are decimal minutes converted to decimal degrees?
Divide the decimal minutes by sixty and add the result to the whole degrees. Apply a negative sign for S or W.
Can the hemisphere appear before the numbers?
Yes. Both N 40° 26.767′ and 40° 26.767′ N are accepted, as are the equivalent S, E, and W forms.
Why are south and west negative?
Signed decimal-degree convention treats latitude south of the equator and longitude west of the prime meridian as negative.
Can I enter degrees, minutes, and seconds?
No. This capability is specifically for degrees and decimal minutes. Convert DMS with the dedicated degrees-minutes-seconds converter.
What ranges are accepted?
Latitude accepts zero through ninety degrees and longitude accepts zero through one hundred eighty. At the maximum degree, minutes must be zero.
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/ddm-to-decimal \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"40° 26.767′ N"}'const res = await fetch("https://api.kit.forhosting.com/geo/ddm-to-decimal", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "40° 26.767′ N"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/geo/ddm-to-decimal",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "40° 26.767′ N"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/geo/ddm-to-decimal", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"40° 26.767′ N"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"40° 26.767′ N"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/geo/ddm-to-decimal", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "40° 26.767′ N"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "geo.ddm_to_decimal",
"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
Recognize a degrees and decimal minutes coordinate
Supply only one coordinate per request.
Understand the conversion and geographic limits
The response returns the signed decimal_degrees value, the original numeric components, the uppercase hemisphere, the inferred axis, a normalized DDM string, and the exact formula structure used. This makes the result suitable for both display and auditable automation.
Use the result safely in mapping workflows
Browser use is free for quick checks, while a successful automated API conversion costs $0.002 per item.
Technical questions
What does an API conversion cost?
A successful API conversion costs $0.002 per item. You can also run the conversion free in your browser.