[josm-dev] JOSM, the relation killer

Apollinaris Schoell aschoell at gmail.com
Tue Apr 6 00:31:54 BST 2010


had the same problems but seen it before upload. at that time conflict
resolution had other bugs too and I didn't spend time to analyze and just
went back and did my edits again.
If I remember correct it was that by default all members are removed in the
conflict dialog and you have to explicitly choose yours or the one from the
server and put it back. Just clicking on ok and all members are dropped.




On Mon, Apr 5, 2010 at 12:52 PM, Frederik Ramm <frederik at remote.org> wrote:

> Hi,
>
>    every now and then we have isolated reports about all members of a
> relation having accidentally been removed with JOSM.
>
> Just recently, with JOSM 3097, someone made this changeset
>
> http://www.openstreetmap.org/browse/changeset/4238359
>
> in which this 2700 member relation
>
> http://www.openstreetmap.org/browse/relation/18162
>
> (which has meanwhile been deleted and re-created as #544296) was robbed
> of all its members; only the empty, tagged relation remained.
>
> The user says that he had not changed the relation except removing a
> node from a way that was part of the relation; then, on upload, that
> edit produced a conflict which he resolved by saying that the deletion
> of the node can be ignored.
>
> I don't have details but I have a feeling that some sort of conflict
> resolution was involved in most of these "help, JOSM has removed all
> members from the relation" problem.
>
> I'll play around a bit on then dev API and see if I can reproduce the
> problem.
>
> Bye
> Frederik
>
> --
> Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"
>
> _______________________________________________
> josm-dev mailing list
> josm-dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/josm-dev
>



More information about the josm-dev mailing list