Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: cockroachking on December 09, 2023, 09:50:08 pm
-
The following exits are split into two points, and as far as I can tell, should be combined per 1PPI:
89 & 89A (0.4 mi apart)
97 & 97A (0.37 mi apart)
110 & 110A (0.37 mi apart)
In all three cases, it seems to me that the non-suffixed waypoint should be centered on the overpass and the suffixed label removed (none of which are in use).
Also, an incorrect exit number on both routes:
88 > 87A (https://www.google.com/maps/@41.9663843,-75.2553422,3a,20.6y,309.83h,92.56t/data=!3m6!1e1!3m4!1sE3m6J_6zAZMB7UemcjZrGw!2e0!7i16384!8i8192!5m1!1e1)
And on NY17Bin only:
SteMineRd > CR72 (https://www.google.com/maps/@41.1462406,-74.1897219,3a,15y,0.34h,91.43t/data=!3m6!1e1!3m4!1s4DNq9yv0NVK-bukSTw4Vmw!2e0!7i16384!8i8192!5m1!1e1)
-
Also 106 should be recentered as well, as it was reconfigured sometime between July '09 & Nov '16. Point is where the 'old' overpass was located.
-
The following exits are split into two points, and as far as I can tell, should be combined per 1PPI:
89 & 89A (0.4 mi apart)
97 & 97A (0.37 mi apart)
110 & 110A (0.37 mi apart)
In all three cases, it seems to me that the non-suffixed waypoint should be centered on the overpass and the suffixed label removed (none of which are in use).
All combined. Along with a few others not listed per
Some interchanges have unusual shapes or are stretched-out versions of normal interchanges. Use your best judgment.
(Bold in original; italics added.)
This led to also deleting 97B, and keeping 97 in place serving a central location for the interchange as a whole, rather than on the underpass.
Also, an incorrect exit number on both routes:
88 > 87A (https://www.google.com/maps/@41.9663843,-75.2553422,3a,20.6y,309.83h,92.56t/data=!3m6!1e1!3m4!1sE3m6J_6zAZMB7UemcjZrGw!2e0!7i16384!8i8192!5m1!1e1)
Weird. I got curious & checked HistoricAerials for anything that may have historically been an Exit 88, that got closed. Didn't find anything.
Changed.
And on NY17Bin only:
SteMineRd > CR72 (https://www.google.com/maps/@41.1462406,-74.1897219,3a,15y,0.34h,91.43t/data=!3m6!1e1!3m4!1s4DNq9yv0NVK-bukSTw4Vmw!2e0!7i16384!8i8192!5m1!1e1)
Changed.
Also 106 should be recentered as well, as it was reconfigured sometime between July '09 & Nov '16. Point is where the 'old' overpass was located.
It's a bit east of it. ;) Either that was Early Google Imprecision, or a deliberate Misbehaving Parclo placement, which it can continue to be now.
https://github.com/TravelMapping/HighwayData/pull/7157
-
Also 106 should be recentered as well, as it was reconfigured sometime between July '09 & Nov '16. Point is where the 'old' overpass was located.
It's a bit east of it. ;) Either that was Early Google Imprecision, or a deliberate Misbehaving Parclo placement, which it can continue to be now.
No, was in the 'correct' place for the previous overpass (well, a tic to the east, but close enough, lol). There wasn't an EB offramp before the June '09 imagery there (https://maps.app.goo.gl/qqDytc7Cz4mqU2by5). When they replaced the overpass, they added that missing movement. Could say 106 acts the same way as 109 (which is centered on the overpass).