AARoads Forum

National Boards => General Highway Talk => Topic started by: fillup420 on March 27, 2017, 09:26:10 AM

Title: Parent/sibling or sibling/sibling concurrencies
Post by: fillup420 on March 27, 2017, 09:26:10 AM
In Boone NC, US 221, 321, and 421 all go through town. 321 and 421 run concurrent north out of town. 221 and 321 run concurrent south out of town, and 221 and 421 run concurrent east out of town, with 221 signed North and 421 signed South. Also in Raleigh, US 64 and 264 run together from I-440 to Zebulon. This is interesting because 264 ends at I-440, with 64 continuing on. Any other examples like this?

Also, fun fact: I believe Boone, NC is the only place in the country where 3 sibling routes meet each other. There even used to be an intersection where 221, 321, and 421 all met, but that changed when a new alignment was built for 221
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: TXtoNJ on March 27, 2017, 10:02:04 AM
US 30/130 in Camden/Collingswood NJ is a notable one.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: hotdogPi on March 27, 2017, 10:04:45 AM
MA 2/2A (signed), 1/1A (once signed and once unsigned), 3/3A (unsigned)
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Eth on March 27, 2017, 10:12:08 AM
- US 231/431 from Huntsville, AL to Fayetteville, TN
- US 41/441 from High Springs to Lake City, FL
- US 1/301 near the FL/GA border
- US 301/501 near the SC/NC border
- US 1/501 in Sanford, NC
- US 78/278 twice: once in Atlanta and again in Augusta, GA (did it ever also happen in AL before I-22 was built?)
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Big John on March 27, 2017, 10:16:31 AM
US 41/141 from Green Bay to Abrams.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Max Rockatansky on March 27, 2017, 10:28:47 AM
Quote from: Big John on March 27, 2017, 10:16:31 AM
US 41/141 from Green Bay to Abrams.

US 41 has another US 441 from Lake City to High Springs in Florida.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: froggie on March 27, 2017, 10:34:08 AM
If we expand this to include Interstate routes, there are a couple:

- I-94/694 northwest of Minneapolis, MN
- I-95/495 on the east side of the (DC) Capitol Beltway

Some others:

- Another US 1/US 301 in central Virginia (basically from Petersburg to Richmond)
- US 1/US 401 north of Raleigh, NC (surprised Eth didn't catch this one)
- US 58/US 258 near Franklin, VA
- US 158/US 258 near Murfreesboro, NC
- US 69/US 169 in suburban Kansas City, KS (along with I-35 for part of it)
- US 10/MN 210 in central Minnesota (210 was numbered deliberately as a child of US 10, and east of the concurrency was a U.S. route until 1973)


Quote from: Eth- US 78/278 twice: once in Atlanta and again in Augusta, GA (did it ever also happen in AL before I-22 was built?)

Yes, between Guin and Hamilton.  US 43 was also part of that concurrency to complete the triplex.  IIRC, this remained until Corridor X was finished between Exit 16 (south side of Hamilton) and Exit 52 (east of Carbon Hill) sometime in the early 2000s.  I distinctly remember it existing (and Corridor X not completed there) when I was stationed in Meridian, MS from 1998-2001.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: bzakharin on March 27, 2017, 12:46:20 PM
I-87/I-287 in New York. US 22 / 322 / 422 in PA and Ohio, though only 22 is signed, so it can be analyzed as separate 322s and 422s (though that would mean the former occurs twice in the same state)
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: jemacedo9 on March 27, 2017, 12:50:54 PM
Quote from: bzakharin on March 27, 2017, 12:46:20 PM
I-87/I-287 in New York. US 22 / 322 / 422 in PA and Ohio, though only 22 is signed, so it can be analyzed as separate 322s and 422s (though that would mean the former occurs twice in the same state)

Outside of Lewistown PA, if US 422 were signed on it's implied concurrency, there would be a very short US 22 / US 322 / US 422 / US 522 concurrency. 
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: sparker on March 27, 2017, 01:17:19 PM
Here in N. Calif. we've got the I-80/I-580 reverse concurrency (EB 80/WB 580 and vice-versa) between the Bay Bridge distribution (with I-880) interchange at Emeryville/W. Oakland and Albany, where they diverge.  Approximately 5 miles in length.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: cwf1701 on March 27, 2017, 05:01:15 PM
 in Michigan,  was there a Concurrency of US-12 and US-112 where US-112 was  routed around the Ann Arbor/Ypsilanti area with US-12 on what is now I-94 in the 1950s?
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: bassoon1986 on March 27, 2017, 05:26:44 PM
US 71 and US 371 for a mile or two in Coushatta, LA.
US 67 and US 167 through Little Rock and north-central Arkansas
US 60 and US 160 in Springfield, MO
US 18 and US 218 near Charles City, IA
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: 1995hoo on March 27, 2017, 09:06:52 PM
A former one: I-440 and I-40 around the south side of Raleigh (I-440 has since been truncated).
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: briantroutman on March 27, 2017, 09:33:15 PM
Quote from: bzakharin on March 27, 2017, 12:46:20 PM
US 22 / 322 / 422 in PA and Ohio, though only 22 is signed, so it can be analyzed as separate 322s and 422s

You're correct about 422 (there is some evidence (https://www.aaroads.com/forum/index.php?topic=15227.msg2056231#msg2056231) suggesting that PennDOT internally considers 422 to be continuous, but it's not signed that way).

