Hi,
These tagging issues always make me uncomfortable :)
Against "use_sidepath" in this case:
- it's a trunk road, so no cycling anyway (Wouter)
- the cycle path can be seen as just a path that happens to be near the R4;
it doesn't -really- have a relation with the road itself (escada on Riot)
-
Hey everyone,
We are doing a lot of cycle route planning. 'use_sidepath' is a very
clear hint to us and interpreted as 'don't use', in order to force the
cyclist over the cyclepath just next to it. So please, do add them!
Mvg, Pieter
On 09.04.20 12:27, Jo wrote:
> Since both the highway and the
Since both the highway and the cycleway are separate (mostly parallel)
'entities' in OSM, I think it does make sense to use bicycle=use_sidepath.
For routing purposes, it's probably not needed, while editing in JOSM and
for highlighting using MapCSS it is handy to have the tags directly on the
Hi,
All three are correct in my opinion. Tbh, I've never really understood the
use of use_sidepath. The only case where it contains really helpful
information for me is when that alternative is not mapped. But then there
is a more efficient solution...
But I don't really have anything for or
Hi,
When working on a data extract for the Gents Milieu Front, I stumbled opun
this situation:
On most of the trunk part of the R4, you cannot cycle.
This is expressed in the following ways:
bicycle=no (example https://www.openstreetmap.org/way/306470852)
bicycle=use_sidepath (example
