More games at WuGames.ioSponsoredDiscover free browser games — play instantly, no download, no sign-up.Play
Geo Tools GeoConverter Tools ConverterData Tools Data

Reverse Geocoder - Convert Coordinates to Address

Free reverse geocoder: convert decimal or DMS GPS coordinates (lat/long) to street addresses via OpenStreetMap/Nominatim, with ISO 3166 region context.

°
°
Example: Latitude: 21.0278, Longitude: 105.8342 (Hanoi, Vietnam)DMS and hemisphere notation accepted too, e.g. 21°01'40"N, 105 50 03 E.

What is Reverse Geocoding?

Reverse geocoding is the process of converting geographic coordinates (latitude and longitude) into a human-readable address. This is the opposite of geocoding, where addresses are converted to coordinates.

Reverse geocoding is essential for GPS devices, mobile apps, location-based services, and any application that needs to display addresses from coordinate data. It helps users understand where a specific coordinate point is located in terms they can recognize.

Key features of this reverse geocoder:

  • Global Coverage: Find addresses worldwide from any valid GPS coordinates
  • Detailed Results: Get street, city, state, country, and postal code information
  • High Accuracy: Uses OpenStreetMap data for precise location identification
  • Instant Results: Fast lookup with detailed address breakdown

How to Use the Reverse Geocoder

Using the reverse geocoder is straightforward:

  1. Enter Latitude: Input the latitude value in decimal degrees (-90 to 90)
  2. Enter Longitude: Input the longitude value in decimal degrees (-180 to 180)
  3. Click Find Address: Press the 'Find Address' button to search
  4. View Results: See the full address and individual address components

Reverse Geocoding Use Cases

Reverse geocoding is used in many applications:

  • GPS Navigation: Display current location address in navigation apps
  • Mobile Apps: Show user location in human-readable format
  • Photo Geotagging: Display location where photos were taken from GPS metadata
  • Tracking Systems: Convert vehicle/asset GPS coordinates to addresses
  • Analytics: Analyze geographic data by converting coordinates to regions

Understanding Address Components

The reverse geocoder breaks down addresses into components:

  • Street: Road name and number (if available)
  • City: City, town, or village name
  • State/Province: Administrative region within a country
  • Country: The country where the coordinates are located

Coordinate Formats and Accuracy

This tool accepts coordinates in both decimal degrees (DD) and degrees-minutes-seconds (DMS), including N/S/E/W hemisphere notation — no manual conversion needed. Paste 21.0278, 105.8342 or 21°01'40"N, 105°50'03"E (or 40 26 46 N) and the tool auto-normalizes to decimal degrees, shows the normalized value, and uses it for the lookup.

The accuracy of the returned address depends on the availability of address data for the location and the precision of the input coordinates. More precise coordinates (more decimal places) may yield more accurate street-level addresses.

Frequently Asked Questions

Both decimal degrees (DD) and degrees-minutes-seconds (DMS) work, in either field. DD is a single signed number such as 21.0278 or -33.8688. DMS can be written with symbols (21°01'40.1"N), with plain spaces (21 01 40.1 N), or with just degrees and minutes (40° 26.5' N). Hemisphere letters N, S, E, and W are recognized and applied automatically: S and W make the value negative, exactly like a leading minus sign. You can also omit minutes and seconds (e.g. 105°E). After you submit, the tool prints the normalized decimal-degree value it actually queried — for example DMS 21°01'40.1"N becomes 21.027806 — so surveyors, pilots, and GIS users can paste whatever notation their source provides without converting it elsewhere first. Anything that is not a valid DD or DMS string (like 21XYZ) is rejected with a range/format error.

Latitude always comes first, then longitude — the same order Google Maps and most GPS devices use, written (lat, lon). Latitude ranges from -90 to +90 and measures north-south distance from the equator; longitude ranges from -180 to +180 and measures east-west distance from the Greenwich prime meridian. The sign encodes the hemisphere: positive latitude is North, negative is South; positive longitude is East, negative is West. So Hanoi at 21.0278 N, 105.8342 E is (21.0278, 105.8342), while Santiago at 33.45 S, 70.66 W is (-33.45, -70.66). Swapping the two fields is the single most common reverse-geocoding mistake and usually drops you in the ocean or a different continent. If you enter DMS with explicit N/S/E/W letters this tool sets the sign for you, so you do not also need to add a minus — use one or the other, not both.

Forward geocoding takes a human-readable address ("1600 Amphitheatre Parkway, Mountain View") and returns latitude/longitude coordinates. Reverse geocoding does the opposite: given a (lat, lon) pair such as (37.4220, -122.0841) it returns the closest street address, place name, administrative regions, postal code, and country (using ISO 3166 codes). Both operations rely on the same underlying address-coordinate database, but reverse geocoding additionally requires spatial indexing (R-tree, geohash, S2 cells) so that a nearest-neighbor lookup on a billion-point dataset still runs in milliseconds. Reverse geocoding is what powers "What address is this?" features in photos, ride-sharing app pickup detection, and IoT device location logging.

