"In fact, I'm wondering if it's time to remove that format
from our list and
two tweak the cited doc to just use KML instead. Is anybody on the
successfully using this format?"
After struggling with the js format, I have been using KML for route
planning on Google maps then converting to OziExplorer. It is not
straightforward. The file contains the set of waypoints describing
the route, and one or more polylines with the more detailed
geometry. I have to read the destination coordinates from one part
of the file and paste them into another part before doing the
conversion. With KML I can use a text editor to do this. Otherwise
the destination doesn't plot in the right place. It is a while
since I wrote the Vim scripts to do this, so I'm struggling to
remember exactly what the problem was but I can send the scripts if
you want. They do work, even if you have dragged your route around
a bit. There is also an issue with output to the OziExplorer
format, which is csv, where there are commas in the waypoint
I'm sorry I don't understand the structure of babel's source well
enough to solve the problem in C.
However, there is still a problem where you have intermediate
destinations (vias). Babel will pick up the first part but not
subsequent parts, in my experience. I don't have a workaround for
that as I rarely use it.
What you do with the converted files is of course subject to
Google's terms of service. Hope this helps.