Warn about bicycle=use_sidepath with conflicting cycleway tags

[skyper]

cycleway=* together with bicycle=use_sidepath is only valid with cycleway=separate and cycleway:both=separate. Additionally cycleway:right/left=* together with bicycle:forward/backward=use_sidepath is only valid with cycleway:right/left=separate. See ​https://community.openstreetmap.org/t/widerspruchlich-getaggte-rad-und-fusswege/98297/5 and ​https://community.openstreetmap.org/t/widerspruchlich-getaggte-rad-und-fusswege/98297/9.

There might be some more combinations with oneway=yes.

[osm@…]

I hope this table is complete
cycleway (null) o.k.
cycleway(:both) separate o.k.
cycleway:left/right separate/separate o.k
cycleway:left/right no/separate o.k
cycleway:left/right separate/no o.k
cycleway:left/right no/(null) o.k
cycleway:left/right (null)/no o.k
cycleway:left/right separate/(null) o.k
cycleway:left/right (null)/separate o.k

cycleway(:both) !separate wrong
cycleway(:both) no wrong
cycleway:left/right separate/!separate wrong
cycleway:left/right !separate/separate wrong
cycleway:left/right !separate/no wrong
cycleway:left/right no/!separate wrong
cycleway:left/right no/no wrong
cycleway:left/right !separate/(null) wrong
cycleway:left/right (null)/!separate wrong

[GerdP]

Please clarify the description. I use bicycle=use_sidepath often and I see no need to add a tag like cycleway=separate. I agree that a combination like cycleway=both + bicycle=use_sidepath should produce a warning.

[anonymous]

the problem is not the presense or missing of the tag cycleway=separate.

use_sidepath is only to use with an separate mapped cycleway.

so any other value which is defining a cycleway (track/lane/shared/shared_lane/...) along the way without an separate geometry is wrong
also cycleway=no is wrong, because there have to be a separate way!

Have a look in my decision table. (null) stands for no cycleway tag present

[anonymous]

Same for foot=use_sidepath and sidewalk!=separate

[Famlam]

Probably good to exclude any highway that contains bicycle:conditional, bicycle:forward/backward/both_ways:conditional for this check.

There might be some more combinations with oneway=yes.

Be additionally aware of oneway:bicycle, oneway:conditional, oneway:bicycle:conditional in this case :)

[skyper]

Replying to GerdP:

Please clarify the description. I use bicycle=use_sidepath often and I see no need to add a tag like cycleway=separate. I agree that a combination like cycleway=both + bicycle=use_sidepath should produce a warning.

Hope the description is a bit better, now.

Replying to Famlam:

Probably good to exclude any highway that contains bicycle:conditional, bicycle:forward/backward/both_ways:conditional for this check.

I would expect cycleway:conditional or similar then.

There might be some more combinations with oneway=yes.

Be additionally aware of oneway:bicycle, oneway:conditional, oneway:bicycle:conditional in this case :)

Yes, I am aware of oneway:bicycle. For *:conditional again, I would expect all tags to carry the suffix.