> Are there any options to getting the old location of a moved node > without writing my own Osmosis patch (if that's even possible)?
I think this cannot be solved easily. But I like your Idea of creating a change file "extract". One could implement it like this: Exclude all <create> and <modify> datasets of nodes which are not within the specified region. Keep everything else. This should work. Nodes which are to delete will be kept in the change file, regardless of their geographical position. Node-Delete-Datasets should be a minority, and they will be very small if you get rid of their tags, metadata and lon/lat. For to delete a node you only need its id and - for validation purposes - the version number. Markus -------- Original-Nachricht -------- > Datum: Fri, 15 Jul 2011 16:28:42 +0100 > Von: Andrew Ayre <[email protected]> > An: dev <[email protected]> > Betreff: Re: [OSM-dev] Merging Changes with Bounding Boxes > Thanks. > > You mentioned that the change file only contains the new version of > objects. If a node is being deleted is the lat/lon in the change file > guaranteed to be identical to the lat/lon for that node an up-to-date > planet file? > > Are there any options to getting the old location of a moved node > without writing my own Osmosis patch (if that's even possible)? > > Andy > > On 7/15/2011 3:35 PM, Toby Murray wrote: > > The problems with change files + bounding boxes is that the change > > file only contains the NEW version of objects. So when you clip it to > > a bounding box, nodes that started out inside of the bbox and were > > moved outside will get eliminated from the change and you will keep > > the old version of the node in your database. > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/dev _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
