I have developed a script that automatically corrects the capitalization of the diet:vegan tag from “Yes” to “yes” to allow for easier searching / rendering.
This currently affects 131 nodes, exclusively in the UK (I have already manually fixed the single one outside the uk).
If you approve I would be running a simple script on my user account, where you can also contact me: wombatmaper | OpenStreetMap
I have already tested my script, locally as well with a single edit on production, that worked as expected: Changeset: 156192667 | OpenStreetMap
I would also rerun the script every month or so, to ensure that the tagging stays consistent.
If this works I hope to repeat the process with diet:vegetarian (I am starting with vegan as it has fewer objects). Furthermore I can think of some additional tags that this could be applied to, in future:
I’d suggest to check the affected objects for other tags with a capitalized values - Often these things happen not on a single tag, but on all changes of an edit.
When you already touch them, it’s best to fix all the mistakes at once.
Have you spot checked some values? Are they coming from various confused users or single bad import/specific editor/are related to some more serious data damage?
It seems like the largest portion are “weatherspoons” pubs, mostly edited by GAFAAAAA | OpenStreetMap (I have contacted the user). Though there are some outliers. The user has also put a few “Yes” tags into other fields.
I agree that that would be ideal, however it would significantly increase the scope of what I want to achieve, as well as requiring some quite complex logic (should all “Yes” be fixed or only some tags?), and potentially cause edits in other regions.
(for those unfamiliar) that’s also a typo. There are a few others.
While this change obviously makes sense (“Yes” is a typo for “yes”, and couldn’t logically mean anything else), I’d have thought you’d just be able to do it in one edit in Josm without the need for a script? Define one or more overpass queries (based on this), fetch the data into Josm, edit the one value you want to change and write it back?
From my understanding this would still require consultation with the community as a semi automated edit, and would create one huge edit instead of many smaller ones?
Generally speaking yes - although a “typo fix” from “Yes” to “yes” normally wouldn’t need to be discussed since the “wrong” value can only mean one thing. Problems occur with (say) changing “gr” to “gravel” when it might also mean “grass”.
Arguably a UK-wide changeset with 131 nodes in it is easier to manage than 131 changesets for individual nodes. You can be descriptive in the changeset comment to say exactly what you are doing and refer to this forum thread there or in the changeset discussion.
I suspect this won’t need to be rerun, since it is the result of a previous (mis)automated edit. New users might use “Yes” instead of “yes” in future, but that’ll be solved by talking to them as they do that.
