NC: New I-73 segment opening 5/19

[mapmikey]

shaping point added and submitted

[rickmastfan67]

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.

Well, if they put up I-73 shields on the Bryan Blvd part once it's reopened, I'd say we should make it a 'proper' interstate no matter what IMO.

[rickmastfan67]

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.

Well, if they put up I-73 shields on the Bryan Blvd part once it's reopened, I'd say we should make it a 'proper' interstate no matter what IMO.

I was right, the Bryan Blvd part IS posted as a full Interstate now after it opened.  So, I propose to promote it all to a full Interstate, including the I-840 part.  Also, I-840 (West) needs to be promoted as well.

http://www.malmeroads.net/i7374nc/i73seg4.html

[dfilpus]

Signage for I-73 from I-40 to Bryan Boulevard has been changed from Future to Full Interstate signage.
Overhead signs, exit and mile numbers are not yet changed.
The END I-73 sign on the ramp from I-73/US 421 to I 73 has been changed to a NORTH I-73 sign.
I-73 shields have been removed from the FUTURE signs.
I-73 reassurance signs have been erected, similar to the I-87 signs in Raleigh.
Temporary advisory signs direct I-73 traffic to Bryan Boulevard West.
There is now no FUTURE I-73 signage until north of the US 220 merge north of Summerville.

I-840 is still signed FUTURE.

[mapmikey]

Unless anyone objects, I can make everything actual I-73 when the next segment opens soon...

[rickmastfan67]

2(840) -> 104
https://www.aaroads.com/forum/index.php?topic=4121.msg2296193#msg2296193

Assuming that on I-840 'Future' (which I'm sure will become a full Interstate finally once it's open to US-220), that the following points will also need to be updated.
1 -> 103(73)
2 -> 104(73)

[mapmikey]

I have submitted the extension of I-73 up US 220 to NC 68 and eliminated I-73 Fut W Greensboro (alt name added to I-73).

[rickmastfan67]

2(840) -> 104
https://www.aaroads.com/forum/index.php?topic=4121.msg2296193#msg2296193

Assuming that on I-840 'Future' (which I'm sure will become a full Interstate finally once it's open to US-220), that the following points will also need to be updated.
1 -> 103(73)
2 -> 104(73)

This still needs to be addressed on I-73's file, as the '840' point is still labeled as such.  Also I-840's file needs the fixes too.

Also, I would recommend the following exits to be re-centered, as they are off the center of the interchange (mainly due to guess work when they were originally added into OSM, but have since been corrected when newer imagery came out showing the correct location of the center point of the interchanges).

116 (NC-150)
123 (NC-68/US-220)

[mapmikey]

Made all these changes, plus went ahead and extended I-840 to US 220 as its opening is supposed to be April 14.

In the queue for submittal...

[oscar]

A post on AARoads, and a linked news article, indicate that:

-- the opening will be delayed until at least April 23 (darn, I was hoping to clinch the new segment on my way back from Florida next week)

-- the new segment will be signed as regular, not future, I-840.

[dfilpus]

The waypoint for the southern terminus of I-73 Future Madison does not correspond with the waypoint in the routes NC 68, US 220 and I-73, which breaks the concurrency between US 220 and I-73 Future Madison.

[oscar]

Followup on what the HB has as I-840FutWGr:

I drove it today (coming from I-73 NB north of I-85), including the new segment between Bryan Blvd. and US 220. The new segment appears to be consistently signed as regular, rather than future, I-840, including on overhead signs, freestanding reassurance signs, and milemarkers. The older segment, from I-40 to Bryan Blvd. (concurrent with I-73), is less clear -- I saw a Future I-840 sign on that segment NB (there was greenout indicating the sign once had Future I-73 on it as well). But on WB Bryan Blvd. approaching I-73/I-840, an overhead shows not only the new freeway north of Bryan Blvd. to US 220 as regular I-840, but I-73 south of Bryan Blvd. is also regular I-840.

I drove the new segment in both directions, but the old segment SB only to exit 102 where I turned back to leave Greensboro on US 220. Also, I didn't drive Bryan Blvd/I-73 EB past the airport, so I don't know how I-840 is signed from that approach.

No photos. alas, due to inconveniently-timed rain showers.

[mapmikey]

I have corrected the I-73 future madison issue and went ahead and changed I-840futgre to just I-840.

In the queue for submisison

[mikeandkristie]

This may seem like an odd question, but is there anything involved with the recent changes you made to I-73 Future Madison and I-840 Future --> I-840 around Greensboro that would cause someone's numbers to drop?  Possibly some road mileage was being double counted and it no longer is.

I noticed this after checking my total miles yesterday.  I was expecting about a half mile jump after the fix to get the NC126/NC181 intersection corrected since I already had a line in for this waypoint so it would see it when the update went through.  Instead, I saw a 5-6 mile drop.  I usually keep a previous version of our log file so I can compare them after submitting updates.  My last submission was on 4/29.  And I compared it against the new log file.

