-
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 common web services. #1
Comments
Google maps has some pretty strict limits on what you can do with results On Tue, Jan 20, 2015, 4:10 PM Blake Grotewold [email protected]
|
And while I think Google's legal usage policies about geocoding are dumb, I still think it's still valuable to implement it as an option for this library. If you're looking for other geocoding services, you can check out what geopy has listed: https://github.com/geopy/geopy |
Hi, Google is great, but the lack of openness of the data, and thus limitations on what is possible with it, are a major turn off. One alternative is the OpenCage Geocoder. We (I'm one of the people behind it) provide a single API to various open geocoders. OpenStreetMap of course, but also several smaller, country-specific services. |
Hi Ed, |
See #4 for a PR relating to this. |
22: Implement Openstreetmap provider r=urschrei a=pjsier Thanks for putting this library together! I took a stab at implementing an OpenStreetMap provider here since it was listed in #1 I tried to follow the patterns from the OpenCage provider and used the builder pattern for specifying additional parameters, but I'm new to Rust so let me know if anything seems off. I'd like to use the `InputBounds` struct for the `viewport` parameter here, but wanted to check and see what the best way of restructuring that would be Co-authored-by: pjsier <[email protected]>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
I typically use the google v3 api and osm. what other ones should be addressed first?
Web Services to support:
EDIT: ADD OPENCAGE AND IMMEDIATELY CLOSE IT THANKS TO @urschrei ;)
The text was updated successfully, but these errors were encountered: