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 category data. If you use this along with per-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.
Location Imports are handled via a CSV file for users that signed up for the MySLP Professional service or are using the WPSLP Power Add On. With MYSLP the import feature is under the StoreLocatorPlus sidebar/locations as shown in screenshot. If you are using WPSLP self managed and have the Power add-on it will look similar.
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:
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.
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.
Always export with UTF-8 support enabled.
Export to a CSV format. Comma delimited not tab delimited and quoted strings if given the option.