<div style="font-family: helvetica; font-size: 14px;">Agree with ：</div><div style="font-family: helvetica; font-size: 14px;"><br></div><div style="font-family: helvetica; font-size: 14px;"><span> surface=surface</span><div> surface=Maxar<br></div><span> surface=a</span></div><div style="font-family: helvetica; font-size: 14px;"> surface=*</div><div style="font-family: helvetica; font-size: 14px;"><br></div><div style="font-family: helvetica; font-size: 14px;">because those tags are rediculous and can't give anything useful for later mapper. But "no data" may means the mapper failed to armchair mapping and need a on the ground servey, a "unclassified" surface may means the road situation is complex and can't match typical value.</div><div style="font-family: helvetica; font-size: 14px;"><br></div><div style="font-family: helvetica; font-size: 14px;">So I only support those 4 kind of truly useless values. <br></div><div style="font-family: helvetica; font-size: 14px;"><br></div>
<div class="protonmail_quote">
------- Original Message -------<br>
在 2022年7月28日 星期四 下午 12:51，Mateusz Konieczny via talk <talk@openstreetmap.org> 寫道：<br><br>
<blockquote class="protonmail_quote" type="cite">
<div dir="auto">I propose to remove following surface tags by doing an automated edit:<br></div><div dir="auto"><br></div><div dir="auto">surface=unclassified <a href="https://taginfo.openstreetmap.org/tags/surface=unclassified" rel="noreferrer nofollow noopener" target="_blank">https://taginfo.openstreetmap.org/tags/surface=unclassified</a><br></div><div dir="auto">surface=no data <a href="https://taginfo.openstreetmap.org/tags/surface=no%20data" rel="noreferrer nofollow noopener" target="_blank">https://taginfo.openstreetmap.org/tags/surface=no%20data</a><br></div><div dir="auto">surface=unknown <a href="https://taginfo.openstreetmap.org/tags/surface=unknown" rel="noreferrer nofollow noopener" target="_blank">https://taginfo.openstreetmap.org/tags/surface=unknown</a><br></div><div dir="auto">surface=undefined <a href="https://taginfo.openstreetmap.org/tags/surface=undefined" rel="noreferrer nofollow noopener" target="_blank">https://taginfo.openstreetmap.org/tags/surface=undefined</a><br></div><div dir="auto">surface=unspecified <a href="https://taginfo.openstreetmap.org/tags/surface=unspecified" rel="noreferrer nofollow noopener" target="_blank">https://taginfo.openstreetmap.org/tags/surface=unspecified</a><br></div><div dir="auto">surface=Unspecified <a href="https://taginfo.openstreetmap.org/tags/surface=Unspecified" rel="noreferrer nofollow noopener" target="_blank">https://taginfo.openstreetmap.org/tags/surface=Unspecified</a><br></div><div dir="auto"><br></div><div dir="auto">and other such null values, explictly expressing that surface is not<br></div><div dir="auto">tagged. Note that<br></div><div dir="auto"><br></div><div dir="auto">surface=yes<br></div><div dir="auto">surface=*<br></div><div dir="auto">surface=no<br></div><div dir="auto">surface=<different><br></div><div dir="auto">surface=surface<br></div><div dir="auto">surface=Maxar<br></div><div dir="auto">surface=a<br></div><div dir="auto"><br></div><div dir="auto">and similar values would NOT be removed despite being utterly useless<br></div><div dir="auto">as a surface=* value as repair may be possible or is it possible that<br></div><div dir="auto">it is some unusual tagging scheme which is actually useful<br></div><div dir="auto"><br></div><div dir="auto">Edit would be automatic, rerun from time to time, split into small<br></div><div dir="auto">changeset by geographic areas and run by<br></div><div dir="auto"><a href="https://www.openstreetmap.org/user/Mateusz" rel="noreferrer nofollow noopener" target="_blank">https://www.openstreetmap.org/user/Mateusz</a><br></div><div dir="auto">Konieczny%20-%20bot%20account/history bot account<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<br></div><div dir="auto"><br></div><div dir="auto">Why automatic edit? I a have 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 completely useless.<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">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">I have experience with bot edits and will repair any damage caused<br></div><div dir="auto">by bot edits that I operate.<br></div>
</blockquote><br>
</div>