> Thanks for your quick response, what would you recommend as a solution > because I have seen examples where large amounts of data are being > displayed. How do they do this?
Since the problem is with parsing and rendering complex/large KML, look for alternative parsers. There are two commonly-used 3rd party parsers, GGeoXml and GeoXml. Or of course you can write your own parser (especially worth considering if you're only using a subset of KML functions, like say polys - you don't have to support everything). These run client-side, so you'll lose browser performance to download and analyse fat KML files. Note that doesn't do anything about other inherent limitiations of the maps API - trying to display several hundred complex polys will still crease the browser. It's possible to build a server-side KML parser that would render to tile overlays instead (like Google's parser does in some circumstances) but I don't know of anyone that has done that. Drawbacks of that would be ease of interaction (click, mouseover) client-side but all things are possible. 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 -~----------~----~----~----~------~----~------~--~---
