API Console Counts

[Mike Cairns]

The Maps API v3 "# of requests" in the APIs console shows 2 hits for each map load, even using the example map code from the Google Maps Javascript API V3 Tutorial.

I have tried the v2 example as well, with a different key, and the results are the same.

[Andrew Leach]

Not only that, but the console key doesn't work in the [Version 2]
geocoder. Error 610 (bad key).

This is a stumbling-block. I need to know the usage of one particular
set of maps in order to know whether it's worth converting them to
Version 3 or something else. And to know how the geocoder and
directions service are counted.

[Richard Davies]

Yes, I've noticed my console reporting two requests for every page load also.

[Chris Broadfoot]

Hi all,

We're looking into it - looks like there's a problem with our graphs - as far as I know we're actually counting quota correctly, just displaying it incorrectly.

Chris

--

http://twitter.com/broady

On Fri, Dec 2, 2011 at 7:54 AM, Richard Davies <richard...@gmail.com> wrote:

Yes, I've noticed my console reporting two requests for every page load also.

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/B96RJ22iZjIJ.

To post to this group, send email to google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[alpaca]

We are getting "REQUEST_DENIED" response codes when we add the key
generated by the API Console (tried both the key for server apps and
the key for browser apps). I confirm that I have Google Map API v3
enabled.

Tested using the following url (basically the sample url), works fine
without the key added... but returns request denied when we add
"&key=[generated key]"

http://maps.googleapis.com/maps/api/geocode/json?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA&sensor=false

Just like Andrew Leach... this is a pretty big stumbling block for us
to evaluate the viability of using the v3 Geocoder going forward.

Thank you for your time,

On Dec 1, 6:26 pm, Chris Broadfoot <c...@google.com> wrote:
> Hi all,
>
> We're looking into it - looks like there's a problem with our graphs - as
> far as I know we're actually counting quota correctly, just displaying it
> incorrectly.
>
> Chris
>

> --http://twitter.com/broady

>
> On Fri, Dec 2, 2011 at 7:54 AM, Richard Davies <richarddavie...@gmail.com>wrote:
>
>
>
> > Yes, I've noticed my console reporting two requests for every page load
> > also.
>
> >  --
> > You received this message because you are subscribed to the Google Groups
> > "Google Maps JavaScript API v3" group.
> > To view this discussion on the web visit
> >https://groups.google.com/d/msg/google-maps-js-api-v3/-/B96RJ22iZjIJ.
>
> > To post to this group, send email to
> > google-map...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-maps-js-a...@googlegroups.com.
> > For more options, visit this group at

> >http://groups.google.com/group/google-maps-js-api-v3?hl=en.- Hide quoted text -
>
> - Show quoted text -

[Barry Hunter]

v3 geocoder does not require a key.

There is nothing in the documentation that mentions a key
http://code.google.com/apis/maps/documentation/geocoding/

... the geocoder is not included in the new quotas anyway. So having a
console key on the geocoding request wouldnt help you. (the console
key is for loading the javascript api itself)

[Chris Broadfoot]

This was fixed last week, thanks for all the reports on this!

--

G+: http://chrisbroadfoot.id.au/+

Twitter: http://twitter.com/broady