Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: sipes23 on February 19, 2017, 03:20:43 pm
-
US87 has a broken concurrency in Casper, WY. At Hat Six Road (WYO 253), it should stay concurrent with US20/26 as far as where it breaks off of Yellowstone Highway to join I-25 at exit 186. The exit ramp is kind of strange there. (I actually think it stays concurrent with US20/26 at that point too. I'll make a point of driving through it this afternoon to double check if anyone has any questions.)
It's one of those super concurrent stretches of road that seems to crop up here and there. (Wisconsin, I'm looking at you.)
-
I think the problem is that the WY 258 point on US 87 and the WY 258 point on US 20 have slightly different coordinates; I think the WY 258 point realignment was missed for US 87 during the usawy review.
https://github.com/TravelMapping/HighwayData/commit/01d0764db0e3bd0bac7e3bb3f1b71c46ce61f255 (https://github.com/TravelMapping/HighwayData/commit/01d0764db0e3bd0bac7e3bb3f1b71c46ce61f255) - relevant github link; US 87 was not adjusted when US 20/26 were.
-
It's one of those super concurrent stretches of road that seems to crop up here and there. (Wisconsin, I'm looking at you.)
Because we (sensibly) limit labels to 2 routes, I missed it. Fixed.
-
It's one of those super concurrent stretches of road that seems to crop up here and there. (Wisconsin, I'm looking at you.)
Because we (sensibly) limit labels to 2 routes, I missed it. Fixed.
And it's even kind of tricky on the ground. I don't even know what motivated me to find out why I had this stretch of road not clinched.