This site uses cookies to offer you a better browsing experience. Find out more about how to manage cookies, or dismiss this message and continue to use cookies.
Didn't get fastest route with Drivesmart 61
I just bought this and tested it. I put in a specific address I didn't know in a general area that I did. To get to the general area I would have used two freeways and it would have been 5 minutes from there. The Garmin had me take one freeway and then a long city street. I came back using my way and it was 10 minutes less than the way the Garmin took me. I had it set to fastest route with no avoidances.
Any way to make sure it actually uses the fastest route?
Any way to make sure it actually uses the fastest route?
Comments
Ditto.
It may have been taking traffic into consideration - as mentioned.
You can always look at the entire route in advance - and see it it makes sense. If you do this at night - when traffic might not be a factor - you can see if the device then changes the route as you drive.
That might indicate that traffic is being monitored, and adjustments being made.
The DriveSmart 60 has me turn right at the end of my road. Go about 1 mile and a half up the road past the side street to the pond, take a left onto a side street to another left onto a side street and then take a right back onto the main road. Go back down the same road about a mile and a half, pass my road, to take a right onto a side street, turn right onto a main road, turn right onto a side a side street and then turn left down to the pond.
I tried using Google maps and it gave both routes with the Garmin route as preferred. The second freeway does have traffic at certain times of day.
I tried using Google maps in the car. When I plug the phone or tablet into the car's usb, Android Auto starts and then freezes. I've also lost the connection using the phone unplugged. Just looking for something that will be reliable.
Not sure if this Photobucket link will work. I recently discontinued my paid subscription but I may have time left before they block my linking on sites like this. Either way, if this image shows today it may not tomorrow.
But I commented above on the crazy route the DriveSmart 61 (and previously the Drivesmart 60) wants me to take to a local pond. It's nuts.
Earlier Garmins and with earlier maps did not do this. My only guess is that they irroniously "updated the map" to make the obvious route a i way street BUT, I don't get that "YOU are goingthe wrong way up a one way roud notice. Or it could think that the road is blocked in that lane. Note that going home it does realize that the dorect route is the best.
It may have a short section of road incorrectly marked as one way, I have found/fixed several strange things.
The Here "mapcreator.here.com" allows you to analyse the roads and fix it yourself, then I find they appear in the next Garmin update.
On my DriveAssist 50, I get the same results as you - a convoluted route.
On my Nuvi 2595, I get a direct route from Tea Street to Pinewood Pond on Lakewood Drive.
https://imgur.com/a/xvJQn
But I feel vindicated. Do you have the same map version on both units? It does look like the 50 is interpreting the map differently as there is even larger disconnect at that corner on the 50 than it appears to be on the 2595. Perhaps it's a map interpretation issue?
As a note, although now dead, my 3590, which I think "thinks" pretty much the same as your 2595, did route that correctly. This problem first showed up on my Drive Smart devices.
FWIW, the routing engine in the Drive seems to think that Lakewood Drive is unpaved. So does the current version of BaseCamp (4.6.2) using default routing options.
To "solve" your problem and get a direct route, turn off the Unpaved Roads avoidance.
But there's more strange mapping stuff... HERE maps (wego.here.com) (which CNNA 2018.20 is based on) has only one Tea Street. Google Maps shows multiple Tea Streets off Decota Drive.
I've reported the problem to Garmin. Will post back once I get a reply.
https://imgur.com/a/kOE75
I'll see what happens if I turn the avoidance off but I probably wont keep it off. It's not like I really need the GPS to get to the pond.
I will say that while there are some unpaved roads right by the pond, Lakewood is completely paved and has been since I moved into the general area back in 1997.
And there are not two Tea streets for sure!
It's puzzling why the 50 won't route on Lakewood but the 2595 will.
The multiple Tea Streets could just be a red herring. I mentioned it just because Google seems to have issues with that area too.
Wildwood Ave appears to be unpaved. It's almost as if the unpaved attribute is spilling out to the corner of Lakewood Drive.
crazyfingers you can report it here:
https://support.garmin.com/faqSearch/en-US/faq/content/pJLZBzPen9A7OXw5vlRyu5