KML files have to be served from a publicly available server, you cannot do this from localhost.
I fell over on this point too, and we won't be the last, we've both lost time and money. Move the KML file to a public-facing server and it will probably work, but still, the rewrite-publish-test procedure really slows things down. BE AWARE that Google does some caching of the files too, so you have to keep changing the url of the kml file. (easiest way is to apend a timestamp to the url ie: [PHP example] http://www. a real website .com/mykml.kml?<?php echo time() ;?> It is definitely worth persevering though, there is an awful lot of good about being able to bundle a LOT of stuff into KML files. This is one spec you will benefit from reading line by line - ESPECIALLY if you start by assessing the supported elements shown on the table on this page: http://code.google.com/apis/kml/documentation/kmlelementsinmaps.html Good luck with it. (I apologise for not saying much more than Davide just did, but I want to test whether I can actually post to this group without Google Groups getting into some infinite loop of redirects - which has been the case for the last two days) -- 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.
