Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on December 28, 2020, 08:32:48 pm

Title: NJ: US 322 Minor Point Concerns
Post by: Markkos1992 on December 28, 2020, 08:32:48 pm

1.   BoweBlvd should technically be longer.
2.   SLeiAve should just be LeiAve.

Title: Re: NJ: US 322 Minor Point Concerns
Post by: yakra on December 29, 2020, 01:17:33 am

https://github.com/TravelMapping/HighwayData/pull/4441

Title: Re: NJ: US 322 Minor Point Concerns
Post by: Markkos1992 on December 29, 2020, 10:40:25 am

I did want to note that I went with a "no-build" take on CR536.  My understanding based on Wikipedia is that CR536 is concurrent with US 322 west to the PA State Line from CR536_W, but I think that making changes here on that alone is more trouble than it is worth for a county route.

Title: Re: NJ: US 322 Minor Point Concerns
Post by: yakra on December 29, 2020, 01:00:29 pm

Oh man, these are fun. :P
If this were an otherwise identical waypoints (https://travelmapping.net/devel/manual/wayptlabels.php#disambiguation) situation, CR536_W and CR536_E would check out (https://travelmapping.net/devel/manual/wayptlabels.php#underscore). But since there's a multiplex (https://travelmapping.net/devel/manual/wayptlabels.php#multiplex) involved, the "otherwise" bit doesn't kick in.
The multiplex, followed by a regular old crossing, give us CR536_E and CR536. Luckily, only CR536_W is in use, leaving us free to move CR536_E on top of it.