This tool turns a table of addresses, postcodes or place names into a point layer, using the /geocoding/search endpoint. The table can be a CSV file, an Excel worksheet or any table in the project.
| Description | |
|---|---|
| Input Table | The table of addresses. Browse to a CSV file or an Excel workbook (then pick the worksheet), or choose a table in the project. |
| Address Field | The column holding the text to geocode. Rows where it is blank are skipped. |
| Within Country | Only return matches in these countries. Leave blank to search worldwide. |
| Results per Address | The most matches to return for each address, best first (1 - 50). Defaults to 1. |
| Bounds | Only return matches inside this rectangle: the current map extent, a layer's extent, or typed corner coordinates |
| Fields To Keep | Columns from the Input Table to copy onto each match, such as an ID column |
| Output Point Layer | Where to save the output - must be in the project geodatabase |
A point layer with one row per match, so an address can give several rows when Results per Address is above 1.
| Field | Description |
|---|---|
input_row | The row's position among the rows read, starting at 1. With a selection on the Input Table, only the selected rows are read. |
query | The text that was geocoded |
rank | The match's order for its address, 1 being the best. Only added when Results per Address is above 1. |
score | The API's confidence in the match, from 0 to 1 |
| Address parts | name, label, house_number, street, neighbourhood, postcode, town, city, district, local_admin, county, region, region_code, macroregion, country, country_code, continent, category, place_type |
longitude / latitude | The point's WGS84 coordinates |
Addresses with no match, and requests that fail, are reported as warnings naming the rows. With Robust Mode on (the default), the tool only fails if nothing at all was geocoded. Geocoding requests don't count towards the Hits Per Minute limit.