Powering route optimization systems with blazing fast distance matrix calculations
/route/batch
endpoint for processing multiple route requests efficiently in a single API call. This enables:Solvice Maps Demo Page
/cube
endpoint/table
endpoint), but Route Optimization systems require multiple slices throughout the day.
Ideally one for every 5 minutes in the day in order to get the travel time as granular and accurately as possible.
However, if you would want to solve a 1000-jobs VRP request, you would need 288 matrices of 1000x1000 elements.
That would be quite cumbersome to first calculate and then secondly hold in memory during the solve.That is why we are introducing a /cube endpoint to fetch the entire 3-D matrix or what we call cube. 288 slices is too much but what if we can approximate it with a function?
A polynomial that reduces the necessary slices. Read more in the /cube
introductionIncrease granularity with the Travel Coefficient Cube
TomTom traffic integration