What is Geocoding ?
Geocoding is the process of converting addresses (like a street address) into geographic coordinates (like latitude and longitude). With Woosmap you can request nearby location or display on a map a lot of geographic elements like stores or any other point of interest.
To take advantages of these features, you first have to push geocoded locations to our system, in Woosmap data management API. Most of the time, your dataset has addresses but no location information.
The following script, hosted on our Woosmap Github Organization, is a basic utility for geocoding CSV files that have address data included. It will parse the file and add coordinate information as well as some metadata on geocoded results like the location type. It calls Geocoding API through the GeoPy python client.
The source code is open to view and change, and contributions are welcomed.
GeoPy is a Python client for several popular geocoding web services. It makes it easy for Python developers to locate the coordinates of addresses, cities, countries, and landmarks across the globe using third-party geocoders and other data sources. It includes geocoder classes for the OpenStreetMap Nominatim, ESRI ArcGIS, Google Geocoding API (V3), Baidu Maps, Bing Maps API, Mapzen Search, Yandex, IGN France, GeoNames, NaviData, OpenMapQuest, What3Words, OpenCage, SmartyStreets, geocoder.us, and GeocodeFarm geocoder services.
Geocoding API is a service that provides geocoding and reverse geocoding of addresses. In this python script we used the GeoPy wrapper of this API but a nice alternative could be to implement the Python Client for Google Maps Services available on Google GitHub organization. Adapting the source code of the script to this python client would be easy as the Geocoding method accepts identical parameters and returns almost the same object.
Each Google Maps Web Service request requires an API key that is freely available with a Google Account at Google Developers Console. The type of API key you need is a Server key.
To get an API key (see the guide to API keys):
Important: This key should be kept secret on your server (but you can revoke a key and generate a new one if needed)
A Client ID is given to you when you sign up as a Google Maps Platform. The Digital Signature is generated using a cryptographic key provided to you by Google and used when authenticating with a Client ID.
To get your Client ID and Crypto Key (see the guide to API keys):
Important: This Crypto Key must be kept secrete as you can’t revoke it!
The script takes an input csv file with addresses you need to geocode and produce an output csv file that contains all values from origin csv with appended following fields :
Download the script to your local machine. Then run:
python google_batch_geocoder.py
To make it compatible with your own CSV file and Google keys, you have to set the following parameters on top of the script.
ADDRESS_COLUMNS_NAME
- LIST - used to set a google geocoding query by merging these values into one string comma separated. it depends on your CSV input file
NEW_COLUMNS_NAME
- List - appended columns name to processed data csv (no need to change this but you can add new columns depending on Geocoding Google Results)DELIMITER
- String - delimiter for your input csv fileINPUT_CSV_FILE
- String - path and name for input csv fileOUTPUT_CSV_FILE
- String - path and name for output csv fileCOMPONENTS_RESTRICTIONS_COLUMNS_NAME
- DICT - used to define component restrictions for google geocoding. See Google component Restrictions doc for details.
GOOGLE_SECRET_KEY
- String - Google Secret Key, used by GeoPy to generate a Digital Signature that allows you to geocode for Google Maps API For Work Users.GOOGLE_CLIENT_ID
- String - Google Client ID, used to track and analyse your requests for Google Maps API For Work Users. If used, you must also provide GOOGLE_SECRET_KEY.GOOGLE_API_KEY
- String - Google API Server Key. It will become a mandatory parameter soon.The sample data (hairdresser_sample_addresses.csv
) supported by default is a CSV file representing various hairdressers around the world. You can see below a subset of what the file looks like:
name | addressline1 | town | postalcode | isocode |
---|---|---|---|---|
Hairhouse Warehouse | Riverlink Shopping centre | Ipswich | 4305 | AU |
Room For Hair | 20 Jull Street | ARMADALE | 6112 | AU |
D'luxe Hair & Beauty | Burra Place Shellharbour City Plaza | Shellharbour | 2529 | AU |
As described above, the destination file contains all the origins fields plus geocoded data (latitude, longitude and error when occur) and some metadata (formatted_address and location_type). In the case of our sample file, the Header of destination CSV file looks like :
with open(INPUT_CSV_FILE, 'r') as csvinput:
with open(OUTPUT_CSV_FILE, 'w') as csvoutput:
# new csv based on same dialect as input csv
writer = csv.writer(csvoutput, dialect="ga")
# create a proper header with stripped fieldnames for new CSV
header = [h.strip() for h in csvinput.next().split(DELIMITER)]
# read Input CSV as Dict of Dict
reader = csv.DictReader(csvinput, dialect="ga", fieldnames=header)
# 2-dimensional data variable used to write the new CSV
processed_data = []
# append new columns, to receive geocoded information
# to the header of the new CSV
header = list(reader.fieldnames)
for column_name in NEW_COLUMNS_NAME:
header.append(column_name.strip())
processed_data.append(header)
The principle is to build for each row a line address by merging multiple values in one string, based on the list ADDRESS_COLUMNS_NAME
, to pass it to Google Geocoder. For instance, the first line of our csv will become the line address:
"Hairhouse Warehouse, Riverlink Shopping centre, Ipswich".
# iterate through each row of input CSV
for record in reader:
# build a line address
# based on the merge of multiple field values to pass to Google Geocoder`
line_address = ','.join(
str(val) for val in (record[column_name] for column_name in ADDRESS_COLUMNS_NAME))
Geocoding API is able to return limited address results in a specific area. This restriction is specified in the script using the filters dict COMPONENTS_RESTRICTIONS_COLUMNS_NAME
. A filter consists in a list of pairs component:value
. You can leave it empty {}
if you don’t want to apply restricted area.
# if you want to use componentRestrictions feature,
# build a matching dict {'googleComponentRestrictionField' : 'yourCSVFieldValue'}
# to pass to Google Geocoder
component_restrictions = {}
if COMPONENT_RESTRICTIONS_COLUMNS_NAME:
for key, value in COMPONENT_RESTRICTIONS_COLUMNS_NAME.items():
component_restrictions[key] = record[value]
Before call the geocoding method of GeoPy, instantiate a new GoogleV3 Geocoder with your Google credentials, at least the Server API Key.
geo_locator = GoogleV3(api_key=GOOGLE_API_KEY,
client_id=GOOGLE_CLIENT_ID,
secret_key=GOOGLE_SECRET_KEY)
Then call the geocoding method passing the geocoder instance, built line address and optional component restrictions.
# geocode the built line_address and passing optional componentRestrictions
location = geocode_address(geo_locator, line_address, component_restrictions)
def geocode_address(geo_locator, line_address, component_restrictions=None, retry_counter=0):
# the geopy GoogleV3 geocoding call
location = geo_locator.geocode(line_address, components=component_restrictions)
# build a dict to append to output CSV
if location is not None:
location_result = {"Lat": location.latitude, "Long": location.longitude, "Error": "",
"formatted_address": location.raw['formatted_address'],
"location_type": location.raw['geometry']['location_type']}
return location_result
The script retries to geocode the given line address when intermittent failures occur. That is, when the GeoPy library raised a GeocodeError
exception that means that any of the retriable 5xx errors are returned from the API. By default the retry counter (RETRY_COUNTER_CONST
) is set to 5
:
# To retry because intermittent failures sometimes occurs
except (GeocoderQueryError) as error:
if retry_counter 〈 RETRY_COUNTER_CONST:
return geocode_address(geo_locator, line_address, component_restrictions, retry_counter + 1)
else:
location_result = {"Lat": 0, "Long": 0, "Error": error.message, "formatted_address": "",
"location_type": ""}
Other exceptions can occur, like when you exceed your daily quota limit or request by seconds. To support them import the GeoPy exceptions and handle each errors after geocode call. The script also raises an error when no geocoded address is found. The error message is appended to Error
CSV field.
# import Exceptions from GeoPy
from geopy.exc import (
GeocoderQueryError,
GeocoderQuotaExceeded,
ConfigurationError,
GeocoderParseError,
)
# after geocode call, if no result found, raise a ValueError
if location is None:
raise ValueError("None location found, please verify your address line")
# To catch generic and geocoder errors.
except (ValueError, GeocoderQuotaExceeded, ConfigurationError, GeocoderParseError) as error:
location_result = {"Lat": 0, "Long": 0, "Error": error.message, "formatted_address": "", "location_type": ""}
If you’re not customer of Google Maps Platform, you will have to wait between two API Call otherwise you will raise an OVER_QUERY_LIMIT error due to the quotas request per seconds.
# for non customer, we have to sleep 500 ms between each request.
if not GOOGLE_SECRET_KEY:
time.sleep(0.5)
Apart from the Latitude
and Longitude
fields, here are the 3 main results appended to destination CSV file.
The formatted_address matches a readable address of the place (and original line address). This address is most of the time equivalent to the “postal address”.
For each succeeded geocoded address, a geocoding accuracy results is returned in location_type
field. It comes from the Geocoding API service (see Google geocoding Results doc for more information). The following values are currently supported:
Whenever the call to Google Maps API failed, the script will return an error message “None location found, please verify your address line”. For all other errors, the message raised by GeoPy will be appended to the field value. See GeoPy Exceptions for more details.
If you want to go further
This article focuses on the different ways to technically implement a Product Locator on your platform. [...]
Let's start by putting in place the Woosmap Map API! In the video below, you will learn how to implemen [...]
and don't miss a single one of our news