On Apr 30, 9:04 am, Dommer <[email protected]> wrote: > I know this is a simple question, but: What is the difference between > an encoded polygon and a gpoly? > > An encoded polygon uses GGeoXML() and a regular gpoly uses the general > addoverlay() on parsed and formatted strings? No.
See the documentation and Mark McClures description (referenced earlier): http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/ -- Larry > > Dom > > On Apr 30, 6:01 am, bratliff <[email protected]> wrote: > > > > > > The "Earth's circumference" constant used to convert from Lat/Lon > > > coordinates to pixels may be an issue. Encoded polys are only > > > accurate to five decimal places. Beyond zoom level 17 you will > > > experience rounding errors. Whether "mapsdt" / "mapslt" has similar > > > limitations, who knows ? > > > P.S. > > > Try using traditional GPolys. You ought to see less distortion at > > very deep zoom levels (18, 19, 29, 21). Floating point numbers are > > not reduced to five decimal places to convert to integers. Zoom level > > strings are not used to perform point reduction.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
