On Saturday I went out in the sunshine to eliminate a funny little cluster of unnamed streets quite close to my house, by Tufnell Park Road. I wasn't sure if this was a cluster of insignificant streets which don't actually have names, or an real area which nobody has mapped yet. Turns out it was the latter, complete with two unmapped parks and a very pleasant unmapped pub!
Going out mapping was kind of a bad idea, given the increasing backlog of data I had to enter. But hey it's a long weekend. Plenty of time to get stuck in with JOSM right? So that's exactly what I did. Unfortunately I didn't take the time to update JOSM. It would seem version 1526 has a rather nasty bug causing it to pretend upload without doing so in some circumstances. And it would seem the circumstances are rather common. I've just realised that out of the four different hour-long mapping sessions I've done this weekend, three of them have been lost completely. Gah! Not happy.
I knew that some JOSM versions were having upload problems, I just didn't realise it was quite so prevalent, and devoid of any errors/warnings.
Lesson 1. During this period, update JOSM regularly and check changesets are appearing on 'my edits' before closing down.
Lesson 2. Don't worry about creating too many changesets. Upload regularly.
hey ho. Looks like I still have a backlog.
Discussion
Comment from TomH on 5 May 2009 at 08:13
Lesson 3. Pay attention to the words "You need JOSM version 1529 or later" in the JOSM banner message about the 0.6 API update ;-)
Comment from Harry Wood on 5 May 2009 at 09:52
yeah that aswell :-)
Comment from Firefishy on 5 May 2009 at 10:56
I have a "fun" problem... When using JOSM with OpenGL on my nvidia video card, it semi-randomly bombs out, not fun.