I'd like to clarify the item below a bit-- I found that 2.140 DID work but anything later doesn't. Hope that helps. If I use v=2 it breaks. NWOP
On May 5, 5:37 pm, "[email protected]" <[email protected]> wrote: > On Apr 30, 5:23 pm, pamela fox <[email protected]> wrote: > > > Maps API versions prior to 2.140 will be deprecated on July 1, 2009. > > As detailed in the Maps API documentation, we review recent Maps API > > versions each quarter to select a release suitable for use as the > > current stable version, v=2.s. The 2.s version is also provided to all > > sites that request a specific version older than the current 2.s > > version. > > > We've recently completed such a review, and have chosen 2.140 as the > > next stable version. We will be updating the 2.s Maps API version to > > 2.140 on July 1, 2009. All sites requesting version 2.s or a version > > prior to 2.140 will automatically move to using 2.140 at that time. > > If your Maps API application is using 2.s or a version prior to 2.140 > > we recommend that you begin preparing for this change now by testing > > your applications using 2.140 (or the most recent v=2, 2.151). Please > > file bugs for any regression issues that you encounter. > > Pamela, > There seems to be a problem with encoded polylines. They work in > v2.118, but not in v2.140. See this > thread:http://groups.google.com/group/Google-Maps-API/browse_frm/thread/54cb... > > -- Larry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
