<div dir="ltr">In the parking example that i talk about, the multipolygon is not usable if i want to indicate the specificity of each part of the parking lot like capacity or capacity:disabled (as the tagging is global for every outer part). I like the site relation as it allows to also group the vending machine or the amenity=parking_entrance for underground parking (as a car park may have both underground + overground parkings). I find a site relation more practical in such cases and I never used it technically for malls with only overground parkings (but that was in the original proposal example i think ^^). <div><br></div><div>My use case was more about the underground parking where I grouped all the parking_entrance (both pedestrian and for vehicle) with a "site=parking" relation. One example is this one : <a href="https://www.openstreetmap.org/relation/8425228#map=18/50.66911/4.61226">https://www.openstreetmap.org/relation/8425228#map=18/50.66911/4.61226</a> (there are one vehicle entrance, one vehicle exit, multiple pedestrian entrance/exit and few vending machines for it). <b>Do you have a better way of tagging this ? ^^</b></div><div>I just used what i found on the wiki at the time, and it was clean in my opinion. :-p</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 15 juil. 2020 à 09:35, Martin Koppenhoefer <<a href="mailto:dieterdreist@gmail.com">dieterdreist@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Mi., 15. Juli 2020 um 01:40 Uhr schrieb Paul Allen <<a href="mailto:pla16021@gmail.com" target="_blank">pla16021@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Tue, 14 Jul 2020 at 23:44, Matthew Woehlke <<a href="mailto:mwoehlke.floss@gmail.com" target="_blank">mwoehlke.floss@gmail.com</a>> wrote:</div><div dir="ltr"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The multipolygon is just ammenity=parking, but the sub-objects are <br>
tagged with more information (capacity, in particular). Again, is that <br>
sane, or do I need to do this differently?<br></blockquote><div><br></div><div>Doesn't look sane at present. You have combined one public parking area</div><div>with two private ones. If they're all private, for use by the restaurant, mark</div><div> them all as private.</div></div></div></blockquote><div><br></div><div><br></div><div>if they are for the clients of the restaurant, the typical tagging is access=customers</div><div>Also you should not have 2 objects amenity=parking which cover the same area (regardless of additional tags). <br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><div>Even so, is a multipolygon giving any information that couldn't be had</div><div>by separate parking areas with the appropriate operator tag?</div></div></div></blockquote><div><br></div><div><br></div><div>+1, this is what I would choose, no relation at all. It is also what you can probably argue for "on the ground": two parkings operated by the same business, not one parking spread over 2 areas.<br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
(BTW, is there any accepted way to tag a 'carry-out only' space?)<br></blockquote><div><br></div><div>If you're talking about one (or both) of those parking areas by the</div><div>restaurant, then it is (or they are) not really a parking area. I'd</div><div>probably make it a closed way with highway=service + area=yes</div><div>and then risk the wrath of purists by naming it "Pick-up Zone".</div></div></div></blockquote><div><br></div><div><br></div><div>there is the "maxstay" tag which can be used with a value like 5 or 15 minutes.</div><div><a href="https://taginfo.openstreetmap.org/keys/maxstay#values" target="_blank">https://taginfo.openstreetmap.org/keys/maxstay#values</a></div></div><div><br></div><div>Cheers</div><div>Martin<br></div></div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>