WV: Corridor Point Concerns

[Markkos1992]

US 19:
1.  Consider replacing the shaping point south of WV123 with a visible point. (also affects US 460)
2.  Should HonAve_W be marked as closed?
3.  HolRd>-HolHilRd (and slight relocation)
4.  WolfCreRd>-BucMouRd (and slight relocation)
5.  RosBraRd, OldSpaRd, MillDamRd, BobByrdRd, and DunRd could use a slight relocation.
6.  Consider adjusting the lines south of ClaGapRd.
7.  ClaGapRd>-FlatTopRd (and slight relocation)
8.  OddGheRd>-OddRd
9.  MapForRd>-MapForkRd
10.  Consider adding a point between CR19/55 and CR19/19 to keep the line west of WV 16/WV 61.  (The issue barely exists south of CR19/55.)
11.  CR19/19>-CR19/36
12.  CR82>-CR85/9
13.  Consider replacing the shaping point along the WV 41 concurrency south of Summersville with a visible point.  (also affects WV 41) 
14.  Consider replacing the shaping point south of PolRd with a visible point.
15.  PolRd>-PolRunRd
16.  Consider replacing the shaping point south of I-79(57) with a visible point.
17.  GreHilRd>-PleHillRd  (also affects WV 4)
18.  FalRunRd could use a slight point relocation.  (also affects WV 4)
19.  WareRd>-WarRd or CR19/2  (also affects WV 4)
20.  MckRunRd>-McWRd
21.  LauParkRd could use a slight recentering. 
22.  It looks like HoodAve may be incorrect. 
23.  Consider replacing the shaping points south of WV218 with visible point(s).
24.  Consider replacing the shaping point south of CR17 with a visible point.
25.  MainSt_Riv>-JacSt   
26.  Consider replacing the shaping point between WV100_N and WV/PA with a visible point.

US 30:
1.  Consider replacing the shaping point west of AbeRd with a visible point at CR30/2.
2.  Is AbeRd a worthy visible point?  I feel like it is only here due to the EB ramp to WV 8 (and WV 8 does not have a point at the end of this ramp).

US 33: 
1.  Are MouGoatTrl, RavLn, etc. worthwhile visible points?
2.  KiyGapRd should be KisGapRd.
3.  Consider replacing the shaping point east of US220_S with a visible point.
4.  Consider replacing the shaping points west of US220_S with visible points.
5.  ReeCrk should be ReeCrkRd.
6.  Consider replacing the shaping point west of WV28_S with a visible point.  (also affects WV 28)
7.  Consider replacing the shaping point west of WV28/55 with a visible point.  (also affects WV 55)
8.  I think there are enough visible point opportunities east of WV32 to make Har unnecessary.  (also affects WV 55)
9.  Should OldUS219_S be CR219/86?
10.  The shaping point north of US219/250 should be made visible.  (also affects US 219, US 250, and WV 92)

US 48:  WV32 should be WV32_S.

US 52:  I-77>-I-77(1)

US 60: 
1.  RCHilRd should be UnusRd.
2.  The shaping point east of RCHilRd should be replaced with a visible point at CR60/12.
3.  CR60/11 should be CR40.
4.  BlueSulPk should be BlueSulPike.

US 119:  WilSt>-WilSt_W.

US 219:
1.  SprRunRd should be BackValRd (Back Valley Rd).
2.  The shaping point north of SprRunRd should be replaced with a visible point at CR219/40.
3.  The shaping point south of WV 122 should be replaced with a visible point at CR219/14.
4.  It looks like the third shaping point south of MainSt_Uni should be replaced with a visible point at what OSM calls CR219/7.
5.  Consider changing MainSt_Uni to CR13.
6.  The shaping point north of WV3_E should be replaced with a visible point at CR10.  (also affects WV 3)
7.  The second shaping point south of WV63_E should be replaced with a visible point at CR219/9.
8.  Consider replacing the shaping point south of RivRd with a visible point at CR41.  (also affects WV 63)
9.  I would change MainSt_Ron to CR45 instead of MainSt_E.
10.  BroCutRd should be CR7.
11.  The shaping point south of GeoHillRd should be replaced with a visible point at CR219/11.
12.  The shaping point south of WV39/55 should be replaced with a visible point at CR20.
13.  Consider replacing the shaping point south of DryCrkRd with a visible point.  (also affects WV 39 and WV 55)
14.  Consider replacing the second shaping point south of WV150_E with a visible point.  (also affects WV 55)
15.  It looks like CR219/14 should be CR51.  (also affects WV 55)
16.  ElkWatRd should be ElkForkRd.  (also affects WV 55)
17.  The shaping point south of US250_S should maybe be replaced with a visible point at CR43.
18.  MilSt should be Adolph Rd (AdoRd). (also affects US 250, WV 55, and WV 92)
19.  Consider replacing the shaping point south of CR219/9 with a visible point at CR219/10.  (also affects US 250, WV 55, and WV 92)
20.  The shaping point south of GeoRMRd should be replaced with a visible point at Scotts Lake Rd (ScoLakeRd).  (also affects US 250, WV 55, and WV 92)
21.  The shaping points south of US33_E should be replaced with visible points at CR219/11 and CR 24. (also affects US 250, WV 55, and WV 92)

