Batch Processing allows you to import a .csv or .xlsx file containing origin/destination pairs, and export a file containing the mileage, duration, and cost estimates using your preferred route processing settings.
Import Wizard
To get started, navigate to the Batch Processing tab in the top navigation bar.
Batch Processing supports both Guide 20 and Guide 19. Guide 20 is the default.
You can import a .csv or .xlsx file. The import wizard supports various formats, and an example file can be viewed by clicking the 'Download Sample' button.
After importing the file, the user must select which columns from the import file to use as the origin, and which to use as the destination. The import wizard supports both parsed data (separate columns for address, city, state) and concatenated data (address, city, state, zip code, all in one column).
After choosing the origin/destination columns, the user must select the route processing settings. The same route templates available in the application can be used here, or you can select "create template" to configure the settings manually.
Resolve Issues
Routes may fail to be calculated if MileMaker cannot find an unambiguous search result from the input string. When this occurs, you can attempt to resolve these issues by clicking the more options menu for your batch, and click "Resolve Issues."
You can adjust the input string for the failed locations, and select the appropriate search result from the list below. After resolving one or more issues, you can click the 'Resolve Issues' button to reprocess the routes that failed with the corrected location.
Result File
To download the result file, click on the more options menu of the batch, and click "Download"
You can then choose between two formats for your export file, .xlsx or .csv.
The first sheet of the export file contains the route processing settings:
The second sheet of the result file contains the origin and destination strings used to calculate the routes, and the distance, duration, and cost estimates.
Comments
0 comments
Please sign in to leave a comment.