I just got my MINI with NAV, and I noticed that the computer never recommends getting on the Rock Creek Parkway, even though it's the fastest route. I ignore the NAV directions and get on the Parkway anyway hoping that the computer would automatically give me new directions, but it doesn't, it merely tracks my position. In order to get new directions, I need to specifically ask the NAV for directions. Anyone else from DC notice this problem?

 

The OEM Nav system is very hesitant to ever take you on a road that you might not be allowed on.

In the case of RCP, since it is only one-way at certain times of the workday, it would rather route you around it than try to take you on it in the wrong direction.

In the case if I-66 inside the Beltway, since the entire road in one direction is HOV only during rush hour, it pretty much ignores the road exists.

It sucks, I know... but at least you can understand why... MINI/BMW/Navteq (not sure exactly who made the decision) wants to be absolutely sure they aren't to blame for getting you in an accident or getting an HOV ticket, because they told you to do it.

 

So I assume that you've experienced this problem. It's good to know it's something that's happening to everyone in DC, and not just me.

I can understand MINI/BMW/Navteq's rationale, but my old Garmin unit knew when the parkway was one way or two way, so it's frustrating that my MINI NAV, which costs $1,500 more, can't provide me with the same info.

I assume the problem is with Navteq. Is there a way to complain to them?

 

Not specifically, as I don't drive into DC much any more... but based upon the proven similar behavior with I-66 inside 495, I expect the same thing is happening here - the system is just being extra-careful not to get you in trouble.I agree... it's probably the #1 thing I don't like about the OEM Nav, although in general I really like it.Yes, on their website they have the ability to report problems & changes...

but I think you'll find that there's nothing for them to correct. I know that another member here (mbabishkin I believe) reported the I-66 problem to them, and they checked their database... apparently it is recorded in the map data as being conditional HOV during certain times of the day, and those times are recorded correctly.

If that's the case, it means that the Nav system itself is ignoring that conditional info and just bypassing I-66 altogether until you get outside 495. Perhaps it does not have a tie-in to the time of day (although you'd think it should since all GPS systems can get very accurate clock data from the satellites).

I suspect the exact same limitation is causing your RCP problem... Navteq probably has the correct "1-way in rush hour during these times" data recorded on the map disc, but the Nav system isn't using it. That's my hunch... but it wouldn't hurt to contact Navteq to check with them.

 

A bit off-track, but this would certainly explain why Google Map web site always ignore I-66 inside the Beltway, even when I tried to "force" to use I-66.

Are we so afraid of being sued for liability that NAV and web sites do silly things like ignoring certain highways?? What ever happened to PERSONAL RESPONSIBILITY???? :impatient

 

That went out the window when mother's started blaming teachers for actions of their children when it was really their failure to parent at home.

 

This is a problem that also exists with Canal road. The Parkway is usually closed on weekend days to allow runners, bikers, etc. to use the road as a bike path. Because the Nav system does not know what day or time it currently is, it will NEVER recommend using a route that has any type of driving restriction. I first noticed this with Canal road (the best way to get from Bethesda to Georgetown) then I noticed it on I-66 inside the beltway. I'd like to know about any other places that people have experianced problems...

 

add to that a dash of lazy programmers and voila....the reason becomes completely clear.

Speaking of Canal Rd, anyone tried using the GPS to get to the portion of reservoir rd between Canal Rd & Foxhall Rd?