Routing

Unfortunately, there is no workaround for the problem you are trying to solve. As soon as you join a direct and an auto route, the joined route becomes a direct route. The only option is to keep it separate with some name prefix to help you identify which segment is which, for example, name the first route "1.AutoRouteToEndOfRoad" and the second route "2.DirectRouteFromEndOfRoad".

If there are more users who would like to add support for this feature to the BaseCamp wishlist, feel free to comment in this thread.

If there are more users who would like to add support for this feature to the BaseCamp wishlist, feel free to comment in this thread.

Yes please.

I have the same problem with Basecamp and TopoFrance!!

günter

If there are more users who would like to add support for this feature to the BaseCamp wishlist, feel free to comment in this thread.

Yes please. There was a discussion about it before and I thought that it was already in wishlist.
But again - this feature + ability to export in .tcx would be great addition for owners of EDGE series.

Regards, Ivan

RE: Routing

If there are more users who would like to add support for this feature to the BaseCamp wishlist, feel free to comment in this thread.

YES. I want this function yesterday!

I use Germany TOPO 2010. If a trail head ends 73 ft from a road (across a parking lot), BaseCamp will route you all the way back you came and around to that same point on the road because the map doesn't join the trail to the road. I have tried to overcome this with the "track" function and creating a partial route, but to no avail.

My curiosity obliges me to ask the question: why would someone design a program that cannot overcome the map? It isn't just BaseCamp (Google Maps is the same way in some cases). All maps are flawed and are never 100% up-to-date. BaseCamp engineers should believe consumers may know better where the roads and trails are. :D

BaseCamp has potential to be better than "very good". It could be "great"!

Moreover, what I can't figure out--if Garmin wishes to address issues with BaseCamp--why there is no function to create a "course" (.crs file) from a "route" (.gpx file). BaseCamp is virtually ideal for planning exercises, but you can't get those routes on your Forerunner XXX without using a third-party converter (http://www.gpsies.com/convert.do).

Are these "offroad" routes? If so, they will always be an issue. The routing calculations only know how to work with routing data in the map. So if most of the route is offroad, any time the route calculations need to find a way to get you from one spot to another, they'll do a "crow flies" shot to a routing data point in the map nearest one of the points, do routing on known map data to a point nearest the other point and another "crow flies" jump to that point.

By definition, "offroad" means no routing data. All of the "routing" that takes place offroad is just "crow flies" hops between user-created waypoints/markers.

If your routes are actually on roads with routing data in the detail maps, I apologize for the digression.

...ken...

A good example of bad routing using only a tracked route (route created from tracks)

There seems to be more to this problem than you posted Ken, I would expect that the behavior would be similar for all points on a track based route, for the entire route, if this were the only issue at play, but I'm not a software engineer and not trying to create an argument here just want to get the issue resolved so I can make better use out of My GPS and its capabilities. please dont take this as an attack, just as more niformation to help resolve the issue; so here is example of whyi think autorouting is not the only issue:

I have a route from a camp location in Utah, using both Tracks I have acquired on my own rides there, and using existing roads and markers based in the BaseCamp software. The issue I am seeing is while on a primitive road, or trail that may exist near a road, that BaseCamp wants to route me back to the road after each route-point, which in most casea are further away than the next route-point/waypoint on the route. However, once the road gets far enough from the route BaseCamp will follow the track/route until it presumably gets close to known routing info and then repeats the behavior. I have attached a pic of the specific issue as an example.

Definitely add a feature that allows the customization of routing to use both track/routes and roads/autorouting. I use this to determine how far a particular journey might be so I can adequately plan Fuel and food to safely return to base/camp.

Attachment:
The route Basecamp calculated is in Red, while the track based route is in blue: in my opinion/request Basecamp should chose the direct route to the next waypoint in the list, especially when the routing options are set to use "Shorter distance." You can see by the two highlited route points, that Basecamp is taking the long way when thats not the desired setting for the route as Ken Described, but then mamages to figure out how to follow the track route once far enough away from known routing data.



Hope this helps pinpoint and resolve the issue :)
-Pete
BaseCamp v4.1.0, but also experianced in v3.x.x

Unfortunately, there is no workaround for the problem you are trying to solve. As soon as you join a direct and an auto route, the joined route becomes a direct route. The only option is to keep it separate with some name prefix to help you identify which segment is which, for example, name the first route "1.AutoRouteToEndOfRoad" and the second route "2.DirectRouteFromEndOfRoad".

If there are more users who would like to add support for this feature to the BaseCamp wishlist, feel free to comment in this thread.

I think the ability to join routes with different 'routing', eg direct and any other, would be immensely powerful and be a vast improvement. How easy it would be to implement I have no idea :)