Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on April 26, 2020, 03:21:14 pm
-
Wow I am very much confused.....
An initial glance would make you think that the issue is that US 220 BUS (Asheboro) just needs to be synced with I-73, I-74, US 220, and US 220 ALT (Candor) here. However, the posting here shows things differently.
1. US 220 BUS (Asheboro) should be synced with I-73, I-74, and US 220 here. (https://www.google.com/maps/@35.6203955,-79.8264647,3a,75y,134.75h,90t/data=!3m7!1e1!3m5!1sJbXPM1mARfUuJ_pyNiop-Q!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DJbXPM1mARfUuJ_pyNiop-Q%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D140.6474%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656) I am certain on that.
2. US 220 ALT (Candor) looks like it should be truncated to the nearby intersection with US 220 BUS (Asheboro) to the northeast instead of being concurrent with it to I-73/I-74/US 220 as it shows now. (https://www.google.com/maps/@35.6215093,-79.8248986,3a,75y,293.51h,82.54t/data=!3m6!1e1!3m4!1sNJQJoqJiIOLERfgaMx7o6g!2e0!7i13312!8i6656)
3. NC 134 (https://www.google.com/maps/@35.6203955,-79.8264647,3a,75y,169.19h,85.09t/data=!3m6!1e1!3m4!1sJbXPM1mARfUuJ_pyNiop-Q!2e0!7i13312!8i6656) is posted at the interchange even though the END sign NB is where the HB shows its endpoint (https://www.google.com/maps/@35.6182411,-79.8272159,3a,37.5y,5.07h,89.06t/data=!3m6!1e1!3m4!1s4h2TpHSVEuDjCr1Y98jveQ!2e0!7i13312!8i6656). I think it should just be extended to the interchange though I am unsure what official sources would say on that.
-
3. NC 134 (https://www.google.com/maps/@35.6203955,-79.8264647,3a,75y,169.19h,85.09t/data=!3m6!1e1!3m4!1sJbXPM1mARfUuJ_pyNiop-Q!2e0!7i13312!8i6656) is posted at the interchange even though the END sign NB is where the HB shows its endpoint (https://www.google.com/maps/@35.6182411,-79.8272159,3a,37.5y,5.07h,89.06t/data=!3m6!1e1!3m4!1s4h2TpHSVEuDjCr1Y98jveQ!2e0!7i13312!8i6656). I think it should just be extended to the interchange though I am unsure what official sources would say on that.
NC 134 was created in Randolph County as a renumbering of SR 1134 and SR 1116 by a NC Route Change dated June 3 1966. SR 1134 ended at SR 1138 ( Dawson Miller Road). This is an official source which places the END sign where it is.
-
3. NC 134 (https://www.google.com/maps/@35.6203955,-79.8264647,3a,75y,169.19h,85.09t/data=!3m6!1e1!3m4!1sJbXPM1mARfUuJ_pyNiop-Q!2e0!7i13312!8i6656) is posted at the interchange even though the END sign NB is where the HB shows its endpoint (https://www.google.com/maps/@35.6182411,-79.8272159,3a,37.5y,5.07h,89.06t/data=!3m6!1e1!3m4!1s4h2TpHSVEuDjCr1Y98jveQ!2e0!7i13312!8i6656). I think it should just be extended to the interchange though I am unsure what official sources would say on that.
NC 134 was created in Randolph County as a renumbering of SR 1134 and SR 1116 by a NC Route Change dated June 3 1966. SR 1134 ended at SR 1138 ( Dawson Miller Road). This is an official source which places the END sign where it is.
Ah, but the same 1966 document says NC 134 starts at US 220.
OTOH, NCDOT has been very inconsistent on this:
2012 document assigning I-73/74 to the freeway north of the interchange in question says both NC 134 and SR 1138 are at the interchange.
The current NCDOT Randolph County map explicitly shows the road between NC 134 END sign and I-73/74 as SR 1138.
The on-line traffic data has a point on the segment in question and also calls it SR 1138.
-
Based on the full posting without a "TO" shield at the I-73/I-74 interchange, I am in favor of extending NC 134 to there.
-
fixes made and in the queue