A modern reverse-geocoding response includes a hierarchy of administrative components, each tagged with the standard code where applicable: country (ISO 3166-1 alpha-2 like "US" and alpha-3 like "USA"), country subdivision (ISO 3166-2 like "US-CA" for California), county, city, neighborhood, postal/ZIP code, street name, street number, and often the OpenStreetMap or government parcel ID. Open services like Nominatim also return a "display name" string (a human-friendly concatenation), a place class (highway, building, amenity), and OSM element type (node, way, relation). Coordinates within the result let you locate the centroid of the matched feature. ISO 3166 codes are critical for any downstream system that aggregates by region — they avoid the ambiguity of names ("Georgia" the US state vs. the country).

Ocean points return either no result or a maritime zone (EEZ name, sea name) depending on the provider — Marine Regions and OpenStreetMap "natural=coastline" relations cover this. National-park points return the park name and country but no street address — the response degrades gracefully to whatever administrative coverage exists. Building-rooftop points are the trickiest: providers either snap to the building footprint centroid, to the nearest street access (the "approach point"), or return both with a snapping-distance field so you can flag low-confidence matches. For drone-delivery and emergency-response applications you specifically want the approach point, not the rooftop; check whether your provider exposes that field. Always inspect the confidence/match-type field, not just the address string.

Three reasons. First, source data: OpenStreetMap, Google's proprietary database, HERE, Mapbox, and government cadastral systems all have different coverage and update cycles — a new subdivision may exist in one but not another. Second, address-snapping policy: some services return the nearest known address regardless of distance (returning a wrong address up to 500 m away), others return null beyond a threshold. Third, administrative boundary versions: country borders, city limits, and ZIP-code boundaries change over time; a coordinate near a city border might be assigned differently by services using different vintages of boundary data. For audit-critical work, always log the provider, the API version, and the timestamp alongside the response. For consensus, query 2–3 services and accept the most common result.

OpenStreetMap coverage is exceptionally rich in Western Europe, the United Kingdom, Germany, the Netherlands, and urban North America — often matching or exceeding Google's data, because OSM editors trace from cadastral maps and field surveys. In sub-Saharan Africa, rural India, much of Southeast Asia, and Latin America outside major cities, OSM coverage is sparser; commercial providers using Maxar satellite imagery often have more buildings and roads. Nominatim addresses can lack house numbers in countries where OSM tagging is incomplete; the returned address might fall back to the street name plus the city. For consumer-grade applications Nominatim (self-hosted or via the Mapbox or LocationIQ providers) typically delivers 95%+ accuracy in covered regions. Cross-check with a second source for mission-critical applications.

The public Nominatim service at nominatim.openstreetmap.org enforces 1 request per second and requires a User-Agent header — bulk processing is forbidden and gets your IP banned. For production, self-host Nominatim (Docker images available) or use a paid mirror like LocationIQ, Geocode Earth, or MapTiler that allow high throughput. Google Maps Geocoding API charges roughly $5 per 1,000 requests beyond a free monthly tier, requires an API key, and prohibits storing results long-term per its terms. HERE, Mapbox, and TomTom have similar paid tiers. The data licensing also matters: OSM data is ODbL-licensed (share-alike), so derivative datasets must be released under ODbL too. Commercial APIs typically allow display-only use but restrict redistribution.

Three approaches scale well. (1) Self-host an offline reverse geocoder: load OSM extracts into PostGIS or use the open-source "reverse-geocoder" Python package (which uses a 5-million-city KD-tree for sub-millisecond country/city lookup but no street-level detail). (2) Pre-compute administrative boundaries: download Natural Earth or GADM polygon shapefiles, then for each point do a point-in-polygon test against an R-tree-indexed boundary set — this gives country/state/city for ~100k points/second per CPU core. (3) For street addresses at scale, batch through a paid API in parallel respecting rate limits; AWS Location Service, Mapbox, and Google support batch endpoints. Always deduplicate identical coordinates first (round to 4–5 decimal places) — repeated queries on the same point waste credits.

Reverse geocoders fall back to whatever administrative or named-place data exists. For Antarctic research stations like McMurdo or Vostok, providers return the station name, the territorial claim region (often listed as "AQ" ISO 3166), and no postal code. For ships at sea, they return the EEZ or international-waters designation — MMSI-based AIS tracking systems supplement this. For refugee camps and informal settlements, OpenStreetMap has detailed Rohingya camp mapping in Bangladesh and Syrian camps in Jordan, often with named subsections; commercial geocoders may not. For unaddressed rural India and parts of Africa, Plus Codes (Open Location Codes) provide a synthetic address grid that some reverse geocoders now return alongside or instead of a street address — useful for delivery to slums and undeveloped land where no postal address exists.
Reverse Geocoder - Convert Coordinates to Address — Free reverse geocoder: convert decimal or DMS GPS coordinates (lat/long) to street addresses via OpenStreetMap/Nominatim
Reverse Geocoder - Convert Coordinates to Address
See also
Geography & Mapping ToolsGEOGRAPHY & MAPPING TOOLS21
WuToolsWUTOOLS