On Tue, Aug 18, 2020 at 11:26 AM Colin Smale <colin.sm...@xs4all.nl> wrote:
> There are two use cases here: one is "what is the address of this building > (or whatever)" and the other is the reverse situation: "where can I find > number XXX". As long as we have tagging that is potentially ambiguous we > won't be able to cover both. > > In the US I know of cases where an apartment number can follow the street > address, i.e. 10-321 meaning Street Address 10, apartment 321. In Europe I > know of the suffix being used to indicate apartment number, or floor number > - e.g. 379-3 meaning Street Address 379, Floor/Flat 3. Sometimes other > characters are used for the floor/flat such as A/B/C or I/II/III - in these > cases it is unambiguous because it is non-numeric. > Can you point out some examples? I've never seen that syntax used in US addresses. On the other hand using the "1-5" notation to indicate a range is pretty > well understood in the UK at least. What it is missing is the > "interpolation" value (even, odd, all). > > So let us sort this mess out by defining: > 1) that a hyphen indicates a range > 2) sub-addresses like a floor or apartment number must not use the hyphen > notation, but must be given in addr:unit > 3) an address using the range syntax should indicate the interpolation > scheme by means of addr:interpolation=* > This leaves the situation in Queens, NY unsolved, where hyphenated addresses do not indicate ranges.
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
