<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>How would this break routing and navigation? As far as I know, geocoders currently read hypenated addresses as ranges anyway (correct me if I'm wrong) so this proposal won't change what happens to hypenated addresses without addr:range tag. (Ime. Navigation is already broken in NYC)<br></div><div><br></div><div>IpswichMapper</div><div><br></div><div>---<br></div><div><br></div><div><br></div><div>21 Dec 2020, 19:44 by kevin.b.kenny@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div dir="ltr"><br></div><div><br></div><div class=""><div class="" dir="ltr">On Mon, Dec 21, 2020 at 2:15 PM ipswichmapper--- via Tagging <<a href="mailto:tagging@openstreetmap.org" rel="noopener noreferrer" target="_blank">tagging@openstreetmap.org</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=""><div><div>What do you mean by this? You would have to tag with addr:range=no, as that is not a default value.<br></div><div><br></div><div>However, don't see this as a downside. Currently, software such as OSMand interprets hypenated addresses as a range anyway, so requirement to tag addr:range=no would be a benefit.<br></div></div></blockquote><div><br></div><div>Ouch. So every building in Queens, NY (one of the five boroughs of New York City, with about 2.3 million inhabitants) would need to have an 'addr:range=no' tag added in order not to break routing and navigation there?<br></div></div><div><br></div><div><br></div><div>-- <br></div><div class="" dir="ltr">73 de ke9tv/2, Kevin<br></div></div></blockquote><div><br></div> </body>
</html>