WV 2:  KParkMRd violates the manual as-is.

WV 3: 
1.  Consider replacing the shaping point east of WV 305 with a visible point. 
2.  SweRd>-RanRd
3.  RaiAve_W>-CR3/17
4.  CreRd>-CR3/2
5.  CenChuRd>-CR11/3

WV 7: 
1.  BloRid should be BroRidRd.
2.  The WVDOH Wetzel County Map seems to indicate that CR7/8 should be CR7/20.
3.  BroRidRd should be relabeled.
4.  The US250 labels should be N and S instead of W and E.
5.  I think that CR5 is correct, but I do not see a shield here.  It is the same with CR7/6.
6.  DelRd48>-CR14.
7.  WadRunRd_S seems incorrect.  (also affects US 19, which has two WadRunRd labels)
8.  Consider replacing the shaping point west of JakRunRd with a visible point.
9.  RogAve>-RogAve_S?
10.  Consider replacing the shaping point east of WV 72 with a visible point at CR7/13.

WV 8: 
1.  CR8/1 should be CR18.
2.  Is BreHeiRd the best point location here?  (should be BreHeiDr if kept)

WV 12:  CR3/17>-CR31/7

WV 16:  Consider replacing or removing the shaping point south of WV61_N.  (also affects WV 61)

WV 26: 
1.  Preston County GIS indicates that BeaSt should be BankSt.
2.  TerAltaPk>-StJoeRd or CR7/12

WV 28:
1.  PubRd14>-MidMouRd (Middle Mountain Rd) (according to the WV Property Data Viewer)
2.  Consider replacing the shaping point east of PubRd14 with a visible point at PubRd52.
3.  PatCreRd should be CR28/3 or PatCrePike.
4.  Consider replacing the shaping point between WV 956 and WV 28 ALT with a visible point.

WV 29:  I recommend changing CR45/4 to CR45/7.

WV 32:  This map shows WVDepRd as MainParkRd.

WV 41: 
1.  CR41/11>-CR41/38 (because of confidence that the latter is correct)
2.  BurrRd>-TwigRd (if kept)
3.  OldRte19>-CR19/86
4.  ForkRd>-BenWay  (if kept, maybe could be replaced by nearby CR 10)

WV 42:  KnoRd>-CR3 (because I am unsure if KnoRd is right or not)

WV 46 (Keyser): 
1.  It looks like CR46/9 should be CR9/3.
2.  Consider replacing the shaping point northeast of ChaLn with a visible point.
3.  I am unsure if CR46/7 should instead be CR10.

WV 54: 
1.  OldWV54>-CR54/3
2.  SawDr>-4thAve  (also affects WV 97)
3.  CR17/6>-CR54/1 (also affects WV 97)

WV 55: 
1.  Consider replacing shaping points with visible points between WV 41 and WV 20.
2.  CR28/1_S>-CR28/1

WV 63: 
1.  CR48 should be CR46.
2.  Is GraDr a worthwhile visible point?
3.  It looks like WalSt should be WalSt_S.

WV 66:  I think that CR11/1 should be CR9/3.  (or just go SnoDr_W and SnoDr_E)

WV 72: 
1.  CR45>-CR45/3 (based on GSV)
2.  Consider replacing the shaping point north of CR45 with a visible point at Jenningston Rd.
3.  I am unsure if CR1 is at the right location.
4.  CatSt>-CatSt_E.

