During the recent snowstorm here in Virginia, I discovered this odd GPS directions problem. While trying to make it across the county, I put in my destination address, but was forced to change my route several times due to blocked roads and in one case, a bridge being out.
The navigation system would recalculate very quickly, but frequently sent me down dead-end streets, and then direct me to make a u-turn. It's like it never completely mapped the new route...only a general "direction". Not only was this a huge time-waster, in those conditions it was dangerous.
This seems to happen anytime you deviate from the Droid's navigation route. The re-routing never seems to be complete before it starts directing you. Maybe this is a city-vrs-country driving glitch?
Try this at home: Put in a destination, then drive an alternate route, ignoring the directions. Droid will send you down dead-ends and then make u-turns for no reason, plotting a path that cannot possibly get you to your target.
Please post your results.
Note: Luckily, I had a Garmin unit in my car, which seems like ancient technology when compared to Google maps, but the route it finds is always 100% complete end to end. Although, once while were driving to UNC Charlotte via a road-construction detour (Still a highway), the Garmin suddenly announced "Destination Unreachable" and refused to calculate any routes until we moved from the city limits to the city itself. This has got to be the dumbest error message I've ever seen in my life (and I've worked with Windows 3.1!).
The navigation system would recalculate very quickly, but frequently sent me down dead-end streets, and then direct me to make a u-turn. It's like it never completely mapped the new route...only a general "direction". Not only was this a huge time-waster, in those conditions it was dangerous.
This seems to happen anytime you deviate from the Droid's navigation route. The re-routing never seems to be complete before it starts directing you. Maybe this is a city-vrs-country driving glitch?
Try this at home: Put in a destination, then drive an alternate route, ignoring the directions. Droid will send you down dead-ends and then make u-turns for no reason, plotting a path that cannot possibly get you to your target.
Please post your results.
Note: Luckily, I had a Garmin unit in my car, which seems like ancient technology when compared to Google maps, but the route it finds is always 100% complete end to end. Although, once while were driving to UNC Charlotte via a road-construction detour (Still a highway), the Garmin suddenly announced "Destination Unreachable" and refused to calculate any routes until we moved from the city limits to the city itself. This has got to be the dumbest error message I've ever seen in my life (and I've worked with Windows 3.1!).
), so I'm sure the kinks will get worked out. For now, in situations like the one you described above, I'd say don't rely on Google Nav as fool-proof and keep that Garmin around for any other life-and-death situations that may arise.
