Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on January 28, 2024, 06:12:53 pm
-
At it's intersection with US-25E, the intersection has now been split apart, creating a short multiplex with US-25E now.
When they did this, the 'original' location of the intersection is now gone, as they put the two intersections on either side of it.
Thus, the 'TN131' point in US-25E should be marked as a 'closed' point when the new intersections are added in.
No imagery shows this yet, but both OSM & Google have been updated to reflect this. Plus GSV was already in the area to photograph it back in July '21.
-
https://github.com/TravelMapping/HighwayData/pull/7243
Fortunately the 3 users with travels on TN 131 that used the US25E point in their lists were either using it for travel the same direction (north of the point) or keeping it in an unused line, so US25E +> US25E_N and no broken lists.
-
https://github.com/TravelMapping/HighwayData/pull/7243
Fortunately the 3 users with travels on TN 131 that used the US25E point in their lists were either using it for travel the same direction (north of the point) or keeping it in an unused line, so US25E +> US25E_N and no broken lists.
You forgot to add in the '*OldTN131' point in TN-131 where the old intersection with US-25E was. Thus, the site will not properly trigger the multiplex between the two routes because of that.
-
Fix submitted and pulled in.
FWIW, if there's an urgent message for me, I won't look for it here. Thanks for deciding to post it to Github too.
-
FWIW, if there's an urgent message for me, I won't look for it here. Thanks for deciding to post it to Github too.
Well, it wasn't 'THAT' urgent. At least it wasn't a point that made a route traverse the earth 10x times over. LOL!