I know this question has been asked, but most of the answers have been several years, not for the Ruby on Rails project. In my current project, I use the Geocode gem (through Ruby on Rails), and everyone can search for users by their location (which I also use for Carmen stones for the country, subregion).
Anyway, I recently got this question ( Google Geocoding API error: over query limit.). After reading this, I see that it is quite common. Most resolutions seem to be related to caching, but others say it doesn't work much / well.
I wanted to ask a question to many here and see what different people think is a good solution. Ideally, it would be great to keep the Geocoding gem under the project, but if it’s not worth it, let me know about the alternative. If you know a solution to this problem, let me know.
Thanks and just want to get feedback for this situation =)
PS: I do not use the Google Maps API. The project is configured so that the user enters their information (using the Carmen gem) and prints a quote. The location is geocoded, while others may enter a city, state / region to find users in that region.
EDIT
Additional question: when this limit is met, will it also cause the value of longitude and latitude to be zero when the user signs up? Since it is a limit, it will not bind geocoding to the specified location and therefore keeps the value at zero? I had this before, so I just want to make sure that's why = P
EDIT 2 - ANSWER?
Speaking a little (in the comments below), caching information seems to be the best option. With that said, after researching, I see that there are many legitimacy when it comes to caching with Google? Again, I do not use the Google Maps API, so the legal aspect may not be relevant?
(https://github.com/codeforamerica/ohana-api/wiki/Customizing-the-geocoding-configuration)?
, = P !