VA: VA 403 and VA 404

[oscar]

I drove the short northbound VA 403, on my way home from the Outer Banks. It might be unsigned. The signs in both directions on VA 165, and eastbound on US 58, don't mention VA 403, but instead use To I-264/To I-64. Could've missed signage on southbound VA 403, or westbound US 58, or on I-264 (looked in those places on GMSV, didn't see any, imagery is usually several years old).

VA 168 has a waypoint for VA 404, but there's no VA 404 in the HB, nor did I see any signage for it (but I didn't leave VA 168 to look for it). Suggest renaming or deleting the unused VA404 point on VA 168.

[froggie]

Last time I was in Norfolk (last year), 403 was still signed on WB 58.  Though, in typical Virginia Beach fashion, 403 is signed as continuing north from 58.  Unless it's confirmed those westbound signs have been removed, I'd suggest leaving 403.

[Markkos1992]

I clinched VA 404 Thursday Night, and I did not see any shields on it either (as I had expected).  That point on VA 168 should definitely be renamed to PriAnneRd.

[mapmikey]

2019 GMSV still has 403 posted on 58 WB, so no change here yet.

Renamed the VA 404 point on VA 168.

[dave1693]

I clinched VA 404 Thursday Night, and I did not see any shields on it either (as I had expected).  That point on VA 168 should definitely be renamed to PriAnneRd.

A small subset of my friends have referred to VA 404 as "Highway Not Found" for a while now. 

[yakra]

Not to be confused with US Federal Route File Not Found

[Markkos1992]

Not to be confused with US Federal Route File Not Found

Well I did find an error US 404 shield in DE earlier this year.

[Jim]

Maybe we should modify the shield generator to use a special "not found" shield for all routes numbered 404.

[Markkos1992]

GSV shows PriAnneSt as clearly still PriAnneRd. 

[mapmikey]

corrected and in the queue