Jump to content

Talk:Interstate 35/Archive 1

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 1

Highway Damage and Collapses

-jakob187 - 3:18pm (08/04/2007) I am a resident of Waco, and after hearing about the collapse of the bridge in Minneapolis, I thought I would post up on here that it may be more than just Missouri dealing with this. Last month, a piece of the I-35 bridge that overpasses University Parks Dr. collapsed off and fell onto top of some cars. Mind you, this isn't the same thing as an entire bridge collapsing like in Minneapolis. However, I think it's safe to say that maybe some inspection needs to be done on I-35 with so many reports coming in of collapses. My cousin lives in Oklahoma, and they said there was a piece of cement that had fallen from an overpass as well.

It just makes me worry like crazy about how safe this highway is anymore.

This page is for discussing the article, not the subject. --TMF Let's Go Mets - Stats 20:23, 4 August 2007 (UTC)

Hmm.. Dallas/Fort Worth and Minneapolis/St. Paul are not links..

I suppose if I change this page, then there'll be 50 others to change too..


Major cities

Should we remove Albert Lea, MN from the list? It's not even a major city in Minnesota. Even though it lies at the junction of I-35 & I-90, it's not very significant of its own accord.

  • Well, technically Mason City, IA isn't even on I-35 -- it's approximately 8 miles east. I-35 actually runs through eastern Clear Lake, and the original two Mason City exits (not counting the exit for 'new' Highway 18, which only goes east) are signed as "Clear Lake/Mason City". However, I would vote to keep both Albert Lea and Mason City on the list -- they are know, at least locally, and provide landmarks for where the interstate falls. --Rehcsif 17:39, 1 May 2006 (UTC)
  • The significance of Albert Lea and Mason City being on the list is that they are AASHTO control cities as designated on the highway. That's why I think they should stay, regardless of size. —C.Fred (talk) 21:48, 1 May 2006 (UTC)
That makes sense, thanks. --Rehcsif 21:54, 1 May 2006 (UTC)

Interstate table changes

Added I-30 as a major junction and Laredo, Waco & San Antonio to 'major cities' list. Laredo (208k), Waco (120k) & San Antonio (1.3m) meet requirements. Houston, however, was removed because it's 180 miles east of I-35. 208.190.154.22 20:17, 15 September 2005 (UTC)

Whoops, I shouldn't add infoboxes late at night; it makes reading maps hard. :P Thanks for your fix! Scott5114 19:36, 17 September 2005 (UTC)

Control cities designations

I'm a bit concerned about the apparently dated nature of the source list for control cities linked to this page. In addition to being purely an Adelphia subscriber's personal web site, the information pertaining to I-35 is somewhat inaccurate. The page lists I-35's use of alternating control cities for Dallas/Fort Worth both north and south of DFW. I know for a fact that 'Denton' is used as a control city from the north (also, 'Dallas' in Oklahoma), and has been for some 15 years or so now. Also, Temple is used extensively as a control city both south of Waco and north of Austin (although, it's co-signed with Waco). And new overheads have recently been placed just north of Norman indicating 'Norman' as a new control city for I-35 south of Oklahoma City. Thanks for reading this - are you asleep yet? :P --Emersonbiggins85 05:46, 12 January 2006 (UTC)

Temple may appear on the sign as a destination city, but is it a control city? If it's signed as Temple/Waco, then Waco is the control city. I can't recall now whether 35 SB lists Temple only coming out of town. I'd like to see the AASHTO list first-hand, but the only place it seems to be online is that reprint. C.Fred 06:33, 12 January 2006 (UTC)
I've tried unsuccessfully to track down an I-35 Temple control city sign anywhere on the net. However, here is a link for Denton as a control city for I-35, found in Gainesville. Notice that US 77 was cosigned with I-35 originally, but removed in the mid-90s or so. 'Denton', SB I-35 This recent sign in Dallas legitimizes the control city status for Denton as the control city for I-35E, and a similar situation exists for I-35W. 'Denton', NB I-35E--Emersonbiggins85 21:13, 16 January 2006 (UTC)
Here is a link for Norman, OK as a control city on I-35. I believe that this only exists on a couple of southbound signs, and is probably yet another ODOT anomaly, seeing as many violations of standard signage protocol occur on their watch. 'Norman', SB I-35--208.190.154.22 15:52, 17 January 2006 (UTC)

Of course, all of this could call into question the officiality of the respective state DOTs in adhering to federal guidelines for control cities, though the 'Denton' guidesigns are so old that they exist in button-copy form. 1990~ish

Old routebox content

This was the previous content of the routebox, before the reformulation. It might be useful for making exit guides sometime in the future.

Mexican BorderTX 0
I-10TX 153-156
I-37TX 158
I-20TX 418 (I-35E)
I-30TX 427-428 (I-35E)
I-40OK 126-128
I-44OK 133-138
I-70MO 2
I-29MO 4-8
I-80IA 72-87
I-90MN 13
I-94MN 107 (I-35E)
Minnesota State Highway 61MN 259

--Emersonbiggins85 05:58, 12 January 2006 (UTC)

That sort of stuff happens all the time. I believe the term for it is intermediate destination if memory of the MUTCD serves correctly. They're not official control cities but intended to aid navigation, especially around urban areas. (Side note - one thing I always think of when I see that I-35 Norman sign you linked to is "if you've made it this far, you're going to Norman, like it or not.") Scott5114 05:21, 21 January 2006 (UTC)
Thanks for the clarification. I wholeheartedly agree about the Norman designation, but I am less convinced that particular designation applies for Denton, as it is signed both southbound from the north (all the way from the Red River) and northbound from the south out of both Dallas and Fort Worth. For all intensive purposes, it is treated just like Waco is treated to the south of DFW, which is an official AASHTO control city. Both have equal standing, at least according to the signs that exist. Probably another codified and copied TxDOT inconsistency. --Emersonbiggins85 16:54, 23 January 2006 (UTC)

Exit table

Texas

Number Mile Destinations Notes
1A Scott St./Washington St. Laredo
1B Park St./Sanchez St.
2 U.S. Route 59
Corpus Christi/Freer/Houston
3A Calton Rd.
3B Interstate 35 Business
San Bernardo Ave/Mann. Rd.
4 Farm to Market Road 1472
Del Mar Blvd./Santa Maria Ave.
7 Shiloh Dr./Las Cruces Dr.
8 Texas State Highway Loop 20
World Trade International Bridge
13 Unitec Industrial Park / Uniroyal Proving Grounds
18 U.S. Route 83
Texas Tourist Information Center
Botines
24 Texas State Highway 255
Colombia-Solidarity International Bridge
Laredo Terminus:
East End Webb County
West End Laredo, Texas
38 Business Loop Interstate 35 Encinal, Texas Encinal
39 Texas State Highway 44

Oklahoma

see Interstate 35 in Oklahoma

Kansas

Mile Destinations Notes
4 U.S. 166/81
Arkansas City South Haven
Kansas Turnpike Free exit
17 Southern Terminal toll plaza Replaced old toll plaza under U.S. 160 bridge, opened spring 2003 [1]
19 U.S. 160
Wellington Winfield
26 Belle Plaine Service Center Opened in May 1998, burned down in 2002 due to a grease fire, and was later rebuilt[2]
33 U.S. 81/K-53
Mulvane
39 U.S. 81
Haysville/Derby
42 I-135/I-235/U.S. 81
Wichita/Salina
Wichita
45 K-15 Wichita
50 U.S. 54/400
Kellogg Ave.
53 K-96
Wichita
57 Andover Kansas Turnpike
65 Towanda Service Center
71 K-254
El Dorado
76 U.S. 77
El Dorado North
Nick Badwey Plaza
92 K-177
Cassoday
97 Matfield Green Service Center Contains a memorial to football coach Knute Rockne, who died in a plane crash near Bazaar, Kansas[3]
127 I-35/U.S. 50
Emporia/Kansas City
Mainline becomes Interstate 335
128A U.S. 50 West
Newton
Emporia
128B Industrial Rd.
130 K-99
Merchant St.
National Teachers Hall of Fame
131 Burlingame Rd.
133 U.S. 50 West
6th Ave.
U.S. 50 joins northbound and splits southbound
135 County Rd R1
138 County Rd U
141 K-130
Neosho Rapids/Hartford
148 K-276
Lebo
Sun Dance Park
155 U.S. 75
Lyndon/Burlington
160 K-31 North
Melvern
K-31 joins northbound and splits southbound
Melvern Lake
161 K-31 South
Waverly
K-31 splits northbound and joins southbound
170 Williamsburg/Pomona Was once K-273[4]
Pomona Lake
Rest Area
176 Homewood
182 Business U.S. 50
Eisenhower Rd.
Ottawa
183 U.S. 59
Lawrence/Garnett
185 15th St.
187 K-68
Ottawa/Louisburg
Ottawa Univ., Old Depot Museum
193 Tennessee Ave. Baldwin City LeLoup
198 K-33
Wellsville
202 Edgerton
207 Gardner Rd. Gardner
210 U.S. 56 West
Gardner
U.S. 56 joins northbound and splits southbound
215 U.S. 169 South/K-7
Paola
Olathe U.S. 169 joins northbound and splits southbound
Great Mall of the Great Plains
217 Old Highway 56 Southbound only
218 Santa Fe Kansas State School for the Deaf
220 119th St.
222A-B Interstate 435 Lenexa U.S. 169 splits northbound and joins southbound
224 95th Street
225A 87th Street Northbound exit number is 225
225B U.S. 69 South
Overland Parkway
Southbound only
U.S. 69 joins northbound and splits southbound
227 75th Street Merriam
228A 67th Street
228B-C U.S. 56 East/U.S. 69 North
Shawnee Mission Parkway (63rd St.)
U.S. 56 and 69 split northbound and join southbound
229 Johnson Dr.
230 Antioch Rd. Overland Park
231 I-635 North

