Why does graphhopper not use the obvious route?

Help and support
1

I do not see what is wrong with the road that would be the direct connection start-1-2-3-goal. Bosch Flow App has the exact same problem, so it has to be in the map.

2

I think is the sac_scale=mountain_hiking tag on this way: Way: 113716774 | OpenStreetMap

1 Like
3

Thanks. This road is by far the best in the whole area. I cycled it some days ago. It is 3-4 meters wide and not to steep, suitable for wood transport and cars. The route I posted above contains footpaths and other unridable stuff. I looked up sac_scale=mountain_hiking (I am new here) and this is not correct for this road. Can you please remove it or what is the next step?

4

Das hört sich sehr danach an, als wäre tracktype=grade2 ok, sac_scale=hiking ausreichend und vermutlich wäre surface=compacted passender als surface=pebblestone. Es sieht nicht nach Absturzgefahr aus. Vor-Ort-Kenntnis ist jedoch hilfreich.

Du kannst das selbst korrigieren.

5

Ich habe es geändert. Danke für eure Hilfe.

1 Like
6

That is an interesting take if you look at their backend :smiley:

They are using graphhopper with custom routing profiles :)

1 Like
7

Interesting, thanks. Here are the credits in the flow app. OSM ist mentionend, graphhopper not.

flow credits
flow credits349×366 13.8 KB

1 Like
8

It now works as expected in Graphhopper