Jean-Marc Liotier <j...@liotier.org> writes: > Peter Budny wrote: >> OSM right now has very little tools to support editing. Compare this to >> text processing [..] > > This thread certainly has something to do with advanced version > control for geographic data. That said, a discussion that happened a > few months ago here > (http://www.mail-archive.com/talk@openstreetmap.org/msg33788.html) did > not conclude positively about branching and merging being capable of > solving the import management conundrum.
That's good to hear (I admit to not being on the lists much the last few months). I'm not surprised that people couldn't get behind a branch-merge system; it works well enough for source code and text, usually, but that doesn't mean it's perfect for an entirely different type of data. All that says to me, is that OSM should look at OTHER techniques for handling data. For instance, how might one merge three sets of data... let's say, TIGER has good coverage but bad alignment and bad name tags, another data set may have good centerlines but no tags, and a third may have good name tags but poor coverage. Surely there is a way to integrate all of these (and merge them with existing OSM data) other than to just open it all in JOSM and do it by hand? -- Peter Budny \ Georgia Tech \ CS MS student \ _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
