Blog post: Coming Soon: IP-Based Geocode Limiting System - Google Maps API

Message from discussion Blog post: Coming Soon: IP-Based Geocode Limiting System

More options Oct 2 2007, 4:42 am

From: Bo <zorg...@gmail.com>

Date: Tue, 02 Oct 2007 08:42:15 -0000

Local: Tues, Oct 2 2007 4:42 am

Subject: Re: Blog post: Coming Soon: IP-Based Geocode Limiting System

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

The new quota system is live. If you experience any troubles, please
let us know by posting to this forum. We are trying to simplify lives
of regular map users while limiting abusive behavior, so the system is
still being actively tuned. Your feedback is very valuable. Pamela is
working on a tutorial devoted to geocoding. But until it comes out,
the general recommendation is: if you are using GClientGeocoder add a
check for Status.code == 620 to your code. If you get it, please
inform the user that geocoder was temporarily unavailable, however,
they should try again shortly. If you are using server side geocoding,
you can re-geocode an address. However, a short, semi-random delay
would be appreciated.

Regards ... Bo

On Sep 28, 3:15 am, brooklineTom <Brookline...@gmail.com> wrote:

> > First John's guess to the rate is pretty good. The actual rate depends
> > on the load the servers are experiencing and it may vary a bit. But
> > don't worry about stepping on our toes. Just watch for 620 as a status
> > code. If you get it, insert a short pause and continue as before. Of
> > course, if you used up daily quota, you will need until the end of the
> > 24h period (counted from the first accepted query).

> Thanks, Bo, this is very helpful. I'm hoping that the time it takes
> python to catch and handle a 620 and then retry the item will count as
> the "short pause" ... I can always insert an explicit sleep on the
> second failure.

> > Regarding about announcement about the new system being live, yes, I
> > will make an appropriate post. Currently, the best estimate is Oct 1.

> Sounds great, this will be a big help to us and perhaps to you as
> well.

> Thanks,
> Tom

Reply to author Forward