id summary reporter owner description type status priority milestone component version resolution keywords cc 8085 conflict management and deleted nodes and ways dieterdreist team "There appears to be something wrong in JOSM latest, I am not completely sure, what but I am quite sure that this is a degradation of something which worked before. given: two roads with some bus routes on them, where road A stops the road B starts (i.e. they are continuous) What I did: 1. split one road (A) in 2 parts (""p"") 2. recombine the piece of A with the rest of B (""c""). I got a window asking me about one conflicting tag (the street name), no surprise because this was the reason for my edit, so I correct it from the suggested ""A;B"" to ""B"" and continue. Now I try to upload. Message: ""uploading failed because of a conflict"", what do you want to do? (I do ""synchronize whole dataset"").and it turns out that 16 conflicts are reported, all happen to have to do with this routes. I go to conflict resolution and choose 16 times ""my version"". On the next upload try I get this: ""Uploading to the server failed because your current dataset violates a precondition. The error message is: ResponseCode=412, Error Header="" Maybe JOSM could also check (on demand) when resolving conflicts whether conflicting elements have been deleted on the server? (This will not eliminate all similar problems, but a fair amount of them, if the mapper acts fast). " enhancement new major Core latest conflict resolution reference deleted object