Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on October 18, 2024, 10:18:01 pm
-
We should have point on each end of the 'bypass' around Wildwood where the old route joins/leaves the current AB-16.
They even consider the WB end an 'exit (https://maps.app.goo.gl/LF4ZkUd68zroEcg98)'. Only name I can find for it, is 'Twp Rd 534A (https://maps.app.goo.gl/j5oZr7UzXTBGxXDw9)'. Not sure how we'd name the WB on-ramp on the other end.
Also:
50St_Wil -> RR92A (https://maps.app.goo.gl/uCRBNUFtbEvTkhzV6)
-
We should have point on each end of the 'bypass' around Wildwood where the old route joins/leaves the current AB-16.
Nah, no sense tracking every little reroute that's happened, especially since before the CHM era.
They even consider the WB end an 'exit (https://maps.app.goo.gl/LF4ZkUd68zroEcg98)'.
Not anymore! (https://www.google.com/maps/@53.6096075,-115.2163402,3a,15y,255.68h,91.01t/data=!3m9!1e1!3m7!1ssZpB4OwYsN8-O9R9fHU-kg!2e0!7i16384!8i8192!9m2!1b1!2i50?coh=205409&entry=ttu&g_ep=EgoyMDI0MTAxNi4wIKXMDSoASAFQAw%3D%3D) ;)
Not sure how we'd name the WB on-ramp on the other end.
Simple, just 1PPI that $grawlix onto Fif...ty...
Also:
50St_Wil -> RR92A (https://maps.app.goo.gl/uCRBNUFtbEvTkhzV6)
Aah, OK.
And the other one, 50St_Lav is actually RR134 (https://www.google.com/maps/@53.456288,-111.868238,3a,15y,135.05h,85.02t/data=!3m9!1e1!3m7!1sPT7_Rw69EQ5TcCqSB2tjfQ!2e0!7i16384!8i8192!9m2!1b1!2i50?coh=205409&entry=ttu&g_ep=EgoyMDI0MTAxNi4wIKXMDSoASAFQAw%3D%3D).
https://github.com/TravelMapping/HighwayData/pull/7822
-
They even consider the WB end an 'exit (https://maps.app.goo.gl/LF4ZkUd68zroEcg98)'.
Not anymore! (https://www.google.com/maps/@53.6096075,-115.2163402,3a,15y,255.68h,91.01t/data=!3m9!1e1!3m7!1ssZpB4OwYsN8-O9R9fHU-kg!2e0!7i16384!8i8192!9m2!1b1!2i50?coh=205409&entry=ttu&g_ep=EgoyMDI0MTAxNi4wIKXMDSoASAFQAw%3D%3D) ;)
Well, the sign 'could' be in the grass, as the poll is still there. lol.