On Aug 26, 5:08 am, "pamela (Google Employee)" <[email protected]> wrote:
> We have now launched a version 2 of the Static Maps API, and > deprecated version 1 of the API. The new version introduces several > new features (encoded paths, filled polys, geocoding, hexadecimal > colors), and also fixes various issues. Please see the changelog for > more detailed > information:http://code.google.com/p/gmaps-api-issues/wiki/StaticMapsAPIChangelog I'm sorry that I seem to post first with a potential problem on many of these change notices. While it's good that encoded polys are supported, as that will help include lines and polygons within the browser's limit on GET requests, how does something like the following (from the documentation) help with that? >> For example: midreda becomes: size:mid|color:red|label:A << I appreciate that separating properties of a marker in such a way will make it easier to build markers server-side and add them to the map image; but it hardly helps with the length of the URL. I'll raise an enhancement request, but I think that size:mid|color:red|label:A could be implemented with abbreviated property names s:mid|c:red|l:A or even make property names optional so that if they are not specified the order is used: mid|red|A which is still two characters longer than the v1 request. 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 -~----------~----~----~----~------~----~------~--~---
