Home › Microsoft Streets and Trips › Preferred roads types in Streets & Trips
Using Microsoft Streets and Trips 2009 - wondering what S&T's definition of "Other highways" and "Arterial roads" is!? Is the definition documented somewhere? If not, why not?
Below is an image of my 'Preferred Roads' sliders set in Route Options - Segments.
Started my route at Biggs Junction OR and ended route at Yakima, WA. Both start and end points are on US Hwy 97 (an arterial road I'd guess). No street addresses specified and no stop along the way.
For some weird reason, S&T's route does not take the obvious direct route on Hwy 97 but instead heads east on Hwy 14 and also uses several "back" roads! In fact, if I force the route to US 97 by placing pushpins with stop points along the way, S&T will set a route using any available back road which intersects with US 97 at any point and then intersects US 97 at a more distant point! In other words, the routing algorithm in S&T seems to want to avoid US 97 at all costs and prefers to use back roads!
Since I've specified maximum dislike for "Other highways" and maximum like for "Arterial roads", it appears that S&T's route did exactly the opposite! Isn't a US highway considered an arterial highway? What am I missing?
Below is an image of my 'Preferred Roads' sliders set in Route Options - Segments.
Started my route at Biggs Junction OR and ended route at Yakima, WA. Both start and end points are on US Hwy 97 (an arterial road I'd guess). No street addresses specified and no stop along the way.
For some weird reason, S&T's route does not take the obvious direct route on Hwy 97 but instead heads east on Hwy 14 and also uses several "back" roads! In fact, if I force the route to US 97 by placing pushpins with stop points along the way, S&T will set a route using any available back road which intersects with US 97 at any point and then intersects US 97 at a more distant point! In other words, the routing algorithm in S&T seems to want to avoid US 97 at all costs and prefers to use back roads!
Since I've specified maximum dislike for "Other highways" and maximum like for "Arterial roads", it appears that S&T's route did exactly the opposite! Isn't a US highway considered an arterial highway? What am I missing?
OK, apparently, US highways are considered "Other highways" by S&T. When I moved the slider for "Other highways" to maximum "Like" (slider all the way to the right), the resulting generated route was correct.
Again, I wonder how S&T's defines "Arterial" and "Other" highways. It would be helpful if this was documented!
Again, I wonder how S&T's defines "Arterial" and "Other" highways. It would be helpful if this was documented!
There are both state and federal highways that are limited access. S&T has "limited access" grouped with Interstates. It apparently treats them the same. I travel from Columbus, GA, to Bay City, Michigan, a lot and nearly all mapping programs, including S&T take me north from Ohio using U.S. 23. It's limited access. If it was just interstates, it would route me through Detroit. I'd rather be set on fire for 15 minutes than to have to take I-75 through Detroit. I'm guessing that, for the most part, it means actually Interstates and limited access roads.
I've made the trip scores of times and I don't need maps or GPS. I use the GPS to check the progress of the trip and for entertainment.
I've made the trip scores of times and I don't need maps or GPS. I use the GPS to check the progress of the trip and for entertainment.