So, you can't have a US highway and interstate in the same state. How about when the same number touches? When they moved US-10 in Minnesota to the new alignment, the old one was named county 10. I'm sure that confuses no one.
Kitchener has King's Highway 8 and Waterloo RR 8 side-by-side. RR 8 between Weber St and the 401 was highway 8's former alignment. This sign can be confusing for non-locals:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FqQmbVpH.jpg&hash=3215a636c52a2d4b6fa1e16a2c82f9c9b91b0bd5)
There's also King's Highway 24 and Norfolk CR 24 north of Simcoe, ON, where the CR is the old alignment of the highway.
You mean like where I-64 has an exit for IN 64 west of New Albany?
Quote from: texaskdog on July 06, 2017, 10:29:24 AM
So, you can't have a US highway and interstate in the same state. . . .
Except it happens. US 69 awaits I-69 in Lufkin . . . .
Also the idiotic I-74 monstrosity and US 74 in, of course, NC.
Quote from: SP Cook on July 06, 2017, 11:43:44 AM
Also the idiotic I-74 monstrosity and US 74 in, of course, NC.
And I-41 and US 41 in WI.
Also, WY 89 and US 89 come really close.
In DE, Concord Pike at I-95 (https://www.google.com/maps/@39.7681491,-75.5376658,3a,75y,284.24h,88.77t/data=!3m7!1e1!3m5!1sHRG8V1I5D6-Im9G58y7VxQ!2e0!6s%2F%2Fgeo0.ggpht.com%2Fcbk%3Fpanoid%3DHRG8V1I5D6-Im9G58y7VxQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D300.56415%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656) is US 202 north of the interchange & DE 202 south of the interchange.
US 3 & MA 3 meet in Cambridge (at Mass Ave./MA 2A).
I-283 & PA 283 interchange w/each other near the PA Turnpike (I-76).
Quote from: hbelkins on July 06, 2017, 11:29:25 AM
You mean like where I-64 has an exit for IN 64 west of New Albany?
You beat me to it. Was going to mention that. Also, I-265 meets IN 265 at I-65, though I imagine IN 265 is going away before too long.
If you include situations where a road continues under the same number but in a different class, this is not terribly uncommon.
In California, I-15, I-110, I-210, and I-238 all continue under the same number but as state routes instead of Interstates.
In Pennsylvania, US 222 continues as PA 222 in Allentown. I was also going to suggest I-378 as a historical example, but I believe the non-freeway portion south of the Lehigh River wasn't designated as PA 378 until the Interstate designation was removed.
Quote from: texaskdog on July 06, 2017, 10:29:24 AM
When they moved US-10 in Minnesota to the new alignment, the old one was named county 10. I'm sure that confuses no one.
It's generally a mistake one makes only once (if at all) because the traffic on county road 10/old highway 10 can be atrocious.
Many cases in NY State: I-787 and NY 787, I-390 and NY 390, I-590 and NY 590, I-690 and NY 690, I-890 and NY 890, I-495 and NY 495, I-481 and NY 481.
!-794 and WI 794 in Milwaukee.
I-20 and GA 20 interchange east of Atlanta
At this intersection: https://goo.gl/eV8bpr County route 657 (https://goo.gl/HxtmHQ) meets county route 657 (https://goo.gl/nu8Uze). Same county even. There is a third CR 657 that does not cross either of these in the same county too.
MN 65 and US 65 used to intersect in Minneapolis where they changed over, though US 65 has now long been truncated.
-MN 61 and Lake/St. Louis County 61, the old alignment of 61 between Duluth and Two Harbors. MnDOT seems to be toning this one down a bit as they apparently removed the physical "JCT COUNTY 61" markers from MN 61.
-I-35 and Freeborn County 35 in Geneva, MN.
-MN 45 and Carlton County 45 in Cloquet.
-MN 62 and Hennepin County 62 in Eden Prairie. The county portion remains after NIMBYs stopped the planned continuation of MN 62.
I-73(/74) intersects NC 73 in Norman
Quote from: TheHighwayMan394 on July 06, 2017, 03:40:43 PM
MN 65 and US 65 used to intersect in Minneapolis where they changed over, though US 65 has now long been truncated.
-MN 61 and Lake/St. Louis County 61, the old alignment of 61 between Duluth and Two Harbors. MnDOT seems to be toning this one down a bit as they apparently removed the physical "JCT COUNTY 61" markers from MN 61.
-I-35 and Freeborn County 35 in Geneva, MN.
-MN 45 and Carlton County 45 in Cloquet.
-MN 62 and Hennepin County 62 in Eden Prairie. The county portion remains after NIMBYs stopped the planned continuation of MN 62.
To add to this, MN-112 and Le Sueur CR-112 intersect:
(https://i.imgur.com/0gYrQwu.jpg)
US 36 intersects CO 36 (an old routing of US 36/40/287) in Byers. I believe there is also a CO 40 in that area, but it doesn't show up on Wikipedia.
GA 20 has an exit on I-20; the State Route is north/south, which is a good idea:
(https://farm5.staticflickr.com/4193/34346887391_479255c492_b.jpg) (https://flic.kr/p/Uk7LZD)
Quote from: formulanone on July 06, 2017, 04:45:31 PM
GA 20 has an exit on I-20; the State Route is north/south, which is a good idea:
Well, it is
right there, at least - turn onto GA 20 here (in either direction) and follow it far enough, and the signs will eventually start saying "WEST". But it's well away from I-20 by then.
Several other examples in the Peach State: US 27 intersects GA 27, for instance. And perhaps best of all, the US 23/GA 23 concurrency (https://www.google.com/maps/@30.8384524,-82.0068487,3a,75y,103.1h,89.4t/data=!3m6!1e1!3m4!1s3E33aTOCmw9hVuQPotJOfA!2e0!7i13312!8i6656) in southeast Georgia.
Quote from: briantroutman on July 06, 2017, 01:59:12 PMI was also going to suggest I-378 as a historical example, but I believe the non-freeway portion south of the Lehigh River wasn't designated as PA 378 until the Interstate designation was removed.
Correct.
US and VA 360.
How about State Routes that share the same number across the State Lines?
IL/MO 110 comes to mind
Similar to I-265 in IN, I-255 in IL continues north of its Interstate designation terminus @ I-270 as IL 255 (still a freeway)
This may be cheating, but IL 43/Harlem Ave and 43rd St near Chicago -- but calling these roads "highways" is a stretch -- a city street and a busy Arterial
Ogden Ave and 34th St is close to here as well, but it is east of Harlem/IL 43, and Ogden loses its US 34 designation at Harlem
US 41/Indianapolis Blvd in Highland, IN has the local 41st St as a Cross Street
I can locate more of the Numbered Route and Street Number crossings, but I think I will stop, as I don't think its the spirit of the OP's request
Quote from: texaskdog on July 06, 2017, 10:29:24 AM
So, you can't have a US highway and interstate in the same state.
Is this is a serious rule?
They are in different parts of the state, but IL has I-24 in Southern IL, and US 24 in Central IL
Unless the statement is to mean a US Highway and Interstate cannot meet and/or be concurrent in the same state. That, I am down with, except for WI, NC, and someday TX
Quote from: ilpt4u on July 06, 2017, 08:15:31 PM
Quote from: texaskdog on July 06, 2017, 10:29:24 AM
So, you can't have a US highway and interstate in the same state.
Is this is a serious rule?
Yes, and until the 74/74 and 41/41 abominations came along, to the best of my knowledge Illinois had the only exception, with the reasoning being that the two routes were so far apart that no one would get them confused.
Quote from: ilpt4u on July 06, 2017, 08:00:41 PM
How about State Routes that share the same number across the State Lines?
IL/MO 110 comes to mind
Similar to I-265 in IN, I-255 in IL continues north of its Interstate designation terminus @ I-270 as IL 255 (still a freeway)
This may be cheating, but IL 43/Harlem Ave and 43rd St near Chicago -- but calling these roads "highways" is a stretch -- a city street and a busy Arterial
Ogden Ave and 34th St is close to here as well, but it is east of Harlem/IL 43, and Ogden loses its US 34 designation at Harlem
US 41/Indianapolis Blvd in Highland, IN has the local 41st St as a Cross Street
I can locate more of the Numbered Route and Street Number crossings, but I think I will stop, as I don't think its the spirit of the OP's request
State Route 200 in ID/MT/ND/MN.
Quote from: hbelkins on July 06, 2017, 10:30:54 PM
Quote from: ilpt4u on July 06, 2017, 08:15:31 PM
Quote from: texaskdog on July 06, 2017, 10:29:24 AM
So, you can't have a US highway and interstate in the same state.
Is this is a serious rule?
Yes, and until the 74/74 and 41/41 abominations came along, to the best of my knowledge Illinois had the only exception, with the reasoning being that the two routes were so far apart that no one would get them confused.
Learn something new every day
I'm sure others have done this before, but I might have to look hard at maps for the next few days, and see if there are other exceptions. I guess TX already is officially an exception, since there are parts of I-69 signed in Houston, and US 69 exists in TX as well
I didn't even realize it was uncommon, let alone a rule. I knew the WI US 41/I-41 thing was weird (same thing with NC and 74), but that can be (at least partially) blamed on us FIBs for not wanting to share I-55 or I-57. I figured they just had to be "away" from each other, a la US 24 and I-24
By "the grid" naturally, there should be few overlapping areas anyway, numerically speaking, with N/S US being E to W::Low to High and N/S Is being E to W::High to Low, and same with E/W US being N to S::Low to High and E/W Is being N to S::High to Low
Only in the "middle" of the country should there be opportunity to break this pattern. 74, 24, and 69 due to diagonal Interstate routes, and 41 being a pretty "middling" number
Quote from: ilpt4u on July 06, 2017, 08:15:31 PM
Quote from: texaskdog on July 06, 2017, 10:29:24 AM
So, you can't have a US highway and interstate in the same state.
Is this is a serious rule?
They are in different parts of the state, but IL has I-24 in Southern IL, and US 24 in Central IL
Unless the statement is to mean a US Highway and Interstate cannot meet and/or be concurrent in the same state. That, I am down with, except for WI, NC, and someday TX
Quote from: hbelkins on July 06, 2017, 10:30:54 PM
Quote from: ilpt4u on July 06, 2017, 08:15:31 PM
Quote from: texaskdog on July 06, 2017, 10:29:24 AM
So, you can't have a US highway and interstate in the same state.
Is this is a serious rule?
Yes, and until the 74/74 and 41/41 abominations came along, to the best of my knowledge Illinois had the only exception, with the reasoning being that the two routes were so far apart that no one would get them confused.
Illinois, being a state with more N-S than E-W mileage, was likely considered to be an unavoidable exception to the "rule" (essentially an idiomatic guideline), as was California. Before the '64 state renumbering effort, there were
two in-state duplications: I-40/US 40 and I-80/US 80; which didn't seem to concern anyone at any level for the 6+ years the situation existed. The fact that the renumberings dealt with the problem was pretty much incidental; the goal of the renumbering was to eliminate multi-route multiplexes; doing so meant truncating many of the US highways entering the state.
What's actually ironic & funny is that the Illinois situation concerning I-24/US 24 could have been avoided back in '57 by simply swapping I-24 and I-26; it would have been logical as well, considering the whole of I-26 exists at a more southerly mean latitude than does I-24!
I keep forgetting about California, even though I'm old enough to remember current maps with the US routes posted, and thinking how neat it was that a route that runs within about an hour of where I live (US 60) went all the way to California.
The "no duplication" rule is why there are no interstates numbered 50 or 60. Any interstates with those numbers would, out of necessity, have passed through states with the same numbers used on US routes.
Arkansas now has I-49 and US 49. Smaller state, but they are still on E-W opposite ends of the state.
iPhone
Quote from: TheHighwayMan394 on July 06, 2017, 03:40:43 PM
-MN 62 and Hennepin County 62 in Eden Prairie. The county portion remains after NIMBYs stopped the planned continuation of MN 62.
Where was that supposed to go?
I wonder if you could make an interstate into I-50 and successfully keep US 50 out of those states (even if you had to reroute it).
Quote from: texaskdog on July 07, 2017, 04:46:02 PM
Quote from: TheHighwayMan394 on July 06, 2017, 03:40:43 PM
-MN 62 and Hennepin County 62 in Eden Prairie. The county portion remains after NIMBYs stopped the planned continuation of MN 62.
Where was that supposed to go?
It was supposed to connect with an interchange at MN 101 at the Dell Road intersection.
Quote from: TheHighwayMan394 on July 07, 2017, 05:13:58 PM
Quote from: texaskdog on July 07, 2017, 04:46:02 PM
Quote from: TheHighwayMan394 on July 06, 2017, 03:40:43 PM
-MN 62 and Hennepin County 62 in Eden Prairie. The county portion remains after NIMBYs stopped the planned continuation of MN 62.
Where was that supposed to go?
It was supposed to connect with an interchange at MN 101 at the Dell Road intersection.
Correct. Although I find it somewhat humorous considering MnDOT pretty much said "fuck MN-101 south of I-94" and that would've left MN-62, as you described, a spur route that would've made little sense, ending at an otherwise unimportant intersection.
US 222 becomes PA 222 at the Allentown city limits due to a denial by the AASHTO of an extension of US 222 into Allentown.
Quote from: ekt8750 on July 07, 2017, 08:01:27 PM
US 222 becomes PA 222 at the Allentown city limits due to a denial by the AASHTO of an extension of US 222 into Allentown.
PA should pull an Oklahoma and just sign it as US 222.
Guess I didn't mean roads that just turn into other roads, I meant completely different roads that meet or cross, causing confusion for inattentive drivers (i.e. anyone not like us)
US 69 and Interstate 69 In Lufkin TX
If left unresolved in Lufkin, they would definitely intersect and probably run concurrently.
There are three solutions.
1) Extend US175 from Jacksonville TX to Woodville and truncate US 69 in Jacksonville.
2) Extend US271 from Tyler to Woodville and truncate US69 in Tyler
3) Delete US175 altogether and extend US75 from Dallas to Woodville along the current US175 and US69.
Another US75 possibility would be to truncate US69 in Durant OK and reroute US 75 along the current US69 to Woodville. This would also require the current US75 being renumbered to IH45. This of course flies in the face of the idea that I45 will eventually extend along SH114 and US287 to Amarillo
Quote from: bwana39 on July 12, 2017, 09:00:25 PM
Another US75 possibility would be to truncate US69 in Durant OK and reroute US 75 along the current US69 to Woodville. This would also require the current US75 being renumbered to IH45. This of course flies in the face of the idea that I45 will eventually extend along SH114 and US287 to Amarillo
Why would I-45 go to Amarillo?
Does GA 10/ GA 10 LOOP count?
Quote from: cabiness42 on July 06, 2017, 01:15:28 PM
Quote from: hbelkins on July 06, 2017, 11:29:25 AM
You mean like where I-64 has an exit for IN 64 west of New Albany?
You beat me to it. Was going to mention that. Also, I-265 meets IN 265 at I-65, though I imagine IN 265 is going away before too long.
NC will eventually have an I-42/NC-42 interchange near Clayton once US-70 between I-40 and Morehead City officially becomes I-42.
On a brief off-topic note, once US-264 is upgraded to interstate standards between Zebulon and Greenville, NC will be the first state to have a 3-di interstate concurrency where both routes begin with an odd number: I-795/I-587 in Wilson.
Quote from: hbelkins on July 07, 2017, 11:08:23 AM
I keep forgetting about California, even though I'm old enough to remember current maps with the US routes posted, and thinking how neat it was that a route that runs within about an hour of where I live (US 60) went all the way to California.
I know the feeling. I lived in Warsaw, NC for a couple of years when I was a kid and it's right off of I-40. Straight shot to Barstow! :-D
Quote from: MNHighwayMan on July 07, 2017, 05:52:08 PM
Quote from: TheHighwayMan394 on July 07, 2017, 05:13:58 PM
Quote from: texaskdog on July 07, 2017, 04:46:02 PM
Quote from: TheHighwayMan394 on July 06, 2017, 03:40:43 PM
-MN 62 and Hennepin County 62 in Eden Prairie. The county portion remains after NIMBYs stopped the planned continuation of MN 62.
Where was that supposed to go?
It was supposed to connect with an interchange at MN 101 at the Dell Road intersection.
Correct. Although I find it somewhat humorous considering MnDOT pretty much said "fuck MN-101 south of I-94" and that would've left MN-62, as you described, a spur route that would've made little sense, ending at an otherwise unimportant intersection.
Actually, it was supposed to meet MN 7 in the now-CSAH 101 vicinity. The milemarkers along MN 62 (minus the 100 that was added to them) reflect this original proposed terminus.
Also, as I understand it, it wasn't NIMBY's that stopped it, but changing priorities at the county level. Then-CSAH 18/now-US 169 in particular was becoming problematic to fund and construct. I still remember when the last "inside the Beltline" segment next to Hopkins wasn't yet completed.
Quote from: froggie on July 13, 2017, 09:50:41 AM
Quote from: MNHighwayMan on July 07, 2017, 05:52:08 PM
Quote from: TheHighwayMan394 on July 07, 2017, 05:13:58 PM
Quote from: texaskdog on July 07, 2017, 04:46:02 PM
Quote from: TheHighwayMan394 on July 06, 2017, 03:40:43 PM
-MN 62 and Hennepin County 62 in Eden Prairie. The county portion remains after NIMBYs stopped the planned continuation of MN 62.
Where was that supposed to go?
It was supposed to connect with an interchange at MN 101 at the Dell Road intersection.
Correct. Although I find it somewhat humorous considering MnDOT pretty much said "fuck MN-101 south of I-94" and that would've left MN-62, as you described, a spur route that would've made little sense, ending at an otherwise unimportant intersection.
Actually, it was supposed to meet MN 7 in the now-CSAH 101 vicinity. The milemarkers along MN 62 (minus the 100 that was added to them) reflect this original proposed terminus.
Also, as I understand it, it wasn't NIMBY's that stopped it, but changing priorities at the county level. Then-CSAH 18/now-US 169 in particular was becoming problematic to fund and construct. I still remember when the last "inside the Beltline" segment next to Hopkins wasn't yet completed.
Looking at the maps after the previous posts, that looked like it made the most sense. MN is not fast to build highways.
FL-29 and county road 29 in Collier County Florida just north of Everglades City. They change when they cross US 41.
Quote from: froggie on July 13, 2017, 09:50:41 AM
Actually, it was supposed to meet MN 7 in the now-CSAH 101 vicinity. The milemarkers along MN 62 (minus the 100 that was added to them) reflect this original proposed terminus.
Also, as I understand it, it wasn't NIMBY's that stopped it, but changing priorities at the county level. Then-CSAH 18/now-US 169 in particular was becoming problematic to fund and construct. I still remember when the last "inside the Beltline" segment next to Hopkins wasn't yet completed.
So was this proposed freeway/roadway/whatever then supposed to follow some new alignment? I ask because I measured the distance on Google Earth following CSAH-62 and it pretty well measures out (within error) to being the start of Mile 100 at the CSAH-62/101 intersection.
Edit: So the route logpoint states that the present-day Metro MN-62 begins at mile 103.592. There is no way to get to MN-7 with that short of a path (ie ~3.6 miles) without cutting a brand new route through all those suburban housing developments, and I find it hard to believe that ever was MnDOT's intention.
It would have followed the existing CSAH 62 alignment west to roughly Scenic Heights Dr, then turned on new alignment northwest and north through what is now Purgatory Park to the general MN 7/CSAH 101 vicinity. Back in the early 1960s when planning first began, there was little in the way of "suburban housing development" out there. Now while that started changing in the mid 1960s, the general proposed corridor remained intact at least into the early 1970s.
Some iterations had it tying into CSAH 101 at Excelsior Blvd. The length of this iteration roughly matches the mileposts along MN 62.
Also, this was planned under the county, not MnDOT. MnDOT didn't take over the Crosstown until 1988, and even then the segment west of 494 remained under county control.
If I can find them when I get home, I'll post a couple map scans I have of the corridor online and share.
Quote from: froggie on July 13, 2017, 04:58:27 PM
It would have followed the existing CSAH 62 alignment west to roughly Scenic Heights Dr, then turned on new alignment northwest and north through what is now Purgatory Park to the general MN 7/CSAH 101 vicinity. Back in the early 1960s when planning first began, there was little in the way of "suburban housing development" out there. Now while that started changing in the mid 1960s, the general proposed corridor remained intact at least into the early 1970s.
Some iterations had it tying into CSAH 101 at Excelsior Blvd. The length of this iteration roughly matches the mileposts along MN 62.
Also, this was planned under the county, not MnDOT. MnDOT didn't take over the Crosstown until 1988, and even then the segment west of 494 remained under county control.
If I can find them when I get home, I'll post a couple map scans I have of the corridor online and share.
Interesting. Guess it must just be coincidence that they're about the same length then. Would love to see those maps if you get a chance.
TX70 & US70 cross in Matador.
Every intersection between a route and one of its banner routes!
Haines City, FL US 17 and FL 17 intersect since US 27 ALT was decommissioned. I am not sure but I think Polk County 17 meets the two, as its not signed there, but at nearby US 27 it shows CR 17 going east to that location in signage.
US 95 and AZ 95 in Quartzsite:
(https://farm3.staticflickr.com/2888/32766345393_38a1c59f2f_h.jpg) (https://flic.kr/p/RVs5Vx)95AZb (https://flic.kr/p/RVs5Vx) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
I am guessing but I will bet AZ originally wanted US 95 for itself, but CA objected so they created AZ 95 to spite their neighbor for taking it away.
Quote from: roadman65 on July 17, 2017, 09:42:10 AM
I am guessing but I will bet AZ originally wanted US 95 for itself, but CA objected so they created AZ 95 to spite their neighbor for taking it away.
Actually it looks like AZ 95 might have been the result of US 95 being extended to Blythe. AZ 95 at the time would have just ran from the border at San Luis north to AZ 72:
(https://www.arizonaroads.com/maps/1938-3.jpg)
I'd speculate that Arizona wanted US 95 to cross the Colorado in Parker and continue south to the border. Given that former SSR 195 in California was a much straighter route from US 66 out of Needles to US 60/70 I'd speculate that's why it was chosen over the Arizona side:
http://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~239588~5511892:Road-Map-of-the-State-of-California?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&qvq=q:caltrans;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&mi=69&trs=86
And AZ 95 didn't really change north of Quartzsite when US 95 made it to Arizona:
(https://www.arizonaroads.com/maps/1961-3.jpg)
But that said I really have no idea why there is a second section of AZ 95 north from Needles. BTW, I can't believe Arizonaroads is still active:
https://www.arizonaroads.com/maps/index.html
Quote from: roadman65 on July 17, 2017, 09:42:10 AM
I am guessing but I will bet AZ originally wanted US 95 for itself, but CA objected so they created AZ 95 to spite their neighbor for taking it away.
Just like WY 89 and US 89. WY 89 was numbered as such back when US 89 ended in Spanish Fork UT, in hopes of getting 89 extended. Then, apparently US 89 was extended along today's US 189, and WY 89 was renumbered to 91
to reduce confusion. But then a few years later 89 was moved to its current route through UT and ID, and US 189 was created. WY was apparently so pissed off by this that they renumbered WY 91 back to WY 89.
The cure for not duplicating I-69/US 69 in Lufkin, TX: truncate I-69 at Memphis.
Quote from: roadguy2 on July 13, 2017, 01:54:09 AM
Quote from: bwana39 on July 12, 2017, 09:00:25 PM
Another US75 possibility would be to truncate US69 in Durant OK and reroute US 75 along the current US69 to Woodville. This would also require the current US75 being renumbered to IH45. This of course flies in the face of the idea that I45 will eventually extend along SH114 and US287 to Amarillo
Why would I-45 go to Amarillo?
Doesn't make sense to me either. NCTCOG would not cross the Dallas plan back in the 60's. Texas is like it's own nation. Why build a n interstate to Oklahoma when you can build one across Texas. Also remember I45 and US75 complete one another even though they never meet.
So much on my Trite response. It is more likely they are waiting until they finish the toll roads before they look for Interstate numbering.
Quote from: cjk374 on July 19, 2017, 07:32:55 PM
The cure for not duplicating I-69/US 69 in Lufkin, TX: truncate I-69 at Memphis.
I don't fully disagree with you. The Arkansas segment is a mess. So I understand, it will be slightly CLOSER to go through Texarkana and Little Rock.
Interstate 30 is near capacity. There needs to be some relief. This said the Arkansas routing of I69 us not the answer. They take diagonal path and put a significant east west segment in.
Then they cross the Mississippi river too far south. The road should cross at farthest south around Clarksdale Ms if not nearing Tunica. The Arkansas segment should run from Haughton La to Eldorado Ar, to Monticello AR. , Skipping McGehee to near Dumas then run up the west bank to the crossing.
To me crossing nearer to Tunica is the better choice it adds an additional crossing for greater Memphis.
But east central Arkansas wants a bridge in the middle of nowhere.
So yes, I agree if they run all over Arkansas to me it is a deal breaker.
Quote from: Max Rockatansky on July 17, 2017, 10:21:45 AM
But that said I really have no idea why there is a second section of AZ 95 north from Needles. BTW, I can't believe Arizonaroads is still active:
https://www.arizonaroads.com/maps/index.html
I remember reading that AZ 95's two segments are officially connected via Needles and I-40, but it's (naturally) unsigned on the California side (because why would California recognize it), meaning there's a US 95/AZ 95 overlap in California!
(What the hell's a non-cutout US 95 shield doing in California?! https://www.google.com/maps/@34.8483803,-114.6143672,3a,66.8y,90.47h,90.51t/data=!3m4!1e1!3m2!1sBAg_Exam6ll3KJO8lY0XLQ!2e0 )
Closest CalTrans gets to acknowledging AZ 95 in California? https://www.google.com/maps/@34.8483984,-114.6103334,3a,66.8y,139.81h,87.62t/data=!3m4!1e1!3m2!1sm_xuzdl1H9a_RyssdO9j_A!2e0
lol, guide sign to Arizona I-40 as you're leaving Arizona and entering California. Wrong state on the shield, AZDOT https://www.google.com/maps/@34.8529731,-114.608262,3a,38.1y,253.05h,80.66t/data=!3m4!1e1!3m2!1skECux8ZvQwTv5YONWo5bzQ!2e0
Quote from: Bickendan on July 27, 2017, 06:57:19 AM
Quote from: Max Rockatansky on July 17, 2017, 10:21:45 AM
But that said I really have no idea why there is a second section of AZ 95 north from Needles. BTW, I can't believe Arizonaroads is still active:
https://www.arizonaroads.com/maps/index.html
I remember reading that AZ 95's two segments are officially connected via Needles and I-40, but it's (naturally) unsigned on the California side (because why would California recognize it), meaning there's a US 95/AZ 95 overlap in California!
(What the hell's a non-cutout US 95 shield doing in California?! https://www.google.com/maps/@34.8483803,-114.6143672,3a,66.8y,90.47h,90.51t/data=!3m4!1e1!3m2!1sBAg_Exam6ll3KJO8lY0XLQ!2e0 )
Closest CalTrans gets to acknowledging AZ 95 in California? https://www.google.com/maps/@34.8483984,-114.6103334,3a,66.8y,139.81h,87.62t/data=!3m4!1e1!3m2!1sm_xuzdl1H9a_RyssdO9j_A!2e0
lol, guide sign to Arizona I-40 as you're leaving Arizona and entering California. Wrong state on the shield, AZDOT https://www.google.com/maps/@34.8529731,-114.608262,3a,38.1y,253.05h,80.66t/data=!3m4!1e1!3m2!1skECux8ZvQwTv5YONWo5bzQ!2e0
There are a couple more non-cutout US Shields in California that I've found:
(https://farm5.staticflickr.com/4278/34959428443_e69caa0d54_k.jpg) (https://flic.kr/p/Vgfd7g)395USb (https://flic.kr/p/Vgfd7g) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
(https://farm5.staticflickr.com/4288/35769673005_b2e4948bc5_k.jpg) (https://flic.kr/p/WuQVA6)395USa (https://flic.kr/p/WuQVA6) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
Really I get what AZDOT was going for with a state highway to Needles, I'm just not getting why it has to be numbered "95" of all things. If route continuity was such a big thing than AZDOT should have adopted Mohave County Routes 1 and 10 south to I-40 through Toppock...it isn't like there aren't already two AZ 95Ss connecting to California already.
at one time, Michigan was big on having their same number US-xx and M-xx routes meeting. Historic examples includes M-10 and US-10 in Flint in the 1930s, US-24 and M-24 in Pontiac (before I-75 was built in the 1960s), US-25 and M-25 in the thumb, US-112 and M-112 at the current day Exit 210 on I-94.
Quote from: Max Rockatansky on July 27, 2017, 08:02:53 AM
Quote from: Bickendan on July 27, 2017, 06:57:19 AM
Quote from: Max Rockatansky on July 17, 2017, 10:21:45 AM
But that said I really have no idea why there is a second section of AZ 95 north from Needles. BTW, I can't believe Arizonaroads is still active:
https://www.arizonaroads.com/maps/index.html
I remember reading that AZ 95's two segments are officially connected via Needles and I-40, but it's (naturally) unsigned on the California side (because why would California recognize it), meaning there's a US 95/AZ 95 overlap in California!
(What the hell's a non-cutout US 95 shield doing in California?! https://www.google.com/maps/@34.8483803,-114.6143672,3a,66.8y,90.47h,90.51t/data=!3m4!1e1!3m2!1sBAg_Exam6ll3KJO8lY0XLQ!2e0 )
Closest CalTrans gets to acknowledging AZ 95 in California? https://www.google.com/maps/@34.8483984,-114.6103334,3a,66.8y,139.81h,87.62t/data=!3m4!1e1!3m2!1sm_xuzdl1H9a_RyssdO9j_A!2e0
lol, guide sign to Arizona I-40 as you're leaving Arizona and entering California. Wrong state on the shield, AZDOT https://www.google.com/maps/@34.8529731,-114.608262,3a,38.1y,253.05h,80.66t/data=!3m4!1e1!3m2!1skECux8ZvQwTv5YONWo5bzQ!2e0
There are a couple more non-cutout US Shields in California that I've found:
(https://farm5.staticflickr.com/4278/34959428443_e69caa0d54_k.jpg) (https://flic.kr/p/Vgfd7g)395USb (https://flic.kr/p/Vgfd7g) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
(https://farm5.staticflickr.com/4288/35769673005_b2e4948bc5_k.jpg) (https://flic.kr/p/WuQVA6)395USa (https://flic.kr/p/WuQVA6) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
Really I get what AZDOT was going for with a state highway to Needles, I'm just not getting why it has to be numbered "95" of all things. If route continuity was such a big thing than AZDOT should have adopted Mohave County Routes 1 and 10 south to I-40 through Toppock...it isn't like there aren't already two AZ 95Ss connecting to California already.
(from Max's first pic): SPEEDING KILLS BEARS (very unique sign BTW)
Wouldn't a more effective message read "BEARS KILL SPEEDERS" or "WE FEED SPEEDERS TO THE BEARS"? :sombrero:
Quote from: cjk374 on July 29, 2017, 08:17:23 AM
Quote from: Max Rockatansky on July 27, 2017, 08:02:53 AM
Quote from: Bickendan on July 27, 2017, 06:57:19 AM
Quote from: Max Rockatansky on July 17, 2017, 10:21:45 AM
But that said I really have no idea why there is a second section of AZ 95 north from Needles. BTW, I can't believe Arizonaroads is still active:
https://www.arizonaroads.com/maps/index.html
I remember reading that AZ 95's two segments are officially connected via Needles and I-40, but it's (naturally) unsigned on the California side (because why would California recognize it), meaning there's a US 95/AZ 95 overlap in California!
(What the hell's a non-cutout US 95 shield doing in California?! https://www.google.com/maps/@34.8483803,-114.6143672,3a,66.8y,90.47h,90.51t/data=!3m4!1e1!3m2!1sBAg_Exam6ll3KJO8lY0XLQ!2e0 )
Closest CalTrans gets to acknowledging AZ 95 in California? https://www.google.com/maps/@34.8483984,-114.6103334,3a,66.8y,139.81h,87.62t/data=!3m4!1e1!3m2!1sm_xuzdl1H9a_RyssdO9j_A!2e0
lol, guide sign to Arizona I-40 as you're leaving Arizona and entering California. Wrong state on the shield, AZDOT https://www.google.com/maps/@34.8529731,-114.608262,3a,38.1y,253.05h,80.66t/data=!3m4!1e1!3m2!1skECux8ZvQwTv5YONWo5bzQ!2e0
There are a couple more non-cutout US Shields in California that I've found:
(https://farm5.staticflickr.com/4278/34959428443_e69caa0d54_k.jpg) (https://flic.kr/p/Vgfd7g)395USb (https://flic.kr/p/Vgfd7g) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
(https://farm5.staticflickr.com/4288/35769673005_b2e4948bc5_k.jpg) (https://flic.kr/p/WuQVA6)395USa (https://flic.kr/p/WuQVA6) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
Really I get what AZDOT was going for with a state highway to Needles, I'm just not getting why it has to be numbered "95" of all things. If route continuity was such a big thing than AZDOT should have adopted Mohave County Routes 1 and 10 south to I-40 through Toppock...it isn't like there aren't already two AZ 95Ss connecting to California already.
(from Max's first pic): SPEEDING KILLS BEARS (very unique sign BTW)
Wouldn't a more effective message read "BEARS KILL SPEEDERS" or "WE FEED SPEEDERS TO THE BEARS"? :sombrero:
And the irony is that I can't even remember the last time I actually encountered a bear in Yosemite, Kings Canyon, and even Sequoia National Park. I ran into black bears all the time in central Florida out in the swamp boons, you'd think they would be more attracted to the smell of the food I'm carrying.
Those may likely be NPS signs. Separate maintenance authority.
Quote from: SSOWorld on July 30, 2017, 01:14:26 PM
Those may likely be NPS signs. Separate maintenance authority.
In the case of Yosemite they definitely are Park Service maintained which is why the California spades look so strange. It looks like the park has a MUTCD supplier for the US 395 shields. The second one I posted was replaced this year in fact.
Quote from: Bickendan on July 27, 2017, 06:57:19 AM
Quote from: Max Rockatansky on July 17, 2017, 10:21:45 AM
But that said I really have no idea why there is a second section of AZ 95 north from Needles. BTW, I can't believe Arizonaroads is still active:
https://www.arizonaroads.com/maps/index.html
I remember reading that AZ 95's two segments are officially connected via Needles and I-40, but it's (naturally) unsigned on the California side (because why would California recognize it), meaning there's a US 95/AZ 95 overlap in California!
(What the hell's a non-cutout US 95 shield doing in California?! https://www.google.com/maps/@34.8483803,-114.6143672,3a,66.8y,90.47h,90.51t/data=!3m4!1e1!3m2!1sBAg_Exam6ll3KJO8lY0XLQ!2e0 )
Closest CalTrans gets to acknowledging AZ 95 in California? https://www.google.com/maps/@34.8483984,-114.6103334,3a,66.8y,139.81h,87.62t/data=!3m4!1e1!3m2!1sm_xuzdl1H9a_RyssdO9j_A!2e0
lol, guide sign to Arizona I-40 as you're leaving Arizona and entering California. Wrong state on the shield, AZDOT https://www.google.com/maps/@34.8529731,-114.608262,3a,38.1y,253.05h,80.66t/data=!3m4!1e1!3m2!1skECux8ZvQwTv5YONWo5bzQ!2e0
I don't know that it's actually true that AZ 95 exists in California - there is no record of that being the case in any of AZDOT's documentation that I've ever been able to find - nor is it borne out in the mileposts or in AZDOT's route log.
That said, this is my favorite of the Needles signs
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.corcohighways.org%2Fhighways%2Faz%2Faz95%2F68toca%2F15.jpg&hash=44c38be3283c4213c735040be97f92b25f9d1d2c)
They took an "Arizona 95" sign and covered the "Arizona" label.
Has I-759 becoming AL 759 been mentioned yet? I don't seem to recall if it has...
Quote from: bwana39 on July 27, 2017, 12:37:36 AM
Quote from: cjk374 on July 19, 2017, 07:32:55 PM
The cure for not duplicating I-69/US 69 in Lufkin, TX: truncate I-69 at Memphis.
I don't fully disagree with you. The Arkansas segment is amess. So I understand, it will be slightly CLOSER to go through Texarkana and Little Rock.
Interstate 30 is near capacity. There needs to be some relief. This said the Arkansas routing of I69 us not the answer. They take diagonal path and put a significant east west segment in.
Then they cross the Mississi river too far south. The road should cross at farthest south around Clarksdale Ms if not nearing Tunica. The Arkansas segment should run from Haughtiness La to Eldorado Ar, to Monticello AR. , Skipping Mcgehe to neat Dumas then run up the west bank to the crossing.
To me crossing nearer to Tunica is the better choice it adds an additional crossing for greater Memphis.
Bur east central Arkansas wants a bridge in the middle of nowhere.
So yes, I agree if they run all over Arkansas to me it is a deal breaker.
What you're describing was originally proposed by Arkansas congressman Dickey back when the routing for High Priority Corridor #18 -- as I-69 -- was being finalized circa 1995 (NHS legislation from that year). It became a controversy and more or less a tug-of-war between Mississippi and Arkansas. AR wanted I-69 to head straight up US 79 via Pine Bluff and exit into MS somewhere around the US 49 Mississippi River bridge; MS originally wanted to route I-69 straight down US 61 to US 82, then turn west via Greenville and thence into AR. So what eventually was proposed was called the "Dickey Split", where
both alignments (US 82/61 and US 79/49) would have been built, possibly as a E/W arrangement. The divergence point would have been near El Dorado, with the reconnection north of the point where US 49 and US 61 meet in northern MS. But two alignments were eventually considered redundant, and the alignment favoring MS was selected but rerouted to follow US 278 across the southern part of AR rather than US 82, deemed too close to the parallel I-20 (the presence of U of A/Monticello was also one of the deciding factors in this instance). Even though the Pine Bluff alignment was not selected, as a "consolation prize" the use of corridor funds to extend I-530 south of Pine Bluff to intersect I-69 west of Monticello was tacked on to the corridor's authorizing legislation in the form of an additional SIU. Ironically, that I-530 extension, even as the 2-lane expressway AR 530, will in all likelihood be completed well before mainline I-69; it's about 60% done today.
Quote from: Max Rockatansky on July 29, 2017, 06:28:08 PM
Quote from: cjk374 on July 29, 2017, 08:17:23 AM
Quote from: Max Rockatansky on July 27, 2017, 08:02:53 AM
Quote from: Bickendan on July 27, 2017, 06:57:19 AM
Quote from: Max Rockatansky on July 17, 2017, 10:21:45 AM
But that said I really have no idea why there is a second section of AZ 95 north from Needles. BTW, I can't believe Arizonaroads is still active:
https://www.arizonaroads.com/maps/index.html
I remember reading that AZ 95's two segments are officially connected via Needles and I-40, but it's (naturally) unsigned on the California side (because why would California recognize it), meaning there's a US 95/AZ 95 overlap in California!
(What the hell's a non-cutout US 95 shield doing in California?! https://www.google.com/maps/@34.8483803,-114.6143672,3a,66.8y,90.47h,90.51t/data=!3m4!1e1!3m2!1sBAg_Exam6ll3KJO8lY0XLQ!2e0 )
Closest CalTrans gets to acknowledging AZ 95 in California? https://www.google.com/maps/@34.8483984,-114.6103334,3a,66.8y,139.81h,87.62t/data=!3m4!1e1!3m2!1sm_xuzdl1H9a_RyssdO9j_A!2e0
lol, guide sign to Arizona I-40 as you're leaving Arizona and entering California. Wrong state on the shield, AZDOT https://www.google.com/maps/@34.8529731,-114.608262,3a,38.1y,253.05h,80.66t/data=!3m4!1e1!3m2!1skECux8ZvQwTv5YONWo5bzQ!2e0
There are a couple more non-cutout US Shields in California that I've found:
(https://farm5.staticflickr.com/4278/34959428443_e69caa0d54_k.jpg) (https://flic.kr/p/Vgfd7g)395USb (https://flic.kr/p/Vgfd7g) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
(https://farm5.staticflickr.com/4288/35769673005_b2e4948bc5_k.jpg) (https://flic.kr/p/WuQVA6)395USa (https://flic.kr/p/WuQVA6) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
Really I get what AZDOT was going for with a state highway to Needles, I'm just not getting why it has to be numbered "95" of all things. If route continuity was such a big thing than AZDOT should have adopted Mohave County Routes 1 and 10 south to I-40 through Toppock...it isn't like there aren't already two AZ 95Ss connecting to California already.
(from Max's first pic): SPEEDING KILLS BEARS (very unique sign BTW)
Wouldn't a more effective message read "BEARS KILL SPEEDERS" or "WE FEED SPEEDERS TO THE BEARS"? :sombrero:
And the irony is that I can't even remember the last time I actually encountered a bear in Yosemite, Kings Canyon, and even Sequoia National Park. I ran into black bears all the time in central Florida out in the swamp boons, you'd think they would be more attracted to the smell of the food I'm carrying.
I saw bears in my neighborhood in Sanford FL.. My previous boss had a bear in their hot tub... It broke thru the screened lanai to take a bath
LGMS428
Quote from: jwolfer on September 02, 2017, 10:04:05 PM
Quote from: Max Rockatansky on July 29, 2017, 06:28:08 PM
Quote from: cjk374 on July 29, 2017, 08:17:23 AM
Quote from: Max Rockatansky on July 27, 2017, 08:02:53 AM
Quote from: Bickendan on July 27, 2017, 06:57:19 AM
Quote from: Max Rockatansky on July 17, 2017, 10:21:45 AM
But that said I really have no idea why there is a second section of AZ 95 north from Needles. BTW, I can't believe Arizonaroads is still active:
https://www.arizonaroads.com/maps/index.html
I remember reading that AZ 95's two segments are officially connected via Needles and I-40, but it's (naturally) unsigned on the California side (because why would California recognize it), meaning there's a US 95/AZ 95 overlap in California!
(What the hell's a non-cutout US 95 shield doing in California?! https://www.google.com/maps/@34.8483803,-114.6143672,3a,66.8y,90.47h,90.51t/data=!3m4!1e1!3m2!1sBAg_Exam6ll3KJO8lY0XLQ!2e0 )
Closest CalTrans gets to acknowledging AZ 95 in California? https://www.google.com/maps/@34.8483984,-114.6103334,3a,66.8y,139.81h,87.62t/data=!3m4!1e1!3m2!1sm_xuzdl1H9a_RyssdO9j_A!2e0
lol, guide sign to Arizona I-40 as you're leaving Arizona and entering California. Wrong state on the shield, AZDOT https://www.google.com/maps/@34.8529731,-114.608262,3a,38.1y,253.05h,80.66t/data=!3m4!1e1!3m2!1skECux8ZvQwTv5YONWo5bzQ!2e0
There are a couple more non-cutout US Shields in California that I've found:
(https://farm5.staticflickr.com/4278/34959428443_e69caa0d54_k.jpg) (https://flic.kr/p/Vgfd7g)395USb (https://flic.kr/p/Vgfd7g) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
(https://farm5.staticflickr.com/4288/35769673005_b2e4948bc5_k.jpg) (https://flic.kr/p/WuQVA6)395USa (https://flic.kr/p/WuQVA6) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
Really I get what AZDOT was going for with a state highway to Needles, I'm just not getting why it has to be numbered "95" of all things. If route continuity was such a big thing than AZDOT should have adopted Mohave County Routes 1 and 10 south to I-40 through Toppock...it isn't like there aren't already two AZ 95Ss connecting to California already.
(from Max's first pic): SPEEDING KILLS BEARS (very unique sign BTW)
Wouldn't a more effective message read "BEARS KILL SPEEDERS" or "WE FEED SPEEDERS TO THE BEARS"? :sombrero:
And the irony is that I can't even remember the last time I actually encountered a bear in Yosemite, Kings Canyon, and even Sequoia National Park. I ran into black bears all the time in central Florida out in the swamp boons, you'd think they would be more attracted to the smell of the food I'm carrying.
I saw bears in my neighborhood in Sanford FL.. My previous boss had a bear in their hot tub... It broke thru the screened lanai to take a bath
LGMS428
It's a problem in Central Florida, are they still authorizing Bear hunts?
Quote from: Max Rockatansky on September 02, 2017, 10:44:40 PM
Quote from: jwolfer on September 02, 2017, 10:04:05 PM
Quote from: Max Rockatansky on July 29, 2017, 06:28:08 PM
Quote from: cjk374 on July 29, 2017, 08:17:23 AM
Quote from: Max Rockatansky on July 27, 2017, 08:02:53 AM
Quote from: Bickendan on July 27, 2017, 06:57:19 AM
Quote from: Max Rockatansky on July 17, 2017, 10:21:45 AM
But that said I really have no idea why there is a second section of AZ 95 north from Needles. BTW, I can't believe Arizonaroads is still active:
https://www.arizonaroads.com/maps/index.html
I remember reading that AZ 95's two segments are officially connected via Needles and I-40, but it's (naturally) unsigned on the California side (because why would California recognize it), meaning there's a US 95/AZ 95 overlap in California!
(What the hell's a non-cutout US 95 shield doing in California?! https://www.google.com/maps/@34.8483803,-114.6143672,3a,66.8y,90.47h,90.51t/data=!3m4!1e1!3m2!1sBAg_Exam6ll3KJO8lY0XLQ!2e0 )
Closest CalTrans gets to acknowledging AZ 95 in California? https://www.google.com/maps/@34.8483984,-114.6103334,3a,66.8y,139.81h,87.62t/data=!3m4!1e1!3m2!1sm_xuzdl1H9a_RyssdO9j_A!2e0
lol, guide sign to Arizona I-40 as you're leaving Arizona and entering California. Wrong state on the shield, AZDOT https://www.google.com/maps/@34.8529731,-114.608262,3a,38.1y,253.05h,80.66t/data=!3m4!1e1!3m2!1skECux8ZvQwTv5YONWo5bzQ!2e0
There are a couple more non-cutout US Shields in California that I've found:
(https://farm5.staticflickr.com/4278/34959428443_e69caa0d54_k.jpg) (https://flic.kr/p/Vgfd7g)395USb (https://flic.kr/p/Vgfd7g) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
(https://farm5.staticflickr.com/4288/35769673005_b2e4948bc5_k.jpg) (https://flic.kr/p/WuQVA6)395USa (https://flic.kr/p/WuQVA6) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
Really I get what AZDOT was going for with a state highway to Needles, I'm just not getting why it has to be numbered "95" of all things. If route continuity was such a big thing than AZDOT should have adopted Mohave County Routes 1 and 10 south to I-40 through Toppock...it isn't like there aren't already two AZ 95Ss connecting to California already.
(from Max's first pic): SPEEDING KILLS BEARS (very unique sign BTW)
Wouldn't a more effective message read "BEARS KILL SPEEDERS" or "WE FEED SPEEDERS TO THE BEARS"? :sombrero:
And the irony is that I can't even remember the last time I actually encountered a bear in Yosemite, Kings Canyon, and even Sequoia National Park. I ran into black bears all the time in central Florida out in the swamp boons, you'd think they would be more attracted to the smell of the food I'm carrying.
I saw bears in my neighborhood in Sanford FL.. My previous boss had a bear in their hot tub... It broke thru the screened lanai to take a bath
LGMS428
It's a problem in Central Florida, are they still authorizing Bear hunts?
Yes on the bear hunts. Seminole County near Wekiva State Park seems to be the worst where suburbia come right up to wilderness areas.
My uncle saw a bear in the neighborhood where he anf my parents live in Middleburg, Clay County near Jacksonville.
LGMS428
US 25 and GA 25 meet (hidden designation for US 17); but there's also a signed Spur Route GA 25 where they meet in Brunswick:
(https://farm8.staticflickr.com/7844/47377097381_ea6d29bc19_b.jpg) (https://flic.kr/p/2fby1sz)
Quote from: formulanone on March 14, 2019, 09:15:20 AM
US 25 and GA 25 meet (hidden designation for US 17)
snipped image
I wish. But nooo, Georgia insists on signing all these underlying state routes that I doubt anyone even uses to navigate.
Quote from: US 89 on March 14, 2019, 11:32:19 AM
Quote from: formulanone on March 14, 2019, 09:15:20 AM
US 25 and GA 25 meet (hidden designation for US 17)
snipped image
I wish. But nooo, Georgia insists on signing all these underlying state routes that I doubt anyone even uses to navigate.
Georgia: "Hidden" but "not hidden", except where denoted (or forgotten) is more like it.
And of course, there's the tiny portion of GA 25 northwest of Savannah that is not US 17.
Arkansas has I-49 and US 49.
US 70 crosses TX 70.
US 59 comes within about 2 miles from AR 59 in the Siloam Springs area. I don't know if there was a "border war" or if AR 59 just happens to have the same number.
There might have been a disagreement between Oklahoma and Arkansas over the routing of US 71. The 1927 official Oklahoma shows US 71 running through Oklahoma between Fort Smith and Mena.
Quote from: briantroutman on July 06, 2017, 01:59:12 PM
If you include situations where a road continues under the same number but in a different class, this is not terribly uncommon.
In California, I-15, I-110, I-210, and I-238 all continue under the same number but as state routes instead of Interstates.
In Pennsylvania, US 222 continues as PA 222 in Allentown. I was also going to suggest I-378 as a historical example, but I believe the non-freeway portion south of the Lehigh River wasn't designated as PA 378 until the Interstate designation was removed.
In California I-710 was going to continue as CA-710 if the freeway was going to expand from Alhambra to Pasadena at the CA-134@ I-210.
Also there were old maps showing that there was going to be a CA-380 west of I-380@ I-280 interchange in San Bruno.
There are also lollipop-shaped routes that intersect themselves. Like QC 132, which loops around the Gaspe Peninsula and back to intersect itself near Mont-Joli.
Quote from: hbelkins on July 06, 2017, 10:30:54 PM
Quote from: ilpt4u on July 06, 2017, 08:15:31 PM
Quote from: texaskdog on July 06, 2017, 10:29:24 AM
So, you can't have a US highway and interstate in the same state.
Is this is a serious rule?
Yes, and until the 74/74 and 41/41 abominations came along, to the best of my knowledge Illinois had the only exception, with the reasoning being that the two routes were so far apart that no one would get them confused.
No such rule in Michigan. We currently have I- and M-69, 75, 94, and 96; US-10 and M-10; US-24 and M-24; and US-45 and M-45. Used to be even more. Michigan actually originally made a point of assigning nearby M and US routes the same number. Thus we used to have US-112 and M-112 running parallel only about a mile or so apart between Detroit and Ypsilanti, M-131's southern terminus used to be at US-131's northern terminus, and similar with 24 and 25.
Most of Michigan's current number duplications are far part enough that there's no confusion, although I-96/M-96 aren't all that far apart, nor are I-75/M-75 and US-24/M-24. The latter have interchanges with I-75 only 12 miles apart and there are signs on I-75 to remind motorists of the distinction.
(https://i.imgur.com/NITgq7T.jpg)