NC: New I-73 segment opening 5/19

[dfilpus]

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.

The change to I-73 Future Madison fixed the concurrency between I-73 Future Madison and US 220. Before the fix, if you had both routes clinched, the segment between US 311/220 Bus and NC 65 was counted twice. Now, it is correctly counted once. This reduces overage mileage in NC to drop by the length of that segment.

[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.

The change to I-73 Future Madison fixed the concurrency between I-73 Future Madison and US 220. Before the fix, if you had both routes clinched, the segment between US 311/220 Bus and NC 65 was counted twice. Now, it is correctly counted once. This reduces overage mileage in NC to drop by the length of that segment.

I did in fact have both of those clinched, so that makes sense.  I was focusing in on the I-840 change as the culprit.  Thank you.

Mike

[rickmastfan67]

I would change the '107(73)' label on I-840 to '3' since it's posted going 'WB' on I-840 at least.  I mean, if it had been posted with an I-73, I would have no problems with the current label.  But since there is a 'true' I-840 exit number posted there, that should be the number to go with for the label, IMO.
https://www.aaroads.com/forum/index.php?topic=4121.msg2296193#msg2296193

[mapmikey]

adjusted the label name ('3' was an alternate name and it is now the primary) and in the queue for suubmission

[michih]

https://github.com/TravelMapping/HighwayData/commit/4d9e6ac50f2a2a993f629f76d9a237de721b5c0f#diff-a51268160175e0fc23e87843f120bf76

Marking solved