Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on July 02, 2025, 04:27:32 am
-
So, was just randomly looking @ WV-83 due to another thread, and noticed some funkyness with the boarder of WV/VA at the southern end of the route.
So, I started to GSV scope out the route, and discovered that our transition between the two states on 83 is way off.
https://maps.app.goo.gl/YtSpR8aKuPNpGk7h9 - WV border sign
https://maps.app.goo.gl/wAGcNKmhdATyYia16 - VA border sign
If we go with the border line from Google Maps, we might have some 'VA-83' segments solely in WV.
Should we just make the transition of the routes where the pavement changes since the state line seems to ride 83 here? If we choose this, the 'DavMouRd' point in WV-83 will need to move to VA-83's file. And the 'current' border point in both files, should become a 'CR83/9 (https://maps.app.goo.gl/m13seze7zuVAuV8L9)' point in just VA-83's file.
Anyway we look at this, this will require news entries for both routes.
-
I moved the state line point to the pavement change location, renamed the former state line location as DivRidRd, and added DavMouRd to the file...
-
I moved the state line point to the pavement change location, renamed the former state line location as DivRidRd, and added DavMouRd to the file...
Can you post the coordinates you used for the new border point so I can make sure WV is synced?
-
^ Looks like what he sent is live, so should be able to just grab them from Github...
-
^ Looks like what he sent is live, so should be able to just grab them from Github...
Isn't live on the site. Just only in Github. Guess something else broke the update. (EDIT: Yeah, I see what broke it, the new VA US-311 Alt file was missing.)
Still, will submit my end in a little bit.
-
WV side submitted.
https://github.com/TravelMapping/HighwayData/pull/8469