On Apr 6, 12:33 am, programmertim <[email protected]> wrote: > By viewing the source of the google site, I think the > geocode parameter must be the "via"s of the route. It > appears that the route is built by the list of destinations > (in this case just the start and end) and then adding the > via points from the geocode parameter. But plugging those > codes into the site here: > http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/decode.html > doesn't give valid points.
Bit late, but I just stumbled on this. The decoder probably fails because driving directions produce point's string with escaped backslashes. Strings entered into my polyline decoder don't need escaped backslashes; thus, every '\\' should be replaced with a '\'. The \\ thing is a bit subtle. You need it for a string literal, "like this". You don't need it when the string is read from a web form. I know it's odd, but I tried to explain this here: http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/pitfalls.html Mark McClure --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
