About Location QR Codes
A street address describes a building; a pair of coordinates describes a point. That distinction is the entire reason this type exists separately from the Google Maps generator elsewhere on this site. A location QR code encodes a "geo:" link - a format defined in an actual internet standard (RFC 5870) specifically for representing geographic coordinates - carrying a latitude and longitude pair that most phones recognize natively and hand off to whichever mapping app is set as the default, pinning that exact point rather than a named address someone has to type, search for, or hope resolves correctly.
Because it deals in raw coordinates rather than a named place, it's precise down to an exact spot on the ground rather than a general building or block, which matters more than it might first seem. A street address can only point you at a building; it has no way to specify a particular trailhead deep inside a park, a specific meeting point somewhere within a sprawling festival ground with no addresses of its own, or a delivery entrance tucked around the back of a building that shares one street-facing address with several other doors. A hiking guide company might print this code at a trailhead with coordinates for a scenic overlook partway along the route, letting hikers navigate to that exact point rather than following a string of verbal landmarks that are easy to miss or misremember.
It's also the natural choice for places with no formal address at all - a campsite in a dispersed camping area, a specific rock formation popular with climbers, a buoy or GPS waypoint out on open water. Anywhere "there's no street address for this" is literally true, a geo link is often the only precise, shareable way to describe the location at all.
Getting the coordinate format right matters more than it might seem for something that looks like just two numbers. Latitude and longitude need to be expressed in decimal degrees - a format like 40.7484, -73.9857 - rather than the older degrees-minutes-seconds notation still used in some contexts, since most consumer mapping tools expect the decimal form and won't interpret the other correctly. Mixing up the order of latitude and longitude, or accidentally transposing a digit, is an easy and common mistake that silently points the pin somewhere else entirely - sometimes a few streets away, sometimes on the other side of the world if a sign gets flipped or a decimal point moves.
One genuine advantage of the geo URI format over a Google Maps-specific link is that it doesn't tie the destination to any one company's mapping service. Since it's an open, cross-platform standard rather than a link built around a particular app, a phone hands it off to whatever mapping app is already set as that user's default - Google Maps, Apple Maps, or something else entirely - rather than forcing everyone toward one specific provider regardless of what they'd normally use.
That same openness comes with a real tradeoff worth knowing about honestly: because a geo link carries nothing but coordinates, with no business name, no photos, no reviews, and no address for context, some mapping apps display little more than a bare pin with a set of numbers, rather than the rich business listing a Google Maps-specific link can surface. If what you actually want is a business's full profile - hours, photos, reviews - alongside directions, the Google Maps generator is the better tool for that job; reserve this type for situations where an exact, named-place-agnostic point genuinely is the goal.
Support for the geo scheme itself has historically been a little less consistent across every possible combination of phone, browser, and default map app than support for a plain web link, particularly in older software versions or less common browser and camera-app combinations. It's worth testing a generated code on a couple of different phones before relying on it for anything printed at scale, just to confirm it hands off cleanly to a mapping app rather than displaying as inert text on some devices.
There's essentially no privacy concern with sharing coordinates for a public place like a trailhead or a festival ground - but if the coordinates point at a private residence or a similarly sensitive location, treat that with the same judgment you'd apply to sharing any home address, since a geo link is exactly as precise and exactly as shareable as a house number, just formatted differently.
Finding accurate coordinates in the first place is usually the easiest part of the process, since most mapping apps let you drop a pin at a precise spot and read off its latitude and longitude directly - dropping the pin as close as possible to the actual point you mean, rather than an approximate spot nearby, is worth the extra minute it takes, since the entire value of this format over a plain address is exactly that precision.
Where this type isn't the ideal choice: any place that already has a clean, well-recognized street address and would benefit from the extra context - hours, reviews, photos - that a business-oriented mapping link can provide. A destination that's genuinely a business, rather than a bare point in the landscape, is usually better served by the Google Maps generator elsewhere on this site, which surfaces that richer information alongside the directions themselves.