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

[Peter Elderson]

Option 1
addr:range=* specifies the increment

addr:range=even
addr:housenumber=2..250

if .. is used, a hyphen combined with a range can be handled.

addr:range=odd
addr:housenumber=200-01..200-91

In these examples, a default of 2 would simplify things: .. infers a range,
increment is default 2 and - is never a range indicator.

Error to be expected: people just copying the housenumber plate may use
2-250.
When using the explicit addr:range tag, the format error may be detected
because .. is missing.

Peter Elderson


Op do 24 dec. 2020 om 15:12 schreef Paul Allen <pla16021 at gmail.com>:

> On Thu, 24 Dec 2020 at 10:14, Martin Koppenhoefer <dieterdreist at gmail.com>
> wrote:
>
>> maybe we should add an expression marker, like {10..20} to make it more
>> explicit and avoid confusion with typos?
>>
>
> In programming, you also have the ability to define the increment,
> which defaults to 1 if left unspecified.  That way you can distinguish
> between 10, 11, 12, 13, 14, 15, 16 and 10, 12, 14, 16 (or even
> 10, 13, 16).  You could argue that for addresses the increment
> ought to default to 2, since that is most commonly encountered.
>
> --
> Paul
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20201224/ab3b449d/attachment.htm>