Unchecked
Listen to this article

Interstate 35

From Wikipedia
Jump to navigation Jump to search

Template:Infobox road

Interstate 35 (I-35) is a major Interstate Highway in the central United States. As with most primary Interstates that end in a five, it is a major cross-country, north–south route. It stretches from Laredo, Texas, near the Mexican border to Duluth, Minnesota, at Minnesota State Highway 61 (MN 61, London Road) and 26th Avenue East.[1] The highway splits into I-35E and I-35W in two separate places, the Dallas–Fort Worth metroplex in Texas and at the Minnesota twin cities of Minneapolis–Saint Paul.

At 1,568 miles (2,523 km), I-35 is the ninth-longest Interstate Highway following I-94, and it is the third-longest north–south Interstate Highway, following I-75 and I-95. Even though the route is generally considered to be a border-to-border highway, this highway does not directly connect to either international border. I-35's southern terminus is the traffic signal at Hidalgo Street in Laredo, Texas, just short of the Mexican border. Travelers going south can take one of two toll bridges across the Rio Grande and the border, either straight ahead onto the Juárez–Lincoln International Bridge, or via Business Interstate 35-A (Bus. I-35-A) through downtown Laredo into the Gateway to the Americas International Bridge. To the north, I-35 terminates in Duluth, Minnesota, with connections to Canada from the Interstate's terminus via MN 61 to Grand Portage, or north to the border at International Falls, Minnesota, via U.S. Route 53 (US 53) in Duluth.

In addition to the Dallas–Fort Worth and Minneapolis–Saint Paul areas, the major cities that I-35 also connects to include (from south to north) San Antonio, Texas; Austin, Texas; Oklahoma City, Oklahoma; Wichita, Kansas; Kansas City, Missouri; and Des Moines, Iowa.

Route description

[edit | edit source]

Template:Lengths table |- |TX |style="text-align:right;"|503.96 |style="text-align:right;"|811.05 |- |OK |style="text-align:right;"|235.96 |style="text-align:right;"|379.74 |- |KS |style="text-align:right;"|235.53 |style="text-align:right;"|379.05 |- |MO |style="text-align:right;"|114.74 |style="text-align:right;"|184.66 |- |IA |style="text-align:right;"|219.23 |style="text-align:right;"|352.82 |- |MN |style="text-align:right;"|259.64 |style="text-align:right;"|417.85 |- |Total |style="text-align:right;"|1,569.06 |style="text-align:right;"|2,525.16 |}

Texas

[edit | edit source]
Error creating thumbnail:
I-35 starts at this traffic signal in Laredo, Texas

I-35 northbound begins at a traffic-signaled intersection with Bus. I-35-A in Laredo, Texas, just north of the Rio Grande and the international border between Mexico and the US. It has a 17-mile (27 km) concurrency with US 83. Through Webb, La Salle, and Frio counties, it has a mostly north-northeastern course, turning more northeasterly around Moore.[2] It then cuts across the corners of Medina and Atascosa counties before entering Bexar County and San Antonio.

I-35 is named the Pan Am Expressway in San Antonio. There, it has brief concurrencies with I-10 (with it US 87) and I-410, and it serves as the northern terminus of I-37. I-35 heads northeast out of the city toward the state capital, Austin.

In Austin, I-35 is the Interregional Highway and has a concurrency with US 290 through Downtown Austin.[3] Throughout Austin, elevated express lanes were constructed on either side of the original freeway. Prior to this expansion, this section included an at-grade railroad crossing, which is extremely unusual for a freeway. From Austin, I-35 goes through Round Rock, Temple, Pflugerville, and Waco. In Belton, south of Temple, it serves as the current eastern terminus for I-14. In Waco, I-35 is known as the Jack Kultgen Freeway, and begins its concurrency with US 77. The campuses of both the University of Texas at Austin and Baylor University are located adjacent to I-35.

I-35 then heads to Hillsboro, where it splits into I-35W and I-35E and runs through the DallasFort Worth area. The official milemarkers, along with the route of US 77, follow I-35E through Dallas—I-35W, which is 85 miles (137 km) in length, carries its own mileage from Hillsboro to Denton, as though it were an I-35 loop. In Dallas, I-35E is the R.L. Thornton Freeway south of I-30, which picks up the name heading east. North of I-30, it is the Stemmons Freeway.

After passing through Dallas and Fort Worth, I-35's two forks rejoin each other in Denton near the University of North Texas campus. The unified Interstate then continues north to Gainesville before crossing the Red River into Oklahoma.

Oklahoma

[edit | edit source]
Error creating thumbnail:
I-35 in Goldsby, Oklahoma, at milemarker 102

In Oklahoma, I-35 runs from the Red River at the Texas border to the Kansas state line near Braman. It passes through or adjacent to many of the state's major cities. From south to north, these cities include Ardmore, Pauls Valley, Purcell, Norman, Moore, Oklahoma City, and Edmond. In Downtown Oklahoma City, I-35 has a major junction with I-40 and spurs into I-235 through the north central inner city as heavy traffic follows through the city into the northern area of the state.

Kansas

[edit | edit source]
Error creating thumbnail:
A view from the I-35 portion of the Kansas Turnpike, between mileposts 29 and 30

Between the Oklahoma state line and Emporia, I-35 is part of the Kansas Turnpike. This section of Interstate serves Wichita and passes through the Flint Hills area. At Emporia, I-35 branches off on its own alignment. This free section of I-35 provides access to Ottawa before entering the Kansas City Metropolitan Area, where it serves Johnson County and Kansas City, Kansas.

Of note on the route, at several points between Cassoday and Emporia in the Flint Hills, dirt driveways that provide direct access without a ramp for cattle trucks may be found in either direction along the highway.

BETO Junction is a highway intersection in Coffey County, Kansas, that is the intersection of US 75 and I-35. It derives its name from the four major cities nearest the intersection: Burlington, Emporia, Topeka, and Ottawa. It is located 16 miles (26 km) north of Burlington at exit 155. Historically, the intersection referred to as "BETO Junction" before I-35 was constructed was located on the old US 75 alignments two miles (3.2 km) south and two miles (3.2 km) east, near Waverly, Kansas.

Missouri

[edit | edit source]
Error creating thumbnail:
Bond Bridge carries I-35 in Kansas City

I-35 enters Missouri two miles (3.2 km) southwest of Kansas City's Central Business District as a six-lane highway. After merging with Southwest Trafficway and Broadway, it becomes eight lanes and continues north to downtown Kansas City, where it serves as the west and north legs of the downtown freeway loop. Along the north edge of the loop, I-35 joins with I-70 immediately west of Broadway and carries six lanes of traffic with a speed limit of 45 mph (72 km/h). Upon leaving the loop, I-29 begins, concurrent with I-35. The two Interstates cross the Missouri River together on the Bond Bridge.

After crossing the river, I-29 and I-35 split. I-35 heads north to Cameron, Missouri, and then continues northward to the Iowa state line.

Error creating thumbnail:
I-35 in Iowa, near exit 182. The town of Swaledale is about one mile (1.6 km) to the east.

In the southern sections of the state, I-35 is parallel to US 69 for much of its course.

In Des Moines, I-35 has a 12-mile (19 km) overlap with I-80. The concurrency takes place northwest of the downtown district of the city. At exit 127 of I-80, the overlap turns east and terminates at exit 137 via an interchange with I-235.

North of Des Moines, I-35 is mainly parallel with US 69, traversing a vast and rural area of Iowa.[4]

I-35 is part of the Avenue of the Saints between Clear Lake and St. Paul, Minnesota. A four-lane link has been completed between Clear Lake and I-380 in Waterloo, Iowa.

Minnesota

[edit | edit source]
Error creating thumbnail:
I-35's northern terminus is at this intersection with London Road (MN 61) in Duluth, Minnesota, with Lake Superior in the background.

