Opened 5 years ago

Last modified 3 years ago

#17677 new defect

Large upload with multiple changesets fails silently. Failed to automatically close a full changeset.

Reported by: anonymous Owned by: team
Priority: critical Milestone:
Component: Core Version:
Keywords: upload Cc:


Some background when this happened:
I have recently done an update/reimport of some trees. There were a total of about 25000 new trees and 29000 modified trees.

This upload was split into 6 seperate changesets. With max size of 10000. The first 3 changesets went fine. The fourth changeset did no go as well. After it was completely filled up JOSM somehow refused to close it and did move on to the next one.

To work around this I had to:

  1. Cancel the upload,
  2. Manually let JOSM close the still open changeset,
  3. Redownload all data modified by changeset 4. It did not register those changes had happened.
  4. Start the upload again.

Finally, repeat the above steps for each changeset left until everything is fully uploaded.

The error happened when creating changesets with only modified nodes.
Both the tags and location were modified. With the only exeption being a handful of nodes for which the location was not modified.

This happened with version 14824

Attachments (0)

Change History (2)

comment:1 by Don-vip, 5 years ago

Keywords: upload added
Priority: blockercritical

comment:2 by zelonewolf@…, 3 years ago

This does not appear to be an issue on 17084.

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to anonymous.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.