Frederik Ramm wrote: > Hi, > > Brett Henderson wrote: >> As of 10:55 UTC, the daily/hourly/minute changeset files now include >> a uid attribute on all entities. This brings osmosis into alignment >> with the planet format which has included uid details for some time now. > > Should they also include the object's version id since that is > required to make changes? Will we have the version id in the planet > file with 0.6 or will any attempt to change an object first require > asking the API for the most recent? The 0.6 format will include the version id in changeset files, but 0.5 is more difficult due to the node table not having a version id. It should be possible to calculate one for 0.5 but not straightforward. As a general rule, any element attributes in the osm snapshot file will also be included in the osc changeset file, in fact the same osmosis code writes the osm xml element and its children as the create/modify/delete elements and their children.
I haven't written a --migrate-change task yet due to this lack of version information. I was hoping it wasn't necessary, but if people want to synchronise a 0.6 database with 0.5 source data (ie. for testing prior to 0.6 going live) then it may be required. The simple option may be to create a --migrate-change task that always creates entities with version 1, I think osmosis would just keep overwriting the old version 1 in the destination database thus not maintaining history but I haven't tried it out. _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
