Best Route Calculations Sometimes Incorrect

 

I absolutely love my Garmin unit. The one drawback I have noticed is that the software does not calculate the time travel on Streets or Highways with lights as well as it does on highways. This causes a problem when it is deciding which is the best route because it puts me on more local type streets sometimes rather than a slightly more circuitous highway route that ends up, because of the constant speed, being faster. Is there any way to let Garmin know they have to adjust more time for routes with traffic lights? They cannot assume all the lights to be green and just calculate the presumed time it will take to travel the route by the speed limit of that particular road. And if they are allowing time for red lights it is not enough.

Mostly bang on target

I have found my nuvi 660 almost bang on target.....I have used it many times across states and have found it similar to the routes planed through Google or yahoo...

Check your preferences

Are you set to "Shortest route" or "Fastest"?

If you are set on shortest, that is exactly what you get.

--
*Keith* MacBook Pro *wifi iPad(2012) w/BadElf GPS & iPhone6 + Navigon*

I am taking about a trip of

I am taking about a trip of 30 miles that is all highway or the alternative is 4 miles shorter but goes through routes that have a similar speed limit but lights. The Garmin will send me on that path and more often than not and it just does not end up being shorter time wise.

I notice this also because the time of arrival is usually correct when it is mostly a highway route but almost never correct when it is a route with lights.

I have found that.

sulkyracer wrote:

I absolutely love my Garmin unit. The one drawback I have noticed is that the software does not calculate the time travel on Streets or Highways with lights as well as it does on highways. This causes a problem when it is deciding which is the best route because it puts me on more local type streets sometimes rather than a slightly more circuitous highway route that ends up, because of the constant speed, being faster. Is there any way to let Garmin know they have to adjust more time for routes with traffic lights? They cannot assume all the lights to be green and just calculate the presumed time it will take to travel the route by the speed limit of that particular road. And if they are allowing time for red lights it is not enough.

My Gamin quite often gives a route that I know I don't want to take at that time of day, so I go the way I know is quicker and it adjusts along the way. I think the gps knows the speed limit and assumes you can drive that fast, with no considerations for traffic, lights or other things that might slow your progress…..

--
It is terrible to speak well and be wrong. -Sophocles snɥɔnıɥdoɐ aka ʎɹɐƃ

fastest vs shortest

I've run into a similiar problem as you've described. If you know this is happening, just continue on the route you prefer and the unit will adjust to your new route. I guess this is one of those quirks in route calculations. Fastest always seems best from my experiences.

gusb

--
augie billitier I2,c330,660

Is your gps set for shrotest route?

sulkyracer wrote:

I am taking about a trip of 30 miles that is all highway or the alternative is 4 miles shorter but goes through routes that have a similar speed limit but lights. The Garmin will send me on that path and more often than not and it just does not end up being shorter time wise.

I notice this also because the time of arrival is usually correct when it is mostly a highway route but almost never correct when it is a route with lights.

Then that is why you are sent the shortest not the fastest way. Change the setting to fastest...

--
It is terrible to speak well and be wrong. -Sophocles snɥɔnıɥdoɐ aka ʎɹɐƃ

My nüvi 650 is set at "Faster Time"

aophiuchus wrote:
sulkyracer wrote:

I am taking about a trip of 30 miles that is all highway or the alternative is 4 miles shorter but goes through routes that have a similar speed limit but lights. The Garmin will send me on that path and more often than not and it just does not end up being shorter time wise.

I notice this also because the time of arrival is usually correct when it is mostly a highway route but almost never correct when it is a route with lights.

Then that is why you are sent the shortest not the fastest way. Change the setting to fastest...

Dear A,

My nüvi 650 is set at "Faster Time". When I leave for work early in the morning (little traffic), the unit always indicates that the trip will take ten minutes. The trip takes 16-20 minutes and is through the streets of Brooklyn. Coming home takes half an hour. This causes me to wonder whether my unit may not be good at calculating driving time on city streets.

david

