<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Re-reading this I phrased this with more hyperbole than I intended, sorry.<div class=""><br class=""></div><div class="">I do think we should learn from past mistakes and approach any automated edit, be it an import or a (subsequent) fix, with the proper diligence. Which is what we’re doing here, and I commend you for taking an open-minded approach in your initial email.</div><div class=""><br class=""></div><div class="">Martijn</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 21, 2019, at 8:29 AM, Martijn van Exel <<a href="mailto:m@rtijn.org" class="">m@rtijn.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">Stepping back a bit, the urge to fix previous automated edits with new automated fixes is understandable, but it may lead to a more casual approach to imports and automated edits, because we basically say with each fix that ill-informed automated map edits can always be fixed with more automated edits later. We’ve already gone down that path in the U.S. quite far, so we should proceed with extra care - unless we as a community decide that that is the nature of OSM in this country. It isn’t to me.</div><br class="Apple-interchange-newline"></div></blockquote></div><br class=""></div></body></html>