Feature request - Route / Track transfer

I'm unclear what you hope to gain from this? What device are you thinking of using it on?

I'm unclear what you hope to gain from this? What device are you thinking of using it on?

The device I am using is an Oregon 300 - but this is not a device specific request, I think.

In terms of what I want to gain, here an attempt to explain it better:

If I generate a Route from Point A to Point B, BaseCamp autoroutes between these Points, giving me Route Direction Points in between. This Route (the path from A to B with its Route Direction Points) is specific to the selected Activity Profile.
But when I transfer that Route to my Oregon, it only transfers Point A & B (and not the direction points based on the autorouting).
I can recalculate the Route on the GPS, but it would not guarentee that the exact same path as selected by BaseCamp would be used - that is what I am missing currently.
Esp. as the GPS has not all the different Activity Profiles as Basecamp has. (I.e. When I use "Tour Cycling", I get the Route I want; but when I use "Bicyling", I get a different Route.)
A Route-to-Track-conversion option with track points only at each relevant point (the Route Direction Points - i.e. turn from street a to street b ect). would get me close to what I want - with trackpoints exactly (and only) at points on the trail where I need them - and not at a fixed intervall - which might skip a relevant turning point and has way to many on a straight path.

I hope this explains it better.
Any chance for this to be considered nearterm?

Thanks and all the best,
Heiner

Well that really wouldn't help you. Garmin devices are limited to the number of viapoints in a route and the number for most GPS is 50 and in some cases even less. Creating a 'route from a route' using the technique you're suggesting would create far too many viapoints and the route would fail on the GPS.

The device I am using is an Oregon 300 - but this is not a device specific request, I think.

In terms of what I want to gain, here an attempt to explain it better:

If I generate a Route from Point A to Point B, BaseCamp autoroutes between these Points, giving me Route Direction Points in between. This Route (the path from A to B with its Route Direction Points) is specific to the selected Activity Profile.
But when I transfer that Route to my Oregon, it only transfers Point A & B (and not the direction points based on the autorouting).
I can recalculate the Route on the GPS, but it would not guarentee that the exact same path as selected by BaseCamp would be used - that is what I am missing currently.
Esp. as the GPS has not all the different Activity Profiles as Basecamp has. (I.e. When I use "Tour Cycling", I get the Route I want; but when I use "Bicyling", I get a different Route.)
A Route-to-Track-conversion option with track points only at each relevant point (the Route Direction Points - i.e. turn from street a to street b ect). would get me close to what I want - with trackpoints exactly (and only) at points on the trail where I need them - and not at a fixed intervall - which might skip a relevant turning point and has way to many on a straight path.

I hope this explains it better.
Any chance for this to be considered nearterm?

Thanks and all the best,
Heiner

If when you create a Route you put in more points between A and B instead of only the two points they will transfer to your GPS and increase the chance of the route being the same in your GPS. The more points the better the chance it will be the same but as sussamb pointed out there is a limit.

With the Oregon can you create a new profile? I think you can with all Garmin's that use profiles, I know I can on both of mine. If so create a profile with the same routeing options you are using in BaseCamp.

Can you disable off route auto recalculate on the Oregon? If so disable it or set it to prompted. Unfortunately not all Garmin's have this option I'll never understand why. Without it the route you create in BaseCamp can change in the GPS and send you where ever and not where you told it to go.

This will all increase the chances the route will be the same on the GPS as it is in BaseCamp.

Well that really wouldn't help you. Garmin devices are limited to the number of viapoints in a route and the number for most GPS is 50 and in some cases even less. Creating a 'route from a route' using the technique you're suggesting would create far too many viapoints and the route would fail on the GPS.

That is why I suggested doing it via Track Points- there is a far bigger number of Track points allowed on the GPS than Route points.
In Case of the Oregon 300, it would be:
250 points per route, but 10,000 points per track!

Therefor, this would work - especially, as my suggested method would reduce the amount of trackpoints needed for a meaningful track / route.

What do you think?

Heiner

You need to decide what you want. You can already have a track. Routes are limited as mentioned. You cannot have track points in a route, your GPS doesn't work that way. So even IF Base Camp could do it there'd be no point.

?
I know what I want and I did not change that - I just restated / clarified what I asked for in the 1st post:
'I would like to have the option to generate a track, which consists of the generated 'Route Directions' Points '

I'm not sure you're listening though. There would be no point in doing so.

You'd only end up with fewer track points with straight lines between them that wouldn't match the route/track you were expecting :confused:

I can't therefore see anything changing.

I'm not sure you're listening though. There would be no point in doing so. I can't therefore see anything changing.

My friend, why the hostility?
('You need to decide what you want.' - 'I'm not sure you're listening though.')
This is not helping. I explained very detailed what I suggested and you did not come up w/ an argument that it would not be a beneficial add on.
But I see now that you are not a Garmin person, so asking you was anyhow the wrong addressee for s/w changes, I guess.

But when I transfer that Route to my Oregon, it only transfers Point A & B (and not the direction points based on the autorouting).

I am not near the expert on the inner workings of routes that others on this forum are, so I invite corrections to my comments. But I think part of the confusion here is that the premise as you stated above in an early post is, I think, not correct.

When you send a route that was defined in BC to a device, it sends much more than just the A and B points. It sends many intermediate points that define accurately the way that BC, along with any via points or shaping points you add, set up the route. So really, what is sent is already essentially what you are suggesting. Your device should faithfully follow the defined route unless it does an automatic recalculation. On many devices (I'm not sure about the Oregon), you can set "autorecalculate" to "off' and then it will not alter the route. It is common for users to set autorecalc to off just so the device does not change the route.

You can see this if you select a route that you created in BC, then export that route as a gpx file (export is on the file menu). then open the created gpx file with a text editor like wordpad. You will see many points in there listed as "gpxx:rpt". these are the points that define the route. Many more than just A and B, and more than just the route direction points. This allows the device to follow the route and generate the turn-by-turn directions, distance to next turn, etc.

So perhaps you can see that what you want is already there?