[Tagging] Feature Proposal - RFC - addr:interpolation on closed ways and nodes

[ipswichmapper at tutanota.com]

Turns out nominatim just doesn't do ranges at all. I.e. if you label a building 40-48 xyz street and then search 42 xyz street it won't show up. OSMand, however, does assume that they are ranges.

I see two solutions:

1. Have no default value and geocoders will do whatever they already do with hypenated addresses.
2. Default value is addr:range=no and it has to be specified if you want a geocoder to assume its a range.

Thanks,
IpswichMapper
-- 
 

21 Dec 2020, 19:50 by ipswichmapper at tutanota.com:

> 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.kenny at gmail.com:
>
>>
>>
>> On Mon, Dec 21, 2020 at 2:15 PM ipswichmapper--- via Tagging <>> tagging at 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
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20201221/5bb1bb93/attachment.htm>