Thanks for updating it!

Boy, if it's not doing the conversion, then we need to get to the bottom of the problem. Cuz it's not very useful when you're talking tight city streets, it tends to make you miss turns when it's off by a factor of 100-200 feet.

I tried taking a route I'd recenly done with parse_google.py and comparing it to the same route done with FromGM.exe, and they were different in some interesting ways, such as the number of points on the line being different. (FromGM had more points.) I'd assume Google changed the datum, but oddly, a some of those additional points were ones directly adjacent to a turn, and were exactly one digit off from the turn. It's not the double-points-at-a-turn thing rearing its ugly head again?

Anyway, I'll send you the comparison of the two routes in a Private Message.

PS: Also noticed that the text of the last data point no longer says "End At <address>" the way Parse_Google used to do. The last data point is now blank. Was that something specifically put into Parse_Google, or did the web site change the way it shows the instructions?