When a Garmin handheld locks position in twelve seconds under a forest canopy, that fix is the work of roughly 130 satellites operated by four governments who do not always agree on much else. Receivers built in the last five years routinely listen to all of them at once. Two audiences should care equally about what follows, for different reasons. The prepared individual carries gear that needs to work when the cell network is down and the road signs are gone. The emergency manager coordinates responders from outside the affected jurisdiction who do not know the local landmarks, working off maps that may not match what is on the ground. Both groups end up dependent on the same physics. Both need to understand the settings.

Why There Is More Than One System

The United States built GPS for the Department of Defense in the 1970s and opened it to civilians in stages through the 1990s. Every other major constellation that followed was built for the same reason. A nation that depends on a foreign navigation signal for its military, its banking timestamps, its power grid synchronization, and its emergency services has handed control of critical infrastructure to a government it cannot vote out. Russia, the European Union, China, India, and Japan each reached the same conclusion and built their own.

The civilian payoff is that a modern receiver picking up signals from multiple constellations sees more satellites at any given moment, gets a position fix faster, and stays locked under tree cover, in urban canyons, and at high latitudes where any single system thins out. The four global systems combined put roughly 130 active satellites overhead at all times.

The Four Global Systems

GPS (United States)

GPS, the Global Positioning System, is operated by the U.S. Space Force out of the 2nd Space Operations Squadron at Schriever Space Force Base, Colorado. The constellation reached full operational capability in July 1995 and remains the reference standard against which the others are measured. As of early 2026, approximately 31 active GPS satellites orbit in six planes at 20,180 km altitude. The original design called for 24; the extras provide redundancy and improved geometry.

GPS broadcasts on multiple frequencies. The two that civilians and consumer devices care about are L1 at 1575.42 MHz, which every receiver since the 1990s can hear, and L5 at 1176.45 MHz, the newer high-precision signal added with the GPS III generation. L5 is the band that makes dual-frequency receivers possible in consumer hardware. The current modernization program is rolling out GPS III satellites with stronger signals, better atomic clocks, and the M-code military signal. The follow-on GPS IIIF series begins launching in the late 2020s.

GLONASS (Russia)

GLONASS, the Globalnaya Navigatsionnaya Sputnikovaya Sistema, is operated by Roscosmos and the Russian Aerospace Forces. The Soviet Union began launching GLONASS in 1982 and the system reached full constellation status in December 1995, months after GPS. The constellation collapsed during the post-Soviet financial collapse, was rebuilt in the 2000s, and now flies 24 operational satellites in three orbital planes at 19,130 kilometers.

GLONASS uses a different signal scheme than GPS. Where GPS satellites all transmit on the same frequencies and identify themselves with unique codes (CDMA), legacy GLONASS satellites transmit on slightly different frequencies and identify themselves by which frequency they use (FDMA). Newer GLONASS-K satellites are adding CDMA signals to improve interoperability with the other systems.

The system’s practical strength is high-latitude performance. GLONASS maintains stronger signal stability in northern regions such as Siberia or the Arctic thanks to a unique orbital configuration. That translates to better performance in Alaska, in northern Canada, and in Scandinavia than GPS alone provides, which is the reason GLONASS shows up in serious outdoor receivers even outside Russia.

Galileo (European Union)

Galileo is operated by the European Union Agency for the Space Programme with infrastructure built by the European Space Agency. It began offering initial services in December 2016 and has been declared operational since 2022. The constellation will consist of 30 satellites (27 operational and 3 spares) in three orbital planes at an altitude of 23,222 kilometers. As of early 2026, roughly 28 satellites are launched with 22 to 24 usable at any given time.

Galileo’s headline feature is accuracy. The system was built with newer atomic clocks and modern signal designs from the start, and it broadcasts dual-frequency signals (E1 at 1575.42 MHz and E5 at 1176.45 MHz) that overlap with GPS L1 and L5 by deliberate design. This frequency overlap is what lets a single chip in a consumer device receive both systems with one antenna. Galileo’s Open Service typically delivers better than 1-meter accuracy in good conditions.

Galileo also carries a Search and Rescue payload. Every operational Galileo satellite relays distress beacons from 406 MHz EPIRBs and PLBs to ground stations, and uniquely among GNSS systems, Galileo can broadcast an acknowledgment back to the beacon so the person in distress knows the signal got through.

BeiDou (China)

BeiDou, named after the Chinese term for the Big Dipper, is operated by the China Satellite Navigation Office. Unlike the other three, BeiDou was built in three generations. BeiDou-1 was a small regional system, decommissioned in 2012. BeiDou-2 added regional Asia-Pacific coverage. Fully operational since 2020, BeiDou consists of 35 satellites in a hybrid configuration that none of the other systems use: 27 in medium Earth orbit at 21,528 kilometers, 3 in geostationary orbit, and 5 in inclined geosynchronous orbit.

The geostationary and inclined satellites are what give BeiDou unusually strong performance over China and the Asia-Pacific region. They also enable a feature no other GNSS offers: short message communication. BeiDou receivers in China can send and receive text messages of up to 1,200 characters through the constellation itself, with no cellular network required.

For civilian receivers outside China, BeiDou contributes additional satellites for position fixing and is fully interoperable with the other three systems through shared L1/L5 frequency bands.

The Regional Systems

Two countries built navigation systems that cover their own region rather than the entire globe. Both are designed to augment GPS rather than replace it.

QZSS (Japan)

The Quasi-Zenith Satellite System, branded Michibiki, is operated by Japan’s Cabinet Office and reached operational status on November 1, 2018. QZSS currently flies four satellites with a target of seven, in highly inclined geosynchronous orbits between roughly 32,000 and 40,000 kilometers. The orbits are designed so that one satellite is always nearly directly overhead Japan, which is the “quasi-zenith” the system is named for. That overhead geometry is what makes QZSS valuable in Tokyo’s dense urban canyons where GPS satellites lower on the horizon get blocked by skyscrapers. QZSS uses GPS-compatible frequencies and is treated by most modern receivers as additional GPS satellites.

