BTW if anyone was looking at my thousand edits, a lot of them were trying to address the errors showing up at https://www.openmapchest.org/mapfixer/united-states/ -- I click through them one by one, and each time they pull up iD or whatnot to edit, I can't "merge" multiple edits into one changeset. I don't know if this use model is considered or not, then again, any two errors may or may not be physically close together.

Incidentally I've stopped fixing them for about a month now or at least slowed down a lot... the times I was actively editing, the biweekly error count was holding steady. Now it's growing like 100 errors per week. misery...

iD takes forever to startup on slow machines like my Atom 1.6GHz - it takes minutes to load up and very sluggish in edits. On fast machines, it's not really noticeable, mostly network latency. However when editing several hundred node ways, it gets slow on even fast machines. when i was drawing boxelder creek in the unrelated changeset osm.org/changeset/81338878 , by the end of the creek it took nearly 1 second to lay down another node and connect the way to it. Pretty painful. In any case one thing I noticed with iD is that by default it will pickup business logos from face***k etc, i made sure to turn it off as it was ***king with my privacy blocker script in my browser. The option is like one of the only options you can change in iD which is kind of disappointing but very very helpful in itself.

Dang. Really need a chat forum for discussions like this. On the other hand perhaps another tangently related question is

how can we get paid by amazon to ***k up the map? :-)

Sorry, bad joke, sorry, sorry....

oh fu** (expletive self censored) the openmapchest USA map snapshotted this error :( Looks like this two weeks I have a bad map. Need to make sure I don't archive this weeks map with a known problem.

But anyway I was always worried about how iD handles restored sessions. I knew that if you make changes in iD and then goto another page (firefox will warn unsaved changes) and then come back, it will offer to "restore" changes. The restore seems kind of flaky, don't know what it actually saves. And you're right, you cannot have two different iD sessions open at the same time (at least with the same userid on the same computer/browser). While I don't know how the change got duplicated into Colorado, they need to find out.

Another thing that I found annoying is that while editing turn restrictions, a lot of the changesets are tiny. I couldn't find a way to get iD to collate a bunch of tiny changes into one big change. I gave up - and just saved the tiny changes. I figure this is safer with how iD handles going back to a old session. Really should just switch over to another editor if I really want to make a big changeset with only TR fixes in it.

This was a fairly large piece of road that was plopped down, I really would like to get an explanation on how this got through. Unlike the previous overlapping roads that were of the same road, this one was two different roads in two different states... Noting that the overlapping roads problem is fairly frequent, I sure hope this kind of splatter isn't frequent, Amazon really needs to figure out what's going on fast, and so far it seems like they're dragging their feet.

The changeset that I did so is in # 81338179 ... sorry I had to change this back so quickly before you had a chance to respond to figure out how this happened to begin with.

Couldn't contact in 24 hours on this serious problem, I went ahead and deleted the erroneous road in Fort Collins, CO that overlapped Mulberry Street.

It looks like you edited the original road in osm.org/changeset/81159035 (road is circa osm.org/way/221353854#map=13/40.7078/-86.1217)
Seems like your editor tool is dropping bits and pieces of old edits without clearing them, and placed in weird places. Please get back ASAP I don't want this piece of road in my Garmin maps and want to delete this extraneous road quickly, but want you to fix your tools or workpath.

Uh WOAH, how did West 400S get overlaid on top of Mulberry St in Fort Collins. Please respond ASAP, may need to do an emergency revert on this.

Oops, I wrote the wrong changeset ID, that changeset doesn't even exist yet. Meant to write # 63648694

osm.wiki/Tag:healthcare%3Dphysiotherapist

Oops I noticed I did make a whole bunch of typos recently, caught one, must have missed this one. Not sure where I picked up this as the best way to tag a physical therapy shop that focuses on sports injuries. And perhaps the stupid spelling of the shop (took a double take when I saw the store today) deserves it... What would be the best way to tag these, I had been tagging them "clinic" but I don't think they deserve the icon they get.

Fixed overlapping highway created in this changeset on East 109th Ave in changeset # 79634821

It looks like you broke the turn restrictions you made earlier, may need to revisit them. However my question to you... there is a turn lane between the ways of West Broad Street which typically allows left turns as it buffers oncoming traffic so people don't have to wait for clearing in both directions. Why is this particular driveway special that there needs to be these turn restrictions and not others along the route? Perhaps there are actual signs prohibiting these turns but then the turn lane is kind of redundant?

Oops, I think I misunderstood your question, sorry for answering incorrectly. When I edit things now in iD, most of the times I end up zooming into the intersection very closely and randomly click on the items in the vicinity. For each intersection I should see specific items highlight as one would expect when I click on them.

Sometimes, however, I see it highlighting oddly. Other times I see a long highway and when clicking on it, I see a split highway (a gray node instead of a white node) despite the long highway. This leads me to investigate why, I start moving nodes around, also temporarily using the "disconnect" command in iD. The "UNDO" button is my favorite button as I do a lot of experimental edits to find the overlaps.

Otherwise without playing with the ways a bit with some careful scrutinization of the behavior of iD along the ways, it's really difficult to tell where the overlaps are. Sometimes KeepRight will flag but as said the cadence is too long and there are false negatives.

I don't know how else to better visualize these errors in iD other than by their behavior. And I see what you mean, the other thing I wish in iD was a way to manually select different objects at the same point even if it's not on the "top" of the stack. This causes me a lot more changes than necessary to get exactly what I want, including having to delete a node and put it back -- 1 mm (in the real world, not in the editor) off from where it was because I can't get it exactly where it was before when the best way to fix a problem is to remove the item on the bottom of the stack.

Don't know...should always demand more...?

Hey, since you seem to have interests in editing city boundaries, curious, cities tend to change in size due to annexation, etc. I've seen some sources where Berthoud has actually increased in sized close to your edit. Should Berthoud be increased even further? Example:
https://www.berthoud.org/home/showdocument?id=13571

OK I fixed this overlap: changeset is at
osm.org/changeset/79037833

I was able to fix another overlap at osm.org/note/2038869 -- luckily that one wasn't too hard to fix, just tedious. Used iD to fix(!)

I was able to fix the problem. This one wasn't as bad to fix as others I've seen. Please watch out for these problems before editing, and don't have too many cooks in the kitchen.

OKAY: The person who created the overlap is osm.org/user/yerramg who had version 1, not this last changeset. It's scary that people are editing on top of this before noticing a duplicate. This is kind of dangerous.

I was trying to fix some turn restrictions here but noticed the overlap so I stopped and tried looking for who caused it. Still tough to tell. Anyway the two broken ways can be determined without an editor through OSM main web browser, just "Query Features" on the point and it will show the two ways:
osm.org/way/700830577
osm.org/way/60542166

Both were touched by amazon but have to go back further in time to see who created them... these have been out here for a few revisions already which is kind of alarming.