WV 86: 
1.  WooLn is probably best replaced by nearby JefAve.
2.  GreHilRd>-GreHilDr

WV 88: 
1.  CR88/25 needs to be slightly relocated.
2.  DemCemRd>-DemRd
3.  ForkShoRd>-ForkRd, NorForkRd, NForkRd, etc.
4.  LibHarRd>-HarRd

WV 92: 
1.  I presume that Tra is one of those "we need a point somewhere" points. 
2.  CR28/9_S should just be CR28/9.
3.  I am unsure if the shaping points from Durbin east to the south end of the US 250 concurrency are necessary (though the closest one to the south end could be replaced by CR250/4).  I am at a "whatever" mood in regard to the forest roads northwest of Dublin because I am unable to clarify PubRd92.  (also affects US 250)
4.  FriSt should be FinSt.
5. Shale Rd may be a worthwhile visible point south of Belington.  (also affects US 250)
6.  I think CR56 should be CR5/6.

WV 270:  HighSt_N>-HighSt

WV 307:  Consider replacing the shaping point south of GraRd_N with a visible point.

WV 310:  SpeRd>-SpeAve

WV 311:  Is JefLn even needed?

WV 705:  WilDr>-DonNehDr

[rickmastfan67]

US 30:
1.  Consider replacing the shaping point west of AbeRd with a visible point at CR30/2.
2.  Is AbeRd a worthy visible point?  I feel like it is only here due to the EB ramp to WV 8 (and WV 8 does not have a point at the end of this ramp).

1) Meh, I honestly like where I have the shaping point, and honestly can't see any reason to change it.
2) Yeah, that's kinda why I added it, since a road was there I could justify it more than normal.  Could add a point to WV-8 at the end of the ramp since it's 0.6 miles from US-30.  But does bring up an interesting issue for labeling, due to it being one-way.  Either I could make it 'US30_A' or 'FromUS30'.  Guessing 'US30_A' is the safest, but LMK your opinion on the other possible label name and I might adjust it later.

US 48:  WV32 should be WV32_S.

US 52:  I-77>-I-77(1)

US 119:  WilSt>-WilSt_W.

All fixed.  Though, to be honest with US-52, had that label as an alt already due to a previous 'swap'.

WV 8: 
1.  CR8/1 should be CR18.
2.  Is BreHeiRd the best point location here?  (should be BreHeiDr if kept)

1) Fixed.
2) Thought it was a logical location due to the curve in the road.  Guess I could adjust this one to "Locust Hill Rd (CR5)".

=====

Submitted these changes listed above.
https://github.com/TravelMapping/HighwayData/pull/6680

[rickmastfan67]

US 33: 
1.  Are MouGoatTrl, RavLn, etc. worthwhile visible points?
2.  KiyGapRd should be KisGapRd.
3.  Consider replacing the shaping point east of US220_S with a visible point.
4.  Consider replacing the shaping points west of US220_S with visible points.
5.  ReeCrk should be ReeCrkRd.
6.  Consider replacing the shaping point west of WV28_S with a visible point.  (also affects WV 28)
7.  Consider replacing the shaping point west of WV28/55 with a visible point.  (also affects WV 55)
8.  I think there are enough visible point opportunities east of WV32 to make Har unnecessary.  (also affects WV 55)
9.  Should OldUS219_S be CR219/86?
10.  The shaping point north of US219/250 should be made visible.  (also affects US 219, US 250, and WV 92)

1. I'd say yes, as it allows me to have that area of the road properly mapped due to all the curves and such.  Plus, with 'MouGoatTrl', that's an obvious previous alignment of US-33 there when you look at the satellite imagery.
2. Fixed.
3. Replaced with OakEstDr.
4. Replaced with BufHilRd & JohHolRd, but kept the 2nd hidden one, due to still adding a decent amount of mileage to justify it IMO.
5. Fixed.
6. Are you sure you didn't mean 'East' of that intersection?  There's 2 shaping points to the east on top of roads that I've just 'unhidden'.  But can't see any reasonable point to the west that doesn't lose over .2 a mile.  So, no changes to WV-28 here.
7. Added 'LTRidRd' & 'WhiRunRd'.
8. Only labeled it that due to no StreetView back in the day.  Replaced with 'SteHarRd'.
9. Label fixed to match with US-250 there (and changed US-219 as well to match).
10. Done in all affected files as 'LocSt'.

