Another possible use is to compare OSM data with Cybo data on a coarse
(e.g. city/county) level to get an idea of how much is in OSM. How many
POIs are in [COUNTY] in OSM and compare that to Cybo. It could be
interesting to "rank" areas against each other, to get an idea of OSM's
completness (in U
On 11/13/2017 9:23 AM, Richard Fairhurst wrote:
If done right, I'd hope this could be the spur to greatly improving OSM POI
coverage in the US.
Another useful way to use the Cybo data if it's kept current is to be
able to subscribe to a feed of opened or closed businesses within an
area.
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 suita
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.
I'll update you all
Hi Sean,
The problem isn't disagreement, the problem is legality. We'd need to
look at the licences of the data you have and check that one can legally
import them into OSM. Perhaps it might be better to start with one or
two of the large datasets you have, and start the process there? Perhaps
th
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/ ,
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 t
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 oth
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 t
12 matches
Mail list logo