Lukas Kabrt

Update: The problem is related to the edge based graph * if I set `ProcessRestrictions = false` all distances are computed correctly * if I set `ProcessRestrictions = false` and...

I was able to reproduce the problem on an even smaller network (just 3 vertices and 2 edges). See [minimal-example.osm.pbf.zip](https://github.com/itinero/routing/files/4111945/minimal-example.osm.pbf.zip)

@xivk Yes, the same code with `forceEdgeBased: true` flag can be used to reproduce the issue with the tiny network. Absolute values of weights are little different than in the...

Unfortunately it doesn't seem to be fixed ... if I download source code form #302 and try to run code from https://github.com/itinero/routing/issues/293#issuecomment-578402556 to reproduce the bug, I still get different...

It seems to be fixed for the minimal repro case. But if I use larger network from the first comment (https://github.com/itinero/routing/files/4061607/prague-small.osm.pbf.zip) the issue is still there.

I haven't tried `GetAugmentedWeightHandler`, but over the weekend I might have a time to try it. You can easily reproduce the issue with the source code from https://github.com/itinero/routing/issues/293#issuecomment-578402556 and https://github.com/itinero/routing/files/4061607/prague-small.osm.pbf.zip...

> I see so essentially just change the pbf file for the one linked instead of the minimal and I should be able to reproduce with the same test case?...

Solution that works for me: * set `touch-action: pan-y` CSS style on the slider * set `behavior: none` in the slider initialization - users can't tap the slider to set...