Hi Karl, As part of my conflation plugin work, I was thinking about extending the core JOSM code to support resolving conflicts between different primitive types, rather than rolling everything on my own. I know this kind of breaks with the intention of the conflict tools, which are of course to resolve conflicts between different versions of the same primitive. So the two big changes would be: 1) Allow creation of "conflicts" between different objects, not just different versions. This would be allowed between two different objects on the server, two objects on local, or a mix. This would essentially be a more robust form of the merge node command. 2) Allow creation of "conflicts" between different types of primitives, i.e. between a way and a node. Of course in this case it doesn't make sense to "resolve" nodes/members, but only tags.
Does this make any practical or technical sense? How deep is the assumption that conflicts are always between primitives of the same type? Aside from helping with my conflation plugin, this would also allow merging of ways (possibly utilizing the utilsplugin2 replace geometry command) and relations. Thanks for any input, -Josh _______________________________________________ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
