Where something is located depends entirely on the reference frame you choose. The same object has different coordinates in body-relative, room-relative, address-based, and Earth-centered systems. Location is never a single fixed fact; it is the pairing of a position with a coordinate framework, a datum, and a time.

This explainer unpacks how those frameworks work, where they disagree by millimeters or miles, and why "where is this located" is really a question about measurement conventions, not just geography.

Mechanism: Reference Frames and Datums

Every location statement relies on a reference frame. A frame is a chosen origin, a set of axes, and a convention for measuring angles, distances, or position. For a building, the frame may be a street address tied to a parcel map. For a GPS reading, the frame is the WGS84 ellipsoid, a mathematical model of the Earth's shape. For an anatomical finding, the frame is the body's standard anatomical position.

The critical mechanism is the datum: a fixed, agreed starting surface and adjustment model. Earth's surface is irregular and constantly moving, so surveyors and satellites project positions onto an ellipsoid, then apply a geoid model to convert to height above sea level. Two coordinate pairs can describe the same physical point yet differ because they were referenced to different datums.

Consider WGS84 against NAD83, the North American datum. In the continental United States, the practical offset between them is roughly 1 to 2 meters. That sounds trivial until you are aligning a property line, a pipeline weld, or a runway threshold. The mechanism behind the gap is plate motion: NAD83 was fixed to the North American plate in the 1980s, while WGS84 approximates a global average. The plates keep drifting, so the mismatch grows by centimeters per year.

At smaller scales, the same logic applies. A location described as "the third drawer down" is a position in a body-relative frame. A location described as latitude 40.7128 and longitude -74.0060 is a position in a geodetic frame. Neither is more real than the other; each is more or less useful for a specific task.

Plain language: a location is a number plus the rulebook telling you what that number means.

Quantified Context: How Big Are the Differences

The size of a location error or ambiguity scales predictably with the frame and the precision of the measurement.

A generic consumer GPS receiver, under open sky, typically reports horizontal accuracy within about 3 to 5 meters. Under tree canopy or between tall buildings, that can degrade to 10 meters or more because signals reflect off surfaces before reaching the antenna. Survey-grade receivers using real-time kinematic corrections can reach centimeter-level accuracy, but they require a base station or correction service.

Address systems add their own uncertainty. In the United States, a rooftop-level geocode can land within a few meters of the building, while a street-interpolated geocode may be off by tens of meters, especially on long rural blocks. Parcel boundaries introduce legal precision that GPS cannot replicate, because a deed describes a boundary by monuments and bearings, not by decimal degrees.

Indoor and body-relative locations carry their own numbers. Hospital imaging systems routinely record lesion locations to millimeter precision because treatment planning depends on it. By contrast, a verbal report of "left side, lower back" may map to a region spanning many centimeters and several possible structures.

Time adds a moving target. Tectonic plates shift at rates of roughly 1 to 10 centimeters per year in active regions and a few centimeters per year in stable continental interiors. Earthquake events can displace ground by meters in seconds. Any coordinate stored without a date is a snapshot, not a permanent truth.

The takeaway: the appropriate tolerance for "where is this located" depends on the question. A delivery driver needs building-level accuracy; a surgeon needs millimeter accuracy; a geologist needs a time-stamped coordinate with an uncertainty ellipse.

Edge Cases: When Location Becomes Genuinely Ambiguous

Some situations break the ordinary mapping between position and answer.

Antimeridian crossing. Longitude runs from -180 to 180 degrees. A point near the international date line can be described as +179.9 or -179.9, and a naive average of the two yields a location near the prime meridian. Software must handle this wrap explicitly.

Poles. Longitude is undefined at the geographic poles, and projected map coordinates distort severely near them. Locations there are better given as distances along a chosen meridian or in a polar stereographic system.

Heights. "Where" in the vertical dimension depends on the reference surface. Ellipsoidal height, orthometric height above the geoid, and local tidal datums can differ by tens of meters. A building footprint at the same horizontal coordinate can have two legitimate "elevations."

Numerical precision limits. The coordinate value in PostgreSQL's double precision has about 15 significant decimal digits. Latitude values can store a fixed-point representation of about 17 significant digits with a scale of 6, while longitude values can store about 16 significant digits. Either is enough for centimeter use, but truncation during storage or display is a common silent error source.

Relative descriptions. "Next to the red door" is a valid location only if the listener shares the landmark set and can see the door. Change the observer or the lighting and the description fails.

If you are storing locations, flag these as warning conditions:

Coordinates without a datum and precision metadata are not reproducible. Averaging longitude values across the antimeridian produces wrong results. Heights quoted without a reference surface are meaningless. Address-level geocodes should never be treated as parcel boundaries. Any coordinate older than a few years in a tectonically active region needs a time correction.

Misconceptions: Latitude, Longitude, and "Exact"

