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
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
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
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
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
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
7 matches
Mail list logo