-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add info about open data and restrictions to services vignette #138
Comments
I think this is a good idea, but I'm curious where we should draw the line and how we should categorize services. I did a brief search on a few services and found that MapBox requires attribution and Geocodio seems to have a permissive license, but may require attribution in some cases:
Should we draw the line at if the service (or underlying data sources) requires attribution? And if so would we classify both Geocodio and Mapbox as proprietary even though many of Geocodio's data sources are under open source licenses? |
commenting as someone who often has people ask about this kind of thing the main thing people seem to be interested in
there are other fine grain distinctions but I think this would cover 99% of questions |
We are currently relatively silent on whether the geocoding services utilize open or proprietary data. That's like - as someone put it - comparing R to Stata without mentioning that R is open source and Stata is not. I think it would be good to add an "open data" column to the table in the services vignette.
Some proprietary services (Google, HERE, ...) have some pretty strong restrictions on the use of the geocoding results, e.g. storing or displaying them on a map other than their own is prohibited. Maybe we should mention this in the highlights as well.
The text was updated successfully, but these errors were encountered: