> I am still eager to know how you would approach and resolve the issue that OSM contains a large quantity of redundant and duplicate data.
* Write a proposal such as this, and put it on the wiki:
osm.wiki/Mechanical_Edits/malenki
* Send an email to the *official* OSM mailing list announcing your intention, providing a link to your plan, and seeking feedback.
* Incorporate feedback received.
* Execute your plan

Not sure what happened, but this changeset does have actual changes in both Arizona and Michigan. Otherwise things look pretty good. You did a lot of work in Michigan. Just need to finish that giant forest polygon
---

Published using OSMCha: https://osmcha.org/changesets/108653009

Given that there are a number of houses along this road: way/16349170
I would say that it should be left as highway=residential.

"University layouts are in public domain to help people understand the locations quick and clear" - Just because a map is viewable by the public, does not mean it is "in the public domain." The fact that the map "help people understand the locations" also has no bearing as to whether the map is in the public domain or not, or as to what license the map creator/owner may have attached to the map. If you want to use sources like this you need to contact the university and get explicit permission to do so.

If every data element (way, node, relation) was individually reviewed, then it is not a mechanical edit, but based on what Casper has said, that is not what happened here (for example, there was no mention of loading all elements about to be changed into something like the todo list and looking at each one individually).

I would prefer to just review those in my metro area or county.

> Then how would you prefer to review my 3200 changes
If you don't have enough respect for our community to follow our norms and invest the time, effort, and skill (or recruit others with the necessary time and skill to help you) to do things inline with community expectations and rules, then I would prefer that you do not make this type of change at all. The fact that there are a few "color" vs "colour" tags is not a life and death situation for OpenStreetMap, and data consumers can easily translate if it is important to them.

BTW, regardless of what you call it, this does fall under the Automated Edits Code of Conduct[0], which states the code covers the "use of find-and-replace functionality using a standard editor such as JOSM "

[0]osm.wiki/Automated_Edits_code_of_conduct

Thanks, I understand things happen.

Please limit the geographic extent of your changesets to a more reasonable size
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108536838

Pretty arrogant for you to post yet another changeset with a huge geographic extent after you have been informed via changeset comments on one of your other changesets that this is not appropriate. Also, this appears to be a mechanical edit, which is also not appropriate.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108548780

Nice job! Thanks for the edits!
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108551391

Can you share your workflow with us?

Thanks again for the edits, and your reply.

I have never used Streetcomplete, but I raised this on the mailing list, and here is what was reported as a way to avoid this problem:

"Uploading solved quests manually before solving a geographically distant
quest, it's a pretty prominent button in the upper right of the main
screen. "

Another changeset with a large geographic extent. You really should group all of the Boulder edits together one changeset, and group all of the Egan edits in a separate changeset, and then have a third one for those in the middle of Iowa.

Hello again,

This change set also spans a large geographic area, it really should be two separate changesets.

Mike

Thanks for the edits. In the future, please limit the geographic extent of your changesets to a smaller area, for example, a couple of neighbourhoods. This changeset has edits in Egan MN; Boulder, CO; and somewhere in the middle of Iowa. It really should be three separate changesets.
---

Published using OSMCha: https://osmcha.org/changesets/108503646

Thanks for the edits, but please, limit the geographic extent of your changesets! Many of us try to monitor our local area for changes, and these large changesets show as being in our area, regardless if there were actually any changes in that area.
---

Published using OSMCha: https://osmcha.org/changesets/108496890

Thanks for the edits on this task! The fire is long out - thankfully, but I am sure there will be other disasters, so this still helps.
---

Published using OSMCha: https://osmcha.org/changesets/108342480

Thanks for the edits Beth!
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108388275

Please!, find a way to group these changes by geographic area, and keep the bboxes a reasonable size.
---

Published using OSMCha: https://osmcha.org/changesets/108430155