Surely it's true that pure XML is a lot more flexible to use than KML. But Google is interested in data, so they are interested in KML because they can index these files.
On Jul 9, 4:10 pm, AJ <[email protected]> wrote: > Greetings. I'm new to the API, trying to optimize my strategy. > > I've got server-side code that's outputting KML from my database. I'm > using the API to display the KML as a an overlay. > > As the title says, it seems like I can do a lot more by parsing the > KML file and plotting data using the API. Seems like that way I can do > some sorting/filtering and apply different markers to different > features, while using the KML I am pretty limited. > > Should I keep using the KML as an overlay? Or, should I use Javascript > to crack open the KML and plot the data using markers? Or, would I be > better off just creating an XML file, and not using KML at all? > > Thanks in advance. -- 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.
