AARoads Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

New rules for political content in signatures and user profiles. See this thread for details.

Author Topic: Same number concurrencies or highways meeting  (Read 5215 times)

Max Rockatansky

  • *
  • Offline Offline

  • Posts: 8286
  • Location: Route 9, Sector 26
  • Last Login: Today at 01:00:19 AM
    • Sure, Why Not? (Highway Blog Spot)
Re: Same number concurrencies or highways meeting
« Reply #50 on: July 17, 2017, 07:43:56 AM »

US 95 and AZ 95 in Quartzsite:

95AZb by Max Rockatansky, on Flickr


roadman65

  • *
  • Offline Offline

  • Posts: 8862
  • Location: Orlando, fl
  • Last Login: Today at 12:01:55 AM
Re: Same number concurrencies or highways meeting
« Reply #51 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.
Logged
Every day is a winding road, you just got to get used to it.

Sheryl Crowe

Max Rockatansky

  • *
  • Offline Offline

  • Posts: 8286
  • Location: Route 9, Sector 26
  • Last Login: Today at 01:00:19 AM
    • Sure, Why Not? (Highway Blog Spot)
Re: Same number concurrencies or highways meeting
« Reply #52 on: July 17, 2017, 10:21:45 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:



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:



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

US 89

  • *
  • Offline Offline

  • Posts: 1812
  • 189 to Evanston!

  • Location: Salt Lake City, UT/Atlanta, GA
  • Last Login: Today at 01:03:36 AM
Re: Same number concurrencies or highways meeting
« Reply #53 on: July 19, 2017, 03:13:57 PM »

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.
« Last Edit: July 19, 2017, 03:16:12 PM by roadguy2 »
Logged
Interstate clinches: 14, 82, 215 (UT), 225, 345, 444, 575
US clinches: 491, 550

Flickr
Imgur

cjk374

  • *
  • Offline Offline

  • Posts: 2011
  • The road less travelled is well worn under my feet

  • Age: 45
  • Location: Simsboro, LA
  • Last Login: March 25, 2019, 09:47:49 PM
Re: Same number concurrencies or highways meeting
« Reply #54 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.
Logged
Runnin' roads and polishin' rails.

bwana39

  • *
  • Offline Offline

  • Posts: 8
  • Location: Near Texarkana TX
  • Last Login: August 09, 2017, 03:56:43 PM
Re: US 69 and Interstate 69 In Lufkin TX
« Reply #55 on: July 27, 2017, 12:14:17 AM »

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.
Logged

bwana39

  • *
  • Offline Offline

  • Posts: 8
  • Location: Near Texarkana TX
  • Last Login: August 09, 2017, 03:56:43 PM
Re: Same number concurrencies or highways meeting
« Reply #56 on: July 27, 2017, 12:37:36 AM »

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.
Logged

Bickendan

  • *
  • *
  • Offline Offline

  • Posts: 2430
  • Last Login: March 25, 2019, 02:19:33 PM
Re: Same number concurrencies or highways meeting
« Reply #57 on: July 27, 2017, 06:57:19 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
Logged

Max Rockatansky

  • *
  • Offline Offline

  • Posts: 8286
  • Location: Route 9, Sector 26
  • Last Login: Today at 01:00:19 AM
    • Sure, Why Not? (Highway Blog Spot)
Re: Same number concurrencies or highways meeting
« Reply #58 on: July 27, 2017, 08:02:53 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:

395USb by Max Rockatansky, on Flickr

395USa by Max Rockatansky, 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.

cwf1701

  • *
  • Offline Offline

  • Posts: 66
  • Location: michigan
  • Last Login: March 25, 2019, 04:38:49 PM
Re: Same number concurrencies or highways meeting
« Reply #59 on: July 28, 2017, 08:54:56 PM »

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.
Logged

cjk374

  • *
  • Offline Offline

  • Posts: 2011
  • The road less travelled is well worn under my feet

  • Age: 45
  • Location: Simsboro, LA
  • Last Login: March 25, 2019, 09:47:49 PM
Re: Same number concurrencies or highways meeting
« Reply #60 on: July 29, 2017, 08:17:23 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:

395USb by Max Rockatansky, on Flickr

395USa by Max Rockatansky, 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:
Logged
Runnin' roads and polishin' rails.

Max Rockatansky

  • *
  • Offline Offline

  • Posts: 8286
  • Location: Route 9, Sector 26
  • Last Login: Today at 01:00:19 AM
    • Sure, Why Not? (Highway Blog Spot)
Re: Same number concurrencies or highways meeting
« Reply #61 on: July 29, 2017, 06:28:08 PM »


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:

395USb by Max Rockatansky, on Flickr

395USa by Max Rockatansky, 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.

SSOWorld

  • 'Sconsin
  • *
  • *
  • Offline Offline

  • Posts: 3029
  • Interstate <Make up your mind!>

  • Age: 45
  • Location: MAH House!
  • Last Login: Today at 04:50:07 AM
Re: Same number concurrencies or highways meeting
« Reply #62 on: July 30, 2017, 01:14:26 PM »

Those may likely be NPS signs.  Separate maintenance authority.
Logged
Scott O.

