just finished a 250 mile RT from SF Bay area to Sacramento
traffic showed in navi the whole time

However, the route time did not reflect traffic congestion as I had hoped or as in previous RL. I knew from radio traffic reports that there was significant congestion nearing SF on west 80 heading to Bay Bridge as well as all the way over Bay bridge. I could scroll on the navi and see that it showed solid red for that stretch. However the route time (with my route going through that area) was showing no delay. It was not until I got within 20 miles or so of the actual delay that the time started to increase. I ended up rerouting around that area, but seems to me route time should have adjusted well in advance of getting that close.

 

Did the same RT last week
The estimated time based on route traffic is worthless. As previously stated, it does not up date until you are too close to traffic to really do anything about it. Furthermore, it does not really update much. I sat in stop and go traffic for 15 minutes. Estimated time changed only 1 minute during this entire segment.

 

I agree with you. It doesn't update soon enough.

I've been stuck in traffic more than once when the route still showed green hashes.

If you check Traffic Incidents, does it force a refresh? I did that once recently and when I got back to NAV it showed some changes.

 

The strange thing is that the route showed red and I was in the middle of the red, but the time remaining did not account for the red traffic

 

after more trips, I'm more and more convinced the estimated time remaining does not factor in the traffic flow.
The 2005 system worked better

 

I know solid green means traffic flowing well but what does the green dashes represent - I see those along side streets?

 

I believe the dotted green lines mean "estimated" traffic flow.

 

Well. All I can say is that they're not "estimating" correctly sometimes!

:-)

If I am traveling the DC Metro area around rush hours, I've got in the habit of trying to force a refresh. But I am not sure it does any good at all.

Google and Apple don't seem to do any better, if that's any consolation.

 

IMO, Google traffic and estimated time is a lot better

 

The slow traffic info has nothing to do with the particular NAV system. This has been an issue for me since 2007. I canceled my XM subscription long ago, I use good old AM radio for my traffic info.

 

the new traffic does not come via XM, rather it is cellular. Slow traffic info depends on many factors. XM had a refresh delay - refreshed about every 10 minutes. However, the bigger delay was upstream to NavTraffic vendor. I compared it to Google many times and there could be a 30 minute or more delay in the info being sent from Navtraffic. There is also delays depending on the source -could be sensor data collected by State Agencies or private companies.

 

On one of our xcountry trips I had the same problem and got so upset that I called Acura CSD and asked them "Why"...
They connected me to the engineering dept and he told me that when you program a route into the NAV sys , Acura is actually monitoring the trip and traffic "Real Time" and they will or should provide rerouting and actual arrival times.


Hope this helps...

 

My nav sometimes estimates an arrival time that is way longer than should be expected based upon traffic flow and speed. It appears to be completely unrelated to traffic at all. Not sure if this is a glitch in my particular unit