NavIC (India)

NavIC, the Navigation with Indian Constellation, is operated by the Indian Space Research Organisation. The system covers India and a region extending roughly 930 miles (1,500 km) beyond its borders. NavIC was conceived after the 1999 Kargil War, when the United States denied India access to selective GPS data during military operations in high-altitude terrain. India concluded it could not afford that dependence and authorized the program in 2006.

The original constellation called for seven satellites: three in geostationary orbit and four in inclined geosynchronous orbit. As of mid-2026, NavIC is operating below design strength following a series of atomic clock failures. ISRO confirmed on March 13, 2026 that the atomic clock aboard the IRNSS-1F satellite had stopped functioning, dropping NavIC to just three operational satellites, below the minimum of four required for reliable, continuous regional navigation coverage. Replacement satellites NVS-03, NVS-04, and NVS-05 are scheduled for launch over the following 15 to 18 months. The second-generation NVS series adds an L1 signal that consumer receivers can use, which is why some smartphones now list NavIC as a supported system.

How Receivers Actually Use This

A modern GNSS receiver is not switching between systems. It listens to all of them at once and treats every visible satellite as another data point in a least-squares position calculation. The math does not care which government launched a particular satellite, only how precisely its signal can be measured and how well its orbital position is known.

Single-Constellation vs Multi-Constellation

An older or budget receiver, including most automotive GPS units sold before 2015 and basic fitness trackers, listens to GPS only. This works fine in open country but degrades quickly under tree cover, near tall buildings, in deep valleys, or in any environment where the sky view is restricted. The receiver needs at least four satellites for a 3D fix and noticeably more for good accuracy.

A multi-constellation receiver expands the pool. With GPS, GLONASS, Galileo, and BeiDou all available, the receiver typically has 20 or more satellites to choose from and can reject the ones with poor geometry, weak signal, or known errors. This produces faster cold-start times, better accuracy in degraded environments, and more stable tracks.

Single-Frequency vs Multi-Frequency

The other axis is frequency. The ionosphere bends GNSS signals slightly as they pass through, and that bending changes with the sun’s activity. A single-frequency receiver, listening on L1 only, has to estimate the ionospheric delay using a model and accepts a few meters of unavoidable error. A multi-frequency receiver listens on L1 and L5 simultaneously, measures how differently the two frequencies were delayed, and solves the ionospheric error directly. The result is sub-meter accuracy on hardware that is now affordable in consumer watches and handhelds.

SBAS: The Setting Called “WAAS/EGNOS” on Your Garmin

Open the System menu on any Garmin handheld and you will find a setting called WAAS/EGNOS. Most users leave it on permanently or turn it off based on bad forum advice. Neither is necessarily the right call. The setting is short for Satellite-Based Augmentation System (SBAS), and it does something specific worth understanding before you choose.

SBAS is a layer of regional accuracy improvement that sits on top of the four global constellations. A network of ground reference stations in a specific region (North America, Europe, India, Japan, etc.) precisely measures the position errors in the GPS satellite signals they receive, computes correction data, uplinks that data to a geostationary satellite parked over the region, and that geostationary satellite broadcasts the corrections back down on a GPS-compatible frequency. A receiver that listens for the SBAS signal can apply the corrections in real time and reduce its position error from roughly 10 to 15 feet down to roughly 10 feet or better. SBAS also adds an integrity component: if one of the GPS satellites starts broadcasting bad data, SBAS notifies receivers within six seconds so they stop trusting that satellite.

SBAS was built primarily for aviation. The FAA developed WAAS to let aircraft fly GPS-based instrument approaches without ground equipment at every airport, and similar systems were built by the equivalent civil aviation authorities in Europe (EGNOS), India (GAGAN), Japan (MSAS), and others. Maritime, surveying, and recreational users get the benefit for free because the satellites broadcast on frequencies the same GPS antenna already receives.

The Global SBAS Network

The systems are interoperable by international agreement: a receiver that supports any one of them generally supports all of them, and travelers crossing between regions get whichever one is overhead. Garmin labels the menu setting “WAAS/EGNOS” because those were the first two systems online and because most Garmin customers operate in North America or Europe, but the same setting enables GAGAN reception in India, SouthPAN reception in Australia, and so on.

When to Turn It On, When to Turn It Off

The default Garmin behavior is to leave SBAS enabled, and for most users in North America or Europe that is correct. Two situations argue for turning it off.

Situation 1: You are outside any SBAS coverage area. If you are operating in central Africa, central South America, the open Pacific, or most of the Southern Hemisphere away from Australia/New Zealand, no SBAS signal is reaching your receiver. The unit still uses CPU cycles searching for the SBAS satellite, which costs a small amount of battery for zero benefit. Turning the setting off in those areas saves battery without sacrificing accuracy.

Situation 2: You have heavy obstructions overhead. SBAS corrections come from geostationary satellites parked over the equator. In the continental United States, that means the SBAS satellite sits roughly 30 to 45 degrees above the southern horizon. A receiver in a deep canyon, dense forest, or urban environment may have a fine view of GPS satellites passing overhead but no view at all of the southern sky where the SBAS satellite lives. Some receivers will burn battery hunting for an SBAS signal that geometry guarantees they cannot see. If you are operating consistently in heavily obstructed terrain and your handheld supports it, disabling SBAS can stabilize the fix and save battery.

For all other situations, leave it on. The accuracy improvement is real (typically 1 to 3 feet on a handheld in open country), the integrity warning system is a genuine safety feature, and the battery cost on a modern receiver is small.

What Garmin Actually Does

Garmin’s handheld and wearable devices have used multi-constellation receivers for years, but their settings menus expose the trade-offs to the user, which is unusual and worth understanding. Most Garmin watches track multiple satellites within GNSS and refer to this as “all systems”. Current Garmin outdoor watches and handhelds typically offer four GNSS modes:

