OpenGeofiction
Hello everyone,
just a quick question; I’ve downloaded the latest ogf-backup an hour ago (18th April), and, as I usually do, cropped and transformed it into an osm file with the size of my country using osm convert. Only that while editing on JOSM, I’ve noticed that there were some unconnected and untagged points here and there. Comparing with the browser map, I’ve found that all of them either were tagged with railway=station or place=town or place=suburb;they were all still as they used to be when I looked through the browser editor, so the problem occurred either with the data set itself or during converting. If I had uploaded my “changes” from JOSM to OGF, I’d have done quite some damage to Kojo and adjacent territories.
Usually I’d just think that the data set is impaired, but at least its size looks very reasonable, 191mb, and I wonder why it’s only such a very limited number of objects that’s affected? It would be great if another mapper could check if they have similar issues with the newest backup file, and I just have to wait for the next file, or if it relates to osm convert :)
Cheers,
Leonard
Discussion
Comment from Bstn on 18 April 2016 at 12:53
That fault occured also for me when I cut Gobrassanya out. I also used osmconvert. - Bstn
Comment from Luciano on 18 April 2016 at 23:12
I have seen problems like this, not just with osmconvert from the backup file, but also occasionally in direct object downloads in JOSM, especially of large relations containing lots of ways and nodes (eg large boundary relations). Because of this, I have decided the problem is in JOSM, rather than in the backup file necessarily (although yes, that too sometimes has problems). My only advice is that whenever I see this kind of problem, my instinct is to immediately close the file, without upload, and try again, since, as you point out, it creates huge problems to try to update from an incomplete file. I guess that’s not very helpful advice - but at least in my experience, it doesn’t happen very often, as long as you’re careful not to get a “truncated” backup file.
Comment from Leowezy on 19 April 2016 at 11:56
I see, thank you very much for your responses :)