Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on February 18, 2021, 05:27:07 pm
-
US29Bus/NC87 should be changed to US29Bus/87.
-
fixed and in the queue
-
Now I see why you did what you did. "US29Bus/87" puts up a duplicate label error as it is still under the "US29Bus_S" label.
Anyway removing "US29Bus/87" under "US29Bus_S" is the only option here.
The only list file using this line according to the Github search ""NC US158" "US29Bus/87" is dave1693. I will notify him via Github as he updates regularly.
EDIT: Saying "only option" is technically incorrect, but keeping the "US29Bus/87" label is the best option here IMO.
-
The existing US29Bus_N AltLabel would be a perfectly serviceable primary label.
-
Now I see why you did what you did. "US29Bus/87" puts up a duplicate label error as it is still under the "US29Bus_S" label.
Anyway removing "US29Bus/87" under "US29Bus_S" is the only option here.
The only list file using this line according to the Github search ""NC US158" "US29Bus/87" is dave1693. I will notify him via Github as he updates regularly.
Breaking that line in my .list file won't change my mileage, as I actually traveled that segment as part of Business US 29 (back when it was still US 29, before the east side bypass was built). Let me know what change I need to do to unbreak that line and I'll fix it when I have more brain.
-
I changed it to US29Bus_N
-
I changed it to US29Bus_N
Effectively right at the same time as I posted my update, thus generating the following line in my log file:
"Equivalent waypoint labels mark zero distance traveled in line: NC US158 US29Bus/87 US29Bus_S"
Which still doesn't affect my miles traveled, but I'll have to put in another fix for the line.