Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on November 18, 2020, 06:00:58 pm

Title: WV: WV 259 Point Errors
Post by: Markkos1992 on November 18, 2020, 06:00:58 pm

1.  CR20/1 is actually at CR12 (https://www.google.com/maps/@38.8777062,-78.8662925,3a,37.5y,311.37h,80.24t/data=!3m6!1e1!3m4!1scyK3nw-bTBxcL6De-YxKSg!2e0!7i13312!8i6656).
2. CR1/4 should be CR14 (https://www.google.com/maps/@38.9538035,-78.8041006,3a,15y,249.25h,83.49t/data=!3m6!1e1!3m4!1sfU8F8-plLMwa4PhbVgL_-w!2e0!7i13312!8i6656), but there is already a CR14.  I suggest CR14_A.

Note that the OldRt55 labels may be on a future yakra grep (also affects US 48 and WV 55).

Title: Re: WV: WV 259 Point Errors
Post by: rickmastfan67 on January 31, 2021, 03:18:51 am

1) Fixed.
2) Went with 'KimRunRd' instead. (the current 'CR14' is in-use)

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

Title: Re: WV: WV 259 Point Errors
Post by: yakra on January 31, 2021, 01:27:56 pm

No suffix, be it either directional or county?

Title: Re: WV: WV 259 Point Errors
Post by: rickmastfan67 on January 31, 2021, 01:39:28 pm

Quote from: yakra on January 31, 2021, 01:27:56 pm

No suffix, be it either directional or county?

Most of the time, WV doesn't put up shields on the CR's beyond at the intersections as shown in the SV links in the original post.  So, I sometimes just pic and choose the best option possible depending if there's a possibility of a duplicate (which is high in WV) somewhere else along the route.