"Direct routes"

[JRThump]

Feature wish: Tick box called "direct routing" or "disable auto-routing" or similar. With this box ticked the program allows to create routes in which the legs are direct lines between the route nodes rather than following any roads. This is because sometimes you want to make a route but there are no roads or the small forest road may not be routable by google maps. In these cases it is nice for a motorcycle offroader, wanderer, mountain biker or the like, to be able to use direct routing (cause you may still wish to have a route leading you).

[routeconverter]

Feature wish: Tick box called "direct routing" or "disable auto-routing" or similar. With this box ticked the program allows to create routes in which the legs are direct lines between the route nodes rather than following any roads.

Hi JRThumb,

how about changing the Type: combobox to Track? It's meant to accomplish your feature wish.

[JRThump]

Feature wish: Tick box called "direct routing" or "disable auto-routing" or similar. With this box ticked the program allows to create routes in which the legs are direct lines between the route nodes rather than following any roads.

Hi JRThumb,

how about changing the Type: combobox to Track? It's meant to accomplish your feature wish.

Yes, I understand you and that is exactly how I want the route to behave with the tick box activated. But there is a distinct difference: A track is a track and a route is a route. The track is saved as a <trk> in the gpx whereas route is saved as <rte> and in the GPS it is treated differently. A track is more or less drawn as an overlay road. A trail of bread crumbs. A route on the other hand can be "activated" in the GPS so that the GPS starts pointing which direction to go, etc.

[routeconverter]

[..] there is a distinct difference: A track is a track and a route is a route. The track is saved as a <trk> in the gpx whereas route is saved as <rte> and in the GPS it is treated differently. A track is more or less drawn as an overlay road. [..]

I'm aware of the basics and decided to connect the rendering (as route, track, waypointlist) with the type of a position list to simplify the user interface. Since there only a very few formats (I just remember GPX) that can represent the type of a position list, most users can change the type of the rendering without thinking about changes of the data in the file. Currently, I don't have a good idea how to solve this without introducing more problems for typical users. At least there is a simple workaround for you: set the type to track before planning and change it to route before saving.

[JRThump]

Checked now and it seems that the .gpx never specifies how to do the routing, it merely specifies the order of the nodes and their position (lat/lon).

This means you're right and just switching to route mode to ensuer it getting saved as route solves my problem.

Thanks for pushing me in the right direction!