• GPS Only. Listens to GPS L1 only. Maximum battery life, adequate accuracy in open country.
• All Systems. Uses GPS, GLONASS, and Galileo, with BeiDou and QZSS added on most current models. Processing signals from multiple frequencies requires more power, which can reduce battery life by 20 to 40 percent compared to single-band GNSS.
• All + Multi-Band. Adds L5 dual-frequency reception. Best raw accuracy, highest battery drain.
• SatIQ (AutoSelect). Lets the device decide which mode to use based on signal conditions. Newer Garmins have spare processing power to determine a confidence score for each satellite based on the discrepancy between distances reported by the two bands, and switches modes accordingly.

Garmin’s marine and aviation gear (chartplotters, the MSC 10 satellite compass, the GPS 24xd sensor) runs full multi-band, multi-constellation as standard. There is no battery budget to protect on a 12-volt boat or aircraft bus.

The Military Inheritance: Signals, Restrictions, and Accuracy

GPS was built for the U.S. Department of Defense. The civilian signal that consumer hardware uses is the second product of that system, not the first. Understanding what the military gets, what civilians get, and how the gap has changed over time matters because it determines what could happen to civilian positioning during a future conflict, and it explains why the gear most readers carry is suddenly capable of accuracy that used to require federal credentials.

The Signal Stack: What Each Frequency Carries

Every GPS satellite transmits on three L-band radio frequencies. Each frequency carries multiple coded signals layered on top of each other using a technique called code-division multiple access, so a single antenna can receive several signals at once and separate them by their distinct codes.

The other three global constellations follow similar patterns, with their own band designations and their own civilian-restricted signal splits. Each system reserves part of its signal stack for its operator’s military and authorized partners; only the names and policies differ.

GLONASS (Russia)

Legacy GLONASS used frequency-division multiple access (FDMA), assigning each satellite a slightly different frequency rather than a unique code. Modernized GLONASS-K satellites add code-division (CDMA) signals on G1, G2, and G3 to improve interoperability with the other constellations.

Galileo (European Union)

Galileo is the only major constellation built as a civilian system. Its restricted Public Regulated Service (PRS) is not operated by a single military; access is granted to EU member state governments, emergency services, and selected critical infrastructure operators on a national basis.

BeiDou (China)

BeiDou’s deliberate frequency overlap with GPS L1 and L5 (on B1C and B2a) is part of the international compatibility framework that allows a single consumer chipset to receive all four constellations on the same antenna. The authorized-user signals are operated by the People’s Liberation Army.

The pattern across all four global constellations is consistent: open civilian signals on bands designed for international interoperability, restricted higher-accuracy and anti-jam signals on overlapping bands reserved for the operator’s military or government users. The civilian-military signal split is not unique to GPS; it is how every operator of a global navigation system has chosen to manage the tension between commercial value and military security.

The Original Civilian Handicap: Selective Availability

From the time civilian use of GPS opened in the early 1990s until May 2000, the Department of Defense deliberately degraded the civilian signal. The technique was called Selective Availability, and it injected pseudo-random timing errors into the C/A code that propagated into the receiver’s calculated position. Typical SA errors were about 164 feet horizontally and 328 feet vertically, with the error pattern changing constantly so receivers could not average it out over short observation windows. The accuracy denial was global, not selective by user or region. Every civilian receiver in the world, military allies included, saw the same degraded signal.

The civilian accuracy with SA active was good enough for car navigation and recreational hiking but useless for survey work, precision agriculture, or aviation approach guidance. An entire industry grew up to defeat SA using ground reference stations transmitting real-time corrections, a technique called differential GPS or DGPS, which became the standard for surveying and Coast Guard maritime navigation throughout the 1990s.

The 2000 Decision

President Clinton ordered Selective Availability turned off at midnight on May 1, 2000. The change happened simultaneously across the entire constellation, and civilian receiver accuracy improved overnight from roughly 330 feet to roughly 30 to 65 feet without any hardware changes. The decision was driven by three factors. First, DGPS had already neutralized SA for any user willing to pay for correction data, so the military restriction was hurting unauthorized adversaries less and less while imposing real costs on legitimate civilian users. Second, civilian GPS had become economically critical to U.S. and allied economies in ways the 1980s designers had not anticipated. Third, the military had developed what it called regional denial capability, the ability to jam or spoof civilian GPS signals over a specific battlefield without globally degrading the system.

In September 2007 the United States announced that all future GPS satellites (the GPS III generation) would be built without SA capability at all. The 2000 policy decision was made permanent by engineering choice. SA is not coming back.

What Replaced Global Denial: Regional Jamming and Spoofing

What did come back, and what every modern operator should plan around, is local interference. The military capabilities that allowed SA’s retirement are real and have been demonstrated repeatedly since 2000. Two techniques matter to civilians:

• Jamming broadcasts noise on the GPS frequencies in a localized area, drowning out the satellite signal so civilian receivers in that area lose their fix. Russia has deployed jamming routinely in eastern Ukraine and the Black Sea since 2014. The North Atlantic has seen intermittent jamming incidents attributed to military exercises. Civilian aircraft over conflict zones lose GPS regularly.
• Spoofing broadcasts fake GPS signals that overpower the real ones, causing receivers to compute a wrong position without realizing anything is wrong. A spoofed receiver can be made to think it is in Moscow when it is actually in Helsinki. This has been demonstrated against commercial shipping in the Black Sea, against ride-sharing apps in Moscow, and against military and civilian aviation in multiple theaters.

Neither jamming nor spoofing is a U.S. monopoly. China, Russia, Iran, North Korea, and several non-state actors all have demonstrated GPS interference capability. The practical implication is that during a regional conflict or major incident, civilian GPS may be unreliable or actively dangerous in the affected area regardless of which government is responsible. Multi-constellation receivers help because jamming one frequency band does not necessarily affect all four constellations equally, but a determined adversary can jam everything at once if they are willing to dedicate the power.

