Calculated time of routing is much lower than compared with online GraphHopper

Hi all,

When I run e.g. this in online, it results in 12 minutes.

Doing the same via the Java API locally (using the most recent Belgium map ), it results in 8 minutes; quite a big difference.

This is not an isolated case, comparing some routings with Google Maps shows sometimes big deviations.

I’ve found a topic Improved Feature: Better ETA values announcing from begin 2016 to improve the ETA.

Are my results expected? Can I influence this? Just multiplying with a factor doesn’t seem right since the deviation is different case by case.

Yes, this cannot be part of the open source release.

Are my results expected? Can I influence this? Just multiplying with a factor doesn’t seem right since the deviation is different case by case.

Yes, you’ll need some external data to improve it or heavy heuristics.