Number of Unique Addresses Optimization (Max 25?)

4 posts / 0 new
Last post
DHS2016
Number of Unique Addresses Optimization (Max 25?)

It appears that the number of stops to maximize is 25?   If a driver has 30-40 unique addresses they visit per day, is there an option in the directions API to optimize the directions? or, is there any other API option or toolset?


MQBrianCoakley
Nope, the limit is 25. You
Nope, the limit is 25. You can submit multiple requests to optimize the 40 locations, but only 25 locations per request.

DHS2016
Thank you, Brian. Can you

Thank you, Brian. Can you expound more on sending multiple request for the 40 locations? in that example would  we send locations 1-25 and then send locations 26-40 and have them optimized separately. When you submit multiple request, what is the best practice? What have others done in this situation? For instance, if we had a limit of 3 locations and I needed to optimize 6--are you saying i would send ABC and then send DEF. It would give me me BAC and then FDE and so I have two groups of optimized locations? 


MQBrianCoakley
It all depends on what the
It all depends on what the application is doing. Generally, the application would want to do some clustering to find if any locations are close to each other and can be considered one group to be optimized and then used as a single location in a more general group to be optimized. But if there is no cluserting, then the potential groups would all need to be submitted. So ABC, ABD, ABE, ABF, ACD, ACE, ACF, etc, would need to be submitted for best results. This can add up transactions real fast though. So clustering locations before routing is a good start to the process. Sorry, I don't have any clustering code on hand. But it should be out on the internet somewhere.