We looked quite a bit into dropping the key requirement, but it wasn't possible.
Only an encoded points string is required for encoding polys - we will display the points necessary for the displayed zoom level. That statement means that when you specify &mobile=true, we will render the static map using mobile-optimized tilesets. It's still a single image, but we tend to refer to the source as tilesets (since the static map server is really just a tile stitcher). There's more info on the mobile parameter in the developer's guide. - pamela On Wed, Aug 26, 2009 at 8:30 PM, bratliff<[email protected]> wrote: > > On Aug 26, 6:54 am, "pamela (Google Employee)" <[email protected]> > wrote: >> Hey Andrew- >> >> Thanks, that has come up a few times, and SV filed a request. Please star >> it:http://code.google.com/p/gmaps-api-issues/issues/detail?id=1637 >> >> If there is enough concern about the verbosity of the parameters, we >> can introduce short versions of each of them. There is a balance >> between URL length and API usability, but it is certainly possible to >> offer aliases of parameters. >> >> - pamela > > Dropping the key requirement (like V3 of the API) would reduce the URL > length by 100 plus characters. > > I assume the "zoom string" is not required for encoding polys. > > The Upgrade Guide makes the following statement: > > "we can provide mobile optimized tiles for every map type." > > What does it mean ? A static map is still just a single image, > right ? > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
