@Marco – Thanks a lot for your kind words, I’m glad it was helpful. I spent a decent amount of time smashing my face into the desk when I first stumbled across the encoded Polyline problem, which is what prompted me to create this in the first place.

As you say, it does seem odd that the ‘native’ Google Maps Flash API doesn’t expose the encoded String given that it must exist somewhere. Perhaps it’s a consequence of trying to keep the Flash API featureset common with the JS version. In any case, it’s definatly something worth adding as a feature request, which I shall do very soon.

Thank you so much for posting this! I’ve spent the last six hours trying to get the encoded String that results from a Directions request. After reading this post, it only took me 15 minutes.

I wonder why Google doesn’t allow access to it? It is part of the response you get from their servers, a simple Directions.getEncodedPoints() would’ve been great. Nonetheless, you’re a lifesaver, so thank you for taking the time to share this with us.

- Marco

Thanks!

yep, you’re free to use this as you please and I’m glad you’ve found it useful. I’m not sure what issues you’re having with the license though, if you look at the source at http://code.google.com/p/duncanhall-lib/source/browse/trunk/net/duncanhall/gmaps/PolylineEncoder.as you can see it’s licensed under GNU General Public License which should cover your needs.

http://www.opensource.org/licenses/mit-license.php

Cheers,
– Dan

your site is good!…