-
Notifications
You must be signed in to change notification settings - Fork 644
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
How to choose which geocoding provider to use? #90
Comments
Your questions pretty much hit on the reasons you’d go with one or the other. Both Google and Microsoft are good starting points with good databases and generous quotas. It’s more a consideration if you’re outside of mainstream Asia/US/Europe. Some places can be a real hassle due to either poor data coverage or an addressing system that does not lend itself well to the assumptions built into linear referenced geocode systems. Personally I find Bangkok street addresses to be hopeless and hope I never have to geocode anything there.
|
I don't think accurate documentation could be provided on this. It's more tractable, to me, to do one thing well here and defer to the documentation on each service's site. |
I've at least determined that these ones are free and don't require any credentials (at least when you are not reverse-geocoding) GoogleV3, Nominatim, ArcGIS, OpenMapQuest, Yandex |
You have to be careful though. Google's API requires you to use the data only on their maps (e.g NOT open street maps, mapbox, etc). Which means you can only display it on a publicly available google map which doesn't require a login, or pay for Google Maps API for Business at $10,000 a year. Other's have similar (but not equal) restrictions, like Bing Maps, Yahoo, and Mapquest (non-community version). |
Yandex geocoding data also must not be stored in your database (only cache) and must use only on public yandex maps in your service. Also Yandex geocoder API have limit for 25000 requests per day. |
If anyone'd like to add to the docs explaining what you need to be aware of when choosing a service, that'd be welcome. |
Yandex.Maps API Terms of Use - http://legal.yandex.com/maps_api/ |
I'm closing this in favor of #268 |
There are a lot of provider options to chose from, but there is nothing in the documentation to suggest a reason for using any one of them in particular. Are some of the providers more accurate? Are some faster? Are some of them more rate limited than others?
The text was updated successfully, but these errors were encountered: