<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
I just it a rather frustrating scenario. I was uploading a large
set of data into the Thunder Bay area. My network connection died
in the middle. (and didn't notice for a day) No big deal, I just
restarted the upload as it had been saving changes in the new
JOSM. <br>
<br>
However, what I didn't realize is
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-style:
normal; font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span" style="font-family: Arial,sans-serif;
line-height: 19px; text-align: left;"><a
href="http://www.openstreetmap.org/user/magellan"
style="color: rgb(0, 0, 255); text-decoration: none;">magellan</a></span></span>
had gone in and started deleting any orphaned nodes from the now
closed first change set. So I have this big batch that I can't
finish the upload as magellan has deleted all required nodes.<br>
<br>
I've asked magellan if they could refrain from deleting objects in
that area so I can fix the batch... just wanted people to be aware
if there deleting in an area. I'm guessing magellan saw the 50,000
orphaned or duplicate nodes and did a clean up while my batches were
still processing. Problem is if your uploading and it's going to
take multiple change sets the first set contains all the new nodes.
(thus creating duplicates and orphans) The second or third
changeset has the ways, and relations.<br>
<br>
<br>
<br>
</body>
</html>