Has your navi EVER routed you down the portion of the dulles toll road between 123 and I-66 (inside the beltway)?

I have programmed in two trips that would normally use that part of the highway: Reston to Ballston, and Reston to downtown DC. On both occasions, it asked me to take the toll road to the beltway and exit there. When I pass the beltway, it asks me to exit on to 123. When I pass that it says "Cannot calculate route". But if I just punch it in again once I'm past 123, it will route me correctly down the remainder of 267 to I-66.

My theory is that because the entire eastbound side becomes HOV during the morning rush hour, they've set it up so that the navi will never use that part of the highway. Haven't attempted it from the other direction. Anyone else notice this?

 

That's very interesting. When calculating a route from Reston to Arlington -- Lee Highway near the Arlington / Falls Church line -- my navi told me to get off at Leesburg Pike and use city streets the rest of the way. So of course, I just ignored it. It's probably the rush hour restrictions you mention -- I think there are truck restrictions there, too, but haven't done any comparison testing,

Lynn
Reston South Lakes

 

This would be in the category of - limitations of NAV systems.

I heard that there's a place at NavTeq that will take issues like this and fix them in future releases.

 

More often than not, I find that the nav selects a circuitous route. Just happened last night actually. I was in Foggy Bottom (22nd & I St), and was headed to Alexandria. Rather than send me down 23rd Street towards the Memorial Bridge/110, it sent me up to Rt.50, over and around to Rt.1, then down. And of course, these crazy routes are always selected with passengers in the car who know the area, so I look like an idiot for buying an Acura nav that doesn't really know the area near as well as they do.

 

Ok, what I want to know is why there are three DC area AZers I've never heard of replying this post and who aren't signed up for the may mini meet yet.

It's still on page one people, get to it!

 

its funny you say that, the only time i ever encountered my navigation saying it couldn't calculate the route was on I-66 within the beltway, heading onto the beltway, i don't know the area really well so i can't give specifics, i was just visiting a friend and somewhere on I-66 right near the beltway, it just simply said, can't calculate route and i waited a minute, as soon as i went another half mile or so i recalculated the "go home" route and it worked perfectly

 

I've had problems in the Fair Lakes area with "can't calculate route." My Nav routes me around that portion of the Toll Road also.

I've definitely had it route me down 66 before though (inside the beltway), and that whole thing is HOV in the AM, so I don't think your theory holds.

One of the Arlington exits it always tells me to take a left and then a U-turn instead of a right though, it's strange.

 

another one!

Sign up for the meet!

 

Guy, I'm with you entirely.

I work in Reston. When I travel into DC for dinner or an event after work, I naturally take the Toll Road to 66 inbound. The navi (in my 2006) insists I exit at the Beltway exit from the tollroad, then take the GW Parkway along the river back to... 66. If you don't take that turn, it tells you to get off at 123 and correct it. If you pass by 123, it says 'cannot calculate route'. EVERYTIME. Every destination in DC / Rosslyn etc.

Its funny isn't it. I just give it the destination after 123 and it does fine.