A common misconception is that latitude and longitude are a grid of equal-sized cells. They are not. A degree of latitude is roughly 111 kilometers everywhere, but a degree of longitude shrinks with the cosine of latitude. Near the equator it is about 111 kilometers; near 60 degrees north it is about 56 kilometers. Distance calculations that ignore this produce large errors at high latitudes.

Another misconception is that "GPS coordinates" are inherently precise. The receiver's reported accuracy estimate matters as much as the number itself. A coordinate with a 20-meter uncertainty radius is not a precise location, even if it has six decimal places.

A professional caveat: legal boundaries and property lines are established by surveys and recorded documents, not by consumer devices. A phone reading that places a fence within a meter of a line is not evidence of ownership. Surveyors use monumented control points, calibrated equipment, and documented procedures precisely because raw coordinates are not adjudicative.

The counterintuitive detail: higher numerical precision does not imply higher accuracy. A value with 12 decimal places derived from a low-accuracy source remains a low-accuracy location dressed in precise clothing.

Comparisons: Location Systems Side by Side

System Typical accuracy Reference frame Best use Main limitation
Street address Sub-meter to tens of meters Local parcel grid Mail, services Rural and new construction ambiguity
Consumer GPS 3 to 5 m open sky; 10 m+ obstructed WGS84 Navigation Multipath and canopy errors
Survey-grade GNSS Centimeters WGS84/NAD83 with corrections Boundary and engineering work Cost and setup requirements
Geocoded coordinates Meters to tens of meters Vendor geocoder Mapping and analysis Interpolation and address quality
Floor plan / indoor map 1 to 5 m with Wi-Fi; better with beacons Building-local Indoor navigation Infrastructure dependency
Anatomical coordinates Millimeters Body planes and landmarks Clinical imaging Requires imaging context
Astronomical coordinates Arcseconds to arcminutes Celestial frame (ICRS) Sky location Time-dependent proper motion

The table makes the core point visible: the answer to "where is this located" depends on which row of the system you are using. Each row has a fit-for-purpose tolerance.

Timeline: How Location Precision Evolved

Period Dominant method Practical precision
Ancient through medieval Landmarks and dead reckoning Hours to days of travel error
Age of sail Sextant and chronometer Nautical miles
19th century Triangulation networks and benchmarks Meters to tens of meters
Mid-20th century Electronic distance measurement Sub-meter on surveys
1978 onward First GPS satellites Tens of meters
2000 Selective availability removed Few meters
2010s Multi-constellation GNSS and RTK Centimeters with corrections
Present Mass-market multi-band receivers 1 to 3 m typical in the open

This timeline matters because stored locations carry the precision of their era. A coordinate recorded from a 1990s handheld unit should not be reinterpreted as if it had modern accuracy.

Practical Actions: Getting a Defensible Location Answer

The right procedure depends on what you are locating and for whom.

For everyday navigation and deliveries, record the coordinate, the datum, the horizontal accuracy value, and the date. If the answer matters later, keep the uncertainty. A coordinate without an accuracy estimate is an incomplete record.

For property, construction, and legal questions, do not rely on consumer devices. Obtain a boundary survey from a licensed surveyor and reference the recorded plat or deed. The threshold question is legal, not technical: the recorded document controls.

For scientific and clinical measurements, specify the reference frame explicitly. State the ellipsoid and geoid for heights. State the anatomical landmarks and imaging modality for internal positions. Report uncertainty alongside the value.

For data systems, store latitude and longitude as separate numeric fields with adequate scale. Avoid floating-point rounding during display. Handle the antimeridian and pole cases in code. Attach a timestamp to any coordinate expected to remain accurate over years.

For interpreting someone else's location claim, ask four questions: which frame, which datum, what accuracy, and what date. If the answer to any of those is missing, treat the location as provisional.

Concrete thresholds to apply:

If accuracy is 10 m or worse, do not use the point for boundary or safety decisions. If the datum is unspecified, do not merge the coordinate with modern datasets without checking the offset. If the coordinate is older than five years in an active tectonic zone, request an updated measurement. If the height reference is unstated, do not compare it to sea-level or flood datasets.

Limitations: What Location Answers Cannot Deliver

No location system resolves every question, and each has a ceiling.

GNSS cannot work indoors, underground, or underwater without augmentation. Address systems cannot describe places that have no address. Parcel records cannot resolve occupation versus title. Anatomical coordinates cannot substitute for a clinician's interpretation of imaging. Astronomical coordinates drift as stars move, requiring epoch information.

A deeper limitation is conceptual: location is relational. "Where is this located" presupposes a frame, and every frame is chosen by someone for a purpose. The coordinate is a tool, not a fact of nature.

A professional caveat worth repeating: precision and accuracy are different properties, and legal, clinical, or engineering decisions require the appropriate instrument and the appropriate record, not merely a number with many digits.

For property-law questions, medical-image interpretation, or safety-critical positioning, this article is general educational information. It is not a legal opinion, diagnosis, or engineering certification, and it does not promise any particular outcome. Consult a qualified local professional for decisions that depend on an exact location. For immediate danger or self-harm risk, contact local emergency or crisis services.