Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on October 24, 2024, 11:03:16 pm
-
Should we clean up this area a tic?
On I-95, 'Exit 22' is only for Midland Ave (https://maps.app.goo.gl/F2Co9LgdCJai5Rvy5). And '21' has been for I-287 (https://maps.app.goo.gl/5fN4iFFVWjub2CfaA).
So, on I-95, I recommend shifting 22 to the Midland Ave overpass, and creating a new '21A' for I-287's endpoint.
==
On I-287, I recommend adding a 'new' 12 point for the ramps to/from SB I-95 (https://maps.app.goo.gl/WrX48E7kahHF5NhT7) just beyond Exit 11 (US-1). The only reason I'm suggesting this, is because of the current '21' point on I-95 which is what these ramps would connect to. If we're gonna have a '20' & '21' right beside either other on I-95, why can't we have the same thing for '11' & '12' on I-287?
-
On I-95, 'Exit 22' is only for Midland Ave (https://maps.app.goo.gl/F2Co9LgdCJai5Rvy5). And '21' has been for I-287 (https://maps.app.goo.gl/5fN4iFFVWjub2CfaA).
So, on I-95, I recommend shifting 22 to the Midland Ave overpass, and creating a new '21A' for I-287's endpoint.
Nah. The Midland Ave interchange is wholly within the I-187 interchange footprint except for the EB offramp. 1PPI.
On I-287, I recommend adding a 'new' 12 point for the ramps to/from SB I-95 (https://maps.app.goo.gl/WrX48E7kahHF5NhT7) just beyond Exit 11 (US-1). The only reason I'm suggesting this, is because of the current '21' point on I-95 which is what these ramps would connect to. If we're gonna have a '20' & '21' right beside either other on I-95, why can't we have the same thing for '11' & '12' on I-287?
12 is an AltLabel for the I-95 point. Moving it would break 49 .list files, the majority of these being 100% clinches.
-
On I-287, I recommend adding a 'new' 12 point for the ramps to/from SB I-95 (https://maps.app.goo.gl/WrX48E7kahHF5NhT7) just beyond Exit 11 (US-1). The only reason I'm suggesting this, is because of the current '21' point on I-95 which is what these ramps would connect to. If we're gonna have a '20' & '21' right beside either other on I-95, why can't we have the same thing for '11' & '12' on I-287?
12 is an AltLabel for the I-95 point. Moving it would break 49 .list files, the majority of these being 100% clinches.
Then go with 12A for those other ramps on I-287 to match up with I-95's 21?
Otherwise, wouldn't 20 & 21 be a 1PPI thing on I-95 then?
-
When is it 1 interchange; when is it 2? Fnord. (https://www.youtube.com/watch?v=rgLJrvoX_qo)
This doesn't meet the same "within the footprint" as the eastern half; either way just not worth the bother of introducing another blob tree & commit to the repo.
-
If anything I would 86 the current "21" point on I-95 as 1PPI.
Or well if doing it from scratch I'd have what's currently 22 as 21 since that's the exit number for I-287 which is the primary junctioning route there, but can't do this now without giving some people credit for some mileage they might not want credit for.
-
Meh, not quite the same "within the footprint" scenario...
If I were to nix 21, we'd just be revisiting this topic another few moths (that's a typo (https://www.youtube.com/watch?v=1-MJy7w69EU)) down the road, with somebody asking
<randomly presses & releases shift while typing>
where's exit 21 why is 22 called 22 when i's signed 21 at the same place shouldn't the lower number take precedence?
</randomly presses & releases shift while typing>
Like I said, not worth the bother of adding new objects to the repo.
All Things are Perfect / To every last flaw / And bound in accord / With Eris's Law. (HBT; The Book of Advice 1:7) (https://en.m.wikisource.org/wiki/Page:Principia_Discordia_(1970).djvu/13)