You appear to have understood him correctly, but remember that it won't be a filepath to the KML file your server created but rather the URL of the KML file itself. The Google server will fetch the KML file, do its thing, and then create and display the layer for you.
On Fri, Jul 30, 2010 at 9:43 AM, Rossko <[email protected]> wrote: > > Have I understood correctly ? > > That'll work. > > Bear in mind all the data seems to be available at the client in the > first place and could be rendered directly; why you are sending it off > to be converted to KML is opaque to us. > > If you need it as KML for storing/distributing/sharing, you need also > to keep in mind the restrictions on the use of Directions service > derived data. > > -- > 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]<google-maps-js-api-v3%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- 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.
