<div dir="ltr">Thanks for all your feedback, I'm not going to advocate whether or not OSM should use this data. I do want to produce something that is useful for open source and OSM/its community, and I plan on taking everything I've learned from this thread to produce something a bit better.<div><br></div><div>I'll update you all when I have something meaningful, and describe how I tried to address some of the concerns and issues that were raised here.</div><div><br></div><div>As always I'd love to hear any comments on how we can improve this dataset, make it easier to use or alleviate legal concerns. Questions are welcome as well.</div><div><br></div><div>Best,</div><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 10, 2017 at 4:43 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 Sean,<br>
<br>
The problem isn't disagreement, the problem is legality. We'd need to<br>
look at the licences of the data you have and check that one can legally<br>
import them into OSM. Perhaps it might be better to start with one or<br>
two of the large datasets you have, and start the process there? Perhaps<br>
the licence issues can be worked out. First we figure out if we *can*<br>
import the data, then we figure out if we *should*. 🙂<br>
<br>
I'm not 100% sure what you mean by the "secondary resource". OSM doesn't<br>
have "layers" or things like that. I don't think mappers could be able<br>
to copy from it if there is copyright licencing issues. We can't copy<br>
from other maps/databases.<span class=""><br>
<br>
On 09/11/17 23:11, Sean Lindsey wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
It seems that it's going to be hard to come up with a mass import solution that every one can agree on. I would suggest that you take name, address, phone number, website and category then try and re-geocode the data, but it seems there is opposition to this method as well.<br>
<br>
Another approach - as a way of keeping OSM and this data separate - is having this POI data be a "secondary resource" that OSM users could "opt in" to adding into their mapping set, but not be inherently owned or in OSM's primary data set. For example, by loading up an OSM database you could be linked to us or someone who creates a derivative of our data suitable for importing into OSM maps. Thereby OSM does not feel responsible for this resource but it still becomes available for people to import and use via us or someone else. In this case we would want to work with someone in order to create an OSM import-friendly version of this data. We have a ton of indicators that tell us the quality and freshness of this data and potentially we can rework in into something more usable.<br>
<br>
Thoughts?<br>
<br></span><span class="">
On Thu, Nov 9, 2017 at 1:09 AM, Rory McCann <<a href="mailto:rory@technomancy.org" target="_blank">rory@technomancy.org</a> <mailto:<a href="mailto:rory@technomancy.org" target="_blank">rory@technomancy.org</a>>> wrote:<br>
<br>
Hi Sean,<br>
<br>
On 09/11/17 07:14, Sean Lindsey wrote:<br>
> Thanks for all the feedback, we have put together some blogs to help<br>
> people figure out how to play with the data, to give people an idea of<br>
> what it is and how it was put together.<br>
><br>
> <a href="https://blog.cybo.com/" rel="noreferrer" target="_blank">https://blog.cybo.com/</a><br>
<br>
So that website says:<br>
<br>
OmniPlaces is formed from billions of records (literally), from<br>
tens of thousands of sources (literally)<br>
<br>
<br>
Trying to figure out the licence for tens of thousands of datasets is<br>
practically impossible.... Licence issues are often a problem with<br>
imports, and I think this could be a show-stopper for this.<br>
<br>
On 09/11/17 05:54, Jo wrote:<br>
<br>
If the addresses are in the data as well, we don't really need<br>
to use<br>
the lat/lon coordinates.<br>
<br>
<br>
Not necessarily, depends where the addresses came from. If you had<br>
lots of lat/longs, and geocoded the, and threw away the lat/longs<br>
then you don't have a clean dataset.<br>
<br>
-- Rory<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><span class=""><br>
<<a href="https://lists.openstreetmap.org/listinfo/imports" rel="noreferrer" target="_blank">https://lists.openstreetmap.o<wbr>rg/listinfo/imports</a>><br>
<br>
<br>
<br>
<br>
-- <br>
Sean Lindsey<br>
Cybo Company<br></span><span class="">
LinkedIn <<a href="https://www.linkedin.com/in/sean-lindsey/" rel="noreferrer" target="_blank">https://www.linkedin.com/in/s<wbr>ean-lindsey/</a>><br>
<a href="tel:541-912-2505" value="+15419122505" target="_blank">541-912-2505</a> <tel:(541)%20912-<wbr>2505><br>
<br>
<br></span><span class="">
______________________________<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>
<br>
<br><div class="HOEnZb"><div class="h5">
<br>
______________________________<wbr>_________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org" target="_blank">Talk-us@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-us" rel="noreferrer" target="_blank">https://lists.openstreetmap.or<wbr>g/listinfo/talk-us</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sean Lindsey<div>Cybo Company</div><div><a href="https://www.linkedin.com/in/sean-lindsey/" target="_blank">LinkedIn</a><br><div>541-912-2505</div></div></div></div></div></div>
</div>