Every Request (Almost) Always Raising Query Limit Error

mjohnson324 commented 6 years ago

Recently I've been seeing "Google API error: over query limit." a lot. With only a few exceptions I raise this error in my rails app regardless of the number of queries that have already been fired and I don't know how to fix this.

Context

The app simulates ZocDoc and can be used to search for doctors. Fake doctors are added via seeding for demoing the app. Part of this involves geocoding their addresses via the following lines in the Doctor model:

geocoded_by :location, latitude: :lat, longitude: :lng
after_validation :geocode
attr_accessor :location

Expected behavior

I run this line and expect geocoding to be successful:

doc_hibbert = Doctor.create!(location: '51 W 51st St, New York, NY', address: '51 W 51st St, New York, NY' first_name: 'Julius', last_name: 'Hibbert', education: 'Johns Hopkins University School of Medicine', degree: 'MD', address: '51 W 51st St, New York, NY')

Actual behavior

With few exceptions I instead raise 'Google API error: over query limit.'

I don't think it's a model error because I was able to successfully geocode 3 doctors (out of 57) on my last try.
There was no pattern to the geocoding. The only successful attempts were for doctors 18, 44 and 46.
This is not related to the rate of requests either. This error was raised immediately for the very first geocoding attempt in the seed file and hits me with individual queries.
Nor is this related to the number of requests in a day. This is a website I designed during a bootcamp and it gets very little traffic. The last time I attempted geocoding was almost a week ago and the behavior was identical (high chance of failure, small chance of success, random). I raised this error starting with my first geocoding attempt in several days.

Steps to reproduce

Geocode an object. I also get the same error if I attempt something like this in the rails console:

Doctor.first.update(location: Doctor.first.address)

That's just an example of how I tried manually geocoding one doctor afterwards, and how I was updating doctors when I encountered the same error because of rate limits. The update failed due to the error but the commit was successful.

Environment info

Geocoder version: 1.4.9
Rails version: 5.1.3
Ruby: 2.5.1
Database: PostgreSQL 10.5
Lookup: ipinfo_io (the default)
OS: Ubuntu 18.04

alexreisner commented 6 years ago

Closing, because this sounds like it has to do with your environment, not the gem, but if you post your Geocoder.configure block I might be able to suggest something. Are you using an API key and a paid Google API account? (This is required as of a few months ago.)

mjohnson324 commented 6 years ago

Thank you for the response. I don't have an API key, and until yesterday I hadn't set up a paid account on Google Maps. I don't intend for the site to be anything beyond a demo so I'll need to evaluate whether to stick with Google Maps.

Update:

got it working smoothly once keys and billing were set up, and the keys are encrypted.

Also just wanted to say this is an amazing project that's saved me a lot of time. Seriously, thank you.

viktorsmari commented 6 years ago

Came here because of the same problem. Maybe information about Google now requiring billing etc. should be added to the readme for a while?

alexreisner / geocoder