Numbered routes that should be merged?

[SkyPesos]

US 33 and US 131, for the only reason of removing an almost intrastate US route.

[Flint1979]

M-46 and M-82. The western end of M-46 becomes an extension of M-57.

[Flint1979]

US 33 and VA 33. Seriously, why does the latter even exist? If I were VDOT, I would just make the whole thing US 33.

Same thing with US 15 and NY 15, US 3 and MA 3 - you get the idea. Just have the US route take over the whole road.

Because the US route wasn't approved for the whole thing and the state's wanted an extension of the route so it becomes a state highway.

[DandyDan]

In Iowa, the obvious merger candidates are IA 39 and IA 471. I don't know why when US 71 was rerouted they just didn't extend IA 39. It's only 5 miles from the end of IA 39 to the end of IA 471. I also wonder why IA 23 and IA 78 aren't merged.

[GaryV]

I've probably mentioned this in another similar thread, but ...

M-117 and the western leg of M-123.  (Possibly extend the eastern leg of M-123 from Paradise to Whitefish Point.)

As far as US-18 crossing Lake Michigan, what benefit does it give for long-distance travel?  Anyone with a destination more than a few miles from Lake Michigan, say 25 or so, would probably benefit from going around the lake rather than waiting for (and paying for) the ferry.  This may be heresy, but I also think the Badger still being a part of US-10 is more for historical reasons rather than  practical reasons.

[JayhawkCO]

I'll go first: CO-16 and CO-21 in Colorado Springs.

And then merge CO83 onto that too.

Chris

[TheHighwayMan3561]

Another MN one, MN 210 and MN 39

Hot take I've heard from more than a few (I don't want this, but OK ): MN 23 and MN 61

[ftballfan]

FL 655 and FL 620. Heading southbound along Recker Hwy, FL 655 magically changes to FL 620 at Lake Shipp Drive before ending at FL 540 a short distance later.

[SkyPesos]

Hot take I've heard from more than a few (I don't want this, but OK ): MN 23 and MN 61

Hotter take: US 61 and MN 61 

Though if MN 23 and 61 gets merged, I think that would be the longest route in the state, at just under 500 miles.

[Henry]

Don't we have at least 15 of this thread topic in fictional already?

I actually took this into consideration. Looked up "CO-21", but there were no matching threads.

Most Colorado posters here use "˜SH-XX' for their state routes. If you're going to use a route number to search for a combining routes thread, use I-44 or I-64, as they're the most commonly suggested ones for some reason.

In regards to I-44 and I-64, while they do connect in St. Louis, I feel the overall trajectories of each highway are different enough to merit (retain) separate numbering.

That's my general concieus too. I-44 is a diagonal SW-NE route, while I-64 is mostly straight, with a NW-SE (opposite of I-44's trajectory) between Richmond and the Hampton Roads. That's why I didn't combine those two routes together in my fictional interstates thread in my sig.

Meanwhile for I-29 and I-49 at the other side of the state, I combined them as a single I-45.

What would you do with the I-45 that connects Houston to Dallas and Galveston?

I-17 and I-19 are two worthy candidates for merging, with an I-10 concurrency in the middle.

[NWI_Irish96]

IN 15 (except for the far southern stub) and the middle section of IN 37 should be merged.
IN 2 and IN 120 should be merged via a US 20 concurrency
IN 327 and IN 205 should be merged

[jp the roadgeek]

CT 14 extended along CT 66 (and through Meriden on East/West Main St), the E/W portion of CT 322, through Wolcott and Waterbury on Meriden Rd, East/West Main St and Chase Parkway, CT 64, a wrong-way concurrency with US 6, CT 317, and CT 133.

CT 21 and CT 193 as an extended CT 193.  That way, you could free up the 21 number to repurpose for CT 286 and CT/MA 186 and add the 21 number to Elm St, Cooley St, and Parker St to MA 21.

CT 82 and CT 165.  RI could renumber RI 165 to RI 82.

CT 27 and CT 201

CT 49 and CT/RI 78 via a brief concurrency with CT 2

[kurumi]

CT 14 extended along CT 66 (and through Meriden on East/West Main St), the E/W portion of CT 322, through Wolcott and Waterbury on Meriden Rd, East/West Main St and Chase Parkway, CT 64, a wrong-way concurrency with US 6, CT 317, and CT 133.

CT 21 and CT 193 as an extended CT 193.  That way, you could free up the 21 number to repurpose for CT 286 and CT/MA 186 and add the 21 number to Elm St, Cooley St, and Parker St to MA 21.

CT 82 and CT 165.  RI could renumber RI 165 to RI 82.

CT 27 and CT 201

CT 49 and CT/RI 78 via a brief concurrency with CT 2

Yes, to all these. (Based on the "route changes" spreadsheet, it looks like ConnDOT wanted to absorb CT 21 into 193 just as you propose.)

I'd also:
* extend CT 190 along CT 171 to Putnam (leftover 171 in Union can be an SR)
* extend CT 61 south to CT 64, then take over CT 188 south to 34
* 138 along 207 and 16 to East Hampton

