How to Convert Latitude/Longitude to a Geo Link — geo: URI, Google Maps & More

Why Raw Coordinates Need to Become Links

A pair of numbers like 40.7128, -74.0060 means nothing to most people at a glance, and it can't be tapped on a phone. GPS devices, survey exports, delivery systems, and APIs all speak in raw decimal or DMS coordinates — but the person receiving that data usually just wants to tap something and see the location open in their maps app.

Converting coordinates into a proper link closes that gap. It also solves a second problem: different platforms (Google Maps, Apple Maps, Bing, OpenStreetMap) each use their own URL format, so "the right link" depends on who's opening it.

Raw: 40.7128, -74.0060
Link: https://www.google.com/maps?q=40.7128,-74.0060&z=15

You'll run into this exact conversion need across delivery coordination, field survey reporting, real estate listings, and any app feature that shows "open in maps."

Understanding the geo: URI Standard

The geo: URI scheme is defined in RFC 5870 and looks like geo:40.7128,-74.0060. It is the only link format that doesn't hard-code a specific maps provider — mobile operating systems intercept it and let the user pick whichever maps app is installed and preferred.

Optional parameters extend the base format — a zoom level via ?z=15, or a search label via ?q=. Not every desktop browser resolves geo: links, which is why platform-specific links (covered in Method 4) still matter for cross-device sharing.

Method 1 — Convert Coordinates Online (No Code Required)

For a one-off conversion — sharing a delivery point, checking a coordinate from a spreadsheet, or verifying a GPS export — the fastest method is a dedicated browser tool. No setup, and it handles decimal, separate-field, and DMS input equally well.

Method 2 — Build Map Links Manually With JavaScript

If you're building a feature that generates these links dynamically — say, a "share location" button — you can construct each URL directly from a lat/lng pair.

function buildMapLinks(lat, lng, zoom = 15, label = "") {
  const latStr = lat.toFixed(6);
  const lngStr = lng.toFixed(6);
  const encodedLabel = label ? encodeURIComponent(label) : "";

  return {
    geoUri: `geo:${latStr},${lngStr}?z=${zoom}`,
    googleMaps: `https://www.google.com/maps?q=${latStr},${lngStr}${
      label ? `(${encodedLabel})` : ""
    }&z=${zoom}`,
    appleMaps: `https://maps.apple.com/?ll=${latStr},${lngStr}&z=${zoom}`,
    osm: `https://www.openstreetmap.org/?mlat=${latStr}&mlon=${lngStr}#map=${zoom}/${latStr}/${lngStr}`,
  };
}

// Usage
const links = buildMapLinks(40.7128, -74.006, 15, "Office HQ");
console.log(links.geoUri);
// geo:40.712800,-74.006000?z=15

Method 3 — Converting DMS to Decimal Degrees

GPS receivers, surveying equipment, and photo EXIF data often store coordinates in Degrees-Minutes-Seconds (DMS) format rather than decimal. Before you can build a standard map link, you need to convert DMS to decimal degrees.

  function dmsToDecimal(degrees, minutes, seconds, direction) {
                                    let decimal = degrees + minutes / 60 + seconds / 3600;
                                    if (direction === "S" || direction === "W") {
                                        decimal = -decimal;
                                    }
                                    return decimal;
                                    }

                                    // Example: 40°42'46.1" N, 74°0'21.6" W (New York City)
                                    const lat = dmsToDecimal(40, 42, 46.1, "N"); // 40.712806
                                    const lng = dmsToDecimal(74, 0, 21.6, "W");  // -74.006000

The reverse conversion — decimal back to DMS, useful for display purposes — follows the same logic in the opposite direction:

function decimalToDMS(decimal, isLat) {
  const abs = Math.abs(decimal);
  const deg = Math.floor(abs);
  const minFloat = (abs - deg) * 60;
  const min = Math.floor(minFloat);
  const sec = ((minFloat - min) * 60).toFixed(2);
  const dir = isLat
    ? decimal >= 0 ? "N" : "S"
    : decimal >= 0 ? "E" : "W";
  return `${deg}°${min}'${sec}" ${dir}`;
}

Method 4 — Choosing the Right Link for Each Platform

Not every recipient uses the same maps app. Picking the right link format for the context avoids unnecessary redirects or broken previews.

Embedding a Live Map Preview

A link alone doesn't let someone verify the pin without leaving the page. Embedding an OpenStreetMap iframe gives an instant visual check before sharing further.

<iframe
  src="https://www.openstreetmap.org/export/embed.html?bbox=-74.016,-40.7228,-73.996,40.7028&layer=mapnik&marker=40.7128,-74.0060"
  width="100%"
  height="300"
  style="border:0"
  loading="lazy"
></iframe>

The bbox parameter defines the visible map bounds — a small delta (e.g. ±0.01 degrees) around your coordinate keeps the marker centered and reasonably zoomed. This is exactly the approach used in the QuickTextTools Lat/Long to Geo Link Converter live preview.

Common Mistakes and How to Avoid Them

Frequently Asked Questions