I still haven't found a way to implement what I want, but just to let you know both the KML files and the application reside in the same domain.
Thanks! Joice On 23 jul, 12:22, Rossko <[email protected]> wrote: > The first problem to address is cross-domain. You seem to be asking > to parse KML from someone else's domain, is that right? > > The API provides a method GGeoXml which can do that (because it gets > Google's servers to do it for you), but its quite restrictive about > how much you can customize the results. > > There are third-party clientside KML parsers, GeoXml and EgeoXml, that > allow you as much scope to tailor as writing your own. But they won't > work directly with other-domain source - that's a browser restriction, > not a maps one. You can circumvent that by putting a proxy service > on your own server. > > KML is only XML ina given layout. You can enhance your existing XML > parser to read KML instead. You only need to read the parts you want, > not implement a full KML parser. You'd still need that proxy for > cross-domain work. > > cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
