Reverse Geocoding in Bulk: Turn Coordinates Into Addresses

If you've ever exported a GPS log from a field-survey app, a fleet tracker, or a drone flight, you end up with a list that looks like `40.748817, -73.985428` — accurate, useful for maps, useless for a printed report.

What is reverse geocoding?

Reverse geocoding takes a latitude/longitude pair and returns the human-readable address: street, neighborhood, city, country. The reverse direction (address → coordinates) is called forward geocoding.

Doing it in bulk

The free Reverse Geocode Batch tool takes a list of coordinates (paste or CSV upload) and resolves each to an address. Results export as CSV with the original lat/lng plus the resolved address fields.

Because the tool uses the OpenStreetMap Nominatim public API, it throttles to one request per second as required by their usage policy. A 500-coordinate list takes ~8 minutes; the tool keeps the tab alive and shows progress.

When you need higher throughput

For tens of thousands of coordinates, switch to a paid provider:

• Google Geocoding API (most accurate in cities)
• Mapbox Geocoding (good global coverage)
• LocationIQ or Geoapify (Nominatim-based, no per-second limit)

For a one-off batch under a few thousand, the free tool is fine.

Accuracy notes

• City-scale results are reliable everywhere.
• Street-level results depend on OSM coverage — excellent in Europe and North America, patchy in rural areas elsewhere.
• A coordinate in the middle of a lake or forest returns the nearest named feature, not "(none)".

Use cases

• Cleaning up field-survey GPS logs into a deliverable spreadsheet.
• Adding human-readable locations to a fleet's daily trip report.
• Resolving drone waypoint files for inspection paperwork.
• Building a list of "where my photos were taken" from EXIF GPS.

Related

• GPS coordinates format: decimal vs DMS
• Read GPS coordinates from a photo