Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: yakra on May 01, 2020, 12:41:12 pm
-
During usanp activation, when WY US212Yel was deleted (https://github.com/TravelMapping/HighwayData/commit/67e2e42415fb8f5cdb249709ac36faecb75de72f#diff-7da7156b4996bf8fcbd6cc3739221addL624), its AltRouteNames were added to MT NEntRd (https://github.com/TravelMapping/HighwayData/commit/67e2e42415fb8f5cdb249709ac36faecb75de72f#diff-73ce3c90c91d96e3f5de8f7feec5466dR135) rather than to WY NEEntRd (https://github.com/TravelMapping/HighwayData/commit/67e2e42415fb8f5cdb249709ac36faecb75de72f#diff-73ce3c90c91d96e3f5de8f7feec5466dR136) the next line down.
The old WY US212Yel (https://github.com/TravelMapping/HighwayData/blob/67e2e42415fb8f5cdb249709ac36faecb75de72f/hwy_data/WY/usaus/wy.us212yel.wpt), which originally had the US212_W AltRouteName (https://github.com/TravelMapping/HighwayData/commit/67e2e42415fb8f5cdb249709ac36faecb75de72f#diff-7da7156b4996bf8fcbd6cc3739221addL624), corresponds to the current (https://github.com/TravelMapping/HighwayData/blob/e924be2ee2b4a037212a0ec1d0a9c148a80a61e6/hwy_data/WY/usanp/wy.neentrd.wpt) WY NEEntRd (http://travelmapping.net/hb/?r=wy.neentrd).
This causes an AltRouteName collision in MT: usanp is processed after usaus, and mt.nentrd "steals" MT US212_W in the route hash table from MT US212Coo (https://github.com/TravelMapping/HighwayData/blob/758c3e94894771cf05e0124b9afa62dabb5a8cd2/hwy_data/_systems/usaus.csv#L624), the proper route for that .list name.
usanp.csv:
usanp;MT;NEntRd;;;North Entrance Road, Yellowstone NP;mt.nentrd;US212Yel,US212_W
usanp;WY;NEEntRd;;;Northeast Entrance Road, Yellowstone NP;wy.neentrd;
->
usanp;MT;NEntRd;;;North Entrance Road, Yellowstone NP;mt.nentrd;
usanp;WY;NEEntRd;;;Northeast Entrance Road, Yellowstone NP;wy.neentrd;US212Yel,US212_W
-
I've fixed this and will pull it in shortly.