[Talk-us] Integrating our open source data into OSM

[Michael Patrick]

The Cybo "Terms of Use" page at https://yellowpages.cybo.com/terms/
specifically
mentions Google ...

"This information is not to be reused for public display." and "We use
various Google services or API's (e.g. Google Maps API). By using our
services you are bound by Google's Terms of Service
."

Google itself is an aggregator, and licenses it's data from many, many
providers. Which is why their ToCs are very restrictive. But even some of
the 'Open Source' friends on https://yellowpages.cybo.com/friends/
providing spatial data are problematical - I seem to recall a discussion of
compatibility between OdbL and the Creative Commons flavors and Wikipedia.

Probably easier to ask what portion of the Cybo data is contributed by
individuals, and under what terms.

Michael Patrick
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Integrating our open source data into OSM

[Frederik Ramm]

Hi,

On 09.11.2017 02:53, Brian May wrote:
> Its critical to know where the lat/longs came from. For example, if they
> came from Google Maps - then its a no go, because Google's licensing is
> incompatible with OSM. Their geocodes are not public domain, etc. Same
> thing applies to many / most other commercial geocoding services. If you
> don't know how the lat/longs were derived, then that is probably a show
> stopper as well.

I've enterered a random sample of addresses from this data set into
Google for geocoding and ended up with the exact same lat/lon in about
half of cases - but I only tested a handful.

Of course it is totally possible that a public domain geocoding source
is used by both Cybo and Google which would lead to both having the same
data without Cybo having copied from Google.

As a further explanation to Sean, in case you're not familiar with the
legal situation; while deriving "facts" from Google's database and
re-using them in your own data set will often not violate copyright
(because "facts are free"), it can violate database protection which is
a different legal concept that protects a database from repeated
extraction even if the individual extracted bits are not copyrighted.
This concept doesn't exist in the US to my knowledge, but someone using
such a database in, for example, the EU, could be sued by the database
owner. That's why OSM must avoid adding location data that has been
derived from non-free sources.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] [Imports] Integrating our open source data into OSM

[Sean Lindsey]

Thanks for all the feedback, we have put together some blogs to help people
figure out how to play with the data, to give people an idea of what it is
and how it was put together.

https://blog.cybo.com/

I assumed the set we released was not yet ready for OSM but with some
guidance I may be able to go back through and derive something that's more
useful for you and likely others interested in working with the data. Most
of our records/POIs are from several different sources, which means the way
a record is compiled could influence how useful it is.

On Wed, Nov 8, 2017 at 8:54 PM, Jo  wrote:

>  If the addresses are in the data as well, we don't really need to use the
> lat/lon coordinates. The best way to use this kind of data, is to use it as
> one of several sources. So a direct import is out of the question, but
> using it as a shortcut and combining with what we already have plus aerial
> imagery plus possibly an extra lookup in other sources could be considered.
>
> Of course, we don't want to be a front end for SEO techniques, so maybe
> the data needs to be pruned from overly commercial information and
> descriptions, before it is useful to us.
>
> I'm downloading it too, but it takes a while. I can probably figure out a
> way to convert it into something usable (at a technical level).
>
> Polyglot
>
> 2017-11-09 2:53 GMT+01:00 Brian May :
>
>> Its critical to know where the lat/longs came from. For example, if they
>> came from Google Maps - then its a no go, because Google's licensing is
>> incompatible with OSM. Their geocodes are not public domain, etc. Same
>> thing applies to many / most other commercial geocoding services. If you
>> don't know how the lat/longs were derived, then that is probably a show
>> stopper as well.
>>
>> Brian
>>
>>
>> On 11/8/2017 1:53 PM, Sean Lindsey wrote:
>>
>> We have open sourced our US POI data, it may not be ready for a direct
>> import into OSM, but we'd be willing to try to get it there.
>>
>> Its a national directory of 59 million US businesses, that has been
>> updated as of this summer. And should be getting another refresh shortly.
>>
>> What process is there to discuss and work to integrate this data?
>>
>> The data is available under a creative commons attribution license at
>> https://omniplaces.cybo.com/
>>
>> I would be willing to waive and/or clarify certain aspects of the licence
>> if needed however.
>> * I asked this same question in help.openstreetmap.org
>> ,
>> and was referred to these mailing lists
>>
>> Regards,
>> --
>> Sean Lindsey
>> Cybo Company
>> LinkedIn 
>> 541-912-2505 <(541)%20912-2505>
>>
>>
>> ___
>> Talk-us mailing 
>> listTalk-us@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-us
>>
>>
>>
>> ___
>> Imports mailing list
>> impo...@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/imports
>>
>>
>


