Erroneous road signs

[Alex4897]

http://i.imgur.com/3Bj7cUnl.jpg

US 192 WB at the exit for World Dr NB.

US 192 has three total lanes and none of them split here.  The right most lane could be considered an option lane, it spits out both of the ramp's two lanes at once.

Wow... was this reconfigured from that configuration??? But yeah, that's bad.

Per HistoricAerials, I think that's the case.


You can't exactly see the stripes, but you can see two distinct streams of vehicles on US 192 past the split.  This image is from 1999 and the next one is from 2007, so no matter where between those years the widening of US 192 occurred the fact that this sign is still here is all the more surprising.

[Rothman]

Found in a parking lot off of Essex Street in Lodi, NJ near where Essex St and NJ 17 intersect:

[vtk]

Found in a parking lot off of Essex Street in Lodi, NJ near where Essex St and NJ 17 intersect:

Are pedestrians expected to be able to cross here? In that case, a proper crossbuck might be appropriate for them, while vehicular traffic needs some end-of-road markers. This may be a case of "right idea, wrong sign"...

[jeffandnicole]

Found in a parking lot off of Essex Street in Lodi, NJ near where Essex St and NJ 17 intersect:

Are pedestrians expected to be able to cross here? In that case, a proper crossbuck might be appropriate for them, while vehicular traffic needs some end-of-road markers. This may be a case of "right idea, wrong sign"...

I see a fence.  Definitely no pedestrian crossing.  If it was for pedestrians, there would need to be a proper sidewalk thru the tracks. It would need to be handicap accessible.  Most likely there would need to be a gate, flashing lights and bells also...even for a pedestrian crossing.

Similar to a situation I'm familiar with.  Maybe the crossing existed...but it would've been 40 or 50 years ago.  Yet, the sign seems new!

Also...No O tlet.  You've been warned.

https://goo.gl/maps/CYYAS

[JCinSummerfield]

IL 31 gets a promotion to a US route in Ringwood, IL

Well they only missed by one state!

[Jim]

Forgive me for not searching through so many pages of this thread to make sure this isn't a repeat.  Taken this month in South Strafford, Vermont:

[jakeroot]

Forgive me for not searching through so many pages of this thread to make sure this isn't a repeat.  Taken this month in South Strafford, Vermont:

I wouldn't worry. Repeats happen a lot. But I must ask, what's the error here? I'm probably not getting it due to my unfamiliarity.

[SignGeek101]

Forgive me for not searching through so many pages of this thread to make sure this isn't a repeat.  Taken this month in South Strafford, Vermont:

I wouldn't worry. Repeats happen a lot. But I must ask, what's the error here? I'm probably not getting it due to my unfamiliarity.

I don't think US 132 exists. Either that or the directional tab is mis-placed (even though I personally prefer it below the shield).

[jakeroot]

Forgive me for not searching through so many pages of this thread to make sure this isn't a repeat.  Taken this month in South Strafford, Vermont:

I wouldn't worry. Repeats happen a lot. But I must ask, what's the error here? I'm probably not getting it due to my unfamiliarity.

I don't think US 132 exists. Either that or the directional tab is mis-placed (even though I personally prefer it below the shield).

Looks like your right. That should have been my first guess but it skipped my mind.

EDIT: I'm not a genius in any respect, but I can't believe it didn't occur to me that a number like 32 being in Vermont makes no sense whatsoever. 

[Jim]

Forgive me for not searching through so many pages of this thread to make sure this isn't a repeat.  Taken this month in South Strafford, Vermont:

I wouldn't worry. Repeats happen a lot. But I must ask, what's the error here? I'm probably not getting it due to my unfamiliarity.

I don't think US 132 exists. Either that or the directional tab is mis-placed (even though I personally prefer it below the shield).

Should have included more in my post.  This is on Vermont 132 (or whatever the proper name is for the circle-shield routes in Vermont).  There is no US 132 anywhere, and if there was one, it likely wouldn't be in Vermont.

[jakeroot]

Forgive me for not searching through so many pages of this thread to make sure this isn't a repeat.  Taken this month in South Strafford, Vermont:

I wouldn't worry. Repeats happen a lot. But I must ask, what's the error here? I'm probably not getting it due to my unfamiliarity.

I don't think US 132 exists. Either that or the directional tab is mis-placed (even though I personally prefer it below the shield).

Should have included more in my post.  This is on Vermont 132 (or whatever the proper name is for the circle-shield routes in Vermont).  There is no US 132 anywhere, and if there was one, it likely wouldn't be in Vermont.

No worries. I just updated my second post, but yeah, on second thought, having an even number that far north wouldn't make any sense. Lol.

[Jim]

No worries. I just updated my second post, but yeah, on second thought, having an even number that far north wouldn't make any sense. Lol.

One could say the same about US 44 and US 46, yet there they are.

[Big John]

No worries. I just updated my second post, but yeah, on second thought, having an even number that far north wouldn't make any sense. Lol.

