Geocode
Convert an address or place name to latitude/longitude via OpenStreetMap's Nominatim service. Free, no auth, globally usable.
Tool ID
geocode
Credential Required
No.
Input Properties
| Property | Type | Default | Description |
|---|---|---|---|
query |
string | — | Required. Address or place name to geocode. |
limit |
string | "1" |
Max results to return (1-10). |
Published Outputs
| Output | Description |
|---|---|
found |
"true" if at least one match, "false" otherwise |
summary |
Human-readable text of the top match |
latitude |
Best-match latitude (string) |
longitude |
Best-match longitude (string) |
displayName |
Best-match full formatted address |
city |
Best-match city/town/village |
country |
Best-match country |
matches |
JSON array of all matches (up to limit) |
count |
Number of matches returned |
Example
Input:
tool: geocode
properties:
query: "Eiffel Tower, Paris"
Actual captured output:
Geocoded 'Eiffel Tower, Paris' → Eiffel Tower, 5, Avenue Anatole France,
Quartier du Gros-Caillou, 7th Arrondissement, Paris, Ile-de-France,
Metropolitan France, 75007, France
lat: 48.8582599, lon: 2.2945006
Pairs naturally with weather-forecast (which takes lat/lon):
- name: locate
tool: geocode
properties:
query: "{{input.address}}"
- name: weather
tool: weather-forecast
properties:
latitude: "{{locate.latitude}}"
longitude: "{{locate.longitude}}"
days: "3"
Nominatim usage rules
Using OpenStreetMap's free service comes with a Terms of Service:
- Rate limit: 1 request per second max. Fine for interactive use; if you're batching more than a few queries, add delays between calls or run your own Nominatim instance.
- Attribution required when displaying results: "Data © OpenStreetMap contributors, ODbL 1.0".
- User-Agent header is already set by the tool.
For heavy use, switch to a paid geocoder (Google Maps, Mapbox, HERE) — the tool would need modification.
Chaining Patterns
- geocode → weather-forecast — weather by address instead of lat/lon
- geocode → dataframe — normalize a CSV of addresses to coordinates
- Part of
daily-briefcomposites that take human-friendly location input
Limitations
- Precision varies: city names get city centroids, full addresses get house-level precision when data exists.
- OSM coverage is uneven globally — US/EU rich, some regions sparse.
- No reverse geocoding (lat/lon → address). Separate endpoint; could be added later.