🌍 Geocoder (OpenStreetMap)

Turn addresses or place names into coordinates (forward geocoding) and turn coordinates back into addresses (reverse geocoding) — with full structured address parts, bounding box, OSM ids and place type. Powered by the public OpenStreetMap Nominatim API, so it's reliable and needs no API key. Requests are rate-limited to respect the OSM usage policy.

Built for enriching lead lists and CRMs, mapping, real-estate data and location pipelines. Export to JSON/CSV/Excel, run on a schedule, call via API, or connect to Make, Zapier or n8n.

🔎 What is the Geocoder?

Pass addresses to get latitude/longitude and a parsed address — or pass lat,lon coordinates to get the nearest address back. Optionally restrict forward results to a country.

What data does it extract?

• Latitude and longitude
• Full display name and place name
• Structured address: house number, road, city, state, postcode, country, country code
• Place type and category (e.g. attraction, city, building)
• Importance score and bounding box
• OSM type and id, place id

⬇️ Input

Field	Type	Description
addresses	array	Addresses/place names to geocode, e.g. Eiffel Tower, Paris.
coordinates	array	Optional: lat,lon pairs to reverse-geocode.
countryCode	string	Optional: restrict forward results to a country (ISO alpha-2).
maxResultsPerQuery	integer	Matches per address. Default 1.

Example input

{
  "addresses": ["Eiffel Tower, Paris", "1600 Amphitheatre Parkway, Mountain View"],
  "maxResultsPerQuery": 1
}

⬆️ Output

One record per result:

{
  "query": "Eiffel Tower, Paris",
  "display_name": "Eiffel Tower, 5, Avenue Anatole France, Paris, France",
  "lat": "48.8582599",
  "lon": "2.2945006",
  "type": "attraction",
  "category": "tourism",
  "importance": 0.79,
  "osm_type": "way",
  "osm_id": 5013364,
  "road": "Avenue Anatole France",
  "city": "Paris",
  "postcode": "75007",
  "country": "France",
  "country_code": "fr",
  "bounding_box": ["48.857", "48.859", "2.293", "2.296"]
}

💡 Use cases

• 📍 Lead & CRM enrichment — add coordinates and clean addresses to records.
• 🗺️ Mapping & visualization — plot addresses on a map.
• 🏠 Real-estate data — standardize and locate property addresses.
• 🤖 Automation — geocode inside Make/Zapier/n8n workflows.

❓ FAQ

Do I need an API key or login? No — it uses OpenStreetMap Nominatim.

Does it do reverse geocoding? Yes — pass lat,lon pairs in coordinates.

Can I restrict to a country? Yes — set countryCode.

How fast is it? Requests are throttled to ~1/second to respect the OSM usage policy.

What address parts do I get? House number, road, city, state, postcode, country and country code.

How does pricing work? Pay per result returned. No subscription.

Is it legal? It uses the public OSM Nominatim API. Use responsibly and within the OSM usage policy.

🔗 You might also like

• Google Maps Email Scraper — local business leads + emails.
• Public Holidays Scraper — holidays by country.
• Website Contact Extractor — emails & phones from sites.

---

Keywords: geocoder, geocoding api, address to coordinates, reverse geocoding, openstreetmap, nominatim, lat lon lookup, address parser, location data, lead enrichment, gps coordinates, batch geocoding, address standardization, mapping data

Production workflow

This Actor is designed for operations teams, property analysts, logistics workflows and location-data developers. Normalize input addresses first, retain the original query beside every match, and review importance, type and bounding-box fields before using a coordinate in routing, territory or property workflows. Small, repeatable runs are easier to audit than occasional unlimited exports: they expose source changes quickly, reduce duplicate processing and keep automation costs predictable. Use the input defaults as a smoke test, then widen the query only after confirming that the returned fields match the downstream workflow.

Treat each dataset row as source evidence captured at a point in time, not as a permanent fact. Preserve the canonical identifier and source URL, add the run timestamp in the receiving system, and deduplicate before writing to a CRM, spreadsheet, warehouse or alert channel. For recurring monitoring, compare the newest dataset with the previous successful run and send only additions or material changes onward. That pattern avoids repeated notifications and makes the automation more useful over time.

Data quality and interpretation

The primary output includes query, display_name, lat, lon, type, category, importance, place_id, osm_type, osm_id, name, house_number. Availability depends on what the source publishes for a particular result. Empty values are retained as null or empty fields rather than invented. Search rank is source-specific and can change with language, geography, query wording and time. Validate critical decisions against the linked source page, especially when the data is used for outreach, compliance, pricing, routing or reporting.

Use bounded inputs and respect the source's published interface. The Actor does not bypass logins or collect private account data. Avoid placing passwords, session cookies, personal access tokens or confidential records in Actor input. If a public source changes its response shape, attach a reproducible public input and run ID to an Actor issue so the parser can be updated without exposing private data.

Automation and cost control

The default dataset can be exported as JSON, CSV, Excel, XML or RSS and can be consumed through the Apify API. In Make, Zapier or n8n, start the Actor, wait for the run to finish, then read default-dataset items. In code, store the Actor run ID and dataset ID alongside the imported rows so every record remains traceable. Apply filters after collection only when the source cannot express them directly; source-side filtering usually reduces cost and noise.

This Actor uses pay-per-event billing. A result event is charged only when a structured row is saved to the default dataset. Keep test runs small, estimate expected row volume before scheduling broad searches, and use platform spending limits for unattended workflows. Failed requests and empty searches should not create result events.

Support and feedback

If the Actor saves time in a real workflow, please leave a short Apify Store review describing the use case and the fields that were most useful. Reviews help other users evaluate the product and help prioritize maintenance. For support, open an Actor issue with the run ID, public input, expected behavior and one affected field. Do not include credentials or confidential information.