piebro/osm-data huggingface dataset:
Friendly_Ghost (2021-07-25 10:58:35+00:00): Workflow is as follows: 

1. Browse Taginfo & Wiki for common tagging mistakes and deprecated tags.
2. Run a global query with overpass-turbo.eu, in this case nwr[“color”]. (If tags have too much or too little usage for a global query, use a bbox or country search area instead.)
3. Load in JOSM.
4. ctrl+F --> color=* and colour=* --> remove color=*.
5. ctrl+F --> color=* + “building:colour”=* --> remove color=*.
6. ctrl+F --> color=* + building=* --> update color=* to building:colour=*
7. ctrl+F --> color=* + “building:part”=* --> update color=* to building:colour=*
8. ctrl+F --> color=* --> update to colour=*
9. Press upload just to run the validator.
10. Update some outdated roof tags (like building:roof:shape=*) in the same way with ctrl+F.
11. Fix other issues that the validator picks up.
12. Run the validator again to check if the fixes work.
13. Upload all changes. 

All in all it takes a couple of hours to do.
G1asshouse (2021-07-26 02:37:17+00:00): I find your mass change of one tag to another troublesome. Since both spellings (color/colour) are correct, I assume your changes are based only on forcing uniformity. As much as that is a useful goal, the OSM community has for a long time expressed that it values flexibility and mutability of the tags over the perfect conformity of the tags.
Without communicating with the OSM community at large, it is not possible to know if the “color” tags were tagging mistakes or a user’s preferred tagging scheme. If they were a preferred tagging scheme, then a conversation among the OSM community needs to occur to decide if we live with both spellings or if, as a group, we override the few editors, who prefer “color”, and force the change to “colour” only. Your actions make it appear that you have misinterpreted “depreciated” and “discouraged”, which is used as heavy social pressure and not to mean “these are mistakes that no one has yet taken the time to fix”.
snoozingnewt (2021-07-26 02:59:12+00:00): So there's actually been a bit of discussion on the OpenStreetMap World Discord Server and the general consensus is that the correct spelling is "colour". It's not like the edits went ahead with no discussion and no approval.
G1asshouse (2021-07-26 07:31:21+00:00): I respect you and anyone that enjoys the community side channels. With all due respect, those are not official OSM channels and the final discussion needed to occur on the mailing list and OSM wiki. It gets very frustrating when folks conflate the many OSM community side channel with appropriate, community agreed upon OSM discussion methods/sites.
For those interested, here is the first mailing list conversation, I have found, related to this user's changesets.
https://lists.openstreetmap.org/pipermail/talk/2021-July/086817.html
Friendly_Ghost (2021-07-26 08:55:46+00:00): Optimistically speaking, even if a few hundred people are subscribed to the mailing lists, they still don't represent the entire OSM community. From that POV, the Discord server does a better job, even though it's a side channel. 

The Wiki already lists color=* as deprecated and searching for key:color redirects you to key:colour. 

We are making geospatial data so it can be used. Using data is easier when there are No multiple tags that mean the same thing, especially if one is barely in use compared to the other and is also marked as deprecated. I set out to fix that and make it consistent for everyone who wants to use colour data. You're very welcome.

The automated edits code of conduct lists obvious typo fixes as acceptable usage. That's what I did. 

I'm not presenting a full plan to the mailing lists either when I fix highway=residental or =Residential. That level of bureaucracy would stagnate OSM completely. Changes like this just need to be done.
G1asshouse (2021-07-26 11:03:12+00:00): The mailing list is the agreed upon final community discussion location. Just because you've isolated yourself with like-minded people, on discord, does not make it an appropriate alternative to the mailing list. You are welcome to bring this point up to the mailing list and state your logic for using discord instead. As of now, contrary to your wishes, Discord and other side channels are inappropriate.

My point that you do not know if there are OSM editors whom prefer to tag with color instead. If it is not a "typo" then it's a valid tag...even if heavily discouraged. I wish to emphasise that you have not done due diligence with the larger community and may have just blindly robed another OSM editor of their right to make reasonable tagging choices, especially if those choices differ from the community as a whole.

This whole thing smells a lot like "it's better to ask for forgiveness than approval". I don't think you've made these large changes out of ignorance of the community standards. I get a strong feeling that you are very aware of your actions.
If I am correct, then I find your destain for the larger OSM community to be reprehensible.
maraf24 (2021-07-26 13:43:38+00:00): That's funny: https://www.openstreetmap.org/way/616060622
What's the point in correcting the name of "color" tag for leisure=park?
Friendly_Ghost (2021-07-26 16:47:35+00:00): @maraf24 ¯\_(ツ)_/¯ Ask the mapper who originally mapped color=* there. 

