Chad, Larry, Added <Document> tag. it worked.
I then went on created one for Australia. The file size is 19M and the boundaries did not show up. BUT, I then created one for Tasmania (the one part that has the most points in AU). It shows HUGE (thanks Chad) performance improvement over my FromEncoded() method. So, even with the size limitation of the kml, I will use this approach (with clustering at country zoom level). Thanks a lot for your insight and help. John On Oct 19, 9:16 am, Chad Killingsworth <[email protected]> wrote: > > <[email protected]> wrote: > > > If you have more than one placemark, your placemark nodes need to > > > be wrapped in a <Document> node. > > > Where is that defined/stated? > > http://code.google.com/apis/kml/documentation/kmlreference.html#kml > A basic <kml> element contains 0 or 1 Feature and 0 or 1 > NetworkLinkControl: > > > > You can always test your kml by > > > loading it in Google Earth and at maps.google.com (put the kml url > > > in the search bar). > > > maps.google.com doesn't > > complain:http://maps.google.com/maps?hl=en&q=http:%2F%2F209.35.190.130%2Fkmlte... > > but only displays one polygon. I didn't try google earth > > Correct (Google Earth doesn't complain either but only displays 1 > poly) - but in all instances, it's not what he wants. Therefore the > problem lies in the KML and not in the map or javascript. > > Chad Killingsworth -- 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.
