[OSM-dev] Merging Changes with Bounding Boxes

[Toby Murray]

Not 100% sure. The API documentation in the wiki does state that
lat/lon are required parameters for a delete operation. It doesn't say
that they must be the same as they were for the previous version of
the object. So I'm not sure if you can count on the lat/long being
identical.

Regardless of the API, you could certainly get a location change and
then a delete for the same node in one change file. I'm not sure what
happens if a user moves and then deletes a node, all before uploading.
This might depend on the editing software. Some editors might just
drop any changes and only send the delete operation while others could
upload any changes first and then the delete.

Toby


On Fri, Jul 15, 2011 at 10:28 AM, Andrew Ayre <andy at britishideas.com> wrote:
> 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.
>