2009/8/23 Frank O'Dwyer <frank-...@wordonthestreethq.com>: > John Smith wrote: >> It's unlikely someone would delete and add a POI in the same spot, >> they are more likely to be modified. > Cheers, that's what I expected. So I can probably just ignore that case > for now and run a cleanup script separately later on if needed.
It happens more often with ways than nodes because someone splits the way at a node and the editor creates two new ways and deletes the old one, and then even if they're merged back together, the way gets a new id. (though some editors are smarter about it) > Is there a recommended way to do this so as not to cause undue load on > osm servers? Any existing code I could to pull changesets? You can run osmosis weekly in a script to download 7 daily diffs and produce one weekly diff which you'd then apply or apply the four of them at the end of the month. Osmosis can track what new diffs there are since you last ran it and you don't need to mess with the names of the diffs which include day numbers. >> The vast majority of data in changesets is nodes, however most of >> these wouldn't be amenity nodes, on a half decent machine it doesn't >> take much to process a daily file through an xml parser to pull out >> just the amenity changes. Also node changes could turn an amenity into >> something else if it was tagged wrong so you would need to keep tabs >> on this and delete them. > Is there already existing ruby code to parse the changesets? So far I've > been playing around with osmlib but it seems like it only supports .osm > files. I know very little about ruby but I'd expect you can reuse the ruby code for parsing changesets that runs the API server. Cheers _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
