<div dir="ltr">Hi Rory,<div><br></div><div><div class="gmail_extra">I'm not in disagreement that providing the code could improve it, though I don't think it is required to provide the code that made the data. If we are handling this as any other import than providing the entire data source should be sufficient. We don't require governments that provide open data to provide the tools that they used to make the data. In the three processing steps you mentioned I think the only one that would be required to make the source code available might be the custom iD if that is the point where the data is submitted to OSM. </div><div class="gmail_extra"><br></div><div class="gmail_extra">I'm not disagreeing at all that having additional imagery would be great, though I think as Kevin mentioned that is really a separate conversation (and seemingly in the works). </div><div class="gmail_extra"><br></div><div class="gmail_extra">-Kate</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 17, 2017 at 6:28 AM, Rory McCann <span dir="ltr"><<a href="mailto:rory@technomancy.org" target="_blank">rory@technomancy.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Yes, we must treat Facebook the same as all others. We ask importers to show all the data. FB have shown part of the data. If they want to import lots of data for Thailand, then they could show all of that data for review.<br>
<br>
The Automated Edits & Imports guidelines do call for documentation of the algorithms/source code. I think there are ~3 processing steps. The computer vision code, the custom iD editor (w/ validator), and (maybe) some server side processing/"internal processes". Many places bugs could creep in. With many eyes, we can find bugs and possibly help make it better.<br>
<br>
>From my reading, you should show the data or the code. Yes, we don't ask for ArcGIS to be open source, but in that case one provides the data.<br>
<br>
:)<br>
<br>
Rory<br>
<br>
P.S.: I suggested sharing the imagery because OSM has 2 main global imagery source (Mapbox & Bing). It would be great to have a third. :)<span class=""><br>
<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
____<br>
<br>
<br>
______________________________<wbr>_________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org" target="_blank">Imports@openstreetmap.org</a><br></span>
<mailto:<a href="mailto:Imports@openstreetmap.org" target="_blank">Imports@openstreetmap.<wbr>org</a>><br>
<a href="https://lists.openstreetmap.org/listinfo/imports" rel="noreferrer" target="_blank">https://lists.openstreetmap.or<wbr>g/listinfo/imports</a><br>
<<a href="https://lists.openstreetmap.org/listinfo/imports" rel="noreferrer" target="_blank">https://lists.openstreetmap.o<wbr>rg/listinfo/imports</a>><span class=""><br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org" target="_blank">Imports@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/imports" rel="noreferrer" target="_blank">https://lists.openstreetmap.or<wbr>g/listinfo/imports</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org" target="_blank">Imports@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/imports" rel="noreferrer" target="_blank">https://lists.openstreetmap.or<wbr>g/listinfo/imports</a><br>
</div></div></blockquote></div><br></div></div></div>