Author Topic: WV: Point Concerns from June 2023-May 2024 Trips  (Read 8298 times)

0 Members and 1 Guest are viewing this topic.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3301
  • Last Login:Yesterday at 10:44:11 pm
WV: Point Concerns from June 2023-May 2024 Trips
« on: October 26, 2023, 01:50:10 pm »
I-77:  Consider adjusting the shaping point on this or WV 31 to keep the line on I-77 east of WV 31.

US 52: 
1.  BarRd>-MayRidRd or CR10
2.  The shaping point south of BarRd could possibly be replaced with a visible point.
3.  Consider replacing the shaping point west of WV 71 with a visible point.

US 60:  (from east to west) 
1.  I am unsure that DunTolBrg is correct.  I think I would go with DunBri.
2.  RoxSt>-RoxAve
3.  MidTrl>-8thAve
4.  23rdSt should be relabeled.
5.  KanTur>-JRKanTpk (also affects WV 20)

US 119:  (from north to south)
1.  CR119/14>-CR119/11
2.  Consider replacing the shaping point north of CR83 with a visible point at CR119/16.
3.  Consider replacing shaping points with visible points throughout route.
4.  I would replace LatSt with MainSt_W in Grafton because the latter has a signal.
5.  BeeSt>-BeeSt_S
6.  CR2/2>-CR22 (also affects US 250)
7.  I am unsure if VinHilRd is correct.  I think it should be CR60 or CR250/60.
8.  CamChuRd>-ChuRd (also affects US 33)
9.  FinCrkRd>-VadRd or CR11 (also affects US 33)
10.  CedCrk>-CedCrkRd (also affects US 33)
11.  BFGooDr>-MusWay or CR119/23 (also affects US 33)
12.  GanHarRd>-HarRd
13.  PocRiv>-RivRd or CR34
14.  RobRun>-RobRunRd
15.  JulyRun>-JulyRunRd
16.  HurCrkRd>-AmmaRd or CR23
17.  I am unsure SycSt is at a road.

US 250: 
1.  CR2/3>-CR23
2. Consider replacing the shaping point south of WV38 with a visible point.
3.  Is the shaping point south of MidRd necessary?
4.  JacSt>-CR1 (also affects WV 2)

WV 2: 
1.  BruDr>-CroCreRd or CR7
2.  CR2/34>-CR2/14

WV 3:
1.  CaveHolRd>-LostLn
2.  Consider replacing the shaping point east of CaveHolRd with a visible point at CR3/5.

WV 16:  CraMouRd>-CanMouRd

WV 20:
1.  NewHopeRd>-CerRd or CR17/1 
2.  Consider replacing the shaping point north of MorSt with a visible point.
3. A point should be added at CR 3 (access to Brush Creek Falls State Park).
4.  CR18/2>-CR18
5.  Consider replacing the shaping point north of CR20/2 with a visible point at CR44/7.
6.  NewRivRd>-CR26
7.  MainSt>-CR31.  EMainSt>-MainSt (if doable)
8.  The shaping point north of LeeHolRd should be replaced with a visible point at CR44/2.
8.  AmiAve>-AmiSt
9.  GraCreRd_S>-CR32_S.  GraCreRd>-CR32_N
10.  Consider replacing the shaping point south of CR11.
11. MayAve>-CR48
12.  RaiAve>-CR9
13. CR20/11 should debatably be CR4/15.
14.  CR57/2>-CR20/22

WV 27:  NorRd>-CR18

WV 38: 
1.  CR56>-CR5/6
2.  If we really need a point at CreDr, I think QuaDr is a better option nearby.

WV 39:  GraCreRd>-CR32

WV 57: 
1.  ArnRunRd>-ArnRd  (The ArnRunRd label on WV 20 nearby is oddly correct.)
2.  DogRunRd>-DogRd

WV 58: 
1.  CostRd>-CotLn (I cannot quite read the fractional county route number.)
2.  PhiPk_N>-PhiPike_N
3.  PhiPk_S>-CR23/9

WV 67: 
1.  Consider replacing the shaping point south of BraRidRd with a visible point.
2.  WinHillRd>-HukRunRd or CR30

WV 76:
1.  OakLakeRd>-OralLakeRd or CR17
2.  CR77/1>-CR77/7
3.  GalRd>-ASt or CR76/3

WV 83: BForkRRd>-BFRidRd

WV 122: 
1.  Consider replacing shaping points with visible points.
2.  WayCemRd>-WayCreRd
3.  CR219/17>-CR23/7

WV 123: 
1.  AirRd>-DawSchRd or CR23/1
2. I cannot justify OldRd as a worthwhile visible point, but replacing it with the visible point at the nearby King Coal Hwy Extension when it opens is fine enough IMO.

WV 161: 
1.  Tazewell County GIS indicates RavSt>-RadSt.
2.  HorRd>-AbbsValRd
3.  The shaping points south of Mon are off the route.
4.  I guess Mon is here because a point is needed somewhere.

WV 218:
1.  I am seeing MainSt_W instead of CroRd.
2.  MirRunRd>-CR22/1
3.  CR39/3>-CR18
4.  Consider replacing the shaping point north of DaysRunRd with a visible point.

WV 310: 
1.  CR20>-CR310/1
2.  Consider replacing the shaping point south of CR5/4 with a visible point at CR5/5.
3.  CR52>-CR5/2
4.  CR31/7>-CR31/10
5.  Consider replacing the shaping point(s) north of BurCabRd with a visible point.

WV 635:  I think that HiteForkRd should be CR635/1.
« Last Edit: May 20, 2024, 02:57:34 pm by Markkos1992 »

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3301
  • Last Login:Yesterday at 10:44:11 pm
Re: WV: Point Concerns from June 2023-March 2024 Trips
« Reply #1 on: April 12, 2024, 06:53:30 pm »
As a more general FYI, I have bookmarked this map that shows all of WV Routes.  I am very much glad that I will not have to deal with the DOH Map anymore.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
Re: WV: Point Concerns from June 2023-May 2024 Trips
« Reply #2 on: October 30, 2024, 09:31:15 pm »
I-77:  Consider adjusting the shaping point on this or WV 31 to keep the line on I-77 east of WV 31.

Fixed in I-77.

US 52: 
1.  BarRd>-MayRidRd or CR10
2.  The shaping point south of BarRd could possibly be replaced with a visible point.
3.  Consider replacing the shaping point west of WV 71 with a visible point.

1. Going with 'CR10'.
2. I'm assuming you're referring to the one just to the 'east' of that point?  Nah. Leaving that one as-is.  However, the one to the 'west', yeah, I can adjust that one to 'CR10/2'.
3. Adjusted to nearby 'CR52/11'.

US 60:  (from east to west) 
1.  I am unsure that DunTolBrg is correct.  I think I would go with DunBri.
2.  RoxSt>-RoxAve
3.  MidTrl>-8thAve
4.  23rdSt should be relabeled.
5.  KanTur>-JRKanTpk (also affects WV 20)

1. Changed based on this sign to 'DunBrg'.
2. Fixed.
3. Fixed.
4. Changed to 'CR60/14', as I added another 'CR1' somewhere else that's more important when removing shaping points near some roads.
5. Went with 'CR60/32' in both routes instead.

==

Submitted: https://github.com/TravelMapping/HighwayData/pull/7872

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
Re: WV: Point Concerns from June 2023-May 2024 Trips
« Reply #3 on: November 08, 2024, 01:18:04 am »
US 119:  (from north to south)
1.  CR119/14>-CR119/11
2.  Consider replacing the shaping point north of CR83 with a visible point at CR119/16.
3.  Consider replacing shaping points with visible points throughout route.
4.  I would replace LatSt with MainSt_W in Grafton because the latter has a signal.
5.  BeeSt>-BeeSt_S
6.  CR2/2>-CR22 (also affects US 250)
7.  I am unsure if VinHilRd is correct.  I think it should be CR60 or CR250/60.
8.  CamChuRd>-ChuRd (also affects US 33)
9.  FinCrkRd>-VadRd or CR11 (also affects US 33)
10.  CedCrk>-CedCrkRd (also affects US 33)
11.  BFGooDr>-MusWay or CR119/23 (also affects US 33)
12.  GanHarRd>-HarRd
13.  PocRiv>-RivRd or CR34
14.  RobRun>-RobRunRd
15.  JulyRun>-JulyRunRd
16.  HurCrkRd>-AmmaRd or CR23
17.  I am unsure SycSt is at a road.

1. Fixed.
2. Went with 'KelRd', as I already had a CR119/16 in a separate area.
3. I try to due to better GSV now whenever possible if it's reasonable.
4. Done.
5. Changed.
6. Went with 'HacCreRd' instead for both, as there's already a 'CR22' in US-119's file.
7. Wrong route.  No such label in US-119.  This should have been in US-250's section.  Either way, I'll go with 'CR250/60' in US-250's file till when/if ever, they post signage at that intersection. It's wild, as normally WVDOH is very good at signing roads like this.
8. Fixed in both.
9. Fixed in both.
10. Went with 'CR17' instead in both.
11. Chose 'CR119/23' for both.
12. Fixed.
13. Went with 'CR34'.
14. Fixed.
15. Looks like it's more like a driveway if anything, and not a real road, since there's no signage there.  Demoting to a shaping point since not in-use.
16. 'AmmaRd' since there's already another 'CR23' in the file.
17. Is is.  lol.  There's a streetblade there.

=====

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

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
Re: WV: Point Concerns from June 2023-May 2024 Trips
« Reply #4 on: November 10, 2024, 01:05:43 am »
US 250: 
1.  CR2/3>-CR23
2. Consider replacing the shaping point south of WV38 with a visible point.
3.  Is the shaping point south of MidRd necessary?
4.  JacSt>-CR1 (also affects WV 2)

1. Seems that WVDOH has 'multiple' CR23's in that area.  Because of that, I'm going to 'revert' to road names here instead, as I found a tolerance issue in the area as well. Going with 'FoxRd' instead here.
2. ReeRd
3. Meh, probably not really.  Only a loss of 0.05 miles when removing it.  Gone.
4. There's already a 'CR1' in US-250's file.  However, the road name is incorrect per signage to begin with. Going with 'BogRunRd' instead in both routes.

WV 2: 
1.  BruDr>-CroCreRd or CR7
2.  CR2/34>-CR2/14

1. CR7
2. Fixed.

WV 3:
1.  CaveHolRd>-LostLn
2.  Consider replacing the shaping point east of CaveHolRd with a visible point at CR3/5.

1. Fixed.
2. No change.  Doing so, would cause the route to go out of tolerance, requiring another point.  Don't feel like it's justifiable here.

WV 16:  CraMouRd>-CanMouRd

Fixed.

=====

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