Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: vespertine on May 15, 2022, 04:26:21 pm
-
Quick one I discovered while checking future roadtripping plans: US21BusElg -> US21BusElk.
v.
-
Other Related Revisions:
US 21 BUS (Elkin): Maybe replace SimmSt with EastEndBlvd (https://www.google.com/maps/@36.2252195,-80.8309279,3a,75y,344.31h,97.41t/data=!3m6!1e1!3m4!1sp5-gyGzsUrmaGlwL0LNy4g!2e0!7i16384!8i8192).
NC 268: The US21Bus labels should be N and S instead of W and E.
-
changes made and in the queue
-
US 21 BUS (Elkin): Maybe replace SimmSt with EastEndBlvd.
Looking at every intersection in GSV shows ValDr instead of ValRd.
Secondly, I think that US21BusElg should be added as an alternate name. yakra, who is directly affected by this change?
NC 268: The US21Bus labels should be N and S instead of W and E.
I think these labels were accidentally switched.
-
US 21 BUS (Elkin):
Secondly, I think that US21BusElg should be added as an alternate name. yakra, who is directly affected by this change
I'm one of them, though I can change the route name in my list file (update to be pulled in later this week).
-
US 21 BUS (Elkin):
Secondly, I think that US21BusElg should be added as an alternate name. yakra, who is directly affected by this change
I'm one of them, though I can change the route name in my list file (update to be pulled in later this week).
I did this in the usausb.csv file. Was there somewhere else the alt name also needed to be placed?
-
^I see it now. It should have been written as US21BusElg instead of nc.us021buselg. I think that is the issue here.
-
^I see it now. It should have been written as US21BusElg instead of nc.us021buselg. I think that is the issue here.
Yes, I have it fixed for tonight's update.