WV: WV 46, WV 90, WV 115, and WV 230 Point Concerns

[Markkos1992]

WV 46 (Keyser):  HamSt>-HamSt_W

WV 90:  Should WilRd be OldWilRd?

WV 115: 
1.  Is WV9_Har (I guess for Harpers Ferry) accurate?  (By the way, WV 115 is still not-posted from WV 9 here as of today.)
2.  LeePk should be OldLeePike.
3.  I am unsure if CR9/19 is correct.  Maybe just go ShoRd.

WV 230:  HalRd_W>-HalRd

[Markkos1992]

EDIT (2-2-2022):  Added changes to WV 46 (Keyser) and WV 90.

[rickmastfan67]

WV-46: Fixed.
WV-90: Fixed.
WV-230: Fixed.

WV-115:
1. I think that's why I had it that way.  Guess I could change it to 'WV9_Key' instead for Key's Gap (would have considered just plain 'WV9', but that's still in-use under 'CR9/1').  And figures about the signage.  I have no idea what's wrong with WVDOH.  They have it even on the official state map showing this as part of WV-115...... (see 4 below)
2. Fixed.
3. You're right, it's incorrect.  It's really CR9/26 instead.  Corrected.

4. While looking at StreetView for 1, I noticed that they have FINALLY updated it along 'WV-115' in July '21.  So, I took a quick spot look in a few places where I would think that there would be signage.  At Mission Road, I discovered this pair of 'TO WV-9' shields instead of what should have been WV-115 ones.... https://goo.gl/maps/5SvfoVGRbHwNW2nK9  And nothing else beyond this one SB WV-115 shield just after the US-340 interchange.  So, what to do here..........  Do we just keep it as-is (as shown on the official WV map), or shorten it to just beyond the US-340 interchange?  If we want to go with the shorten option, where then? This is so annoying for sure.......

All of these fixes have been submitted, except for of course, 'WV-115 #4', as that requires some discussion.  So, leaving this thread un-solved at the moment.
https://github.com/TravelMapping/HighwayData/pull/5621

[Markkos1992]

What you saw for #4 is what I saw for WV 115 when I clinched it in December.  I guess that those signs would not be as they are if it was not WV 115, but who knows what WVDOH's official position on it is.

EDIT:  As I was clinching more MD routes Saturday and today, I realized that truncating WV 115 could create a rabbit hole leading to the truncation of a lot of other routes.  Since WV 115 is clearly signed east of US 340 by one sign, and is shown on maps to go to WV 9, I support leaving WV 115 as it is now.

[rickmastfan67]

EDIT:  As I was clinching more MD routes Saturday and today, I realized that truncating WV 115 could create a rabbit hole leading to the truncation of a lot of other routes.  Since MD 115 is clearly signed east of US 340 by one sign, and is shown on maps to go to WV 9, I support leaving WV 115 as it is now.

Yeah, WV does have a few other hanging ends, as WV-817 also has this issue too at it 'northern' end.  Not signed @ WV-2, but signed from US-35 going towards there, with no logical other end point.

So, yeah, let's just leave WV-115 as-is for now at it's 'southern end', and mark this as solved.  We can always come back to it if either signage or map changes come to light.