<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Jun 7, 2021, 16:50 by f@zz.de:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On Sun, Jun 06, 2021 at 10:50:54PM -0400, Jmapb wrote:<br></div><blockquote><div>What do folks here think of the barrier=kerb + kerb=lowered combo? I've<br></div><div>started seeing it a lot with mappers micromapping crosswalks.<br></div><div><br></div><div>Offhand, it seems like textbook troll tagging to me, negating a tag with<br></div><div>its own subtag. If the kerb has been lowered so that the footway is<br></div><div>level with roadway, then not only is there no kerb but there's no<br></div><div>barrier at all. Exactly the opposite.<br></div><div><br></div><div>Currently the wiki doesn't indicate that kerb=lowered and other kerb=*<br></div><div>values are intended to be subtags of barrier=kerb. But it doesn't say<br></div><div>they shouldn't be, either.<br></div><div><br></div><div>https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dkerb<br></div><div>https://wiki.openstreetmap.org/wiki/Key:kerb<br></div></blockquote><div><br></div><div>I am bit annoyed by barrier=kerb. kerb=lowered is perfect for me.<br></div><div><br></div><div>The point is that a lot of software assumes barrier=* to be impassable<br></div><div>as long as there are not other positive modality tags on it like<br></div><div>bicycle/foot etc.<br></div></blockquote><div dir="auto">Such software will be confused by barrier=bollard and barrier=height_restrictor.<br></div><div dir="auto">And some other values.<br></div><div dir="auto"><br></div><div dir="auto">And for pedestrians by barrier=stile, barrier=kissing_gate, barrier=turnstile.<br></div><div dir="auto">And some other values.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto"> Which IMHO would be a perfect abstraction. A software<br></div><div>which only want navigation only needs to check for barrier=something<br></div><div>and then check modality. But instead we already overloaded<br></div><div>barrier=bollard etc with implicit modality tags, and with barrier=kerb <br></div><div>we overloaded it again with kerb=* tags.<br></div><div><br></div><div>So for barrier=kerb. Its a barrier for a lot of Software.<br></div><div><br></div><div>For example OSRM treats it as a barrier, or better it did. For OSRM the<br></div><div>barrier=kerb+kerb=lowered has been fixed for the car profile in March,<br></div><div>but not so for bicycle and foot profile. So today we had a strange<br></div><div>bicycle routing because of this on the regional mailinglist which<br></div><div>was caused by a barrier=kerb + kerb lowered. All except one barrier=kerb <br></div><div>had been removed already so it was a hard find.<br></div></blockquote><div dir="auto">Adapting software will be likely easier than deprecating all barrier=* values<br></div><div dir="auto">that are not completely blocking.<br></div> </body>
</html>