<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div dir="auto">I propose to fix some obvious typos in tag values. Cases were found<br></div><div dir="auto">automatically and manually reviewed with sampling across values (in<br></div><div dir="auto">process some were entirely retagged).<br></div><div dir="auto"><br></div><div dir="auto">Content here is a mirror of<br></div><div dir="auto"><a href="https://community.openstreetmap.org/t/proposed-bot-edit-fixing-bunch-of-typos-in-tags/110039" rel="noopener noreferrer" target="_blank">https://community.openstreetmap.org/t/proposed-bot-edit-fixing-bunch-of-typos-in-tags/110039</a> as required by automated edits code of conduct<br></div><div dir="auto">- if you have seen then it is likely not worth rereading it here<br></div><div dir="auto"><br></div><div dir="auto">Typical example would be something like<br></div><div dir="auto"><br></div><div dir="auto">state before a mechanical edit (example for a tunnel value):<br></div><div dir="auto"><br></div><div dir="auto"> highway=footway<br></div><div dir="auto"> tunnel=building_passage2<br></div><div dir="auto"> layer=-1<br></div><div dir="auto"><br></div><div dir="auto">state after an edit:<br></div><div dir="auto"><br></div><div dir="auto"> highway=footway<br></div><div dir="auto"> tunnel=building_passage<br></div><div dir="auto"> layer=-1<br></div><div dir="auto"><br></div><div dir="auto">Full list of values is at<br></div><div dir="auto"><a href="https://wiki.openstreetmap.org/wiki/Mechanical_Edits/Mateusz_Konieczny_-_bot_account/fix_many_obvious_typos#What" rel="noopener noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Mechanical_Edits/Mateusz_Konieczny_-_bot_account/fix_many_obvious_typos#What</a><br></div><div dir="auto"><br></div><div dir="auto">(in case of finding more cases like this - can I just add them to bot<br></div><div dir="auto">edit? Or should I make a new thread here and on talk mailing list)<br></div><div dir="auto"><br></div><div dir="auto">Why it is useful? It helps newbies to avoid becoming confused. It<br></div><div dir="auto">protects against such values becoming established. Without drudgery<br></div><div dir="auto">that would be required from the manual cleanup. It also makes easier to<br></div><div dir="auto">add missing surface= values and makes easier to use OpenStreetMap data,<br></div><div dir="auto">including support in editors which explain/translate meaning of surface<br></div><div dir="auto">values.<br></div><div dir="auto"><br></div><div dir="auto">Why automatic edit? I have a massive queue (in thousands and tens of<br></div><div dir="auto">thousands) of automatically detectable issues which are not reported by<br></div><div dir="auto">mainstream validators, require fixes and fix requires review or<br></div><div dir="auto">complete manual cleanup.<br></div><div dir="auto"><br></div><div dir="auto">There is no point in manual drudgery here, with values obviously<br></div><div dir="auto">fixable.<br></div><div dir="auto"><br></div><div dir="auto">This values here do NOT require manual overview. If this cases will<br></div><div dir="auto">turn out to be an useful signal of invalid editing than I will remain<br></div><div dir="auto">reviewing nearby areas where bot edited.<br></div><div dir="auto"><br></div><div dir="auto">I already skipped edits to primary tags except few blatant cases where<br></div><div dir="auto">mistake is easy to miss (flowerbed until recently was not rendered).<br></div><div dir="auto">Typos in primary tags that cause them to be outright missing from<br></div><div dir="auto">typical map rendering is often coupled with other serious problems.<br></div><div dir="auto">Probably because it indicates mapping by newbies who are likely to be<br></div><div dir="auto">confused also by other complexities. The same goes for access tags that<br></div><div dir="auto">I will keep fixing manually. Though typos in for example shop values<br></div><div dir="auto">are safe to fix automatically, probably because effects are less<br></div><div dir="auto">noticeable. Also, more obvious typos in rare, typically not rendered<br></div><div dir="auto">amenity tags are often safe to fix.<br></div><div dir="auto"><br></div><div dir="auto">Yes, bot edit WILL cause objects to be edited. Nevertheless, as result<br></div><div dir="auto">map data quality will improve.<br></div><div dir="auto"><br></div><div dir="auto">This values were found automatically based on taginfo and iD presets,<br></div><div dir="auto">also accessed via taginfo.<br></div><div dir="auto"><br></div><div dir="auto">Taginfo values statistics list values in OSM database, while iD presets<br></div><div dir="auto">list which values are known for given keys.<br></div><div dir="auto"><br></div><div dir="auto">Multiple heuristics were applies to find various typos, for example<br></div><div dir="auto">“cuisine=bubble tea” was found to match “cuisine=bubble_tea” from iD<br></div><div dir="auto">presets after space was replaced by underscore.<br></div><div dir="auto"><br></div><div dir="auto">“cuisine=Thai” to “cuisine=thai” after lowercasing value.<br></div><div dir="auto"><br></div><div dir="auto">“cuising=regional1” to “cuisine=regional” after skipping ending.<br></div><div dir="auto"><br></div><div dir="auto">All values were looked at then manually to drop any dubious replacement<br></div><div dir="auto">(for example healthcare=nursery to heatlhcare=nurse was skipped).<br></div><div dir="auto"><br></div><div dir="auto">Samples was also looked at in OSM, with many values just edited. Note<br></div><div dir="auto">that not each replacement was sampled: as many, many have just few<br></div><div dir="auto">cases, so sampling and verifying ends with just editing all of them<br></div><div dir="auto">manually.<br></div><div dir="auto"><br></div><div dir="auto">If you see any values where edit would be dubious, not safe or in any<br></div><div dir="auto">way problematic: let me know.<br></div><div dir="auto"><br></div><div dir="auto">(BTW, one typo in iD presets was found while looking for typos, see<br></div><div dir="auto"><a href="https://github.com/openstreetmap/id-tagging-schema/pull/1063" rel="noopener noreferrer" target="_blank">https://github.com/openstreetmap/id-tagging-schema/pull/1063</a> )<br></div><div dir="auto"><br></div><div dir="auto">Some conversion were found manually in addition to iD presets,<br></div><div dir="auto">currently it is only cycleway:both and shop=gun.<br></div><div dir="auto"><br></div><div dir="auto">I also contacted community already in some cases (like sport values<br></div><div dir="auto">with ; and in some cases of extra trailing characters) - via changeset<br></div><div dir="auto">comments and notes.<br></div><div dir="auto"><br></div><div dir="auto">Response confirmed that this changes are a good idea - and that just<br></div><div dir="auto">editing will be better than asking more people.<br></div><div dir="auto"><br></div><div dir="auto">This edit will be rerun in future as many of such typos are expected to<br></div><div dir="auto">reappear.<br></div> </body>
</html>