OpenStreetMap
So I've put a bit of effort in recently to trying to put in all the residential areas around a city. I did it, and only part of it seemed to get uploaded, which wicked me off as I'm generally fairly observant for things such as failures.
Still, the missing bits I did again. They appeared nicely up on the Osmarender layer. Until today. A large number of them have gone. Data and all.
Screw this, I can't be arsed putting time and effort into a system where there is no method of commenting on changes, and rollback versions. If work I put in is simply going to get deleted without comment, then why should I put my own time into this?
토론
2009년 1월 26일 19:24에 lyx님의 의견
I expect there is some way for rolling back changes, it's just not exposed to the public interface. That would make it even more easy for malicious individuals to destroy other peoples work, at least if there is no corresponding "roll forward".
2009년 1월 26일 19:27에 Dashers님의 의견
It's tricky, as anybody could maliciously go in and delete a whole load of work. A version history would be good though, even if you can't roll back yourself on bulk. Just details of who made the change. At least then you can message them.
As it happens, I think I need my eyes checked, it all seems to be back. I guess my cache was funny or something, doesn't explain the lack of data though.
2009년 1월 26일 20:20에 burto님의 의견
I use JOSM to edit locally and then upload. I keep local copies and use a
version control program to save each major version so if it gets trashed on
the server, I still have my local copy. You don't have to be a computer wiz
to do that (but it helps!)
2009년 1월 26일 21:11에 Dashers님의 의견
That's an excellent idea. I generally stash my GPS traces, but never really thought about storing individual (large) edits. I may start doing that. Thanks for the tip burto.
2009년 1월 26일 21:22에 HannesHH님의 의견
You can get someone "important" to rollback changes if you ask on the mailing lists (or IRC).
This summer there will be major changes in the background (API upgrade), from what I remember there will also be a much better version control then.
2009년 1월 26일 22:05에 Minh Nguyen님의 의견
In Potlatch, you can select a node or ID and then click on its ID (to the left of all the key/value pairs). That brings up a history box, where you can revert pretty easily. Unfortunately, there’s no way to bring it up for completely deleted features.
2009년 1월 26일 22:06에 Minh Nguyen님의 의견
Typo: In Potlatch, you can select a node or way and then click on its ID…
2009년 1월 26일 22:51에 RichardB님의 의견
Um, doesn't Potlatch have an undelete function? It certainly used to. If you press something like "U" then it highlighted in red any way that had been deleted.
2009년 1월 26일 23:04에 RichardB님의 의견
Oh, and surely you don't need to store large edits locally - if someone delets loads of data then it could be restored from a recent Planet.osm file.
2009년 1월 26일 23:36에 Minh Nguyen님의 의견
Thanks, Richard. Didn’t know about that one.
2009년 1월 27일 11:35에 burto님의 의견
I don't store "loads" of data locally. My current local area OSM file is about
12MB. The version control software compresses the data so well that keeping the
history is no problem. I am using git which like most "modern" version control
systems allows you to put any directory tree under version control without having to set up a repository. It makes keeping local history trivial.
2009년 1월 27일 11:53에 robx님의 의견
Regarding "important" people rolling back, I think it's mostly a matter of having the technical ability to do the roll-back. Rolling back then is just uploading an old state of data, and can be done by anyone.
The only part which might be helped by "importance" is doing large uploads locally, which will go faster thanks to lower latency.
2009년 1월 27일 21:11에 Igor Shubovych님의 의견
The first rule from the Hitch-hiker's Guide to Mapping is "Don't panic" ;)
Everything can be restored. The receipts are above.