3 ms·
Google's is nice (unsurprisingly) but I'm not sure what the free tier limits are. If you want to try out a bunch, I recommend GeoPy: http://geopy.readthedocs.o
by Osmium 12y ago
Google's is nice (unsurprisingly) but I'm not sure what the free tier limits are. If you want to try out a bunch, I recommend GeoPy:
http://geopy.readthedocs.org/en/latest/ http://geopy.readthedocs.org/en/latest/
I used it for a personal project recently and it really easily allows you to switch between geocoders, which was useful for the edge case that Google didn't get.
- zacwest 12y agoGoogle says: > Using client-side Maps API services (JavaScript and Flash) in the browser is rate limited per map session. That means that requests are distributed across all your users and scale as the number of users grows. Therefore, client-side APIs should be always preferred and used whenever possible. (pretend the document wasn't written for like 2007) https://developers.google.com/maps/documentation/business/articles/usage_limits https://developers.google.com/maps/documentation/business/ar... Their API limits are pretty amazing for free, if you're able to distribute the load across all your clients, which on iOS is the name of the game.
- mbell 12y agoGoogle's ToS used to, and may still have, a clause that only allows the geocode API to be used in conjunction with maps, i.e. you can't use the geocode results for whatever you want, they have to be intended for display on a Google map. I used MapQuest's free tier awhile back which didn't have the map usage restriction but was limited to 5000 queries a day, enough for what I needed but probably no where near enough for many applications.