You should include tag this meaning "enable/disable inheritance (propagation) of tags to all its memebers". This is main difference between Relation:street and Relation:associatedStreet. Sometimes you need this feature, but sometimes not. 1. inherit tags from parent relation 2. don't 3. unspecified
Also you need tag to suppress all tags that are used at its members in order to keep data consistent (name=* is different for relation, who do you trust?) 1. trust relation 2. trust members 3. unspecified Many mappers fail to realise need in separate tag for this and countlessly fight "we don't need addr:street=*", "we don't need Relation:associatedStreet" at tagging list and wiki pages. 2015-01-15 16:23 GMT+04:00 Janko Mihelić <jan...@gmail.com>: > 2015-01-15 11:23 GMT+01:00 Martin Koppenhoefer <dieterdre...@gmail.com>: > >> >> I wonder if it wouldn't make more sense to use the approach of islands / >> archipelago, i.e. have a dedicated, explicit and specific tag for the >> "combined feature" (e.g. several natural=island/islet can be together in a >> multipolygon relation which is tagged natural=archipelago). >> > > IMHO we don't even need a relation. All islands can have the same tag > cluster:archipelago=*. If data consumers find a tag that starts with > "cluster:" they can group all elements that have the same > cluster:archipelago. It's the same as streets in a city. How do you know if > two segments of a street are the same street? They have the same name. > > Archipelago isn't so much an entity in itself. It is just an attribute of > the islands it is consisted of. > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
