But if the program is unreliable on fairly simple routes like I-40 in Arizona or I-93 in New Hampshire, how unreliable is it on other secondary or minor roads where "the anomoly" would not be so obvious? Your point about "using human intelligence" is well taken however, in the instances we have discussed it may be fairly obvious that there is a "minor irrgularity" in the routing that could be easily detected by "human intelligence" and corrected
I once thought S&T was a great product and a good value now I'm not so sure. At least I could have reverted to the previous version that worked correctly, even if the maps What's even sadder is my stupidity for trusting Microsoft to do an "upgrade" correctly and discarding the installation DVD's for my previous versions. I wonder how many more of these I'm gonna find along the route.? Off SR7 thru town and no amount of fiddling will keep it on SR7 that bypasses the village. The other area I have found having a similar problem is along SR7 near Boyntonville, NY. This is the first year I have found such problems. Screen in ten-mile-segments looking for possible bugs. With each new version of S&T, as a final check, I drag the route along the I have a 3200-mile-one-way trip from Phoenix to Rimouski, QC, Canada that has evolved over the years in several variations using previous versions of S&T. Even if the map data is at fault, the consumer has the right to expect the product to work as advertised.
MICROSOFT STREETS AND TRIPS 2011 PROBLEMS SOFTWARE
I can understand "new" software having bugs, but when things move backwards like this it is very frustruating. Previous versions of S&T have handled this segment of highway correctly, and now the 2011 "upgrade", for I-40 was constructed in its present location in the 1960's and has not been relocated. This is a sad testimony for this product. gpx file issues) and recalculated the route. Lastly, I have exported the route from S&T 2011 to MapSource (after solving. The previous versions, but I have also tried to create this route in a "virgin" 2011 file with the same problem resulting. The issue was discovered in S&T 2011 in a file created under I have also discovered a similar issue in a location in New York State. In short, as reported under the "Broken Routing" Topic for the Toronto area, it's as though this segment of road does not exist in the database.įurthermore, I have calculated the same route in S&T 2006 thru 2010 with no such issues.
The following steps all fail to place the route on I-40 between MP300 & MP303:ġ) setting road types preferences to "Interstate" and all other types to "dislike"Ģ) dragging and dropping the route onto I-40 EBģ) creating one or more avoidance areas on Goodwater Road between MP300 & MP303Ĥ) setting a stop point on I-40 EB between MP300 & MP303 and recalculating route However, at I-40 MP300 EB (34-59-26N 109-57-57W) the route leaves I-40 and follows a parallel road (Goodwater Road) to MP303, then re-enters I-40 EB. Situation: Create a route from Phoenix, AZ to Albuquerque, NM in S&T 2011, Win7 Home Premium 64-bit.
0 kommentar(er)