U.S. 69 South Metcalf Ave.

Mission U.S. 69 joins northbound and splits southbound
Kansas City International Airport
232B Roe Avenue Kansas City
232C U.S. 69 North
18th Street Expy.
U.S. 69 splits northbound and joins southbound
233A Southwest Blvd.
233B Mission Rd.
234 U.S. 169
7th St. Trfwy./Rainbow Blvd.
235 Cambridge Circle

Missouri

Mile Destinations Notes

IH vs. I?

Where in Central Texas is IH actually used? Nova SS 03:39, 26 April 2006 (UTC)

I've seen it in general use in the Waco area, in Yellow Pages ads and the like. I specifically point out this restaurant listing: note the address given for Dock's River Front. It's also used in San Antonio: see these hotel directions. —C.Fred (talk) 04:06, 26 April 2006 (UTC)
Yes, but the implication is that Texas has a unique way of referring to Interstates that no other state uses. That is totally false. For example, see Google searches on IH-35 in Kansas, Oklahoma, Misery, Iowa, Minnesota. Only a pinhead says "eye hech thirty five" when talking about I-35 in everyday conversation about an Interstate.
I know what this is about: TxDOT uses IH in its internal designations, but this is obscure trivia that does not belong on the topic summary. Furthermore, who's to say that other state DOTs don't use this?
If this "IH" abbreviation is noteworthy, it is noteworthy only as trivia. Also, since it is not unique to Texas, if anything needs to be said about this "IH" thing, it needs to be on every Interstate highway page or on the master Interstate highways page.
Nova SS 14:45, 26 April 2006 (UTC)
On the service/feeder roads around Denton I distinctly remember signs reading IH-35 SERVICE ROAD, so it's not only internal. Perhaps the IH- designation could be mentioned further down the page, in the Notes section. The clause about IH- was added to the article lead by an anon a couple of months ago. ...Scott5114 18:17, 26 April 2006 (UTC)

Merging

I believe Red Bull Highway (Iowa) and Red Bull Highway (Minnesota) are terse enough that they could be covered in this article. I don't believe either article can be expanded much beyond their current length. -Ravedave 17:30, 17 April 2007 (UTC)

Highway of Holiness

I was interested to see that addition to the article. I used to live in Waco, Texas, and a church group held services under one of the overpasses near the Baylor campus. I always figured they were just using the large, open space; I've never seen anything linking it to the Highway of Holiness, but now I'll have to go looking. —C.Fred (talk) 00:56, 20 December 2007 (UTC)

Trans-Texas Corridor

Do we really need this tinfoil-hat horseshit? As just a reader and occasional graffiti-eraser, I didn't want to delete a whole section without consulting anyone, but whatever merit this has (none), it's only tangentially related to I-35. kmd, dallas —Preceding unsigned comment added by 99.57.40.112 (talk) 22:50, 1 June 2009 (UTC)

Interchanges with I-20, 30, 94?

It's been reverted back and forth as a nitpick, so I'm opening discussion. Should I-20, I-30, and I-94 be listed in the major intersections box? Or should the be omitted, because I-35 never intersects them; the interchanges are with I-35W and I-35E? If there were room for a footnote in the box, I'd say to do that, but there's just no space for it.C.Fred (talk) 23:14, 11 August 2010 (UTC)

Looks like with the <small> tag, there is room for a note; I've boldly added one. —C.Fred (talk) 23:17, 11 August 2010 (UTC)

Photo removal, Kansas City

I've removed the photo File:KCInterstateMass.jpg from this article because, while the image does contain some signage indicating the way to to I-35 in Kansas City, MO, examination of the signage as a whole leads me to believe that it was taken from the northbound lanes of U.S. 71 near its intersection with I-70 and I-670. I-35 is approximately one mile away from this location, either to the north or to the west. See map here. Gummigoof (talk) 23:55, 16 April 2011 (UTC)