[Hwy 61 Revisited]

US 222 and PA 222. It's kind of useless to have a federal highway continue as a state highway just to end at a lowly state route. It doesn't even traverse the whole valley!

[SkyPesos]

That's my general concieus too. I-44 is a diagonal SW-NE route, while I-64 is mostly straight, with a NW-SE (opposite of I-44's trajectory) between Richmond and the Hampton Roads. That's why I didn't combine those two routes together in my fictional interstates thread in my sig.

Meanwhile for I-29 and I-49 at the other side of the state, I combined them as a single I-45.

What would you do with the I-45 that connects Houston to Dallas and Galveston?

It's in my fictional compilation thread. Current I-45 becomes I-41, and current I-41 becomes an I-65 extension, with current I-94 broken up into multiple segments. Also renumbered the whole upper midwest and Texas N-S grid as part of it. Since combining route numbers 99.9999% of the time won't happen in real life, regardless how simple it is (like my OH 16 and OH 161 swap idea west of Granville), might as well go a bit deeper than looking at the two routes.

Speaking of fictional, I'm surprised that this thread has been up for 4 days with 38 replies, and haven't been moved to fictional yet.

[TheGrassGuy]

I-5 and I-95

no

[ran4sh]

Australia highway 1 is a route that goes around the whole country, if the US did the same it could make such a route out of I-5, I-10, I-95, I-90, and I-94.

[ftballfan]

Another one: FL 33 and FL 37. FL 33's south end and FL 37's north end are about a half mile apart.

[zzcarp]

Ohio 31 and Ohio 38 end at each other in downtown Marysville, Ohio. Ohio 31 was truncated there when Ohio 4 took over its route southwest of Marysville in 1926.

Another possible extension could have Ohio 53 take over both routes. Ohio 53 and Ohio 31 are co-signed through downtown and both end at US 68 in Kenton (57 on the south side and 31 on the north). US 68 took over Ohio 31 north of Kenton and Ohio 53 south of Kenton when it was extended to Ohio in 1933.

[SkyPesos]

Ohio 31 and Ohio 38 end at each other in downtown Marysville, Ohio. Ohio 31 was truncated there when Ohio 4 took over its route southwest of Marysville in 1926.

Another possible extension could have Ohio 53 take over both routes. Ohio 53 and Ohio 31 are co-signed through downtown and both end at US 68 in Kenton (57 on the south side and 31 on the north). US 68 took over Ohio 31 north of Kenton and Ohio 53 south of Kenton when it was extended to Ohio in 1933.

Ohio have a lot of state routes that end close to each other that could be combined. A full list would take a long time to make out. Here are some in the Cincinnati area I can think of

OH 63 and OH 350. Could be connected on an approx 3.7 mile long concurrency with OH 123.
OH 125 and OH 561. Those two routes, along with OH 32 share the same terminus at US 50. OH 125 is pretty much a SE-NW routing at that point, and it can be continued on OH 561's SE-NW routing.
OH 126 and OH 131. Originally thought of OH 126 and OH 28, but OH 28's SW-NE routing doesn't really fit with OH 126's NW-SE routing.

[roadman65]

US 72 and US 76.
US 130 and US 301.
US 113 and US 202.

[Occidental Tourist]

CA 72, the eastern end of CA 90, and CA 142.  Relinquish the mile or of CA 90 east of CA 142 that isn't already relinquished to Brea and Placentia.

[Avalanchez71]

KY SR 79 and US 79
US 76 and US 72

[Flint1979]

Hot take I've heard from more than a few (I don't want this, but OK ): MN 23 and MN 61

Hotter take: US 61 and MN 61 

Though if MN 23 and 61 gets merged, I think that would be the longest route in the state, at just under 500 miles.

The thing there is that MN-61 use to be US-61 until it was scaled back to Wyoming and the former route became I-35 and a state highway with the same number (MN-61). Then there's Ontario Highway 61 that goes from the border to Thunder Bay. I think it should have stayed US-61.

[SkyPesos]

Hot take I've heard from more than a few (I don't want this, but OK ): MN 23 and MN 61

Hotter take: US 61 and MN 61 

Though if MN 23 and 61 gets merged, I think that would be the longest route in the state, at just under 500 miles.

The thing there is that MN-61 use to be US-61 until it was scaled back to Wyoming and the former route became I-35 and a state highway with the same number (MN-61). Then there's Ontario Highway 61 that goes from the border to Thunder Bay. I think it should have stayed US-61.

I still think US 61 is the most unnecessary US route truncation out there. Most of the California E-W ones make sense, as the route ends in the state and shares the same path as an interstate the whole way through. US 61 have a significant path north of Duluth that US 35 doesn't cover, and it's only about 120 miles from current 61's northern terminus to I-35's northern terminus in Duluth.

US 65 makes sense as it ended at Minneapolis and it's mostly with I-35 between Albert Lea and Minneapolis

I wouldn't be surprised if MN attempted to work with North Dakota to truncate US 52 at St Paul before either.