Add common web services.

[groteworld]

I typically use the google v3 api and osm. what other ones should be addressed first?

Web Services to support:

• Google v3 API
• OpenStreetMap
• OpenCage

EDIT: ADD OPENCAGE AND IMMEDIATELY CLOSE IT THANKS TO @urschrei ;)

[calvinmetcalf]

Google maps has some pretty strict limits on what you can do with results
from their geocoder, mainly you can only display them on Google maps (not
esri, leaflet or anything else) and you can only store data for performance
purposes for at most 90 days

On Tue, Jan 20, 2015, 4:10 PM Blake Grotewold notifications@github.com
wrote:

I typically use the google v3 api and osm. what other ones should be
addressed first?

Web Services to support:

• Google v3 API
• OpenStreetMap

—
Reply to this email directly or view it on GitHub
#1.

[frewsxcv]

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

[freyfogle]

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.
I'd love to see us integrated into this library. Unfortunately though I don't know rust. Happy to pay someone for a few hours of their time to do the work of creating a pull request. Is that something anyone on this thread would be open to?

[urschrei]

Hi Ed,
Yep, we can have a look at incorporating it (it looks like nobody ever kicked off the geo-coding functionality anyway, so you'd be one of the first available services).

[urschrei]

See #4 for a PR relating to this.