non-streetbound routes?

[Andreas]

Hi,

I'm new to RouteConverter and have a question about routes.

But first, some words about me. I'm the developer of GPSMonitor (www.gpsmonitor.de), a tool for GPS-based navigation especially on board of sport boats. While searching for a tool for creating and editing routes for later use with GPSMonitor, I just found RouteConverter.
I'm 36 years old and live in Germany (Dortmund, working in Duisburg).

Now for my question:
As mentioned, I would like to create routes with RouteConverter for use on a boat. Therefore, the fact that routes in RouteConverter seem to be street-bound in the left-hand map view is somewhat annoying. In the exported GPS-file, the structure of routes / route points fits my purposes perfectly. Is there any chance to "loose" routes from streets in the map view and show the simple direct line between the route points?

As this would help anyone who uses RouteConverter for watersports, it seems to be a nive feature to me.

Andreas

[routeconverter]

Is there any chance to "loose" routes from streets in the map view and show the simple direct line between the route points?

Hi Andreas,

look for the "Type:" chooser and select "Track" to get a simple beeline view.

[Andreas]

Is there any chance to "loose" routes from streets in the map view and show the simple direct line between the route points?

Hi Andreas,

look for the "Type:" chooser and select "Track" to get a simple beeline view.

Hi Christian,

thanks for your quick reply.
That works perfectly fine, but in that case, the points are stored as track points in the gpx file. In my understanding, track points are used for points of actually driven routes (= tracks) only, not for planned routes. Therefore, my tool today uses <rtept> for managing routes and <trkpt> for saving the effectivly driven track. But of course I can change that.

Aside from that, RC is the perfect tool for my purposes (and I've been searching a while now!), and especially the Java WebStart concept is quite fine.
I will keep on testing, then I probably will modify GPSMonitor in some details and recommend RC as a complementary tool for it to it's users.

[routeconverter]

That works perfectly fine, but in that case, the points are stored as track points in the gpx file. In my understanding, track points are used for points of actually driven routes (= tracks) only, not for planned routes. Therefore, my tool today uses <rtept> for managing routes and <trkpt> for saving the effectivly driven track. But of course I can change that.

Actually, I wouldn't do that as it's fine the way you've currently implemented it. Google Maps just offers streetbound routes...

[Andreas]

That works perfectly fine, but in that case, the points are stored as track points in the gpx file. In my understanding, track points are used for points of actually driven routes (= tracks) only, not for planned routes. Therefore, my tool today uses <rtept> for managing routes and <trkpt> for saving the effectivly driven track. But of course I can change that.

Actually, I wouldn't do that as it's fine the way you've currently implemented it. Google Maps just offers streetbound routes...

Ok. Perhaps I will implement a "RC compatibility mode" flag in the ini file for that.