On Jan 18, 6:25 am, "Randall H." <[email protected]> wrote: > I had 4 KMZs - each one was 270K to 600K compressed, and each was > 2.2MB to 3.8 uncompressed. Attached is one of the files that was > specifically called out with the statement: > > "The problem is that your KML files have too many vertices (the > largest is ZayoMetroNet_part3_010311.kmz which has about 115,000 > vertices in about 6,600 lines) and they are triggering a > performance bug in our rendering system."
The main thing I see looking at that file is that it contains a lot of short <LineString> segments in a MultiGeometry. Why the short segments and not a single <LineString>? I suspect it is the large number of <LineString> elements that is causing the problem (or the combination of the 2), not the absolute number of vertices. -- Larry > > I've since split the 4 files I had into 10 smaller KMZs. > > ZayoMetroNet_part3_010311.kmz > 854KViewDownload -- 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.
