NM: US 60, US 380, and Other Point Concerns

[Markkos1992]

I-25/US 85:  I would probably add a shaping point between 147 and 150 to put the route clearly east of I-25BL (Socorro).

US 60:  FR81A>-OldNM32.

US 70: I-25(6)>-I-25.

US 285: McGafSt>-McGSt.

US 380:
Normal Point Concerns:
1.    MathRd>-WalRA (Waldrop Rest Area)?
2.   NM265>-CR106?
3.   Should CRC008 between CRC011 and YardRd have a visible point?
4.   Was there a relocation at some point west of CRA008?
5.   Should WSMR3506 be slightly relocated?
Uncertain CR Labels:
1.   CR162A>-BlaRd?
2.   CR65>-CR248. Meaning QueRd should be?
3.   CR51>-PonRd?
4.   CR1 (affects US 70)
5.   CRC011>-IndDivRd?

NM 1:  Should a point be added here?

NM 254:  WhiMillRd>-WhiMillRd_S or BraRd_E

NM 256:  Should McGSt be added?

[oscar]

I-25/US 85:  I would probably add a shaping point between 147 and 150 to put the route clearly east of I-25BL (Socorro).

Sure.

US 380:
Normal Point Concerns:
2.   NM265>-CR106?

NM265 point will be deleted rather than renamed. NMDOT's latest online mapping shows the supposed NM 265 is not a primary state route. Not in use, really close to NM254 point, and even if it's a signed county route, it's not a required waypoint.

3.   Should CRC008 between CRC011 and YardRd have a visible point?

I'll replace the existing shaping point with one for Tucson Mountain Rd. (which might be CRC008, but GMSV shows no confirming signage).

4.   Was there a relocation at some point west of CRA008?

Maybe, but I have no time to confirm that there was a real alignment change rather than just an old mapping error (which affects whether we need an Updates entry). Can you research this, as well as the approximate date (Microsloth Streets and Trips 2013 indicates any change happened before 2013)?  Otherwise, I'll just adjust the waypoints to conform to what OSM shows as the current routing, but no Updates entry.

The other items seem to be small beer (mostly unimportant relabels).

[Markkos1992]

I looked at Historic Aerials and the only clue of a realignment would be looking at the US 380 imagery.  I am fine considering it a mapping error.

Anyway, I used Acrevalue to check labels for US 380 in TX leading me to practically nothing, so I thought that would be the case in NM.   

[oscar]

Addressed in part of https://github.com/TravelMapping/HighwayData/pull/5392

Marking this topic solved.

[Markkos1992]

I am guessing then that you had no plans to make changes to US 60, US 70, and US 285.  The NM 254 and NM 256 ones are more debatable.

I am fine with US 380, I-25/US 85, and NM 1 (all three included in the pull request).

[Markkos1992]

I guess I was waiting on clarification from you oscar on how to proceed before throwing this in the solved pile.

[oscar]

I guess I was waiting on clarification from you oscar on how to proceed before throwing this in the solved pile.

I had marked the topic solved, and am doing so again. I made the changes I thought were worthwhile, and even made unimportant "small beer" label fixes (not necessarily the ones you suggested) to the US 380 file since I needed to make more substantive changes to that file anyway.

As a general rule, I think it's usually not a productive effort to scour old systems for arguably incorrect labels. Usually, nobody is using those waypoints anyway, and I'm really skeptical that any label imperfections hinder users from finding the points they need in the HB and plugging them into their list files. Better to direct perfectionist inclinations (which I share to some extent) to new systems in need of peer review.

[Markkos1992]

Fair enough.  I still think that the US 70 one (that could eventually become an EXTRANEOUS LABEL FP based on yakra's side projects) is still worth doing since I-25 is only intersected once.