Okay, original research, but: I live here and I agree that this was taken from US 71 northbound, just north of 18th Street. Google Street View shows the same sign bridge here. 174.58.136.73 (talk) 21:27, 22 May 2011 (UTC)

I agree with your findings. Anyway, it's not original research if StreetView backs it up. :D –Fredddie 22:21, 22 May 2011 (UTC)

Where did I-35 in Missouri article go?

Currently (about 21:15 UTC, 22 May 2011), the Missouri section in this article consists only of a link to the "Interstate 35 in Missouri" article... which then redirects back to this article. I want to fix the link but I can't find the original "Interstate 35 in Missouri" article, if it existed. 174.58.136.73 (talk) 21:27, 22 May 2011 (UTC)

It was redirected because there was no substantial content. I rescued what content there was and put it back into the main article. –Fredddie 22:21, 22 May 2011 (UTC)
Thanks! 174.58.136.73 (talk) 22:31, 22 May 2011 (UTC)

Chicago-Kansas City Expressway

I came here to see if the Chicago-Kansas City Expressway was mentioned in the Missouri section. I don't know that any legislation supports the CKC designation in Missouri, but there are CKC signs on I-35 north of KC (original research). If the "I-35 in Missouri" article comes back or gets written, CKC would be good to mention. 174.58.136.73 (talk) 21:27, 22 May 2011 (UTC)

I live in Des Moines and I've never seen any CKC signage outside of Missouri. Seems odd that a Chicago-to-KC highway would only be signed in Missouri. –Fredddie 22:21, 22 May 2011 (UTC)
The CKC expressway article (link fixed, above) claims that there are signs in Illinois. [[1]] has some photos of the signs in Illinois (search in that page for "Hillside" twice to jump to the first one). A few minutes with Google isn't showing a picture or a reference for these signs in Missouri, though. 174.58.136.73 (talk) 22:31, 22 May 2011 (UTC)

BETO Junction

The following is a closed discussion of the proposal. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

Merge. Imzadi 1979  01:19, 25 August 2011 (UTC)

My comments on a merger are located at Talk:BETO Junction as I feel that that is a better forum for any discussion of merger.Cuprum17 (talk) 20:59, 2 June 2011 (UTC)

The following was moved here to keep the discussion in one place. The merger templates will direct editors to make there comments here, so they should be made here. Imzadi 1979  21:34, 2 June 2011 (UTC)
  • Oppose A proposal to merge the BETO Junction article with the Interstate 35 article has been made by User:Fredddie. I am opposed to the merger for the following reasons. First, no mention is made of BETO Junction on the current I-35 article, not even in the Kansas section of the article. Second, it is a local thing and mention of it would be lost in the whole of the larger article. BETO Juntion has existed in the area since the 1930's as a local landmark, not just a truck stop along an Interstate highway. Third, no other named intersections are mentioned in the I-35 article, what makes this on so special that it needs merged? Why not just mention it in the I-35 article and link to the stub? The article on BETO Junction has not even had a chance to be developed any further and now it will probably get sucked into the larger article and lose the local Kansas flavor it was meant to have. Cuprum17 (talk) 20:47, 2 June 2011 (UTC)
  • Weak Support without prejudice for recreation later if additional information is found. That the I-35 article doesn't mention it now doesn't preclude a merger (in fact, that's what a merger is all about!) If there were an Interstate 35 in Kansas article started, this would be 100% appropriate to merge there. Why don't we start that state-detail article, merge the appropriate content from this article there and expand the s-d article out to C-Class (route description, history, exit list) and call it a day? Note, that doesn't mean we need to do any of this tomorrow or next week, but maybe before Christmas 2011? Imzadi 1979  21:24, 2 June 2011 (UTC)
  • Questions what exactly is the article about? a junction built in the early 1900s? do all old junctions deserve an article? AMAPO (talk) 21:49, 2 June 2011 (UTC)
  • Support - A brief mention of the interchange can be made in this article. Dough4872 01:53, 3 June 2011 (UTC)
The above discussion is preserved as an archive of the proposal. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.
  1. ^ Stuve, Eric. Kansas Highway Guides - Interstate 35. OKRoads. URL accessed 01:23, 25 January 2006 (UTC)
  2. ^ Kansas Turnpike Authority. Belle Plaine Service Area - Travel Information Center. PDF file. URL accessed 03:54, 29 January 2006 (UTC)
  3. ^ Kansas Turnpike Authority. Knute Rockne - The player, the coach, the man. URL accessed 03:54, 29 January 2006 (UTC)
  4. ^ Kennedy, Richie. K-273 Routelog. Kansas Highways 7.0. URL accessed at 02:55, 16 January 2006 (UTC).