On May 12, 10:14 am, "Alex (cp9)" <[email protected]> wrote: > > This was very very quick without any recognizable lag when you use > GPolygon without fromEncoded. But than the Polygon needs to load very > long on first time. Because the data to send for a Polygon with 1500 > Points is about 10 times bigger if it is not encoded. And on the > client side you have to create GPoints for all the 1500 Points to > create the GPolyline. This needs long time.
It would be useful to have a link to a demonstrator page, perhaps with a comparison. Have you tried fixing your API version to something other than v=2 (say v=2.153 or 2.155 or even 2.140)? If you can find a previous version where behaviour is better, you may well have found a bug. Do you really need all 1500 points? Can you simplify your polygon? Does that make a difference? However, as you say, there may well be a trade-off between "ordinary" polygons and encoded polygons. 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 -~----------~----~----~----~------~----~------~--~---
