Opened 13 years ago

Last modified 3 years ago

#6002 new defect

"Upload selection" should not check for parents

Reported by: bilbo Owned by: team
Priority: major Milestone:
Component: Core Version: tested
Keywords: upload selection conflict parent Cc:

Description (last modified by skyper)

When I use upload selection to upload only some deleted objects, JOSM starts checking for parents of deleted objects ("Checking parents for deleted objects").

If I cancel it, upload is cancelled.

If I let it finish, then after 2 requests per every deleted node (could be several hundred requests and few minutes) it just present upload dialog with all the nodes for deletion, which will fail soon, as some of the nodes are used.

So the result (information about which nodes have parents) obtained during those hundreds of requests is not used and is just waste of time and resources. Also, this step is IMHO absolutely unnecessary, as it could be resolved by handling conflicts as they appear.

Attachments (0)

Change History (3)

comment:1 by skyper, 4 years ago

Description: modified (diff)

Objects within download area should not need to be check on server but include the modified parents in upload which seems to be strange if you only upload selection on the other hand you will get conflicts on these objects without uploading them.

Last edited 3 years ago by skyper (previous) (diff)

comment:2 by skyper, 3 years ago

Keywords: upload selection conflict parent added

comment:3 by skyper, 3 years ago

As "Upload selection" is treated like data outside of downloaded area, I think this check is needed. See #6128 for an example where JOSM should download and update all parent ways but does not.

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 bilbo.
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.