*Sigh* Not improperly, really.
The granularity of route traces in the project is pretty low-res. This is known, understood & accepted, and we don't pretend it's anything but.
There's nothing in the manual about keeping route traces away from one another, or shaping routes so the traces don't cross over where they don't in the field; it's just something that people have slowly started to latch onto over the last few years.
While it can help tell routes apart in "busy" urban areas where there are a lot of polylines, NY7 & I-88 are pretty isolated here, and looking at the map, there's no difficulty in telling which route is what.
Minor cases like this, I just may not give much consideration in the future.
That all said, since a fix for this involves edits that are minor improvements in their own right, I'll do it.
• I-88: Delete one shaping point & move another, staying in tolerance. Fewer points overall FTW.
• NY7:
Replace +X590312 with BouRdhttps://github.com/TravelMapping/HighwayData/pull/6861