Geocoding Errors

Google will return various error codes depending on the data format or request timing. The following table of errors and their meanings will help you determine what is going on when Google tries to lookup up your location coordinates. The most common issue is reaching your quota limits or missing your Google API Key.
Continue reading “Geocoding Errors”

Q: Some of the Map Markers are not where I know they should be how do I fix this?

When a location is added into your SLP data set, you will see a message “Store Locator Plus wants you to know:”  and the output of the Latitude and Longitude where Google thinks the location is.

For Example, I added Sydney Opera House and no street address, just name, the city and the country Australia:

“Google thinks Sydney Australia is at lat: -33.8674869 long 151.2069902”
Continue reading “Q: Some of the Map Markers are not where I know they should be how do I fix this?”

Q: My Locations Will Not Geocode. Why?

Whether doing a bulk import or adding locations by hand there are times when you will see a “location uncoded” or “cannot geocode” error message.     This is always the result of an address that was sent to Google that cannot be processed in their address location system.
Continue reading “Q: My Locations Will Not Geocode. Why?”

Q: How Does Store Locator Plus Handle Large Location List Imports?

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 to including Google’s limit of 2,500 daily requests.

In order to perform bulk location imports with a CSV file you will need to the Power add-on installed.  The following constraints can keep the locations from loading or cause slower processing.

Continue reading “Q: How Does Store Locator Plus Handle Large Location List Imports?”

Importing Large Lists into Store Locator Plus

Import features are available with the Power Add-on

Load Data

If checked , use the faster MySQL Load Data method of file processing. Only base plugin data can be loaded, see the approved field name list.

This feature uses the MySQL Load Data command and is much faster than WordPress / PHP CSV file parsing, with the typical Google Geocoding limitations on performance and record counts (if you are not supplying, filling in the latitude/longitude data fields). This feature will only import basic location data. It does not import extended data fields or (Tagalong) category data. If you use this along with  pre-entered latitude and longitude values you can import 100,000 locations in less than 10 minutes on a basic web server. The column headers must be included in the file and must match the basic fields. You do NOT need to include all columns.
Continue reading “Importing Large Lists into Store Locator Plus”

Location Imports

Location Imports are handled via a CSV file for users that signed up for the MySLP Power service or are using the WPSLP Power Add On.

CSV Import Format

Getting the proper CSV format can be a challenge when using spreadsheet apps like Excel or Numbers.  Here are some tips to getting a valid CSV format out of a spreadsheet app:

  1. Make sure you always have a header row.  That tells the import process what data is in each column.   The column headers have meaning, so be precise.
  2. When a cell is a text field that STARTS WITH A LEADING ZERO, make sure you explicitly mark the cell as text.   The easiest way to do this is to type a single apostrophe then the number when adding data to the cell as in ‘01886 for the zip code 01886.
  3. Always export with UTF-8 support enabled.
  4. Export to a CSV format.  Comma delimited not tab delimited and quoted strings if given the option.

Check out the Example CSV Imports post to get some usable import files you can play with.

Continue reading “Location Imports”