I’ll let a more local manager decide. It looks fine from a functional perspective. Bowties are necessary for some kinds junctions to ensure proper control over turn restrictions.
Thanks, I’ll PM him. I looked at the resources but these intersections meet the requirements to be split, plus it’s not operational as it is now. It caused my icon to jump all over place when I drive through it.
I know I am a bit late seeing this. I know that the first intersection I was a part of, sorry if I messed it up for you there AWD. I didn’t realize they made another interchange a diverging diamond until I saw your other permalink…unless I had my name on it too and forgot.
The first one was already done, I think I touched it. I primarily used it for the KC diverging diamond at Front St and 435.
AWDTerror, the second permalink, you have an unnamed segment on St Robert Blvd…
Also, I might be behind on this as well, but does it pronounce as Saint for that street or is it Street? I saw somewhere here recently about naming certain things St. for Saint, just wondered. I have to try it out around here for St Louis pathfinder naming. I now some segments are St Louis, but I don’t know how the voice guidance is handling them at the moment. I wish I had a simulator.
Just trying to keep up to speed with you all for the 44 corridor, thanks.
Edit: I saw on the first permalink wrong way segments, I updated it for the diverging diamond and closed the UR as solved. Just writing to mention that.
Edit 2: I’m realizing something here, that’s not a diverging diamond is it? One reason I don’t like bowtie intersection editing…sorry for the problem…with the UR though, it instructed a turn before the actual turn was needed. So the bowtie actually created some issues here.
The one problem I see here (2nd permalink on OP) is that the ramp highlighted in this permalink is going to get a right turn instruction… it would almost be better just to move the end of the segment to where the road goes straight again. It isn’t necessary to have it go to that junction it is currently at because it isn’t going to be routing anywhere but right anyways. So if it is moved and made straight, people won’t get confusing instructions there and submit UR’s either.
I see you have the segment for a left turn enabled, but that shouldn’t be, the roads don’t really allow for a left turn there, they are setup for traffic to flow off the freeway and continue straight. For proper navigation, to prevent people from trying to cut across two lanes of traffic, I’d disable that turn for sure, so Waze can route them off the interchange just to the East of this one for better/safer routing. There isn’t a no u-turn sign there or anything nor no left turn signs, but you can just see that it wasn’t setup for a left hand turn off that ramp from all the aerial and street level sources. Just my opinion, leaving at your discretion here. Maybe locals use it for that, but other users passing through it would not be a good route for people pulling trailers/RVs, other vehicle types. Just my POV.
It’s illegal to make u-turns at lighted intersections (RSMO 304.341 section 2) in Missouri. Plus this is a hazardous intersection since there is a crest in the opposing lane that limits the visibility of other drivers. As of currently, the intersection with the left turn indicator is used by most coming off the interstate needing to go in the opposite direction. While crossing 2 lanes of traffic isn’t ideal, it is probably the best option for a u-turn unless they go about a mile down and turn around in a parking lot.
I think I’ve got it all done. I’ve ran through some of the changes tonight while driving and it seems to be working. I’m still waiting on the rest of the changes to get updated.