Hi,
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.
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.
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.
:)
Rory
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. :)
On 16.03.2017 22:46, Kate Chapman wrote:
Thanks for sharing this information. In reading through the comments so
far I think we need to keep a few things in mind.
1. We can't demand more of Facebook than others doing imports. When a
government releases data under an open license we don't demand to see
the imagery they used to make it. I purchase the same imagery Facebook
does for my job and our license also ensures that we have the rights to
release the derived vectors under the license we choose. I think this is
sufficient.
2. There is not a requirement to share all the source code used to
create data either. Nor for the imports. Previously people have used all
kinds of scripts to perform imports. Some people use ArcGIS to perform
imports. We haven't required they open-source that software. We can't do
it specifically for this case either. Many of us in OSM are fans of
open-source, but the ethos of OpenStreetMap is more than anything open
data.
I applaud new approaches to OSM and look forward to this import being
worked through with the community.
-Kate
On Tue, Mar 14, 2017 at 7:39 PM, osm <[email protected]
<mailto:[email protected]>> wrote:
Dear OSM Community,
This email is to share the Facebook process and sample data for
review by the OSM community. We welcome feedback.
Our goal is to collaborate with the OpenStreetMap community to
create quality road data, validated by trained mappers and local OSM
communities. Our import documentation on the wiki
<https://wiki.openstreetmap.org/wiki/AI-Assisted_Road_Tracing>
explains the process in depth, but we're happy to answer any other
questions you might have.____
To get community feedback we are sharing our sample data (attached)
and outlining our process. We understand our process is not a
traditional OSM import because we are creating the data ourselves
and conflating it with existing OSM. As you will see on the wiki,
the**process is similar to remote tracing using satellite imagery,
where human mappers are assisted with road suggestions generated by
machine learning algorithms. Using the tasking manager, multiple
people go through each node and way making sure to tag each road
appropriately, connect them to current OSM data, fix alignment, when
necessary, add sensible changeset comments/notes and resolve
conflicts before finally saving where it is merged with the current
OSM data.
We are working with just one country at a time and our edits will
happen slowly by grouping areas into small regions so we complete
one before moving to the next. We plan to spend the next few months
in Thailand. ____
We hope to continue to engage the local community, as we know this
is an important part of being an OSM contributor. We are open to
feedback and willing to improve processes and learn from feedback.
We are happy to share our Tile Service as mentioned here
<https://wiki.openstreetmap.org/wiki/AI-Assisted_Road_Tracing>. For
now we can also share .osm files for specific areas of interest,
while we work on creating a better way to share this through a
Tasking Manager or something similar that is public facing. So far
we have been chatting with a few members in the community, but as we
learnt from the forum discussion we should have also posted publicly
and will do that going forward.
__
____
_______________________________________________
Imports mailing list
[email protected]
<mailto:[email protected]>
https://lists.openstreetmap.org/listinfo/imports
<https://lists.openstreetmap.org/listinfo/imports>
_______________________________________________
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
_______________________________________________
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
