Other than the official documentation, here's a good start: http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/
Chad Killingsworth On Oct 5, 4:30 am, sgiddings <[email protected]> wrote: > "The "old" encoding algorithms are freely available if you wanted to > extend the APIs classes. " > > Can you tell me how to get hold of these ? > > On Oct 5, 1:10 am, Rossko <[email protected]> wrote: > > > > > > > > > > Also, it's just plain messy to have a loop that steps over all the > > > points creating a new instance of a LatLng for each point, surely that > > > sort of drudgery should be hidden via a Google API call like > > > Polyline.setPathByPoints(pointarray); or similar, and all the looping > > > etc. can be done behind the scenes and in whatever optimised way that > > > google wants. > > > It's only a loop, probably three lines of code. An alternative view > > is that you can optimize it exactly how you wish, and transfer data in > > whatever form you wish, without being constrained by what Google might > > choose for you. > > The "old" encoding algorithms are freely available if you wanted to > > extend the APIs classes. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
