The original boundary has a point about every 100 metres, and it's around 1000km in length, so approximately 10000 points in the polygon. 10000 is too many points if you want the map to load quickly, especially if the boundary is being drawn twice (20000 points for the browser to draw).
100 metres is approximately 0.001 degrees, so by reducing the points using the douglas algorithm with 0.001 degrees as the tolerance produces a polygon with around 1500 points. Using the Encoding form on http://facstaff.unca.edu/mcmcclur/googlemaps/encodepolyline/ produces an encoded polygon of approximately 10KB in size. Encoded polygons will be quicker to load than KML. You could load them using an ajax query for JSON data. Including the outer boundary, the total size of the following map is around 12KB and loads quickly: http://www.william-map.com/20100609/2/map.htm ... -- 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.
