I was thinking of just.. Um.. drawing an area of the building, with levels=x, layer=1, then drawing the parking lot on top of it (it usually is a bit smaller and less than 100% of the top, elevators and AC and all), and then tagging the parking with Amenity=parking & parking=rooftop / layer=2
Here’s the place I’m tracing/aligning now in OSM. https://www.google.com/maps/@36.3557609,139.1296344,438m/data=!3m1!1e3 <https://www.google.com/maps/@36.3557609,139.1296344,438m/data=!3m1!1e3> Here’s my local shopping mart. https://www.google.com/maps/@36.4191102,139.2343137,109m/data=!3m1!1e3 <https://www.google.com/maps/@36.4191102,139.2343137,109m/data=!3m1!1e3> Both are parking only on the roof. I was just thinking that having them render differently would be necessary, and since they are different than other parking, they might need a new tag J > On Nov 11, 2014, at 7:09 PM, Holger Jeromin <mailgm...@katur.de> wrote: > > Martin Koppenhoefer wrote on 11.11.2014 11:01: > >> 2014-11-11 10:56 GMT+01:00 Holger Jeromin >> <mailgm...@katur.de >> I would suggest two overlapping ways: >> building=yes >> amenity=parking >> parking=multi-story >> building:levels=5 >> building:min_levels=2 >> layer=1 >> >> and >> building=retail >> building:levels=2 >> shop=department_store >> Me similarily, but would propose to use a multipolygon relation instead. >> That's why they are there, overlapping ways are hard to maintain and >> more difficult to spot. > > Instead? > > Adding a relation to the two overlapping ways seems not making it > easier. The building (parts?) have the same outline, so they have to > overlap in the first place. > > -- > regards > Holger > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
