Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on October 17, 2021, 08:24:08 pm
-
I think that this route should extend east (https://www.google.com/maps/@37.1335401,-80.3731408,3a,75y,330.72h,84.41t/data=!3m7!1e1!3m5!1sjQ0LeB8Uc4wwtBtYmOyI4A!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DjQ0LeB8Uc4wwtBtYmOyI4A%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D107.881645%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192) along US 11 to I-81 (Exit 118C)/US 460.
-
Signage @ I-81 Exit 118C 2nds this.
https://goo.gl/maps/NT7BxoWmaxpsvhYa6
-
route was extended
-
I recommend making the following label changes back at the US 11/US 460 interchange:
US 11: US460_W>-US460 or US460_Chr (This is not exactly wrong as-is, but it comes off as the US 11/US 460 concurrency ending farther west than it actually does.)
US 460 BUS (Christiansburg): US11/460>-US460_C (based on using US460_A and US460_B for the other intersections now, the current label created an odd self-reference error)
-
US 460 BUS (Christiansburg): US11/460>-US460_C (based on using US460_A and US460_B for the other intersections now, the current label created an odd self-reference error)
Or the US-460 exit numbers there could be used instead.
-
US 460 BUS (Christiansburg): US11/460>-US460_C (based on using US460_A and US460_B for the other intersections now, the current label created an odd self-reference error)
Or the US-460 exit numbers there could be used instead.
That could be done too. The problem I have with using those US 460 exit numbers is that they are not mileage-based, and that the Richlands and Tazewell Bypasses (could include Bluefield, VA) have sequential numbers starting from 1 as well.
-
US 460 BUS (Christiansburg): US11/460>-US460_C (based on using US460_A and US460_B for the other intersections now, the current label created an odd self-reference error)
Or the US-460 exit numbers there could be used instead.
That could be done too. The problem I have with using those US 460 exit numbers is that they are not mileage-based, and that the Richlands and Tazewell Bypasses (could include Bluefield, VA) have sequential numbers starting from 1 as well.
I don't think that would be much of an issue on the Business route, since they're separate. It would be better than _A _B _C type labels for sure though. Sad that VA doesn't want to do the numbering like NC on US highways. Would make this so much easier.
-
^Yeah, it is probably fine to go with US460_W, US460(5), US460(3), US460(2), US460_E.
I-73 may solve this in 2460 as the earliest. :-X
-
the current label created an odd self-reference error)
FWIW, I've been working on some improvements to the LABEL_SELFREF datacheck. Once it's ready for production, cases like this where a bannered route has its unnumbered parent's number after a slash won't be flagged.
That said, I like the exit number solution.
-
changes made