Highway Data Discussion > Solved Highway data updates

NV: US-95 tweaks

(1/1)

rickmastfan67:
76A -> 76C
NEW -> ElkRd (HOV only exit, between exits 91 & 93)
NV157 -> 96 (plus it needs to be recentered for both routes due to it being converted to an interchange)
136 -> MerHwy (can't find any signage supporting a posted exit number, current or historical in StreetView)

Areas that need shaping point(s) due to going well out of tolerance between the 2 listed points:
BeaWashRd & FleLisRd
RamSt & SilPeakRd

Shaping points that can become usable points:
+X25 -> YelRd? Seems to be called that due to Google/OSM.

Other stuff:
MilCutRd -> Maybe swap it with Gabbs Pole Line Road to the east as it's a real road?  Would also effect US-6.

oscar:
Most US 95 and related changes in https://github.com/TravelMapping/HighwayData/pull/6353

I'll follow up tomorrow with a conforming change to NV 157, to re-synch it with US 95, that somehow was left out of the PR.

rickmastfan67:

--- Quote from: oscar on February 01, 2023, 04:00:32 pm ---I'll follow up tomorrow with a conforming change to NV 157, to re-synch it with US 95, that somehow was left out of the PR.

--- End quote ---

The change didn't make it to US-95's file either.  Only the label on US-95 was changed.  It's location stayed the same as it was previously.

oscar:

--- Quote from: rickmastfan67 on February 01, 2023, 08:21:41 pm ---
--- Quote from: oscar on February 01, 2023, 04:00:32 pm ---I'll follow up tomorrow with a conforming change to NV 157, to re-synch it with US 95, that somehow was left out of the PR.

--- End quote ---

The change didn't make it to US-95's file either.  Only the label on US-95 was changed.  It's location stayed the same as it was previously.

--- End quote ---

Grrr. Before I fix the US 95/NV 157 junction point, I'll need to look for screwups elsewhere in the PR.

Navigation

[0] Message Index