But the 22 - 322 overlap is visibly signed for both.

(https://tribwpmt.files.wordpress.com/2013/06/photo-taf.jpg?quality=85&strip=all)
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Ian on March 27, 2017, 10:54:23 PM
A few that come to mind...
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Max Rockatansky on March 27, 2017, 11:12:50 PM
US 89 and 189 from downtown Jackson south to the split on the Snake and Hobeck River in Wyoming.  Completely weird multiplex that makes zero sense when you think about:

http://www.usends.com/189.html
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Bickendan on March 28, 2017, 02:52:31 PM
Former: I-40 and 540 near Fort Smith, Arkansas.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: LM117 on March 29, 2017, 05:34:47 AM
US-360/460 in Burkeville, VA
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: OracleUsr on March 29, 2017, 05:56:46 AM
US 21/321 in Cayce, SC
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: iBallasticwolf2 on March 29, 2017, 07:00:47 AM
US 27 and US 127 on Central Parkway in Cincinnati.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: roadman65 on March 29, 2017, 09:09:45 AM
US 1/301 in Virginia.
US 301/501 across the NC-SC Line.
US 41/ US 41 ALT in Nashville.
US 9/ NY 9N in Elizabethtown, NY
US 231/431 in AL
US 31/431 in Nashville
US 6/106 now defunct in PA
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Max Rockatansky on March 29, 2017, 09:38:12 AM
Some other defunct parent/child multiplexes:

-  US 399 met US 99 south of the city of Bakersfield and multiplexed in to the city.
-  US 66 and 666 were concurrent from Sanders, AZ to Gallup, NM.
-  US 60 and US 260 were concurrent for a couple miles near Springerville, AZ.  Oddly US 60 and AZ 260 are now concurrent west of Springerville in the City of Show Low despite the new 260 having nothing to do with the previous US Route.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: jeffandnicole on March 29, 2017, 09:45:51 AM
NJ tries to encourage this parent and sibling to work together, even though it's truly just the parent route.

https://goo.gl/maps/QR82q3jVmH42

(Technical note - NJDOT doesn't always do this parent/sibling numbering on state routes, although in cases like this its apparent that was the goal here)
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: bdmoss88 on March 29, 2017, 11:46:31 AM
US 80/280 - wrong-way in Phenix City, AL
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: dfilpus on March 29, 2017, 12:43:59 PM
Lots of concurrencies of US 1 and its children in NC.

Two separate concurrencies of US 1/501 (with US 15) in Sanford NC and Aberdeen NC.
US 401/501 (with US 15) in Laurinburg NC.
Two separate concurrencies of US 1/401 north of Raleigh and from Norlina NC to I 85, where US 401 ends.
US 301/501 crossing the NC/SC border.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: sparker on March 29, 2017, 12:54:38 PM
And lest we forget, the reverse concurrency of US 77 and US 177 -- themselves concurrent with US 60 -- between Tonkawa and Ponca City, OK.  One of two such "place shifting" concurrencies in that state, but the only one to feature parent & sibling designations (the other is 60/64/81 near Enid).
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: bzakharin on March 29, 2017, 06:50:36 PM
Quote from: jeffandnicole on March 29, 2017, 09:45:51 AM
NJ tries to encourage this parent and sibling to work together, even though it's truly just the parent route.

https://goo.gl/maps/QR82q3jVmH42

(Technical note - NJDOT doesn't always do this parent/sibling numbering on state routes, although in cases like this its apparent that was the goal here)
Another questionable NJ one is 47/347
https://www.google.com/maps/@39.2906888,-74.9668333,3a,15y,26.23h,90.64t/data=!3m6!1e1!3m4!1s0CSUqoUo8IsMvYiilB4tYw!2e0!7i13312!8i6656
47 is either discontinuous Northbound or it runs along CR 670 and NJ 347.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: NE2 on March 29, 2017, 07:33:10 PM
Quote from: bzakharin on March 29, 2017, 06:50:36 PM
Another questionable NJ one is 47/347
https://www.google.com/maps/@39.2906888,-74.9668333,3a,15y,26.23h,90.64t/data=!3m6!1e1!3m4!1s0CSUqoUo8IsMvYiilB4tYw!2e0!7i13312!8i6656
47 is either discontinuous Northbound or it runs along CR 670 and NJ 347.
Or NJ 347 ends northbound at CR 670.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: hbelkins on March 29, 2017, 08:34:20 PM
US 60/US 460 -- 460's western terminus is at US 60 in Frankfort. In Mt. Sterling, they have a one-block wrong-way concurrency (East 460 is on West 60, and vice versa.) Then US 460 terminates at US 60 in Norfolk, Va.

US 50 and US 150 have a concurrency in Indiana.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: bzakharin on March 29, 2017, 09:29:07 PM
Quote from: NE2 on March 29, 2017, 07:33:10 PM
Quote from: bzakharin on March 29, 2017, 06:50:36 PM
Another questionable NJ one is 47/347
https://www.google.com/maps/@39.2906888,-74.9668333,3a,15y,26.23h,90.64t/data=!3m6!1e1!3m4!1s0CSUqoUo8IsMvYiilB4tYw!2e0!7i13312!8i6656
47 is either discontinuous Northbound or it runs along CR 670 and NJ 347.
Or NJ 347 ends northbound at CR 670.
There is an END 347 sign at the merge with the southbound 47 lane, but the SLDs do seem to show that 347 ends at CR 670 in both directions and the piece to the north is 47Z
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Bitmapped on March 29, 2017, 11:10:33 PM
- US 19 and US 119 in Morgantown, WV (southbound only)
- US 19 and US 119 in Weston, WV
- US 50 and US 250 in Pruntytown, WV
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: WNYroadgeek on March 29, 2017, 11:42:32 PM
NY 14 and 414 overlap in Watkins Glen
NY 34 and 34B overlap in Lansing (Bonus: it's a wrong-way concurrency)
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: NE2 on March 30, 2017, 12:48:50 AM
US 60 and US 60 in Newport News.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: GenExpwy on March 30, 2017, 03:52:43 AM
Quote from: WNYroadgeek on March 29, 2017, 11:42:32 PM
NY 14 and 414 overlap in Watkins Glen

NY 14 is (probably) not NY 414's parent.

NY 414 started out as NY 44, and got renumbered when US 44 was created. Apparently they decided the easiest thing to do was to send out a guy with a can of black paint and put 1's between the 4's.

Maybe there was some intent to make a reference to NY 14, but more likely it's just a coincidence.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Max Rockatansky on March 30, 2017, 09:08:53 AM
US 92 and US 192 are mulitplexed for a coupled blocks on Vine Street in downtown Kissimmee, FL.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: GaryV on March 30, 2017, 09:15:48 PM
US 223 joins US 23 for it's last few miles into Ohio.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: cl94 on March 31, 2017, 12:37:36 AM
US 9 in New York might be the poster child for these things. Two concurrencies with NY 9A and two with NY 9N.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Buffaboy on March 31, 2017, 02:48:10 AM
This is probably a stretch, but I'd say NY-265 and NY-266.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: MrDisco99 on March 31, 2017, 05:03:06 PM
I-95 and I-495 on the DC beltway
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: bassoon1986 on March 31, 2017, 11:33:19 PM
Quote from: sparker on March 29, 2017, 12:54:38 PM
And lest we forget, the reverse concurrency of US 77 and US 177 -- themselves concurrent with US 60 -- between Tonkawa and Ponca City, OK.  One of two such "place shifting" concurrencies in that state, but the only one to feature parent & sibling designations (the other is 60/64/81 near Enid).

Thanks for this example. I forgot about US 77 and US 377 in Denton TX


iPhone
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: PColumbus73 on April 01, 2017, 10:24:22 AM
In South Carolina:

US 301 & US 601 are concurrent from Orangeburg to Bamberg

US 501 & US 701 have a brief concurrency in Conway, also, US 701 has a shorter concurrency with Business US 501 on 16th Ave in Conway

US 76 & US 176 have a short concurrency in Irmo

US 21 & US 321 are concurrent through most of Columbia
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: fillup420 on April 05, 2017, 09:18:08 AM
US 21 and US 221 run together around the NC/VA state line


iPhone
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: hbelkins on April 05, 2017, 03:46:51 PM
US 231 has concurrencies with both of its parents (US 31E and 31W) in south-central Kentucky. US 231 and 431 are concurrent when they cross from Tennessee into Alabama.

US 19 and US 119 have about a block-long concurrency in Weston, WV.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Roadgeekteen on April 24, 2017, 08:09:27 AM
480/271
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Charles2 on April 24, 2017, 10:27:53 PM
Quote from: froggie on March 27, 2017, 10:34:08 AM
If we expand this to include Interstate routes, there are a couple:

- I-94/694 northwest of Minneapolis, MN
- I-95/495 on the east side of the (DC) Capitol Beltway

Some others:

- Another US 1/US 301 in central Virginia (basically from Petersburg to Richmond)
- US 1/US 401 north of Raleigh, NC (surprised Eth didn't catch this one)
- US 58/US 258 near Franklin, VA
- US 158/US 258 near Murfreesboro, NC
- US 69/US 169 in suburban Kansas City, KS (along with I-35 for part of it)
- US 10/MN 210 in central Minnesota (210 was numbered deliberately as a child of US 10, and east of the concurrency was a U.S. route until 1973)


Quote from: Eth- US 78/278 twice: once in Atlanta and again in Augusta, GA (did it ever also happen in AL before I-22 was built?)

Yes, between Guin and Hamilton.  US 43 was also part of that concurrency to complete the triplex.  IIRC, this remained until Corridor X was finished between Exit 16 (south side of Hamilton) and Exit 52 (east of Carbon Hill) sometime in the early 2000s.  I distinctly remember it existing (and Corridor X not completed there) when I was stationed in Meridian, MS from 1998-2001.

And the 43/78/278 triplex in Alabama involved a wrong-way concurrency.  NB 43 was routed with WB 78 and EB 278.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Charles2 on April 24, 2017, 10:31:54 PM
I'm surprised that no one has mentioned I-85 and I-285 on the SW side of Atlanta.  Until they were rebuilt in the '80's, the two routes actually shared the same pavement.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: sparker on April 26, 2017, 04:48:00 AM
US 1 & US 601 between Lugoff and Camden, SC.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: jp the roadgeek on April 28, 2017, 06:49:21 PM
NY 25 and NY 25A in Smithtown
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: dgolub on April 28, 2017, 06:55:26 PM
NY 17/NY 17M is another one with New York's letter-suffixed routes.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: cl94 on April 28, 2017, 07:45:13 PM
Quote from: dgolub on April 28, 2017, 06:55:26 PM
NY 17/NY 17M is another one with New York's letter-suffixed routes.

That's an oddity for a couple reasons.The length isn't particularly clear. Some signage says it's for 1 exit, other signage says 2 exits. I've seen some things that have no WB concurrency, routing 17M straight onto US 6. The concurrency wouldn't even exist if the US 6 WB slip ramp wasn't there.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: mapman1071 on May 01, 2017, 09:43:19 PM
I-87 & I-287 New York
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: mapman1071 on May 01, 2017, 09:45:13 PM
AZ 87 - AZ 287 Thru Coolidge, AZ
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: jmd41280 on May 01, 2017, 10:37:32 PM
PA 56 & 156 between Avonmore and Spring Church
(https://c1.staticflickr.com/9/8258/29592201435_2f4c7eb223_c.jpg) (https://flic.kr/p/M5XLvz)
PA Routes 56/156 multiplex - Spring Church, PA (https://flic.kr/p/M5XLvz) by Jon Dawson (https://www.flickr.com/photos/jmd41280/), on Flickr

Also in Western PA:

PA 231 & 331 between Acheson and West Middletown (used to connect to a stretch of PA 31 that is now PA 844)
PA 56 & 356 near West Leechburg
PA 68 & 168 in Midland
PA 351 & 551 in Enon Valley
PA 288 & 588 in Zelienople (used to connect to a stretch of PA 88 that is now PA 65)
PA 58 & 358 in Greenville
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: DandyDan on May 02, 2017, 06:21:48 AM
One I don't think was mentioned yet is US 63 and IA 163.  IA 163 got its number for previously being US 163, but Iowa decided to extend 163 several years ago, making the Des Moines to Burlington expressway one number, and creating the overlap with US 63 between Oskaloosa and Ottumwa.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: ilpt4u on June 10, 2017, 07:48:00 PM
US 50 and US 150 in Southern IN comes to mind...
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: dvferyance on June 10, 2017, 07:52:13 PM
I-40 and I-540 used to be duplexed in Arkansas until the northern part became I-49.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Roadgeekteen on June 10, 2017, 08:38:50 PM
I-95/I-495 near DC
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: hotdogPi on June 10, 2017, 08:39:29 PM
Quote from: Roadgeekteen on June 10, 2017, 08:38:50 PM
I-95/I-495 near DC

Reply #6
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: theline on June 11, 2017, 12:00:07 AM
Quote from: ilpt4u on June 10, 2017, 07:48:00 PM
US 50 and US 150 in Southern IN comes to mind...

Reply 28 in this topic:
Quote from: hbelkins on March 29, 2017, 08:34:20 PM
US 50 and US 150 have a concurrency in Indiana.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: ilpt4u on June 11, 2017, 09:57:49 AM
My bad, I tried to read the thread to make sure I wasn't duplicating, but I missed that post

I don't believe this one has been listed, tho:
US 31A and US 431, in Lewisburg, TN
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: JJBers on June 11, 2017, 11:27:47 AM
RI 1A and US 1 are bi-system family in Rhode Island
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Roadgeekteen on June 11, 2017, 01:15:23 PM
Quote from: 1 on June 10, 2017, 08:39:29 PM
Quote from: Roadgeekteen on June 10, 2017, 08:38:50 PM
I-95/I-495 near DC

Reply #6
Oops, thought the 3rd page was the first page. No idea how that happened.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: ilpt4u on June 11, 2017, 01:59:09 PM
IN-550 either has a gap, or is an unsigned concurrency with US 150 (and partially with US 50) between Loogootee and Wheatland

The Wiki article for IN-550 claims it is gapped, and not an unsigned concurrency. But that is good old Wikipedia for ya
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: hbelkins on June 11, 2017, 03:18:28 PM
Quote from: ilpt4u on June 11, 2017, 01:59:09 PM
IN-550 either has a gap, or is an unsigned concurrency with US 150 (and partially with US 50) between Loogootee and Wheatland

The Wiki article for IN-550 claims it is gapped, and not an unsigned concurrency. But that is good old Wikipedia for ya

Indiana's gaps really are gaps. There are at least three flavors of IN 101.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: ilpt4u on June 11, 2017, 06:07:00 PM
Maybe...US 24 Business and US 224, for 1 Block in each direction along Park Dr in Huntington, IN, although looking at Streetview, this may not be a signed US 24 Business route, but Google has it ID'd as such
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Roadgeekteen on June 11, 2017, 06:21:41 PM
Quote from: ilpt4u on June 11, 2017, 06:07:00 PM
Maybe...US 24 Business and US 224, for 1 Block in each direction along Park Dr in Huntington, IN, although looking at Streetview, this may not be a signed US 24 Business route, but Google has it ID'd as such
224 is a child of 24, not business 24.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: ilpt4u on June 11, 2017, 06:36:31 PM
Quote from: Roadgeekteen on June 11, 2017, 06:21:41 PM
Quote from: ilpt4u on June 11, 2017, 06:07:00 PM
Maybe...US 24 Business and US 224, for 1 Block in each direction along Park Dr in Huntington, IN, although looking at Streetview, this may not be a signed US 24 Business route, but Google has it ID'd as such
224 is a child of 24, not business 24.
Even if so, does not Business 24 count as a child of 24 as well, making 224 and Business 24, siblings? Maybe step-siblings?

It may be a Google Maps error -- there is no signage for Business 24 at either end of its route on Google Maps -- US 24 is routed onto what Google describes as "US 24 Bypass"/Huntington Bypass, by the signage seen on Streetview
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Roadgeekteen on June 11, 2017, 08:14:14 PM
Quote from: ilpt4u on June 11, 2017, 06:36:31 PM
Quote from: Roadgeekteen on June 11, 2017, 06:21:41 PM
Quote from: ilpt4u on June 11, 2017, 06:07:00 PM
Maybe...US 24 Business and US 224, for 1 Block in each direction along Park Dr in Huntington, IN, although looking at Streetview, this may not be a signed US 24 Business route, but Google has it ID'd as such
224 is a child of 24, not business 24.
Even if so, does not Business 24 count as a child of 24 as well, making 224 and Business 24, siblings? Maybe step-siblings?

It may be a Google Maps error -- there is no signage for Business 24 at either end of its route on Google Maps -- US 24 is routed onto what Google describes as "US 24 Bypass"/Huntington Bypass, by the signage seen on Streetview
My iq apparently drops to zero when reading this thread.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: US 89 on June 12, 2017, 11:27:23 AM
I don't think this has been said yet: WY 130/230 in Laramie.

Also, US 91 and US 191 were concurrent between Virginia and Idaho Falls in ID.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: ilpt4u on June 12, 2017, 06:43:54 PM
The US 31 and US 431 Nashville concurrency was listed, but a little south of Nashville, around Franklin, TN, they are concurrent once again (they travel between Franklin and Nashville as separate routes)
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Takumi on June 12, 2017, 06:59:04 PM
US 60 and US 360 for a few blocks in Richmond.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: ilpt4u on July 02, 2017, 04:30:18 PM
US 50 and IL-250 between Olney and Sumner

Just drove it today!
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: amroad17 on July 03, 2017, 02:35:00 AM
I have a historic one: US 6 and US 106 from Carbondale, PA to east of Honesdale, PA.
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: plain on July 13, 2017, 02:38:20 AM
Quote from: NE2 on March 30, 2017, 12:48:50 AM
US 60 and US 60 in Newport News.

Doesn't US 19 (or US 19 TRUCK, I forget which one) do the same thing in Pittsburgh?
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: fillup420 on July 16, 2017, 09:48:23 PM
I found one this weekend: NC 41 and NC 411 from US 421 to their split about a mile west
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: ilpt4u on August 19, 2017, 12:16:08 AM
IL gives us another one, in the Western part of the state:

US 136 and IL 336, between Carthage, IL and Tennessee, IL for now
Title: Re: Parent/sibling or sibling/sibling concurrencies
Post by: Flint1979 on August 19, 2017, 01:11:28 AM
Quote from: hbelkins on June 11, 2017, 03:18:28 PM
Quote from: ilpt4u on June 11, 2017, 01:59:09 PM
IN-550 either has a gap, or is an unsigned concurrency with US 150 (and partially with US 50) between Loogootee and Wheatland

The Wiki article for IN-550 claims it is gapped, and not an unsigned concurrency. But that is good old Wikipedia for ya

Indiana's gaps really are gaps. There are at least three flavors of IN 101.
I'm assuming Indiana uses the same number for different sections of highway is because of the way the highways are numbered in Indiana. Indiana's state highways are setup the same way the U.S. highways are going across the country with the even numbers going east and west and the higher numbers being in the south and the same for north-south and the higher numbers being in the west. There are some exceptions though and those are the diagonal routes SH 37, SH 47, SH 56, SH 57, SH 62, and SH 67.