Wazeopedia.png

Wazeopedia

USA

MobileDiff/167992

Roundabouts

51 bytes removed, 4 months ago
changed AGC to bypass throughout last section
In general, it's only appropriate to connect multiple segments to a single node of a roundabout if the exit leaves the roundabout to the left of the entry, such as, for example, both directions of a divided highway meeting at one node. This will be treated exactly like a single two-way segment in navigation instructions.
Do not connect an entry belonging to one road to or past an exit belonging to the next road to the right, as this causes the first exit not to be counted and the subsequent exits to be numbered incorrectly. Even if the movement into and out of the roundabout is prohibited at this point (often the case in [[#At-grade connector|roundabouts with at-grade connectorsbypasses]]), if it is physically possible, users will tend to count it as the first exit, and we need to provide a consistent experience when mapping.
Do not connect more than one exit (either two-way segments or outgoing one-way segments) to the same node at a roundabout, as this causes Waze not to number any exit. In these cases Waze will show an empty circle for the roundabout instruction and will simply truncate the spoken instruction to "at the roundabout."
==Moving junctions and disconnecting roads==
When adjusting roundabouts, drag the junction nodes and move/delete the geometry points of the segments. Do not disconnect or reconnect roads just to adjust angles. Apart from the loss of turn data that happens with disconnections, some nodes can't be deleted from roundabouts, and changing segment IDs within them (caused by cutting and merging) can cause them not to work properly.{{ReturnTo | Editing manual | the editing manual}}
==At-grade connectorBypass==Some roundabouts are designed with physically separated '''bypass roads''' or '''[[at-grade connectors]] (AGCs)'''. In many cases, roundabout at-grade connectors bypasses can be mapped just like any other, but some roundabouts with AGCs bypasses have persistent routing problems.
=== Correcting inappropriate avoidance of roundabout AGCs bypasses ===
[[File:RA-bad.png|thumb|The example on the left had entrances of one road connected to exits of a different road at the same nodes, and it gave incorrect normal instructions. The example on the right had entrances of one road connected past exits of the next road, and it gave incorrectly numbered non-normal instructions.]]<!--
-->Where AGCs bypasses have been built to allow right-turning or straight traffic to avoid the roundabout altogether, Waze might send traffic through the roundabout anyway, if Waze thinks the roundabout is even a few seconds faster at a certain time of day. If there are any difficulties with assigning traffic to the correct segments at this junction, Waze may be incorrect. This is often confusing to drivers when it is contrary to regulatory or informative signs.
Junction boxes cannot be applied to control turns in roundabouts, so other approaches have been explored.
Do not move the incoming segment after the outgoing segment to make Waze avoid the exit. This is also a distortion if the roundabout and can cause incorrect roundabout instructions,
{{Mbox|type=warning|text=Because the following solutions are hacks, do not use them unless improper avoidance of the at-grade connector bypass has been persistently demonstrated in real route testing; work under the supervision of local leadership.}}
====Fake U-turn prevention====
====Fake or real detour prevention====
[[File:RA-BDP.png|thumb|US-41 S is the continuous name coming from the west, bypassing the roundabout and continuing south on all {{Major Highway|MH}} segments. The segment from the roundabout going south is unnamed and has the {{Minor Highway|mH+1}} type, so the movement from US-41 S, into the roundabout and back out to US-41 S is penalized as a detour.]]<!-- -->Another solution is to activate the [[Detour Prevention Mechanisms#Big detours|big detour penalty]]. This treats the movement into and out at the next exit as a detour away from the AGCbypass. To use:# Make sure that the segment before the AGCbypass, the AGC bypass and the segment after the AGC bypass all share a name.#* If no real named or numbered road continues through the AGCbypass, a fake alt name can be used, such as "BDP" or "roundabout hack."#* A [[turn instruction override]] will probably be necessary to force a turn instruction into the AGCbypass.
# Make sure that these three segments all share the same road type group.
# Along the path to be avoided, select the entrance segment that leads from the roundabout to the end of the AGC bypass (the last segment of the detour), remove all names (they will be [[Navigation instructions for unnamed segments|inherited]] in instructions from other entrances) and change the road type to be of a different group from the AGC bypass and its bracketing segments.
## To ensure proper pruning behavior, the [[Road types#Routing road type|routing road type]] of this segment may be adjusted to match those it connects.
If all detour criteria are met, a significant penalty will be applied to the movement away from the at-grade connectorbypass, through the roundabout and back, causing the at-grade connector bypass to be preferred in routing.
This solution makes sense when the roundabout path is truly a detour from the highway (the segment or segments bypassing the roundabout are part of the carry a numbered highway, rather than being AGCs). It cannot be used if the roads connected by the AGC bypass are not highways, or if one is a minor highway and the other is a major highway or freeway road type.
1,269
edits