Hi,
It appears that the production directions API is not applying the 90% max speed limit as part of CarAverageSpeedParser and it is instead using the max speed as the speed of the vehicle. This results in unrealistic driving time ETAs. I’m not sure if this is expected, but it seemed odd so thought it was worth bringing it up.
Example route:
When calculating the same route on the master
branch of the graphhopper repository it applies the limit and thus the total route duration is about 7 minutes slower.