Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on December 07, 2024, 02:35:12 am
-
36(580) -> 68 (https://maps.app.goo.gl/enWBLaXoqZnUfWPH9) (the routes own exit numbers take priority if they are posted)
70 -> 70A
(missing) -> 70B - graph connection for NV-443 is needed here. There's already a point in NV-443's file for this interchange, but it's missing in US-395's file.
-
I'll take care of the graph connection and Exit 70 today.
The 36/68 issue is a case of 36 is the exit number NB, but 68 is SB. I can make the change, but is there other precedent for this?
-
https://github.com/TravelMapping/HighwayData/pull/7967
"68" was already an alternate waypoint for the 80/580/395 interchange, so I swapped that to be the primary label. I also used this opportunity to add a couple of points at major intersections in the Carson Valley, both former SRs and one a signed national scenic byway in an in-development system.
-
The 36/68 issue is a case of 36 is the exit number NB, but 68 is SB. I can make the change, but is there other precedent for this?
I-840 in NC is one recent one that rings a bell where I-73 leaves it.
Pretty much, if the route has exit numbers of it's own beyond an interchange, and has a number in that chain posted where another routes numbering scheme starts/ends, we always use the posted number for the route of the file.
If they had used I-580's number 36 both ways, then that 36(580) label would have been acceptable. But since SB used US-395's number 68, that gains the priority in US-395's file, while I-580's file keeps using the 36.
-
Noted for future reference. Regardless, it's in there with 68 as the primary number. Thankfully, I don't see much more exit number confusion of this sort in Nevada's future.
-
Noted for future reference. Regardless, it's in there with 68 as the primary number. Thankfully, I don't see much more exit number confusion of this sort in Nevada's future.
Pretty much, as easier way to look at it, is consider each side as a 'T' interchange where a route ends at a different cross route. Since I-580 ends there, consider US-395 ends there too (even though it doesn't). If the exit numbers are different on each approach, use the numbers that sync with the primary route exit numbering scheme in each file. :)
-
This thread was marked solved for a while but not moved to the "solved board". Movning now....
-
This thread was marked solved for a while but not moved to the "solved board". Movning now....
Actually, I just noticed it now, the '36(580) -> 68' change wasn't done in US-395's file. So, moving back for the moment.
-
Gah, thought I did that. New pull request is in.
-
Gah, thought I did that. New pull request is in.
From the look of the original PR, you did, and then when you added in the extra points, it somehow reverted in the same PR. Weird, I know.