How the Military Is More Accurate (And By How Much)

The military still has positioning advantages beyond what civilians can match, but the gap is smaller than it used to be. The traditional advantage was the P(Y) code on L1 and L2, which gave authorized receivers a precision signal that was both more accurate than C/A and resistant to spoofing because it was encrypted. The newer M-code, broadcast from GPS Block IIR-M satellites and later, replaces P(Y) for modern military gear and adds significantly stronger anti-jamming protection plus secure key management that makes spoofing impractical without the daily-rotated cryptographic keys.

The accuracy comparison today looks roughly like this:

Two surprising facts fall out of this table. First, a $400 dual-frequency Garmin watch with multi-band enabled is roughly as accurate as a military M-code receiver under normal conditions. The military’s edge is no longer raw accuracy in friendly territory. It is resilience against jamming and spoofing in contested territory, plus consistent performance when an adversary is actively trying to corrupt the signal. Second, survey-grade and precision-weapon accuracy both depend on additional information beyond the satellite signal itself: ground reference stations broadcasting corrections, inertial navigation systems filling in when satellite signals drop, or both. Neither is achievable from a satellite signal alone in any constellation.

The Third Service: Timing

Everything in this article so far has been about positioning. Position is what most users think GPS does. It is not what most GPS receivers in the world are actually used for. The acronym GNSS stands for Global Navigation Satellite System, but a more accurate description of the service is Position, Navigation, and Timing (PNT). The timing piece is hidden, invisible to the user, and economically larger than the positioning piece by every measure that has been studied.

Every GPS satellite carries multiple atomic clocks (cesium and rubidium standards) and broadcasts the current time stamped into every signal. A receiver that can see four or more satellites can solve for its own clock error along with its three position coordinates. Once that clock error is known, the receiver knows the absolute time to within tens of nanoseconds, anywhere on Earth, for free, continuously. There is no other practical way to get that level of time synchronization across a continent without GPS.

This matters because a long list of critical infrastructure systems quietly depend on it:

The 2016 GPS time anomaly illustrates the dependency. On January 26, 2016, an erroneous time correction broadcast from a single decommissioned GPS satellite propagated through ground systems and caused some GPS-disciplined clocks to jump backward by 13 microseconds. Thirteen microseconds is not a number most people can intuit. It was enough to disrupt some digital radio broadcasts, trigger fault alarms in cellular networks across multiple countries, cause some power grid monitoring equipment to flag spurious anomalies, and force the BBC to take some digital radio services off air. The whole event lasted about ten hours and was caused by a software issue, not an attack. A deliberate, sustained denial would have far more consequential effects.

How Your Cell Phone Is Different

A modern smartphone contains a GNSS chip that, on paper, looks similar to what is in a handheld. The hardware difference is that a phone’s GNSS antenna is a small ceramic patch crammed into a metal-bodied device designed to be held against a head. The handheld’s antenna is larger, better positioned, and built for sky view. The bigger difference is what the phone does to compensate for that compromised antenna, and the dependencies it introduces in the process.

The Four Things a Phone Combines

A phone’s reported location is not just GNSS. It is a fused estimate drawn from up to four sources, weighted by which ones are available and how confident the operating system is in each:

1. GNSS satellite signals. Same as a handheld, just with a worse antenna.
2. Assisted GPS (A-GPS). The phone downloads the current satellite almanac and ephemeris data over the cellular network instead of decoding it from the satellites themselves. This speeds up a cold start from several minutes to a few seconds. A-GPS requires a working cellular data connection to update. Cached almanac data is usable for a few hours to a few days, then degrades.
3. Cell tower positioning. The least accurate method, Cell ID, uses the known location of the single cell tower the phone is communicating with. Multilateration uses signal strength and timing from multiple adjacent cell towers to triangulate the phone’s position. Accuracy ranges from a few hundred meters in dense urban areas to several kilometers in rural areas with sparse tower spacing.
4. Wi-Fi positioning. Phones run a background service that constantly seeks Wi-Fi access points and sends Wi-Fi BSSID addresses along with their location identified through GPS or cell tower triangulation to Apple’s or Google’s servers, where they are stored in a database. The phone then identifies its location by detecting which Wi-Fi access points are nearby and looking them up in the database. Accuracy ranges from 10 to 25 meters in dense urban areas to 20 to 100 meters where access points are sparser.

What This Means When the Infrastructure Fails

The phone never tells you which source it is currently using. The “blue dot” on a map app could be a 3-meter GNSS fix, a 50-meter Wi-Fi estimate, or a 2-kilometer cell tower guess. The OS displays a confidence circle but most users never read it.

Coordinate Formats: Same Position, Different Strings

A latitude and longitude can be written several ways, and a position passed from one operator to another in the wrong format is one of the more common causes of search teams ending up in the wrong drainage. The position itself does not change. The way it is written does.

The following all describe the same point, the entrance to Codorus State Park in southern Pennsylvania:

The Three Lat/Long Variants

Decimal degrees, DMS, and DDM all express the same latitude and longitude, just sliced differently. Decimal degrees is the cleanest format for software. DMS is what is printed on every paper map you will pick up at a ranger station. DDM is the standard for aviation and maritime use because it splits the difference: still readable on paper, but the decimal portion makes interpolation easier than full seconds.

The conversion is mechanical. One degree contains 60 minutes; one minute contains 60 seconds. So 39.78250° equals 39 degrees plus 0.78250 of a degree, which is 0.78250 × 60 = 46.95 minutes, which is 46 minutes plus 0.95 × 60 = 57 seconds. Going the other way, take the seconds, divide by 60, add the minutes, divide by 60, add the degrees. Most handheld GPS units convert between these three formats automatically through a menu setting.

Signed vs Hemisphere Notation

