Coordinates to Address

What “coordinates to address” actually does

Reverse geocoding is the conversion from a geographic coordinate pair — latitude and longitude — to the nearest known address in a reference dataset. It is the inverse of forward geocoding (address → coordinates) and a separate operation from point-of-interest (POI) lookup (place name → coordinates). The conceptual distinction matters: a reverse geocoder never invents an address; it snaps your point to the closest record in its dataset and reports that record back, along with how certain it is about the match.

The reference dataset behind this tool is Mapbox Geocoding API v6, which is built on OpenStreetMap plus Mapbox Boundaries and proprietary postal-address data. The precise data lineage varies by country: dense urban North America and Western Europe is mostly rooftop-level accurate; rural and developing regions inherit OSM's coverage, which ranges from excellent to sparse depending on the contributor community.

Per ISO 19112:2019 Geographic information — Referencing by identifiers, an address is a hierarchical locator (country → administrative area → locality → thoroughfare → number). The Mapbox response carries that hierarchy in its context object, surfaced in the result panel above as separate fields for street, locality, region, postcode, and country.

How accurate is reverse geocoding?

Accuracy depends on three things: the underlying address density, the precision of the query coordinate, and how the provider resolves ambiguity when the query falls between known records. Mapbox surfaces this combined uncertainty in a single match_code.confidence field with three values: high, medium, and low.

The number for “dense urban coverage” is consistent with Mapbox's documented accuracy targets. Real-world tests against ground-truth coordinates published by the US Census Bureau TIGER/Line dataset typically place high-confidence Mapbox responses within one parcel of the correct address in metropolitan US areas.

What reverse geocoding is not

It is not a place-name lookup. If you reverse-geocode the coordinates of the Empire State Building (40.7484° N, 73.9857° W), Mapbox returns the building's street address — 350 5th Ave, New York, NY 10118— not the string “Empire State Building”. Place names require either a separate point-of-interest (POI) endpoint or a places dataset; the Mapbox v6 geocoder is intentionally address-only.

It is also not parcel data. Reverse geocoders return postal addresses, not the legal property boundary or ownership record. For US parcel-level lookup, the authoritative source is the county assessor's GIS layer; nationwide parcel APIs (Regrid, ATTOM) provide commercial access.

Ten ways reverse geocoding gets used in production

Reverse geocoding is one of the most common operations in modern software: anywhere a device reports a GPS fix and the user wants a human-readable place, it's happening. The ten cases below cover the bulk of real-world traffic against geocoders. Each is paired with a worked example using a real coordinate that you can paste into the tool above.

1. Emergency dispatch (Next-Generation 911 / PSAP)

When a mobile phone places a 911 call, the carrier delivers location to the Public Safety Answering Point (PSAP). Per the FCC Wireless E911 Location Accuracy Requirements, the location must be horizontally accurate to 50 m for 80% of calls (the “z-axis” vertical requirement adds floor-level accuracy in multi-storey buildings as of 2025). PSAPs reverse-geocode that coordinate to a street address so the dispatcher can route an ambulance, fire truck, or police unit to a specific door rather than a lat/lon.

Worked example: A caller's phone reports 37.795200, −122.393500with a 30 m uncertainty ellipse. Reverse geocoding returns Pier 7, The Embarcadero, San Francisco, CA 94111 with high confidence. Dispatch sends EMS to Pier 7. Reference standard: NENA i3 (Detailed Functional and Interface Standards for the NG9-1-1).

2. Last-mile delivery confirmation

Couriers (UPS, FedEx, USPS, Amazon Logistics, DHL) confirm package delivery by capturing GPS coordinates at the drop-off and reverse-geocoding to verify the captured location matches the shipping address. The match is a primary input to the “proof of delivery” record stored against the parcel ID.

Worked example: A USPS scanner records 47.620500, −122.349100 at delivery. Reverse geocoding returns Space Needle, Seattle, WA 98109 — the shipping label said “Pacific Northwest Office, Space Needle”, so the captured location passes verification. The USPS Publication 28 addressing standard is the canonical format used in this verification.

3. Photo geotagging (Lightroom, Apple Photos, Google Photos)

Digital cameras and smartphones write GPS coordinates into the EXIF metadata of each JPEG (per JEITA CP-3451, Exif 2.2+). Photo-management software reverse-geocodes those coordinates to attach human-readable place names to each photo and to group photos by trip or city.

Worked example: A photo's EXIF reads GPSLatitudeRef N, GPSLatitude 48 51 30.13, GPSLongitudeRef E, GPSLongitude 2 17 40.18 — or in decimal degrees 48.858370, 2.294480. Reverse geocoding returns Champ de Mars, 5 Avenue Anatole France, 75007 Paris, France — the Eiffel Tower. The library automatically tags the photo “Paris” in its album view.

4. Ride-hailing and food delivery (Uber, Lyft, DoorDash)

When a driver taps “I'm here” or “arrived at pickup”, the app reverse-geocodes the driver's GPS to a street address and pushes that text to the customer's phone. The same operation runs on the customer side when the “set pickup location” pin is dragged on the map.

