NJ: NJ 143 Northern Endpoint

[Markkos1992]

Personally, I am having a hard time justifying myself that this route should be shown in the HB north of US 30.

While the SLDs and other sources agree with this, it still feels like that endpoint is still practically within the intersection.  (making this like MD 175 to me) (https://forum.travelmapping.net/index.php?topic=3412.0)

The difference with PA 184's dangling end is this segment marker exists.

I guess this is what happens when I go clinch a route I did not notice while planning my clinch of US 30 in NJ yesterday.

[rickmastfan67]

I'll second that the route probably should end @ US-30.

No field evidence that it goes beyond US-30.  Streetblade on US-30 shows CR-716.

[yakra]

Agreed; it's similar to MD175.
Also reminds me of several Nebraska Links/Spurs that technically extend a bit beyond the intersections, a bit of a wide spot in the road / end of pavement kinda deal. Those stayed no-build, ending at the relevant interchange / intersection.

Looks like the designation includes the bits that were newly constructed back in the day, and has stayed the same ever since, NJDOT never bothering to relinquish / download / $terminoligy that last little bit.

Looks like an oddity of One Point Per Intersection, and I can get behind changing this.
https://github.com/TravelMapping/HighwayData/pull/7990

Forgoing an updates entry here, as it's more or less a different representation of the same junction.
I'll use that as justification as writing the update text would be an awkward PitA otherwise.

If there are strong objections, I'm open to suggestion.


I'm not sold on the LWS justifying a counterexample for PA184, but that's outside the scope of this thread, and not my call to make.