Is there a way to increase the maximum tower node distance, so it doesn’t get reset to “a large number”?
Note: I am aware that this (normally) only occurs, if there is an error in the OSM dataset. I am working on an experiment where this is not the case though
Currently not, but you can edit EdgeAccess to work for larger distances better (e.g. tweak
See also this related issue: https://github.com/graphhopper/graphhopper/issues/435
Thank you very much!
I never expected the problem to be the number an integer can contain
Since I have control over the imported data, I will try splitting the longest ways into smaller chunks, so I won’t run into this issue – a little workaround, but you even suggested that for implementation in Graphhopper.