Hello, all - The starting point for this post is the note on KmlLayer here: http://googlegeodevelopers.blogspot.com/2010/05/map-your-data-with-maps-api-and-fusion.html
We're now managing complex polygon sets as KML files with GGeoXML. GGeoXML fails with a .kmz somewhere over 1MB. It's the size of the whole file, not the number of polys, which seems to matter - I have one with about 1,000 polys which loads just fine, but the polys are very simple. As a practical example, a .kmz of the postal area file for Ontario (789KB, about 500 polys) loads, but one of all of Canada (2.8MB, about 1500 polys) won't. The all-Canada .kmz has a lot of space-hogging complexity (eg. the Arctic islands are mapped in a lot of detail), and I could probably bring it under 2MB with no loss of meaningful information. I haven't bothered thus far because we haven't been able to display a file that large. Based on some experiments putting these two files into KmlLayer, the results are about the same as with GGeoXML, which is that the Ontario file loads and the Canada one doesn't. Is there a known failure point for KmlLayer for polygons, either in terms of the whole size of the file or the number of polys represented (or even the size of individual polys)? -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
