I can see maybe changing
US30... the I-295 crossing is just about exactly centrally located in the interchange footprint on that road. And it's more intuitive to have an
I-295 point there, rather than at a separate at-grade jct that would otherwise be
CopRd.
I-295?29B wouldn't be our label for Copley Rd, as the 29B ramp connects only to US30, same as 29A.
But regardless... Extra points?
Is this complex a case of...
• a single interchange
• double half interchanges, or
• two interchanges?
The way the ramps of the one half fill out the missing moves of the other, it falls more into the "one interchange" camp than two. IMO it's a "misbehaving diamond" variant centered at Copley Rd with some extra/redundant moves thrown in.
If we consider it to be
double half interchanges, it doesn't pass the "clear gap of at least 0.5 mi/0.8 km separates the two halves, or each half connects to a different highway that we are also mapping" test. Ergo it's a 1PPI situation; "
use one central point and treat both halves as a single, full interchange." Falls into the
exceptions to positioning at centerline crossings and
unusual shapes categories, IMO.
One central point midway between the westernmost & easternmost gores neatly corresponds to midway between the two centerlines we're serving, so w0ot. And it's a good location to indicate that the point is intended to serve the whole interchange complex, rather than just half of it.
While I do see some room for improvement, sadly we still don't quite make it to a graph connection here.
https://github.com/TravelMapping/HighwayData/pull/4196