On Mar 22, 11:23 pm, BuckyE <[email protected]> wrote: > Rather than mucking about with GeoXML, I've decided to just use the > brute force method of having all markers, polylines and polygons > created from a standard XML. It works for me. Someone more expert at > the whole thing needs to work out a routine for handling Garden Shed > Sized Polygons!
I have not been following the discussion. Sorry if I am repeating something someone else has already said. At very deep zoom levels (18, 19, 20, 21), encoded GPolys suffer severe rounding errors. Floating point Lat/Lon coordinates are converted to integers by truncating to five decimal places of precision. Zoom level strings perform point reduction which may introduce distortion. Traditional GPolys may improve appearance. Google seems to be abandoning "fromEncoded" GPolys in its GGeoXml service. If a KML file is relatively simple, without "click" requirements, Google builds a tile layer overlay with its "mapslt" service, the successor to its "mapsdt" service. A tile layer overlay has superior performance to a GPoly. Parsing a KML file served to the browser through a proxy with a javascript addon approaching the size of the API itself seems a bit senseless. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
