<div dir="ltr">Hi! <div><span style="color:rgb(32,33,34);font-family:sans-serif">We share json archives with linters that we plan to fix, which can be looked through </span><a rel="nofollow" class="external gmail-free" href="http://geojson.io/" style="text-decoration-line:none;color:rgb(51,102,187);padding-right:13px;font-family:sans-serif">http://geojson.io</a></div><div><span style="color:rgb(32,33,34);font-family:sans-serif">Also you can use </span><a rel="nofollow" class="external gmail-free" href="https://maproulette.org/" style="text-decoration-line:none;color:rgb(51,102,187);padding-right:13px;font-family:sans-serif">https://maproulette.org/</a><span style="color:rgb(32,33,34);font-family:sans-serif"> where users can make a project by adding json files, so you can look through json we sent. </span></div><div><span style="color:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji"">We will prepare more specific documentation about how we work with the Linters and about our approach in resolving issues mentioned in feedback. </span><span style="color:rgb(32,33,34);font-family:sans-serif">After discussion of our work with restrictions with the Italy OSM community, we changed the approach. Now we don’t delete restrictions if there are no clear proofs of it. We leave notes about broken restrictions if we don’t have ground truth sources for mapping them.</span><span style="color:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji""><br></span></div><div><span style="color:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji"">Always open for your comments and feedback.</span><br></div><div><span style="color:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji""><br></span></div><div><span style="color:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji"">Best regards</span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 20, 2021 at 4:26 PM Andy Townsend <<a href="mailto:ajt1047@gmail.com">ajt1047@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>On 20/09/2021 13:50, Sonya Khilchyk via
Talk-GB wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">We already notified you at the end of August that
we plan to start a mapping project. </div>
</blockquote>
<p>... and since then I think that it's fair to say that "questions
have been raised about the approach and quality of the edits
performed".</p>
<p><br>
</p>
<blockquote type="cite">
<div dir="ltr">We updated our <a href="https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/Resolve_linting_issues_in_the_UK" target="_blank">wiki page</a> and <a href="https://github.com/mapbox/mapping/issues/387" target="_blank">ticket</a> with json files, so you can
get more information about items we are working with.
<div><br>
</div>
</div>
</blockquote>
<p>No we can't. Searching either
<a href="https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/Resolve_linting_issues_in_the_UK" target="_blank">https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/Resolve_linting_issues_in_the_UK</a>
or <a href="https://github.com/mapbox/mapping/issues/387" target="_blank">https://github.com/mapbox/mapping/issues/387</a> for json finds
nothing. A table has been added but it adds literally no value -
it does not explain how these alleged problems were detected, what
each one represents, or how Mapbox propose to resolve the issues.
The wiki page says "We will use existing OpenStreetMap editing
tools" but that's about as useful as this:
<a href="https://www.youtube.com/watch?v=-1sM29zGxeo" target="_blank">https://www.youtube.com/watch?v=-1sM29zGxeo</a> .<br>
</p>
<p>Often what seems to happen is that the Mapbox mapper is simply
removing something that is getting flagged up as "invalid" without
investigating whether anything is mismapped at all. Mapbox
mapper's "solutions" have included "adding a cycleway without
survey to prevent vehicle routing" (the actual problem was that a
gate, visible on aerial imagery, was missing from OSM and their
router was buggy) and "just deleting a road" (the actual problem
there seems to be that the road exists, but is a path not open to
vehicle traffic). My experience of Mapbox's mapping local to me
is that it is actually _reducing_ the quality of OSM data by
removing features that people have tried to add but haven't quite
got right, or that have become broken by some other mapper than
didn't understand the feature.<br>
</p>
<p>For everyone else's benefit, the Mapbox employees taking part in
the exercise seem to be from
<a href="https://wiki.openstreetmap.org/wiki/Mapbox#Current_Data_Team_members" target="_blank">https://wiki.openstreetmap.org/wiki/Mapbox#Current_Data_Team_members</a><br>
</p>
<p>Based on the quality of these individuals' editing so far, I
would regard any edits by these users with great suspicion.</p>
<p>Best Regards,</p>
<p>Andy</p>
<p><br>
</p>
</div>
_______________________________________________<br>
Talk-GB mailing list<br>
<a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-gb" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a><br>
</blockquote></div>