<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>That is an irritating case.<br></div><div dir="auto"><br></div><div dir="auto">1) with you assumptions it is possible to argue that it refers to case where<br></div><div dir="auto">there is a separately mapped sidewalk that nevertheless is inaccessible<br></div><div dir="auto">(some technical/escape route in a tunnel or on motorway?)<br></div><div dir="auto"><br></div><div dir="auto">2) in practise it is far more likely to be used in case where user tags each<br></div><div dir="auto">way with own access tags.<br></div><div dir="auto">Basically<br></div><div dir="auto">> that foot=* applies to "the whole of the road" including the roadway,<br></div><div dir="auto">> shoulders, verge, sidewalks, and so forth<br></div><div dir="auto">has added at the end<br></div><div dir="auto">> "unless represented with separate geometry"<br></div><div dir="auto"><br></div><div dir="auto">3) to avoid problem from (2) foot=use_sidepath was invented to mark<br></div><div dir="auto">"yes, on carriageway you cannot walk, but you can walk on separately<br></div><div dir="auto">mapped sidewalk"<br></div><div dir="auto"><br></div><div dir="auto">-----------------------------------------------------------------------------------------------<br></div><div dir="auto"><br></div><div dir="auto">practical advise:<br></div><div dir="auto"><br></div><div dir="auto">- if there is no separately mapped footway then sidewalk=separate<br></div><div dir="auto">is wrong and should be fixed<br></div><div dir="auto">- if pedestrian cannot walk on carriageway and can on sidewalk<br></div><div dir="auto">and it is separately mapped then use foot=use_sidepath instead<br></div><div dir="auto"><br></div><div dir="auto">-----------------------------------------------------------------------------------------------<br></div><div dir="auto"><br></div><div>No idea:<br></div><div dir="auto"><br></div><div dir="auto">- how to tag situation from (1) that distinguishes it from case (2)<br></div><div dir="auto"><br></div><div dir="auto">Not sure:<br></div><div dir="auto">- should we treat foot=no instead of foot=use_sidepath in case (2)<br></div><div dir="auto">as invalid data<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div>Would folks regard that as accurate data modeling? I.e. should I change my software to treat streets tagged in this way as pedestrian-accessible, or would folks regard this combination as a tagging error?<br></div></div></blockquote><div dir="auto">For start, is there a separately mapped sidewalk geometry there?<br></div><div dir="auto">If no then tagging is invalid.<br></div><div dir="auto">If yes, then I personally would be treating as invalid data and assume road to be <br></div><div dir="auto">pedestrian accessible, maybe flag is worth reviewing and ask users for feddback<br></div><div dir="auto">what is going on there and ask for photo.<br></div><div dir="auto"><br></div><div>18 gru 2022, 21:29 od zelonewolf@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div>Hello,<br></div><div><br></div><div>I am the author of a data consumer which generates a list of streets that are accessible to walkers and joggers. The idea is that a user would have a map of the streets in their town and can challenge themselves to walk/jog down every street, and they can look at statistics on which streets they've completed. I use a 25-meter rule, so if a user can walk along the shoulder, or on a sidewalk/pavement, or in the verge, that's acceptable.<br></div><div><br></div><div>I recently came across an unexpected tagging combination and I would like to understand how folks in various places would interpret this:<br></div><div><br></div><div>highway=<whatever><br></div><div>foot=no<br></div><div>sidewalk=separate<br></div><div><br></div><div>In my software's logic, I've made the assumption that foot=* applies to "the whole of the road" including the roadway, shoulders, verge, sidewalks, and so forth and thus excluded any roads that include that tag, regardless of other tagging. I came to understand that this tagging was used by a mapper to indicate that "pedestrians are not allowed on the roadway, however, they are allowed on the sidewalk"<br></div><div><br></div><div>Would folks regard that as accurate data modeling? I.e. should I change my software to treat streets tagged in this way as pedestrian-accessible, or would folks regard this combination as a tagging error?<br></div><div><br></div><div><br></div></div></blockquote><div dir="auto"><br></div> </body>
</html>