I created a route a few days ago with no problems. Today I went back to that route as I wanted to edit it. I alt clicked on a point to move it but then the program started to recalculate and sent paths all over .the place. Had to undo to restore. What is the problem here and what is the solution?
Did you have the same map selected? Same activity profile? I suspect one or the other or both are different. If that doesn't resolve it can you post a screenshot or describe in detail what the problem is?
Funny as it has stopped occurring now.The profile that I am using is hiking, because that is correct for the activity. However should I just leave it as direct. When the problem reoccurs I will post a screen shot
Hope this of some help. It started again after I had connected my Oregon 600 and tidied up some files All that I did was to edit one point and the program started to recalculate and create all of the extra paths
Well I can see what's happening. Your original route comprises straight lines, but you've selected hiking activity and a routeable map, so the minute you change part of the route it's recalculated. As the map can only route along roads etc set as routeable in its data where there are points off those roads it draws a direct line from them to the nearest road point.
You need to set activity to direct and then amend the route. Incidentally where did the original route come from?
Just had a look to mention that this happens on two other pcs as well, and am glad that you know what the problem is.
However I do not understand.
The route was plotted out by myself on a map in Basecamp. The activity is set to hiking because that is what I am doing. I plot the points along the footpaths and the program makes straight lines between them. There are very few roads roads, mainly footpaths.
Do you mean that the program is making readjustments to roads, but as I see it, it is recalculating backwards and forwards to arbitrary points on the map.
Why can I not select hiking when that is my activity.
What do you mean by a routable map? This is the map that is in Basecamp that I created.
Thanks for your help
Garmin makes use of two types of routes – Automatic and Direct.
Direct Routes go directly from one user point to another. This type of route can be made on any map.
Automatic Routes must follow routable features (i.e. roads and on some maps paths as well) between user points. So, if you have two points that are not on a routable feature, then BaseCamp will find the nearest routable feature that will get closest to both points and follow that feature rather than making a straight line connection between the two points. Following routable features requires a map with these features. The Global Map in BaseCamp does not have these features. If an Automatic Route is made on a map without routable features, it will create a Direct Route in BaseCamp by default.
Garmin uses Activity Profiles to determine the type or route (Direct or Automatic) AND to pre-set parameters for Automatic Routes. The Direct profile is the only profile for Direct Routes. All other Profiles are for Automatic Routes. As mentioned above, the profiles will pre-set parameters to aid in selecting a route. For example, an RV should not be on a hiking trail and a hiker should not be on a major highway.
These pre-sets may or may not be best suited for a particular route and you are free to use a different pre-set profile (e.g. Driving make work better than Motorcycling at times) or create one of your own.
Just been playing around and find that this problem only occurs when my garmin oregon 600 is attached, so when editing I will make sure it is not connected
Well it's not that causing the issue ... Unless of course the map you're using is coming from your Oregon and that without it connected the map you use is not routeable, so BC cannot recalculate the route.
As already said, with your Oregon connected or not, if you select either the direct activity or a map that isn't routeable you won't see what you're seeing.
Ok I have solved the problem.
All I have to do is to make sure that the map selected to display in Basecamp when editing is not routable and then the problem does not arise.
When just working in Basecamp without the device attached all that I have is the Global map plus the OS overlay, and I make sure that is what I have when editing when the device is attached.
Ok I have solved the problem. All I have to do is to make sure that the map selected to display in Basecamp when editing is not routable and then the problem does not arise.
I wouldn't go that far, it's what I and others have been telling you ;)
and as posted above you can either do that or just select Direct activity.
