Fallback values for highway=cycleway + bicycle_road=yes

[tordans]

A rendering cyclosm/cyclosm-cartocss-style#629 (comment) started a talk locally about the best tagging to describe a road that is only for bikes but build like a residential or service road. We are using highway=cycleway + bicycle_road=yes for that.

Example:

• OSM https://www.openstreetmap.org/way/859427215#map=18/52.48412/13.44547 (the issue here)
• Mapillary https://www.mapillary.com/app/?pKey=1287704951654498&focus=photo

That brings me to the question of which values osm2lanes should fall back to if none are given for width, surface and such.

My argument in that thread is, that in this combination, the highway should be treated like residential or service in term of how it is build but like a cycleway in terms of its function.

I don't know how far the "local fallback values" "database" has grown in osm2lanes, but that might be something to look at.

Looking at https://a-b-street.github.io/osm2streets/#19.5/52.48473/13.44443, the bottom segment that I describe above looks great already. Its move the bicycle_road=yes segment to the north, that is not shown as such. That that is a-b-street/osm2streets#77 I guess.

Feel free to close if you think there is no relevant action here.

---

Ping @SupaplexOSM FYI

[westnordost]

In the interest of keeping the scope of this project manageable, I'd suggest to at least strictly separate any "fallback/defaults smartness" from the pure interpreting of the tags that are given.