Each of the three lat/long formats can also be written two different ways depending on how the hemisphere is indicated. Both ways describe the same point. Mixing them up silently breaks software that expects one or the other.

The hemisphere-letter convention is what you see on printed maps, nautical charts, and aviation plates. The signed convention is what APIs, GIS software, mapping JavaScript libraries, and most programming languages use, because a single number with a sign is easier to compute against than a number plus a letter that has to be parsed. Positive latitude is north, negative is south. Positive longitude is east, negative is west. The continental United States is entirely positive latitude (north of the equator) and entirely negative longitude (west of the prime meridian), so most U.S. coordinates in signed format have a leading minus on the longitude.

The trap is the silent failure mode. A coordinate copied as 39.78250, 76.92806 (no minus sign on the longitude) and pasted into Google Maps will plot in central China rather than southern Pennsylvania. The number is “right” but the hemisphere is missing. The same coordinate written as 39.78250 N, 76.92806 W has the hemisphere stated explicitly and is unambiguous. When in doubt, write the hemisphere letter. When ingesting coordinates from software, confirm the signed convention is correct.

UTM, MGRS, and USNG

These three are grid-based rather than angular. The Universal Transverse Mercator system divides the world into 60 north-south zones, projects each zone flat, and assigns coordinates in meters east and meters north from a fixed origin. The result is that distances on the grid behave like distances on a sheet of paper: you can measure them with a ruler, and one kilometer east is one kilometer east regardless of where you are in the zone.

MGRS, the Military Grid Reference System, is UTM with the verbose easting and northing replaced by a compact grid square designator and shortened coordinate digits. USNG, the United States National Grid, is functionally identical to MGRS and was adopted as the FGDC standard for domestic incident response. FEMA, state emergency management agencies, and US&R task forces use USNG/MGRS because it eliminates the decimal-point confusion of lat/long formats and gives a precision indicator built into the string itself: more digits means tighter precision, in clean factors of ten.

USNG strings have a built-in precision indicator: more digits means tighter precision, in clean factors of ten. You can clip the right end of a coordinate to deliberately reduce precision and the string still parses cleanly.

This precision-by-digits feature is one of the reasons USNG is the preferred format for incident response. A dispatcher who needs to call out a 1-kilometer grid square (about 0.62 miles on a side) for a search team gives them just the first eight characters. A team member at the search area can radio back a 10-meter precision (about 33-foot) refinement using fourteen characters. No conversion, no datum recalculation, just more digits.

The Reality Gap: USNG Doctrine vs. Lat/Long Practice

The previous sections describe what FEMA, federal US&R task forces, and the National Incident Management System doctrine prescribe. USNG and MGRS are the official ground coordinate standard for federal-led incident response, and have been since FGDC adopted USNG as a federal standard in 2001. That is one half of the picture.

The other half is that nearly everyone who is not a federal responder thinks, speaks, and types in lat/long. A 911 caller reads coordinates off their smartphone’s lock screen in decimal degrees. A local sheriff’s deputy enters a position into the CAD system in DMS. A hunter calling in a missing party uses their handheld GPS’s default DDM. A drone operator over the search area transmits telemetry in signed decimal degrees. The civilian world, the local response world, and the consumer-electronics world all run on lat/long. The federal-grid world runs on USNG. When the two meet, somebody has to convert.

The conversion is not trivial. There is no mental shortcut between a decimal-degree pair and a USNG grid string. The math involves a Transverse Mercator projection, zone determination, and easting/northing calculation that fills several textbook pages. In practice, the conversion is done one of three ways:

• By software. NOAA’s online converter, the FCC’s coordinate tool, FEMA’s USNG center, Avenza Maps, CalTopo, Gaia GPS, and dozens of other tools convert between formats instantly. All of them require a working internet connection, a working device, or a pre-loaded offline application.
• By handheld GPS. A Garmin handheld set to “Position Format: USNG” will display the current location in USNG regardless of the source data. You can also enter a waypoint in any supported format and the GPS will display its USNG equivalent. This works without internet but requires the handheld.
• By laminated conversion card or paper lookup. Some EOCs and SAR teams print conversion reference cards for their AO. This is the analog fallback when the device fails or the internet is down.

Maidenhead Grid Locator

The Maidenhead system was designed in 1980 specifically for amateur radio. It carves the globe into 324 large fields (two letters, A through R), each subdivided into 100 squares (two digits, 0 through 9), each subdivided into 576 subsquares (two letters, a through x). The whole locator is six characters and identifies a roughly 1.6 by 3.1 mile rectangle on the ground (about 2.5 by 5 km).

Maidenhead is built around the needs of HF and VHF/UHF operators. It compresses a position into something easily exchanged over a noisy voice or CW contact, it works as a contest scoring unit, and it directly supports beam heading and great-circle distance calculations between stations. Most amateur logging software, every modern contest log, and every HF propagation prediction tool accepts Maidenhead natively.

The eastern United States covers a handful of Maidenhead fields. EN covers the upper Midwest, FN covers the northeast, FM covers the mid-Atlantic, EM covers the southern Plains, EL covers the Gulf Coast. South-central Pennsylvania sits in FM19. A six-character locator like FM19fs pins a station down to within a couple of kilometers, which is enough resolution for almost any amateur radio purpose. For ARES, RACES, and ACS operators supporting emergency management, Maidenhead is also the natural way to report a deployed station’s location when checking into a regional net.

Bearings: Degrees, Magnetic, Mils

A position is a point. A bearing is a direction. The two settings are separate on a GPS, and the bearing setting is where mils show up.

True, Magnetic, and Grid North

“North” sounds like a single direction. On a GPS, on a paper map, and in a compass, it can actually mean three different things. Confusing them causes some of the most consistent navigation errors in both recreational and emergency operations.

True north is geographic. It points to the rotational North Pole, the fixed point at the top of the planet’s axis. Lines of longitude on every map converge to true north. Astronomical observations (Polaris, sun shadows) reference true north. Aviation, marine navigation, and survey work all use true north as the primary reference because it is the only one of the three that does not drift over time.

