Yes but how can I figure it out that its to short? We even multiply by factor 2 (not 1.5 as suggested) and the results are (of course) not optimal, because as you said the max_time_in_vehicle is to small if we set the direct travel way as base.
It seems that theres no current way over you API to achieve this without some more computation on our side (or in just a few calls of your API), isn’t it?
Okay, after playing around with the API, it seems that the suggested solution doesn’t work on all or the most routing cases.
Solution for us is now to request for all possible route-start-points, get the length of the resulting routes and use the shortest track of all of them.
This increases our API-Calls massively, so this solution is very expensive for us.
We would really appreciate a better solution over your API 