Route Query

[Warhippo]

Hi Guys

Could someone explain why viewing waypoints as a Route ignores the set waypoints and instead follows the closest road? For example, when I create a series of waypoints, I can view them as a Track correctly (the blue path line goes from waypoint to waypoint ala dot to dot) but when I view it as a Route, the blue path line follows the closest path from start to end waypoint.

I want to export my 'path' to my GPS as a Route that follows each point in exactly the same way as a Track works, but I don't want to export it as a Track.

I'm probably being dense here so feel free to chastise me : )

Cheers.

PS I'm using RCMac64 v2.4 on OS X10.6

[routeconverter]

Could someone explain why viewing waypoints as a Route ignores the set waypoints and instead follows the closest road? For example, when I create a series of waypoints, I can view them as a Track correctly (the blue path line goes from waypoint to waypoint ala dot to dot) but when I view it as a Route, the blue path line follows the closest path from start to end waypoint.

It seems like you have a lot of waypoints. Then two effects occur:

• RouteConverter reduces the number of waypoints given to the Google Maps servers to avoid a crash of the embedded map
  
• the routing algorithm on the Google servers routes over its own street map - for waypoints distant to routes this often results in strange results. And this may be completely different if you do the routing on your device.
  

So to sum up: Don't take the routing too seriously and always double check that the exported route does on your device what you'd expect.

I want to export my 'path' to my GPS as a Route that follows each point in exactly the same way as a Track works, but I don't want to export it as a Track.

I guess you're exporting to GPX? Then select the type 'Route' and save the file while simply ignoring the display on the map on the left.

[Warhippo]

Thanks for getting back so fast!

As it happens, I only have 4 waypoints in my route (I've got the same results with all the Routes I have created - the largest had about 20 waypoints in it).

So you're saying that the blue path (at least for Routes) may have nothing to do with what I export (as a GPX file). Consequently, I could dot my Waypoints, view them as a Track with RouteConverter to check that it matches what I'm after but export as a Route and although the blue path will suddenly change from when I viewed it as a Track, the Route will be stored 'correctly' on my GPS. If that's the case, then that's great - your app is just what I'm after.

[routeconverter]

So you're saying that the blue path (at least for Routes) may have nothing to do with what I export (as a GPX file).

Not nothing, but you'll find only your 4 waypoints in that GPX file and the device that reads the file has to calculate the intermediate points to form a route.

Consequently, I could dot my Waypoints, view them as a Track with RouteConverter to check that it matches what I'm after but export as a Route and although the blue path will suddenly change from when I viewed it as a Track, the Route will be stored 'correctly' on my GPS. If that's the case, then that's great - your app is just what I'm after.

RouteConverter should work like you assume it. Just make sure you switch to 'Route' before saving before that changes the GPX that is written.

[Warhippo]

Excellent - thanks very much for helping me out (and writing the s/w in the first place).

[kumo]

This is for street based navigation devices:

Per definition...
...the waypoints of a route are connected via streets.
...the waypoints of a track are connected via air-to-air.

Routes are some pre-planned waypoints for street based navigation devices.
Tracks are many waypoints, recorded during motion while following a route.

Offroad, nautical, aeronautical are special cases.