Overall, my miles dropped by 5.69.  I see and extra 0.59 for NC181 and 0.02 for the change in I-73Fut (Madison).  On I-840, we've been on the part that overlaps with I-73.  That's 3.61 out of 6.76 miles and I do see it move from Interstate Future to regular Interstate and the totals change accordingly.  The Interstate miles driven doesn't change as they were already covered by I-73.  Total Interstate miles increased by 17.82 which includes the new 3.15 miles of I-840 and then the rest is I-269.  Predictably, my Interstate Future mileage changed by 3.59 (3.61 driven minus the 0.02 for Madison) and 6.74 (6.76 total minus 0.02 for Madison).  But, the future I-840 miles are also I-73 miles, so I shouldn't have dropped any here.  I haven't found anything yet that would explain my overall mileage drop. 

Mike

Note:  If the file doesn't show up that I'm trying to attach which shows a file comparison between the relevant lines, I will just paste in the text.

[mikeandkristie]

OK, my image attached, but I had to shrink it enough to get it under what I saw was the 128KB limit that it isn't legible anymore.  So, here are the relevant lines from my log file. 

Also, I tried posting the full size file.  But, it wouldn't accept the modest 522 KB file.  And afterwards, the Post button wouldn't work even after hitting Clear Attachments.

Relevant Before Lines

Log file created at: 2018-04-29 20:59:27.790373
Waypoint label(s) not found in line: NC NC181 NC126 US64Bus
Processed 1617 good lines marking 21123 segments traveled.
Clinched Highway Statistics
Overall in active systems: 36757.28 of 792125.85 mi (4.6%)
Overall in active+preview systems: 38331.05 of 1107233.14 mi (3.5%)
Overall by region: (each line reports active only then active+preview)
MS: 392.92 of 3296.81 mi (11.9%), 404.29 of 3619.03 mi (11.2%)
NC: 5375.15 of 14945.13 mi (36.0%), 5596.95 of 15180.82 mi (36.9%)
VA: 3573.48 of 10133.82 mi (35.3%), 3906.23 of 10471.87 mi (37.3%)
System usai (active) overall: 16264.24 of 48863.73 mi (33.3%)
System usai by region:
  MS: 288.21 of 815.28 mi (35.4%)
  NC: 1271.79 of 1307.57 mi (97.3%)
I-840: 77.75 of 77.75 mi (100.0%)
 (TN I-840 only)
I-895 (Maryland): 8.75 of 14.42 mi (60.7%)
 (MD I-895 only)
System usai connected routes traveled: 136 of 355 (38.3%), clinched: 50 of 355 (14.1%).
System usaif (active) overall: 446.95 of 875.94 mi (51.0%)
System usaif by region:
  NC: 140.04 of 202.56 mi (69.1%)
I-73Fut (Madison, NC): 18.27 of 18.27 mi (100.0%)
 (NC I-73FutMad only)
I-840Fut (West Greensboro, NC): 3.61 of 6.76 mi (53.4%)
 (NC I-840FutWGr only)
I-840Fut (East Greensboro, NC): 7.33 of 7.33 mi (100.0%)
 (NC I-840FutEGr only)
System usaif connected routes traveled: 21 of 38 (55.3%), clinched: 14 of 38 (36.8%).
System usanc (active) overall: 1734.10 of 8739.99 mi (19.8%)
NC181: 0.90 of 33.54 mi (2.7%)
 (NC NC181 only)

Relevant After Lines

Log file created at: 2018-05-06 23:00:36.677021
Note: deprecated route name I-840FutWGr -> canonical name I-840 in line NC I-840FutWGr 103(73) 107(73)
Processed 1618 good lines marking 21124 segments traveled.
Clinched Highway Statistics
Overall in active systems: 36751.59 of 792429.49 mi (4.6%)
Overall in active+preview systems: 38325.36 of 1116077.54 mi (3.4%)
Overall by region: (each line reports active only then active+preview)
MS: 392.92 of 3311.49 mi (11.9%), 404.29 of 3633.71 mi (11.1%)
NC: 5369.46 of 14938.86 mi (35.9%), 5591.26 of 15174.55 mi (36.8%)
VA: 3573.48 of 10132.73 mi (35.3%), 3906.23 of 10470.78 mi (37.3%)
System usai (active) overall: 16264.24 of 48881.55 mi (33.3%)
System usai by region:
  MS: 288.21 of 829.96 mi (34.7%)
  NC: 1271.79 of 1310.72 mi (97.0%)
I-840 (Tennessee): 77.75 of 77.75 mi (100.0%)
 (TN I-840 only)
I-840 (North Carolina): 3.61 of 6.76 mi (53.4%)
 (NC I-840 only)
I-895 (Maryland): 8.75 of 14.42 mi (60.7%)
 (MD I-895 only)
System usai connected routes traveled: 137 of 356 (38.5%), clinched: 50 of 356 (14.0%).
System usaif (active) overall: 443.36 of 869.20 mi (51.0%)
System usaif by region:
  NC: 136.45 of 195.82 mi (69.7%)
I-73Fut (Madison, NC): 18.29 of 18.29 mi (100.0%)
 (NC I-73FutMad only)
I-840Fut (East Greensboro, NC): 7.33 of 7.33 mi (100.0%)
 (NC I-840FutEGr only)
System usaif connected routes traveled: 20 of 37 (54.1%), clinched: 14 of 37 (37.8%).
System usanc (active) overall: 1734.69 of 8740.01 mi (19.8%)
NC181: 1.49 of 33.56 mi (4.5%)
 (NC NC181 only)