Extend oneway-Quest for cycleway's

[mcliquid]

Use case The oneway quest currently appears only on narrow roads (e.g., width ≤ 4 m, lanes ≤ 1). This skips many pieces of bicycle infrastructure where directionality matters for routing and legality, such as highway=cycleway and highway=path with bicycle=yes|designated. In practice, these ways often remain without oneway information even when they are effectively one-way.

Proposed Solution

• Include bicycle facilities as eligible: Treat highway=cycleway and highway=path with bicycle=yes|designated as candidates for the oneway quest regardless of width/lanes. Keep the existing global constraints (!oneway, area != yes, junction != roundabout) so already-tagged or non-linear features are still excluded.
• Ensure they enter the candidate pool: Add the above bicycle ways to the initial “all roads” set used for connection counting; otherwise they are filtered out before eligibility is evaluated.
• Connectivity criterion tailored to bike ways: For the bicycle cases, require connectivity at at least one end (many cycleways terminate at a ramp or transition). Keep the current “both ends connected” check for regular roads to preserve existing dead-end/bounding-box safeguards.

Expected result: the oneway quest is also offered on cycleways and designated bicycle paths (even if wide and only connected on one end), improving completeness for bicycle routing without changing the quest’s UI or workflow.

[Helium314]

If we want to ask regardless of width, should we add additional filters to avoid asking everywhere? E.g. requiring a nearby cycle path that's not directly connected (assuming there is one in the other direction, though this should also consider lanes), exclude non-segregated bicycle/foot paths, country filter, ...

[mcliquid]

I'm happy to hear other opinions, but I don't see any disadvantage in displaying the quest "everywhere". The information is similar to segregated=*, smoothness=*, or surface=*. What could be filtered anyway if needed:

• Filter for ispaved, because most probably unpaved ways are not oneway at all?
• Filter for is_sidepath, because they are most likely oneway=yes?

[Helium314]

I don't see any disadvantage in displaying the quest "everywhere".

I'm a little afraid about this being considered unwanted by other mappers, e.g. in Poland only very few cycleways are oneway (https://github.com/streetcomplete/StreetComplete/issues/4827#issuecomment-1437975649) And I can't remember any non-segregated bicycle & foot one-ways (but that might differ by region).

• Filter for ispaved, because most probably unpaved ways are not oneway at all?

Sounds reasonable, though anything MTB-related should still be asked

• Filter for is_sidepath, because they are most likely oneway=yes?

Actually none of the examples in the is_sidepath proposal are clearly one-way

[mcliquid]

For the moment, I'm leaving the quest locally activated and observing whether I can identify patterns for further filtering. :)