On Jan 19, 5:40 pm, bratliff <[email protected]> wrote: It looks like "mapslt" has replaced "mapsdt". The parameters are different. The path to the KML file has been obfuscated.
If your KML file is complex enough, GGeoXml will use "mapslt" instead of GPoly.fromEncoded. The trick is to figure out the threshold. You will have to use trial & error to figure out the point at which GGeoXml starts using "mapslt". The difference in speed is significant. Also, the tiles produced are cacheable both locally & at the server. With GPoly.fromEncoded, each session has to rebuild polys from scratch. Two users displaying the same polys will not benefit from a common server cache. One user running the same application twice will not benefit from a common local cache. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
