I've been in touch with Brekin/Jan/Cindi off-thread as well, by the
way. We didn't think about this sort of usage (many maps on one page),
so our limits do not quite accomodate it, and we haven't resolved the
best way to accomodate this usage while avoiding scrapers.
The current limits are:
250/6 hours ("1000/day" is the documented version of that)
50/1 minute (we didn't document this, as we didn't expect anyone to run into it)
We can document that second limit as well, but we would probably
describe it as a limit of the maps on a page, as that's how it
manifests itself to people using the API in a legal way.
Thanks for bringing this to our attention!
- pamela
On Thu, Sep 3, 2009 at 10:32 AM, Rossko<[email protected]> wrote:
>
>> ... As for demanding resources you could probably have greater
>> than 50 normal Google Maps on a page (I have not tested that though)
>> and that would be a lot more demanding (though unusable).
>
> Would it? Each static map is created at the server as required, i.e.
> image manipulation and stitching together.
> An API map is just a simple tile-serving load.
>
> Anyways, its not me you have to justify anything to. If you want
> anything to change, or think the documentation is lacking, raise a
> formal issue.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---
