Query Limit Problem/Question

[See The Light]

Over the past couple of weeks I have noticed an increase in the number
of "OVER_QUERY_LIMIT" responses we have been receiving. Currently
whenever we make a call to be geocoded we keep track of that call and
decrease a counter on our end. I have historical data that shows we
usually end the day with at least 300 queries left. This AM, I cannot
even make a query off the server because it returns the limit message,
and I show in our table that we have some 2300 call left.

Is there a call that can be made to get your current query limit? If
not, does the 2500 calls allowed happen in a sliding window? Are there
hourly limits to prevent flooding?

This would be greatly helpful provided our search mechanism first
attempts to get relevant geocoded data from the server before actually
calling over to Google for an unknown geocode.

Thanks.

[Ikai Lan (Google)]

Is this the maps API you're referring to?

--

Ikai Lan 
Developer Programs Engineer, Google App Engine

plus.ikailan.com | twitter.com/ikai

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[See The Light]

The Geocoding API v3. I am using the Xml response.

I just hit the limit tonight testing some changes that needed to be
implemented. I had 698 addresses to geocode. I pulled them from the
database and submit each address using:

http://maps.googleapis.com/maps/api/geocode/xml?address={0}&sensor=false

I then write back some of the data in the response. I checked and 26
came up empty. I reran the code and 2 came back with the
OVER_QUERY_LIMIT. So, it took 3 passes to geocode 698 addresses. I had
to use 726 calls. Luckily this is only one of the tables that needs
updating and we only submit it to geocoding when the address changes.
We keep track of all our calls when geocoding on the server side as
stated previously.

Thanks again for the help.

On Aug 17, 9:19 am, "Ikai Lan (Google)" <ika...@google.com> wrote:
> Is this the maps API you're referring to?
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com | twitter.com/ikai
>

[Robert Kluin]

You know this is the App Engine list, not a Maps or gdata list, right?

[See The Light]

I have moved this to the API v3 group.

Thanks.

On Aug 18, 7:59 pm, Robert Kluin <robert.kl...@gmail.com> wrote:
> You know this is the App Engine list, not a Maps or gdata list, right?
>

> On Thu, Aug 18, 2011 at 22:37, See The Light <envisas...@gmail.com> wrote:
>
>
>
>
>
>
>
> > The Geocoding API v3. I am using the Xml response.
>

> > I just hit thelimittonight testing some changes that needed to be

> > implemented.  I had 698 addresses to geocode. I pulled them from the
> > database and submit each address using:
>
> >http://maps.googleapis.com/maps/api/geocode/xml?address={0}&sensor=false
>
> > I then write back some of the data in the response. I checked and 26
> > came up empty. I reran the code and 2 came back with the
> > OVER_QUERY_LIMIT. So, it took 3 passes to geocode 698 addresses. I had
> > to use 726 calls.  Luckily this is only one of the tables that needs
> > updating and we only submit it to geocoding when the address changes.
> > We keep track of all our calls when geocoding on the server side as
> > stated previously.
>
> > Thanks again for the help.
>
> > On Aug 17, 9:19 am, "Ikai Lan (Google)" <ika...@google.com> wrote:
> >> Is this the maps API you're referring to?
>
> >> --
> >> Ikai Lan
> >> Developer Programs Engineer, Google App Engine
> >> plus.ikailan.com | twitter.com/ikai
>
> >> On Tue, Aug 16, 2011 at 9:28 AM, See The Light <envisas...@gmail.com> wrote:
>
> >> > Over the past couple of weeks I have noticed an increase in the number
> >> > of "OVER_QUERY_LIMIT" responses we have been receiving.  Currently
> >> > whenever we make a call to be geocoded we keep track of that call and
> >> > decrease a counter on our end.  I have historical data that shows we
> >> > usually end the day with at least 300 queries left.  This AM, I cannot

> >> > even make aqueryoff the server because it returns thelimitmessage,

> >> > and I show in our table that we have some 2300 call left.
>

> >> > Is there a call that can be made to get your currentquerylimit? If