On Sep 9, 3:02 am, Andrew Leach <[email protected]> wrote: > > Ignoring Google's documentation on encoding is probably a good idea. > Mark McClure's is far better. > > http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/
LOL. I never thought of it that way (it probably being a good idea to ignore) ... But I have started to use Mark's encoder. I do still want to figure out what the three options do together though. the API's documentation does say that they work together, but ... what exactly they do is still a mystery to me. Oh well, for now it works, and I'm going to move on to the next step in the project. Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
