<html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office"><head><!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]--></head><body>
<div><br></div><blockquote class="iosymail"><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">I heard Mapbox is working on this and divide data spatially not as<br clear="none">a sequence of changeset. My impression would be that this way<br clear="none">you could produce a "nice looking map" but most likely it will<br clear="none">break for routing purposes in most horrible ways where ways suddenly<br clear="none">are not connected anymore as some changeset inbetween has been<br clear="none">withdrawn/rejected.</span></blockquote><br>Mapbox Streets Review groups data for review by feature type and spatial proximity, for a single day. There’s some complexities but it does maintain the routing graph.<div><br></div><div>I understand Facebook does something similar, but yes their use case does not involve routing but only visible map. Nothing wrong with that, fit the process to purpose.</div><div><br></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br clear="none">> So i'd guess the way you and IIRC Mapbox try to solve the vandalism/bad<br clear="none">edit issue is a labour and machine learning intensive task which you cant win. Once you eliminate changesets you fall behind and you pile up inconsistencie</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">That’s not the case. It is labor intensive, but with well designed processes it’s manageable, and you can stay on pace and consistent.</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">I’d say one issue is not missing problems but being overly conservative, and flagging false positives. So flags in OSMCha from Mapbox shouldn’t be interpreted as a definite problem, but a suspicion. That’s by design, but it would be good to get even more accurate.</span></div><div><br></div><div>> <span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">So i'd love to hear more thoughts about long term ideas how to solve</span></div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">this in a collaborative manner. OSMCha is probably not the final solution but currently it brings together analysis, be it human<br clear="none">or machine learning in a transparent way, not that it currently has an impact on the main OSM database.</span><div><br></div><div>100%. OSM and OSM validation needs to be collaborative to work. One idea, OSMCha could be more integrated into OSM.org, could provide more insightful insight in the history view. </div><div><br>Mikel<br><p class="yahoo-quoted-begin" style="font-size: 15px; color: #715FFA; padding-top: 15px; margin-top: 0">On Tuesday, March 10, 2020, 5:52 PM, Florian Lohoff <f@zz.de> wrote:</p><blockquote class="iosymail">On Mon, Mar 09, 2020 at 05:08:10PM -0700, Michal Migurski wrote:<div class="yqt3394872979" id="yqtfd63994"><br clear="none">> Hi everyone,<br clear="none">> <br clear="none">> I’m writing to let you know about a new OpenStreetMap project Facebook<br clear="none">> just released. It’s called Daylight Map Distribution. Daylight is a<br clear="none">> complete, downloadable preview of OpenStreetMap data we plan to start<br clear="none">> using in a number of our public maps:</div><br clear="none"><br clear="none">I think its a humble approach to try to identify (un)intentional bad<br clear="none">edits. A lot of people try to deal with this.<br clear="none"><br clear="none">I am doing a lot of QA myself and i look at OSMCha changesets in <br clear="none">my greater surrounding on a daily basis.<br clear="none"><br clear="none">I fail to see a sane technical way of producing consistent map data<br clear="none">out of some intermingled data of which some changesets have been <br clear="none">flagged/removed.<br clear="none"><br clear="none">I heard Mapbox is working on this and divide data spatially not as<br clear="none">a sequence of changeset. My impression would be that this way<br clear="none">you could produce a "nice looking map" but most likely it will<br clear="none">break for routing purposes in most horrible ways where ways suddenly<br clear="none">are not connected anymore as some changeset inbetween has been<br clear="none">withdrawn/rejected.<br clear="none"><br clear="none">So i'd guess the way you and IIRC Mapbox try to solve the vandalism/bad<br clear="none">edit issue is a labour and machine learning intensive task which you<br clear="none">cant win. Once you eliminate changesets you fall behind and you<br clear="none">pile up inconsistencies. This is, i guess, the reason for<br clear="none">your "one shot" dump of your current internal state.<br clear="none"><br clear="none">So from my perspective the vandalism/bad edit issue will only be<br clear="none">fixable if we have some review process (Not that i would suggest one)<br clear="none">for strictly sequential changesets where review must be in order<br clear="none">and a once rejected/withdrawn changeset can only be requeued not<br clear="none">put in that sequential place again. And even then you'll see <br clear="none">vandalism sneak by with innocent looking edits or intentional<br clear="none">3rd party validation.<br clear="none"><br clear="none">So i'd love to hear more thoughts about long term ideas how to solve<br clear="none">this in a collaborative manner. OSMCha is probably not the final<br clear="none">solution but currently it brings together analysis, be it human<br clear="none">or machine learning in a transparent way, not that it currently<br clear="none">has an impact on the main OSM database.<br clear="none"><br clear="none">Flo<br clear="none">-- <br clear="none">Florian Lohoff <a shape="rect" ymailto="mailto:f@zz.de" href="mailto:f@zz.de">f@zz.de</a><br clear="none"> UTF-8 Test: The 🐈 ran after a 🐁, but the 🐁 ran away<div class="yqt3394872979" id="yqtfd84541">_______________________________________________<br clear="none">talk mailing list<br clear="none"><a shape="rect" ymailto="mailto:talk@openstreetmap.org" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br clear="none"><a shape="rect" href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br clear="none"></div><blockquote></blockquote></blockquote></div>
</body></html>