Mac/Windows Software

Basecamp Windows basecamp mapping errors

basecamp mapping errors

Former Member over 13 years ago

I'm not sure if this is the best forum for this, but it's the best I could find.

I'm using Basecamp 4.0.1 with citynavigator 2013.2 and I have found numerous problems with the maps, particularly in the Sierras around Lake Tahoe and Yosemite.

For example, I wanted to map a ride coming south on highway 395 to 89 to 4 and on west. But the software doesn't let me route on highway 89. If I set a waypoint anywhere in the eastern third of 89, then the next anywhere along 89 near it's junction with 4, the software refuses to connect them via the short route of highway 89 and instead creates a 50+ mile circle around to the north. This is just one example I've found in this area. I've had similar problems with several other highways near here as well as in other western states, so I assume the problem isn't limited to just this area.

These aren't small or new roads. They are substantial, long established highways. I could understand if they were tiny gravel two-tracks and I had a prefernce set to avoid gravel, but in this case I can't understand what the problem is.

I run the maps on a Montana 650T and of course have the same or worse problems with route building on it.

Is this an error in the map database or something I've set wrong? I'm new to basecamp and find it rather infuriating as the user interface is anything but simple/intuitive (God help me for saying it, but they could take a lesson from Apple or Google here) so I suppose there is something I've missed that is making it chose to route me so far out of the way.

Any suggestions? Other people seeing these errors?

Thanks.

Here's the example I'm speaking of. Only two points, start and finish, are defined. Yet it routes me in a huge out of the way loop.

0 Former Member over 13 years ago

https://my.garmin.com/mapErrors/report.faces

0 Airwolf65 over 13 years ago

I tried to create the same route as you and got the same results. But, from there I went to the toolbar, selected the insert tool and clicked on any section of your route to get the rubber band, then clicked on a section of route 89 between your start and stop points. I was left with what I believe was your intended route. I hope I explained this in a way that makes sense to you.

Cheers,
Dave

0 Former Member over 13 years ago

I tried to create the same route as you and got the same results. But, from there I went to the toolbar, selected the insert tool and clicked on any section of your route to get the rubber band, then clicked on a section of route 89 between your start and stop points. I was left with what I believe was your intended route. I hope I explained this in a way that makes sense to you.

Cheers,
Dave

Thanks, that did work. Now I need to figure out how to do that on the Montana. When I first ran into this particular glitch I didn't have a computer with me and was doing it from the GPS. Despite trying to set many waypoints along 89 I still couldn't force the route I wanted.

Jbarge, thank you for the link. Reported.

0 Former Member over 13 years ago

Does that road have any special routing attributes like unpaved or closed in winter? Have you tried using different profiles (walking, bicycle, motorcycle)? Have you zoomed in to confirm that there are no breaks in the route, or avoidances set?

Just tried to route over 89 from between the intersection of 4 and 89, and 395. It worked with hiking profile and motorcycling profile, but got the pictured results with the automotive profile and something similar with bicycle profile. Routing attributes for that road segment must be really weird.

0 Former Member over 13 years ago

I HAVE had this problem many times, both with BC and MS, and have had to force the route I wanted to make with dozens more intermediate waypoints than should have been necessary. I gotta figure out how to work this rubber band thing to see if that works next time I have the "issue."

My conversion from a Quest and MS to a Nuvi 2455 and Basecamp has been tedious and has taken most of six months, but I think I'm about there. Now just going through these forums to learn as much about it as I can. Very helpful after working with MS for 10 years -- old dogs, new tricks and all.

0 Former Member over 13 years ago

My belief is that it is related to the profile settings. I've had similar results and in one case discovered that there was a 1 mile unpaved section (at least on the Garmin map) and my (motorcycle) profile said paved roads only. Another time the 'obvious' route went across a river, either bridge or ferry - which had a toll, and my profile said 'no tolls'. I have ridden many times in the area that you mentioned (88, 89, 4, 395,etc) and am not sure what characteristic (other than snow) the road might have had.
-ceej