https://github.com/TravelMapping/HighwayData/pull/6692

[rickmastfan67]

US 19:
1.  Consider replacing the shaping point south of WV123 with a visible point. (also affects US 460)
2.  Should HonAve_W be marked as closed?
3.  HolRd>-HolHilRd (and slight relocation)
4.  WolfCreRd>-BucMouRd (and slight relocation)
5.  RosBraRd, OldSpaRd, MillDamRd, BobByrdRd, and DunRd could use a slight relocation.
6.  Consider adjusting the lines south of ClaGapRd.
7.  ClaGapRd>-FlatTopRd (and slight relocation)
8.  OddGheRd>-OddRd
9.  MapForRd>-MapForkRd
10.  Consider adding a point between CR19/55 and CR19/19 to keep the line west of WV 16/WV 61.  (The issue barely exists south of CR19/55.)
11.  CR19/19>-CR19/36
12.  CR82>-CR85/9
13.  Consider replacing the shaping point along the WV 41 concurrency south of Summersville with a visible point.  (also affects WV 41) 
14.  Consider replacing the shaping point south of PolRd with a visible point.
15.  PolRd>-PolRunRd
16.  Consider replacing the shaping point south of I-79(57) with a visible point.
17.  GreHilRd>-PleHillRd  (also affects WV 4)
18.  FalRunRd could use a slight point relocation.  (also affects WV 4)
19.  WareRd>-WarRd or CR19/2  (also affects WV 4)
20.  MckRunRd>-McWRd
21.  LauParkRd could use a slight recentering. 
22.  It looks like HoodAve may be incorrect. 
23.  Consider replacing the shaping points south of WV218 with visible point(s).
24.  Consider replacing the shaping point south of CR17 with a visible point.
25.  MainSt_Riv>-JacSt   
26.  Consider replacing the shaping point between WV100_N and WV/PA with a visible point.

1. Added point @ CR19/33.
2. Good question, I have honestly no idea.  All I can think is that I added when Sat imagery & Google/OSM back in the day weren't fully up-to-date.  Looking at StreetView, kinda looks like it never connected there to be honest.  So, I'll just convert it to a hidden point.
3. Fixed.
4. Fixed.
5. All done.
6. Two shaping points added to keep US-19 west of I-77.
7. Fixed.
8. Went with CR48 instead.  Also added a point @ CR19/26 just to the south for the ski resort there.
9. Fixed.
10. Added points at the 'new' Welcome Center (RubyWelCen) & CR21/5.
11. Fixed.
12. Fixed.
13. Replaced with 'AirRd' in both routes.
14. Replaced with 'CR19/31'.
15. Went with 'CR40' instead, as I think that's the more important road there.
16. Replaced with 'CR19/48'.
17. Went with 'CR24' in both files instead.
18. Fixed.
19. Went with 'CR19/2' and slightly recentered too.
20. Fixed.
21. Fixed.
22. Hmmm, this one is interesting.  Street blade right after that does indeed say 'Hood Ave.  Might be a case that there should be a 'To' on the sign along US-19, as it seems that's the name of the road once it leaves Shinnston.  So, going with 'HoodAve_S' instead, as the name is also along US-19 on that side of the river.
23. Replaced with points at 'BinRd' & 'FourStaRd'.
24. Replaced with point at 'CR19/7'.
25. Fixed.
26. Going with 'no-build' here, as it does it's job keeping US-19 away from I-79 here.

https://github.com/TravelMapping/HighwayData/pull/6697

[rickmastfan67]

US 60: 
1.  RCHilRd should be UnusRd.
2.  The shaping point east of RCHilRd should be replaced with a visible point at CR60/12.
3.  CR60/11 should be CR40.
4.  BlueSulPk should be BlueSulPike.

1. Fixed.
2. Done.
3. Fixed.
4. Fixed.

US 219:
1.  SprRunRd should be BackValRd (Back Valley Rd).
2.  The shaping point north of SprRunRd should be replaced with a visible point at CR219/40.
3.  The shaping point south of WV 122 should be replaced with a visible point at CR219/14.
4.  It looks like the third shaping point south of MainSt_Uni should be replaced with a visible point at what OSM calls CR219/7.
5.  Consider changing MainSt_Uni to CR13.
6.  The shaping point north of WV3_E should be replaced with a visible point at CR10.  (also affects WV 3)
7.  The second shaping point south of WV63_E should be replaced with a visible point at CR219/9.
8.  Consider replacing the shaping point south of RivRd with a visible point at CR41.  (also affects WV 63)
9.  I would change MainSt_Ron to CR45 instead of MainSt_E.
10.  BroCutRd should be CR7.
11.  The shaping point south of GeoHillRd should be replaced with a visible point at CR219/11.
12.  The shaping point south of WV39/55 should be replaced with a visible point at CR20.
13.  Consider replacing the shaping point south of DryCrkRd with a visible point.  (also affects WV 39 and WV 55)
14.  Consider replacing the second shaping point south of WV150_E with a visible point.  (also affects WV 55)
15.  It looks like CR219/14 should be CR51.  (also affects WV 55)
16.  ElkWatRd should be ElkForkRd.  (also affects WV 55)
17.  The shaping point south of US250_S should maybe be replaced with a visible point at CR43.
18.  MilSt should be Adolph Rd (AdoRd). (also affects US 250, WV 55, and WV 92)
19.  Consider replacing the shaping point south of CR219/9 with a visible point at CR219/10.  (also affects US 250, WV 55, and WV 92)
20.  The shaping point south of GeoRMRd should be replaced with a visible point at Scotts Lake Rd (ScoLakeRd).  (also affects US 250, WV 55, and WV 92)
21.  The shaping points south of US33_E should be replaced with visible points at CR219/11 and CR 24. (also affects US 250, WV 55, and WV 92)

1. Fixed.
2. Done.
3. Added as 'PeteAmosRd'.  However, had to add an additional point @ CR219/15, due to the shaping point shift taking the route out of tolerance in that area.
4. Done.
5. Changed.
6. Nuked point instead, and put one way farther up @ CR3/6 due to it looking more useful.
7. Done, as 'JacHillRd'.
8. Done.
9. No.  Seems that 'CR45' is the next street down, and that sign should really have a 'TO' on it instead.  Changing to 'FraRd' instead.
10. Changed.
11. Added as 'BeaRd'.
12. Done.
13. Shifted to CR219/42.
14. Add point @ CR1.
15. Fixed.
16. Fixed.
17. Done.
18. Fixed in all 4 routes.
19. Done as 'BraMouRd'.
20. Done as 'CR37'.
21. Done.

WV 2:  KParkMRd violates the manual as-is.

KParkMRd -> CR2/34

https://github.com/TravelMapping/HighwayData/pull/6711

[rickmastfan67]

WV 3: 
1.  Consider replacing the shaping point east of WV 305 with a visible point. 
2.  SweRd>-RanRd
3.  RaiAve_W>-CR3/17
4.  CreRd>-CR3/2
5.  CenChuRd>-CR11/3

1. Done @ CR3/27.
2. Fixed.
3. Fixed.
4. Fixed.
5. Fixed.

WV 7: 
1.  BloRid should be BroRidRd.
2.  The WVDOH Wetzel County Map seems to indicate that CR7/8 should be CR7/20.
3.  BroRidRd should be relabeled.
4.  The US250 labels should be N and S instead of W and E.
5.  I think that CR5 is correct, but I do not see a shield here.  It is the same with CR7/6.
6.  DelRd48>-CR14.
7.  WadRunRd_S seems incorrect.  (also affects US 19, which has two WadRunRd labels)
8.  Consider replacing the shaping point west of JakRunRd with a visible point.
9.  RogAve>-RogAve_S?
10.  Consider replacing the shaping point east of WV 72 with a visible point at CR7/13.

1. Fixed.
2. StreetView confirms CR7/20. Fixed.
3. Changed to 'KodRd'.
4. Fixed.
5. CR5 changed to 'CampRunRd'. ===== As for 'CR7/6', there's no such label in the file.  That was already labeled 'RusRunRd'.  BUT, I'm going to change it to 'CR7/6' due to new StreetView showing a CR number.
6. Done.  Hate roads like this with no signage due to be close to the borders.....
7. Fun.  Going with 'Num8Hol' in both WV-7 & US-19.  Also fixed the other 'WadRunRd' in US-19's file by shifting it to Brand Road (CR52) above it.
8. Done @ TedWilDr.
9. No, going with 'BroAve_E' instead since RodAve ends at that intersection per StreetView.
10. Done.

