Thanks! That is very informative and helps me out a great deal
On Feb 16, 7:03 pm, "warden [Andrew Leach - Maps API Guru]" <[email protected]> wrote: > On Feb 16, 11:00 pm, mcslain <[email protected]> wrote: > > > > > Can I inquire further though about your comments on encoded level > > strings and the purpose of encoded polylines? I thought that the > > purpose of an encoded polyline was: > > > 1) compact code > > 2) faster rendering times > > 3) ability to set zoom levels > > > How am I missing these benefits? I am using a string of Bs because > > that is what the encoding utility gave me. The GMap doc example > > seems to use all Bs as well: > > If your levels string is all the same, you plot every point and every > zoom level. The beauty of correctly encoded polylines is that they > don't plot every point if there's no point in doing so (excuse the > pun). > > Mark McClure is the expert and has done a better job of explaining > things than Google > has:http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/ > > He also explains about the double-backslash peculiarity of Javascript > strings as opposed to HTML textboxes. > > Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
