geocoder: Geocoder raises "Google API error: over query limit." error if non-valid address is entered

With the following settings: Geocoder.configure(always_raise: :all)

Expected behavior

When attempting to geocode invalid input via the Google API, it should raise a Geocoder::InvalidRequest (or similar) error – or, return nil, as is the default behavior when the above config is unset.

Actual behavior

When attempting to geocode invalid input via the Google API, it raises a Google API error: over query limit. error.

Steps to reproduce

Geocoder.coordinates("alksdjf") produces a Google API error: over query limit. error. Geocoder.coordinates("25 Main St, Cooperstown, NY") behaves as expected.

Environment info

Geocoder version: 1.4.7
Rails version: 5.1.4
Ruby version: 2.5

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 18 (5 by maintainers)

Most upvoted comments

Hi! I’m in the same boat. Our Google account is unlimited, so I don’t think we’re going over. I checked the Google console and didn’t see so much activity that we would be going over the per-second query limit.

LizPrescott on Aug 8, 2018

I have specified the API key in config but still getting over query limit error. Anyone still facing the issue?

adilhussain003 on May 28, 2018

@alexreisner I’ve been getting over query limit errors more frequently since posting the issue, regardless of the always_raise settings. I’m wondering if they are related to the upcoming changes to the Google Maps API

eric-norcross on May 7, 2018

I have the same issue. Any address returns nil.

irb(main):001:0> Geocoder.coordinates('jason statham')
Google API error: over query limit.
=> nil
irb(main):002:0> Geocoder.coordinates('神奈川県川崎市幸区大宮町１３１０ ミューザ川崎１４３')
Google API error: over query limit.
=> nil

Mizumaki on Nov 8, 2018