At Medford, Minnesota, the on- and offramps lead to roundabouts rather than standard cross intersections.[5] This is the first site in the state linked to a major highway to use roundabouts.

I-35 splits again into I-35W and I-35E in the MinneapolisSaint Paul area. The mile- and exit-numbering sequence continues along I-35E. At one sharp turn in I-35W near the junction with I-94, drivers are advised to slow to 35 mph (56 km/h) (although many drivers are able to maintain the speed limit of 55 mph (89 km/h)). It is not possible to go from westbound I-94 to northbound I-35W, from southbound I-35W to eastbound I-94, and vice versa, without resorting to surface streets.

On I-35E in Minnesota between MN 5 and I-94, in both directions, trucks weighing more than 9,000 pounds (4,100 kg) are banned from the freeway, and the speed limit drops to 45 mph (72 km/h). This section was not completed until the late 1980s (although the route was cleared and graded earlier) due to opposition from the historic Crocus Hill neighborhood, which sits only a few hundred feet from the alignment. The four-lane alignment, "parkway" design was a compromise. The truck bypass for this section is signed on I-494 and I-694 to the east of Saint Paul.

I-35 has an interchange with I-535/US 53 in Duluth, Minnesota, known locally as the "Can of Worms". This junction features a pair of left exits from I-35, a stoplight, and lane drops over the I-35 bridge.[6]

The national northern terminus of I-35 is at an intersection in eastern Duluth. Drivers' options include merging with London Road/MN 61 northbound, proceeding through the stop lights onto 26th Avenue East, or turning left onto London Road southbound.

History

[edit | edit source]

Some portions of I-35 in Oklahoma City were already built in 1953, before the Interstate system was created.[7] Through Norman, Oklahoma, the Interstate opened in June 1959. In Moore, it opened in two parts: the northern half, connecting Moore to Oklahoma City, opened in January 1960. The southern half, linking it to Norman, was opened to traffic in June 1967.[8]

I-35 through Oklahoma largely parallels US 77. This is in large part due to efforts of the towns of Wynnewood, Paoli, and Wayne, which fought to keep I-35 as close as possible to US 77. This was successful due to a threat from Governor Henry Bellmon to build a toll road rather than I-35, and legislation preventing state funds for the Interstate from being spent if it were more than one mile (1.6 km) from the U.S. Route.[9]

I-35 was completed in Oklahoma in 1971, when parts of the Interstate running through Carter Co. and Murray Co. were opened to traffic.[7]

The final segment of I-35 (as originally planned) to open was in north-central Iowa, between Mason City and US 20 near Iowa Falls. This segment was delayed due to some controversy. Originally, I-35 was to follow the alignment of US 69 from Des Moines to the Minnesota border, but Mason City's business community lobbied for the route to be moved closer to their city. On September 1, 1965, the alignment was changed to instead parallel US 65 through northern Iowa, which brought the highway much closer to Mason City. This created a long diagonal section through Wright and Franklin counties. Local farmers objected to their farms being bisected into triangular pieces, and resulting litigation delayed I-35 for several years. A November 1972 ruling rejected a lawsuit filed by the farmers, and the final segment of I-35 was allowed to proceed, eventually opening in 1975.

The Paseo Bridge over the Missouri River in Kansas City, Missouri, was replaced by the dual-span cable-stayed Christopher S. Bond Bridge in December 2010.[10]

"NAFTA Superhighway" controversy

[edit | edit source]
Error creating thumbnail:
I-29 and I-35

The proposed Trans-Texas Corridor toll-road project included one proposal (TTC-35) to primarily parallel I-35 from the Mexican border up to the Oklahoma border.[11] There are major disagreements as to what impact this parallel route would have on I-35 in terms of traffic, maintenance, and commerce.

