We've seen several examples of this recently: Iowa and Missouri creating 27 for the Avenue of the Saints (though only Iowa continues it along U.S. Routes), Iowa extending 163 to Burlington, and Illinois assigning 110 to their piece of the Chicago-Kansas City corridor. The same has been done with US 400, US 412, and perhaps other U.S. Routes. Are there any older examples?
IL/IA-64 so that they meet at the Sabula-Savanna Bridge.
IL-110, IMHO, is one of the sillier ones. Why do we need a Chicago-Kansas City Corridor? We already have I-55 and I-70.
MSR 789 was definitely one of these, though it's mostly been removed except in WY.
There is also MT 3, supposedly to unify the Billings-to-Great Falls route, which I guess US 87 wasn't adequately doing.
I think there are a lot of examples of this nationwide, but I can't think of too many examples in the western states.
Quote from: Brandon on July 17, 2011, 07:59:00 AM
IL-110, IMHO, is one of the sillier ones. Why do we need a Chicago-Kansas City Corridor? We already have I-55 and I-70.
Because I-70 across Missouri is not user friendly and can be pretty unreliable on weekends. But I'm still not sure why a better numbered couldn't have been used such as 336 or a new IL 88 for the section west/south of Quad Cities.
NY 812 appears to be one, given all the multiplexes it has.
I need one of the Louisiana natives to comfirm (or debunk) this, but La 10 appears to be an obvious answer.
I thought you were coming here to mention Ohio's SR 1 (1950s-). I'm not seeing LA 10 being this way - it still goes from Pickering to the state line near Bogalusa, right? It doesn't have any long overlaps, and none at either end - it's just a long route like LA 1 that's not much of a through corridor but a collection of end-to-end routes joined by short overlaps.
I will just add to Revive 755 that Illinois wanted a route for drivers who want to avoid the 1-80 and 1-55 truckways . The tollway liked the idea too of course.
I would have liked Illinois 88 better as well. I dont know wht IA and MO picked 27 . It is out of grid for a fantasy future interstate.
I like the fictional interstate idea of making it I-43 too but that will remain fictional.
I never thought I would be so strongly supporting the idea of the Quincy Highway committee.
How about DE 404 overlapping US 9 in Delaware?
WV 55.
VA 32 north of downtown Suffolk.
Quote from: Brandon on July 17, 2011, 07:59:00 AM
IL/IA-64 so that they meet at the Sabula-Savanna Bridge.
It gets worse. Back in the day (I'd guess '50s and '60s), IA-64 went across the entire state to meet up with NE-64 as well. This includes a 70-mile-long multiplex with US-30 between Cedar Rapids and Marshalltown. The part west of Marshalltown became IA-191, IA-44, and IA-330.
WIS 32. It follows other highway numbers for just about 75% of its and is concurrent along 45 for all of it between Eagle River (or south of it actually) and the U.P.
Wisconsin - in general is home of useless concurrencies.
IL-267 over IL-111 so that IL-267 can meet US-67.
Back in the day, California had Route 21 continuing south of Mission San Jose along what was then Route 9 (now Route 262), so that it could terminate at then-Route 17 (today's I-880).
For some time from 1964 on (but not the case for the last two or so decades), Route 70 continued 30 miles south of Catlett (in Sutter County) to I-5 in the Natomas district of Sacramento in a concurrency with Route 99. (From 1964-1968 it went down 99 all the way to Route 16 in downtown Sacramento at the I Street Bridge - basically because 70 was a direct replacement of the 1950s Route 24 segment to Marysville.)
Route 108 does this with Route 132 in Modesto for several blocks so it can terminate at Route 99.
---
A couple of out-of-state examples:
- in Connecticut, Route 25 continues along Route 8 between Trumbull and Bridgeport to reach I-95.
- Route 1X in Kananaskis, Alberta apparently is concurrent for its entire length with Route 40.
GA 520 on US 82/280 in S GA. Really the SR numbers on US highways in Georgia should be relegated to secret status, as in Florida.
VA 2 with the exception of the portion between Bowling Green and US 17 is entirely multiplexed and goes from Richmond to Fredericksburg, sounds obvious here.
NC 24 for over 100 miles with NC 27, just to connect Charlotte to Fort Bragg and Camp Lejeune. It used to end in Charlotte where NC 27 and US 74 meet, but they rerouted it a few years ago to I-77.
Judging from signage on Los Angeles's Terminal Island, Route 103 ends at the terminus of I-710...while concurrent with Route 47!
http://maps.google.com/maps?q=Terminal+Island,+Los+Angeles,+CA&hl=en&ll=33.759847,-118.234102&spn=0.003581,0.004908&sll=37.0625,-95.677068&sspn=54.928982,80.419922&vpsrc=6&hnear=Terminal+Island&t=m&z=18&layer=c&cbll=33.759847,-118.234102&panoid=XhxLSDoy23iYhpiUgjRikQ&cbp=12,252.05,,1,0.79
http://maps.google.com/maps?q=Terminal+Island,+Los+Angeles,+CA&hl=en&ll=33.75888,-118.237798&spn=0.003581,0.004908&sll=37.0625,-95.677068&sspn=54.928982,80.419922&vpsrc=6&hnear=Terminal+Island&t=m&z=18&layer=c&cbll=33.758923,-118.237647&panoid=D2BdEvVd4YKa3i9nMMHHpg&cbp=12,257,,0,0.79
http://maps.google.com/maps?q=Terminal+Island,+Los+Angeles,+CA&hl=en&ll=33.75881,-118.238236&spn=0.003581,0.004908&sll=37.0625,-95.677068&sspn=54.928982,80.419922&vpsrc=6&hnear=Terminal+Island&t=m&z=18&layer=c&cbll=33.75881,-118.238236&panoid=aMojhryGsz5USubBVOOVlw&cbp=12,267.57,,1,-1.52
Did Ohio's Route 3 predate the US routes that are concurrent with it, or was it created after the fact to link Ohio's three largest cities?
Quote from: 74/171FAN on October 28, 2011, 09:41:07 AM
VA 2 with the exception of the portion between Bowling Green and US 17 is entirely multiplexed and goes from Richmond to Fredericksburg, sounds obvious here.
Except that 2 predates 301.
Quote from: TheStranger on October 28, 2011, 02:03:09 PM
Did Ohio's Route 3 predate the US routes that are concurrent with it, or was it created after the fact to link Ohio's three largest cities?
Yes, 3 was part of the original numbering in the early 1920s.
Quote from: TheStranger on October 28, 2011, 02:03:09 PM
Did Ohio's Route 3 predate the US routes that are concurrent with it, or was it created after the fact to link Ohio's three largest cities?
Predate. US 36 and US 22's overlaps with Oh 3 came in the mid 1930s.
Quote from: Hot Rod Hootenanny on October 28, 2011, 07:49:59 PM
Quote from: TheStranger on October 28, 2011, 02:03:09 PM
Did Ohio's Route 3 predate the US routes that are concurrent with it, or was it created after the fact to link Ohio's three largest cities?
Predate. US 36 and US 22's overlaps with Oh 3 came in the mid 1930s.
How about US 62 – another 1930s addition I believe – and more relevant to OH 3's inclusion in this thread than US 36.
Personally, I don't think the southern half of OH 3 is necessary at all, assuming all the US and Interstate routes are staying as they are. It's not necessary as a Cincinnati—Cleveland route; we have US 42 for that. It's not necessary as a Cincinnati—Columbus—Cleveland route; we have I-71 for that. OH 3 might as well be truncated, with its new south end at Broad & 3rd in Columbus. Then, to preserve continuity of the old route and satisfy roadgeek historians, put up "OLD 3C HWY" markers along the whole length, including the part that's still OH 3. Of course, old alignments that still go through should get these markers.
Or, leave well enough alone, I suppose.
Oklahoma highway 3. I don't know if it or the routes it overlaps came first but most of it west of Oklahoma City is concurrent with other routes. And is there a need for a route from the Colorado state line to southwestern Arkansas?
Quote from: apeman33 on October 28, 2011, 11:15:44 PM
Oklahoma highway 3. I don't know if it or the routes it overlaps came first
https://www.aaroads.com/forum/index.php?topic=5112.0
I never understood US 221's extension to Lynchburg. From Roanoke to Bedford it duplexes with US 460, and east of Bedford it's on 460's old alignment. To me, it would have seemed more logical to just swap 460 and VA 297.
US 25 south of Jesup, GA is not called by locals at all. It is US 341 in Brunswick and probably referred to it the rest of the way to as US 341. What is interesting is at Ludowici, GA; GA 57 continues south of US 84 from US 25 with a "TO I-95" shield there and you wonder why US 25 does not continue along GA 57 to I-95 and end at US 17 in Elonia, GA.
Quote from: NE2 on October 28, 2011, 11:35:17 PM
Quote from: apeman33 on October 28, 2011, 11:15:44 PM
Oklahoma highway 3. I don't know if it or the routes it overlaps came first
https://www.aaroads.com/forum/index.php?topic=5112.0
Or if you don't want to bother with that, I've done the work for you:
http://en.wikipedia.org/wiki/Oklahoma_State_Highway_3#History
Not quite the same, but US 59 is duplexed with other routes from Texarkana, Texas to Heavener, OK. The whole distance within Arkansas is duplexed with other US highways. According to AHTD maps, US 59 does not exist in Arkansas. Also, there are no US 59 sections in Arkansas.
Quote from: dave19 on April 01, 2012, 12:24:00 AM
Quote from: hbelkins on October 27, 2011, 08:40:01 PM
WV 55.
Also WV 92.
Hasn't 92 always run from WSS to Morgantown? At one point it was co-signed with WV 7 into downtown Morgantown, and I've heard there is still some remnant signage along WV 7.
The former AZ 93 was a southern extension of US 93 from Congress Junction (near Wickenburg) was multiplexed with US 89, US 60, US 70, US 80 through Downtown Phoenix, then turned onto AZ 87 and followed what is now AZ 587, I-10, AZ 387, AZ 84 to Tucson and then US 89 all the way to the Mexican border at Nogales.
Quote from: jwolfer on October 28, 2011, 08:20:51 AM
GA 520 on US 82/280 in S GA. Really the SR numbers on US highways in Georgia should be relegated to secret status, as in Florida.
This is actually useful, though, as it indicates a continuous strand of 4-lane highway along a pretty high traffic corridor. If you're going from Columbus or east/central Alabama to Florida east of the panhandle (or to St Simons like I did last week), this is the road to take. Not to mention the section between Richland and Dawson has no overlap, where US 280 and US 82 exit themselves onto 2 lane roads. It makes sense to number this as a continuous route, rather than US 280 to (something) to US 82.
I and many from this area know it as GA 520 or "corridor Z" rather than any of its overlaps.
Hasn't (WV) 92 always run from WSS to Morgantown?
It doesn't on the 1946 map:
http://cartweb.geography.ua.edu:9001/StyleServer/calcrgn?cat=North%20America%20and%20United%20States&item=States/West%20Virginia/WestVirginia1946a.sid&wid=1600&hei=800&props=item(Name,Description),cat(Name,Description)&style=simple/view-dhtml.xsl
It doesn't on the 1965 RMcN atlas I have, either.
Always wondered what the point of that long multiplex was.
Quote from: national highway 1 on April 01, 2012, 07:14:42 PM
The former AZ 93 was a southern extension of US 93 from Congress Junction (near Wickenburg) was multiplexed with US 89, US 60, US 70, US 80 through Downtown Phoenix, then turned onto AZ 87 and followed what is now AZ 587, I-10, AZ 387, AZ 84 to Tucson and then US 89 all the way to the Mexican border at Nogales.
I think that Arizona initially positioned itself for potential future U.S. route extensions with AZ-93 and 95. When they first established AZ-95, U.S. 95 hadn't been extended south into California from Nevada, and the eventual extension over part of AZ-95 south of Quartzite didn't happen until the early 1960s. I would suspect the same motive existed for establishing an AZ-93 south from Kingman, and part of that became U.S. 93, northwest of Wickenberg. Arizona seems to have eventually adopted California's "one route-one number" policy to eliminate most - certainly not all - of its concurrent routes, and with construction of the interstate system, having parallel U.S. routes connecting the same major cities lost its importance.
U90 through a huge chunk of Texas runs concurrently off and on with I-10 to the point that its almost separate roads relabeled to make it still a US highway.
Quote from: Perfxion on April 04, 2012, 01:41:06 PM
U90 through a huge chunk of Texas runs concurrently off and on with I-10 to the point that its almost separate roads relabeled to make it still a US highway.
This relates to the topic how?
Quote from: 3467 on July 18, 2011, 09:18:38 PM
I dont know wht IA and MO picked 27 . It is out of grid for a fantasy future interstate.
Probably because when it was designated in 2001, it was the lowest unused number that both Iowa and Missouri had available.
VA 2 from Richmond to Bowling Green and US 17 to Fredericksburg. It should really only exist from Bowling Green to US 17.
Quote from: vtk on October 28, 2011, 09:05:36 PM
Quote from: Hot Rod Hootenanny on October 28, 2011, 07:49:59 PM
Quote from: TheStranger on October 28, 2011, 02:03:09 PM
Did Ohio's Route 3 predate the US routes that are concurrent with it, or was it created after the fact to link Ohio's three largest cities?
Predate. US 36 and US 22's overlaps with Oh 3 came in the mid 1930s.
How about US 62 – another 1930s addition I believe – and more relevant to OH 3's inclusion in this thread than US 36.
Personally, I don't think the southern half of OH 3 is necessary at all, assuming all the US and Interstate routes are staying as they are. It's not necessary as a Cincinnati—Cleveland route; we have US 42 for that. It's not necessary as a Cincinnati—Columbus—Cleveland route; we have I-71 for that. OH 3 might as well be truncated, with its new south end at Broad & 3rd in Columbus. Then, to preserve continuity of the old route and satisfy roadgeek historians, put up "OLD 3C HWY" markers along the whole length, including the part that's still OH 3. Of course, old alignments that still go through should get these markers.
Or, leave well enough alone, I suppose.
I was told by an ODOT official some years ago that the reason ODOT keeps Ohio 3 as it is is precisely because it was numbered after the old 3-C Highway....US 22 wasn't commissioned in Ohio until the mid-30s as was US 62. The figuring at the time was since 3 was the highway's traditional number, to leave it alone.....and i dont think that will change any out of deference to the locals along the route
They're not technically state highways, but US 270 and US 412 have long overlaps in western Oklahoma. OK 3 does too.
Don't know why I didn't think of this before, but KY 80. I would have to go find and examine old maps to find out which came first, US 68 or KY 80, but there is really no reason KY 80 can't end at Edmonton, where it intersects US 68. If I am not mistaken, some of the westernmost part of KY 80 actually carried another number at one time (KY 58?). Now they are four-laning KY 80 from the western shore of Kentucky Lake (and the famous broken bridge) west to Mayfield to make a better route through western Kentucky to Murray.
At one point KY 80 was a main route across southern Kentucky, but the Cumberland and
Daniel Boone Hal Rogers parkways have supplanted most of it.
I'd be in favor of truncating KY 80 at Edmonton and rerouting US 68 along the new four-lane in the Purchase region, to terminate at US 45 or the Purchase Parkway (Future I-69) at Mayfield. If you're in Hopkinsville or Cadiz, you're going to take I_24 to Paducah, not US 68. But that probably should go in Fictional Highways.
And what about TN 1? :D
Quote from: bugo on April 05, 2012, 08:33:27 PM
They're not technically state highways, but US 270 and US 412 have long overlaps in western Oklahoma. OK 3 does too.
Is there much of US 412 in Arkansas that's not an overlap?
Quote from: hbelkins on April 05, 2012, 09:13:23 PM
And what about TN 1? :D
What about it? It predates the U.S. Highways.
It is also hidden for most (all) of its route. At least in Nashville anyway.
Quote from: 74/171FAN on April 05, 2012, 07:32:08 PM
VA 2 from Richmond to Bowling Green and US 17 to Fredericksburg. It should really only exist from Bowling Green to US 17.
Agree that it should be truncated, but it was created in 1933 and US 301 was added to it in 1941.
Florida/Georgia 121, Minnesota -Idaho 200, Interstate 90 from Chicago to Cleveland (w/I-80) , I-59 from Meridian, MS to Birmingham,AL (w/ I-20)
Quote from: ctsignguy on April 05, 2012, 08:09:21 PM
Quote from: vtk on October 28, 2011, 09:05:36 PM
Quote from: Hot Rod Hootenanny on October 28, 2011, 07:49:59 PM
Quote from: TheStranger on October 28, 2011, 02:03:09 PM
Did Ohio's Route 3 predate the US routes that are concurrent with it, or was it created after the fact to link Ohio's three largest cities?
Predate. US 36 and US 22's overlaps with Oh 3 came in the mid 1930s.
How about US 62 another 1930s addition I believe and more relevant to OH 3's inclusion in this thread than US 36.
Personally, I don't think the southern half of OH 3 is necessary at all, assuming all the US and Interstate routes are staying as they are. It's not necessary as a CincinnatiCleveland route; we have US 42 for that. It's not necessary as a CincinnatiColumbusCleveland route; we have I-71 for that. OH 3 might as well be truncated, with its new south end at Broad & 3rd in Columbus. Then, to preserve continuity of the old route and satisfy roadgeek historians, put up "OLD 3C HWY" markers along the whole length, including the part that's still OH 3. Of course, old alignments that still go through should get these markers.
Or, leave well enough alone, I suppose.
I was told by an ODOT official some years ago that the reason ODOT keeps Ohio 3 as it is is precisely because it was numbered after the old 3-C Highway....US 22 wasn't commissioned in Ohio until the mid-30s as was US 62. The figuring at the time was since 3 was the highway's traditional number, to leave it alone.....and i dont think that will change any out of deference to the locals along the route
http://www.lincolnhighwayoh.com/articles/10-in-search-of-the-three-c-highway
Quote from: leifvanderwall on April 05, 2012, 10:46:33 PM
Florida/Georgia 121, Minnesota -Idaho 200, Interstate 90 from Chicago to Cleveland (w/I-80) , I-59 from Meridian, MS to Birmingham,AL (w/ I-20)
At least for route 200 (ID-MN), that route is for the most part signed with a single designation. There are overlaps to tie its pieces together, but it is nothing like MO/IL-110 or IA/MO-27.
I can see a bunch of these in Oregon (some intentional, some that occurred throughout the years):
(now decommissioned) U.S. 26 from Cannon Beach Junction to Astoria, multiplexed with U.S. 101 to the south end of the Astoria-Megler Bridge and junction with U.S. 30
U.S. 30 - almost entirely multiplexed with I-84 except west of Portland and in some areas as a de facto I-84 business loop
Oregon 47 - multiplexed with U.S. 26 northwest of Banks, it is a single corridor from Clatskanie to McMinnville but functionally two (or even three, if you count Banks-Forest Grove separately) separate highways
Oregon 219 - multiplexed with Oregon 99W in Newberg. North and south of Newberg are functionally different highways; in Woodburn Oregon 219 suddenly becomes Oregon 214 at I-5, and then at Oregon 99E Oregon 217 is multiplexed with 99E for a short distance within Woodburn while continuing straight through 99E puts you on Oregon 211
Business 99E - Multiplexed with Oregon 22 from downtown Salem to I-5; the historic route of Oregon 99E is Commercial Street.
U.S. 20/Oregon 34 from Lebanon to Philomath. U.S. 20 takes a northerly route through Albany while Oregon 34 is routed onto an expressway. Oregon 34 and U.S. 30 are then multiplexed from Corvallis to Philomath before 34 becomes a separate route through the Coast Range. (U.S. 20 should become "Business U.S. 20" or "Alternate U.S. 20", except Oregon doesn't use Alternate) and Oregon 34 should be U.S. 20 or even "Bypass U.S. 20", IMO.)
Interstate 105/Oregon 126. I-105 only exists from downtown Eugene to I-5 but Oregon 126 continues as a freeway through Springfield and to the west of Eugene to the coast.
In north-central Oregon, Oregon 19, 74, 206 and 207 have some interesting multiplexes with each other but I'm not familiar with the functions of those roads.
U.S. 395 seems to be a hodgepodge of roads - multiplexing with U.S. 20, U.S. 26 and I-84 as it acts as several separate north-south highways. Further north in Washington, U.S. 395 is multiplexed with I-90 for a considerable distance between Ritzville and Spokane, and with I-82 between the Tri-Cities and I-84 near Hermiston back in Oregon.
A fictional example which I think has merit: OH 1, v3 (https://www.aaroads.com/forum/index.php?topic=6441.0) (discuss in that thread rather than here, please)
The MA 128/I-95 overlap between Peabody and Canton, which has been retained for almost 40 years due largely for political and "historical" reasons, is IMO one of the most unnecessary overlaps in existence on the Interstate system to date.
And yet it doesn't fit this thread, since Route 128 long predates I-95.
Another good example from the Sooner State is OK 9. It could end at US 59 but is duplexed with US 59 and US 271 to the Arkansas line.
Quote from: Hot Rod Hootenanny on July 18, 2011, 08:03:43 PM
I need one of the Louisiana natives to comfirm (or debunk) this, but La 10 appears to be an obvious answer.
Debunked, LA 10 was created from older State Routes when the highways were renumbering in 1955. Examples are (according to my 1953 highway map) SR 22, 27, and 35. They just named it LA 10 as the highways were numbered 2, 4, 6, 8, and 10 from north to south.
In Erie PA, PA 290 was created to give the Bayfront Connector a number - to give traffic coming from the east a number to follow to get to downtown. It starts at I-90 and multiplexes with PA 430 until the new Bayfront Connector, and then PA 290 is routed on the new road. Instead of signing the PA 430 exit with TO PA 290, it's actually a duplex.
THEN, PA 290 duplexes with PA 5 west through Downtown Erie. PA 290 ends at I-79 but PA 5 continues.
So, both ends of PA 290 are duplexed, and a little more than half it's length are duplexed. I kinda get the PA 430 issue, but I'm not sure why PA 290 was extended along PA 5. It's almost like they wanted PA 290 to then be signed on I-79 to reconnect back to I-90.
Quote from: NE2 on April 06, 2012, 05:45:33 PM
And yet it doesn't fit this thread, since Route 128 long predates I-95.
Maybe Bostonians think of I-95 as the "useless" overlap to give a corridor one number ;-)
I drove US 69 through Kansas a few weeks back and noticed that between the Oklahoma State Line and Columbus, that K-7 is signed concurrent with the US route even though it doesn't need to be. I am assuming that KDOT wants K-7 to exist as a complete N-S route from border to border and considers it tp be one long corridor.
Quote from: SSOWorld on October 27, 2011, 09:46:39 PM
WIS 32. It follows other highway numbers for just about 75% of its and is concurrent along 45 for all of it between Eagle River (or south of it actually) and the U.P.
Wisconsin - in general is home of useless concurrencies.
And WI-34 duplex with WI-13 in Portage County.
Quote from: roadman65 on October 27, 2011, 08:32:24 PM
How about DE 404 overlapping US 9 in Delaware?
It depends how many Baltimore/DC people haven't figured out that MD / DE 404 is the road to (almost) get to the beaches.
US 9 was a relatively late addition to Delaware. It used to end in Cape May NJ, before it was extended past the end of the Cape May Lewes Ferry to US 13. I believe it superceded existing state routes, but I'd have to look at old maps since I don't know that part of the state as well as Wilmington area.
SH 130 in Texas. Was originally supposed to end at I-10 in Seguin, but was then "extended" over I-10 and I-410 to I-35 in San Antonio. There's also a brief overlap with SH 45 in Austin and US 183 south of Austin (technically?) but I don't know if those count.
Also not a state highway but US 74 overlapping with I-75 from Chattanooga to Cleveland, Tennessee.
Quote from: tmoore952 on September 25, 2023, 06:00:44 PM
Quote from: roadman65 on October 27, 2011, 08:32:24 PM
How about DE 404 overlapping US 9 in Delaware?
It depends how many Baltimore/DC people haven't figured out that MD / DE 404 is the road to (almost) get to the beaches.
US 9 was a relatively late addition to Delaware. It used to end in Cape May NJ, before it was extended past the end of the Cape May Lewes Ferry to US 13. I believe it superceded existing state routes, but I'd have to look at old maps since I don't know that part of the state as well as Wilmington area.
US 9 did supersede existing state routes--DE 28 from Laurel to Georgetown and DE 18 from Georgetown to Five Points. It was in 1974 that US 9 was extended from Cape May to Laurel.
Quote from: Some one on September 25, 2023, 11:33:17 PM
SH 130 in Texas. Was originally supposed to end at I-10 in Seguin, but was then "extended" over I-10 and I-410 to I-35 in San Antonio. There's also a brief overlap with SH 45 in Austin and US 183 south of Austin (technically?) but I don't know if those count.
Also not a state highway but US 74 overlapping with I-75 from Knoxville to Cleveland, Tennessee.
You meant Chattanooga, correct?
I have written my opinion about this particular "useless" overlap in another thread. I believe that the national western terminus for US 74 should be at the I-75/Bypass US 64 interchange in Cleveland (Exit 20). The "useless"
and unsigned 18 mile overlap is just so US 74 could be considered to have a terminus in Chattanooga as the I-75/I-24 interchange is technically within the city limits. Once a motorist reaches I-75 there at the Exit 20 interchange, there are signs directing the motorist to Chattanooga. US 74 does not need to be considered to proceed any further than the Exit 20 interchange. US 74 has "done its job" of getting a motorist from the Asheville and the western NC area to Chattanooga and should have its national western terminus there, which it appears to do as it is unsigned along I-75 and is signed at the off-ramp for Exit 20.
Quote from: amroad17 on September 26, 2023, 03:32:11 AM
Quote from: Some one on September 25, 2023, 11:33:17 PM
SH 130 in Texas. Was originally supposed to end at I-10 in Seguin, but was then "extended" over I-10 and I-410 to I-35 in San Antonio. There's also a brief overlap with SH 45 in Austin and US 183 south of Austin (technically?) but I don't know if those count.
Also not a state highway but US 74 overlapping with I-75 from Knoxville to Cleveland, Tennessee.
You meant Chattanooga, correct?
I have written my opinion about this particular "useless" overlap in another thread. I believe that the national western terminus for US 74 should be at the I-75/Bypass US 64 interchange in Cleveland (Exit 20). The "useless" and unsigned 18 mile overlap is just so US 74 could be considered to have a terminus in Chattanooga as the I-75/I-24 interchange is technically within the city limits. Once a motorist reaches I-75 there at the Exit 20 interchange, there are signs directing the motorist to Chattanooga. US 74 does not need to be considered to proceed any further than the Exit 20 interchange. US 74 has "done its job" of getting a motorist from the Asheville and the western NC area to Chattanooga and should have its national western terminus there, which it appears to do as it is unsigned along I-75 and is signed at the off-ramp for Exit 20.
There's really no need for the entire US 64/74 concurrency in either Tennessee or North Carolina, especially since a decent amount of the route in Tennessee has not yet been upgraded to ADHS standards. Just truncate US 74 back to the last point where it doesn't have a concurrency and sign Chattanooga as a destination.
Quote from: amroad17 on September 26, 2023, 03:32:11 AM
Quote from: Some one on September 25, 2023, 11:33:17 PM
SH 130 in Texas. Was originally supposed to end at I-10 in Seguin, but was then "extended" over I-10 and I-410 to I-35 in San Antonio. There's also a brief overlap with SH 45 in Austin and US 183 south of Austin (technically?) but I don't know if those count.
Also not a state highway but US 74 overlapping with I-75 from Knoxville to Cleveland, Tennessee.
You meant Chattanooga, correct?
I have written my opinion about this particular "useless" overlap in another thread. I believe that the national western terminus for US 74 should be at the I-75/Bypass US 64 interchange in Cleveland (Exit 20). The "useless" and unsigned 18 mile overlap is just so US 74 could be considered to have a terminus in Chattanooga as the I-75/I-24 interchange is technically within the city limits. Once a motorist reaches I-75 there at the Exit 20 interchange, there are signs directing the motorist to Chattanooga. US 74 does not need to be considered to proceed any further than the Exit 20 interchange. US 74 has "done its job" of getting a motorist from the Asheville and the western NC area to Chattanooga and should have its national western terminus there, which it appears to do as it is unsigned along I-75 and is signed at the off-ramp for Exit 20.
Oops, yeah fixed it.
What about US 50/400 in SE Colorado?
Seems like 400 just .. ends around .. what is it, Lamar?
Quote from: zachary_amaryllis on September 30, 2023, 06:44:50 AM
What about US 50/400 in SE Colorado?
Seems like 400 just .. ends around .. what is it, Lamar?
What about the OP?
This was the intent for Utah 30, which got designated over three separate state route corridors (70, 102-69, and 3-51) connected by concurrencies on US 30S and US 89. The three Idaho border counties had wanted one route number to cross the state from Nevada to Wyoming. After several unsuccessful attempts to get a US highway on that corridor, the state created SR 30 on it, both to match with the route number it connected to in Nevada and also because all of their US highway proposals had used a number derived from US 30. That created a fairly long US 30S/SR 30 overlap...definitely not confusing at all...
I'm not sure if either of the overlaps were ever signed well. There is some implied concurrency signage in Logan now but that's about it. For all intents and purposes, Utah has three SR 30s.