NOTICE: is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum


when there are edit conflicts in iD the conflict editors does not help solving them: - it proposes to download our changes, but the link provided goes to a blank page. - trying to select any propposed edit from the change fails, iD does not properly download all the needed changes. Then continuing will fail because iD still wants to save objects from their old version iD

In summary, iD is unusable for editing in areas where there are other users cooperating, we just loose ALL our edits for a single object change that we cannot refresh to download them in their current version so that we can then update them as needed.

The conflict editor simply DOES NOT work at all !

asked 18 Sep '17, 20:30

Verdy_p's gravatar image

accept rate: 0%

edited 12 Nov '17, 17:20

aseerel4c26's gravatar image

aseerel4c26 ♦


I'd suggest that you create an issue (or update an existing one) over at . The OSM help site isn't really the place for "X doesn't work" statements - it's not a "question" that anyone can answer.

What I would suggest is that you explain the problem with a series of steps to reproduce - if you do that on the dev server then you can create any test data that you like.

(18 Sep '17, 20:39) SomeoneElse ♦

Hey verdy_p, the issue with the broken "download changes" link is something I just learned about last week. Turns out that recent versions of Chrome and other browsers no longer like linking to data: urls.

I worked on it over the weekend and was able to fix the issue so that now downloading changes will work again in all supported browsers on the Conflict Resolution screen, as well as the general Upload Changes screen.

I'll probably release a new version of iD in the next few days that includes this fix. Thanks for your understanding!

(18 Sep '17, 20:50) bhousel

Closed with "negative" comment, but this is a REAL problem.

I've never been able to use the conflict editor in iD, it ALWAYS fails finally when all conflicts are supposed to be solved, by a fatal error where iD contains the wrong old version.

It's even impossible to just discard changes on conflicting objetct and continue with others (there may be plenty of them and loosing everything is definitely not an option when we can simply not even download these changes for external review, for example as an .odm file we could fix by using JOSM instead).

So YES this question is FULLY RELEVANT and ON TOPIC, @SomeoneElse you are compeltely wrong ! And it concerns lots of people (not just me).

This is really a severe bug. And it is extremely easy to reproduce, by using two distinct browsers connected to different users and user1 making a change to a way currently loaded by User2, then User1 commiting changes on one node, before User2 attempts to commit changes to the same way (such as adding or moving the same node).

Please REOPEN this unsolved bug

(18 Sep '17, 21:29) Verdy_p

"Closed with "negative" comment, but this is a REAL problem."

Your "question" has not been closed. I don't know where you're seeing this.

"So YES this question is FULLY RELEVANT and ON TOPIC, @SomeoneElse you are compeltely wrong ! And it concerns lots of people (not just me)."

As SomeoneElse said, this is a Q&A site. Someone asks how to do something, and others give answers to help do that thing. What exactly is your question? If you don't have one, then the best place to post your comments about this issue with iD is in GitHub.

(18 Sep '17, 21:40) alester
(18 Sep '17, 21:42) Verdy_p

@Verdy_p - Did you actually read bhousel's comment above?

(18 Sep '17, 21:42) SomeoneElse ♦

Yes of course I read it. You just refuse to admit this is a bug, but many users complain about this. The bug is not solved currently. You refused the bug but bhousel saw it as a real bug on which he is working. Don't be surprised that people stop working on HOT projects when most of them use iD, and if they have passed long time draxing things and thne connecting their ways, to surrounding tile, and loose everything because they can't pass through the edit conflict, they will stop contributing because of their lost patient editing time.

(18 Sep '17, 22:25) Verdy_p

SomeoneElse isn't refusing to admit there's a bug. He's just telling you that this isn't the appropriate place to be discussing it. I ask again, what is your question for this Q&A site?

(18 Sep '17, 22:41) alester

@verdy_p the help site is not a general discussion forum, nor an issue tracker for bug reports. Please take your non-stop arguments elsewhere.

(18 Sep '17, 22:42) SimonPoole ♦

If you cannot see the question, which is there... I have to repeat it, because you don't read: how do we connect then and mange the local profiles? It's impossible. I see your constant replies here very agressive what what is a real problem without solution for now.

(18 Sep '17, 23:08) Verdy_p
showing 5 of 10 show 5 more comments

The question has been closed for the following reason "Too subjective and argumentative" by SimonPoole 18 Sep '17, 22:48


I will NOT vote up for the speedy "solution" proposed incorrectly by Someone else, I would vote down if it was possible, as it is really incorrect.

And this is not about "testing" things, but real edits in the main database (so the dev database in your suggestion is compeltely irrelevant)

permanent link

answered 18 Sep '17, 21:38

Verdy_p's gravatar image

accept rate: 0%

edited 18 Sep '17, 21:39


Please stop misusing the help site, in particular stop posting comments as answers.

(18 Sep '17, 22:45) SimonPoole ♦

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 18 Sep '17, 20:30

question was seen: 2,174 times

last updated: 12 Nov '17, 17:20

NOTICE: is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum