News:

Thanks to everyone for the feedback on what errors you encountered from the forum database changes made in Fall 2023. Let us know if you discover anymore.

Main Menu

US/State mixup shield error signs

Started by hotdogPi, August 17, 2016, 07:04:09 AM

Previous topic - Next topic


tckma

I'm not QUITE sure this counts, but this should be "TO US-29" in Columbia, MD.  Looks like they realized the error, and cheaply pasted "ROUTE" over "MARYLAND":

https://www.google.com/maps/@39.1750083,-76.8606302,3a,50y,76.77h,78.05t/data=!3m6!1e1!3m4!1sszQ7KQPfH9PMOREC9HO5ug!2e0!7i13312!8i6656

tckma

Another US-29 / MD-29 goof-up, at the end of a long-term construction zone to (I think) widen US-29 through Columbia, MD.  This sign is STILL there, but will definitely be removed once the construction is complete:

https://www.google.com/maps/@39.1802603,-76.8755809,3a,25y,241.27h,83.15t/data=!3m6!1e1!3m4!1s9fhYof3ZJR3rKM3i2-sxCA!2e0!7i13312!8i6656

CNGL-Leudimin

About California mixups, I remember seeing a pic where CA 152 was upgraded to I-152.

In this part of the world where we don't use fancy shields, just plain boxes with a full rainbow of background colors, the equivalent of shield mixups is getting the background color wrong. It happens too many times to count, including one example where a 2nd order regional road (green background) got upgraded to a national road (red)!
Supporter of the construction of several running gags, including I-366 with a speed limit of 85 mph (137 km/h) and the Hypotenuse.

Please note that I may mention "invalid" FM channels, i.e. ending in an even number or down to 87.5. These are valid in Europe.

theline

I've been driving past this sign for years, but noticed the error for the first time on the return trip on eclipse day. I'm not sure if the error belongs here or in another thread. Instead of a US shield for the Business 31 turn off US 31 near Peru, the BGS has a simple rectangle reading "BUSINESS 31." Since Indiana uses a rectangle for state routes, one might consider this a US/State mixup, though the shield is missing the usual "INDIANA" designator.

https://goo.gl/maps/MmAoR4yNrzE2

MNHighwayMan

Quote from: MNHighwayMan on February 22, 2017, 12:05:14 AM
How is it that these are so common? In the two states I've lived in, I've seen a mix-up of the two only once - that was a state route shield used in place of a US shield for US-52 in Luxemburg, Iowa. I guess I can see how they wouldn't be confused in Minnesota, but Iowa... still manages to pretty much always get it right? I don't get it.

So I must've said that before I found this picture:



That should be US-52, not MN-52. (Credit for the picture goes to, well, not me. I don't remember where I found it, though I'm pretty sure credit goes to a member here.)

D-Dey65

Quote from: MNHighwayMan on August 25, 2017, 06:45:27 AM
Quote from: MNHighwayMan on February 22, 2017, 12:05:14 AM
How is it that these are so common? In the two states I've lived in, I've seen a mix-up of the two only once - that was a state route shield used in place of a US shield for US-52 in Luxemburg, Iowa. I guess I can see how they wouldn't be confused in Minnesota, but Iowa... still manages to pretty much always get it right? I don't get it.

So I must've said that before I found this picture:



That should be US-52, not MN-52.
Funny, we had the opposite problem with FL 52 until a few years ago or so.

tckma


formulanone


US71

#84

