When routing from A to C one passes a point B mentioned in the GPXList of the PathWrapper of the best route. Let’s call the timestamp when B is reached in the GPXList tB.
If we now request a route from A to B, then we’d expect that the result of getTime(), let’s call it tAB, called on the PathWrapper of the best route will result in the identical, or at least nearly the same, time as tB.
However, there are cases when this is not the case and these times differ by several seconds (e.g. 9 seconds).
Is this intended behavior? Is there any way to disable these seeming inconsistencies?
Note: tBC, the time for the route between B and C, plus tAB do sum up to the same time as the time of the route from A to C for this sample.
I use Grahphopper-Reader-OSM and Graphhopper-Core, both version 0.10.3, set hopper.setMinNetworkSize(200, 200), and set the weighting to “fastest” and the vehicle to “car” for all requests.
In case it is requested, I can provide an example of points where this issue occurs.