title: Route optimization with more than 25 stops using MapQuest API
body: <p>So, I have a service, which as one of its features allows my clients to optimize their driving routes for the day. Normally, they only have a dozen or so stops before returning to base, so I just use the MapQuest API (paid) which has an optimize route function. However, I just got a new client who has 40+ stops per day. However, the MapQuest API only allows 25 stops (start, 23 waypoints, end) with route optimization. So, does anyone have any ideas how I can best attack the problem of trying to optimize a route for 40+ stops?</p>
  
  <p>So, yes, I know that the traveling salesman problem is a computationally difficult problem. The MapQuest API is super fast with the limited number of stops that they allow, and I have a paid subscription, so I can make multiple calls in a row without getting in trouble with them. So, some ideas that I've played around with is simply dividing the route in half, optimizing each half, and combining, but it seems to be lacking in efficacy. So, if anyone has tackled this, I'd love to hear your solution.</p>