Unfortunately, on most *mobile* browser the limit is the bare minimum specified by the RFC which is 255. There are actually some that support even less (such as 128, 100, etc) but I am not planning to support them. You can refer to the WURFL mobile device database file to check for yourself that this is the case.
I suspected that the API key cannot be shortened by the rest of my suggestions result in huge space savings as well. Finally, I cannot write my own proxy because Google explicitly forbids this in their TOS and FAQ (Static Map images can only be used directly in the img-src or background image of an HTML page). As for a URL shortener (even though it seems like a good idea at first) is a not an option because such a service would (if not proxying the request) be redirecting the browser to the actual URL which would still overflow the URL size limit. Sincerely, Ufuk On Jan 12, 6:58 pm, Andrew Leach <[email protected]> wrote: > On Jan 12, 4:46 pm, Ufuk Kayserilioglu <[email protected]> > wrote: > > > The URLs specified by the Static Maps API generally turn out to be too > > large for mobile devices to handle. > > See issue 1637, where an enhancement was > suggested.http://code.google.com/p/gmaps-api-issues/issues/detail?id=1637 > > Google have already indicated elsewhere that the key cannot be > shortened. Is the URL length really only 255 characters? Most browsers > allow up to 2048. > > Don't forget that you could write your own proxy to implement this > abbreviation, or even use a service like TinyURL. > > Andrew
-- 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.
