On Mon, 27 Apr 2009, Frederik Ramm wrote:
Idea 2: Before re-downloading an area, let JOSM mark all objects that
came from the API on the last download as possibly deleted. On merging
the newly downloaded dataset with the existing data, reset that flag for
every object retrieved from the API.
On 28 Apr 2009, at 08:17, Dirk Stöcker wrote:
On Mon, 27 Apr 2009, Frederik Ramm wrote:
Idea 2: Before re-downloading an area, let JOSM mark all objects that
came from the API on the last download as possibly deleted. On
merging
the newly downloaded dataset with the existing data, reset
Hi,
Shaun McDonald wrote:
It is already possible to do a multiget,
... which will return 404 as soon as any one of its targets has been
deleted ;-)
Bye
Frederik
___
josm-dev mailing list
josm-dev@openstreetmap.org
On Tue, Apr 28, 2009 at 11:32:51AM +0200, Rolf Bode-Meyer wrote:
2009/4/27 Frederik Ramm frede...@remote.org:
(Incidentally - how can a node have only one version and this is
deleted? Would one not have to first create the node, making v1, then
delete it, making v2?)
Why? Deleting
Hi,
Rolf Bode-Meyer wrote:
(Incidentally - how can a node have only one version and this is
deleted? Would one not have to first create the node, making v1, then
delete it, making v2?)
Why? Deleting doesn't create a version of the deleted element. I don't
think CVS does either.
I don't
2009/4/27 Frederik Ramm frede...@remote.org:
(Incidentally - how can a node have only one version and this is
deleted? Would one not have to first create the node, making v1, then
delete it, making v2?)
Why? Deleting doesn't create a version of the deleted element. I don't
think CVS does
