> I'm using a KMLLayer to load a KML file, which contains 955 placemarks.
It's getting a bit close to the maximum features limit http://code.google.com/apis/kml/documentation/mapsSupport.html There have been a few threads kicking around which suggest that Google's KML parser will abort renderings of large, complex or slow-to- serve files due to a timeout. There's no clear indication that is the root issue, but the result seems to be apparently 'random' failures. Some people have had success by minimizing the delays under their control, e.g. removing redirections, serving flat files instead of building dynamically, finding fast hosting. It would be nice if some failure type indication were available, this is all guesswork. -- 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.
