Coordinates in Modern Mapping and GPS: From Satellites to Your Device

1) GPS Coordinates and the Reference Model (Datum)

When your phone or GPS receiver shows a latitude/longitude, it is not just giving “a point on Earth.” It is giving a point on a specific mathematical model of Earth called a geodetic datum. A datum defines:

• the size and shape of the Earth model (an ellipsoid),
• how that ellipsoid is positioned relative to the real Earth,
• and the origin and orientation of the coordinate system.

Most consumer GPS uses WGS 84 (World Geodetic System 1984) as its default datum. Many digital maps also use WGS 84 or a closely related system. However, some national mapping agencies and older datasets use local datums (for example, NAD27, NAD83, OSGB36, ED50). If you plot coordinates from one datum on a map expecting another datum, the point can appear shifted.

Why different datums can shift positions

Different datums fit the Earth differently. A local datum may be optimized for one region, while WGS 84 is global. The same real-world location can have slightly different latitude/longitude numbers depending on the datum. The shift might be small (a few meters) or noticeable (tens to hundreds of meters), depending on the datums involved and the location.

Practical implication: If someone shares coordinates from a survey map or a government dataset, confirm the datum before assuming the coordinates match what your phone map shows.

How to check or set the datum

• Dedicated GPS receivers: often allow you to choose the map datum in settings (e.g., WGS 84, NAD83). The displayed coordinates change when you change the datum.
• Phones: typically operate internally in WGS 84 for GNSS. Some apps may display coordinates in other systems, but many do not expose a “datum switch” clearly.
• GIS/web tools: usually let you specify the coordinate reference system (CRS). If you import coordinates, choose the correct CRS/datum before plotting.

2) Accuracy vs. Precision in GPS (and What Affects Readings)

Two terms are often mixed up:

Continue in our app.

• Listen to the audio with the screen off.
• Earn a certificate upon completion.
• Over 5000 courses for you to explore!

Or continue reading below...

Download the app

• Accuracy: how close your reported position is to the true location.
• Precision: how consistent repeated measurements are with each other (tight clustering), regardless of whether they are correct.

A device can be precise but inaccurate (tight cluster offset from the true point) or accurate but not very precise (average near the true point but scattered).

Common factors that change GPS accuracy

• Sky view (satellite geometry): More visible satellites spread across the sky generally improves accuracy. If buildings or terrain block parts of the sky, the solution degrades.
• Multipath: Signals can bounce off buildings, cliffs, vehicles, or even water, causing the receiver to measure a longer path than the direct signal. This can shift your position, sometimes dramatically in “urban canyon” streets.
• Device quality and antenna design: A dedicated GNSS receiver with a better antenna often outperforms a phone in difficult environments.
• Assistance and corrections: Many phones use A-GNSS (assisted GNSS) and can combine GNSS with Wi-Fi and cell signals. Some receivers use SBAS (satellite-based augmentation) or RTK (real-time kinematic) for much higher accuracy.
• Atmospheric effects: The ionosphere and troposphere slightly delay signals. Modern receivers model or correct for this, but conditions still matter.
• Motion and handling: Holding a phone close to your body, placing it in a pocket, or moving quickly can reduce signal quality.

Reading the “accuracy” number on your device

Many apps show an estimated accuracy such as “±5 m.” Treat this as an estimate, not a guarantee. It is typically a statistical radius (often related to a confidence level) based on signal quality and geometry. In challenging conditions, the estimate may be optimistic or may lag behind reality.

3) From Coordinate to Map Pin: How Apps Use Latitude/Longitude

Digital maps turn a coordinate into a visible point by performing these steps:

1. Interpret the coordinate in a datum/CRS: e.g., latitude/longitude in WGS 84.
2. Transform if needed: many web maps display using Web Mercator (a projection used for tiled maps). The app converts latitude/longitude into the map’s internal x/y tile coordinates.
3. Render a marker: the “pin” is drawn at that x/y location on your screen at the current zoom level.

Search (geocoding) and reverse search (reverse geocoding)

• Geocoding: you type an address or place name, and the app returns coordinates for it.
• Reverse geocoding: you tap a point or share coordinates, and the app returns a human-readable place description (street, city).

Geocoding is not perfect. An address might map to a building centroid, a parcel entrance, or a street segment depending on the provider’s data model.

Routing and navigation

Routing engines use coordinates as inputs and outputs:

• Start and destination: coordinates (from your GPS fix or a searched location).
• Map matching: your noisy GPS points are “snapped” to the most likely road or path.
• Turn-by-turn instructions: generated from the route geometry (a series of coordinates) and road attributes.

Practical implication: If your GPS points drift, the app may snap you to the wrong parallel street, especially near dense road networks.

Geotagging (photos, notes, and tracks)

When you take a photo, your device can store coordinates in metadata (commonly EXIF GPS tags). Apps also store:

• Single points: a note or “saved place” with one coordinate.
• Tracks: a time-ordered list of coordinates (a breadcrumb trail).
• Geofences: a coordinate plus radius to trigger alerts when you enter/leave an area.

4) Practical Activity: Record, Verify, and Share Coordinates

Activity goal

You will capture coordinates at a real location, verify them on a map, and share them in multiple formats to see how small formatting choices affect interpretation.

Step A — Record coordinates on your device

1. Go outside to a spot with a clear view of the sky (an open area is ideal).
2. Open a map or GPS status app that shows your current latitude/longitude and an accuracy estimate.
3. Wait 30–60 seconds for the position to stabilize.
4. Write down:
   • Latitude
   • Longitude
   • Displayed accuracy (e.g., ±6 m)
   • Time (optional but useful)
5. Record the coordinates in decimal degrees (example format: 37.421998, -122.084000).

Step B — Verify by plotting on a map

1. Open a web map on another device (or the same device).
2. Paste your coordinates into the search bar in the format lat, lon (many maps accept this).
3. Confirm the pin lands where you were standing. If it is off, compare the offset to your accuracy estimate.
4. Zoom in and check whether the point falls on the correct side of the street, correct building, or correct trail.

Step C — Share in multiple coordinate formats

Create three shareable versions of the same location:

• Decimal degrees (DD): 37.421998, -122.084000
• Degrees and decimal minutes (DMM): 37° 25.3199', 122° 05.0400' W
• Map link: use your map app’s “Share” feature to generate a URL (this often embeds coordinates).

When sharing, include the datum if you know it. For most phone-derived coordinates, you can note: Datum: WGS 84.

Step D — Compare results across apps

1. Send the three formats to a friend (or to yourself via email).
2. Open each in a different app (e.g., a web map, a hiking app, a GIS viewer).
3. Check whether all apps land on the same spot. If one differs, note which format or app caused the mismatch.

5) Troubleshooting Checklist for Mismatched Coordinates

Use this checklist when a coordinate “doesn’t land where it should.” Work from the most common issues to the more technical ones.

1) Datum / CRS mismatch

• Are the coordinates from a source that uses a local datum?
• Is your app assuming WGS 84 while the source uses another datum?
• If using GIS software, did you assign the correct CRS to the data before you reproject it?

Symptom: consistent offset (e.g., always shifted northeast by a similar distance).

2) Latitude/longitude swapped

• Many systems expect lat, lon, but some APIs and file formats use lon, lat (common in GeoJSON).

Symptom: the point appears in a completely different region, often with the numbers still “looking plausible.”

// GeoJSON coordinate order example (lon, lat): [-122.084000, 37.421998]

3) Wrong hemisphere or missing sign

• A missing minus sign can move a point across the equator or prime meridian.
• Confusing E/W or N/S can mirror the location to the other side of the world.

Symptom: the point is far away, often roughly mirrored.

4) Rounding or truncation

• Too few decimal places in decimal degrees reduces positional detail.
• Copying coordinates from a screenshot can drop digits.

Rule of thumb: more decimals generally means finer resolution. If you need meter-level detail, keep enough digits to avoid unnecessary rounding.

5) Mixed formats (DD vs DMM vs DMS)

• Entering 37 25.3199 as if it were decimal degrees (DD) instead of degrees and minutes (DMM) will produce a wrong location.
• Check whether the app expects symbols like ° and ', or expects a specific input pattern.

Symptom: the point is off by a noticeable but not global distance, sometimes tens of kilometers.

6) Map pin vs. place label ambiguity

• Some apps show a place label (e.g., a park name) whose centroid differs from the specific coordinate you intended.
• Geocoding may return a default point for an address range rather than the exact entrance.

Symptom: the pin is “in the right area” but not at the exact feature.

7) GPS drift and multipath at the moment of capture

• If you recorded coordinates next to tall buildings, under trees, or near reflective surfaces, your fix may be biased.
• Try recording again in a more open spot, or average multiple readings over time.

Symptom: repeated readings vary, and the offset changes depending on where you stand or how you hold the device.