The Trans-Texas Corridor was first proposed by Texas Governor Rick Perry in 2002. It consisted of a 1,200-foot (370 m) wide highway that also carried utilities such as electricity, petroleum, and water as well as railway track and fiberoptic cables.[12] In July 2007, US Representative Duncan Hunter successfully offered an amendment to House Resolution 3074, the FY2008 Transportation Appropriations Act, prohibiting the use of federal funds for Department of Transportation participation in the activities of the Security and Prosperity Partnership of North America (SPP). Hunter stated that: "Unfortunately, very little is known about the NAFTA Super Highway. This amendment will provide Congress the opportunity to exercise oversight of the highway, which remains a subject of question and uncertainty, and ensure that our safety and security will not be compromised in order to promote the business interests of our neighbors."[13] Fellow Republican Congressman and presidential candidate Ron Paul brought the issue to mainstream prominence during the December 2007 CNNYouTube GOP debate, where he rejected the concept and also called it the NAFTA Superhighway after the North American Free Trade Agreement and, like Hunter, framed it within the ultimate goal of creating a North American Union.

In 2011, the Texas Legislature formally repealed its authority for the establishment and operation of the Trans-Texas Corridor with the passage of HB 1201.[14][15]

Junction list

[edit | edit source]

Source:[16]

Southern segment
Texas
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Laredo; the highways travel concurrently to Botines, approx. 18 miles (29 km) north.
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Laredo
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Moore
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in San Antonio
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in San Antonio. I-10/I-35/US 87 travels concurrently through Downtown San Antonio.
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in San Antonio
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type on the San Antonio–Windcrest city line; concurrency for three miles (4.8 km).
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Austin; the highways travel concurrently through Austin.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Austin
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Round Rock
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Copperas Cove; US 190 travels concurrently to Belton.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Waco; the highways travel concurrently to northeast of Hillsboro; follows route of I-35E afterward.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type on the Waco–Bellmead city line
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type north-northeast of Hillsboro
Central segment
Texas
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Denton
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Denton
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Denton; the highways travel concurrently to south of Thackerville, Oklahoma.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Gainesville
Oklahoma
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Ardmore; the highways travel concurrently through Ardmore.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type north of Springer
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Davis
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Norman; the highways travel concurrently to Oklahoma City.
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Oklahoma City; I-35/US 62 travels concurrently through Oklahoma City.
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Oklahoma City; I-35/I-40/US 270 travels concurrently through Oklahoma City.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Oklahoma City; the highways travel concurrently through Oklahoma City.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Edmond; the highways travel concurrently to Guthrie.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Perry
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Perry; the highways travel concurrently to north-northwest of Perry.
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type north-northwest of Perry
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Tonkawa
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type north-northwest of Braman
Kansas
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type east-northeast of South Haven
Error: package.lua:80: module 'Module:Road data/strings/USA/KS' not foundModule:Jct error: Invalid route type southern terminus in rural Sumner County
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type east of Wellington
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Wichita
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Wichita
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type north of El Dorado
Error: package.lua:80: module 'Module:Road data/strings/USA/KS' not found / Error: package.lua:80: module 'Module:Road data/strings/USA/KS' not foundModule:Jct error: Invalid route type in Emporia
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Emporia
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type east of Emporia; the highways travel concurrently to Lenexa.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type south-southeast of Olivet
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Ottawa; the highways travel concurrently to east-northeast of Ottawa.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Gardner; the highways travel concurrently to Merriam.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Olathe; the highways travel concurrently to Merriam.
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Lenexa
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Lenexa; the highways travel concurrently to Merriam.
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Mission; I-35/US 69 travels concurrently to Kansas City.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Kansas City
Missouri
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Kansas City
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Kansas City; the highways travel concurrently through Kansas City.
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Kansas City; I-29/I-35/US 71 travels concurrently through Kansas City.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Kansas City
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Claycomo
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Pleasant Valley; the highways travel concurrently to Liberty.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type south of Cameron
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Cameron
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type southwest of Winston
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type north-northwest of Altamont
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Bethany
Iowa
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type on the Iowa state line south of Lamoni
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Osceola
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in West Des Moines; I-35/I-80 travels concurrently to Ankeny.
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type on the CliveUrbandale city line
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Des Moines
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Ankeny
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type southeast of Ames
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type southeast of Blairsburg
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type south-southeast of Clear Lake; the highways travel concurrently to Clear Lake.
Minnesota
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type southeast of Albert Lea
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Albert Lea
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type northeast of Albert Lea
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Owatonna
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Burnsville
Northern segment
Minnesota
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Columbus
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Forest Lake
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Wyoming
Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Duluth; the highways travel concurrently through Duluth.
Error: package.lua:80: module 'Module:Road data/strings/USA' not found / Error: package.lua:80: module 'Module:Road data/strings/USA' not foundModule:Jct error: Invalid route type in Duluth
Error: package.lua:80: module 'Module:Road data/strings/USA/MN' not foundModule:Jct error: Invalid route type in Duluth

