Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on March 21, 2023, 09:01:18 pm

Title: NY: Southern State Parkway exit # issues
Post by: rickmastfan67 on March 21, 2023, 09:01:18 pm
28N -> 28 https://goo.gl/maps/1KbBCpkCnbSv2izcA
28 -> 28A https://goo.gl/maps/ReTSt1DBi9jjw9eU8
41N -> 41 https://goo.gl/maps/rGJTdp5wsZzb3RQj8
43N -> 43 https://goo.gl/maps/ENg5a2a3nXPch5q47
Title: Re: NY: Southern State Parkway exit # issues
Post by: yakra on March 22, 2023, 10:02:41 am
28 -> 28A https://goo.gl/maps/ReTSt1DBi9jjw9eU8
Done. 28 in use; kept as AltLabel.

28N -> 28 https://goo.gl/maps/1KbBCpkCnbSv2izcA
28 is in use anyway, so...
It can be debated whether https://travelmapping.net/devel/manual/wayptlabels.php#dropa applies.
If not, hey, no problem! (https://i.ebayimg.com/images/g/iVcAAOSwND9gWmIJ/s-l500.jpg)
If so, we're good on "If there is another interchange with the same number and different letters, optionally keep the A" grounds.

41N -> 41 https://goo.gl/maps/rGJTdp5wsZzb3RQj8
43N -> 43 https://goo.gl/maps/ENg5a2a3nXPch5q47
Going no-build on these per the above rationale. Keeps things consistent with 28N/28A, and keeps a smaller commit history (not that that matters much in a repo with a commit history the size of HighwayData :P).

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