Re: [Google Maps API v3] Re: KmlOverlayService 500 Internal Server Error

2011-05-30 Thread Matthew C
OK, thanks for shedding some light on the matter. I plan to switch to KMZ, and I certainly won't be serving from SVN in production! The random numbers, too, will disappear in production. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3

Re: [Google Maps API v3] Re: KmlOverlayService 500 Internal Server Error

2011-05-29 Thread James McGill
For those interested, here's the command I used to time downloads: time wget -S http://foothill-web-gis.googlecode.com/svn/data/rooms1.kml?randomnumberhere Looking at the download speed is insufficient as it doesn't take into account the size of the file, or request latency. Regards, James On

Re: [Google Maps API v3] Re: KmlOverlayService 500 Internal Server Error

2011-05-29 Thread James McGill
Hi Matt, You are correct in inferring that the file is taking too long to fetch. By appending a random number (to prevent Google caching the file) you are effectively making the KML file dynamic - Google must download and parse the file every time you change that random number. I used wget to ti

[Google Maps API v3] Re: KmlOverlayService 500 Internal Server Error

2011-05-29 Thread Matthew C
By the way, http://code.google.com/apis/maps/documentation/javascript/forum.html?place=forum/google-maps-js-api-v3seems to be related, but they're discussing dynamically generated KML and this is static and there doesn't seem to be an answer there either. Meant to mention this thread in the ori