MO: things I noticed while doing NMPs

[yakra]

US24/65:
There's no actual connection at WThoDr. Complicating things is that this point is in use, by one person, verruckte_dan. OK, so he still marked something beyond the US24_W/US65_S junction. The closest thing he had available to here, perhaps?

MO45 / MO92: The connecting road is a bit farther northeast now.
MO79: US36 -> I-72/36 ?

I-35 Exit 13-14 & pals:
This struck me as odd at first, but it makes sense in a historical context. With the rebuilt interchange, it could maybe use an update. It's an odd one though. I'm thinking maybe,
I-35 / MO110Han:
13 http://www.openstreetmap.org/?lat=39.216263&lon=-94.475242
14 http://www.openstreetmap.org/?lat=39.219591&lon=-94.472919
(Or I could see even putting 13 a bit farther SW, if you wanted.)
US69:
I-35(13) http://www.openstreetmap.org/?lat=39.214140&lon=-94.476121
LibPkwy http://www.openstreetmap.org/?lat=39.216256&lon=-94.474217
I-35(14) http://www.openstreetmap.org/?lat=39.219591&lon=-94.472919
We would still have "Intersecting/Concurrent Routes" at Exit 14.

MO I-44BLPac: MO100_S -> MO100_W ?

MO US66HisStL:
The concurrency with I-44BLPac between MO100_E and 1stSt is broken: I-44(257) has coords from I-44 itself, and I-44(256) is missing. I'll also ping Si on this item, as I'm not sure how much work any of us with usaush routes in our states have actually done on them (My approach has been pretty hands-off).

[Highway63]

I downloaded the historic route files and have worked with them since sometime shortly after they were made live.

[Highway63]

Pacific BL-related points: Changed/fixed.

US 24/65: Do you think I could move that point to CR516 and keep the user's intent?

MO 45/92: Hmm. I wonder how recently that was. (EDIT: Recently enough for GMSV to catch the construction.) I can move the point northeastward. It will not be a common point anymore because of that little connecting road.

MO 79: No harm in adding it and making US36 hidden.

(Doing this piecemeal.)

[yakra]

US 24/65: Do you think I could move that point to CR516 and keep the user's intent?

Maybe? HistoricAerials shows the new bridge & realignment happening between 2003 & 2007. Thomas Drive would have been an intersection on the old alignment. So maybe that could have been his intent?
verruckte_dan updates his .list by email -- maybe we could have Jim reach out to him if we care this much about it?

Edit: FWIW, verruckte_dan.list is also the only one using PA I-70 147

[Jim]

verruckte_dan emails updates about once a month.  I can send him a note to direct him to this thread, or send along an updated list, or whatever's easiest.

[yakra]

The PA discussion taking place between
http://clinched.s2.bizhat.com/clinched-ftopic2252.html
https://github.com/TravelMapping/HighwayData/pull/2210
http://forum.travelmapping.net/index.php?topic=2678

TL;DR = a gentle suggestion to change "PA I-70 75(76) 147" to "PA I-70 75(76) US30_E", which would enable us to free up 147 for other usage.

[Jim]

The PA discussion taking place between
http://clinched.s2.bizhat.com/clinched-ftopic2252.html
https://github.com/TravelMapping/HighwayData/pull/2210
http://forum.travelmapping.net/index.php?topic=2678

TL;DR = a gentle suggestion to change "PA I-70 75(76) 147" to "PA I-70 75(76) US30_E", which would enable us to free up 147 for other usage.

Emailed him.

[Jim]

From verruckte_dan:

I could change the MO US24/65 point as well.  CR 516 is actually the point where I stopped.

[Highway63]

The other solution would have been to close the point but keep it intact. WThoDr is still good/necessary as a shaping point. I'm going to hide it and add CR516.

[rickmastfan67]

The PA discussion taking place between
http://clinched.s2.bizhat.com/clinched-ftopic2252.html
https://github.com/TravelMapping/HighwayData/pull/2210
http://forum.travelmapping.net/index.php?topic=2678

TL;DR = a gentle suggestion to change "PA I-70 75(76) 147" to "PA I-70 75(76) US30_E", which would enable us to free up 147 for other usage.

Emailed him.

Did you mention to him the PA issue as well?

[Jim]

The PA discussion taking place between
http://clinched.s2.bizhat.com/clinched-ftopic2252.html
https://github.com/TravelMapping/HighwayData/pull/2210
http://forum.travelmapping.net/index.php?topic=2678

TL;DR = a gentle suggestion to change "PA I-70 75(76) 147" to "PA I-70 75(76) US30_E", which would enable us to free up 147 for other usage.

Emailed him.

Did you mention to him the PA issue as well?

Yes, and he has sent in a couple updates since.

[Highway63]

I-35 and US 69: I think those point suggestions in the first post are good. I'll add them to the recently revised files and re-send. I know the moving of the SB lanes isn't technically a de-clinch, but I'll have to check out the reconfigured interchange next time I'm down that way.

Perhaps in about a month or so it will be a good idea to do a re-check of NMPs in my states just to make sure they've all been gotten/I didn't reintroduce errors.

Also, it's kind of nuts how two-thirds of I-35's exits in Missouri are in the first 20 miles.

Batch should be sent over weekend.

[Jim]

The I-35/US 69 changes were submitted and incorporated into last night's update.  If an updates entry is warranted, could someone come up with one?  I don't understand the change well enough to do it accurately.  It's also possible no update is needed.

[yakra]

A reconfiguration of an existing interchange, but not enough IMO to be a newsworthy relocation.
YMMV. Jeff?

[Highway63]

"Recentered points for exits 13 and 14 based on new interchange configuration"?

Upon further review, I think I'm going to move #13 farther southwest given that the ramps specific to it are south of Liberty Road.