I don't think so. If you have avoidances checked and traffic checked in the submenu, if the traffic problem exists at the time of initial routing, it will be included, just as avoid u-turns or any of the other choices for avoidance. The easy way to find out if something like this is going on is to do the same route in simulator mode and see what happens.
I'd like to try this a few more times, but it seems to prove that Garmin isn't allowing for any stop time on local/city streets.I agree in principle, but not precisely. There is an implication that the road database doesn't take these things into account. That isn't really correct. They do try to take those things into account. Now if they get it right or not for each road classification/type is another matter-- and likely what you are seeing. But I'll just nitpick on the wording so we don't get any rumors started.So based on what you describe, the GPS thinks you will transit the stretch of road faster than you actually likely will. This is a bit different than saying the GPS expects you will hit every light green. While the net result is similar (actual drive slower than projected) the same could be true for any type of road.Try this. Run a simulation and see what speed the GPS puts you at for those roads. If it is below the speed limit there is some type of allowance for traffic and lights.I mapped a route on Brown Deer Road in the Milwaukee area between Interstate 43 and Hwy 45. This is a city street with a number of stop and go lights. The posted speed is 40 about half of the way and 45 the other half. Garmin says it is 8.8 miles with a time of 11:48. 11:48 is .197 of an hour. 8.8/.197 = 44.7 miles per hour. Obviously Garmin is not considering stop lights at all on this route. As reference, Bing says 9.2 miles and 16 minutes (about 35 mph).
I'd like to try this a few more times, but it seems to prove that Garmin isn't allowing for any stop time on local/city streets.
Try this. Run a simulation and see what speed the GPS puts you at for those roads. If it is below the speed limit there is some type of allowance for traffic and lights.
Is this what it did?
Is this what it did?That route has a via point in South Orange (the white circle on the route), so it makes perfect sense. Drag the via point onto I91, and the route changes to what you'd expect: this.
I thoght only my Nuvi goes crazy, insted of going straight it makes me go in circles :evil:
I totally agree. Again maybe I'm missing something but I can take a 255 with current firmware and maps and a 1350 with current firmware and maps (all preferences identical) and prove that one routes me to Chicago via HWY 41 and the other via I-94. Both using 'fastest time' opton.What more do they need?Mike
I have seen this a couple of times too. The Garmin will calculate the "fastest route", but I'll stay on what I know to be much faster and the estimated time will drop as soon as it recalculates. I sure wish I would have known how poor the Nuvi's route calcualtion routines were before I bought it. And...it doesn't seem that there are enough people complaining for Garmin to do anything about it. I'm seriously considering trying to sell mine and move to a TOMTOM. I'd feel bad for the poor sucker who bought it though :)
His statement made me giggle, but soon realized he might be correct.
Since there is not solution for this issue yet - you think TomTom or any other GPS is better and does not have this issue?
Does anyone know how to bring this problem to Garmin's attention? I doubt our comments here will have any effect in getting a fix.
I sure wish I wouldn't have believed all of the glowing reviews I read about the 765T before I bought it. I have to wonder if Garmin paid to have them written.
Guaranteed that doesn't happen here :)
If I could just figure out how to get Google map routes into my 765T I would stay with it. Google maps are right on the button as far as route planning. But of course their maps are from TeleAtlas and not Navteq.
Even if there was a way to transfer routes from Google, you need to realize that the only thing that gets transferred to a nuvi when you import a route is the start point, finish point and any waypoints or vias you set explicitly. The nuvi always recalculates the route using it's own routing algorithm. So you can get the exact same results by setting the same waypoints manually on the nuvi.
Absolutely! So what is that we can do to get their attention?
Absolutely! So what is that we can do to get their attention?The most obvious one guys, don't buy garmin! But I doubt seriously that's gonna happen. Especially since I went in to Best Buy one day and wanted to know what they knew about GPS's, which is not much, but they seemed to be pushing Garmins. They had TomToms and Magellan's, maybe a few more. But they didn't know all that much.So it's kinda the blind leading the blind.
For those not familiar with the area, Brooklyn (Kings County) and Queens County along with Nassau and Suffolk counties are part of Long Island. The is no town, village or city named Long Island, NY.
Has anyone here used a slightly older Garmin such as 760?