Which 2dus get roasted the most/least?

[SkyPesos]

After looking through the Unpopular US Route opinions thread, and the Which 2dis get roasted the most/least thread, here's one for 2 digit US routes. This is mostly from what I see on the forum. I don't know enough information about half of the routes, so going to need help filling the blanks in.

1 - Some have issues with it running more inland between Jacksonville and NYC.
2 - Split into two segments by Canada, though I have no issues with it
3 - MA 3 should've been a part of it
4 -
5 - Parallel with I-91 for its entire length
6 - Out of grid placement, parallels an interstate for most of its length, former routing in CA is a straight N-S
7 -
8 -
9 - Parallels I-87 north of NYC
10 -
11 - Parallel with an interstate south of Watertown
12 -
13 - Mostly east of US 1
14 - Parallel with I-90 for most of its length
15 - Unnecessary truncation from Rochester
16 - Short, too many concurrencies
17 - Mostly east of US 1
18 -
19 - Suffixed split, parallels I-79 north of Sutton, WV
20 - Yellowstone gap
21 - Parallels I-77 north of Columbia, SC
22 - Parallels I-78 from Harrisburg eastward
23 - Long concurrency with US 1 before ending
24 - Mostly out of grid, as it's between US 36 and US 40 for most of its length
25 - Suffixed split
26 -
27 - "Why does US 127 go to Michigan over US 27?"
29 - Parallels I-85 south of Greensboro
30 - Parallels interstates for a good portion of its length
31 - Suffixed split, parallels I-65 entirely south of Indianapolis
33 - Odd number for E-W route
34 -
35 - Odd number for E-W route
36 - Doesn't seem to have that much criticism. It's far away enough from I-70 to have its own use. Concurrency with I-72 in IL, though that's a short portion.
40 - Parallels I-70 for most of its length
41 - Parallels an interstate for most of its length, east of US 31 south of Nashville (I have no issues with the latter). Got replaced by a state route expressway (IN 63) for through traffic in Indiana; I have no issue with that either.
42 - Even number for N-S route, parallels I-71 for most of its length
43 - Almost intrastate
44 - Out of grid placement
45 - Suffixed split
46 - Out of grid placement, almost intrastate, parallels I-80 for its length
48 - Out of grid placement (between US 50 and US 60), incomplete
49 - Suffixed split
50 - Doesn't seem to have that much criticism. Only a small fraction of the 3000 mile route parallels an interstate. It got replaced by parallel 4 lane expressways (OH 32 and Corridor H) through the Appalachians, though I haven't seen any issue with that.
51 - Parallels interstates for most of its length
52 - Long diagonal
53 -
54 -
56 - Concurrent with US 412 from western terminus to east of Boise City, OK, though I think this is 412's issue, as 56 was first on this segment.
57 - E-W routing, out of grid placement, intrastate
58 - Out of grid placement (entirely south of US 60)
59 - Out of grid placement (entirely west of US 71)
60 - Convoluted routing west of Springfield, MO after original path got stolen by 66. It exists west of the I-10 and Superstition interchange for some reason
61 - Should've not got truncated in MN
62 - Long diagonal
63 - Exists southwest of Memphis for some reason
64 -
65 - Unnecessary truncation on both ends
66 - Some people here thinks it doesn't deserve the fame it gets in the general public
67 - It's E-W in Texas, but I haven't seen criticism about that.
68 - N-S in Ohio, imo it's a wasted 2dus number for a fitting 3dus routing
69 -
70 - Suffixed splits
71 - Parallels I-49 entirely south of KC when it gets finished
72 - Could've been combined with either US 74 or 76 east of Chattanooga
73 - Too short for a 2dus
74 - It or US 76 could've been combined with US 72
75 - Parallel with I-29 north of Omaha
76 - It or US 74 could've been combined with US 72
77 -
78 - Shorter than US 278, concurrent with I-22 west of Birmingham
79 - More E-W than N-S in most states it goes through
80 - Parallel with interstates for most of its length
81 -
82 -
83 -
84 -
85 - Parallel with I-25 south of Cheyenne
87 - Concurrent or parallels I-25 in Colorado and Wyoming
89 -
90 - Parallel with I-10 for most of its length
91 - Short, parallel with I-15.
92 - Parallel with I-4, concurrent with US 17 for most of its length
93 - It ending before reaching Phoenix is US 60's issue
95 -
96 - N-S routing for even number, intrastate
97 - US 395 would make a better US 97 than its current route
98 -
99 - Currently doesn't exist, but I've seen suggestions in fictional about bringing US 99 back
101 - Loop in Washington

[hotdogPi]

61: shouldn't have been truncated

You do know there's no 28 or 32, right?

[Max Rockatansky]

A lot of people get spun up about US 57 for being out of grid

[kenarmy]

Here's just my take:
1- Indirect of US 17 for most of its length
2- It has a gap (I'm sure some people frown upon that)
3- Short, could be branch route of 1
5- ^
7-  ^
8- Short, could easily be a branch route of 2
10- Got severely truncated
12- Paralleled by I-94 for a while, and I'm pretty sure some US 10 fans are salty that it didn't get truncated
15- Got truncated by an incomplete, out of grid interstate that most people dislike
18- Long overlap with US 20/85
26- Has 1 million concurrencies with US 20, short compared to nearby routes
29- Paralleled by I-85
34- Bumps with US 6 several times. Now that I think of it, US 34 to US 6 is kind of like US 26 to US 20.
36- kinda overshadowed
43- Short, bould be a branch of 45.
50- Lengthy overlap with US 6 (although most people see 6 as being in the wrong) or being truncated to Sacramento?
51- Paralleled by interstates for nearly all its route, lengthy concurrency with I-39.
53- Really short.
54- Got truncated and replaced by a state route with the same number.
56- Overlapped with a longer US 412 for over 130 miles, mostly diagonal
61- got infamously truncated
63- Im sure y'all know this one 
65- got truncated and replaced by US 425 *gross*
69- Idk.. Overlap with US 96?
72- short, could be combined with 74 or 76
74 ^
76 ^
81- Has a branch route that is longer than it
82- ?
83- Rural, got partially replaced by I-2, I-69E
84- Has a curve towards its western terminus.
89- Got truncated by two short interstates
95- ? Maybe that it never meets US 395?
101- Its "Northern" Terminus.

[jeffandnicole]

95 was tremendously roasted for not being completed in NJ.  But now...well, there's still a lot wrong with it, but it's varied throughout the corridor.

[hotdogPi]

95 was tremendously roasted for not being completed in NJ.  But now...well, there's still a lot wrong with it, but it's varied throughout the corridor.

That goes in the roasted Interstate thread.

[SkyPesos]

50- Lengthy overlap with US 6 (although most people see 6 as being in the wrong) or being truncated to Sacramento?

When US 50 used to go to San Francisco, it went via Stockton, using current CA 99 and I-580, replacing much of the first US 48. That's a convoluted routing compared to the northern I-80/former US 40 routing, and definitely a roast I've seen on the forum. Also, I question why US 50 got extended to San Francisco instead of San Jose (where US 48 used to go to).

But with current US 50, it seems like the perfect transcon US route to me. I think the US 6/50 concurrency is more of 6's issue. Not too many parts concurrent or parallel with interstates compared to its peers like *cough* US 40, so it has tons of use on its own right. It takes a relatively direct routing through major metro areas, unlike US 60 west of Springfield. Some medium-large metro areas US 50 goes through are Sacramento, Reno-Carson City, KC, St Louis, Cincinnati and DC. Haven't seen that many criticism that it got replaced by a state route expressway (OH 32) in most of Ohio or Corridor H between I-79 and I-81

[jeffandnicole]

95 was tremendously roasted for not being completed in NJ.  But now...well, there's still a lot wrong with it, but it's varied throughout the corridor.

My bad...


That goes in the roasted Interstate thread.

[SkyPesos]

63- Im sure y'all know this one 

I actually don't know which issue, because there's multiple. The extension past Memphis? The concurrency with US 167 before ending? Or the fact that it ends first and 167 is the route to continue southward?

[Flint1979]

The reason why US-127 goes to Michigan and US-27 doesn't.

US-127 use to end as a freeway at I-69 and continued as US-27 north to Grayling. US-27 went even further north than Grayling before I-75 was built it use to end in Cheboygan.

To end any confusion with 127 ending and becoming just 27 and with 27's really long concurrency with I-69 it didn't make any sense for it to go north of Fort Wayne anymore.

I still think that 27 and 127 should have switched routes in Cincinnati and had 27 go up to Grayling and 127 go to Fort Wayne.

[GaryV]

The reason why US-127 goes to Michigan and US-27 doesn't.

US-127 use to end as a freeway at I-69 and continued as US-27 north to Grayling. US-27 went even further north than Grayling before I-75 was built it use to end in Cheboygan.

At one time it went to Mackinaw City and to St Ignace.

To end any confusion with 127 ending and becoming just 27 and with 27's really long concurrency with I-69 it didn't make any sense for it to go north of Fort Wayne anymore.

I still think that 27 and 127 should have switched routes in Cincinnati and had 27 go up to Grayling and 127 go to Fort Wayne.

Switching north of Cincinnati would have caused more signage changes.  It also would have required the cooperation of Ohio, who would have no interest in a change because it provided no benefit, only the cost of the sign changes.

[TheHighwayMan3561]

63 got a weird extension southwest of Memphis that probably wasn't needed.

[CNGL-Leudimin]

38 and either 32 or 34: Should have been a single route from the get go (Eventually 32 and 38 would get unified... as 6 xD).

You do know there's no 28 or 32, right?

But there used to be. As well as 38, 55 and 99. 66 is already listed.

[Flint1979]

The reason why US-127 goes to Michigan and US-27 doesn't.

US-127 use to end as a freeway at I-69 and continued as US-27 north to Grayling. US-27 went even further north than Grayling before I-75 was built it use to end in Cheboygan.

At one time it went to Mackinaw City and to St Ignace.

To end any confusion with 127 ending and becoming just 27 and with 27's really long concurrency with I-69 it didn't make any sense for it to go north of Fort Wayne anymore.

I still think that 27 and 127 should have switched routes in Cincinnati and had 27 go up to Grayling and 127 go to Fort Wayne.

Switching north of Cincinnati would have caused more signage changes.  It also would have required the cooperation of Ohio, who would have no interest in a change because it provided no benefit, only the cost of the sign changes.

Wouldn't of needed any sign changes if that's how it was to start out which is what I was implementing. And really changing signs wouldn't of been that big of an issue anyway. All you do is cover up the 1 and have an off center 27 just like they did along US-112 with US-12 in the beginning before sign replacements happened.

[SkyPesos]

63 got a weird extension southwest of Memphis that probably wasn't needed.

It seems like the only 'new' segment to the US highway system for the 63 extension is Pine Bluff to El Dorado, which is intrastate, and faster with 79/167 anyways. Memphis-Pine Bluff is already served by 79, and 167 is a straight line for US 63 between El Dorado and near the AR-MO border.

[kenarmy]

63 got a weird extension southwest of Memphis that probably wasn't needed.

It seems like the only 'new' segment to the US highway system for the 63 extension is Pine Bluff to El Dorado, which is intrastate, and faster with 79/167 anyways. Memphis-Pine Bluff is already served by 79, and 167 is a straight line for US 63 between El Dorado and near the AR-MO border.

Makes me think AR was salty that 63 was rejected for being extended through Memphis to the MS gulf coast (via US 49), so they plotted with LA to come up with a ridiculous route  .

[Avalanchez71]

After looking through the Unpopular US Route opinions thread, and the Which 2dis get roasted the most/least thread, here's one for 2 digit US routes. This is mostly from what I see on the forum. I don't know enough information about half of the routes, so going to need help filling the blanks in.

1 -
2 - Split into two segments by Canada, though I have no issues with it
3 -
4 -
5 - Parallel with I-91 for its entire length
6 - Out of grid placement, parallels an interstate for most of its length, former routing in CA is a straight N-S
7 -
8 -
9 - Parallels I-87 north of NYC
10 -
11 - Parallel with an interstate south of Watertown
12 -
13 - Mostly east of US 1
14 - Parallel with I-90 for most of its length
15 -
16 - Short, too many concurrencies
17 - Mostly east of US 1
18 -
19 - Suffixed split, parallels I-79 north of Sutton, WV
20 - Yellowstone gap
21 - Parallels I-77 north of Columbia, SC
22 - Parallels I-78 from Harrisburg eastward
23 - Long concurrency with US 1 before ending
24 - Mostly out of grid, as it's between US 36 and US 40 for most of its length
25 - Suffixed split
26 -
27 - "Why does US 127 go to Michigan over US 27?"
29 - Parallels I-85 south of Greensboro
30 - Parallels interstates for a good portion of its length
31 - Suffixed split, parallels I-65 entirely south of Indianapolis
33 - Odd number for E-W route
34 -
35 - Odd number for E-W route
36 - Doesn't seem to have that much criticism. It's far away enough from I-70 to have its own use. Concurrency with I-72 in IL, though that's a short portion.
40 - Parallels I-70 for most of its length
41 - Parallels an interstate for most of its length, east of US 31 south of Nashville (I have no issues with the latter)
42 - Even number for N-S route, parallels I-71 for most of its length
43 -
44 - Out of grid placement
45 - Suffixed split
46 - Out of grid placement, almost intrastate, parallels I-80 for its length
48 - Out of grid placement (between US 50 and US 60), incomplete
49 - Suffixed split
50 - Doesn't seem to have that much criticism. Only a small fraction of the 3000 mile route parallels an interstate. It got replaced by parallel 4 lane expressways (OH 32 and Corridor H) through the Appalachians, though I haven't seen any issue with that.
51 - Parallels interstates for most of its length
52 - Long diagonal
53 -
54 -
56 -
57 - E-W routing, out of grid placement, intrastate
58 - Out of grid placement (entirely south of US 60)
59 - Out of grid placement (entirely west of US 71)
60 - Convoluted routing west of Springfield, MO after original path got stolen by 66. It exists west of the I-10 and Superstition interchange for some reason
61 - Should’ve not got truncated in MN
62 - Long diagonal
63 - Exists southwest of Memphis for some reason
64 -
65 -
66 - Some people here thinks it doesn't deserve the fame it gets in the general public
67 - It's E-W in Texas, but I haven't seen criticism about that.
68 - N-S in Ohio, imo it's a wasted 2dus number for a fitting 3dus routing
69 -
70 - Suffixed splits
71 - Parallels I-49 entirely south of KC when it gets finished
72 - Could've been combined with either US 74 or 76 east of Chattanooga
73 - Too short for a 2dus
74 -
75 -
76 -
77 -
78 - Shorter than US 278
79 - More E-W than N-S in most states it goes through
80 - Parallel with interstates for most of its length
81 -
82 -
83 -
84 -
85 - Parallel with I-25 south of Cheyenne
87 - Concurrent or parallels I-25 in Colorado and Wyoming
89 -
90 - Parallel with I-10 for most of its length
91 - Short, parallel with I-15.
92 - Parallel with I-4, concurrent with US 17 for most of its length
93 - It ending before reaching Phoenix is US 60's issue
95 -
96 - N-S routing for even number, intrastate
97 - US 395 would make a better US 97 than its current route
98 -
99 - Currently doesn't exist, but I've seen suggestions in fictional about bringing US 99 back
101 -

US 73 was much longer, however, they truncated it and it was replaced in part by US 75 and US 69.  There were two different US 73E/US 73W splits as well.  US 73 did go to Atoka, OK under the 1926 plan.

KS asked for US 73 to be routed along State St with US 24/US 40 and they were denied. Apparently they went ahead with it anyway because by 2008 they asked for it to be routed south with US 24/US 40 in lieu of east on State St. when US 24/US 40 was taken off State St. in KCK.

[Roadgeekteen]

US 96 gets a lot of hate. Also to a lesser extent US 11.

[SkyPesos]

I had more time to take a look at more of these today.

54- Got truncated and replaced by a state route with the same number.

I'm fine with US 54's truncation, and would actually roast it if it didn't get truncated. Its path from its current eastern terminus to Chicago multiplexed with US 36 and US 45 for long lengths, and also doubled US 66 as a (longer) Springfield-Chicago route.

56- Overlapped with a longer US 412 for over 130 miles, mostly diagona

I took a look at this one, and would say that US 412 is the issue here, as it came later.

95- ? Maybe that it never meets US 395?

Guess there's no issues with US 95 then if we have to go to that length of nitpicking to find one. I'm fine with that; not every US route have to have an issue.

[sparker]

I had more time to take a look at more of these today.

54- Got truncated and replaced by a state route with the same number.

I'm fine with US 54's truncation, and would actually roast it if it didn't get truncated. Its path from its current eastern terminus to Chicago multiplexed with US 36 and US 45 for long lengths, and also doubled US 66 as a (longer) Springfield-Chicago route.

56- Overlapped with a longer US 412 for over 130 miles, mostly diagona

I took a look at this one, and would say that US 412 is the issue here, as it came later.

95- ? Maybe that it never meets US 395?

Guess there's no issues with US 95 then if we have to go to that length of nitpicking to find one. I'm fine with that; not every US route have to have an issue.

The Springfield-Onarga section of US 54 was pretty damn gratuitous from the get-go; probably politically foisted on a early IDOT by Chicago politicos who wanted as many US routes terminating within the Loop as they could jam in (e.g. 14, 34, 54, 66).  Easy to deploy; probably just paved the parallel service road to the Illinois Central RR's Springfield branch that departed the main line at Gilman.  US 56 was carved out (ironically or not in 1956) of old US 50N, which was the more indirect of the original 50 split in KS (lots of "jogging" N-S multiplexes), with a SW extension down former K-45 into the OK panhandle, thence on toward NM.  Speaking of gratuitous, US 412 west of I-35 never really made sense; there is limited traffic in that part of the state, and it's not even part of any existing corridor.  East of Tulsa it's part of High Priority Corridor #8, so it's likely someone reasoned that it deserved its own distinct number although multiplexed with other routes for much of its length.  And it can be rationalized as giving the Cimarron and Cherokee Turnpikes a distinct number (like OK 351 for the Muskogee Pike) -- but west of there it simply subsumed some sparsely-traveled state routes (15, 3) before merging with US 56 for its westernmost segment.  I suppose an official somewhere has congratulated themselves for initiating a US highway that spans from I-25 to I-65; whether there was prior rationalization for such a route remains something of a mystery that would take some deep digs into documentation to solve.
As far as US 97 vs. 395 is concerned, hindsight certainly indicates that the 395 route, at least today, warrants 2di consideration -- but it was cobbled up nearly a decade after US 97 had been established, so what happened in the '30's just couldn't readily be reversed.   

[SkyPesos]

Added a couple more roasts that I've seen here, notably with US 1, though I don't have an issue with its routing.

[WillWeaverRVA]

46 - Out of grid placement, almost intrastate, parallels I-80 for its length

US 46 actually is intrastate - it ends at the New Jersey/New York state line on the GWB, in a useless concurrency with I-95, US 1, and US 9. It isn't even signed on that concurrency.

[SEWIGuy]

41 - Parallels an interstate for most of its length, east of US 31 south of Nashville (I have no issues with the latter). Got replaced by a state route expressway (IN 63) for through traffic in Indiana; I have no issue with that either.

61 - Should've not got truncated in MN

There is a logical inconsistency here.  If you believe US highways shouldn't parallel or duplex with an interstate (like US-41), then you should have no problem with them being truncated or demoted (like US-61).

[SkyPesos]

41 - Parallels an interstate for most of its length, east of US 31 south of Nashville (I have no issues with the latter). Got replaced by a state route expressway (IN 63) for through traffic in Indiana; I have no issue with that either.

61 - Should’ve not got truncated in MN

There is a logical inconsistency here.  If you believe US highways shouldn't parallel or duplex with an interstate (like US-41), then you should have no problem with them being truncated or demoted (like US-61).

My issue with US 61 is that there's a somewhat long lone section (MN 61) north of I-35's terminus to the Canadian border that makes it worth keeping the concurrency/parallel with I-35. If I-35 went all the way to the Canadian border, I would agree that the US 61 truncation was justified.

Also, most of the roasts are from what I see on this forum, and not entirely my opinion. Not sure if it's a majority of the forum or not, but a lot of people here don't like parallel/concurrent US routes with interstates, which is why I had "parallel with interstate" as roasts.

[SEWIGuy]

41 - Parallels an interstate for most of its length, east of US 31 south of Nashville (I have no issues with the latter). Got replaced by a state route expressway (IN 63) for through traffic in Indiana; I have no issue with that either.

61 - Should've not got truncated in MN

There is a logical inconsistency here.  If you believe US highways shouldn't parallel or duplex with an interstate (like US-41), then you should have no problem with them being truncated or demoted (like US-61).

My issue with US 61 is that there's a somewhat long lone section (MN 61) north of I-35's terminus to the Canadian border that makes it worth keeping the concurrency/parallel with I-35. If I-35 went all the way to the Canadian border, I would agree that the US 61 truncation was justified.

Also, most of the roasts are from what I see on this forum, and not entirely my opinion. Not sure if it's a majority of the forum or not, but a lot of people here don't like parallel/concurrent US routes with interstates, which is why I had "parallel with interstate" as roasts.

Oh I know.  People complain about all sorts of things.