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 changeset/81159035 (road is circa 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

healthcare=physiotherapist

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
changeset/79037833

I was able to fix another overlap at 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 @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:
way/700830577
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.

There are two copies of E. Chestnut on top of each other. Seems this is the last edit but unsure when the overlap was created, could you take a look?

Not sure who caused this issue, but there is an overlapping road here and you were a recent editor of this road, if you could fix it that would be great. The problem area is at (39.50248,-74.99426) near the service road. If you don't understand the problem, feel free to please contact me.

It looks like @Oksana%20Chubatenko is touching the same areas that the old Daria_something was touching... something strange is going on here. Confused here.

It's 5PM here now, where are the nodes?

I just saw this and thanks for the revert of the deleted business nodes, though duplicates showed up. I'd like to mention I ended up manually deleting the (other?) duplicates, hopefully the current state is accurate (specifically the Greeley,CO nodes.)