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)
IpswichMapper --- 21 Dec 2020, 19:44 by kevin.b.ke...@gmail.com: > > > On Mon, Dec 21, 2020 at 2:15 PM ipswichmapper--- via Tagging <> > tagging@openstreetmap.org> > wrote: > >> What do you mean by this? You would have to tag with addr:range=no, as that >> is not a default value. >> >> 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. >> > > 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? > > > -- > 73 de ke9tv/2, Kevin >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
