> On Sep 30, 2015, at 4:36 PM, Martin Koppenhoefer <dieterdre...@gmail.com>
> wrote:
>
> if the postal address is different to the actual address (e.g. post goes to a
> reception which is in another building and does the internal distribution)
> I'd still tag the actual address where a feature is located
if you are referring to a PO box vs actual routing, yea, best to put the
physical address.
I was trying to say that a perfectly routable “address" may not lead you to the
exact location inside (maybe just the front door), nor the proper entrance for
the location you are trying to reach (it might be addressed to a side road but
the main entrance is the “back” door on a larger street), or an easement from a
different street than the address street. The suite number or level may lead
you to the building, but not the right part (node placement helps solve this)
Very large and complicated places - and ambiguous places (like in Japan which
are labeled by lot, not building), or the building is huge and very difficult
(like a giant mall or station), the address may not be human navigable (the
“suite number” may only be used by the shipping receivables, not by customers),
so you may to have more information to get there than it’s official address and
pin location (level=* or odd level:ref=*).
http://www.tokyo-skytree.jp/en/floor/pdf/skytree_en_130830.pdf
<http://www.tokyo-skytree.jp/en/floor/pdf/skytree_en_130830.pdf>
this is the map of Tokyo Skytree. The actual buildings at the bottom - the
aquarium and mall, loading platforms, etc use floors as we know them, and are
labeled “1F, 2F, etc. - but the observation decks are “floor 340” - which is
referencing not the “floor” number, but the height in meters above ground level
that floor is. (hence the next floor up is “floor 345” - and then 445 and 450.
These are not levels, but level:ref=Floor 350 (it is a name not a value).
name:en=Sky Restaurant 634
Addr:full=Tokyo-to Sumida-ku Oshiage 1-1-2
ref:place=Tokyo Skytree
level:ref=Floor 345
The mall below it is a nightmare. Whoever laid it out is a jerk - there are
refs on the tourist map duplicated all over the place. and location and name
refs mean nothing.
For example, if you want to visit Starbucks there, the shop name is is “
Starbucks Tokyo Skytree Solamachi East 6 floor”, and the official address is
just “Tokyo skytree town”
https://www.starbucks.co.jp/store/search/detail.php?id=1038
<https://www.starbucks.co.jp/store/search/detail.php?id=1038>
the name of this building split into 3 pieces surrounding the Skytree. It’s
location on the tourist map is East yard 6th floor, ref# 11. This ref is
totally not the actual unit number, as the refs are duplicated all over the
place. Maybe unit is E611. But tourists don’t care, becuae all they have is the
(really shitty) guide map. But we can add some of the tourist facing
information using existing tags and a couple *:ref=x tags to get better idea
of where it is.
name:en=Starbucks Tokyo Skytree Solamachi East 6F
addr:full=Tokyo-to Sumida-ku Oshiage 1-1-2 Skytree Town
addr:place:ref=East Yard
level=6
Level:ref=6F
addr:unit:ref=11
This is my thinking of how to reconcile tourist information maps with popular
places without the data polluting the addr field. The addr:full is the
“official” address of that Starbucks. no mention is made of the floor or suite
number.
J
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
