Le 15.03.19 à 12:27, Hufkratzer a écrit : > is that a good/sufficient reason to define a new relation type?
imho nearly no routing tools (nor foot nor bus) is currently able to use a relation type=route with relations as child. so that's a good reason to create/improve a doc if superrelation is needed for ex for routing (of course maybe some mapper need superroute only for the fun of having a relation that collect all other). for ex how a "data user" can detect "it 's a superroute" <> "it's 2 route with a shared segment" ? for the moment, the trick is to notice that the name of the main relationship is close to the name of the children's relationships and to know that the names of all these children's relationships are fake names (which should therefore be removed/corrected). there is for ex nothing called "European long distance path E4 - part France". it's an artificial name to descript how the relation is splited maybe the tag network should be the same and/or the name (the country XYZ may move the a scope tag) the main relation must/should/mustn't/shouldn't have all/some same tag as the child ? all/a lot of child tag must move to the main relation only ? (that's what we do with MP : we don't duplicate alls tags to way + relation) etc... _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging