Travel Mapping
Highway Data Discussion => Updates to Highway Data => Topic started by: Markkos1992 on September 15, 2021, 08:49:04 am
-
1. 5 should be 4B (https://www.google.com/maps/@38.6217509,-90.1236198,3a,75y,100.7h,90t/data=!3m6!1e1!3m4!1szc8FdphO1zBDOFD1_NvbFw!2e0!7i16384!8i8192). 4 could be 4A (https://www.google.com/maps/@38.6236459,-90.1303477,3a,75y,314.36h,100.83t/data=!3m7!1e1!3m5!1sztz3iZyTUiPXD0Zguc-KoA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3Dztz3iZyTUiPXD0Zguc-KoA%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D347.55002%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192).
2. 8 should be 7 (https://www.google.com/maps/@38.6185012,-90.055198,3a,75y,325.3h,92.25t/data=!3m6!1e1!3m4!1sJzGFXZLyrSg217PoPCXzIg!2e0!7i16384!8i8192). (also affects US 50)
3. A point is needed for this interchange (Exit 21) (https://www.google.com/maps/@38.5640208,-89.840999,3a,75y,303.68h,88.81t/data=!3m7!1e1!3m5!1sBn0rlHFrPNAj6zXuqclGEg!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DBn0rlHFrPNAj6zXuqclGEg%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D65.73712%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192). According to Wikipedia (https://en.wikipedia.org/wiki/Interstate_64_in_Illinois), it was opened in 2017.
Side note: For IL 3, I think that I-55(2C) should be I-55(3). Looking at the I-55 and US 40 labels here, this seems a lot more complicated than it should be in theory. Maybe go 3A for I-55, and then I-55(3A) for US 40 and IL 3. Being on this AZ Trip, I do not have tons of times to ruminate on this at the moment.
-
1. 5 should be 4B (https://www.google.com/maps/@38.6217509,-90.1236198,3a,75y,100.7h,90t/data=!3m6!1e1!3m4!1szc8FdphO1zBDOFD1_NvbFw!2e0!7i16384!8i8192). 4 could be 4A (https://www.google.com/maps/@38.6236459,-90.1303477,3a,75y,314.36h,100.83t/data=!3m7!1e1!3m5!1sztz3iZyTUiPXD0Zguc-KoA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3Dztz3iZyTUiPXD0Zguc-KoA%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D347.55002%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192).
That changed from 5 to 4B sometime between Oct '13 (https://goo.gl/maps/fxSPeVHZFokksw2K8) & July '15 (https://goo.gl/maps/2gE8yVDiiXDsoApdA). Same time frame with the 4 -> 4A as well.
-
It looks like 28C should be 28B (https://en.wikipedia.org/wiki/Interstate_64_in_Missouri).
Also what would be the best solution for FortyDr? Maybe just stick with 40Dr?
I also saw something on the I-64 in MO Wikipedia about Exit 38B (https://www.google.com/maps/@38.6348884,-90.3900873,3a,75y,334.75h,90t/data=!3m6!1e1!3m4!1s8oXbacNbp8alg2PCRa8ijQ!2e0!7i16384!8i8192), but I am unsure how to handle it and if we should be handling that now.
-
Here's what it looks like on GMSV:
WB 40B I-44; 40A Stadium/9th; 39 Market/21st; 38B Market 3000 West; 38A Forest Park; no 37
EB 37A Market/Bernard; 37B Grand; 38A Jefferson; 38B Chestnut/20th; 39A 14th; 39B Stadium/11th; 40 6th.
WB 38B is actually west of EB 38A, and I had to make the latter a 38C to separate the points. That one I'm inclined to keep, even though there is no 38C in the field, just so I don't have to merge those points.
So, here's what I am thinking:
What I have labeled as 38D should be turned into 39A. What I have labeled as two discrete points of 39C and 40A should be combined into "40" centered at 8th Street, splitting the difference between the exits to 9th (WB #40A) and 6th (EB #40). Then, 40C should be turned into 40B, which is what's seen on the Poplar Street Bridge exiting to I-44 and there is no EB companion.
That would eliminate non-existent letter suffixes except for 38C, for reasons described above. Unless I call it "I-64(38A_EB)"? Bleah.
-
I-64: Changing 4->4A, 5->4B, 8->7. Adding 21 (Rieder Road).
US 50: Changing I-64( 8 )->I-64(7).
I-55/64/US 40: Keep the 1A/1B designations even though it's signed as 1 in both directions, because of the large space between the WB and EB exit points. Change 2->2A (Eads Bridge/3rd St). NEW point labeled 2C (signed as MLK Bridge) to the WB exit/EB entrance point of that. Current location labeled 2C on I-55/US 40/IL 3, the new I-64/70 junction, needs to become 3, as you say. (Marked as 3 on I-64 already.) Current location labeled 3 on I-55/US 40 becomes 3C.
The latter set might break/move a few people's points, but I think that's unavoidable.
-
Apologies in advance...
Jim asked if I could process Highway63's .zip file and maybe come up with a list of users with broken .lists, as done with the Massachusetts exit renumberings (https://github.com/TravelMapping/HighwayData/pulls?q=is%3Apr+is%3Aclosed+label%3A%22exit+renumbering%22).
Taking a look at the changes, I'm gonna offer my copper two-cent piece.
I-55 et al:
I-55/64/US 40: ... Change 2->2A (Eads Bridge/3rd St). NEW point labeled 2C (signed as MLK Bridge) to the WB exit/EB entrance point of that. Current location labeled 2C on I-55/US 40/IL 3, the new I-64/70 junction, needs to become 3, as you say. (Marked as 3 on I-64 already.) Current location labeled 3 on I-55/US 40 becomes 3C.
The latter set might break/move a few people's points, but I think that's unavoidable.
I think a better solution would be to not add a new point for 2C, go 1PPI, and consider it part of existing Exit 2 on Where the centerlines would cross if it were an at-grade intersection with the same shape (https://travelmapping.net/devel/manual/points.php#two_way) grounds.
2 could stay 2, as 2A/B/C in one interchange (https://travelmapping.net/devel/manual/wayptlabels.php#dropa).
This would free up 2C to become an AltLabel, and avoid breaking 16 .list files at this interstate-interstate junction.
Per that same rule, we can optionally keep the A (https://travelmapping.net/devel/manual/wayptlabels.php#dropa), so 3A label can become the new label for the existing 2C, allowing 3 to be an AltLabel for 3C.
This would avoid breaking any .list files.
2 http://www.openstreetmap.org/?lat=38.628874&lon=-90.160203
3A +2C http://www.openstreetmap.org/?lat=38.633198&lon=-90.144153
3C +3 http://www.openstreetmap.org/?lat=38.634171&lon=-90.140462
IL3:
This looks kinda awkward, because the interchange layout is kinda awkward. Looks like SB does take the obvious right-turn ramp (https://www.google.com/maps/@38.6336835,-90.14726,3a,25.7y,146.79h,90.71t/data=!3m9!1e1!3m7!1sDX5JBCjQCCqqJkEZoiWLCQ!2e0!7i13312!8i6656!9m2!1b1!2i40), though northbound gets more convoluted (https://www.google.com/maps/@38.6324577,-90.1476996,3a,23.2y,83.55h,90.86t/data=!3m6!1e1!3m4!1sFwXQ1wtKaBAxUYlA6CSq9A!2e0!7i16384!8i8192) as there's no direct ramp.
IMO a better visual solution is to "cut the diagonal" as I like to term it, of the couplet, and put a point here (http://www.openstreetmap.org/?lat=38.633104&lon=-90.146465), or even more precisely, maybe here (http://www.openstreetmap.org/?lat=38.633427&lon=-90.146824)? What to call it, maybe StCAve_S?
This would break the graph connection (& thus concurrency) at I-70 et al but would still leave one one point over at Exit 2 for surfing between intersecting/connected routes, or for Jim's students to do algorithms.
64/40:
Don't forget to change 28C -> 28B on I-64 itself. :)
FortyDr -> ForDr
Downtown / Downtown West: Reconstruction, renumbering? Yowch, what a mess!
38A looks appropriate.
That next point that peels off just after the Ewing overpass and touches down at Market & Garrison... Looks like its exit number has been removed but it's still open? (https://www.google.com/maps/@38.629212,-90.2224978,3a,75y,336.12h,98.15t/data=!3m9!1e1!3m7!1sj4aLZZ-ck6eB0gRfoGas9A!2e0!7i16384!8i8192!9m2!1b1!2i40) Weird. Maybe not for long? 38B is not in use; if it's needed elsewhere (https://www.google.com/maps/@38.6260591,-90.2110148,3a,27.3y,300.81h,93.68t/data=!3m10!1e1!3m8!1srb9vcYtlSJB29pZozri6EQ!2e0!5s20210801T000000!7i16384!8i8192!9m2!1b1!2i40) it could become MarSt or eventually *MarSt?
38C looks like an appropriate label (https://travelmapping.net/devel/manual/wayptlabels.php#nextsuffix) given that 38A is already used a couple points west. Probably should still be centered on Jefferson though.
22nd St: Moved from the demolished connector (something MoDOT originally had bigger plans for?). The new coordinates make sense. It's gone through some different exit numbers, switching from 39A to plain 39 between Oct 2011 (https://www.google.com/maps/@38.6260809,-90.2110521,3a,28y,298.65h,94.49t/data=!3m9!1e1!3m7!1sdZbMLl3Xjv9kak9RjAaYKQ!2e0!7i13312!8i6656!9m2!1b1!2i40) & and May 2013 (https://www.google.com/maps/@38.6260454,-90.211056,3a,28.9y,301.64h,96.75t/data=!3m10!1e1!3m8!1svSWaOJNJEXn0_TTJzQtmWg!2e0!5s20130501T000000!7i13312!8i6656!9m2!1b1!2i40), then to 38B between May & Aug 2021 (https://www.google.com/maps/@38.6260591,-90.2110148,3a,27.3y,300.81h,93.68t/data=!3m10!1e1!3m8!1srb9vcYtlSJB29pZozri6EQ!2e0!5s20210801T000000!7i16384!8i8192!9m2!1b1!2i40). I assume 38B is not a contractor error, and is the correct new 38B, along with removing the signage at the other exit farther west. 38D should still be kept as an AltLabel.
14th St: 39B -> 39A +39B
39B: Probably just as well calling 11th St a 1PPI along with Exit 40 (like you're already doing), not giving it its own separate point, and allowing 39B to stay in use as an AltLabel for 39A.
40: I can get behind collapsing the 2 points into one here. Just remember to include both 39C and 40A as AltLabels to avoid breaking .lists.
40C -> 40B makes sense.
-
I merged the topics since yakra's latest post covered both IL and MO.
-
I-55 et al:
I think a better solution would be to not add a new point for 2C, go 1PPI, and consider it part of existing Exit 2 on Where the centerlines would cross if it were an at-grade intersection with the same shape (https://travelmapping.net/devel/manual/points.php#two_way) grounds.
2 could stay 2, as 2A/B/C in one interchange (https://travelmapping.net/devel/manual/wayptlabels.php#dropa).
This would free up 2C to become an AltLabel, and avoid breaking 16 .list files at this interstate-interstate junction.
Per that same rule, we can optionally keep the A (https://travelmapping.net/devel/manual/wayptlabels.php#dropa), so 3A label can become the new label for the existing 2C, allowing 3 to be an AltLabel for 3C.
This would avoid breaking any .list files.
2 http://www.openstreetmap.org/?lat=38.628874&lon=-90.160203
3A +2C http://www.openstreetmap.org/?lat=38.633198&lon=-90.144153
3C +3 http://www.openstreetmap.org/?lat=38.634171&lon=-90.140462
I’m going to be on the losing end of all of these, aren’t I?
I think the points SHOULD be broken to get the present list more in sync with the exits. It’s not perfect (see the retention of a split 1A/1B), but it would get closer. I do realize that 16 lists is a substantial number to break, though. Your solution does preserve lists, and if that's a tier-1 goal in this situation, I guess it'll have to be implemented over my objections.
IL3:
This looks kinda awkward, because the interchange layout is kinda awkward. Looks like SB does take the obvious right-turn ramp (https://www.google.com/maps/@38.6336835,-90.14726,3a,25.7y,146.79h,90.71t/data=!3m9!1e1!3m7!1sDX5JBCjQCCqqJkEZoiWLCQ!2e0!7i13312!8i6656!9m2!1b1!2i40), though northbound gets more convoluted (https://www.google.com/maps/@38.6324577,-90.1476996,3a,23.2y,83.55h,90.86t/data=!3m6!1e1!3m4!1sFwXQ1wtKaBAxUYlA6CSq9A!2e0!7i16384!8i8192) as there's no direct ramp.
IMO a better visual solution is to "cut the diagonal" as I like to term it, of the couplet, and put a point here (http://www.openstreetmap.org/?lat=38.633104&lon=-90.146465), or even more precisely, maybe here (http://www.openstreetmap.org/?lat=38.633427&lon=-90.146824)? What to call it, maybe StCAve_S?
This would break the graph connection (& thus concurrency) at I-70 et al but would still leave one one point over at Exit 2 for surfing between intersecting/connected routes, or for Jim's students to do algorithms.
Yeah, it's ugly. We can’t get around the fact that SB 3 and NB3 have vastly different routes. I like the idea of the break at StCAve_S instead of using the I-55(3) point.
64/40:
Don't forget to change 28C -> 28B on I-64 itself. :)
FortyDr -> ForDr
Right.
Downtown / Downtown West: Reconstruction, renumbering? Yowch, what a mess!
38A looks appropriate.
That next point that peels off just after the Ewing overpass and touches down at Market & Garrison... Looks like its exit number has been removed but it's still open? (https://www.google.com/maps/@38.629212,-90.2224978,3a,75y,336.12h,98.15t/data=!3m9!1e1!3m7!1sj4aLZZ-ck6eB0gRfoGas9A!2e0!7i16384!8i8192!9m2!1b1!2i40) Weird. Maybe not for long? 38B is not in use; if it's needed elsewhere (https://www.google.com/maps/@38.6260591,-90.2110148,3a,27.3y,300.81h,93.68t/data=!3m10!1e1!3m8!1srb9vcYtlSJB29pZozri6EQ!2e0!5s20210801T000000!7i16384!8i8192!9m2!1b1!2i40) it could become MarSt or eventually *MarSt?
38C looks like an appropriate label (https://travelmapping.net/devel/manual/wayptlabels.php#nextsuffix) given that 38A is already used a couple points west. Probably should still be centered on Jefferson though.
22nd St: Moved from the demolished connector (something MoDOT originally had bigger plans for?). The new coordinates make sense. It's gone through some different exit numbers, switching from 39A to plain 39 between Oct 2011 (https://www.google.com/maps/@38.6260809,-90.2110521,3a,28y,298.65h,94.49t/data=!3m9!1e1!3m7!1sdZbMLl3Xjv9kak9RjAaYKQ!2e0!7i13312!8i6656!9m2!1b1!2i40) & and May 2013 (https://www.google.com/maps/@38.6260454,-90.211056,3a,28.9y,301.64h,96.75t/data=!3m10!1e1!3m8!1svSWaOJNJEXn0_TTJzQtmWg!2e0!5s20130501T000000!7i13312!8i6656!9m2!1b1!2i40), then to 38B between May & Aug 2021 (https://www.google.com/maps/@38.6260591,-90.2110148,3a,27.3y,300.81h,93.68t/data=!3m10!1e1!3m8!1srb9vcYtlSJB29pZozri6EQ!2e0!5s20210801T000000!7i16384!8i8192!9m2!1b1!2i40). I assume 38B is not a contractor error, and is the correct new 38B, along with removing the signage at the other exit farther west. 38D should still be kept as an AltLabel.
14th St: 39B -> 39A +39B
39B: Probably just as well calling 11th St a 1PPI along with Exit 40 (like you're already doing), not giving it its own separate point, and allowing 39B to stay in use as an AltLabel for 39A.
40: I can get behind collapsing the 2 points into one here. Just remember to include both 39C and 40A as AltLabels to avoid breaking .lists.
40C -> 40B makes sense.
38C: Re-relocated to center on Jefferson, although I disagree.
I’ll retain the various alt labels, although I disagree.
I really wish I could do a giant “flush” of old names. Not all the ones I’ve changed to exits, but actual reroutes and corrections. I have alt labels up the wazoo in Peoria and keep getting notes about changing IL 116’s north end that would break a years-old deprecated label. Retaining all these on I-64 seems like it could create future issues.
After I post this I'll redo the appropriate files and send updated versions. Then you can check that they match what you want.
-
I am linking to the relevant IL 116 thread here for context (https://forum.travelmapping.net/index.php?topic=4518.0).
-
Thanks for making all those changes.
I've committed (https://github.com/TravelMapping/HighwayData/commit/77ea4a1c4515fa6673cf49a7e99ddf743de74a74) the vast majority, making a couple minor changes in the process:
il.il003: re-added +I-55(2C) as an AltLabel to StCAve_S to avoid breaking .lists.
il.us040: removed new +0 AltLabel, assuming it's just a copy-paste-o from the I-64 file.
The BVB-related changes are not commited. I'll save it in a git stash, and it'll be mostly ready to go when the time comes.
This leaves us with 64/40 in downtown STL.
Heading west from the river...
40B +40C looks good.
US40 has I-64(40) +I-64(39C) +I-64(40A). Looks good. I-64 just has plain 40, no AltLabels. I've changed my local copy to 40 +39C +40A, to avoid breaking .lists here.
39A +39B looks good.
22nd St: This was Exit 39 for 8 years or so, but is now signed as 38B (https://www.google.com/maps/@38.6260591,-90.2110148,3a,27.3y,300.81h,93.68t/data=!3m10!1e1!3m8!1srb9vcYtlSJB29pZozri6EQ!2e0!5s20210801T000000!7i16384!8i8192!9m2!1b1!2i40). Existing 38B is not in use; looks like it's unnumbered now... to be closed soon?
I could see doing...
38A, *MarSt (or MarSt, still open?), 38C, 38B
or
38A 38B (*38B?) 38C 38D
like exists now. A bit odd, this one. Discuss...
I really wish I could do a giant “flush” of old names. Not all the ones I’ve changed to exits, but actual reroutes and corrections. I have alt labels up the wazoo in Peoria
Flushing out unused alt labels (https://travelmapping.net/logs/unusedaltlabels.log) could probably be done via a shell script. Let me know if you're interested.
(Edit to clarify: This would remove unused alts from the .wpt files themselves, not remove anything undesired from .lists.)
In-use ones should still be kept until no longer needed of course, to avoid breaking .list files.
and keep getting notes about changing IL 116’s north end that would break a years-old deprecated label.
Yeah, that's where AltLabels get cumbersome, where an old label still in use at an existing location begs to be moved because its designation is now correct elsewhere. I have some sympathy for the US34/US34Byp situation, though in cases like that it's probably best to bite the bullet and break a .list when it can't be avoided.
Massachusetts was this problem on a grand scale. :(
Retaining all these on I-64 seems like it could create future issues.
Only if the deprecated labels were needed in a new location, begging for .lists to be broken. If this were to happen, it'd have to be dealt with then, whether the original point a label's being moved from is hidden or visible.
So to that end, it's not really creating issues in the future, but avoiding issues (due to needlessly breaking .lists) now.
Plus, AltLabels (at least, ones not at a route's end) gradually fade out of use as people extend their travels and edit their .list lines. Over time, there will be fewer & fewer .lists to eventually break.
-
https://github.com/TravelMapping/HighwayData/pull/5171 includes the Bella Vista Bypass (https://forum.travelmapping.net/index.php?topic=4314) and most of the STL changes (https://forum.travelmapping.net/index.php?topic=4576).
Everything but the I-64 / US40 changes downtown are included, while we continue to sort things out.
I-49: I removed the +0 AltLabel, as it's not needed for a freshly-added waypoint.
MO90: Committed as submitted. GooHolRd is now no longer needed for shaping, and many of the hidden points could be converted to visible or deleted.
Highway63, how do the changes (https://github.com/TravelMapping/HighwayData/pull/5171/files) look?
-
Bella Vista bypass is good.
What more needs looked at on I-64/US40? I thought I had a workable solution in what I sent. Is it the stuff two posts up?
-
I have no further comments in regard to IL. I am pretty sure that we are 100% good on that end.
I did find the following on I-64/US 40 in MO beyond the discussion going on in relation to the 38 points:
1. 32 should be 31B (https://www.google.com/maps/@38.6296303,-90.3297869,3a,75y,310.24h,88.6t/data=!3m6!1e1!3m4!1sh3Rhn1jMcy4y5tI3APDDTA!2e0!7i16384!8i8192). 31 could be 31A (https://www.google.com/maps/@38.6314596,-90.3551078,3a,75y,133.41h,90t/data=!3m7!1e1!3m5!1sdHzSajb_6kxZ96Oorh8Law!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DdHzSajb_6kxZ96Oorh8Law%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D140.45512%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192).
2. 33D should be 33C (https://www.google.com/maps/@38.6320289,-90.3026057,3a,75y,269.66h,101.19t/data=!3m6!1e1!3m4!1syqIs74eaYh73_B1jJKYPPQ!2e0!7i16384!8i8192).
-
1. 32 should be 31B (https://www.google.com/maps/@38.6296303,-90.3297869,3a,75y,310.24h,88.6t/data=!3m6!1e1!3m4!1sh3Rhn1jMcy4y5tI3APDDTA!2e0!7i16384!8i8192). 31 could be 31A (https://www.google.com/maps/@38.6314596,-90.3551078,3a,75y,133.41h,90t/data=!3m7!1e1!3m5!1sdHzSajb_6kxZ96Oorh8Law!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DdHzSajb_6kxZ96Oorh8Law%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D140.45512%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192).
I know what happened here. The names are in relation to the I-64/I-170 interchange before the rebuild of I-64 in 2008. So yeah, 31 (I-170) should be 31A, and Hanley 31B.
-
I have no further comments in regard to IL. I am pretty sure that we are 100% good on that end.
I did find the following on I-64/US 40 in MO beyond the discussion going on in relation to the 38 points:
1. 32 should be 31B (https://www.google.com/maps/@38.6296303,-90.3297869,3a,75y,310.24h,88.6t/data=!3m6!1e1!3m4!1sh3Rhn1jMcy4y5tI3APDDTA!2e0!7i16384!8i8192). 31 could be 31A (https://www.google.com/maps/@38.6314596,-90.3551078,3a,75y,133.41h,90t/data=!3m7!1e1!3m5!1sdHzSajb_6kxZ96Oorh8Law!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DdHzSajb_6kxZ96Oorh8Law%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D140.45512%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192).
2. 33D should be 33C (https://www.google.com/maps/@38.6320289,-90.3026057,3a,75y,269.66h,101.19t/data=!3m6!1e1!3m4!1syqIs74eaYh73_B1jJKYPPQ!2e0!7i16384!8i8192).
These revisions were done via (https://github.com/TravelMapping/HighwayData/pull/5318). I left out the Downtown St. Louis stuff because I had deferred that to yakra, and we had not made a consensus on it.
I may relook at it later since I do have the file now.
-
22nd St: This was Exit 39 for 8 years or so, but is now signed as 38B. Existing 38B is not in use; looks like it's unnumbered now... to be closed soon?
I could see doing...
38A, *MarSt (or MarSt, still open?), 38C, 38B
or
38A 38B (*38B?) 38C 38D
like exists now. A bit odd, this one. Discuss...
Based on the file I see from Highway63, I think I prefer this:
38A stays as-is.
38B as shown now gets moved to replace 38C. I do not think that the current 38B is needed as I see it as 1PPI with 38A.
Then 38C becomes 38B. Then 39 becomes *38D.
Yeah 39 is permanently closed. (https://www.stltoday.com/news/local/metro/five-highway-i--ramps-to-close-permanently-on-feb/article_6c311c99-c464-5506-8296-a994c1c724c3.html) (paywalled so quoted below, article is from January 24, 2020)
ST. LOUIS — Five major ramps on Highway 40 (Interstate 64) will close permanently early next month to make way for construction of a Major League Soccer stadium, the city and stadium developers announced Thursday.
The five ramps being closed are:
I-64 westbound:
On-ramp from Pine Street and Market Street
Exit 39 at Market Street
I-64 eastbound:
On-ramp from South Ewing Avenue
On-ramp from Pine Street and Market Street
Exit 38B at North 20th Street and Chestnut Street
-
There is a new exit being constructed as a diamond interchange with an extension of 22nd Street, and OSM calls it Exit 39.
So the difference I see from what I sent is that the present 38B, which is not in use, moves to Jefferson and replaces 38C. The new 39 is pre-emptively added and 38D is a demoted point with 39. (I can make it "39 +*38D" in the line entry but does that make a difference?)
-
There is a new exit being constructed as a diamond interchange with an extension of 22nd Street, and OSM calls it Exit 39.
So the difference I see from what I sent is that the present 38B, which is not in use, moves to Jefferson and replaces 38C. The new 39 is pre-emptively added and 38D is a demoted point with 39. (I can make it "39 +*38D" in the line entry but does that make a difference?)
I don't think the * affects anything to be honest.
-
There is a new exit being constructed as a diamond interchange with an extension of 22nd Street, and OSM calls it Exit 39.
So the difference I see from what I sent is that the present 38B, which is not in use, moves to Jefferson and replaces 38C. The new 39 is pre-emptively added and 38D is a demoted point with 39. (I can make it "39 +*38D" in the line entry but does that make a difference?)
I don't think the * affects anything to be honest.
There is a new exit being constructed as a diamond interchange with an extension of 22nd Street, and OSM calls it Exit 39.
So the difference I see from what I sent is that the present 38B, which is not in use, moves to Jefferson and replaces 38C. The new 39 is pre-emptively added and 38D is a demoted point with 39. (I can make it "39 +*38D" in the line entry but does that make a difference?)
I don't think the * affects anything to be honest.
Yeah, it does not. I am sure that the Exit probably will be Exit 39, but I am sour on using an OSM Exit Number before the exit opens.
-
22nd St: This was Exit 39 for 8 years or so, but is now signed as 38B. Existing 38B is not in use; looks like it's unnumbered now... to be closed soon?
I could see doing...
38A, *MarSt (or MarSt, still open?), 38C, 38B
or
38A 38B (*38B?) 38C 38D
like exists now. A bit odd, this one. Discuss...
*EwiAve is also a possibility (the point's positioned right there) per the closed ramps in the SW quadrant.
OTOH, signage was for Market.
Comes down to what Highway63 thinks is the nicest looking / most intuitive.
If it were me I'd lean toward something using exit numbers rather than named points.
Based on the file I see from Highway63, I think I prefer this:
38A stays as-is.
Agree.
38B as shown now gets moved to replace 38C. I do not think that the current 38B is needed as I see it as 1PPI with 38A.
Looking at ESRI WorldImagery, do the closed ramps in the SW quadrant change your opinion?
Then 38C becomes 38B.
Still fudges a suffix in that 38A directly touches down here. Taken on its own:
Definitely not worse than my "keep 38C" proposal.
Better in that at least it's served by Exit 38B WB.
Then 39 becomes *38D.
Yeah 39 is permanently closed. (https://www.stltoday.com/news/local/metro/five-highway-i--ramps-to-close-permanently-on-feb/article_6c311c99-c464-5506-8296-a994c1c724c3.html) (paywalled so quoted below, article is from January 24, 2020)
ST. LOUIS — Five major ramps on Highway 40 (Interstate 64) will close permanently early next month to make way for construction of a Major League Soccer stadium, the city and stadium developers announced Thursday.
The five ramps being closed are:
I-64 westbound:
On-ramp from Pine Street and Market Street
Exit 39 at Market Street
I-64 eastbound:
On-ramp from South Ewing Avenue
On-ramp from Pine Street and Market Street
Exit 38B at North 20th Street and Chestnut Street
Just to add some confusion, exit 38B is reborn in the same location. In both directions. The old exit 39 is now exit 38B.
I am sure that the Exit probably will be Exit 39, but I am sour on using an OSM Exit Number before the exit opens.
May 2021 (https://www.google.com/maps/@38.6260752,-90.2110411,3a,36.9y,301.24h,93.67t/data=!3m10!1e1!3m8!1s5zbzssr_AFtANNgqmaJRdA!2e0!5s20210501T000000!7i16384!8i8192!9m2!1b1!2i40)
Aug 2021 (https://www.google.com/maps/@38.6260591,-90.2110148,3a,27.3y,300.81h,93.68t/data=!3m10!1e1!3m8!1srb9vcYtlSJB29pZozri6EQ!2e0!5s20210801T000000!7i16384!8i8192!9m2!1b1!2i40)
OSM shows the old exit number.
-
^Yes yakra, seeing those ramps in the southwest corner change my mind to go with your 38A, 38B, 38C, and 38D proposal.
-
I am now completely confused.
The 38B ramp to Market is not in use. I see no reason to keep a label there. It can be killed and 38B moved to Jefferson to replace 38C without issue.
Then what is the new interchange at 22nd supposed to be?? "38C +*38D"?? "39 +*38D"??
-
There is a segment of US 40 & I-64 in Downtown St. Louis that isn't syncing together. For whatever reason, my map(s) show I-64 traveled from I-170 to the Mississippi River, but showing a gap on US 40 from exit 38C to exit 40B.
-
I moved osu-lsu's post here because I do not think we ever finalized how to handle the Exit 38 mess.
-
I guess not, after 14 months.