Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on March 07, 2023, 09:06:01 pm
-
As part of my FL trip, I got to spend time with Alex, Brent, and Chris (visiting from MN I think) the last couple days.
One thing we discussed was whether there was actually a FL 686/FL 694 concurrency, and we determined that there was not based on GIS. (presuming that the frontage roads are just considered as ramps to/from FL 694 and US 92)
I think that FL 686 should just be truncated to FL 694 in the HB, and that nothing else here is necessary.
-
Signage seems to disagree with you. This is mainly why I added it.
https://goo.gl/maps/UmYE9HEyhwgx43W69
https://goo.gl/maps/cHpwgxywpHNiHgZy8
https://goo.gl/maps/ixkHBCbzJ3UMSbp59
Could probably just break any concurrency with the two.
-
Breaking the concurrencies would work IMO as well here. This kinda reminds me of TX 158/TX 191 if I remember right (cue yakra).
-
Ok, then I'll just add a hidden point to FL-686's file to break this without any label changes needed.
Also gives me a reason to fix up the locations on the route as well in the expressway construction area too between CR-611 & FL-688.
https://github.com/TravelMapping/HighwayData/pull/6474