NV: Today's updates in Boulder City area

[oscar]

@oscar:

Code: [Select]

Line 2117: 2018-08-23;(USA) Nevada;I-11 Future (Hoover Dam);(NONE);Deleted route (folded into I-11)
Line 2118: 2018-08-19;(USA) Nevada;US 93 Business (Wendover);(NONE);Route Deleted
Line 2126: 2017-10-08;(USA) Nevada;I-11 Future (Henderson);(NONE);Deleted route
(NONE) is not required and ends up in a link to nowhere. It should be read:

Code: [Select]

Line 2117: 2018-08-23;(USA) Nevada;I-11 Future (Hoover Dam);;Deleted route (folded into I-11)
Line 2118: 2018-08-19;(USA) Nevada;US 93 Business (Wendover);;Route Deleted
Line 2126: 2017-10-08;(USA) Nevada;I-11 Future (Henderson);;Deleted route
These are all lines with the wrong entry in updates.csv.

"(NONE)" w/o link  is automatically inserted to the table by the front end software.

This seems to be a change of practice -- IIRC, used to be we were expected to enter (NONE) to fill in the blank field. So I did that for the recent Nevada updates items, including the deleted route in Wendover -- but not its counterpart in Utah -- which was previously added by Duke87.

I'll go back later to fix those entries, but the links to nowhere seem harmless so no rush.

[SSOWorld]

Just as harmless as the Bridge to Nowhere.

[rickmastfan67]

I honestly don't ever recall having to manually add the "(NONE)" text, as it was automatic when there was nothing detected between the ;'s in that part of the line.

[yakra]

I honestly don't ever recall having to manually add the "(NONE)" text, as it was automatic when there was nothing detected between the ;'s in that part of the line.

My memory as well. Just the semicolons, with nothing in between.

[Jim]

"(NONE)" has slipped into that field for entries from time to time but it's never supposed to have been there.  Little harm done, as others have pointed out, since it only results in a bad link.

[Jim]

So I think I might have my list updated correctly to reflect roads I'd have traveled on a 1985 ride from Las Vegas over the Hoover Dam and into Arizona, and a 2003 ride that took me up US 95 into Las Vegas then later down along the Nevada shore of Lake Mead and over the Hoover Dam.

I lost the small chunk of now former US 95 that's north of I-11.  Assuming that is not signed as anything now.

I figure I have the whole US 93 business route through Boulder City and that small chunk of Hoover Dam Road we have as Nevada 172 from the 1985 ride.

Of course this also gets me wondering if the 1985 ride give me some of what's now Nevada 582 if some or all parts of I-515 weren't there yet..  I'm fairly confident I have all of current I-515 and the chunk recently renumbered to I-11 from 2003's ride, based on a look at my 2003 RMcN.

http://travelmapping.net/user/region.php?units=miles&u=terescoj&rg=NV

[yakra]

I suggest using HistoricAerials to check on the extent of I-515 in 1985.

I wanted to post a link, but:
1. Now it appears that the "tweet" button that one had to use to manually copy the URL is gone. Man, they don't make this easy.
2. Right now, HistoricAerials is consistently doing that thing that happens sometimes where, when I try to zoom out, by either mouse or keyboard, it zooms me right the heck back in. Does anybody else have this happen?

[oscar]

I lost the small chunk of now former US 95 that's north of I-11.  Assuming that is not signed as anything now.

So did I. It's now NV 173, but apparently not yet signed. That could change.

[yakra]

NV US95BusLsV +NV596 should be unhidden as JonBlvd

[oscar]

NV US95BusLsV +NV596 should be unhidden as JonBlvd

Or eliminated, since nobody's using that point. It was probably included only because of the intersection with a numbered state route, which no longer exists. Certainly not for shaping, since the route is a straight line.

[yakra]

JonBlvd is visible in a concurrent route.
Still useful to access the shortened route farther south, IMO

[rickmastfan67]

Oscar, was just looking @ the "nv.us093trklau" file and notice some more issues with it & it's multiplex with US-95.

US-93 Trk's file is missing the following points that are in US-95's file:

Code: [Select]

