Right turn road missing 156th northbound to King George Southeast bound in Surrey, BC

[WRWazy]

There is a missing right turn loop on 156th northbound to King George Southeast bound in Surrey, BC. I’m a new editor and can’t figure out how to add it properly. Could someone help please?

Thank you!

[BryceCampbell]

Can you provide a permalink?

If it’s something connected already, you should be able to change the arrow and save as a suggestion

[WRWazy]

Apologies, I didn’t know about the permalink method. Thank you for showing me how. Here is the permalink: https://waze.com/en-GB/editor?env=usa&lat=49.04244&lon=-122.79001&marker=true&zoomLevel=20&segments=59532846,525538364,525538365

I can’t seem to figure out how to save that looped right turn as a suggestion though? Perhaps it is locked?

[BryceCampbell]

@WRWazy

Perhaps it is locked?

There are segment locks. Higher use segments have A-Auto locks, and stuff with restrictions we’ll uplock for protection

Can learn about Locking standards on our Wiki
I’ll treat one-way segments like restrictions.

@Canada_Wazeopedia1

Locking Standard

Canada has active “Traffic Locks”, these locks are based on usage from users. They are limited to a max rank of 4, but can be any rank below.

Segments that have restricted turns must be locked to a minimum Level 3.

If the current lock or traffic lock is higher than the minimum standards listed below, please don’t lower the lock.

Minimum Road Locking Rank Standard

Segment Type Minimum locks
Freeway 4
Ramp highest rank of connected segment
3
Major Highway 4
Minor Highway 3
Primary Street 2
Street 1
: : : : :Railroad: : : : : 4

Regarding King George and 156 St - those types of segments we call at-grade-connectors.

@Canada_Wazeopedia1

At-Grade Connectors

At-grade connectors (AGCs) are the highway-ramp-like curved segments that traffic uses to move from road to another. This image shows three AGCs of varying sizes:

Three AGCs of varying sizes connect these two roads.

Current guidance from Waze is to map at-grade connectors if they are longer than two car lengths; that is, if the distance from the gore point (where the AGC lane diverges from the main lanes) and the stop line is more than two car lengths. Start mapping the AGC at the gore point, which can be a solid line that separates the AGC. If there is a solid line that creates a longer AGC, start the AGC where that line starts, like this:

The AGC’s road type simply should be the lower (for lack of a better adjective) of the two road types it connects to. In the image above, all three AGCs are segments of primary street because they connect segments of primary street and minor highway - and the lower value segment type of those two is primary street. Do not use a third segment type for AGCs and do not use the ramp type for an AGC.

Set the street name of an AGC to “None”. Routing instructions will adopt the name of the segment that he AGC leads to. This prevents map clutter as these segments would otherwise display the name in the app map.

There are some things to watch out for when creating AGCs:

• The mix of road types may lead to atypical turn instructions such as “exit right” instead of a more appropriate “keep right” as the instruction for taking an AGC. This is not a serious problem, but using the WME Junction Angle Info script can help you correct this.
• Lane guidance can become tricky with AGCs, particularly when the AGC with junction boxes and paths (a.k.a. far turns). We recommend leaving AGCs outside of junction boxes if possible and not creating paths for them. A user taking an AGC can be told simply to stay right in one (or more) lanes without having to see any other instruction. A user continuing straight past an AGC to the intersection beyond can get turn instructions relevant for that intersection without reference to the AGC lanes. There is no need to group the AGC guidance with the “continue straight” guidance into a single instruction.
• Intersections with an AGC almost always forbid the right turn that the AGC replaces. Remember to block that turn when required.
• If the AGC connects to a two-way segment, remember to block the turns leading the other way, as in these images:

They aren’t always needed. Small traffic refuge islands we don’t [generally] map as they just make the map more complicated. Guidance is if its under 25-30 metres between the gore and the intersection segment, t’s probably not needed.

King George being a diagonal throughway, it can create intersections where the intersecting turn can be quite acute/obtuse causing a delay in the prompt.
For Some like 156, I would add that right turn slip lane as you want the prompt at that turning point, not the intersection 40 metres away.

We had also kept things “simple” without the AGCs in the early days of lane guidance (an R4 thing ATM), but we now have better ability to place the LG we want where.

If you’d like to give it a shot at draw them in (and disable to right at the intersection node), I’ve unlocked the following.

https://waze.com/en-GB/editor?env=usa&lat=49.04263&lon=-122.78901&marker=true&zoomLevel=19&segments=527535294,527535295

https://waze.com/en-GB/editor?env=usa&lat=49.04263&lon=-122.78901&marker=true&zoomLevel=19&segments=525538362,527535289,527535288

Because you’ll be splitting the main segment, you’ll need to provide new permalinks of those suggestions when they’re ready for relocking.

[WRWazy]

Thank you. I tried drawing it in, but when I click save I get the error, “You have no permissions to make some of the changes Suggestion: Check and try again” I’m not sure what I’m doing wrong?

I basically clicked the + symbol, and added a new road, and then drew the ACG. I then changed it to A-B only direction, and it said there were 2 changes to save. But when I clicked Save it gave that error?

[BryceCampbell]

whoops, thats my bad - I unlocked the wrong King George segments.

[WRWazy]

Using the layers, it looks like I still do not have editing capability on this area as my drive didn’t register. Any chance you could fix it?

Thank you!