Not sure what you mean by "connecting to" here. Based on your having mentioned a graph connection, I interpreted that as using the same coords as existing NS NS1 CobRd. That, I can't get behind; I won't put a waypoint off of the road itself just to get a graph connection.
That makes sense. It is pretty far away from the bypass. Certainly far enough away that it doesn't demand a graph connection (see below).
and then continuing northward to join NS 101 at 1F. This sign makes it pretty clear that Cobequid Rd acts as the NS 1 exit from the Bypass.
I wanna leave this pretty much as-is, with one point for 1F/1K that 1PPI's all three routes together.
WRT a CobRd point on the bypass, I can see some merit to that. I may have just considered it 1PPI when first drafting the route, but OTOH, adding a point at the offramp could pull the bypass away from the 101/102 interchange in mapview.
The 1PPI seems adequate for travels in a NW-to-SE direction, but I mostly paid attention to the SE-to-NW movements, which still seem too complicated for one point IMO. If there's a CobRd (or NS 1) point on the bypass, adding it at the gore point would be appropriate.
On another note, should I reverse point order and make BedByp E-W? It functions as kind of an extension/bypass of the ends of two E-W corridors, NS101/1 & NS7.
That would be more consistent, but I don't have a strong opinion.
(On that note, should it maybe be ON ONQEW for consistency?)
https://travelmapping.net/hb/showroute.php?units=miles&u=mapcat&r=on.onqew
