For those of us who live in areas that are pretty sparse on mappers, I don't see this being a problem. Speaking from personal experience, just seeing an undo button on your user history would prevent a lot of conflicts from people trying to "fix" their mistakes.
Take a look at the history for this stretch of I-75 near the TN/GA border, since I was unaware of the undo process, I ended up spending 6+ hours redrawing I-75 (admittedly the work needed to be done to fix TIGER, but still) because of a single-keystroke mistake that the CTRL-Z undo in Potlatch didn't allow me to undo. http://www.openstreetmap.org/?minlon=-85.6267052&minlat=34.8502047&maxlon=-84.2608284&maxlat=35.0374212&box=yes Chris On Tue, Jul 14, 2009 at 12:39 PM, <talk-requ...@openstreetmap.org> wrote: > As soon as someone has edited anything in the changeset after the version > in the changeset, then you have a conflict and can't do a simple one click > revert. OpenStreetMap data is a *lot* more complex than the Wikipedia when > it comes to reverting due to the referential integrity. That is key to there > not being a simple revert system for whole changesets. > > >> If the edit can't be reverted because of conflicts, simply show a: >> "can't revert because of editing conflicts" message. >> >> I guess this would already solve 99.99% of all cases. >> > > Only in the seconds/hours after the edit was made (depending on how active > the mappers in the area are). The further back in time you go the more > conflicts you get and the harder it is. > > Shaun >
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
