Not only this, the problem is worse. When you create a new variant, you would need to create a new variant for all the route= it belongs to, because the member has changed. Even for route=road , doing this for every road renaming (and other attributes) on any significant signposted route would be a horrible mess. Not to mention =bus , =bicycle , =foot etc. That’s not scalable and manageable. The route= that the changed road carries hasn’t changed on its own, so data models that creates a new variant of referred objects should be avoided.
In effect, this basically calls for One Attribute One Object, to put in in extreme. OHM has to keep track of evolutions in many attributes. They should be separated, so that different changes aren’t mixed together conceptually, and not compounding the complexity data-wise. This could benefit viewing and applications as well.
Without any knowledge, I imagine a combination of an unclosed Shrinkwrap / attached “parallel” tool, and “select non-branching way sequence” may serve as a conforming workflow. Outside the topic here, the latter action is more universally needed in iD, so that you don’t have click everything you want to select.
1 Like