Cycleway tag is not taken into account for bike FlagEncoder

Open Source Routing Engine
1

Sometimes streets have an additional cycleway tag (not to be confused with highway=cycleway) indicating that there is a designated bike lane along this road (that is not mapped as a separate highway): https://wiki.openstreetmap.org/wiki/Key:cycleway

For example this route should probably go straight instead of taking the detour using the residential road: https://graphhopper.com/maps/?point=51.664251%2C7.079626&point=51.666613%2C7.078371&locale=de&vehicle=bike&weighting=fastest&elevation=true&turn_costs=false&use_miles=false&layer=Omniscale

Update: I created this issue for this: https://github.com/graphhopper/graphhopper/issues/2074

2

It seems that we completely miss cycleway=track. We only consider cycleway=opposite* for oneway stuff (is this correct @ratrun?). @easbar can you create an issue for this? Strange that we do never stumble over a problem before as this value exists 100k world wide.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.