11 ms·

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#quota-limi

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#quota-limits 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?

sv123 15y ago
I am confused about this too. It seems like 99% of sites using maps would be doing it client side in which case the cost change wouldn't be a big deal, but maybe I am missing something.
- Stratoscope 15y ago
  They are talking about client-side APIs, but the limits are not per client IP address. They can look at the referer header to see what site embedded the map.
  - sv123 15y ago
    Not if your pages are https.
    - ohashi 15y ago
      Google blocks you from seeing referred search terms and you flip it around so they can't see what server the requests on their API are coming from. Seems kind of fair, right?
ajtaylor 15y ago
Probably, since the new JS Maps v3 API a key is no longer required.
Stratoscope 15y ago
They can and presumably do look at the referer header on the requests for .js files and map tiles.
- willfully_lost 15y ago
  So you think that the Geocoding API will work via IP limits as described in the link I provided, but regular Maps API calls will be subject to domain limits?