Magnetic north is what a compass needle points to. It is the location where Earth’s magnetic field lines converge into the planet, which currently sits in the Arctic Ocean north of Canada (it has been drifting toward Siberia at roughly 30 miles per year for the past two decades). Magnetic north and true north are not the same place, and the difference between them, measured from your specific location, is called magnetic declination (nautical charts call it magnetic variation, but it is the same thing).

Grid north is what UTM, MGRS, and USNG grids point to. Because flat map grids cannot perfectly represent a curved Earth, the grid lines on a UTM-projected map align to true north only along the central meridian of each UTM zone. Everywhere else in the zone, grid north tilts slightly east or west of true north by an amount called grid convergence. In the continental United States, grid convergence is usually less than 2 degrees, small enough that most ground operations ignore it. Aviation, precision survey work, and any operation crossing a UTM zone boundary cannot ignore it.

Declination Varies by Location and Drifts Over Time

Declination is not a single number you memorize. It depends on where you are standing, and it shifts measurably over years as Earth’s magnetic field moves. In 2026, declination across the continental United States runs from roughly 17 degrees west on the coast of Maine to roughly 15 degrees east in northern Washington state. Somewhere in between is a north-south curve called the agonic line where declination is zero, and a compass points to true north on its own. The agonic line currently runs roughly through eastern Tennessee, central Kentucky, and the eastern edge of Wisconsin, and it is drifting westward at roughly 10 to 12 miles per year.

That movement matters operationally. A spot in central Pennsylvania that read 11 degrees west declination in 1980 reads only about 3 degrees west today, because the agonic line has been migrating eastward across the state. A spot in eastern Tennessee that read 1 degree west in 1980 reads zero declination today. The compass in your kit has not changed. The map you bought in 1990 has the old value printed on it. Trusting that printed value uncritically is exactly how a navigation error enters.

Practical implications:

• USGS topographic maps print the declination at the time the map was published in the margin, along with the date. If the map is more than ten years old, the declination value is stale. Check NOAA’s National Centers for Environmental Information (NCEI) magnetic field calculator for your area before you trust it.
• GPS receivers compute current declination automatically using an internal model (the World Magnetic Model, updated every five years by NOAA and the UK Defence Geographic Centre). When set to “magnetic,” they apply the correct local declination to whatever bearing they display. This is one of the few cases where the GPS is more reliable than a printed reference.
• Aviation sectional charts show isogonic lines (lines of equal declination) so pilots can interpolate the local value visually. Marine charts do the same. Land navigation maps usually do not.
• The agonic line is moving. The line of zero declination is currently drifting west across the United States at roughly 10 to 12 miles per year. Locations that read east-of-true today may read zero in a decade and west-of-true in two decades. Operators working consistently in one area get used to a local rule of thumb; that rule of thumb is correct on a given date and slightly wrong everywhere else. An operator who learned their craft in eastern Colorado and deploys to eastern Pennsylvania has to flip not just the magnitude of declination but the sign.

True vs Magnetic: Which Should Your GPS Display

The right setting depends on what you are doing and who you are coordinating with.

• Land navigation with a paper map and compass: magnetic, because that is what your compass reads. The map’s marginalia will tell you the declination so you can convert when working between map and compass.
• Coordinating with an aviator: true, because aviation runs on true bearings with magnetic noted separately on the chart. Helicopters supporting SAR, medevac, and fire attack expect true bearings.
• Calling artillery or working with the National Guard: depends on the unit’s doctrine, but increasingly true with magnetic conversion done at the gun line. Confirm before you transmit.
• Generic GPS use with no compass involved: true. It is the universal reference that does not drift, and it is what most digital mapping software uses by default.

Degrees vs Mils

The degree is the familiar unit, 360 to a full circle. The mil is an angular measurement built for precision work at distance. The geometric definition is straightforward: one mil is the angle that subtends one unit of width at a thousand units of range. A target that appears one mil wide at a range of 1,000 yards is one yard wide (and a target one mil wide at 1,000 meters is one meter wide). The math works in any unit so long as you keep range and target width in the same unit. The arithmetic for ranging and adjustment becomes trivial, which is the whole reason artillery, snipers, and mortar crews use mils.

The complication is that there are several competing definitions of “one mil” in use:

The practical takeaway is that a Garmin handheld set to mils is almost certainly displaying NATO mils. A user trained on a Russian or former Soviet system expecting 6,000 mils to the circle will get bearings that are wrong by about 6.7 percent. Confirm which system you are using before passing bearings between units that might be on different references.

Altitude: The Third Coordinate

Latitude and longitude describe where you are on the surface. Altitude describes how high. Most ground users glance at the altitude field on their GPS once and never think about it again. For any operation that involves a helicopter, a drone, an aircraft drop, or a tall structure, altitude is as critical as horizontal position, and there are three completely different numbers that all get called “altitude,” “elevation,” or “height” depending on who you are talking to.

The Three Heights

Why the Ellipsoid and Sea Level Differ

This is the part that confuses everyone first. GPS satellites compute position relative to the WGS84 ellipsoid, a mathematically smooth football-shape that approximates the planet. Mean sea level is defined by Earth’s gravity field, which is irregular because the planet’s mass is unevenly distributed. The result is that sea level and the ellipsoid do not match. In the continental United States, mean sea level sits between 30 and 110 feet below the WGS84 ellipsoid, varying by location.

The difference is called the geoid separation. Modern GPS receivers store a model of the geoid (typically EGM96 or EGM2008) and automatically subtract the local geoid separation from the raw GPS height to display orthometric (MSL) elevation. The setting is usually buried in the GPS menu under something like “Altitude Reference” or “Elevation Source.” Most consumer handhelds default to MSL because that is what users expect. Some surveying and aviation units default to ellipsoid height because that is what their downstream software expects. Check the setting before you trust the number.