Not all who wander are lost...
Ah, the open skies, wind at my back, warm sun on my... wait, where the hell am I?!
As a matter of fact, I do own the road.
Raise your what?

Facebook: http://www.facebook.com/ssoworld-roads/

Wisconsin - out-multiplexing your state since 1918.

Max Rockatansky

  • *
  • Offline Offline

  • Posts: 8286
  • Location: Route 9, Sector 26
  • Last Login: Today at 01:00:19 AM
    • Sure, Why Not? (Highway Blog Spot)
Re: Same number concurrencies or highways meeting
« Reply #63 on: July 30, 2017, 02:24:21 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.

corco

  • *
  • *
  • Offline Offline

  • Posts: 4909
  • Just Livin' the Dream

  • Age: 30
  • Location: Boise, Idaho
  • Last Login: March 25, 2019, 11:30:02 AM
    • Corcohighways.org
Re: Same number concurrencies or highways meeting
« Reply #64 on: July 30, 2017, 02:37:46 PM »


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



They took an "Arizona 95" sign and covered the "Arizona" label.

freebrickproductions

  • *
  • Offline Offline

  • Posts: 2167
  • The traffic signal enthusiast for north Alabama.

  • Age: -6982
  • Location: Huntsville, AL
  • Last Login: December 19, 2018, 02:35:12 AM
    • Mike's Railroad Crossing Website
Re: Same number concurrencies or highways meeting
« Reply #65 on: August 30, 2017, 01:01:28 PM »

Has I-759 becoming AL 759 been mentioned yet? I don't seem to recall if it has...
Logged
It's all fun & games until someone summons Cthulhu and brings about the end of the world.

I also collect traffic lights, road signs, fans, and railroad crossing equipment.

sparker

  • *
  • Offline Offline

  • Posts: 5251
  • Location: Bay Area, CA
  • Last Login: Today at 05:05:45 AM
Re: Same number concurrencies or highways meeting
« Reply #66 on: August 31, 2017, 03:17:45 AM »

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.   
Logged

jwolfer

  • *
  • Offline Offline

  • Posts: 2037
  • Age: 48
  • Location: Jacksonville, FL
  • Last Login: February 26, 2019, 10:02:06 PM
Re: Same number concurrencies or highways meeting
« Reply #67 on: September 02, 2017, 10:04:05 PM »


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:

395USb by Max Rockatansky, on Flickr

395USa by Max Rockatansky, 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

Logged

Max Rockatansky

  • *
  • Offline Offline

  • Posts: 8286
  • Location: Route 9, Sector 26
  • Last Login: Today at 01:00:19 AM
    • Sure, Why Not? (Highway Blog Spot)
Re: Same number concurrencies or highways meeting
« Reply #68 on: September 02, 2017, 10:44:40 PM »


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:

395USb by Max Rockatansky, on Flickr

395USa by Max Rockatansky, 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?

jwolfer

  • *
  • Offline Offline

  • Posts: 2037
  • Age: 48
  • Location: Jacksonville, FL
  • Last Login: February 26, 2019, 10:02:06 PM
Re: Same number concurrencies or highways meeting
« Reply #69 on: September 02, 2017, 10:53:15 PM »


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:

395USb by Max Rockatansky, on Flickr

395USa by Max Rockatansky, 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

Logged

formulanone

  • *
  • Offline Offline

  • Posts: 6403
  • Age: 45
  • Location: HSV
  • Last Login: March 25, 2019, 10:21:20 PM
Re: Same number concurrencies or highways meeting
« Reply #70 on: March 14, 2019, 09:15:20 AM »

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:

US 89

  • *
  • Offline Offline

  • Posts: 1812
  • 189 to Evanston!

  • Location: Salt Lake City, UT/Atlanta, GA
  • Last Login: Today at 01:03:36 AM
Re: Same number concurrencies or highways meeting
« Reply #71 on: March 14, 2019, 11:32:19 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.
Logged
Interstate clinches: 14, 82, 215 (UT), 225, 345, 444, 575
US clinches: 491, 550

Flickr
Imgur

formulanone

  • *
  • Offline Offline

  • Posts: 6403
  • Age: 45
  • Location: HSV
  • Last Login: March 25, 2019, 10:21:20 PM
Re: Same number concurrencies or highways meeting
« Reply #72 on: March 14, 2019, 10:07:57 PM »

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.

bugo

  • *
  • Offline Offline

  • Posts: 6011
  • Age: 45
  • Location: Oklahoma
  • Last Login: Today at 05:31:39 AM
    • No Frills Blog
Re: Same number concurrencies or highways meeting
« Reply #73 on: March 15, 2019, 06:03:41 AM »

Arkansas has I-49 and US 49.

US 70 crosses TX 70.
Logged
This signature has been censored by the AARoads Bureau of Morality.

bugo

  • *
  • Offline Offline

  • Posts: 6011
  • Age: 45
  • Location: Oklahoma
  • Last Login: Today at 05:31:39 AM
    • No Frills Blog
Re: Same number concurrencies or highways meeting
« Reply #74 on: March 15, 2019, 06:17:37 AM »

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.
Logged
This signature has been censored by the AARoads Bureau of Morality.

 


Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.