Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Jim on May 30, 2022, 02:06:36 pm
-
@Highway63, same as you might have seen in the other similar threads, I'd like to clean up and/or mark as FPs the NMPs in Missouri. It looks like there are some quick fixes and some clear NMPs. I'd be a little hesitant to make any changes or mark FPs in KC, but I am happy to take a pass through unless you'd prefer to do it yourself.
-
@Highway63, same as you might have seen in the other similar threads, I'd like to clean up and/or mark as FPs the NMPs in Missouri. It looks like there are some quick fixes and some clear NMPs. I'd be a little hesitant to make any changes or mark FPs in KC, but I am happy to take a pass through unless you'd prefer to do it yourself.
I'm planning to make a pass through MO as well as nearby states in the next day or two. I won't change anything that seems the least bit non-obvious.
-
For tonight, I'm just marking FPs in WI, MO, IA, and IL.
I believe everything else are points that should be aligned to create graph connections. I am going to wait a bit more to make changes, since Highway63 hasn't been on the forum in a few weeks and likely hasn't seen these NMP threads. It will be at least a few more days before I am ready to make the first archive version of the graphs anyway.
-
It will be at least a few more days before I am ready to make the first archive version of the graphs anyway.
Maybe I should dust off those canonical_waypoint_name modifications I drafted back in May...
-
It will be at least a few more days before I am ready to make the first archive version of the graphs anyway.
Maybe I should dust off those canonical_waypoint_name modifications I drafted back in May...
Any improvements would be appreciated. Probably not a huge rush though as another day is going by today without me making progress on that front.
-
Looking for opinions (especially Highway63's as state maintainer) about the points at I-70 2J and 2L and how they line up, or don't, with others. It looks like US 71 is intentionally not concurrent with I-70 between those points but that it should be north of there. These should be the only remaining non-FP NMPs in Missouri after tonight's update.
My MO changes:
https://github.com/TravelMapping/HighwayData/commit/f1c0848c28a83d9fb7851cf4e61fff381b959a69
-
I think that the two remaining NMP pairs in Iowa are intentional to keep I-29 and I-80 separate. They line up on both endpoints but do not match at the 2 interchanges where they are either concurrent or on parallel roadways. I will wait to mark as FPs until I hear for sure.
-
One quick fix and one FP in Illinois:
https://github.com/TravelMapping/HighwayData/commit/082359b7dd672e80def8a1f9992871072eb13497
-
WI just a couple quick fixes: https://github.com/TravelMapping/HighwayData/commit/afe70134939a39a1b0e8784794facf6985991d50
-
Given the bad location of 2J on US 71, and the mainline is together between 10th and 11th, I'm pretty sure that US 71's points are victims of point drift and I fixed other routes without fixing it.
As for the interstates in Council Bluffs, those are intentionally NMPs following the creation of the dual, divided freeway. Technically, the inside lanes are ONLY I-80, and the outer lanes are I-29/US 6 with local I-80. I am open to the idea that they shouldn't be separate, but since one can follow 80 straight through and not be "on" I-29, I think they should be. (The necessity of double-travel to clinch is noted.)
-
Thanks. Now that I look, the Iowa ones were already listed as FPs but when points were marked as closed with a * that invalidated the FP entries.
I've lined up US 71 and I-670's points in KC that should fix that concurrency and create appropriate graph connections after the next site update.
Changes: https://github.com/TravelMapping/HighwayData/commit/3e2e4bfbbd5131a0ff350bdae522b7d1ef080977
-
I think I've got them all in these states.