Degrees decimal minutes to DMS converter
40° 26.78′ N becomes 40° 26′ 46.8″ N: the whole minutes stay, the leftover 0.78 of a minute times 60 gives the seconds, and the hemisphere letter is kept. A signed decimal value comes along so you can check the result. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Degrees
- 40
- Decimal minutes
- 26.78
- Hemisphere
- N
- Minutes
- 26
- Seconds
- 46.8
- Axis
- latitude
- Sign
- 1
A degrees and decimal minutes coordinate sits between decimal degrees and full degrees-minutes-seconds notation. This converter takes a whole degree component, a decimal-minute component, and a hemisphere letter, then separates the minute value into whole minutes and seconds. It returns normalized DMS, the coordinate axis, sign, a formatted coordinate, and a signed decimal-degree check value. The calculation is deterministic and validates geographic limits for latitude and longitude, making it suitable for GPS notes, survey records, navigation worksheets, and automated data-cleaning pipelines that need a precise DDM-to-DMS conversion.
How fractional minutes become seconds
Degrees and decimal minutes, commonly abbreviated DDM, preserves the degree component as a whole number while expressing minutes with a decimal fraction. For example, twenty-six point seven eight decimal minutes contains twenty-six whole minutes. Its remaining zero point seven eight minute multiplied by sixty produces forty-six point eight seconds.
The resulting coordinate is therefore the original degrees, twenty-six minutes, and forty-six point eight seconds, with the supplied hemisphere letter retained. If rounding reaches exactly sixty seconds, it carries into minutes; if that carry reaches sixty minutes, it carries into degrees. This normalization guarantees that successful output never contains an invalid sixty-second or sixty-minute component.
No lookup, datum transformation, map projection, or location search occurs: this is a format conversion of one geographic angle using fixed arithmetic only.
What you can do with it
Normalize handheld GPS notes
Turn DDM waypoints recorded in the field into standard DMS components for reports and shared coordinate lists.
Prepare survey and navigation documents
Split fractional minutes into seconds while retaining the correct latitude or longitude hemisphere letter.
Check coordinate-conversion coursework
Compare hand calculations against deterministic minutes, seconds, sign, and signed decimal-degree verification fields.
FAQ
How do I convert decimal minutes to seconds?
Take the fractional part after removing whole minutes and multiply it by 60. For 26.78 minutes, 0.78 multiplied by 60 is 46.8 seconds.
Can decimal minutes equal 60?
No. Decimal minutes must be at least 0 and less than 60. A value of 60 belongs as a carry into the degree component.
Should degrees be negative for south or west?
No. Supply non-negative whole degrees and use S or W as the hemisphere.
How are seconds rounded?
Seconds are rounded deterministically to six decimal places. A rounded value of 60 carries into the next whole minute.
What happens if the seconds round up to 60?
They carry over: 60 seconds become one more minute, and if the minutes then reach 60 they become one more degree. That way a result never shows 60 seconds or 60 minutes.
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-dms \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"degrees":40,"decimal_minutes":26.78,"hemisphere":"N"}'const res = await fetch("https://api.kit.forhosting.com/geo/ddm-to-dms", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"degrees": 40,
"decimal_minutes": 26.78,
"hemisphere": "N"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/geo/ddm-to-dms",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"degrees": 40,
"decimal_minutes": 26.78,
"hemisphere": "N"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/geo/ddm-to-dms", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"degrees":40,"decimal_minutes":26.78,"hemisphere":"N"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"degrees":40,"decimal_minutes":26.78,"hemisphere":"N"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/geo/ddm-to-dms", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"degrees": 40,
"decimal_minutes": 26.78,
"hemisphere": "N"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "geo.ddm_to_dms",
"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
How fractional minutes become seconds
To convert it to degrees, minutes, and seconds, keep the degrees unchanged, take the whole-number part of decimal_minutes as the DMS minute component, and multiply the remaining fractional minute by sixty. The converter rounds seconds to six decimal places so common floating-point residue does not leak into otherwise clean JSON.
Choosing degrees, minutes, and hemisphere correctly
Latitude is limited to ninety degrees and longitude to one hundred eighty degrees. Lowercase hemisphere letters are normalized to uppercase, but any other letter is rejected. Southern and western coordinates receive a negative check value; northern and eastern coordinates receive a positive value. Send degrees as a non-negative whole number and decimal_minutes as a finite value greater than or equal to zero and strictly less than sixty. Put direction in hemisphere rather than attaching a minus sign to degrees: N and S identify latitude, while E and W identify longitude. This single-source sign rule prevents ambiguous inputs such as negative degrees combined with a western letter. At either endpoint, decimal minutes must be zero because ninety degrees plus any latitude minutes would pass a pole, and one hundred eighty degrees plus longitude minutes would pass the antimeridian limit. A successful response supplies whole degrees, whole minutes, rounded seconds, normalized hemisphere, axis, sign, a readable DMS string, and signed_decimal_degrees for a convenient independent check.
Using DDM-to-DMS conversion in practical workflows
DDM often appears on handheld GPS receivers, field notebooks, marine waypoints, aviation materials, and forms where minutes need more precision than whole values but a full seconds column is inconvenient. DMS remains common in published coordinates, survey descriptions, classroom exercises, and human-readable reports, so converting between the two formats is a routine normalization task. In a field-data workflow, store the original DDM values alongside the returned DMS components so reviewers can reproduce the split and distinguish formatting changes from changes to the measured position. In a spreadsheet migration, call the capability once for latitude and once for longitude, keeping the appropriate hemisphere letter with each row. In education, compare the returned seconds with the hand calculation of fractional minutes times sixty, then use signed_decimal_degrees to discuss how cardinal directions map to signs. This tool deliberately processes one coordinate angle per item: it does not parse a free-form latitude-longitude pair, infer a missing hemisphere, convert datums, or geocode a place name. Those jobs require different validation and different search intent. Before automating a large import, include an endpoint case such as ninety degrees north with zero minutes and an invalid case with sixty decimal minutes in tests. These checks confirm that upstream column mapping has not confused decimal degrees, decimal minutes, and seconds.
Technical questions
What does the conversion cost?
The browser tool runs free. Each successful API request processes one item at the published base price of $0.002.