What's the longest stretch of a single interstate where you can't find any of its own child routes? I think it's I-40 from I-240 in OKC all the way to California. The longest 2di that isn't a parent to anything I think is I-39. Another long stretch is I-90 west of Rapid City. The east coast winner I think is I-91 north of Chicopee, MA. Anything else notable?
Until 2003, 560 miles on I-95 from Jacksonville FL to Petersburg VA.
QuoteUntil 2003, 560 miles on I-95 from Jacksonville FL to Petersburg VA.
Ahead of that would be the ~636 miles on I-64 between Louisville, KY and Hampton, VA since the OP is referring to an Interstate's own child routes. Even if you factor in I-295 Richmond and I-265 Louisville, it's still over 540 miles.
Close behind would be I-81...~540 miles between Roanoke, VA and Syracuse, NY.
Quote from: froggie on August 28, 2013, 06:12:22 AM
Ahead of that would be the ~636 miles on I-64 between Louisville, KY and Hampton, VA since the OP is referring to an Interstate's own child routes. Even if you factor in I-295 Richmond and I-265 Louisville, it's still over 540 miles.
That's the one that I immediately thought of.
I would suspect I-90 would be close, twice. Once from Seattle to Rapid City; the second from Rapid City to the Chicagoland area.
Them having the full boat in New York would make up for that. :-)
Quote from: exit322 on August 28, 2013, 11:22:20 AM
I would suspect I-90 would be close, twice. Once from Seattle to Rapid City; the second from Rapid City to the Chicagoland area.
Them having the full boat in New York would make up for that. :-)
From the early 1980s (when I-880 disappeared from Sacramento) until I-580 to Carson City came along, I-80 between the Bay Area and Cheyenne had no 3di's, although if you want to argue against the "phantom" I-180 and all of its quirks, then you can say the stretch between Reno and Lincoln, NE has no real 3di's.
I-10 from El Paso, TX (110) to Redlands, CA (210) is about 743 miles without intersecting a child route. If we discount I-110 (It's less than a mile long) and I-210 (I still don't think it's signed as an Interstate, although I could be wrong), It grows to 1,341 miles from LA (710) to San Antonio (410).
I-40 goes 1,228 miles between its terminus in Barstow and I-240 in OKC.
Personally, I'd be hesitant to include I-90 from Seattle to Rapid City. It has I-115 in Montana where it's concurrent with I-15.
I-88 and I-89 have no 3dis except for I-189 at the very northern end of I-89.
I-87 north of I-787 has no 3dis.
If and when I-49 gets completely built from downtown New Orleans to Kansas City, the results are about 900 miles. This is assuming that 49 gets built through downtown Shreveport instead of on the loop resulting in a I-149 spur or the like.
I wonder what is longer out west: I-505 to I-105, or I-205 to I-405.
I-81, between Syracuse, NY (I-481), and Roanoke, VA (I-581), is about 535 miles, and the only child it meets is I-380 in Scranton.
534 miles on I-10 between I-110 El Paso and I-410 San Antonio - and the best part, it's all in one state. :)
Quote from: Urban Prairie Schooner on August 28, 2013, 01:21:43 PM
534 miles on I-10 between I-110 El Paso and I-410 San Antonio - and the best part, it's all in one state. :)
and in the other direction, it's 797 miles to the next one: I-710 in Los Angeles.
I think I-210 was pointed out, but I don't believe it is I-210 quite yet.
Quote from: Thing 342 on August 28, 2013, 11:33:54 AM
I-10 from El Paso, TX (110) to Redlands, CA (210) is about 743 miles without intersecting a child route. If we discount I-110 (It's less than a mile long) and I-210 (I still don't think it's signed as an Interstate, although I could be wrong), It grows to 1,341 miles from LA (710) to San Antonio (410).
Why not count the Texas Interstate 110? It is signed now.
Officially, the longest interstate without a 3di is Interstate 57.
Quote from: agentsteel53 on August 28, 2013, 12:53:05 PM
I wonder what is longer out west: I-505 to I-105, or I-205 to I-405.
Longer stretch is I-505 to I-105.
By my rough calculations using exit numbers the California segment is 244 miles long (797-553=244, CA/OR Stateline to Exit 553/I-505) while the Oregon segment is 194 miles (I-105 is Exit 194) for a total distance of 438 miles.
In contrast, the distance from I-205 (Exit 458) to I-405 (Exit 158) is only 300 miles.
Notable is Interstate 25 from its beginning in Las Cruces to Interstate 225 in Denver at 662 miles.
QuotePersonally, I'd be hesitant to include I-90 from Seattle to Rapid City. It has I-115 in Montana where it's concurrent with I-15.
The OP specifically mentioned a given route's "child" 3dis. Given that, I-115 wouldn't count in the I-90 case.
QuoteI-81, between Syracuse, NY (I-481), and Roanoke, VA (I-581), is about 535 miles, and the only child it meets is I-380 in Scranton.
I'd mentioned I-81 previously. Plus you forget I-476. :o)
Quote from: froggie on August 28, 2013, 02:35:12 PM
QuotePersonally, I'd be hesitant to include I-90 from Seattle to Rapid City. It has I-115 in Montana where it's concurrent with I-15.
The OP specifically mentioned a given route's "child" 3dis. Given that, I-115 wouldn't count in the I-90 case.
Right, but this is sort of a special case, I'd think. Like I'm not talking about it merely intersecting some other route's 3di; I-115 branches off I-90 just as much as it does I-15, you'd only not recognize it as a child due to a numbering quirk. (Plus, it's cosigned with BL I-90, so it's still a child of 90 in that sense.)
But I do see the point of the OP, and I agree that there are shockingly few x90s for a route of its length.
Quote from: Alex on August 28, 2013, 02:22:35 PM
Notable is Interstate 25 from its beginning in Las Cruces to Interstate 225 in Denver at 662 miles.
And from I-225 to its end in Buffalo WY there is another 400 miles without any x25. I-225 is the only I-x25 in existence unless I'm missing something.
I-45 all the way. Its only 3di, unsigned I-345, starts where I-45 ends.
Interstates that should be excluded from this discussion, IMHO.
Interstates without a 3di: 2, 4, 8, 12, 17, 19, 27, 37, 39, 41, 43, 49, 57, 66, 68, 73, 86, 88, 97, 99
Interstates with only one current 3di (signed or unsigned) or other 3dis that branch of the one 3di that actually connects to the parent: 16, 24, 25, 26, 44, 45, 69 (yes, others are in the future), 72, 74, 78 (none of them actually meet their parent), 79, 82, 83, 89
These could theoretically be infinite between child 3dis.
I-69 creates no 3dis between Ft. Worth and Sarnia. (There is I-496 in Lansing, and I-475 in Flint)
I-84 creates no 3dis between Portland and Boise.
I-5 creates no 3dis between Springfield and Manteca. (There is I-180/80B in Sacramento)
Quote from: TEG24601 on August 28, 2013, 07:40:22 PM
I-5 creates no 3dis between Springfield and Manteca. (There is I-180/80B in Sacramento)
I-80 Biz is I-305. And there's I-505 to the north.
Quote from: Brandon on August 28, 2013, 05:34:23 PM
Interstates that should be excluded from this discussion, IMHO.
Interstates without a 3di: 2, 4, 8, 12, 17, 19, 27, 37, 39, 41, 43, 49, 57, 66, 68, 73, 86, 88, 97, 99
Interstates with only one current 3di (signed or unsigned) or other 3dis that branch of the one 3di that actually connects to the parent: 16, 24, 25, 26, 44, 45, 69 (yes, others are in the future), 72, 74, 78 (none of them actually meet their parent), 79, 82, 83, 89
These could theoretically be infinite between child 3dis.
I-26 has I-126 and I-526
Mapmikey
Entire length of I-57 from the Dan Ryan in Chicago to it's terminus at I-55. Entire stretch, least until they finish the interchange with I-294
Quote from: TEG24601 on August 28, 2013, 07:40:22 PM
I-69 creates no 3dis between Ft. Worth and Sarnia. (There is I-496 in Lansing, and I-475 in Flint)
I-84 creates no 3dis between Portland and Boise.
I-5 creates no 3dis between Springfield and Manteca. (There is I-180/80B in Sacramento)
I-269 is a thing, so there goes your argument.
Also, I-84 has no children between I-184 in Idaho and I-684 in NY.
I-74 has no children between I-474 in Illinois and I-95 in North Carolina. :bigass:
Quote from: TEG24601 on August 28, 2013, 07:40:22 PM
I-69 creates no 3dis between Ft. Wayne and Sarnia. (There is I-496 in Lansing, and I-475 in Flint)
FTFY.
This is the opposite: I-38 has a grand total of zero miles, yet it has a 3di :sombrero:.
Quote from: CNGL-Leudimin on August 29, 2013, 07:12:19 AM
Quote from: TEG24601 on August 28, 2013, 07:40:22 PM
I-69 creates no 3dis between Ft. Wayne and Sarnia. (There is I-496 in Lansing, and I-475 in Flint)
FTFY.
This is the opposite: I-38 has a grand total of zero miles, yet it has a 3di :sombrero:.
Dude! That is hillarious.
I-95 has none ( I mean none currently) between I-795 in North Carolina to I-295 in Jacksonville, FL. Even when I-295 is officially bannered in North Carolina it will still be a long way from Jacksonville to Fayetteville.
Quote from: TEG24601 on August 28, 2013, 07:40:22 PM
I-5 creates no 3dis between Springfield and Manteca. (There is I-180/80B in Sacramento)
It's unsigned (and only acknowledged by FHWA) I-305 in Sacramento (there's no 180 in California).
Quote from: Steve on August 28, 2013, 09:26:53 PM
Quote from: TEG24601 on August 28, 2013, 07:40:22 PM
I-69 creates no 3dis between Ft. Worth and Sarnia. (There is I-496 in Lansing, and I-475 in Flint)
I-84 creates no 3dis between Portland and Boise.
I-5 creates no 3dis between Springfield and Manteca. (There is I-180/80B in Sacramento)
I-269 is a thing, so there goes your argument.
I-69 doesn't go to Fort Worth; I think he means Fort Wayne, which has I-469.
Quote from: bulldog1979 on August 29, 2013, 11:22:08 AM
Quote from: Steve on August 28, 2013, 09:26:53 PM
Quote from: TEG24601 on August 28, 2013, 07:40:22 PM
I-69 creates no 3dis between Ft. Worth and Sarnia. (There is I-496 in Lansing, and I-475 in Flint)
I-84 creates no 3dis between Portland and Boise.
I-5 creates no 3dis between Springfield and Manteca. (There is I-180/80B in Sacramento)
I-269 is a thing, so there goes your argument.
I-69 doesn't go to Fort Worth; I think he means Fort Wayne, which has I-469.
I thought when I first read it that there was a complete reallignment to the Texas portion of I-69
I-77 between Charlotte and Akron has no 3di's in between; it is notable that both cities have the same number, I-277!
I-80 between Reno (I-580) and Cheyenne (the maligned "I-180"): 953 miles.
Without "I-180", it would be 1438 miles to I-680 in Omaha.
Quote from: Mark68 on September 05, 2013, 05:52:03 AM
I-80 between Reno (I-580) and Cheyenne (the maligned "I-180"): 953 miles.
Without "I-180", it would be 1438 miles to I-680 in Omaha.
Exactly!
Quote from: Henry on September 18, 2013, 12:11:21 PM
Quote from: Mark68 on September 05, 2013, 05:52:03 AM
I-80 between Reno (I-580) and Cheyenne (the maligned "I-180"): 953 miles.
Without "I-180", it would be 1438 miles to I-680 in Omaha.
Exactly!
nah, rounded to the nearest mile or so.
Quote from: bulldog1979 on August 29, 2013, 11:22:08 AM
Quote from: Steve on August 28, 2013, 09:26:53 PM
Quote from: TEG24601 on August 28, 2013, 07:40:22 PM
I-69 creates no 3dis between Ft. Worth and Sarnia. (There is I-496 in Lansing, and I-475 in Flint)
I-84 creates no 3dis between Portland and Boise.
I-5 creates no 3dis between Springfield and Manteca. (There is I-180/80B in Sacramento)
I-269 is a thing, so there goes your argument.
I-69 doesn't go to Fort Worth; I think he means Fort Wayne, which has I-469.
I did mean Ft. Wayne. I was distracted by a conversation in the office at that time.
Did anyone mention Interstate 40 from Barstow going east through California, Arizona, New Mexico, Texas, and all the way to the east side of Oklahoma City where it spawns Interstate 240. 1,230 miles.
Quote from: Mark68 on September 05, 2013, 05:52:03 AM
I-80 between Reno (I-580) and Cheyenne (the maligned "I-180"): 953 miles.
Without "I-180", it would be 1438 miles to I-680 in Omaha.
I'd say it would be less. You forgot about I-180 in Lincoln, Nebraska.
Quote from: bassoon1986 on August 28, 2013, 12:14:12 PM
If and when I-49 gets completely built from downtown New Orleans to Kansas City, the results are about 900 miles. This is assuming that 49 gets built through downtown Shreveport instead of on the loop resulting in a I-149 spur or the like.
I expect MO 249 will eventually be I-249.
Quote from: Mapmikey on August 28, 2013, 07:46:48 PM
Quote from: Brandon on August 28, 2013, 05:34:23 PM
Interstates that should be excluded from this discussion, IMHO.
Interstates without a 3di: 2, 4, 8, 12, 17, 19, 27, 37, 39, 41, 43, 49, 57, 66, 68, 73, 86, 88, 97, 99
Interstates with only one current 3di (signed or unsigned) or other 3dis that branch of the one 3di that actually connects to the parent: 16, 24, 25, 26, 44, 45, 69 (yes, others are in the future), 72, 74, 78 (none of them actually meet their parent), 79, 82, 83, 89
These could theoretically be infinite between child 3dis.
I-26 has I-126 and I-526
Mapmikey
Correctamundo. I-126 is spawned west of downtown Columbia, SC, while I-526 is a beltway of sorts around Charleston, SC.
I-25 from I-10 in Las Cruces & I-225 in Denver is 613 miles.
From I-225 to I-90 in Buffalo, WY is another 400 miles.
Without I-225, I-25 would have over a thousand miles with no 3dis.
Quote from: akotchi on August 28, 2013, 01:01:41 PM
I-81, between Syracuse, NY (I-481), and Roanoke, VA (I-581), is about 535 miles, and the only child it meets is I-380 in Scranton.
I-380 could have been a child of I-81, as it originally was I-81E.
As it connects two mainline Interstate highways, it probably should have had an even prefix.
I-281.
I-94 between Bismark (194) and Minneapolis (494) is about 426 miles.
Quote from: exit322 on August 28, 2013, 11:22:20 AM
I would suspect I-90 would be close, twice. Once from Seattle to Rapid City; the second from Rapid City to the Chicagoland area.
There are plans to eventually make US 52 from I-90 south of Rochester to Minneapolis into an Interstate-grade freeway, as a child route of I-90. There's one section gone.
Quote from: X99 on March 21, 2019, 09:20:25 PM
Quote from: exit322 on August 28, 2013, 11:22:20 AM
I would suspect I-90 would be close, twice. Once from Seattle to Rapid City; the second from Rapid City to the Chicagoland area.
There are plans to eventually make US 52 from I-90 south of Rochester to Minneapolis into an Interstate-grade freeway, as a child route of I-90. There's one section gone.
MnDOT has never said they plan to pursue an interstate designation for that corridor.
Quote from: TheHighwayMan394 on March 22, 2019, 12:08:13 AM
Quote from: X99 on March 21, 2019, 09:20:25 PM
Quote from: exit322 on August 28, 2013, 11:22:20 AM
I would suspect I-90 would be close, twice. Once from Seattle to Rapid City; the second from Rapid City to the Chicagoland area.
There are plans to eventually make US 52 from I-90 south of Rochester to Minneapolis into an Interstate-grade freeway, as a child route of I-90. There's one section gone.
MnDOT has never said they plan to pursue an interstate designation for that corridor.
And actually, that section of US 52 is fine as-is with no interstate designation. It flows well, and has got to be one of my favorite sections of US highway. The freeway through Rochester is super clean and modern.
If it ever was to become an interstate, I would rather a 2di than a 3di, considering it carries plenty of long distance traffic (in my case the last leg of a 16 hour journey), and it connects Minnesota's third-largest metro area to the Twin Cities.
I-75 doesn't have any in Michigan north of I-675. That's 240 miles from the northern end of I-675 to the northern terminus.
I-75 again doesn't have any between I-475 in Georgia and I-275 in Florida. A stretch of 355 miles.
Quote from: NE2 on August 28, 2013, 07:43:51 PM
Quote from: TEG24601 on August 28, 2013, 07:40:22 PM
I-5 creates no 3dis between Springfield and Manteca. (There is I-180/80B in Sacramento)
I-80 Biz is I-305. And there's I-505 to the north.
Business 80 only exists on CA-51 but that is subjected to become a 3d State route of I-7 or I-9 just in case CA-99 gets interstate status from Kern County to Sacramento.
I think that US-52 between the Twin Cities and Rochester is fine as well. I haven't been on that highway in that stretch in probably about 10 years or so but used it a lot to get between Minneapolis and Rochester and vice versa and it was fine. Just thinking in my head and not looking at a map I had thought that I-35 would have been the way to go to Rochester but then after looking at a map and US-52 I figured out why it was better to take US-52.
If an I- was sought, it makes more sense to give it another x94. No one from MSP is using 52/90 to go to Wisconsin.
Quote from: TheHighwayMan394 on March 22, 2019, 08:20:02 PM
If an I- was sought, it makes more sense to give it another x94. No one from MSP is using 52/90 to go to Wisconsin.
They are if they're going to La Crosse and parts of SW Wisconsin.
I think the x94 designation is a good idea if MnDOT wants to upgrade all of US 52 from St. Paul to Rochester into a freeway in the future.
Heh. I forgot there's other stuff besides Madison for people to go to. Weird.
Quote from: MantyMadTown on March 22, 2019, 09:26:00 PM
Quote from: TheHighwayMan394 on March 22, 2019, 08:20:02 PM
If an I- was sought, it makes more sense to give it another x94. No one from MSP is using 52/90 to go to Wisconsin.
They are if they're going to La Crosse and parts of SW Wisconsin.
I think the x94 designation is a good idea if MnDOT wants to upgrade all of US 52 from St. Paul to Rochester into a freeway in the future.
Yeah I was thinking of that. What if they are going to La Crosse?
I-91 has no children between Chicopee, MA and the Canadian border (about 222 miles). Eastern I-84 has no children until you're 3 miles short of crossing 2 states (about 123 miles)
Quote from: MantyMadTown on March 22, 2019, 09:26:00 PM
Quote from: TheHighwayMan394 on March 22, 2019, 08:20:02 PM
If an I- was sought, it makes more sense to give it another x94. No one from MSP is using 52/90 to go to Wisconsin.
They are if they're going to La Crosse and parts of SW Wisconsin.
I think the x94 designation is a good idea if MnDOT wants to upgrade all of US 52 from St. Paul to Rochester into a freeway in the future.
Don't forget the I-90/US 52 interchange itself, it is NOT fully up to I-standards and would have to be rebuilt in a manner similar to what WisDOT is now doing at I-39/90/I-43/WI 81 in Beloit, WI.
Mike
Quote from: mgk920 on March 23, 2019, 10:01:11 AM
Quote from: MantyMadTown on March 22, 2019, 09:26:00 PM
Quote from: TheHighwayMan394 on March 22, 2019, 08:20:02 PM
If an I- was sought, it makes more sense to give it another x94. No one from MSP is using 52/90 to go to Wisconsin.
They are if they're going to La Crosse and parts of SW Wisconsin.
I think the x94 designation is a good idea if MnDOT wants to upgrade all of US 52 from St. Paul to Rochester into a freeway in the future.
Don't forget the I-90/US 52 interchange itself, it is NOT fully up to I-standards and would have to be rebuilt in a manner similar to what WisDOT is now doing at I-39/90/I-43/WI 81 in Beloit, WI.
Mike
At least that's a cloverleaf - the 52/90 one is a parclo.
Quote from: bugo on September 19, 2013, 12:30:24 AM
Quote from: bassoon1986 on August 28, 2013, 12:14:12 PM
If and when I-49 gets completely built from downtown New Orleans to Kansas City, the results are about 900 miles. This is assuming that 49 gets built through downtown Shreveport instead of on the loop resulting in a I-149 spur or the like.
I expect MO 249 will eventually be I-249.
I-49 should actually be realigned along MO-249 with a new alignment connection on the north end to where I-49 has the 90 degree turns north of Carthage. Even as it is, it's faster than taking the shared I-44 segment, and that's with a set of traffic lights to get back on I-49.
Quote from: MikieTimT on March 23, 2019, 10:40:46 AM
Quote from: bugo on September 19, 2013, 12:30:24 AM
Quote from: bassoon1986 on August 28, 2013, 12:14:12 PM
If and when I-49 gets completely built from downtown New Orleans to Kansas City, the results are about 900 miles. This is assuming that 49 gets built through downtown Shreveport instead of on the loop resulting in a I-149 spur or the like.
I expect MO 249 will eventually be I-249.
I-49 should actually be realigned along MO-249 with a new alignment connection on the north end to where I-49 has the 90 degree turns north of Carthage. Even as it is, it's faster than taking the shared I-44 segment, and that's with a set of traffic lights to get back on I-49.
Yeah, to me that stretch doesn't make sense. I think it would be better to upgrade the I-49/MO-249 interchange and make the current I-49 stretch a spur.
Quote from: MantyMadTown on March 22, 2019, 09:26:00 PM
Quote from: TheHighwayMan394 on March 22, 2019, 08:20:02 PM
No one from MSP is using 52/90 to go to Wisconsin.
They are if they're going to La Crosse and parts of SW Wisconsin.
I think I've actually done something similar while heading from MSP to Madison (and Chicago), although the details are a bit fuzzy in my memory. As I recall, traffic was all jammed up on I-494 in Bloomington. I realized that right after it was too late to take I-35W south as an alternate route, so I instead got immediately over and took 3 of the 4 loop ramps to get on southbound I-35W
anyway. At Medford I headed east on a combination of county highways until I eventually hit US-14 somewhere west of Rochester. From there, I took I-90 to Tomah and rejoined my usual route.
Quote from: TheHighwayMan394 on March 22, 2019, 08:20:02 PMNo one from MSP is using 52/90 to go to Wisconsin.
I have. Especially when my parents lived in the south Metro...
Quote from: froggie on March 25, 2019, 09:28:11 PM
Quote from: TheHighwayMan394 on March 22, 2019, 08:20:02 PMNo one from MSP is using 52/90 to go to Wisconsin.
I have. Especially when my parents lived in the south Metro...
Yep, same here (except with my grandparents). In fact that is the recommended route from my home in Upstate NY to their home in Lakeville, MN.
Quote from: webny99 on March 25, 2019, 09:44:09 PM
Quote from: froggie on March 25, 2019, 09:28:11 PM
Quote from: TheHighwayMan394 on March 22, 2019, 08:20:02 PMNo one from MSP is using 52/90 to go to Wisconsin.
I have. Especially when my parents lived in the south Metro...
Yep, same here (except with my grandparents). In fact that is the recommended route from my home in Upstate NY to their home in Lakeville, MN.
That makes sense considering Lakeville is south of the Twin Cities.