References

[edit | edit source]
  1. Template:Google maps
  2. Texas Department of Transportation (2006). Texas Official Travel Map (Map). Texas Department of Transportation.
  3. Bear, Jacci Howard. "Are Interstate Highway 35 and Interregional Highway 35 the Same Road?". About.com. Archived from the original on December 7, 2008. Retrieved December 7, 2006.
  4. Rand McNally (2007). Motor Carriers' Road Atlas (Map) (Deluxe ed.). Chicago: Rand McNally. p. 38.
  5. Federal Highway Administration (September 2004). "Excellence in Highway Design 2004". Focus: Accelerating Infrastructure Innovations. Vol. 21 no. 8. Federal Highway Administration. ISSN 1060-6637. FHWA-HRT-04-029. Archived from the original on June 10, 2010. Retrieved February 12, 2006.
  6. Template:Google maps
  7. 7.0 7.1 Cockerell, Penny (June 29, 2006). "50 Years: As the Intersection of Interstates 35, 40, and 44, Oklahoma Is at America's Crossroads". The Daily Oklahoman. Oklahoma City. p. 2A.
  8. Medley, Robert (June 29, 2006). "Highways Continue to Drive Economy". The Daily Oklahoman. Oklahoma City. p. 1D.
  9. McNichol, Dan (2006). The Roads that Built America: The Incredible Story of the U.S. Interstate System. New York: Sterling. ISBN 1-4027-3468-9.[page needed]
  10. Jansen, Meghan (December 17, 2010). "All Interstate 29/35 Ramps and Lanes Open Tomorrow: On-Budget and Six Months Ahead of Schedule" (Press release). Missouri Department of Transportation. Archived from the original on March 20, 2012. Retrieved November 27, 2011.
  11. "I-35 Corridor Section". Trans-Texas Corridor Study. Archived from the original on May 9, 2007.
  12. Kovach, Gretel (December 10, 2007). "Highway to Hell?". Newsweek. Retrieved December 7, 2007.
  13. Kasper, Joe (July 25, 2007). "Hunter NAFTA Super Highway Amendment Passes House" (Press release). Office of Congressman Duncan Hunter. Archived from the original on December 21, 2008.
  14. "Texas Legislature Online - 82(R) History for HB 1201". Texas Legislature. Retrieved January 28, 2013.
  15. "Texas Legislature Online - 82(R) Text for HB 1201" (PDF). Texas Legislature. Archived (PDF) from the original on October 9, 2022. Retrieved August 13, 2013.
  16. Rand McNally (2014). The Road Atlas (Walmart ed.). Chicago: Rand McNally. pp. 38, 41, 54–55, 58, 83, 100–101. ISBN 978-0-528-00771-2.
[edit | edit source]

Template:Attached KML

Listen to this article (16 minutes)
noicon
Spoken Wikipedia icon
This audio file was created from a revision of this article dated 3 April 2010 (2010-04-03), and does not reflect subsequent edits.

Template:I-35 aux Template:Interstates