On Apr 9, 12:01 am, "Maps.Huge.Info (Google Maps API Guru)" <[email protected]> wrote: > > Encoded polygons work well if you've encoded them properly, except > when you start getting up in the 100's and 1000's of points, then, > like all API objects, they become slow.
Complicated polygons will take a little time to assemble, but correctly encoded polys can generally be manipulated ok once they're drawn. http://www.achurchnearyou.com/parishmap.php?pcode=30/30 shows a map with an encoded polygon comprising 4821 points. That page takes five seconds to load on my ADSL connection, most of which is waiting for Google Analytics. I reckon 5000 points is a reasonable maximum for an encoded polygon. Out of nearly 12900 parish maps, I have four with more than that number (the winner is the Isles of Scilly at 24224 points, and it's horrendously slow!) 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 -~----------~----~----~----~------~----~------~--~---
