A tip from CRM systems: addresses have a specific role, just like we
have multiple phone numbers: one for work, one for home, mobile, fax
etc., we can also have multiple addresses. One may be the legal address
of a company, one for postal deliveries (possibly non-geographic such as
a Postbox number), one for navigation purposes, one to identify the
building..... all leading to the same location, but from a different
perspective. If it is "too difficult" to have address roles, try
defining which "role" the OSM address is intended to represent. They
might all be correct, but just from a different perspective. Why are the
addresses in OSM in the first place?
//colin
On 2017-03-18 18:37, Janko Mihelić wrote:
> Imagine a data consumer trying to find out the address of all those stores.
> Not only is it hard because you have to find surrounding areas and extract
> the address, but in your case it's impossible because you can't know for sure
> which entrance it took its address from. What's your solution to that? The
> only solution I see is relations, but IMHO that would be a mess.
>
> Janko
>
> On Sat, 18 Mar 2017, 17:57 Tristan Anderson, <andersontris...@hotmail.com>
> wrote:
>
>> I"m not sure I agree.
>>
>> Let's say a store has three entrances: 2, 4 and 6 Main Street. The store
>> uses it's main entrance, 4 Main Street, as it's address. Are you suggesting
>> using the addr:housenumber key four times: a node at each entrance in
>> addition to a tag on the store? Now you've tagged 4 Main Street twice, even
>> though there is only one 4 Main Street. Either tag the store or the
>> entrance, not both.
>
> _______________________________________________
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
