Some clients have datasets of 200,000 locations, none of which include latitude/longitude coordinates, only U.S. street addresses. Often customers want to know import limitations  including Google’s limit.  As of June 11, 2018 those geocoding limits will change. You will have a pay as you go billing requirement. You  will need to reconsider how to import, how often to import , and whether to break the list into smaller chunks , or skip geocoding, or switch to the MYSLP SaaS managed service.

In order to perform bulk location imports with a CSV file for the WPSLP plugin you will need the Power add-on installed.  WPSLP Power add-on does not alleviate the need for you to obtain your own API key.  MySLP users  do not need to obtain their own API keys but will need the Professional level plan or higher to import and may have limitations according to the plans.

Browser / Connection Timeout

Most web servers and/or web browsers are configured to only stay connected for a short period of time.   If a browser retains an active connection with your web server trying to load a web page it will timeout, disconnecting the process and often stopping the import file from being processed.

The WPSLP Power add on splits the processing into two parts.  The first part loads the file on the server.  Once the file is loaded on the server a background process will read the file in “chunks” where it sends requests to Google for location geocoding.   This allows for far larger lists to be imported and processed without running into browser timeout limits.

Your web server (Apache, nginx, and IIS are the most common) will have a configuration setting that terminates the connection and all running programs when it is exceeded.  This is often set to 30 or 60 seconds.

PHP can also have a maximum CPU/execution time setting that will kill any process exceeded the limit as protection against infinite loops or other process problems.

Google Query Limits

NOTE:  Changes announced as of  JUNE 11 2018:  If this has not changed for you, don’t worry, Google will catch up eventually.  They have complicated the pricing schema and now talk about Product SKUS. The “Product SKU” for all third party apps like our is Maps Javascript, Dynamic Map Pricing . Previously,the  same SKU was used for all JS Maps and Panos map loads. Now,  there is a unique SKU for each.

On shared servers this limitation is shared between ALL sites running on the same server.   Some larger hosts, such as GoDaddy, may run tens-of-thousands of websites on a single server.  You may find your site is “thrown in the pile” with the others and have less than a dozen goecoding requests left for your use each day, or may be slowed down or deprecated.

As of June 11 2018, ALL sites must have a Google API key and have a billing account. In addition Google has changed the way they count over query limits.  This is a big CHANGE.  See the NEW feeds  and Documentation for more info.

Google API Key is managed and charged by Google.

GeoCoding Takes Time

For faster processing or to geocode as many locations as you can in “chunks” it is often best to check the “Skip Geocoding” while doing a CSV import.  This will load all the locations in your CSV file without being encumbered by the slower Google Geocoding process.    Once all locations are loaded us the “Geocode All Uncoded” bulk action.    This will talk to Google in a separate process and geocode as many locations as Google will allow based on your billing and API.

Hints and suggestions from Google for best results

Note that only geocoded locations will show up on the locator search results.

Add Ons That Support This Feature

Enroll in a Premier Subscription
Support product development : Purchase a Premier Subscription
Buy The Power Add On
Buy The Power Add On