On Dec 29, 6:02 pm, crispy barcelona <[email protected]> wrote: > Hi, > I have just started using v3 with a very basic map which references an > external kml file using KmlLayer. However, while everything works I'm > confused about the kml. I generate the kml in plain old Google Maps > using the My Maps feature, but the kml file produced is not a REAL kml > file but a link to dynamically write the file via Google Maps.(not a > technical explanation, sorry!) > This makes me nervous as it means I don't actually physically have the > kml documents but am dependant on Google getting the info from My > Maps. example:http://www.the-barcelona-guide.com/areas/barcelona.htm
The "real kml" is here (you just need to follow the network link): http://maps.google.es/maps/ms?ie=UTF8&hl=es&vps=1&jsv=304d&oe=UTF8&msa=0&msid=212903287985296253044.00049807f59320c096b7a&output=kml > So my question is: In a no frills map implementation are there > advantages to having the kml doc go request the data from Google Maps > rather than having a full KML doc hosted on my server? The advantage of using the version hosted on Google's servers is that it will be more easily and quickly accessible by most people (and by google when you go to load it with KmlLayer. It would still be a good idea to keep a copy of it on your server, though, just in case. -- Larry > thanks > cripsy -- 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.
