<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Apr 22, 2020, at 8:38 PM, Martin Koppenhoefer <<a href="mailto:dieterdreist@gmail.com" class="">dieterdreist@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span class="" style="float: none; display: inline !important;">but the building is also a thing, it has its own properties, e.g. start_date, wikipedia reference, architect, operator, name, height, etc </span><br class=""><br class=""><span class="" style="float: none; display: inline !important;">yes, often you can understand which tag belongs to which object, when several objects are represented by one OpenStreetMap object (and that’s why we tolerate this kind of representation), but strictly, you can’t even know whether the name belongs to the building or to the occupant (it “works” because you assume that buildings mostly don’t have names).</span></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">Yep, I do this because I assume the buildings have names and attributes that need to be labeled beyond the encompassing landuse. </div><div class=""><br class=""></div><div class="">every building at the mall is not named “the mall”. </div><div class=""><br class=""></div><div class="">the landuse=retail area is all “ the shopping mall” - the named parking lots, the access roads, the hedges along the fence, etc.</div><div class=""><br class=""></div><div class="">Everything inside this area is "the mall”. </div><div class=""><br class=""></div><div class="">a retail building here is 3 levels, named “south Mall”. it is part of “the mall”.</div><div class=""><br class=""></div><div class="">this other retail building is a deptartment store. it is a giant named anchor store. it has 2 levels. it has the shop tagging on it. </div><div class=""><br class=""></div><div class="">This pin over her is a small shop the south building. that pin is “in the mall” and “in the south building” and has all the tagging for this small shop. </div><div class=""><br class=""></div><div class="">It completely baffles me that the way to tag one collection of buildings and amenities sitting on a named area/landuse is fine for one type, yet somehow a contentious issue when it comes to tagging another set of buildings and amenities that sit on an area. </div><div class=""><br class=""></div><div class="">there are many retail establishments that are the area (malls, shopping centers, big-box stores), many that take the building (many supermarkets or similar), and then a myriad of pins that may be on any of these objects to represent smaller shops inside.</div><div class=""><br class=""></div><div class=""> Shopping centers in particular have usually unknown official names (“parkway shopping” printed on the top of the sign) and then a collection of road-facing retail buildings that people see. having the shopping center (shop=shopping_centre) labeled as a pin in the middle of the parking lot is not great mapping IMO. </div><div class=""><br class=""></div><div class="">A large supermarket tagged onto building may sit on a differently named landuse (a shopping center), and have a pin inside the building to represent the small coffee shop or bank or similar tiny shop “inside” the supermarket as well, </div><div class=""><br class=""></div><div class="">Very similar to a Hospital which is a giant named area, a named individual hospital building, and pin for a convenience store in the basement. </div><div class=""><br class=""></div><div class="">keeping this flexibility better represents reality. </div><div class=""><br class=""></div><div class="">Javbw</div></div></body></html>