Google warns that rate limits, overage fees are coming to Maps API

Re:Google warns that rate limits, overage fees are coming to... by willfully_lost on Thursday October 27, 2011 @01:28PM (#3164316)

Reposted from other Maps thread

Aren't the limits IP based? This page on Google's 'Geocoding Strategies' seems to say so: http://code.google.com/apis/maps/articles/geocodestrat.html#...

So as long as your call to the Maps API goes out client side, aren't you ok?

[ Parent | on HN ]

Re:Google warns that rate limits, overage fees are coming to... by lftl on Thursday October 27, 2011 @01:33PM (#3164348)

I think the Maps API is different than the Geocode in that the Maps API requires you to grab a key here:

http://code.google.com/apis/maps/signup.html

So to avoid it in that sense you'd have to force every one of your clients to go grab an API key and input it.

[ Parent | on HN ]

Re:Google warns that rate limits, overage fees are coming to... by willfully_lost on Thursday October 27, 2011 @01:45PM (#3164440)

Look at the note at the top of the page you linked, Version 3 of the Maps API doesn't require a key.

[ Parent | on HN ]

Re:Google warns that rate limits, overage fees are coming to... by mildweed on Thursday October 27, 2011 @03:02PM (#3164931)

Not only does v3 not require an API key, as of Sept 28 (a couple days before the rate limiting went into effect) sending a v2 API key to v3 will cause the request to fail:

http://groups.google.com/group/google-maps-js-api-v3-notify/...

Sounds like they're laying the ground work for v3 to use API keys again.

[ Parent | on HN ]