On Aug 31, 2:02 am, HappyBiker <[email protected]> wrote:
GGeoXml will use encoded polys unless you are able to trick it into
cutting tiles for you using the mapsdt / mapslt service. Encoded
polys only retain five decimal places of accuracy. Your polys require
six. At zoom level 14 things start to degrade.
For V3, Google has an opportunity to scrap its Lat/Lon based poly
encoding algorithm with obsolete "zoom string" in favor of a lossless
pixel based compression algorithm. A little friendly persuasion
cannot hurt.
See:
http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/140a06c9a7441c84#
One option:
www.polyarc.us/polypack.js
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
