Routing with Basecamp problem

Routing really depends more on the map and less on BC. If you are asking BC to autoroute on a map then it can only route along the roads etc that the map has as routeable.

The good news is that the newly released BC beta allows a mix of profiles on a single route, so you should be able to use direct routing on those sections that don't do what you want.

A related issue: Regardless of the activity profile used, point-to-point routes uploaded to any of my several Garmins all follow the same route, specifically the one using the "Driving" activity profile using all of the default settings therein. So: What's the point of having different profiles if they all produce the same route when uploaded to a device???

As SUSSAMB already said routes are more a function of maps--specifically the route data they contain. Garmin's map format is NOT open although it has been reverse engineered so 3rd party maps are available. That said those may not contain the same routing information as Garmin's own maps. Also different Garmin maps contain varying amounts of routing data.

BaseCamp and individual GPS models simply use routing algorithms using the data maps contain.

If you want your nuvi to follow a point to point route you need to set it to 'off road'. At the moment if you send a route to your nuvi it will recalculate it based on the settings on the GPS. I understand (although not verified yet) that the 2013 models will not auto-recalculate routes sent from Basecamp.

Hi, I hope someone here can help with this problem and forgive me if a solution has already been posted, though I've searched and not found one.

I'm planning a route with Basecamp using a cycle touring profile but I've used the walking and MTB profile too with no luck. When using the route tool I'm often sent on a big detour from the route I have clicked on even when I've clicked on points just a few hundred yards apart. I'm using maps I downloaded from Openfietsmap and most of the time it works quite well. I feel sure there must be a solution to this.

Cheers

Try a different process to shape your route where you want it to go.
I set my begin WP1 and end point WP2 first and see what I get.
If part of the route is good I set WP3 at the start or end of the good part leaving the bad part isolated between 2 waypoints, WP1-WP3 or WP3-WP2.
If none is good I set WP3 in the middle on a road I want to take and recalculate to see what I get.
I keep moving that WP3 until part of the route is good leaving the bad part isolated between 2 waypoints.....etc.
This method has worked well for me and uses the least number of waypoints.

I also use the exact same map on my computer as I have in my gps so when I send my new route to my device I get the same route as long as the gps has the same routing properties as the computer. I use either car/motorcycle or truck settings.

I'm planning a route with Basecamp using a cycle touring profile but I've used the walking and MTB profile too with no luck.

For the Openfietsmap in Basecamp, you need to use the driving/car profile instead of cycling: http://www.openfietsmap.nl/tips-tricks/basecamp-nl

Thanks All, I'll try your suggestions. Wish me luck!

Cheers

The problem comes when I transfer those routes to my GPS. On the GPS the routes are back to the shortest/fastest route between points. Am I doing something wrong here? As GERRITO put it earlier "What's the point of having different profiles if they all produce the same route when uploaded to a device???"

I like the way Basecamp works for what I need it to do, I'm just trying to get the routes I create in Basecamp to appear exactly the same way when they are uploaded to my GPS. If I have to upgrade to a new GPS and/or map version, I'm willing to do that (it is about that time anyway) I just don't want to throw money at the problem if that's not going to fix it.

Can anyone help?

Unfortunately your 785 like most nuvis will recalculate the route sent to it. Whether this will be different from your Basecamp route will depend on things like whether the same map is on both, and how closely the routeing and avoidance settings match bewteen the two. You may have to do some experimentation to get the best 'fit'.