WV 12:  CR3/17>-CR31/7

WV 16:  Consider replacing or removing the shaping point south of WV61_N.  (also affects WV 61)

WV-12: Fixed.
WV-16/61: Shifted to 'MapAve'.

https://github.com/TravelMapping/HighwayData/pull/6719

[Markkos1992]

US 119: 
1.  Consider replacing the shaping point north of US33/48 with a visible point.  (also affects WV 20)
2.  HodHacCrk>-HacCrkRd  (also affects WV 20)

WV 61: DanRd>-KanTpk

[rickmastfan67]

WV 26: 
1.  Preston County GIS indicates that BeaSt should be BankSt.
2.  TerAltaPk>-StJoeRd or CR7/12

1. Changed.
2. CR7/12

WV 28:
1.  PubRd14>-MidMouRd (Middle Mountain Rd) (according to the WV Property Data Viewer)
2.  Consider replacing the shaping point east of PubRd14 with a visible point at PubRd52.
3.  PatCreRd should be CR28/3 or PatCrePike.
4.  Consider replacing the shaping point between WV 956 and WV 28 ALT with a visible point.

1.   When I looked it up at that link, the map said the road name was "Johns Run Road".  I see the name you got from the 'address info', but I honestly don't think that's reliable here in this case, as that plot of land is HUGE, and the address could be taken from a completely different road that accesses part of it.  However, I do see that Google is using that name as well.  Honestly thinking of just going no-build here due to the old '07 StreetView, but changing it to 'MidMouRd'.
2. Nah.
3. CR28/3
4. Done @ Scenic Lane (CR28/7).

WV 29:  I recommend changing CR45/4 to CR45/7.

WV 32:  This map shows WVDepRd as MainParkRd.

WV-29: Changed.
WV-32: Since there's no road name posted, and there's this big 'Canaan Valley State Park' sign there, "CanValSP" instead.

WV 41: 
1.  CR41/11>-CR41/38 (because of confidence that the latter is correct)
2.  BurrRd>-TwigRd (if kept)
3.  OldRte19>-CR19/86
4.  ForkRd>-BenWay  (if kept, maybe could be replaced by nearby CR 10)

WV 42:  KnoRd>-CR3 (because I am unsure if KnoRd is right or not)

1. Changed & recentered to said road.
2. Fixed.
3. Changed.
4. Moved to CR10 (SiloRd).

WV-42: Road name is probably 'Lower Knobley Road' if the signage @ US-48 is correct.  Then again, in the blurry '09 imagery at that intersection, looks like it's a single name.  So, yeah, 'CR3' looks to be the best solution here.

WV 46 (Keyser): 
1.  It looks like CR46/9 should be CR9/3.
2.  Consider replacing the shaping point northeast of ChaLn with a visible point.
3.  I am unsure if CR46/7 should instead be CR10.

1. Changed.
2. That point is where it is due to the route just barely going out-of-tolerance there if the point wasn't included.  StreetView shows no name for that road it's on top of, and honestly doubt it has a name.  It's only a 3 mile gap there between usable points, I don't think it's worth moving at this time.
3. It probably is CR10, as even in the super blurry StreetView imagery, it does looks like it's a full number, and not one that is a fractional.  Changed.

https://github.com/TravelMapping/HighwayData/pull/6724

[rickmastfan67]

WV 54: 
1.  OldWV54>-CR54/3
2.  SawDr>-4thAve  (also affects WV 97)
3.  CR17/6>-CR54/1 (also affects WV 97)

1. Fixed.
2. Went with "CR17/3" instead.
3. Fixed.

WV 55: 
1.  Consider replacing shaping points with visible points between WV 41 and WV 20.
2.  CR28/1_S>-CR28/1

1. Replaced first one @ CR15/2, left other 2 as-is.
2. Changed in both WV-55 & WV-28.

WV 63: 
1.  CR48 should be CR46.
2.  Is GraDr a worthwhile visible point?
3.  It looks like WalSt should be WalSt_S.

