Navigation problem
I'm sure this is related 100% to the multi-mapsets that CF uses, but here goes:
This morning I picked up a load from Fairmont, WV to Canton, NC. I've been to the delivery location before, so I had it saved in my POIs. However, I can't select the exact location because it's in a different mapset. So, I select the town itself. No problem. It shows 410 miles (give or take a few) which was dead on the money.
So, when I go to leave I have to circle our building. This caused a recalculation. The route now says 655 miles. Mind you I've moved maybe 100 yards.
Ok - reload the map, select the city again and get the correct mileage. Off I go.
It routes me down I-79, US-19, I-77, I-81, I-26, I-40 to Canton. This is correct.
After I drove about 180 miles or so, I take US-460/US-19 through Bluefield, WV to go around some construction. After CF finally accepts this road, it now shows about 450 miles to Canton. I ignore it and continue on.
When I came onto I-81 in Abingdon, VA, CF now shows 360+ miles to the location. So, again, I reselect the map, reselect the town and it recalculates correctly at about 150 miles.
Off I go again. When I crossed the TN/VA state line on I-81, CF went from showing 140 miles to now showing 190 miles. This time I ignore it since I knew that the map would reload once I crossed into NC.
At the TN/NC state line, CF went from showing 140 miles in TN to now showing 60 miles in NC.
If anything shows that CF needs to use a single map file, or have the ability to load multiple maps at the users discretion/needs, this is it.
Remember, I cross the eastern half of the country on a daily basis. Just since yesterday, I've had the northeast (NJ), Mid-Atlantic (PA/WV), East Central (TN) and South Central (NC) maps in use. Tomorrow I'll use South Central, East Central and Mid Atlantic all over again and I'm quite positive that I'll have the exact same recalculation hiccups that I've had all day today.
|