KY: KY-3174Elk/KY-80

[rickmastfan67]

Should there be a graph connection here between the two routes?

From what I can tell, since at least part of the 'interchange' between the two routes is a direct ramp connection, a graph connection would be desirable here.

Maybe even add an additional point to KY-1373 for the KY-3174 EB ramps connection to it prior to KY-80 too?

[mapcat]

I think I drafted it like this precisely because only one direction of the interchange is a direct connection, and the other makes use of that short stretch of 1373. What do you think about a single point for 80, 1373, and 3174 there?

Another alternative would be to leave 80 as-is, and add the point for the ramps to 3174 from 1373 as you suggested, but I don't know that adding that point while making a separate graph connection for 80/3174 would be consistent.

[rickmastfan67]

Looking at the brand new satellite imagery (via Bing) that shows the 'ramp' seems to be the priority movement on the EB side over 1373.  With that, I would think it's good enough to justify a graph connection with KY-80 for 3174.

As for 1373, I kinda would classify this similar to FL I-4 Exit 104.  Or even like like VA I-81 Exit 313.  I guess we could forgo a point on 1373 for the 3174 ramps, but I still think we should have the graph connection with 80 in the proper place.

[cockroachking]

There is also precedent for adding a point to KY1373 from the MD100/MD104/MD108 interchange, where MD108 has a point for MD100, similar to KY1373 getting a point for KY3174.

[mapcat]

Whatever is done here, it will be messy and won't please everyone. I made the graph connection with 80 & 3174, kept 1373 separate, and added a point on 1373 for the ramp to 3174. Perhaps that last one will help someone who otherwise wouldn't get credit for driving any of 1373. https://github.com/TravelMapping/HighwayData/pull/7008

[rickmastfan67]

Area now looks good to me.