I missed that we had absolute confirmation this was the case. Assuming that's true, I believe we can find words to convey that. I can take a shot if you confirm.CBenson wrote:My understanding is the description of hard turns was written when it was simply a very high penalty and waze would route through a hard restriction if that was the only way to get to the closest segment to the destination. How do we edit the page to make it clear that no longer happens?
USA: Now Idaho; previously California (Northern, SF/SJ)
https://s.waze.tools/gc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/wiki.pnghttps://s.waze.tools/ccp.pnghttps://s.waze.tools/s1000.pnghttps://s.waze.tools/p2000.pnghttps://s.waze.tools/c6s.png
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
https://s.waze.tools/gc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/wiki.pnghttps://s.waze.tools/ccp.pnghttps://s.waze.tools/s1000.pnghttps://s.waze.tools/p2000.pnghttps://s.waze.tools/c6s.png
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
I missed that detail in the OP when catching up on the thread.
I'll take a shot at some adjusted wording once I get some free time (unless someone beats me to it).
I'll take a shot at some adjusted wording once I get some free time (unless someone beats me to it).
USA: Now Idaho; previously California (Northern, SF/SJ)
https://s.waze.tools/gc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/wiki.pnghttps://s.waze.tools/ccp.pnghttps://s.waze.tools/s1000.pnghttps://s.waze.tools/p2000.pnghttps://s.waze.tools/c6s.png
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
https://s.waze.tools/gc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/wiki.pnghttps://s.waze.tools/ccp.pnghttps://s.waze.tools/s1000.pnghttps://s.waze.tools/p2000.pnghttps://s.waze.tools/c6s.png
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
I propose that we accept these changes from CBenson and incorporate them into the standard page.
https://wiki.waze.com/wiki/index.php?ti ... did=128845
https://wiki.waze.com/wiki/index.php?ti ... did=128845
USA: Now Idaho; previously California (Northern, SF/SJ)
https://s.waze.tools/gc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/wiki.pnghttps://s.waze.tools/ccp.pnghttps://s.waze.tools/s1000.pnghttps://s.waze.tools/p2000.pnghttps://s.waze.tools/c6s.png
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
https://s.waze.tools/gc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/wiki.pnghttps://s.waze.tools/ccp.pnghttps://s.waze.tools/s1000.pnghttps://s.waze.tools/p2000.pnghttps://s.waze.tools/c6s.png
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
What does waze do when the destination is closest to a connected segment with all inbound turns restricted. Will it route to the junction, the next closest segment, something completely random, or fail entirely?CBenson wrote:So at this point it would seem that no segment should have all turns to access it restricted. It would seem that if no vehicles can access a segment then it shouldn't be mapped as a driveable segment. If we say this on the page we could then point out that a result of erroneously restricting all turns onto a segment is that it will not be used as the destination for any routes. Does this sound correct to everybody?
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
It used to be a penalty, but has been changed now and according to Karen is now impossible.deeploz wrote:WonderLerm wrote: "Restricted turns should be 100% restricted. Under no circumstance should we route through them. Private roads, referenced in the discussions, are a completely different thing. There we do have a penalty."So if it is not a penalty matter, what is is exactly ?CBenson wrote:But the point of this change is that the hard turn restriction isn't really a penalty anymore.
Can we say that the routing engine consider a hard turn restriction as the same "level of impossible routing" than if the destination segment was disconnected (i.e. no segment connectivity) ?
Because we know, for sure, that Waze has never proposed a route through the void between two disconnected segment. But (even if never experienced it personally) some have reported that, in certain circumstances, a route was proposed through a hard turn restriction. Or is it only an editor's legend ?
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
What it definitely means is that if such a turn is routed through, it is definitely a bug. As opposed to penalized turns where it may be WAD.
Sent from Android using Tapatalk
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Correct, soft turns can still be overridden.
On the "nearest routable segment" - do we have any documented confirmation, either from a test bed or from dev?
Also, to complete the loop, this topic is now intertwined with the following one: viewtopic.php?f=276&t=144250&view=unread#p1270367
On the "nearest routable segment" - do we have any documented confirmation, either from a test bed or from dev?
Also, to complete the loop, this topic is now intertwined with the following one: viewtopic.php?f=276&t=144250&view=unread#p1270367
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
I had a segment time restriction that somebody had messed up and placed. Ramapo, I think. It was the main access road to a development, no other way in or out. Waze routed to a somewhat random spot on a nearby road. Wasn't to the closest junction or I think even to the closest segment on the route to the junction, but it was RELATIVELY close to the destination.
Not 100% same circumstances, but quite similar.
Not 100% same circumstances, but quite similar.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
I'm fine with the changes. I suspect we could be more direct and describe it something like this:
Waze always calculates several possible routes, and selects the best one, usually by how long each route takes to complete. Waze is also aware that certain possible routing decisions (certains streets or turns or other maneuvers) may be undesirable. It will penalize such routing decisions by adding a certain amount of time to the route to compensate for the unwanted behavior. If the undesirable route, by adding this penalty time, becomes longer than the unpenalized route, then the longer-unpenalized route will be favored over the shorter-penalized route.
A single route can have multiple penalties - for example, routing through a parking lot at the beginning of the route, and then later routing off a highway and back on (exit and immediately reenter), perhaps repeating this several times. Each of these undesirable behaviors will add time to the route, and the cumulative time of the actual route and all/ its total penalties is the total route cost for calculating the preferred route for a trip.
Note that the complete list of penalized maneuvers, and the amount of penalty for each, is proprietary to Waze, and much of it has not been revealed publicly. Also note that the times displayed to end users for both route selection and route progress do not include the penalty times; the displayed route time is always the actual trip length calculation without penalties.
Waze always calculates several possible routes, and selects the best one, usually by how long each route takes to complete. Waze is also aware that certain possible routing decisions (certains streets or turns or other maneuvers) may be undesirable. It will penalize such routing decisions by adding a certain amount of time to the route to compensate for the unwanted behavior. If the undesirable route, by adding this penalty time, becomes longer than the unpenalized route, then the longer-unpenalized route will be favored over the shorter-penalized route.
A single route can have multiple penalties - for example, routing through a parking lot at the beginning of the route, and then later routing off a highway and back on (exit and immediately reenter), perhaps repeating this several times. Each of these undesirable behaviors will add time to the route, and the cumulative time of the actual route and all/ its total penalties is the total route cost for calculating the preferred route for a trip.
Note that the complete list of penalized maneuvers, and the amount of penalty for each, is proprietary to Waze, and much of it has not been revealed publicly. Also note that the times displayed to end users for both route selection and route progress do not include the penalty times; the displayed route time is always the actual trip length calculation without penalties.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
Well, the 100%-confirmation-statement uses the standard escape-word "should", does that mean there might still be conditions where the accuracy of the statement is restricted
https://storage.googleapis.com/wazeoped ... gnatur.jpg
AM Region Hannover, CM Deutschland (Germany), Global Champ
Wiki Deutschland | Straßen und Orte benennen D | Karte bearbeiten | Editorbedienung
AM Region Hannover, CM Deutschland (Germany), Global Champ
Wiki Deutschland | Straßen und Orte benennen D | Karte bearbeiten | Editorbedienung
Re: Waze Bug or Wiki Inaccurate on Restricted Turns