Modify

Opened 13 years ago

Last modified 3 years ago

#5214 new defect

duplicate nodes after failed upload

Reported by: dieterdreist Owned by: team
Priority: normal Milestone:
Component: Core Version: latest
Keywords: duplicate nodes upload Cc:

Description (last modified by Don-vip)

While trying to upload the offline data from the offtime this weekend I got an error of 328 duplicate nodes (I think they were created before, because I uploaded 6300 changes and after I finished there were some conflicts).

The problem now: I told JOSM to fix all duplicate nodes, but some were outside the downloaded area (3 nodes). When asked if I wanted to deleted nodes outside the downloaded area I clicked "NO". Then I zoomed to the first problem and downloaded the area: afterwards, all remaining 3 duplicate nodes were gone. This looks like a bug to me, because I clicked on No before, and didn't do anything after besides downloading a very small area.

Attachments (0)

Change History (5)

comment:1 Changed 10 years ago by Don-vip

Ticket #9202 has been marked as a duplicate of this ticket.

comment:2 Changed 10 years ago by Don-vip

Description: modified (diff)
Summary: duplicate nodesduplicate nodes after failed upload

comment:3 Changed 9 years ago by Don-vip

Ticket #7400 has been marked as a duplicate of this ticket.

comment:4 Changed 4 years ago by Don-vip

Keywords: upload added

comment:5 Changed 3 years ago by skyper

If I get it right, this is/was a problem with validator autofixing several problems and not respecting the answer in the dialog.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to dieterdreist
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.