GraphHopper.com | Forum | GitHub | Maps | Blog

Weird routing for MTB


#1

Maybe wrong thread but think that Graphhopper gives me wrong routing based on how I want. I think that all paths are connected and excpected a route straight through the forest rather than around it. I think it looks alright in OSM. https://graphhopper.com/maps/?point=58.267937%2C13.611932&point=58.268366%2C13.636737&locale=sv-se&vehicle=mtb&weighting=fastest&elevation=true&use_miles=false&layer=Omniscale


#2

As this way is a highway type path and the BikeFlagEncoder describes path highways as a pushingSection (where you have to walk and can’t go by bike), I think it is faster to drive around the forest instead of walking through the forest.

Correct me if I’m wrong :slight_smile:


#3

Know what? All of a sudden it´s working again! Paths is gladly used by MTB (maybe not by standard bicycles?) but under a period of time it wouldn´t go through the forest but now it works!


#4

Oh sorry, I oversaw it, that you used the mountain bike instead of the normal bike. So you are correct, MTB doesn’t have that restriction in the open source version.

Maybe there was some data change in openstreetmap or something, that influenced it. I’m not a developer of graphhopper, so I don’t know.