tonestertm wrote:Being a super noob, I'm not even sure I should be requesting this unlock, but it looks to me like there are actually four turns that need to be allowed to make this intersection functional.

Since there appears to be a couple of physical barriers, I tend to agree with you that the geometry needs to be reworked, with turn-only lanes added in several places.

https://www.waze.com/editor/?lon=-118.2 ... 43,4625457

Edit: Sorry, this appears to be the segment that actually needs unlocking. I misunderstood someone else's strange edit, and found one of the turns already fixable.
https://www.waze.com/editor/?lon=-118.2 ... ts=4480030

I have done quite a bit of reading so far, but I still wonder about a couple other things here:

1) I wonder if the eastbound right and westbound left turns are placed properly to allow proper warning in the client -"keep left" etc. Should the entrance ramp actually be split for eastbound and westbound street traffic? I realize that this would add a lot more nodes and turns and thus might be bad. I guess I'll have to get over there and drive it to see what happens.

by all means, drive the intersection and see.
As for getting the right verbal instructions, review
http://www.waze.com/wiki/index.php/How_ ... _maneuvers
and
http://www.waze.com/wiki/index.php/Junction_Style_Guide

I have noticed that when I split the left and right turn only lanes from the SAME junction spot,
the straight through driver does NOT get confusing instructions to keep left and then keep right.

2) I wonder if the (north)eastbound freeway section ending at Colorado Blvd should instead be a ramp?

Sorry if I'm out of line here. Thanks

Not at all. I unlocked everything in the area. Lock what you think appropriate, when you finish.

I like to use ramps because they 'look different' on the map when editing and for some of the other characteristics. There are some argument for NOT using ramps when 'at grade' but I find them less than totally convincing. Note that to properly map that intersection, you will need to make sure some segments 'cross over/under' each other without connecting. That means they will need to be set to different 'levels' so that WAZE doesn't come back complaining about needing to connect them.

Good luck.

Remember, "it is the programmers job to make things easier for the user. It is NOT the users job to make things easier for the programmer." In this case, WE editors are the PROGRAMMERS and the users are the drivers. It is OUR job to make sure the drivers get the correct instructions at the proper time. If we need to 'break some of the guideline rules' to do that, it means that WAZE has some WAZE to go before the guidelines are written correctly. The programs involved, the editing programs and the routing programs are really so complex that no one REALLY KNOWS what will happen at any particular point under all possible conditions, so we need to be flexible.


Keep up the good work. Thanks for all the WAZE you help.

I don't believe that segment should be a ramp. BUT it needs to be a ramp based on the signage at the location.

Thanks for the help and the responses. I've fixed the turn restriction, but I unfortunately don't have the time right at this moment to do the rest of the intersection proper justice (family obligations...) so I'm not re-locking it yet. I'll be back to it tonight, after T-day dinner.

jemay, I'm not quite sure I follow your statement. That particular spot is a peculiar one. I'm just talking about the very last segment, where it meets the Blvd., from where the other ramp splits off. Is it kosher for a Freeway segment (actually it's a really long exit road) to just abut a surface st?

Thanks again!