Why This Matters for Helicopter Operations

Helicopter pilots care about AGL for terrain clearance, obstacle avoidance, hoist operations, and landing zone selection. Aviation altimeters traditionally read pressure altitude (corrected to MSL when the pilot inputs the local barometric pressure), so the cockpit indication is MSL by default. The pilot mentally converts to AGL by subtracting the terrain elevation, or by looking out the window. A radar altimeter reads true AGL directly but only works close to the ground.

The friction point arrives when a ground operator passes an “altitude” or “elevation” to a helicopter without specifying which reference. A SAR ground team reporting a patient’s position at “elevation 1,200 feet” almost certainly means MSL (off their topographic map or GPS). A drone operator reporting “altitude 400 feet” almost certainly means AGL (because that is the FAA Part 107 ceiling and the number their controller displays). A surveyor reporting “height 540 feet” might mean ellipsoid, MSL, or local datum, depending on their equipment configuration. Same word, three references, three operationally different numbers.

How Accurate Is GPS Altitude?

GPS altitude is consistently less accurate than GPS horizontal position, typically by a factor of 1.5 to 3. The geometric reason is that the satellites overhead are all on the same side of the receiver (above), so the vertical component of the position fix has weaker geometry than the horizontal. A handheld that reports horizontal position to within 10 feet is probably reporting altitude to within 20 to 30 feet.

Other factors degrade GPS altitude further. Weather and atmospheric pressure changes do not affect GPS altitude readings (unlike a barometric altimeter, which they do affect), but ionospheric and tropospheric delays add altitude error in single-frequency receivers. Dual-frequency multi-band receivers (L1+L5) cut vertical error substantially, which is one reason aviation and survey gear has standardized on multi-band.

For most ground operations, GPS altitude is good enough to know which side of a ridge you are on and which contour interval you are within. For helicopter operations, drone deconfliction, or any work where vertical separation matters, GPS altitude alone is not sufficient. Pressure altimetry, radar altimetry, or terrain databases need to be in the loop.

Barometer Mode: The Setting Most Users Get Wrong

A Garmin GPSMAP 64st (and most current Garmin handhelds and outdoor watches) carries two completely independent altitude sensors. The GPS receiver computes vertical position from satellite geometry. The barometric altimeter measures atmospheric pressure and infers elevation from it. The two measurements have different strengths and different failure modes, and the device gives you three modes for deciding which to trust:

The failure modes match the modes:

• Fixed Elevation while moving: the device interprets every altitude change as a weather change, the displayed elevation stays wrong, and the pressure graph becomes meaningless. Easy mistake when you set up camp the night before, configure Fixed Elevation for weather watching, and forget to switch it back before you break camp.
• Variable Elevation at a fixed station: the device assumes every pressure change is you moving up or down, so it adjusts the displayed elevation when really it should be holding still and warning you that pressure is dropping. The weather forecasting capability is lost.
• Auto Calibration in a canyon or under dense canopy: GPS vertical accuracy degrades when sky view is restricted, and the barometer inherits whatever errors the GPS is feeding it. The reading can wander by 30 to 50 feet without warning. Auto Calibration assumes the GPS reference is trustworthy.

The Weather Forecasting Application

Most users set Variable Elevation once and never touch it. They miss the most useful feature of having a barometric altimeter at all. With the device in Fixed Elevation mode at a stationary position, the pressure trend graph on a Garmin GPSMAP 64st becomes a short-term weather forecaster that works without cell service, without internet, without any forecast feed at all.

• Steady or rising pressure means stable weather is in place or coming. Generally good conditions for the next several hours.
• Slowly falling pressure (1 to 3 millibars over several hours) suggests a weather system is approaching. Plan for clouds, possibly precipitation, within 12 to 24 hours.
• Rapidly falling pressure (3+ millibars per hour) is a serious storm signal. Severe weather is likely within hours, not days. Get to shelter, secure gear, finish the operation.
• Pressure rising after a fall indicates a front has passed and conditions are improving.

This is field tradecraft that predates GPS by a century and still works when nothing else does. The marine community uses it constantly. The aviation community builds careers on it. Land-based preppers and emergency managers tend to forget it exists.

The barometer mode also interacts with the elevation reference setting (HAE vs MSL) discussed earlier. Both the barometric altimeter and the GPS altitude can be displayed as either ellipsoid height or orthometric height, and the device applies the conversion regardless of which sensor is producing the reading. Set MSL once at the device level and both sensors report in the same units.

The Casio Pathfinder Trap: Manual Declination Devices

A GPS-equipped device knows its current latitude and longitude and can look up the correct local declination from the World Magnetic Model on the fly. A device without GPS cannot. Anything with a magnetometer (electronic compass) but no GPS receiver depends on the user to enter the declination value manually, and to update it when they travel or when years pass. This setting lives in a submenu most users open exactly once, on the day they buy the device, and never look at again.

The Failure Mode, Visualized

The Common Manual-Declination Devices

The failure mode is consistent across all of these. The watch tells the user exactly what it always tells them. The math the watch is doing is exactly what they programmed it to do. The setting is just wrong for where they are standing. There is no error indicator, no warning beep, no red text on the display, because nothing is wrong from the watch’s point of view. It is doing its job.

The same trap applies to baseplate compasses. The declination screw on a Suunto MC-2 set for Pennsylvania will silently produce bad bearings the moment its user crosses into a different declination zone. The compass is mechanically correct; the offset is wrong for the new location.

How to Avoid It

The Setting Almost No One Checks: Datum

The coordinate format determines how a position is written. The datum determines what the position actually refers to. Two GPS units displaying “the same coordinates” in different datums can be 80 meters apart in the eastern United States, hundreds of meters apart in the western United States, and farther still on older overseas maps. This is the setting that has stranded search teams in the wrong canyon, called air assets to grid squares hundreds of meters off the target, and put surveyors’ boundary markers in the neighbor’s yard.