Or nowhere near its parent or orphaned, looking at you 163, 400, 412, 425.

[hotdogPi]

No worries. I just updated my second post, but yeah, on second thought, having an even number that far north wouldn't make any sense. Lol.

Or nowhere near its parent or orphaned, looking at you 163, 400, 412, 425.

Also 202 (part of it is near its parent, but part of it is not).

[Stratuscaster]

Or nowhere near its parent or orphaned, looking at you 163, 400, 412, 425.

Aren't 400/412/425 exceptions - ie; they don't have parents?

[FreewayDan]

Now since when did U.S. Highway 43 was extended northwest from Columbia, TN, up to Portland, OR:
https://www.google.com/maps/@45.4994785,-122.6728231,3a,47.6y,10.26h,91.67t/data=!3m7!1e1!3m5!1sEzTnlLac_AmvsGhIIE9tYg!2e0!5s20140501T000000!7i13312!8i6656!6m1!1e1

[SignGeek101]

Now since when did U.S. Highway 43 was extended northwest from Columbia, TN, up to Portland, OR:
https://www.google.com/maps/@45.4994785,-122.6728231,3a,47.6y,10.26h,91.67t/data=!3m7!1e1!3m5!1sEzTnlLac_AmvsGhIIE9tYg!2e0!5s20140501T000000!7i13312!8i6656!6m1!1e1

That sign has been there for quite awhile too. Not to mention the undersized numbers, wrong width, and wrong shield.

[noelbotevera]

Now since when did U.S. Highway 43 was extended northwest from Columbia, TN, up to Portland, OR:
https://www.google.com/maps/@45.4994785,-122.6728231,3a,47.6y,10.26h,91.67t/data=!3m7!1e1!3m5!1sEzTnlLac_AmvsGhIIE9tYg!2e0!5s20140501T000000!7i13312!8i6656!6m1!1e1

That sign has been there for quite awhile too. Not to mention the undersized numbers, wrong width, and wrong shield.

Critical failure.

[CNGL-Leudimin]

Also 202 (part of it is near its parent, but part of it is not).

Add 220 to that. And depending of your viewpoint, 101 .

Now since when did U.S. Highway 43 was extended northwest from Columbia, TN, up to Portland, OR:
https://www.google.com/maps/@45.4994785,-122.6728231,3a,47.6y,10.26h,91.67t/data=!3m7!1e1!3m5!1sEzTnlLac_AmvsGhIIE9tYg!2e0!5s20140501T000000!7i13312!8i6656!6m1!1e1

That sign has been there for quite awhile too. Not to mention the undersized numbers, wrong width, and wrong shield.

Since no later than July 2011, according to that time machine Street View has.

PS: I was looking at the BGS which has the correct OR 43 shield, and I was thinking there were no errors there... until I saw that standalone shield.

[Rothman]

NY 32 as US 32.  Maybe US 132 in VT is a spur off of this US 32!

[webfil]

Vermont 207 and 235 shield assembly mistakenly manufactured as U.S. highways:

That one struck me as odd too. VT 207 and 235 north of highways 78 and 120 are exclusively signed with pre-95 spec shields (white circle/black square) or US-route shields. (That makes VT-235, let's say, more or less wholly mistakenly signed as US-route).

Franklin county might have lost it when they replaced old markers.

"Hey, we need to replace these old shields. Their numbers have became unreadable.
-What shield?
-Well, you know, the black and white route markers. In Highgate.
-Ok. Like this one? [Shows a US-route marker]
-I don't know... Well... I guess..."

[iBallasticwolf2]

OH 127 instead of US 127 in Hamilton, another one of these are a little further north on the road.

[roadman65]

https://www.google.com/maps/place/Orlando,+FL/@28.536275,-81.378613,3a,66.8y,178.42h,99.22t/data=!3m4!1e1!3m2!1s2KCCIH_86BB2Dmk07DKyBQ!2e0!4m2!3m1!1s0x88e773d8fecdbc77:0xac3b2063ca5bf9e

Look at the FL 408 shields placecards.  The TO and the WEST are switched around and reads wrong.

[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).

Found a few more:

https://www.google.com/maps/@43.0867494,-78.8893658,3a,15y,167.51h,86.92t/data=!3m6!1e1!3m4!1sLf_5zwztAnl27d85w2ymCQ!2e0!7i13312!8i6656?hl=en
https://www.google.com/maps/@43.0928334,-79.0574534,3a,15y,326.87h,89.87t/data=!3m6!1e1!3m4!1sM6GSZ17I4PUBrDcu1127ng!2e0!7i13312!8i6656?hl=en (and with a perfectly accurate US 62 shield right next to it  )

[jbnv]

https://www.google.com/maps/@43.0928334,-79.0574534,3a,15y,326.87h,89.87t/data=!3m6!1e1!3m4!1sM6GSZ17I4PUBrDcu1127ng!2e0!7i13312!8i6656?hl=en (and with a perfectly accurate US 62 shield right next to it  )

And in a sign salad to boot,