[Tagging] Tagging cycleways to distinguish them from combined cycle and footways

Jeroen Hoek mail at jeroenhoek.nl
Wed Aug 3 07:31:09 UTC 2022


On 02-08-2022 23:42, Jens Glad Balchen wrote:
> Pedestrians are compelled in the Norwegian highway code to use
> footways, sidewalks, or the road's shoulder, except when or where
> that wouldn't be possible, practical, or safe. In these cases
> pedestrians may use cycleways, cycle lanes or carriageways (cycleway
> and carriageway in this context meaning the part of the road meant
> for regular vehicle traffic, so not including the hard or soft
> shoulder).

Does this mean that if there is a road with a parallel highway=cycleway,
pedestrians must use the road's shoulder instead of the cycleway?

In the Netherlands if a road has a cycleway (not lane) parallel to it, 
pedestrians must use these instead of the road, unless sidewalks or 
other parallel pedestrian specific footways are present; then the 
cycleway may not be used either. To mark those cases where the 
pedestrian path is mapped separately, we use foot=use_sidepath (on the 
road and sometimes on the cycleway as well). This is like foot=no, but 
it explains more clearly why pedestrians may not use it. It basically 
means that while there is no traffic sign forbidding pedestrians, the 
law says that there is a parallel (separately mapped) way you must use.

You didn't mention that tag, so I would recommend reading up on that one 
to see if it may fit for some of your examples. Similarly, 
bicycle=use_sidepath is very useful for a good cycling map.

> A cycleway with a sidewalk is tagged highway=cycleway +
> foot=designated + segregated=yes + sidewalk=left/right.

You can omit segregated=yes here, because sidewalk=left/right implies
it. The segregated=* tag is mostly meant for cases where there is
segregation of pedestrians and other traffic, but no sidewalk (often 
width highway=path). Including
it isn't bad per se, but may cause maintenance issues because mappers
have to update sidewalk=* and segregated=* in tandem.

I can also recommend defining presets for use in ID and JOSM. That helps 
set most tags right in one go. In the Netherlands we include the 
relevant traffic sign as well (so other mappers know on what basis the 
access tags where set), and add the correct mofa=* and moped=* access tags.

Example:

https://www.openstreetmap.org/way/125595300



More information about the Tagging mailing list