LorStaRd http://www.openstreetmap.org/?lat=35.312932&lon=-114.881909
SeaAirRd http://www.openstreetmap.org/?lat=35.432911&lon=-114.910555
NV164 http://www.openstreetmap.org/?lat=35.465284&lon=-114.920125

Also noticed the following DC errors:

Code: [Select]

nv.us093trklau;x01;;;DUPLICATE_LABEL;
nv.us093trklau;x02;;;DUPLICATE_LABEL;
Maybe convert those on both US-95 & US-93 Trk's files to +x001 & +x002?  Would not only keep them labels synced between the routes, but fix the issue and the labels stay synced on the Truck route with NV-163.  This is personally why I like my system of "+X000(US95)" style labels to prevent any issues along multiplexes.  Sure, adds a few bytes, but keeps it 10x easier for multiplex fixes and avoiding duplicate shaping point labels.

===

Oh, and since we have the 'split' interchanges for I-11, shouldn't we also have the ramps from US-93 Business for Railroad Pass Casino Road too?  Wouldn't it count for like the old route of US-93 & US-95 in front of the casino too?

[oscar]

NV US95BusLsV +NV596 should be unhidden as JonBlvd

Changed in my local file.

Oscar, was just looking @ the "nv.us093trklau" file and notice some more issues with it & it's multiplex with US-95.

US-93 Trk's file is missing the following points that are in US-95's file:

Code: [Select]

LorStaRd http://www.openstreetmap.org/?lat=35.312932&lon=-114.881909
SeaAirRd http://www.openstreetmap.org/?lat=35.432911&lon=-114.910555
NV164 http://www.openstreetmap.org/?lat=35.465284&lon=-114.920125

Also noticed the following DC errors:

Code: [Select]

nv.us093trklau;x01;;;DUPLICATE_LABEL;
nv.us093trklau;x02;;;DUPLICATE_LABEL;
Maybe convert those on both US-95 & US-93 Trk's files to +x001 & +x002?  Would not only keep them labels synced between the routes, but fix the issue and the labels stay synced on the Truck route with NV-163.  This is personally why I like my system of "+X000(US95)" style labels to prevent any issues along multiplexes.  Sure, adds a few bytes, but keeps it 10x easier for multiplex fixes and avoiding duplicate shaping point labels.

===

Oh, and since we have the 'split' interchanges for I-11, shouldn't we also have the ramps from US-93 Business for Railroad Pass Casino Road too?  Wouldn't it count for like the old route of US-93 & US-95 in front of the casino too?

All these changes in my local files, except I left alone the shaping point labels on US 95. I also fixed in my local files an NMP between US 95 and NV 165.

====

I'm marking this topic as "solved". Further changes in the Boulder City area, such as for NV 172 and NV 173, can be addressed in new topics.

EDIT: Pull request submitted, but another one needed to fix first request's breaking concurrence with NV 163. My bad.

Second pull request: https://github.com/TravelMapping/HighwayData/pull/2212

[oscar]

-- The stranded part of US 95, between I-11 and the US 93 business route, is included in the extended NV 172. OSM, and some discussion on the AARoads forum, indicate it's new route NV 173 (unclear whether it's signed), rather than part of NV 172.

Per recent discussion on the AARoads forum:

-- the stranded part of US 95 is officially NV 173, not NV 172

-- unclear whether NV 172 officially extends west of I-11 exit 2, despite what OSM says

-- in any case, as of last Sunday, no NV 172 signage west of I-11 exit 2, nor is there any NV 173 signage.

My inclination is to truncate NV 172 back to where it was originally (with a corrected endpoint at I-11(2)), and rename the NV172_S point on US93BusBou as Old US95. Also, to ignore NV 173 for now as unsigned. I expect to do a field check in October (en route to a
college class reunion in the Bay Area), so all this can be revisited at that point or as other new information comes in.

I did the field check yesterday. NV 172's west end is clearly at I-11 exit 2, with no concurrence with US 93 Business. There are markers for Begin NV 172 eastbound, and End NV 172 westbound, at exit 2. So things stay where they are.

Ditto the exit numbering on the freeway south of I-215, since the anticipated re-signings haven't happened yet.

NV 173 remains unsigned.