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

2017-11-13 Thread Richard Fairhurst
Sean Lindsey wrote: > I do want to produce something that is useful for > open source and OSM/its community Let me join in the thanks for making this available. Even though it might not be suitable for direct import into OSM (for legal and/or community reasons), I wonder whether it might be

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

2017-11-09 Thread Sean Lindsey
Hello, Sorry there are two threads going on here. The terms on the general site are not for the data on the OmniPlaces page and the bit about Google refers to the usage of Google services on the website itself, ie. we embed Google maps. We should probably clarify this. Our blog, blog.cybo.com/ ,

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

2017-11-09 Thread Dave Swarthout
FWIW, I checked the positional accuracy for a few of the Cybo POIs in my town of Homer, Alaska and some of them were close to reality and some not. Any use of this data in my area will require extensive ground checking. This concern may turn out to be academic because in looking through the data

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

2017-11-08 Thread 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

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

2017-11-08 Thread 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

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

2017-11-08 Thread 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

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

2017-11-08 Thread 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] Integrating our open source data into OSM

2017-11-08 Thread 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