We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Achieve high-precision conversions between lat/long, addresses, and WGS84/GCJ02/BD09 coordinate systems to fix map location offsets.
Accepts commas, spaces, semicolons, line breaks, brackets, and longitude/latitude or lng/lat labels. Input is normalized to longitude,latitude before submission.
Enter details to see results
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page performs a reverse lookup: enter a geographic point and request its formatted address and address components. Reverse geocoding describes the step from coordinates to a human-readable location. The input is decimal degrees, with longitude first and latitude second when entering an unlabeled pair. For example, -74.0060,40.7128 places longitude before latitude; labeled forms such as lat: 40.7128, lon: -74.0060 make the axes explicit.
The result can include a formatted address and available administrative or street details. An expanded result option also requests nearby points of interest, roads, and business areas. This is a coordinate-to-address lookup; it does not turn a typed address into coordinates or transform between coordinate reference systems.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Use decimal-degree values. For an unlabeled pair, place longitude first, then latitude, separated by a comma, space, semicolon, or line break. You can also use recognizable labels such as longitude/latitude or lon/lat. Values must fall within the numeric longitude and latitude ranges of −180 to 180 and −90 to 90.
Leave the result setting on the basic option for the address and its available components. Choose the expanded option when nearby roads, points of interest, or business areas may help identify the place. The search-radius field is in meters; adjust it for the nearby detail request.
Submit the coordinates, then compare the formatted address and component fields with the location you intended. Copy the returned result when useful. If the location looks wrong, first verify axis order, signs, decimal points, and the coordinate reference used by the source.
Use cases
See how the tool fits into real work and everyday tasks.
An operations coordinator can look up a coordinate saved in a site log and use the returned address components to check whether the record points to the expected street or district.
A researcher organizing a small set of mapped points can use the basic address result for readable labels, or request nearby details to help distinguish locations around roads or named places.
Q&A
Find concise answers to common questions and confusing cases.
For an unlabeled pair, enter longitude first and latitude second. Labels such as lat: and lon: are recognized, which can help when copying from a source that displays latitude first.
The input accepts decimal-degree numbers, not degree-minute-second notation. Convert a DMS value to decimal degrees before entering it.
The result is a place description supplied for the coordinate by the lookup data. It may identify a nearby mapped address or feature, and some component fields may be absent. Check the input point and verify important locations against an authoritative map or on site.
Notes
Review scope, result limitations, and important precautions before use.
Passing numeric range checks does not prove that a coordinate uses the correct reference system or identifies the intended physical point. Address detail depends on the location data available for that area; a larger nearby-search radius does not guarantee a complete list. Do not treat a returned address as survey-grade positioning or as proof of a legal boundary.
Related
Discover related tools, collections, and available API capabilities.