Checking with
area[name="Nordrhein-Westfalen"];
way(area)[highway=footway][!bicycle][oneway][oneway!=no];
out geom;
turned out that all were either mapping errors or intended to be meant for pedestrians. North Rhine-Westphalia has 22% of the German population and is thus already a quite comprehensive sample, and I happen to have seen many places there.
To make this a good rule, it should be also tested against bicycle=no
in addition to the absence of bicycle
. Afterwards, a pedestrian router can safely follow the rule:
- if
highway=footway
is set andbicycle
is absent then process it as a oneway for pedestrians - ignore the
oneway
for pedestrians in all other cases ofhighway=footway
or a variant that includes bicycle=no
along the no bicycle
tag exemption. Bonus points for looking into highway=steps
. Not claimed to be solved here is highway=path
or highway=pedestrian
(or any other highway
value), denying scope creep.