Recent Posts11
Updates to Highway Data / Re: NM: I-40 issues
« Last post by oscar on Yesterday at 11:29:52 am »167 -> split into 167/167A. This will allow NM-556 to have a proper location for this interchange. Update the point in NM-556 too.
Rather than splitting the point, into two points only 0.2 mile apart, I would just move I-40(167) to the NM 556 underpass, and rely on 1PPI to have the relocated point cover the entire interchange. This also leaves NM 333 and NM US66HisAlb (per your note on NM 333) unchanged.
https://github.com/TravelMapping/HighwayData/pull/8649
https://github.com/TravelMapping/HighwayData/pull/8650
Other changes to I-40 later, to avoid confusion from my trying to follow two baseball playoff games at once.
I can sorta live with a 1PPI here on I-40, but I still think these still work as separate interchanges. With the one that connects to NM-556, you have 2 directions (originally was only an EB off-ramp, but WB on-ramp added in 1982), but with NM-333 there, you have 3 of the 4 movements.
I was drawing on our practice re: half-diamond freeway interchanges, where we don't treat the halves as separate interchanges (with a fake exit number for one of the halves) unless they are at least 0.5 miles apart.
FWIW (given the highway signage quality in NM, worst in the lower 48), both the exit ramp from EB I-40 directly to NM 556, and the ramp from WB I-40 via the trumpet, are signed as parts of exit 167.
===
Pull request addressing the I-40 issues not relating to exit 167:
https://github.com/TravelMapping/HighwayData/pull/8653/