Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: NickCPDX on September 03, 2017, 01:58:57 pm
-
Now that it's clear that the Boulder City Bypass will be called "I-11" by at least someone once it fully opens, when do we add it to the system?
- Now that the first (very short, and parallel to old alignment) segment has opened?
- When we have confirmation that it's signed?
- When it's approved by AASHTO?
- When it extends to US 95?
- When it's all the way around Boulder City in 2018?
Guidance appreciated.
-
Now that the first (very short, and parallel to old alignment) segment has opened?
I'm not sure there's two waypoints to be got there without stretching it - leave off unless signed.
When we have confirmation that it's signed?
If signed, then add.
When it's approved by AASHTO?
Pretty sure it is. Certainly AASHTO didn't bat an eyelid at the existence of I-11 when the applications for US93 and US95 changes routing it onto new I-11 were approved by them in the Spring.
When it extends to US 95?
At least then there would be a route with two points!
When it's all the way around Boulder City in 2018?
That might be a bit after the fact.
-
If signed, then add.
It wasn't signed (other than some "Future I-11" signs) in either state along US 93 last month.
-
When we have confirmation that it's signed?
This one.
-
Well, looks like we have some clarity - signs are on order for I-11 from the I-215/NV 564 interchange in Henderson to the new alignment. I-515 has been decommissioned in this stretch.
https://lasvegassun.com/news/2017/sep/09/more-interstate-11-signs-on-the-way/
-
Well, looks like we have some clarity - signs are on order for I-11 from the I-215/NV 564 interchange in Henderson to the new alignment. I-515 has been decommissioned in this stretch.
https://lasvegassun.com/news/2017/sep/09/more-interstate-11-signs-on-the-way/
I'd still wait till the signs are in the field, as it still could be another 2 months till that might happen.
-
I will leave this to everyone else to make a decision, but I'll point out that we seem to have inherited from CHM some usai-specific rules, by which we include routes that are legally interstates even if not signed (yet, in this case) as such. This includes hidden designations.
I did not merge in the pull requests related to this pending some further discussion and consensus here, and since the csv files did not appear to be updated.
-
I will leave this to everyone else to make a decision, but I'll point out that we seem to have inherited from CHM some usai-specific rules, by which we include routes that are legally interstates even if not signed (yet, in this case) as such. This includes hidden designations.
Well, I wanted to make I-69's TN file in the Memphis area official after the AASHTO approval, but I was overruled into making it as a 'Future' route.
-
we seem to have inherited from CHM some usai-specific rules, by which we include routes that are legally interstates even if not signed (yet, in this case) as such. This includes hidden designations.
Includes hidden designations.
Limited to hidden designations?
It may be, from what I remember... For designations that aren't intended to be hidden, seems we wait for signage, etc. That's the route I've been taking with TX I-69*.
I don't have any skin in this particular game, other than wanting that things be done properly for the project, however that may be.
-
There is a sign now. see AARoads (http://www.aaroads.com/forum/index.php?topic=21080.msg2259041)
-
So do we have some agreement that the changes in the open pull requests 1596-1599 can be merged?
-
Update - there is at least I-11 shield posted now on the Nevada segment.
-
Also if we're going to merge those in, the usaif and usai csv files need updating too.
-
I see this was pulled in.
However, since it isn't opened yet to US-95 (between exits 14 & 15), I don't think that part should be shown yet. Plus, somebody has it marked as 'clinched' already which shouldn't be even possible.
If we aren't going to remove that section, US-93 & US-95's files need be updated to have the 'new' location for '15' (which should really be '15B'). Also, US-95 should have the point for exit 14 added as well.
As for I-11's file itself, we'll need to add '15A' for the Railroad Pass Casino Road interchange. Why you may ask? Well, it's simple. '15A' is a complete interchange, while '15B' isn't. '15A' fills in the missing movements from '15B', plus we have US-93/95 leaving I-11 (well, for now) @ '15A'. (on a side note, US-93 'Business' & US-95 would also need the companion part too for Railroad Pass Casino Road.
-
Not that I have any skin in this -- haven't been south of the Vegas airport in NV. But I am curious about the exit numbering on I-11, which appears to change abruptly from mileage-from-AZ/NV to what I presume is mileage from a putative south end of proposed I-515. Is Nevada planning to do anything about that?
-
I see this was pulled in.
However, since it isn't opened yet to US-95 (between exits 14 & 15), I don't think that part should be shown yet. Plus, somebody has it marked as 'clinched' already which shouldn't be even possible.
If we aren't going to remove that section, US-93 & US-95's files need be updated to have the 'new' location for '15' (which should really be '15B'). Also, US-95 should have the point for exit 14 added as well.
As for I-11's file itself, we'll need to add '15A' for the Railroad Pass Casino Road interchange. Why you may ask? Well, it's simple. '15A' is a complete interchange, while '15B' isn't. '15A' fills in the missing movements from '15B', plus we have US-93/95 leaving I-11 (well, for now) @ '15A'. (on a side note, US-93 'Business' & US-95 would also need the companion part too for Railroad Pass Casino Road.
Bump.
The 11/93/95 concurrency is still broken.
Shaping point +X277934 on I-11 is not on US93/95. Not needed for shaping; suggest removing.
Routes don't line up @ Exit 15; 93/95 still have their coords placed on the old alignment. I don't have a strong preference between a "middle of the central ramp triangle" or a 15A/15B solution as rickmastfan67 suggests, other than that in the latter case I would scoot 15B a bit farther south on "where the centerlines would cross if it were an at-grade intersection with the same shape" grounds.
+X988841 on I-11 is also unneeded.
I-95: Does this keep its existing location, or was it (will it be?) moved onto I-11?
I-93: Yowza, exit numbers here are a mess! Long story short, 56(US95) & pals should all be US95(56) & pals.
-
I'm going to hold off on doing any more updates until the US 95 connection opens.
- By then, hopefully, we will have a better indication of numbering on the segment from I-215 to US 95
- I know NDOT put a contract to re-sign I-515 to I-11 from 215 to Railroad Pass, but it's not showing as I-11 in the list of State Maintained Highways for 2018. This doesn't surprise me terribly – NDOT's Carson City folks don't always keep tabs on what's going on in Southern Nevada.
I see this was pulled in.
However, since it isn't opened yet to US-95 (between exits 14 & 15), I don't think that part should be shown yet. Plus, somebody has it marked as 'clinched' already which shouldn't be even possible.
If we aren't going to remove that section, US-93 & US-95's files need be updated to have the 'new' location for '15' (which should really be '15B'). Also, US-95 should have the point for exit 14 added as well.
As for I-11's file itself, we'll need to add '15A' for the Railroad Pass Casino Road interchange. Why you may ask? Well, it's simple. '15A' is a complete interchange, while '15B' isn't. '15A' fills in the missing movements from '15B', plus we have US-93/95 leaving I-11 (well, for now) @ '15A'. (on a side note, US-93 'Business' & US-95 would also need the companion part too for Railroad Pass Casino Road.
Bump.
The 11/93/95 concurrency is still broken.
Shaping point +X277934 on I-11 is not on US93/95. Not needed for shaping; suggest removing.
Routes don't line up @ Exit 15; 93/95 still have their coords placed on the old alignment. I don't have a strong preference between a "middle of the central ramp triangle" or a 15A/15B solution as rickmastfan67 suggests, other than that in the latter case I would scoot 15B a bit farther south on "where the centerlines would cross if it were an at-grade intersection with the same shape" grounds.
+X988841 on I-11 is also unneeded.
I-95: Does this keep its existing location, or was it (will it be?) moved onto I-11?
I-93: Yowza, exit numbers here are a mess! Long story short, 56(US95) & pals should all be US95(56) & pals.
-
It doesn't matter to me so much if most of the updates wait until openings/signings/etc., but I'd like to see the broken concurrency fix happen at first opportunity.
-
Nick, while you're at it, we still have a broken concurrency (and other issues) (http://tm.teresco.org/forum/index.php?topic=2159.msg8218#msg8218) at the south end of I-580 in Carson City.
-
Follow up thread: http://forum.travelmapping.net/index.php?topic=2581.0