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.

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

Hello DeBigC,

You're right, I should have contacted the Irish community for a changeset of this size. I thought that updating duplicate and deprecated tags was a helpful thing. I'll share some relevant documentation with you:

I updated ~50% of building:roof:shape tags, there used to be nearly 100k. Other changes were not that large. Both Taginfo and Wiki already show clear preferences for certain tags. I made the data more consistent.

https://taginfo.openstreetmap.org/compare/building:roof:shape/roof:shape
https://taginfo.openstreetmap.org/compare/building:roof:colour/roof:colour
https://taginfo.openstreetmap.org/compare/building:roof:material/roof:material
https://taginfo.openstreetmap.org/compare/building:roof_shape/roof:shape
https://taginfo.openstreetmap.org/compare/building:roof:levels/roof:levels
https://taginfo.openstreetmap.org/compare/building:roof:height/roof:height
https://taginfo.openstreetmap.org/keys/building%3Aroof#values

building:roof:shape=*
roof:colour=*
roof:material=*#Possible_tagging_mistakes
height=*#Possible_tagging_mistakes
osm.wiki/Simple_3D_Buildings

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.

> It's very difficult to review a single changeset with 3200 changes.

It's even more difficult to review 3,2k changesets with 1 change each. Choices have to be made and seeing that no one had taken up the job of updating these tags, I made this choice. There is no single solution that pleases everyone, but changes like this still need to be made.

If you can find or make a tool that splits up changes by geographic area, I'll happily use it, and I think several other mappers would also be very happy with it.

> that archavi link posted earlier errors out

That's a complaint to send to achavi rather than to me. Many changesets are larger than this one, imports for example.

You mean you want me to look at all 3,2k buildings individually and replace the same tags over and over again? The ctrl+F tool was invented and implemented specifically for this kind of usage.

In that case you can easily use achavi (https://overpass-api.de/achavi/?changeset=108548780) to zoom in to your area and review each specific object separately.

It's simply not feasible to split up thematic map changes per county, unless you know of a JOSM tool that can perform that kind of action.

Furthermore, you didn't answer my question: how would you prefer to review my 3,200 changes?

Who are you to dictate norms to anyone? OSM does not know the concept of authority. We collaborate. I fixed your tags, you're welcome.

"data consumers can easily translate" - or we can just produce good data in the first place, which is what I'm doing.

Of course a few "color" vs "colour" tags is not a life and death situation. Neither is the fact that I'm taking my time to fix them. I prioritise good data over my bbox size and I suggest that you do the same.

Nobody wants to do the same edit separately for each state, and even then people would complain about state-wide edits that are only a few hundred changes. Changes like this just need to be done.

Of course I wouldn't create tiny edits across the globe in a single changeset, but this one is large enough to warrant the large bbox.

Then how would you prefer to review my 3200 changes: in 10, 100 or 1000 changesets? How many people would bother to review 1,000 very similar tiny changesets?

There is no sweet spot that will please everyone. There are just a whole lot of outdated and erroneous tags. I just fixed a lot of them to make OSM data more consistent and understandable for data users and analysts.

commentaar is incorrect. Moet zijn: "oude 3dShapes opgeruimd, opritten toegevoegd, paar wegen recht gelegd"

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.

Hi Tekim, yes I can. I will do that when I'm at my desk.

Hello Tekim,

No one seems to have a problem with the contents of my changesets so far, only with the method, which I think is ridiculous because it's one of the few ways to get this kind of thing done.

I wouldn't call it a mechanical edit, because I reviewed all of the tag combinations before I changed them to avoid losing any information.

If you have suggestions to update deprecated and misspelled tags, I'm all ears.

Best regards

Casper

I can't code, so automating this process is out of the question for me, but I have figured out a workflow with taginfo, overpass turbo and JOSM to update deprecated tags reliably on a large scale.

If you have the skills to automate this process with smaller bboxes, I invite you to create a bot like that, so we can feed it deprecated tags to update.

Hi Michael,

These changesets need to be done globally to avoid fixing the same thing six or more times. As someone else I spoke to has pointed out: "Honestly it needed doing."

If it helps you, I will make a separate changeset for the German-speaking countries next time.

Best regards,

Casper

That would take me 4 to 6 times as much time with no real benefit. I would understand this request for smaller changesets, but the ones I made yesterday were just too big for that.
---

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

I only just noticed, lol. These bboxes need to be big so I can save myself some time.

Thank you for the reply.

I would prefer that you create a second account that you use to only or mostly delete things, because that would be perfectly valid and also much more helpful than bothering other mappers while you can just press delete yourself.

(If you chose to do it this way, an easy way would be to open iD in a different browser and simply delete outdated data with that, because I suspect that's faster than relogging in JOSM. )