I have not updated my maps to the new map.
When I try to make a trip with way points, things get screwy. At first things worked OK. Then things went south.
To simplify, going from Bakersfield, CA to Arizona Charlies in Las Vegas. I input the way points and at first things showed in Vegas using the 146 at M casino then go E on 215 to the Boulder Hwy and up north to Arizona Charlies. Trip is by travel trailer.
At first it showed it correctly, then when I did inserted some way points, it sent me up to downtown Vegas and then back down S to AZ C. My way points were to Sams Town. I do a recalculate or optimize and it is the same.
Do not what I did. Anyone familiar with L V knows this is a big circle.
It will not go the shortest or quickest route.
Need help. Thanks.
Difficult to comment based on what you say. Are you able to attach some screenshots showing what you mean?
Note if you select Fastest or Shortest it affects the way your device calculates the route but it doesn't guarantee there isn't a faster or shorter route.
I have another mapping app that has that feature (outdated now)but I couldn't find the slowest or fastest on Base camp.
It did calculate the trip correctly only when I changed the mode of travel from a RV back to an automobile.
I have been on these highways/roads before and they are suited for all types of vehicles. Why it directed me way out of the way with an RV type of travel, I don't know.
It does calculate the correct directions now. Fastest and shortest.
Heads up to all and does anyone know what happened?
The restrictions would be stuff like height, width, length, and possibly the restriction of propane.
Not to mention the fact that directions for RVs, (and tractor trailers), take into consideration the overall length as it pertains to turning radii for intersections that may not be apparent to a car driver. There also may be restrictions on the vehicle type itself.
I found it hard to follow what you did so I can't offer much help as to what happened. But when you inserted way points, things got hosed up. Maybe the order that you put them in would affect the order that it wanted to take you to them? And so then it was trying to take you to each way point in a sequence you didn't intend or expect?
I agree with Mike. Look at the trip in Trip Planner in the GPS. There is a list of waypoints in the order to travel in. If they are not in the order you want, touch the up and down arrows to make corrections. Then save the trip before closing it.
I live in N/W Las vegas, but it has been years since I have gone to AZ Charlies on Boulder Hwy by the southern route, so my use of a Garmin there is rusty.
First, the mapping of N/B I-15 to Hwy 140 (At the M casino complex) is right. N/B on Hwy 140 to E/B I-215 is also correct. The next is take the exit for I-515 N/B and proceed north to Tropicana Ave. Exit Tropicana E/B to Boulder Hwy. Sam's Town will be first on N/B Boulder Hwy, on the east side and AZ Charlies is about a 1/2 mile further north.
Waypoints are a real problem with Garmin units. It sounds like one batch input waypoint you put in was near downtown (Fremont St area) that threw the whole waypoint thing off.
Can you list all of the waypoints you programmed in?
Also, road construction in town is at all time high levels. If you have traffic enabled, your Garmin may have rerouted you away from some traffic areas. I cannot see how with I-15 under complete reconstruction at the Fremont St. area. Project Neon has been a nightmare for the locals for years!
Thanks to all that commented.
The route was at M casino go east and onto 215 then hit Boulder Hwy and up north to Sames Town then north to Arizona Charlies. It could have been that there was construction but more likely some restrictions due to being in a travel trailer.
phranc and pwohlrob and might have figured that out.
Nothing beyond that and no downtown. Wanted to stay off I 515. I even inserted a waypoint on Boulder Hwy after I 515 to stay off the main freeway.
When one does a calculate or optimize, it should put waypoints in order.
What brought the trip back to reality and made things correct was when I changed from 'RV' back to an 'automobile'. Go figure.
I am speculating, but you may have attempted to force a route that cannot be driven by an RV for some reason such as passing under a low bridge clearance.
- Tom -
terms | privacy | contactCopyright © 2006-2020