[Tagging] Why isn't the amenity=parking object part of the relation ?
19b350d2-b1b3-4edb-ad96-288ea1238eee at gmx.com
Thu Sep 13 20:35:44 UTC 2018
Thx. Two follow-up questions.
I had a look at a place to which - if I'm not mistaken - you contributed to  and I see what you mean.
Still, I'm curious why we wouldn't use the "role" attributes of a relation to *explicitly* qualify the outer polygon as the "parent" of the parking spaces (and the other possible parking-related objects, if any).
As a was searching more, I saw in JOSM that when I click Presets > Relations > Site, it opens a dialog box which I think tries to explain that one can add nodes, ways or areas with role label, perimeter, entrance or just member (no role).
And indeed, when I start writing in the Role column in the relation editor dialog in JOSM, it will autocomplete when I start typing perimeter, label or entrance.
But I can't find discussion of that in the wiki. 
Although when searching even further the wiki, I found an explanation of role "perimeter" and "label".  
So, it looks like one should tag the amenity=parking member in the relation with role perimeter.
What do you think ?
By the way, back to , I see tags from amenity=parking have been duplicated to the relation object.
I would have deleted the tags on amenity=parking to avoid double maintenance work.
Is that intended ?
More information about the Tagging