--
nüvi 1490T, V1, Sanyo PRO-700a, maps, sunglasses, hot co-pilot, the open road

.

To the OP, it's important to understand that the GPS unit doesn't "know" anything about traffic (notwithstanding units using a traffic receiver) or lights. So it won't take these into consideration at all when planning a route.

The information in the database contains average traveled speeds of different classes of road types.

It uses this information along with the preferences that the user has chosen to attempt to calculate a mathematical solution corresponding to those parameters.

It is not designed to give the "best" route only the fastest time or shortest distance in accordance with the data it has.

The map data comes from Navteq not from Garmin for the most part, however, since traffic and lights are constantly variable, it's unlikely for them to be included in the map data for individual street segments.

Drive time

davidwynyard wrote:

This causes me to wonder whether my unit may not be good at calculating driving time on city streets.

I don't "wonder" about it at all. There are too many unknowns involved. It is not just "your unit" but all of them....unless maybe you have "live traffic" capability.

Some brands may make different (better?) assumptions about city streets but none are really accurate.

Do any of them "adjust" the arrival time as the trip progresses? That is, if the original estimate was 30 minutes and 15 minutes later, you have covered less than 1/4 of the trip, does it UP the ETA.....by more than the remaining 15 minutes ??

I've never been in that situation to test mine.

--
Magellan Maestro 4250// MIO C310X

This exact problem is being

This exact problem is being addressed in a GPS unit that will be coming out in the near future. Each unit will share data with the a sattelite so you will know exactly what the drive time is through an area. The more units in that area the more accurate the info. I cant wait for it to come out and everyone to get one. As opposed to the unit telling you there is traffic you will know exactly how slow it is moving.

The ETA does adjust during the ride to work.

ka1167 wrote:
davidwynyard wrote:

This causes me to wonder whether my unit may not be good at calculating driving time on city streets.

I don't "wonder" about it at all. There are too many unknowns involved. It is not just "your unit" but all of them....unless maybe you have "live traffic" capability.

Some brands may make different (better?) assumptions about city streets but none are really accurate.

Do any of them "adjust" the arrival time as the trip progresses? That is, if the original estimate was 30 minutes and 15 minutes later, you have covered less than 1/4 of the trip, does it UP the ETA.....by more than the remaining 15 minutes ??

I've never been in that situation to test mine.

Dear DT,

The ETA does adjust during my ride to work. As I warm the engine in front of my house and look at the GPSr, I know to add ten minutes to the ETA so that I know I have time to reach work without rushing. I have adapted to the unit's idiosyncrasies.

david

--
nüvi 1490T, V1, Sanyo PRO-700a, maps, sunglasses, hot co-pilot, the open road

Travel Time Accuracy

If you know that the POSTED Travel Time on the GPS is off because of unknown traffic problems. Like actual speed or red Lights or traffic itself, just make it a habit to give you enough time for these road blocks.

The GPS is only a tool, to be used as a tool. If you know that the driving time is going to be off, then adjust the start time accordingly.

I drive at least once a week from Cecilia Ky to Louisville Ky, about 54 miles. I don't like using I65 because of the truck traffic and accidents. So I travel US31w. I have about 13 traffic lights for the first 30 miles and at least 25 within Louisville and depending on the time of day there could be a lot of going to/from traffic. The ETA is only off about 3 to 5 minutes most of the time. Sometimes I even beat the ETA by a few minutes.

Sure you might even show up at your destination a few minutes early. But would that really hurt? You might even not miss a flight!

It is just like back in the days when I was still working. Fellow employees would time there drive to work. Say they could make the trip from home to work in 35 Min in good driving conditions. On bad weather days they would always be late and use the excuse the weather caused them to be LATE.

NOT TRUE! You have to anticipate some problems and adjust accordingly.

I know someone out there will say well what about the time that HE/SHE was stuck on the freeway for 4 hours because of an accident just ahead of me and I had no way to get off.

You can't anticipate everything all the time. So some excuses are valid.