Worked example: Driver app reports 40.758000, −73.985530. Reverse geocoding returns 1556 Broadway, New York, NY 10120(Times Square). The rider sees the notification: “Your driver has arrived at Broadway and W 46th St.”

5. Field-service technicians (Verizon, Comcast, PG&E)

Truck-mounted GPS plus the technician's smartphone provides a location for every service stop. Dispatch software reverse-geocodes the captured location to confirm it matches the work-order address (this prevents the technician from accidentally invoicing the wrong house in a long suburban block).

Worked example:A PG&E truck's telematics report 37.870000, −122.270900. Reverse geocoding returns 2025 Center St, Berkeley, CA 94704 — the assigned work-order address matches.

6. Real estate / property tech (Zillow, Redfin, Realtor.com)

MLS feeds carry latitude and longitude alongside the listing's address. Reverse geocoding normalises the coordinate-derived address to USPS Publication 28 format for display, search, and comparison across listings.

Worked example: A listing's MLS feed reports −33.856880, 151.215150. Reverse geocoding returns Bennelong Point, Sydney NSW 2000, Australia— the Sydney Opera House. The listing page displays the canonical address; the search index keys it by suburb (“Sydney CBD”).

7. Fleet management and asset tracking (Samsara, Geotab, Verizon Connect)

Telematics devices on commercial vehicles report GPS pings every 30–60 seconds. Fleet dashboards reverse-geocode pings at meaningful events (stop, idle, geofence cross) to produce human-readable trip logs. Continuous reverse geocoding of every ping is uneconomical; sampled reverse geocoding at events is the standard pattern.

Worked example:A delivery truck's telematics device reports a 10-minute idle event at 41.882700, −87.623400. Reverse geocoding returns 233 S Wacker Dr, Chicago, IL 60606(Willis Tower). The trip log records “10 min idle, Willis Tower.”

8. Wildfire and natural-disaster response (CAL FIRE, NIFC)

Incident commanders pin fire perimeter coordinates from aerial surveys, drone imagery, and ground-truth crews. Reverse geocoding attaches the nearest road, structure, or named place to each pin so that evacuation orders, road closures, and resource staging can be communicated to civilians using familiar names. The National Interagency Fire Center publishes daily incident reports built on exactly this pattern.

Worked example: A CAL FIRE drone records a hotspot at 38.847000, −120.317800. Reverse geocoding returns Caldor Mountain Rd, El Dorado County, CA. The evacuation order references “Caldor Mountain Rd vicinity” rather than a coordinate.

9. Biodiversity citizen science (iNaturalist, eBird)

Field observers record species sightings with a coordinate fix from their phone. The platform reverse-geocodes to attach a county / state / country / biome label, which becomes the jurisdiction key for downstream conservation queries (“all observations of Lynx rufusin Mason County, Michigan since 2020”).

Worked example:An iNaturalist observer's phone reports 44.052100, −86.491400. Reverse geocoding returns Ludington State Park, Mason County, Michigan 49431. The observation is filed under “Mason County, MI, USA” for state-park biodiversity rollups.

10. Recreation and licensing apps (Fishbrain, onX Hunt)

Catch-and-release logging, hunting unit lookup, and licensing compliance all need the legal jurisdiction at the activity location. Reverse geocoding to county or state polygon — followed by a lookup in the state Department of Natural Resources' rules table — determines which license, season, and bag limits apply.

Worked example:An angler's phone records a catch at 45.382000, −84.957000. Reverse geocoding returns Wilderness State Park, Emmet County, Michigan. The app surfaces Michigan Department of Natural Resources regulations for inland trout in Wilderness State Park — species, slot limit, and seasonal closures.

Choosing the right tool from the “reverse” family

A coordinate pair can be reverse-resolved to several different kinds of place. The right operation depends on which kind of place you want.

Why the result is sometimes wrong

Five recurring failure modes:

• Sparse data. Rural or developing-world locations rely on OSM coverage that may not exist near your query.
• Address-vs-POI confusion.Mapbox v6 is an address geocoder. Querying the centre of a stadium will return the stadium's street address, not the stadium's name.
• Off-the-grid points. Points in the ocean, in large parks, or in deserts have no nearby address; the result will be a distant landmark with low confidence.
• Dataset lag. New construction takes weeks to months to appear in commercial address datasets; coordinates in new developments may resolve to the closest pre-existing record.
• Coordinate-system confusion.If your input is in a different datum than WGS 84 (for example NAD 27), the offset can be tens of metres. Mapbox assumes WGS 84.

Privacy and data-flow notes

Coordinately runs reverse geocoding server-side. Your coordinate is sent to Mapbox; Mapbox returns the address; the page renders the response and discards it. Per Mapbox's terms of service the response cannot be cached or retained, so Coordinately stores nothing. Browser geolocation, when triggered by the “Use my location” button, stays in your browser. The full data-flow description is at /privacy-policy.