I can't understand why Garmin has done this, Google too.
I create routes in an online program called RV Trip Wizard. I export the route as a .GPX file and import it into Base Camp. Base camp accepts the route as a track exactly as I created it in RV Trip Wizard. I convert the track to a route and send it to my Garmin RV 660 GPS. So far so good.
However when I try to navigate the route I imported to my GPS, the GPS recalculates the route based on the parameters (fastest time) and avoidance's (no U turns, no toll roads, etc) completely disregarding the route planning I did in RV Trip Wizard. It doesn't matter if I created the route in RV Trip Wizard or Base Camp, my GPS simply takes the beginning and end points and recalculates a route between them.
Google Maps does the same thing.
The only way around this that I have found is to create sufficient turn points (waypoints) in Base Camp to define the route which will force the GPS to navigate from turn point to turn point, but still using the parameters previously set into it. If enough turn points are created the resulting route the GPS will follow will closely resemble the desired route I created in Base Camp.
This seems like way to much work. Am I missing something???
No. Any route sent that is created on a different map will be recalculated on your device. The way around it is as you've discovered. Use BaseCamp to plot an identical route inserting viapoints as necessary so the BaseCamp route follows the route you want. When you do this ensure the map BC is using is the same as the one on your device, and with identical avoidances etc. All should then be well but worth checking it matches exactly if that's important to you.
You just re-invented the wheel.
It's maddening that different devices will calculate a different route for the same points. If I use BC, I expect the route to be calculated just the same on the GPS. Is that too much???!?!?!?!
It probably is. Think of it this way. Any device calculates the route based on its own algorithm. This algorithm has changed over the years is response to user feedback and other stuff so that there are numerous routing algorithms on numerous devices. BaseCamp has a routing algorithm that may or may not match your particular device, and won't be the same as any third party's algorithm. Now add in different maps each with their own nuances and errors. So while BaseCamp may come close at times there's no way it can get it right 100% of the time
So what's the use in using Base Camp? I can go to a lot of trouble creating a route in BC, but my GPS completely ignores it.
For example I want to go from Alvarado, TX to Mineral Wells State Park in Texas, about 62 miles. BC routes me through Ft. Worth where there is a lot of construction. I use the insert tool to modify the route to take me south of Ft. Worth. All looks good.
I transfer it to my Garmin RV 660 GPS. On my GPS I Select "Where To" > "Trip Planner" > then select the route I created in BC. I select "Go" then select "OK". The GPS starts calculating and displays pretty much the same route BC did before I modified it.
So my question is "Whats the use in creating routes in BC if you can use them to navigate"?
I use basecamp and create waypoints to force the route. I export as GPX and the import into Extra POI Editor.
I open each point on EPE and fine tune it to make sure it's in a good location and on the right side of a divided highway.
I download points into my GPS and then add each waypoint into Trip planner.
A bit tedious, but it worjs for me.
Mostly I find you can. I rarely have to adjust a route but when I do my GPS generally follows it. What helps is ensuring the routing options and avoidances in BC are as close to those in your device as possible. If for example one is set to avoid highways and the other isn't then it's unlikely the routes will match.
I think the problem may be in how you define the route change. Are you certain the RV660 understands a shaping point vice a waypoint?
First in the example above creating a route from Alvarado to the State Park, I used shaping points to modify the route in BC. Downloaded the route into my GPS. GPS ignored the shaping points and recalculated the same route BC did before the shaping points.
Second, I created way points using the waypoint tool in BC to force the route I wanted. Downloaded the route to my GPS and got the same results - GPS ignored the way points.
A previous posted said he downloaded waypoints he created in BC to his GPS and created a route in his GPS using the downloaded way points. My GPS is updating maps and software right now so will try that when I'm done.
Guys, this is really stupid. I can't believe you can't create a route in BC and expect it to be recreated in your GPS. Especially if both BC and the GPS are up to date with current maps.
I used Homeport in my boating days and it was seamless to download the route created in Homeport and have it recreated exactly the same way on the GPS.
That's slightly different. Roads aren't the same as water. If you're using the same map and if your BC and GPS settings and avoidances match you should get a similar if not the same route. If not you have something wrong somewhere. Have you looked at your avoidance and route settings in BC?
One thing I always do after sending a route to my device, and after I've viewed it on my GPS, is to reconnect my GPS to my PC and look at the route in BC. By selecting different colours for it and the original route I can then quickly spot any issues, but I repeat again generally they match.
I'm not an expert here and maybe I'm missing something but I don't understand all the confusion about this.
I create my routes in BC Trip Planner, save them and export to my 3597 and RV760. I then select the route on the GPS. I don't ask the GPS to do any recalculating.
It's possible I've just been lucky but in the dozens of times I've done this, the route on the GPS is always identical to the one created in BC.
I realize the GPSr has to be compatible with Trip Planner for this to work. BC and the GPSr must also have the same installed map.
terms | privacy | contactCopyright © 2006-2022