But waking up in the morning with snow on the ground and still leaving exactly 35 minuets is not exactly using common sense.

--
"Those that stop and smell the roses, must realize that once in awhile you may get a whiff of fertilizer."..copyright:HDHannah1986 -Mercedes GPS - UCONNECT 430N Chrysler T&C - Nuvi 2598- Nuni2555 - Nuvi855 - Nuvi295W - Nuvi 750 - Ique 3600

Common Sense

H Hannah wrote:

But waking up in the morning with snow on the ground and still leaving exactly 35 minuets is not exactly using common sense.

Reading H Hannah's great reply reminded me of an email my wife received a couple months back. Here it is:

My parents told me about Common Sense early in my life and told me I would do well to call on her when making decisions. It seems she was always around my early years but less and less as time passed by.

Today I read her obituary.

Please join me in a moment of silence in remembrance, for Common Sense had served us all so well for so many generations.

Obituary: Common Sense

Today we mourn the passing of a beloved old friend, Common Sense, who has been with us for many years. No one knows for sure how old she was since her birth records were long ago lost in bureaucratic red tape. She will be remembered as having cultivated such valuable lessons as knowing:
When to come in out of the rain,
Why the early bird gets the worm,
Life isn't always fair,
And maybe it was my fault.

Common Sense lived by simple, sound financial policies:
Don’t spend more than you earn.
And reliable parenting strategies.
Adults, not children are in charge.

Her health began to deteriorate rapidly when well intentioned but overbearing regulations were set in place:
Reports of a six-year-old boy charged with sexual harassment for kissing a classmate.:
Teens suspended from school for using mouthwash after lunch.
And a teacher fired for reprimanding an unruly student, only worsened her condition.

Common Sense lost ground when parents attacked teachers for doing the job they themselves failed to do in disciplining their unruly children.

It declined even further when schools were required to get parental consent to administer aspirin, sun lotion or a sticky plaster to a student, but could not inform the parents when a student became pregnant, and wanted to have an abortion.

Common Sense lost the will to live as the Ten Commandments became contraband; churches became businesses; and criminals received better treatment than their victims.

Common Sense took a beating when you couldn't defend yourself from a burglar in your own home, and the burglar could sue you for assault.

Common Sense finally gave up the will to live after a woman failed to realize that a steaming cup of coffee was hot. She spilled a little in her lap, and was awarded a huge settlement.

Common Sense was preceded in death by her parents, Truth and Trust; her husband, Discretion; her daughter, Responsibility; and her son, Reason.

She is survived by three stepbrothers:
I Know my Rights
Someone Else is to Blame
I'm a Victim.

Not many attended her funeral because so few realized she was gone.

If you still remember her, pass this on.

If not, join the majority and do nothing.

--
Tampa, FL - Garmin nüvi 660 (Software Ver 4.90), 2021.20 CN NA NT maps | Magellan Meridian Gold

RE: Common Sense

My favorite anonymous quote: "Common sense is an oxymoron."

--
*Keith* MacBook Pro *wifi iPad(2012) w/BadElf GPS & iPhone6 + Navigon*

Life is hard to predict

It's hard to calculate traffic lights into the equation. Don't really know if your going to hit a redlight or not. I figure in about 4-5 extra minutes onto the time if the driving distance is 5-8 miles in the city. It will be cool when the future garmin units relate travel info to each other to let you know of traffic slow downs better than the current MSN info.

Faster vs shorter vs optimum route

It would be nice to have a third choice of routes. Make an algorithm that would select an optimum route if it saved more than x% of the total miles if it costs less than y% increase in time. I recently plotted a route using faster that was 55 miles and 42 minutes. By forcing a via point I had the Garmin recalculate my normal route which came out to be 45 miles and 43 minutes. I will gladly take one more minute to save 10 miles.

My options for a trip tomorrow are:
Faster - 79 miles and 1:29
Shorter - 66 miles and 1:34

So I will take the shorter route but there may be better routes. Just don't know.

--
Larry ... Garmin Nuvi 650