<div dir="auto">Let me try to describe the basic problem: we are interpreting the key "oneway" with two different meanings:<div dir="auto">(1) "restrictions for the flow of vehicle-only traffic" for example in the widely used case of mixed-use foot-cycle-ways that are one-way for bicycles. </div><div dir="auto"><br></div><div dir="auto">(2) "restrictions for the flow of any type of traffic, including pedestrians" when we talk about using oneway:foot=yes|no|-1</div><div dir="auto"><br></div><div dir="auto">That cannot work unless you can neatly separate the two domains of applicability, which we can't as we have mixed-use ways.</div><div dir="auto">We are discussing in circles around that issue.</div><div dir="auto"><br><div dir="auto">It looks as if definition (1) above is widely used whereas (2) much less so.</div><div dir="auto">To me the logical conclusion is we need a separate new key for (2). Let's define it to be the string of (meaningless) characters "oneway_foot". We need to add that all ways with the key "highway" carry by default "oneway_foot=no" in addition to the default "oneway=no".</div><div dir="auto"><br></div></div><div class="gmail_quote" dir="auto"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
</blockquote></div></div>