nomennominatur

Hi! Thanks for your reply! Maybe it was just my fault, not being deeply familiar with the cyclosm layout style, however, yes, I think that many people might confuse different...

Additional comment: The confusion may be increased (as in my example) in case there is a change of several path attributes at the same junction or geographical position (i.e. change...

**Brainstorming/ first draft of proposal how to potentially render restricted paths:** IMHO, a rendering of access=no / bike=no should fulfill six criteria: 1. Current CyclOSM rendering should not be uprooted,...

Another afterthought: I have heard that in some countries (e.g. Austria), municipalities seem to deny access to recreational paths on bikes by default. In order to refrain from overwhelming such...

You are right, I admit that I was initially mistaken in reading the cyclosm path rendering. I should have properly read the legend first (apology for that). Nonetheless, I feel...

I think that, in a way, it is OK to honour the OSM principle to „map what is on the ground“. Thus, if a path is physically there, and if...

**What about this alternative rendering of restricted paths?**  By filling only every other space between ticks, - line colour will still be visible, - ticks will still be visible,...

@Phyks , @Florimondable Any opinion on the above?

Key:hazard=falling_rocks is technically correct, however, taginfo shows, that this attribute is very, very rarely mapped (global count less than 160 instances), so this may not be worth pursuing.