-- 
Sean Lindsey
Cybo Company
LinkedIn 
541-912-2505
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] [Imports] Integrating our open source data into OSM

[Mike Thompson]

I downloaded data for one of the states (Colorado) to attempt checkout its
quality.  It appears to be in JSON (not GeoJSON).  Is there an easy way to
get the data into something like QGIS so it can be visualized on a map?



On Wed, Nov 8, 2017 at 6:53 PM, Brian May  wrote:

> Its critical to know where the lat/longs came from. For example, if they
> came from Google Maps - then its a no go, because Google's licensing is
> incompatible with OSM. Their geocodes are not public domain, etc. Same
> thing applies to many / most other commercial geocoding services. If you
> don't know how the lat/longs were derived, then that is probably a show
> stopper as well.
>
> Brian
>
>
> On 11/8/2017 1:53 PM, Sean Lindsey wrote:
>
> We have open sourced our US POI data, it may not be ready for a direct
> import into OSM, but we'd be willing to try to get it there.
>
> Its a national directory of 59 million US businesses, that has been
> updated as of this summer. And should be getting another refresh shortly.
>
> What process is there to discuss and work to integrate this data?
>
> The data is available under a creative commons attribution license at
> https://omniplaces.cybo.com/
>
> I would be willing to waive and/or clarify certain aspects of the licence
> if needed however.
> * I asked this same question in help.openstreetmap.org
> ,
> and was referred to these mailing lists
>
> Regards,
> --
> Sean Lindsey
> Cybo Company
> LinkedIn 
> 541-912-2505 <(541)%20912-2505>
>
>
> ___
> Talk-us mailing 
> listTalk-us@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-us
>
>
>
> ___
> Imports mailing list
> impo...@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/imports
>
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Integrating our open source data into OSM

[Brian May]

Its critical to know where the lat/longs came from. For example, if they 
came from Google Maps - then its a no go, because Google's licensing is 
incompatible with OSM. Their geocodes are not public domain, etc. Same 
thing applies to many / most other commercial geocoding services. If you 
don't know how the lat/longs were derived, then that is probably a show 
stopper as well.


Brian

On 11/8/2017 1:53 PM, Sean Lindsey wrote:


We have open sourced our US POI data, it may not be ready for a direct 
import into OSM, but we'd be willing to try to get it there.


Its a national directory of 59 million US businesses, that has been 
updated as of this summer. And should be getting another refresh shortly.


What process is there to discuss and work to integrate this data?

The data is available under a creative commons attribution license at 
https://omniplaces.cybo.com/


I would be willing to waive and/or clarify certain aspects of the 
licence if needed however.


* I asked this same question in help.openstreetmap.org 
, 
and was referred to these mailing lists


Regards,
--
Sean Lindsey
Cybo Company
LinkedIn 
541-912-2505


___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Integrating our open source data into OSM

[Max Erickson]

Hi-

It would be useful if you would describe how the data has been
collected and what other databases it may include information from.

OSM takes a fairly cautious approach to data rights, so it is a
necessary step to any import to clarify where the data has come from.


Max

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] Integrating our open source data into OSM

[Sean Lindsey]

We have open sourced our US POI data, it may not be ready for a direct
import into OSM, but we'd be willing to try to get it there.

Its a national directory of 59 million US businesses, that has been updated
as of this summer. And should be getting another refresh shortly.

What process is there to discuss and work to integrate this data?

The data is available under a creative commons attribution license at
https://omniplaces.cybo.com/

I would be willing to waive and/or clarify certain aspects of the licence
if needed however.
* I asked this same question in help.openstreetmap.org
,
and was referred to these mailing lists

Regards,
-- 
Sean Lindsey
Cybo Company
LinkedIn 
541-912-2505
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us