A datum is a mathematical model of Earth’s shape and a defined origin from which coordinates are measured. Different datums use different ellipsoid models and different reference points, so the same physical spot gets slightly different coordinate values depending on which datum is in use. The values look almost identical to a casual reader. The ground difference is real.

What to Set on Your Handheld

Pull a new handheld GPS out of the box and the first menu it pushes you through is position format and datum. Most people accept the defaults without understanding the choice. By the end of this article, nine different settings determine whether the numbers on your screen mean anything to the person on the other end of the radio. The full settings checklist, then the use-case-specific configurations.

The Complete Settings Check

Every GPS-capable device in the household, the go-bag, the truck, the boat, and the EOC kit should have these nine settings verified. The exact menu paths differ by manufacturer, but every modern handheld and most current smartwatches expose all of them.

Once these settings are verified on one device, the same configuration should propagate to every other device in the same household, MAG, response team, or EOC kit. Settings drift is the friction that turns a coordinated team into one where the coordinates do not match.

Configuration by Use Case

General Outdoor Use: Hiking, Hunting, Camping

• Position format: Decimal degrees if you primarily use a phone for navigation, DDM if you work with maritime or aviation references, DMS if you regularly use paper USGS topos.
• Datum: WGS84.
• North reference: Magnetic if you carry a compass; true if you do not.
• Bearing units: Degrees.
• Altitude reference: MSL (matches topo maps and trail signs).
• Barometer mode: Variable Elevation while moving; switch to Fixed Elevation at camp to use the pressure trend for weather watching.
• GNSS mode: All Systems or SatIQ for battery balance; Multi-Band only when accuracy matters more than battery life.
• WAAS/EGNOS (SBAS): On in North America or Europe. Off if operating outside SBAS coverage areas to save battery.
• Declination: Auto on a Garmin handheld. Verify manually on a Casio Pathfinder or Suunto Vector for your current location.
• Time: 24-hour local clock; enable UTC display if your device supports it.

SAR Team Member, Wildland Firefighter, Disaster Response Volunteer

• Position format: USNG (set as “MGRS” on most Garmins; the strings are identical for civilian users).
• Datum: WGS84.
• North reference: True (matches aviation coordination).
• Bearing units: Degrees.
• Altitude reference: MSL for ground reporting; understand AGL for aviation handoffs (see Section 10).
• Barometer mode: Variable Elevation in the field; Fixed Elevation at staging or a fixed command post for weather indication.
• GNSS mode: Multi-Band when battery permits; otherwise All Systems.
• WAAS/EGNOS (SBAS): On. The accuracy gain and integrity alerts matter for incident response.
• Declination: Auto. Verify on any manual-declination backup device against current local value before deployment, especially for out-of-state mutual aid.
• Time: 24-hour UTC primary, local secondary. Match the incident communications plan.

Amateur Radio Operator

• Position format: Maidenhead Grid Locator if available on your device; otherwise decimal degrees for software logging conversion.
• Datum: WGS84.
• North reference: True (for beam heading calculations).
• Bearing units: Degrees.
• Altitude reference: MSL (for HF propagation prediction tools that need elevation).
• Barometer mode: Fixed Elevation at a home station; Variable Elevation for portable or rover work.
• GNSS mode: All Systems.
• WAAS/EGNOS (SBAS): On for any deployed mobile or portable operation.
• Declination: Auto on GPS-equipped devices.
• Time: UTC primary (every amateur log uses UTC); local secondary.

EOC, Dispatch, or Coordination Role

• Primary format: USNG for ground operations, DDM or decimal degrees for aviation and marine coordination, lat/long for mapping software ingest.
• Datum: WGS84, documented in the incident communications plan.
• Altitude reference: MSL throughout the IAP. AGL only where explicitly required for aviation deconfliction.
• Barometer mode: Field-deployed handhelds at fixed forward operating positions in Fixed Elevation mode for supplementary weather indication; mobile field teams in Variable Elevation.
• Time: UTC primary on all logs and forms; local time for public-facing messaging only.
• Display capability: Train dispatchers to convert between formats and to recognize when an inbound coordinate is in an unexpected format. Practice this before an incident.

One Family, One MAG, One Standard

The single highest-leverage habit a household, a mutual assistance group, or a small response team can build is to standardize all these settings across every device in the group. A family with five GPS-capable devices (two phones, a handheld, a watch, a car nav) should have one position format, one datum, one altitude reference, and one time format across all of them. A MAG with twelve members should have a one-page settings standard that every member configures on their gear before the next exercise. A volunteer response team should brief the settings standard at the start of every deployment.

The cost is zero. The payoff is that when a coordinate gets read off any device by any member of the team, it lands on a receiver that interprets it the same way. The drift that causes confusion happens when each operator runs their own gear on their own defaults.

The Bottom Line

The four global GNSS constellations and two regional augmentations represent decades of national investment by governments that often disagree on much else. The civilian payoff is that any modern receiver, properly configured, can compute its position to within a few meters anywhere on Earth using satellites from multiple nations simultaneously, with no fee and no infrastructure on the ground.

That payoff is conditional on the user understanding what the device is actually doing. The smartphone in your pocket and the handheld on your pack derive their positions through different paths with different dependencies and different failure modes. The coordinates on your screen mean nothing to the person on the other end of the radio unless both of you agree on the format and the datum. The bearing on your compass and the bearing on your GPS may not be the same number even when both are correct.

For the prepared individual, the takeaway is to carry a dedicated handheld that does not depend on cell infrastructure, configure it once with sensible defaults, and learn to read the screen. For the emergency manager, the takeaway is that the coordinate system used to plan a response must be documented, consistent, and unambiguous before the incident starts, because the personnel arriving from outside the jurisdiction will not have time to debug datum confusion when they are looking for a missing person or a staging area.

The satellites overhead are doing their part. The work that determines whether their signal saves a life sits in the settings menu and in the standard operating procedure.