AARoads Forum

Please login or register.

Login with username, password and session length
 1 
 on: Today at 06:08:40 AM 
Started by Henry - Last post by sparker
During the four years I spent in Portland (OR), Christmas time was about the only time the city received even a dusting of snow (in two years out of the four) -- but it was invariably accompanied by most of the roads icing over, which particularly affected my commute home, since I lived near the top of the ridge between Portland and Tigard; a couple of evenings I ended up spending most of the night in a pizza parlor near my PSU T.A. office waiting for someone to clear either I-5 or the parallel Barbur Blvd.  After spending the first 40+ years of my life in CA, having winter disrupt my local travel was a new one on me.  Particularly "chilling" was the ice buildup on the Willamette River bridges -- especially those with steel grates as the driving surface!

 2 
 on: Today at 05:17:52 AM 
Started by jakeroot - Last post by sparker
Wikipedia article feature: Washington State Route 520 from Seattle to Redmond, HQs of Microsoft and Nintendo (of America)...and the suburb of Redmond is known as "Silicon Forest".

https://en.wikipedia.org/wiki/Washington_State_Route_520

No one calls it that. Silicon Forest is the name of the Hillsboro-Beaverton corridor in Portland. We really don't want the region to be known as a "Silicion [Landform]".

Since when has any particular location had any say regarding popular (and decidedly reductionist) monickers?  When I was living in Portland in the mid-'90's, quite a few folks (mostly connected with PSU) referred to Beaverton-Hillsboro (essentially the OR 8 corridor) as either the "Tektronix" or "Nike" corridor after the firms whose facilities tended to dominate the area.  This even continued after the inception of the LR extension in the area -- particularly among the more vehement PSU-based urbanists who viewed the LR as "enabling" development in the suburban area west of town; some even referred to that western area as the "San Fernando Valley" of PDX (however, there were little or no complaints from that quarter about the eastern part of the line extending to Gresham!). 

 3 
 on: Today at 05:08:25 AM 
Started by Roadgeekteen - Last post by jakeroot
In the US, the Hana and Piilani Highways, south and west from Hana until the Kamole Gulch. The road from the Twin Falls to Hana is curvy, but at least it's two lanes (except for the bridges).

In the UK, the A82 from Tarbet to Crianlarich, Scotland (which has since been partly upgraded). Honorable mentions: Old Frome Road east of Wells, England, and the A259 from Hastings to Brenzett, England.

 4 
 on: Today at 04:56:57 AM 
Started by Max Rockatansky - Last post by sparker
Pretty much all state route signage on non-state maintained roadways seems to have been gone by 1940 if the Division of Highways didn't make the acquisition.

The one exception to this was SSR 39, signed on Hacienda Blvd. between Whittier Blvd. and I-10 at least from 1959 to early 1971; the earliest signage I can recall personally seeing on this route -- never formally within the state highway system -- was back about '59; it also used the original Garvey Ave. frontage road on I-10/San Bernardino Freeway to effect the connection between Hacienda Blvd. and Azusa Ave.; white larger post-bear shields (with button copy) were posted on the frontage road, with SB trailblazers from WB Garvey to SB Hacienda.  Signage survived the '64 change to green shields; there was a mixture of old white and new green shields along Hacienda, along with CA 39 signage on the BGS's at the Hacienda Blvd. exits along the CA 60/Pomona Freeway.  In either late '70 or early '71 a green patch reading "TO" was placed on the BGS's 39 shield; any reference to CA 39 was gone by about '74.  That connecting section was always an oddity; it seemed that both Caltrans and L.A. County, at least for a while, displayed a seemingly pathological need to connect the two sections of CA 39 -- although the segment of Hacienda over the top of the Puente Hills was a windy 2-lane road hardly conducive to through traffic, particularly after the largely parallel Colima Road (to the west) and Harbor Blvd. (to the east) were deployed in the '70's.   

 5 
 on: Today at 04:51:07 AM 
Started by lepidopteran - Last post by TheHighwayMan394
I guess widening the scope a bit. I'll just do I-35 in MN since I don't think I use I-94 or I-90 enough to qualify any of them.

North of MSP, I don't ever remember using:
Exit 175 (Pine County 14-Beroun).

South of MSP, I don't ever remember using:
Exit 66 (Rice County 1-Dundas/Montgomery)
Exit 55 (NB only - Faribault BL I-35)
Exit 43 (Steele County 34-Owatonna north side)
Exit 32 (Steele County 4-Hope)
Exit 22 (Freeborn County 35-Geneva/Hartland)
Exit 5 (Freeborn County 13-Twin Lakes)
Exit 2 (Freeborn County 5)

 6 
 on: Today at 04:48:11 AM 
Started by roadman65 - Last post by MNHighwayMan
Minnesotaís general practice is stacks when itís a same-direction concurrency and side-by-sides when itís a perpendicular concurrency.

This is my strong preference.

If we're going to talk preferences, then my preference is horizontal alignment for two and three routes, a square for four, and a 2/3 split for if, god forbid, you need to have five routes together at once. These are all independent of direction; if you have two routes going the same direction, then the assembly gets two tabs.

Of course, I don't think needing five or more routes together at once should ever occur, (and four is really pushing it, too) but that's a whole different topic.

 7 
 on: Today at 04:44:41 AM 
Started by roadman65 - Last post by roadfro
Nevada doesnít have too many concurrencies...only US/US and I/US overlaps.

Where two routes overlap, the shields tend to be side by side more often than not (thereís a few spots on the I-15/US 93 overlap that are on top of each other). For the two triple overlaps involving interstates, the I-shield is typically displayed above the the two side by side US shields.

 8 
 on: Today at 04:35:30 AM 
Started by fillup420 - Last post by roadfro
I think US 395 goes from 2-lane to full freeway near the northern CA/NV border.

Itís full freeway in Nevada, transitions to 4-lane divided right at the California state line for about 7 miles to just past the Hallelujah Junction interchange (this section feels like itís still freeway though), then goes down to 2-lane road.

 9 
 on: Today at 04:31:58 AM 
Started by fillup420 - Last post by slorydn1
Thought of I-290 and IL 53 in the Schaumburg area -- its not usually called both numbers at the same time, but is often referred to Route 53 or I-290 or even Ike Extension (tho that is more proper to the "diagonal" segment between I-88/I-294 and I-355)

You'll hear, from time to time, "355 Route 53 Combo" on WBBM for the entire route from Lake Cook Road to I-80.  I-290 never seems to exist there, sort of like I-96 doesn't really exist in people's minds between M-14 and I-696 around Detroit.

(There's a whole other thread, routes that are primary that don't exist in people's minds, or on the traffic reports.)


Agreed. My time in Chicagoland basicly predates the I-355 era and back then the traffic reports always mentioned time from Austin to the Post office, the Tristate to the Post Office, and 53 to the Post Office when talking about the Ike corridor. When they did give traffic reports on the 53 corridor (usually evening rush not morning for some reason) they would say that 53 was running x minutes from Army Trail to Lake-Cook giving no mention of 290 at all.

 10 
 on: Today at 04:27:21 AM 
Started by lepidopteran - Last post by jakeroot
South of Seattle, I-5 southbound Exit 156. The northbound Exit 156 goes towards the 599 freeway, but the southbound exit goes towards Interurban Ave (you have to make a couple turns to get onto the 599). As far as I can remember, despite the exit being in a very urban area, I've never exited there. I can think of several reasons why I might want to, but I still never have.


Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.