I can’t get on with Basecamp, I use tyre then convert to GPX files and download to my garmin, works great
Via the wise old sages at ukgser I’ve started having a play with Www.kurviger.de Early results are promising.
The problem I had with basecamp Is that if you do not pass exactly on top of a point on the route it recalculates for ever to take you back to that point even though it was as said 20 yards to your left or whatever. Before it used to do it for a short while and revert to route. Now there is a setting that transfers the route on device without the points I think but haven’t tried it yet
Sotos, there are several answers to this problem. First, the passing a waypoint problem is not basecamp, that is a combination of the settings on the device itself, the type of waypoint your using, and you not being precise with your placement. Zoom in on the map and correctly place the waypoints will help greatly. If you happen to drop a waypoint on the wrong side of a split carriageway (e.g. motorway or dual carriageway) it will likely try to turn you around to get to the other side. It is always worth checking the location of each waypoint. I appreciate you may well know most of the following, but its worth saying anyway just in case you don't. on the device itself: I strongly suggest you turn off auto recalculate, and use the screen to get you back on route (or select to manually recalculate if required). If you have a newer device (i.e. 390/395 or 590/595) then you can skip a way point with 3 button presses if you need to. This used to be the bain of my life if I overshot a junction, only to find it recalculate and take me off my intended route. Planning in general: I would also suggest you set most of the points to be unannounced, so they become shaping points, not waypoints. Just have an announced waypoint every 20 miles or so (this is important so you can start a route at a point along it, as it will recalculate to get you to the first point you choose). Announced waypoints show on the device with an icon (flag, whatever), shaping points are displayed as just a circle. There needs to be sufficient waypoints to ensure the device doesn't alter your route from that planned when it recalculates. This is especially important if you plan for shortest route on the pc but have the device set to fastest. More than once we have found ourselves heading onto an autoroute because we didn't have enough waypoints to keep us on the intended road Basecamp: I appreciate some people have issues with basecamp, but I am yet to find anything better. Once you get used to it, it works very well. I've lost count of how many miles on trips we've done using routes planned on a pc and uploaded to a zumo and latterly a 590. Most problems we have encountered are nothing to do with basecamp, and usually when we think we know best (i.e. force the route along an unmade road, or a road it doesn't want to route through only to find you cant get through due to no bridge, gated, private, etc) myrouterapp and Garmin: My mate with a tomtom used to use tyre, and now uses myrouteapp. If he shares a gpx with me it will not load without problem to the device, but will if loaded into basecamp first. This is because even myrouteapp doesn't generate a truly Garmin compliant gpx file, even their shaping points will get treated as announced via points. For the record, and without getting too techy, Garmin is not the issue here, it is what is being written into the gpx file. There are some nice features using myrouteapp such as being able to see how tomtom and garmin routing differs. It still doesn't (in my experience) create a route any better than basecamp though. One final thing. If you are sharing routes, it is worth making a trip log from a route, uploading that to the device, and setting it to displayed (I usually set the colour to red or blue so it stands out too). This shows you the route as calculated by your pc, and so you can see if your route is attempting to differ. This avoids lots of questions from your mates when their device calculates differently and they accuse you of not following what you said you were going to do Hope that helps.
I plotted my own route in Basecamp back from the Alps, I hit every waypoint and didn't get diverted once. I found the key to be adding the waypoints (or shaping points) about 2-3 miles on the road you want to take away from any major junctions and avoid any potential 'shortcuts'.
@John W - thanks for this tip, brilliant way of checking the route has downloaded and calculated correctly on the Sat Nav.
Thank you so much. Will give it a go. Most of my problems arise when choose two points say on the map and the route shown after does not use the road you had intended so use the” insert into route drag and drop function which ultimately gives a flag to the point included. Those are the points I was referring. Did not know you can skip a way point! Can you elaborate on this? Will try the no recalculation mode next time as well. Device is a 590
Steve, no problem. It has saved a lot of arguments, even when someone who is leading has shared their gpx. I can see their intended route regardless of whether my GPS chooses a different route, and when they deviate too. I did a trip with a guy who calculated route on pooter using shortest route, but had his tomtom set to windy roads. He wouldn't have it that we weren't on his route until he bypassed a road he really wanted to do Having more and better placed way points would have avoided this. Sotos, If you know you have passed the way point but it is still trying to take you back to it, it's easy to skip it. On the 590, bottom right, press the overlay menu button, one of the things on the menu is skip way point. Next to it is detour (I think,might be change route). If you click on this it will allow you to recalculate just the current section/leg of your route,up to the next way point. This is what I use should I need to force a detour. Personally I usually have the trip data displayed which is configurable. I have it display current time, time left to arrive, miles left, and display arrival time at bottom right of screen. Showing miles left means it is real easy to see if you have missed a way point,because the mileages starts to go up It is real easy to check the way points on Base camp too. Double click the route, select the checkbox at the bottom left of the dialog to centre on way point (or something like that) and then click your way through your way points to check they are correctly placed. Cheers John.
I often re-number my waypoints so that they come up in the correct order if I am searching through them. Of course you still need to know you have already passed Waypoint 4 and are looking for Waypoint 5 for this to work!
How sad - I do this too I name the waypoints with a date - order prefix (eg. 09-A: , with the destination always being Z). I also name the routes with a date prefix (my Zumo 660 listed route alphanumerically, on the Zumo 595 it doesn't, not sure what order they listed in. Having a date prefix helps as I delete wayoints and routes as I go along. I even do a turn list (road number / towns) in Excel, and highlight which are the numbered waypoints on the route. Even sadder Same here - I find it helps as I don't listen to the sat nav prompts.
I dont bother to number all the way points, but I do give those that are announced way points (not the shaping points) sensible names. So hotels will have their name and town, and petrol stations will say shell, esso, etc plus place name. The same is true for coffee stops. For me, the place name is far more valuable than just a number, as I can locate that on the map. Also if someone asks where is coffee or petrol I can tell them I do number the routes, using the date (e.g. 2806) plus location name from and too. I do the same for the tracks, preceded with a T. I used to split a days route up into morning and afternoon, but there is no need to do this now, since a route can be started anywhere along it as long as you have sufficient waypoints, and pick the next one to go to. I prefer to copy the routes etc to my media card, and only load them as required. In the past (a few years back now) I have had the device crash and bollix the route, so being able to reload it in this manner is invaluable. If necessary I can load a route, edit it, rename it, whatever. It also means I can share it with others if necessary. I too delete them (from the device, not the media card) after the day they have been used. This is for no other reason than having fewer to choose from, so I dont have to scroll the screen I know some people prefer the 3d view, but personally I prefer north up. This is the closest to a scrolling map, and when complex junctions are coming at you it is far easier to glance at the screen to establish which exit is needed. 3d is great in most cases, but for these complex junctions it can be confusing. I see others that use 3d having issues with these cases, especially if you get the wrong exit and then need to get back on route. If you touch the screen to browse the map it reverts to north up anyway, so that is an option. Do any of you guys use the garmin linked app. If you've not tried it, give it a go. I bluetooth my phone to the 590 and it gives me traffic information, so tells me of delays and options to deviate if desired. You can even bring up a weather map overlay too, so you can see where the rain is and avoid it I have my satnav linked to my headset too, and can make phone calls through the garmin (browse phone book etc) if necessary. You can also see the number of who is calling (or their name if in your phonebook). It looks like the old zumoforums is dead, but there is a new one - zumouserforums
On the way back from the alps recently I was riding solo and I tried linking the sat nav to my headset again to try and make sure I didn't miss a junction. However it buggered up my music streaming from the phone so I ended up deleting everything and relinking just the phone. I really need to investigate using the Ducati linking system...
If riding in groups, using shared routes then you need to agree to follow the lead rider without questioning every turn. With best will in the world there will be a setting on someone's say nav, or different make. One will want to go left, another right. End up at same destination though. Be aware some folk are just inept (or even thick as fcuk) at navigating, even with a pre loaded map.Dont let that person lead!! On longer planned routes, in say the Alps. I now split routes in to 3 parts. Then if a route has been bollixed up, it does not need to spoil the day. Don't forget paper maps and G maps though. Normal navigation methods do work!
Yep, we have the same. Using the displayed track though cuts all the crap. Hard to argue with that, and when there are rounds of beers at stake for u turns or deviations, it gets quite interesting
Actually caused the end of a good friendship. Had to decide that the leader - leads and is allowed and given time to stop and think and adjust. if help is needed leader asks..other wise followers, follow and STFU.
What I found odd was that even the Garmin's had various opinions on which road to take, wierd, and both were only a twelve month old.
Depends on what version of map is loaded, which routing preferences and avoidance you have set, so very easy for them to be different. We generally do follow the leader (unless they are clearly wrong,like getting on autoroute heading the wrong way), but it costs them beers when they don't follow their own route
On our last trip we were following a wonderful road up the Ballon D'Alsace. All of our sat nav's told us to take a road to the left, which got smaller and smaller and then very broken up. Finally after 10 mins we popped out back on the main road where we would have been if we had just gone straight on! I think the Sat Nav must have thought it would save us 5 seconds or 100m? I wish the route you carefully plan in Basecamp would just transfer over without 'calculating route' (or perhaps I'm missing something?)
If you have the same version of map, and the same preferences on both device and Base camp, it pretty much always calculates the same. The usual problem here is having the device set to shortest route, but pc set to fastest. We have been along some footpaths before now, and got stopped by a forestry warden in the alsace one year riding along a forestry track
