NC: New I-73 segment opening 5/19

[rickmastfan67]

http://www.aaroads.com/forum/index.php?topic=18.msg2227792#msg2227792
https://apps.ncdot.gov/newsreleases/details.aspx?r=13848
http://www.greensboro.com/rockingham_now/news/danville/portion-of-i--in-guilford-opening-to-drivers/article_2270836a-3b42-11e7-9bb5-cb99c98e102c.html

This will be the NC-68 to US-220 segment.  From the pictures posted in the press release, it will be posted as I-73 from the start (unless they cover over the signs before they open it).

[oscar]

NCDOT's press release has the new segment as part of Future I-73.

[rickmastfan67]

NCDOT's press release has the new segment as part of Future I-73.

May say that, but a picture is worth 1000 words: https://www.flickr.com/photos/ncdot/34681680806/in/pool-2706067@N20/

[rickmastfan67]

I-73 are indeed posted, and not covered over or have a 'Future' banner added.

http://www.aaroads.com/forum/index.php?topic=18.msg2228524#msg2228524

[compdude787]

Friendly reminder that this new segment of I-73 still needs to be added.

[mapmikey]

I hadn't seen a map or satellite view that showed its exact routing, but I do now see that the satellite map at the Cmap editor does show it. 

However, I was also going to wait until the short segment between NC 68 and Bryan Blvd is complete (couple months...?) so that it isn't necessary to create a separate I-73 file to then turn right around and undo that...

[rickmastfan67]

I hadn't seen a map or satellite view that showed its exact routing, but I do now see that the satellite map at the Cmap editor does show it.

Well, OSM's been up-to-date for I-73 between NC-68 and US-220 for awhile.  I personally fixed it up off of the NAIP imagery there just after the highway opened.  However, I will admit the Southern NC-68 interchange and the alignment over to Bryan Blvd isn't correct (I didn't have time to clean that up).

[compdude787]

However, I was also going to wait until the short segment between NC 68 and Bryan Blvd is complete (couple months...?) so that it isn't necessary to create a separate I-73 file to then turn right around and undo that...

That makes sense.

[dfilpus]

However, I was also going to wait until the short segment between NC 68 and Bryan Blvd is complete (couple months...?) so that it isn't necessary to create a separate I-73 file to then turn right around and undo that...

The project (I-5110) to build the I-73/Airport Boulevard interchange will connect I-73 from NC-68 to Bryan Boulevard and should be done in a couple months. However, it will not complete the connection between the two segments of I-73. Bryan Boulevard between the new interchange and I-840/I-73 is not to interstate standards. The project to upgrade Bryan Boulevard and its interchange with I-840/I-73 is part of the larger project (U-2524C) to extend I-840 to US-220. This project is estimated to be complete in Mar 2018. Currently, this segment is in the data base as I-73 Future West Greensboro.
So, in a couple of months, when the NC-68/Bryan Boulevard connector is complete, the current separate I-73 segment will simply be extended, not connected to I-73 proper. If we wait until it actually connects to map the segment, it may not be until Mar 2018 (or even later) before we can.

[rickmastfan67]

So, in a couple of months, when the NC-68/Bryan Boulevard connector is complete, the current separate I-73 segment will simply be extended, not connected to I-73 proper. If we wait until it actually connects to map the segment, it may not be until Mar 2018 (or even later) before we can.

Who knows, maybe they'll get a waiver to sign that segment as I-73 proper right away once they finish the connection to NC-68.

Either way, I finished cleaning up the I-73/NC-68 southern interchange the other day in OSM thanks to the NAIP imagery.  So, points can be properly acquired from OSM now either way at least to update both US-220's and NC-68's files ahead of time.

[oscar]

In case this is new news ...

I drove the new I-73 (future?) segment today. All of the route signage in both directions (including two reassurance markers in each direction, and signs from both SB US 220 and both directions of NC 68) is as regular, not future, I-73.

[mapmikey]

I have added the full extension to US 220 to the I-73 FutWGr file, including the short Bryan Blvd replacement part that won't open for a little while longer.

I also changed NC 68:  BryBlvd to OldBryBlvd and Exit 110 for I-73 is on top of a previous waypoint.  In both cases I left legacy naming...

All associated cross routes were updated.

All have been submitted...

[Jim]

OK, so the decision is to keep it as "Future I-73"?

[mapmikey]

The posting of normal I-73 is in error.  NCDOT's Route Change request for this new segment is shown on their page as Future I-73.

[dfilpus]

The map for nc.i073futwgr is concurrent with NC-68 between exits 110 and 111. This is incorrect. I-73 Future runs west of NC-68 on separate pavement in that segment. A shaping point is needed on I-73 Future to break the concurrency.