You can run an Overpass query with ["leisure"]["colour"] to see if this kind of issue occurs more often, and thanks to me you don't have to check both ["leisure"]["colour"] and ["leisure"]["color"] to get a complete result.
maraf24 (2021-07-26 18:34:41+00:00): What is the colour of this building: https://www.openstreetmap.org/way/373879419/history ?
On what grounds have you decided that it is grey, not white?
snoozingnewt (2021-07-26 18:37:31+00:00): What's better? A less active 'official' discussion, or a more active 'unofficial' discussion? And I find it a bit insulting to generalize all osm discord users like that.
snoozingnewt (2021-07-26 18:52:52+00:00): And @maraf24
Friendly_Ghost isn't adding any colors... ask the original mapper, not him. He's only changingcolor=* to colour=*.
maraf24 (2021-07-26 19:19:55+00:00): @snoozingnewt: That's suprising. You are the second person who thinks I asked about the validity of colour tag on park object, where I specifically asked about the validity of changing the name of the tag. Or in other words - why leisure=parks were not filtered out in the query.
My conclusion is: queries and  logic for these changes are flawed and this changeset should be reverted.
If these edits was discussed before on Discord channel than this discussion was also flawed.
snoozingnewt (2021-07-26 20:54:18+00:00): You... were asking about the color of a building. I was responding to that part. Obviously, the original question is something I cannot answer. I don't get your point.
snoozingnewt (2021-07-26 20:54:55+00:00): "What is the colour of this building: https://www.openstreetmap.org/way/373879419/history ?
On what grounds have you decided that it is grey, not white?"
Friendly_Ghost (2021-07-26 23:54:16+00:00): My apologies to G1asshouse, I'll reply properly to you when I have more time.

@maraf24 Thank you for demonstrating that our map/database contains many different inconsistencies. I cannot fix all issues on my own, so if you think parks shouldn't have a colour, please file a JOSM and iD issue so the validator can pick it up the next time someone tries to edit something similar, and help us by fixing the currently existing "coloured parks" with the overpass query I mentioned. 

Concerning that one building you mentioned, it was already tagged as a building with building:colour=grey before I came along. I did not change that and I did not decide anything at all.
Friendly_Ghost (2021-07-27 18:24:32+00:00): @G1asshouse

> The mailing list is the agreed upon final community discussion location. Just because you've isolated yourself with like-minded people, on discord, does not make it an appropriate alternative to the mailing list.

I find it funny that you think I have “isolated myself with like-minded people”, because it shows your lack of familiarity with the Discord server. You’re very welcome to join it and participate in discussions and chatter. 

I’m absolutely not bringing every tag change I make to the mailing lists. What’s the threshold for contacting them? Ten changes, a hundred, a thousand? Getting bogged down in bureaucracy would mean that none of us will have any time left to just map. I’m sure you wouldn’t mail them for a tag change from highway=Residental to highway=residential, I’m doing exactly the same except I’m doing it on a larger scale. 

> My point that you do not know if there are OSM editors whom prefer to tag with color instead. 

I don’t need to know that. What you, I and all other mappers need to know is that color and colour mean 100% exactly the same, that OSM has a guideline to choose British over American English, that colour is many times as popular as color and that data/map users find our data more useful if it is consistent. I contributed to that in this changeset and others and you're very welcome.
Korgi1 (2021-07-27 19:38:44+00:00): Classic European forcing eurocentric spelling on us poor Americans.
Friendly_Ghost (2021-07-27 22:54:33+00:00): @Korgi1

1. There's no point in playing the victim. You know as well as everybody else that OSM in general prefers British spelling over American spelling. You can also compare former color=* usage (see this changeset) with https://taginfo.openstreetmap.org/keys/colour#chronology . You'll find the same trend for other keys where GB & US spelling differ. 

