We do a precheck for new appointments using the routing API (because it is less expensive then route optimization API) to make sure that a driver could get there from the previous appointment in time and also to the next appointment.
However, when we go to optimize the route with GH sometimes appointments fail. The reason is because the distance and driving_time metrics can vary - sometimes significantly. Also neither API is consistenly shorter then the other
Anyway around this other then using a “buffer” from the routing API result?
source: 43.7252454, -79.3321048 destination: 43.6699782, -79.2862945 Routing API 1084 drive time 13.0 distance Optimization API 919 drive time 9.4 distance