No, there are lots of features that aren't supported yet in v3. In this sense v3 is a clear regression.
It seems there is no easy way to migrate. It has to be done manually line by line. I can imagine that someone will write a conversion script using Perl or something like that. You can try to see it positive: When you now provide a map made with v2 there is a guarantee that nothing will change or be broken the next three years. That's a long time... On May 21, 9:47 pm, anna72 <[email protected]> wrote: > Hi, > > I've seen that v2 is now deprecated and the new v3 version is very > different from the v2. I have a lot of code for v2 that use different > features, like encoded polylines, custom map types, google earth > integration, etc. > Are all feature of v2 already supported in v3? Is there an easy way to > migrate? > > Thanks > > -- > 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 > athttp://groups.google.com/group/google-maps-api?hl=en. -- 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.