2. That's not eurocentric, that's a global thing. See https://taginfo.openstreetmap.org/keys/colour#map for reference.
G1asshouse (2021-07-27 23:43:25+00:00): @Korgi1
(I understood your sarcasm)
Please don't gaslight anyone. It's not about the spelling.
G1asshouse (2021-07-27 23:49:28+00:00): @Friendly_Ghost
> The mailing list is the agreed upon final community discussion location. Just because you've isolated yourself with like-minded people, on discord, does not make it an appropriate alternative to the mailing list.
I find it funny that you think I have “isolated myself with like-minded people”, because it shows your lack of familiarity with the Discord server. You’re very welcome to join it and participate in discussions and chatter. 
I’m absolutely not bringing every tag change I make to the mailing lists. What’s the threshold for contacting them? Ten changes, a hundred, a thousand? Getting bogged down in bureaucracy would mean that none of us will have any time left to just map. I’m sure you wouldn’t mail them for a tag change from highway=Residental to highway=residential, I’m doing exactly the same except I’m doing it on a larger scale. 
> My point that you do not know if there are OSM editors whom prefer to tag with color instead. 
I don’t need to know that. What you, I and all other mappers need to know is that color and colour mean 100% exactly the same, that OSM has a guideline to choose British over American English, that colour is many times as popular as color and that data/map users find our data more useful if it is consistent. I contributed to that in this changeset and others and you're very welcome. 

“...it shows your lack of familiarity with the Discord…”
“... join it and participate…”
My discord personal history with Discord in general and OSM discord servers in particular is irreverent. Though, it is clear that you don’t know who I am and have no idea if I’m already there or even how long ago I joined. I am aware of you though.

“Getting bogged down in bureaucracy would mean that none of us will have any time left to just map.”
The fact that you refer to the larger communities’ request to be included in significant changes to the date base as “bureaucracy” is why your behavior here is objectively grotesque. The whole of the community owns the data set not just you and your friends. To intentionally exclude the community because it inconveniences you is the definition of self-centered. This orientation is obnoxious in life but destructive when in a group setting (such as OSM).

“ highway=Residental to highway=residential”
Your “borrowed” example is not analogous to what you’ve done. It’s also irreverent. The complaints are about your actions and not the inclusion or exclusion of the letter “u”. Further complaints are in regard to your behavior to the communities’ complaints.

“I don’t need to know that.”
“ What you, I and all other mappers need to know…”
“ you're very welcome”
Honestly, I was going to defend you when another OSM editor called you arrogant. Was.
Friendly_Ghost (2021-07-28 00:11:14+00:00): Dear G1asshouse,

To change the topic back to the original constructive discussion, 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.

Best regards

Casper
tekim (2021-07-28 00:18:52+00:00): >  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:   
https://wiki.openstreetmap.org/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
Friendly_Ghost (2021-07-28 00:30:59+00:00): Thank you, tekim, for consisely explaining the procedure to me. That looks very reasonable and I'll use that approach for my next large edit.
Woazboat (2021-07-30 01:47:45+00:00): Welp, I just spent an hour writing a sizable comment in response only to lose it all because I acidentally clicked on a link while trying to resize the comment text box.... 

To sum it up: 
I agree with the changes by @Friendly_Ghost and putting it into a single changeset. Changing `color` to `colour` is clearly correct with little chance of accidental harm. Having multiple spellings and variants of the same thing is harmful to OSM, leads to more unnecessary work for data consumers and has detrimental effects on the software ecosystem around OSM and the usefulness of the database as a whole. (Correcting for one mistake in software is fairly easy, correcting for hundreds is not. Things that could be fixed with a simple change like this in the upstream database have to be worked around a hundred times over in every single downstream application.)

Breaking up large changsets like this without any clearly disjoint clusters does not provide much benefit and has some clear disadvantages. Changesets exist to group changes that belong together. This benefit is lost when the changes are split up and understanding and working with multiple spread out changesets is much harder. Yes, having a changeset like this pop up in your feed when there's no acutal change in your area can be annoying, but the large bounding box cannot really be avoided when the changes actually are spread out across the world. Breaking up the changes into smaller areas does very little to avoid this as there will most likely still be one of these smaller changesets covering a particular area.
drkt (2021-07-30 11:28:41+00:00): I've said this in the Discord and I'll say it again, here. 

Verbatim:
"This changeset size thing just sounds like a poor software problem, to me, not a poor practice problem. I grant my domain is very tiny, but there is a mapper in my country who makes changesets that span my entire domain pretty often, but it's all good data. I use whodidit to see what the changes actually were in the area I care about, rather than review their whole changesets everytime they cross my domain"

To add / clarify:
You have the tools available to filter out bboxes that cover your area but add nothing. That you choose not to use them, or are not aware of them, is not their problem. This particular changeset goes over my area, while changing nothing in it. This went completely over my radar because I don't go by bboxes. I literally did not even know this changeset spanned my area.
eggie (2021-07-22 14:21:26+00:00): Beste hendrik_gt

Wat houden je edits in?

Dat is niet op te maken uit je commentaar.

Ook het gebied van je edits is erg groot en niet te controleren.
Wat is je bedoeling?

MVG
eggie
hendrik_gt (2021-07-22 14:39:08+00:00): Hoi Eggie,

