The tag addr:place has been used to locate one element inside another addressed element. See this example for shops within a Tesco Extra store http://overpass-turbo.eu/s/5CN.
This usage is useful but probably a little difficult to consume, particularly as there seem to be rather more usages of addr:place as a synonym of addr:city. The idea is that one looks for the thing named in addr:place within the immediate locality (I presume this should be mapped as an area and the node or way with the addr:place tag should sit within that area). Examples of usage include: post offices in shops, shops in hypermarkets, hospitals, restaurants & bars in hotels, some retail & business parks where the address is solely for the area not the street, possibly shopping centres etc.), university campus buildings, etc. This overpass query shows how this has been used in the Nottingham area: http://overpass-turbo.eu/s/5CO, largely by Will. The benefit of using a tag like addr:place is that address information does not get duplicated confusingly (e.g., on a bar, 2 restaurants and a hairdresser all inside a hotel). There are at least 2 post offices in other shops in Nottingham which I mapped. at Wilkinson <http://www.openstreetmap.org/node/386846669#map=19/53.00082/-1.19583>(possibly now Wilko !) in Bulwell I never checked inside the store so rather lazily I just tacked on the amenity tag; at The Co-operative <http://www.openstreetmap.org/way/4440508#map=19/52.95587/-1.22930> supermarket (need to check how this is branded these days too) I did survey inside and added the post office & associated post box reasonably accurately. The distinct disadvantage of putting the shop and amenity tags on the same node is that only one gets rendered. (Incidentally, this applies to many smaller sub postoffices, they are actually located within a convenience store or similar, but we rarely try and separate the locations) Jerry On 25 October 2014 22:29, ael <law_ence....@ntlworld.com> wrote: > On Sat, Oct 25, 2014 at 08:19:25PM +0100, Dan S wrote: > > > However two nodes with standard tags don't distinguish "W H Smiths > > > inside Post office" from the inverse. That seems a useful distinction. > > > sub_shop=yes is ugly, but perhaps something along these lines already > > > exists or is needed? > > > > This may have been discussed heavily elsewhere, I don't know. My own > > opinion is that if you need something to be _inside_ something else, > > there's no point trying to do that just with nodes, since areas are > > perfect for the job! > > Agreed, but it breaks the symmetry and requires more careful survey. > In my case, gps is a bit poor among tall buildings, and the shops > are all in one big building. I can get a rough outline from Bing, but > the inner walls would be guesswork. I don't want to introduce spurious > accuracy into the database, so nodes seem appropriate here. > > I suppose a relation might capture the semantics, but I don't think that > would be very obvious to the average user, who may not be a mapper at > all. He/she needs to know he has to go inside WHS to find the Post Office. > I suppose the obvious rendering would be as you suggest: WHS as an area > containing the PO. Ho hum... > > ael > > _______________________________________________ > Talk-GB mailing list > Talk-GB@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-gb >
_______________________________________________ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
