NV: NV US95SprFer

[cl94]

Yesterday evening, I drove NV 427 while keeping an eye out for any mention of the Fernley US 95 Spur, which is included in the highway browser. Not only is 95 Spur completely unsigned, I cannot find any mention of the spur route online or in the NDOT logs, where a US alternate/spur would typically take precedence over a SR. For this reason, I propose that US95SprFer be deleted in favor of NV427 and I-80BLFer.

This would not result in any reductions to mileage in the network, as the route is 100% concurrent with NV 427, which is well-signed, and the semi-signed BL 80.

[oscar]

Thanks. That sounds reasonable.

Some other stuff around Fernley that also needs fixing:

-- US50AltFer, US95AltYer, and US95SprFer are all out of synch with NV 427 and I-80BL, at the south end of US95SprFer. Just deleting US95SprFer leaves the other four routes out of synch.

-- I-80 is missing exit 50, which is also skipped by US95AltYer. GMSV indicates the new interchange was opened between 2009 and 2011. Not sure how it was missed by me and two previous NV maintainers.

UPDATE: Above changes in:

https://github.com/TravelMapping/HighwayData/pull/6001
https://github.com/TravelMapping/HighwayData/pull/6002

[Jim]

-- US50AltFer, US95AltYer, and US95SprFer are all out of synch with NV 427 and I-80BL, at the south end of US95SprFer. Just deleting
US95SprFer leaves the other four routes out of synch.

So far off that they didn't even get caught by NMP detection!  Will be nice to fix up that graph connection.