Erroneous road signs

[okroads]

DSC05331 by Eric Stuve, on Flickr

Photo taken by me on July 11, 2015, in Boise City, OK. U.S. 385 North at U.S. 287.

can you point out the error(s) to us non-locals?

Certainly. 287 & 385 are both U.S. highways, and both of them are signed as Oklahoma state highways here.

[Brandon]

DSC05331 by Eric Stuve, on Flickr

Photo taken by me on July 11, 2015, in Boise City, OK. U.S. 385 North at U.S. 287.

can you point out the error(s) to us non-locals?

Uh, duh.  Read the caption and compare with the photo.  I'm a non-local and I got it.

[odditude]

DSC05331 by Eric Stuve, on Flickr

Photo taken by me on July 11, 2015, in Boise City, OK. U.S. 385 North at U.S. 287.

can you point out the error(s) to us non-locals?

Uh, duh.  Read the caption and compare with the photo.  I'm a non-local and I got it.

yep, complete failure to read on my part. sorry 'bout that, carry on.

[roadfro]

If the divided road becomes undivided just for an intersection and then immediately becomes divided again, I think these signs can be left out entirely.

That's not the case here. These signs are warning of a condition that lies beyond the intersection where the divided highway narrows down to a single carriageway.

[busman_49]

I-675 south at US 35 east...at least someone realized the goof (it said Dayton, but is supposed to say Xenia)
P1080484 by Ryan busman_49, on Flickr

[noelbotevera]

I-675 south at US 35 east...at least someone realized the goof (it said Dayton, but is supposed to say Xenia)
P1080484 by Ryan busman_49, on Flickr

Stop making us guess and flat out tell us what the goof is.

[hotdogPi]

The greenout isn't completely covering everything it's supposed to. Some white sticks out.

[busman_49]

Stop making us guess and flat out tell us what the goof is.

I did...or at least I thought I did...

From the original post:
"I-675 south at US 35 east...at least someone realized the goof (it said Dayton, but is supposed to say Xenia)"

Anyway...
Going from I-675 south, US 35 east was signed for Dayton until someone noticed the mistake and the DOT applied the greenout.  35 WEST will take one to Dayton (apologies if THAT wasn't made clear).  So I guess you could call it a half-assed-fixed mistake.  I surmise that eventually the Xenia wording will be applied.

[ekt8750]

Two from Lehigh Valley Airport...one looks a bit older than the other, but mysterious mix-ups just a quarter-mile apart are part of the fun.

Worst part is we could have been spared that monstrosity if it was signed properly. It's supposed to be PA 987 not US 987. Kinda hard to screw up a keystone.

[hbelkins]

DSC05331 by Eric Stuve, on Flickr

Photo taken by me on July 11, 2015, in Boise City, OK. U.S. 385 North at U.S. 287.

To me, that seems like an awful lot of post/support braces just to mount three route marker assemblies.

[signalman]

Two from Lehigh Valley Airport...one looks a bit older than the other, but mysterious mix-ups just a quarter-mile apart are part of the fun.

Worst part is we could have been spared that monstrosity if it was signed properly. It's supposed to be PA 987 not US 987. Kinda hard to screw up a keystone.

True.  However, we could have gained an acorn US 22 shield, instead of an erroneous PA 22 shield. 

[ekt8750]

Two from Lehigh Valley Airport...one looks a bit older than the other, but mysterious mix-ups just a quarter-mile apart are part of the fun.

Worst part is we could have been spared that monstrosity if it was signed properly. It's supposed to be PA 987 not US 987. Kinda hard to screw up a keystone.

True.  However, we could have gained an acorn US 22 shield, instead of an erroneous PA 22 shield.

Touche. Moral of this story is airports tend to screw up stuff like this on their signage. Although I've seen PennDOT screw up state and US highways. Case and point:

https://www.google.com/maps/@39.888299,-75.300513,3a,42.9y,158.9h,86.03t/data=!3m7!1e1!3m5!1saZFl5apGoUUtU7qo5xKWHg!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DaZFl5apGoUUtU7qo5xKWHg%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D100%26h%3D80%26yaw%3D86.447937%26pitch%3D0!7i3328!8i1664

[PHLBOS]

Although I've seen PennDOT screw up state and US highways. Case and point:

https://www.google.com/maps/@39.888299,-75.300513,3a,42.9y,158.9h,86.03t/data=!3m7!1e1!3m5!1saZFl5apGoUUtU7qo5xKWHg!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DaZFl5apGoUUtU7qo5xKWHg%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D100%26h%3D80%26yaw%3D86.447937%26pitch%3D0!7i3328!8i1664

What's sad about that case was that those erroneous PA 13 trailblazer signs (and its companions, not shown) replaced correct US 13 trailblazer signs (all sporting PennDOT's bastardization of Series D font for the numerals) that were only a year or two old.

[doorknob60]

I don't have a picture as this sign has been installed sometime between January and now, but here is a picture of the old sign.


ODOT recently saw the need to replace this assembly. The mileage sign is now mixed case (fine by me). But they replaced the reassurance marker with an OR-101 shield!

[jakeroot]

The mileage sign is now mixed case (fine by me).

I believe that's a requirement now, so I hope you're fine with it

But they replaced the reassurance marker with an OR-101 shield!

It does seem like Oregon makes this mistake more than Washington. I'd love to see an OR-101 shield.

[SignGeek101]

The mileage sign is now mixed case (fine by me).

I believe that's a requirement now, so I hope you're fine with it

I actually prefer mixed case signs of this nature. They look "neater" in my mind anyway.

[WNYroadgeek]

Apparently New York decided to downgrade US 62 to NY 62: http://binged.it/1LvoXwS

It's a fairly new installation, too, thus it's not present in StreetView (hence the Bing StreetSide link).

[mariethefoxy]

A while back I remember seeing a news article because they new signs on the Robert Moses Causeway had misspelled Jones Beach as "Jonse Beach" Im pretty sure they patched it over already.

[1995hoo]

Someone at VDOT doesn't seem to know the difference between a US Highway shield and a Virginia primary route shield. These are both just east of Gainesville on US-29, seen yesterday and today as indicated by the dashcam time-stamp. (The state shields in the first photo are particularly ugly, too.)

[freebrickproductions]

Found this on Facebook:

It's located in Tuscumbia, AL

[Eth]

Someone at VDOT doesn't seem to know the difference between a US Highway shield and a Virginia primary route shield. These are both just east of Gainesville on US-29, seen yesterday and today as indicated by the dashcam time-stamp. (The state shields in the first photo are particularly ugly, too.)

Not to mention the right lane clearly goes to I-66 west, not east.

[1995hoo]

I noted that too. I think it is intended to refer to the two thru lanes, but it's poorly worded.

[FLRoads]

Found this on Facebook:

It's located in Tuscumbia, AL

Wow, that's still there? I photographed that back in December 2009:

[FreewayDan]

It appears that Interstate 95 has been extended west to Yuma, AZ:
https://www.google.com/maps/@32.698488,-114.603097,3a,65.8y,192.16h,90.29t/data=!3m6!1e1!3m4!1sTIjvyNADYRFxwg5Uk3UumA!2e0!7i13312!8i6656!6m1!1e1

[PurdueBill]

It appears that Interstate 95 has been extended west to Yuma, AZ:
https://www.google.com/maps/@32.698488,-114.603097,3a,65.8y,192.16h,90.29t/data=!3m6!1e1!3m4!1sTIjvyNADYRFxwg5Uk3UumA!2e0!7i13312!8i6656!6m1!1e1

Interesting in comparing old and new street view that it appears that older signage had it right, and it was replaced with the error.