Het idee is om deze historische watergegevens (hydrografie) (nu vanuit paleografie datasets geëxtraheerd) beschikbaar te maken voor modellering en visualisatie van de hydrologische situatie van 1672 (De Oude Hollandse Waterlinie). 

Met vriendelijke groeten,

Hendrik_gt
Commodoortje (2021-07-22 14:41:06+00:00): Hallo Hendrik,
Het lijkt hier te gaan om een massa import, klopt dat?
eggie (2021-07-22 14:42:43+00:00): Oke,  De bedoeling is vast goed, maar in OSM is het motto Map what's on the ground en dan horen historische gegevens niet in de data van OSM.
Daar zou je een aparte layer voor kunnen gebruiken.
Bv 
http://umap.openstreetmap.fr/nl/ voor eigen layer in OSM 

MVG
eggie
hendrik_gt (2021-07-22 14:46:30+00:00): Hoi Eggie,
Oke, ik dacht start_date = 1500 juist door OSM gepropageerd werd om het onderscheid te kunnen maken voor historische gegevens. 
Als het beter is dat via umap te gaan doen. Vind ik ook ok.

Wat stel je voor? Zal ik de data zoals zojuist geupload weer verwijderen (en hoe doe je dat?). 

Gerrit
eggie (2021-07-22 14:49:15+00:00): Dag Gerrit 
Over historische gegevens is wel consensus omm die niet op te nemen in OSM ...  Voor massaimport gelden ook speciale regels. Zie wiki osm. 
Daar is een speciale plugin voor.

Ik kan  alles reverten van nieuw naar oud.
Over historische gegevens is wel consensus...  Voor massaimport gelden ook regels. Zie wiki osm. 
Daar is een speciale plugin voor.
Akkoord?
Commodoortje (2021-07-22 14:49:40+00:00): Hopelijk lukt het om de changesets te reverten, maar het zijn aanzienlijke changesets. Het kan maar zo dat alleen de DWG dit kan doen.
Mijn voorstel is dan ook om even niets te doen, om problemen te voorkomen.
eggie (2021-07-22 14:53:57+00:00): Commodoortje en Gerrit.. Ik houd even pas op de plaats.
Even overleg...
hendrik_gt (2021-07-22 14:55:07+00:00): Commodoortje en Eggie

Als jullie mij nog kunnen voorzien van een soort van 'good OSM practice' dan hoor ik dat graag. Die Wiki is typisch een wiki die goed werkt als je weet waar je moet zoeken. 

Kan ik zelf een changeset reverten, zo ja, hoe?

Gerrit
Leo Slager (2021-07-22 14:55:24+00:00): Succes met reverten, er zullen ongetwijfeld vele conflicten ontstaan.
eggie (2021-07-22 14:58:12+00:00): Gerrit.. Je bent buiten Nederland begonnen voor HOT OSM. Daarom heb je nooit de welkomstmail ontvangen.
Ik zal je dat per PB toesturen incl. de nodige links en tips. 
Zelf reverten kan niet zonder de nodige ervaring.. 
Even het overleg afwachten
eggie
eggie (2021-07-22 15:09:47+00:00): Ik heb deze actie even naar iemand van de DataWorkingGroup  (DWG)  doorgespeeld.
eggie (2021-07-22 15:12:24+00:00): Op het forum van OSM loopt een draadje
https://forum.openstreetmap.org/viewtopic.php?pid=835741#p835741
Commodoortje (2021-07-22 15:21:54+00:00): Hendrik, goed dat je zo snel hebt gereageerd op de reactie van eggie.
Op dit moment wordt naar een oplossing gezocht, tot dan even geen edits verrichten.
Commodoortje (2021-07-22 17:07:07+00:00): Zoals ik heb gelezen, heeft eggie je inmiddels de welkomstmail verzonden met wat links en tips.
.
Ik weet niet zeker of hier een link naar de good practice van OSM bij staat, mocht dit niet het geval zijn dan is het onderstaande link.
https://wiki.openstreetmap.org/wiki/NL:Good_practice
. 
Ook stuur ik nog een link die belangrijk is, aangaande inmports binnen OSM.https://wiki.openstreetmap.org/wiki/Import
.
Hopelijk ben je niet geheel afgestompt, en wordt je een goede mapper. Ik wens je in ieder geval veel plezier met je toekomstige goede bijdragen binnen OSM.
Mocht je vragen krijgen stel ze dan gerust, in het forum, aan prive mappers, wiki's nalezen.
marczoutendijk (2021-07-26 17:46:10+00:00): De gehele import van hendrik_gt is door de DWG teruggedraaid.