1. Removed point and replaced it with the more important road near by @ CR43 since not in-use.
2. Needed for shaping.  If removed, route goes majorly out-of-tolerance right there.
3. Changed to 'GreAve_W' instead (and added a 'GreAve_E' point as well).

WV 66:  I think that CR11/1 should be CR9/3.  (or just go SnoDr_W and SnoDr_E)

Going to go with 'SnoDr_W/E'.

WV 72: 
1.  CR45>-CR45/3 (based on GSV)
2.  Consider replacing the shaping point north of CR45 with a visible point at Jenningston Rd.
3.  I am unsure if CR1 is at the right location.
4.  CatSt>-CatSt_E.

1. Fixed.
2. Done.
3. It WAS in the correct location.  However, it seems it's been moved due to Corridor H construction.  Plus it seems they are working on completely rerouting WV-72 here to come up and intersect Corridor H at-grade instead of having a connector road.  So, I think I'll just place the new CR-1 intersection as close as possible, but keep an eye out for this full reroute and then make a post about it, as CR-1's new location is pretty much were the northern end of the future re-route happens.
4. Fixed.

WV 86: 
1.  WooLn is probably best replaced by nearby JefAve.
2.  GreHilRd>-GreHilDr

1. Done.
2. No change here.  You got the wrong road.  Where the point currently is, is indeed 'GreHilRd'.

https://github.com/TravelMapping/HighwayData/pull/6726

[rickmastfan67]

WV 88: 
1.  CR88/25 needs to be slightly relocated.
2.  DemCemRd>-DemRd
3.  ForkShoRd>-ForkRd, NorForkRd, NForkRd, etc.
4.  LibHarRd>-HarRd

1. Fixed.
2. Fixed.
3. Going with 'CR9' instead then. lol.
4. Fixed.

WV 92: 
1.  I presume that Tra is one of those "we need a point somewhere" points. 
2.  CR28/9_S should just be CR28/9.
3.  I am unsure if the shaping points from Durbin east to the south end of the US 250 concurrency are necessary (though the closest one to the south end could be replaced by CR250/4).  I am at a "whatever" mood in regard to the forest roads northwest of Dublin because I am unable to clarify PubRd92.  (also affects US 250)
4.  FriSt should be FinSt.
5. Shale Rd may be a worthwhile visible point south of Belington.  (also affects US 250)
6.  I think CR56 should be CR5/6.

1. Yes.  However, with StreetView, can confirm a posted road (Hefner Lane) just south of that, so, swapping with that.
2. Was due to 2 of the same route # being in WV-28's file.  Sadly, for 'CR28/9_S', StreetView is too blurry to get the proper name for the road (since it's not shown in OSM).  However, for 'CR28/9_N' in WV-28's file, it's crystal clear, so I changed that one to a name, and fixed 'CR28/9_S -> CR28/9' in both WV-28 & WV-92's file.
3. Not sure how you missed it, but there's a big wooden sign @ the intersection with a '92' at the bottom.  It's that, or I could swap to 227 across the street, as it has a proper visible shield.  Still, probably swap to the 'NF92' style label, due to several shield actually being posted with their intersections with US-250 in the area.
4. Fixed.
5. Done.
6. Definitely a fractional CR route per StreetView.  Changed.

WV 270:  HighSt_N>-HighSt

WV 307:  Consider replacing the shaping point south of GraRd_N with a visible point.

WV-270: Fixed.
WV-307: Done @ CR22/1.

WV 310:  SpeRd>-SpeAve

WV 311:  Is JefLn even needed?

WV 705:  WilDr>-DonNehDr

WV-310: Fixed.
WV-311(Swe): Due to 'Sweet Springs Resort Park' being there, I thought it would be justifiable.  So, no change here.
WV-705: Fixed.

=====

https://github.com/TravelMapping/HighwayData/issues/6781

[rickmastfan67]

US 119: 
1.  Consider replacing the shaping point north of US33/48 with a visible point.  (also affects WV 20)
2.  HodHacCrk>-HacCrkRd  (also affects WV 20)

WV 61: DanRd>-KanTpk

US-119:
1. Done @ CR119/2.
2. Fixed.

WV-61:
Fixed.

https://github.com/TravelMapping/HighwayData/pull/6796

And that should finally finish off this thread.