Modify ↓

Opened 14 years ago

Last modified 14 years ago

#4518 new enhancement

Update data: option to treat objects potentially deleted on the server as conflicts

Reported by: Gubaer Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: Cc:

Description

#4509 reports problems with conflict resolution. This ​comment suggests an enhancement in the context of "Upload Data".

Current situation:

  • run "Update Data". JOSM detects that there are n objects potentially deleted on the server.
  • JOSM provides two options: ignore and skip check each potentially deleted object and delete it locally if it's indeed deleted on the server

Future situation:

  • run "Update Data". JOSM detects that there are n objects potentially deleted on the server.
  • JOSM provides three options: ignore and skip check each potentially deleted object and delete it locally if it's indeed deleted on the server check each potentially deleted object and create a conflict if the object is indeed deleted on the server. This allows JOSM users to treat objects deleted on the server individually.

Attachments (0)

Change History (1)

comment:1 by mjulius, 14 years ago

Deleted objects are only part of the problem. Moved nodes can be equally disturbing.

Modify Ticket

Change Properties
Set your email in Preferences
Action
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 Gubaer.
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 .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.