I'm not sure of some of these edits, looks suspicious.

Uh wow... Looks like this edit is messed up, should we request a revert on this?

Okay, made some changes in changeset #83831641 - Kind of tough to categorize this natural area - as far as I know there's nothing special about this land other than a creek goes through it. Pretty much just leaving it open and letting people walk through it on the designated paths (i.e. no camping, etc.) but mainly letting it be a gap to prevent more urban sprawl / development.

This is a bit different than Long View Farm Open Space to the south. This is yet a different category, and it too needs to be worked on...

Hmm... Kind of a tough call. With it marked type=boundary instead of multipolygon it no longer seems to recognize it as two areas and just as a boundary. I'm not sure what these should be considered as - like a city boundary or a polygon like landuse?

Indeed it seems having both leisure= and landuse=recreation does seem redundant, but it is possible for protected area to have leisure prohibited, and that numerical denotation boundary=protected_area seems really confusing, ugh. Feel free to change it, I was hoping to change as little as possible from the previous configuration hence the original tagging remained.

I'm not sure if way/768453082 is a public road, will people be angry if general public use it as a shortcut between Hwy13 to Hwy15?

Thanks, one more comment - you might also want to mark the allowed access tag to disallow vehicles but allow bicycles, horses, and pedestrians since these modes of transportation are narrow enough to squeeze in between.

Agreed there is a path from Summit View Drive to Timberline Road, I will be willing to bet this owner will not be happy people are driving through their yard. Suggest this passthrough be broken up to proactively prevent people from driving through this pathway.

While I agree there is a way to walk through on way/779877602, this does not appear to be a road that connects the two in the two houses' yards and should not be connected in this way.

There appears to be a bollard blocking access from Hearthfire Drive to the new road addition, has this been removed recently? I can see in mapbox imagery, maxar has some hints of them which I'm not sure if AI can detect, and the other imagery is too fuzzy to tell. Also this does not appear to be paved and should be marked as such.

I'm not local but perhaps you are. Just wondering if you knew which end of Thunderbird Boulevard are you not allowed to make a U-turn (east or west end or both)? The no u-turn restriction 9926202 is not valid until you select the 'via' member for the relation - the east or west end.

Yeah there are a lot of them around, unfortunately I'm not affiliated (nor really want to be affiliated) with any other organizations. Would be nice to have a shared authentication that all OSM users can use directly. The comments field works but quickly devolves off topic such as what I just wrote...sorry again...

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 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 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