Should be US 64 (actually this is OLD 64, so it shouldn't be here at all)


Should be US 70
Like Alice I Try To Believe Three Impossible Things Before Breakfast

JJBers

*for Connecticut
Clinched Stats,
Flickr,
(2di:I-24, I-76, I-80, I-84, I-95 [ME-GA], I-91)

Max Rockatansky

US 99 at Fresno-Yosemite International Airport where CA 99 ought to be:

99USa by Max Rockatansky, on Flickr

US 61 exiting Ely on MN 1, MN 61 ought to be posted:

61USa by Max Rockatansky, on Flickr


The US 99 appears to be a contractor error while the US 61 is a leftover from when the highway still existed north of Duluth.

6a

I got yelled at for not noticing this thread, so here you go.

ChezeHed81

Found September 2015 on Hwy Q (Newark Rd) approaching US-51 (Riverside Dr) near Beloit, Wisconsin:

JJBers

This isn't just some random sign, this is on a BGS on CT 8

CT 8 by JJBers, on Flickr
(It's US 202, not CT 202)
*for Connecticut
Clinched Stats,
Flickr,
(2di:I-24, I-76, I-80, I-84, I-95 [ME-GA], I-91)

US71

Quote from: JJBers on September 15, 2017, 10:34:41 PM
This isn't just some random sign, this is on a BGS on CT 8

CT 8 by JJBers, on Flickr
(It's US 202, not CT 202)

Photo no longer available
Like Alice I Try To Believe Three Impossible Things Before Breakfast

US71

Like Alice I Try To Believe Three Impossible Things Before Breakfast

JJBers

#92
Quote from: US71 on September 16, 2017, 12:35:40 PM
Quote from: JJBers on September 15, 2017, 10:34:41 PM
This isn't just some random sign, this is on a BGS on CT 8

CT 8 by JJBers, on Flickr
(It's US 202, not CT 202)

Photo no longer available
It shouldn't be, it's working fine for me.
*for Connecticut
Clinched Stats,
Flickr,
(2di:I-24, I-76, I-80, I-84, I-95 [ME-GA], I-91)

hotdogPi

Quote from: JJBers on September 16, 2017, 03:49:51 PM
Quote from: US71 on September 16, 2017, 12:35:40 PM
Quote from: JJBers on September 15, 2017, 10:34:41 PM
This isn't just some random sign, this is on a BGS on CT 8

CT 8 by JJBers, on Flickr
(It's US 202, not CT 202)

Photo no longer available
It shouldn't be, it's working fine for me.

Works for me too.
Clinched, minus I-93 (I'm missing a few miles and my file is incorrect)

Traveled, plus US 13, 44, and 50, and several state routes

I will be in Burlington VT for the eclipse.

US71

Quote from: 1 on September 16, 2017, 03:54:26 PM
Quote from: JJBers on September 16, 2017, 03:49:51 PM
Quote from: US71 on September 16, 2017, 12:35:40 PM
Quote from: JJBers on September 15, 2017, 10:34:41 PM
This isn't just some random sign, this is on a BGS on CT 8

CT 8 by JJBers, on Flickr
(It's US 202, not CT 202)

Photo no longer available
It shouldn't be, it's working fine for me.

Works for me too.

Seems to work now.
Like Alice I Try To Believe Three Impossible Things Before Breakfast

tckma

Quote from: JJBers on September 15, 2017, 10:34:41 PM
This isn't just some random sign, this is on a BGS on CT 8

Looks like one of the brand new ones they just installed, too.

ilpt4u

I played this is the Route Number Difference game to satisfy "333"

US 377 in Stroud, OK was signed with a State Route 377 shield. This one has been replaced, the 377 to a US 377 and the 66 and 99 to the current version of State shields in OK. 66 might as well be a US shield, as it is Old US 66


Sourced from http://www.usends.com/377.html

20160805

Another one:
WI 76 and US (not state) 10 west of Neenah, WI.  The erroneous sign still exists as of Sept 2017.
Left for 5 months Oct 2018-Mar 2019 due to arguing in the DST thread.
Tried coming back Mar 2019.
Left again Jul 2019 due to more arguing.

txstateends

Just saw this the other night, in Azle, TX.  Coming into town from the NW, the ramp to Loop 344 is marked with, not the usual TX 'boring square', but the green Biz I-344 shield! 
https://goo.gl/maps/tVNGDNNEQCy

I checked Google Street View, and it shows the same thing.  I'm not sure how far back the installation goes, but it does look new-ish.  I also looked around at the other parts of town on GSV, and no other sign goofs for Loop 344 could be found.
\/ \/ click for a bigger image \/ \/

tckma

Quote from: Max Rockatansky on September 11, 2017, 11:32:31 PM
US 99 at Fresno-Yosemite International Airport where CA 99 ought to be:
The US 99 appears to be a contractor error while the US 61 is a leftover from when the highway still existed north of Duluth.

To be fair -- weren't CA-99 and OR-99 intended to be US-99 someday?  Obviously not anymore, but ... ?



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.