Marc Zoutendijk  
OpenStreetMap Foundation  
Data Working Group
mueschel (2021-07-28 17:42:01+00:00): Hi Marc,
it looks like there are 9 ways left:
http://overpass-turbo.eu/s/19P4
marczoutendijk (2021-07-28 19:19:41+00:00): Obviously because they were "touched" after the date we used for our repair.
I'll fix them tomorrow.
Thanks!
marczoutendijk (2021-07-28 20:03:35+00:00): I mean "before"!
I have fixed some of them right now.
The others go tomorrow.
tguen (2021-08-05 06:37:39+00:00): Hello msemerni

Please use better changeset comments. They should describe the changes you're making, e.g. "add landuse for marketplace". The comments you're using have no obvious meaning.

I see you've been making edits all over the US. Where does your data come from?
Cartographer10 (2021-07-23 07:52:02+00:00): Hey,

Je hebt de Orthodontie praktijk als losse node toegevoegd. Er staat een adresnode langs en in NL is het gebruikelijk om bedrijven op de adresnode te taggen. Zo is ook meteen de adresinformatie goed gekoppeld.

Zou je dit even kunnen corrigeren?

Mvg,
Vincent
pieleric (2021-07-23 08:21:22+00:00): Ja, inderdaad. Ik was met alleen de telefoon, en in principe is het mogelijk in OsmAnd tagen te toevoegen, maar het lukte niet.
Nu gecorrigeerde!
Cartographer10 (2021-07-23 08:27:53+00:00): Ah oke, ik zag al dat het via de telefoon ging. Maar geen probleem. Fijn dat je het zo snel hebt opgelost.
Vinber-Pro (2021-07-22 18:35:38+00:00): Il est plutôt recommandé de mettre dans description, pas dans description:fr (https://www.openstreetmap.org/node/6828011428)
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/108431112
Donlooba411 (2021-07-22 21:34:33+00:00): c'est noté ! merci
Nakaner (2021-07-26 07:39:59+00:00): Hallo,

Hochwasserabfall-Umlade- bzw. -Lagerplätze sind vsl. derart temporärer Natur, dass sie nicht erfassenswert sind. Zur Erfassung solcher Objekte bieten sich persönliche Karten mittels uMap (https://umap.openstreetmap.de) an.

Viele Grüße

Michael
Nakaner (2021-07-26 07:40:46+00:00): PS Ich habe den Änderungssatz durch https://www.openstreetmap.org/changeset/108601470 rückgängig gemacht.
eggie (2021-07-22 14:35:40+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht. 

'k Zie hier trouwens een foutmelding .. Een weg kan nooit eenrichtingsverkeer zijn als die dood loopt. 

warnings:impossible_oneway:highway
MVG, 

Eggie 

Namens de OSM Community
Vinber-Pro (2021-07-22 18:34:18+00:00): Bonjour Alban, chouette de te revoir ici !
attention tu as tasnformé tout le batiment de l'école en oeuvre d'art https://www.openstreetmap.org/way/72686704

et ici https://www.openstreetmap.org/node/4213749395 tu as ajouté l'oeuvre à un noeud d'adresse. Il est préférable de faire un point à part.

Bonne carto
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/108432978
Donlooba411 (2021-07-22 21:45:58+00:00): Hello Vincent,
Je reprends du service ! et je suis déjà grillé ! :-))
Depuis mon transfert à la communauté Pays Basque, la carto du festival a "flotté. Il était que je reprenne un peu  les choses en main.. J'espère une intégration ce travail au nouveau SIG de l'agglo. Avec un peu de chance on sera raccord au niveau du timing ! ^^
Vinber-Pro (2021-07-27 05:29:41+00:00): Super !

est-ce que je te laisse corriger pour l'école et le noeud adresse ?
Donlooba411 (2021-07-27 09:18:55+00:00): Désolé ! j'ai ajouté l'oeuvre hors du polygone mais oublié de supprimer l'attribut en erreur. Je pense avoir bien fait ; si tu peux vérifier ? merci
girinj (2021-07-22 13:57:34+00:00): Hi SafetyIng, 

Thanks for your response. In this scenario, I can find a road leading to human settlement and the pavement looks like the track which is shown in the examples of OSM wiki. Please look into the changeset(108433013) as per your suggestions. can you please guide on how to go ahead in these kind of scenario, can we prioritize the human settlement over the pavement(similar to track) of the road and create a service road. Please let us know your thoughts on this. Always happy to learn from the community.

 Regards
girinj