On Tue, 2009-08-11 at 03:24 +0100, Matthew W. S. Bell wrote:
Hi,
I am experiencing impaired rendering of OSM layers only, whereby part or
all of the layer is displayed only as white. At zoom levels of 100 m or
below indicated on the scale the entire layer is white. Otherwise, parts
are
Hi.
Is svn down? Or do I have miss some migration?
lu...@blackhorse:~/eclipseworkspace/josm$ svn up
svn: OPTIONS of 'http://josm.openstreetmap.de/svn/trunk': could not connect to
server (http://josm.openstreetmap.de)
Thanks for response. (I want to publish last binary of slippymap plugin to
Hi,
josm.openstreetmap.de seems to be dead. Can somebody have a look?
-- Karl
___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev
Hello,
I am trying to upload some changes and it looks like somebody worked in the
same area and already deleted some nodes I edleted in josm.
Each time I try to upload I get one conflict for that deleted node, have to
re-upload again get a new conflict and so on
Is there a way that I could
On Tue, 11 Aug 2009, Nakor Wikipedia wrote:
Is there a way that I could get all those conflicts of nodes already deleted
in one shot?
Use the update data function in file menu.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
___
josm-dev
Thanks for your answer. However it looks like it did not solve my problem.
I used FileUpdate data, no conflicts were found. I then reuploaded my file
and one conflict on a deleted node was found.
Thanks,
N.
___
josm-dev mailing list
File Update Data
You will then get a series of conflicts, where you will have 4 clicks
for each item that has already been deleted on the server to confirm
that you want to delete it from your local data set. (I don't know if
more recent versions have improved on this yet, can't update to
Instead of Uploading, try to *update* first using File-Update Data (or only
File-Update Selection if you already know which primitives might create
problems).
This will reload all data in your dataset and for those nodes in your
dataset which the server will not return it will check whether they
Yes, it may be a bit more complicated with deleted nodes. Search for
modified (or search for deleted) in search
dialog will show all modified nodes. The update these nodes with the
update selected.
Hmm, this shouldn't be necessary. UpdateDataAction compares with
data.getCompletePrimitiveIds()
On Tue, 11 Aug 2009, Karl Guggisberg wrote:
Yes, it may be a bit more complicated with deleted nodes. Search for
modified (or search for deleted) in search
dialog will show all modified nodes. The update these nodes with the
update selected.
Hmm, this shouldn't be necessary.
There are some cases where conflicts should be resolved automatically:
- server has deleted element and local element is deleted also -- delete
- server has deleted element and local element is unmodified -- delete
Yes, this should be an enhancement. I'd slightly reformulate it, though,
Yes, it may be a bit more complicated with deleted nodes. Search for
modified (or search for deleted) in search dialog will show all
modified nodes. The update these nodes with the update selected.
That should help.
Updating modified did not work. And selecting deleted did not work either.
12 matches
Mail list logo
