sounds good. thank you.
Based on feedback received in discord USA wazeopedia channel, I have made more changes. Please give more feedback. on the introduction and criteria for BDP. Thanks.
I won’t be around here much in December. Please continue without me.
I think it is best to get the most up-to-date information about the BDP rules out there as soon as possible. If the text is good enough, please make it live.
We can add pictures later, fix the notes later.
Happy Hannukah, Merry Christmas, Happy New Year!
I don’t have enough time to go over this too carefully, but a quick note – instead of saying “currently, a full continuity check is in place” I would urge use of the {{As of}} template documented here:
https://wazeopedia.waze.com/wiki/Commons/Template:As_of/doc
Not only does this help the reader understand how possible it is that things have changed since the documentation was written, it also provides an easy means for documentation maintainers to find potentially dated guidance.
The {{As of}} template is appropriate anywhere one would otherwise be tempted to use the word “currently” or insert a hard-coded date.
I have added the {{as of}} template, changed a couple capitalizations like waze to Waze, moved one phrase for better flow, corrected a bit of redundancy, and moved voludu2’s draft to the detour prevention page. Thanks for all your work on this!
Thank you to everyone who made a hands-on contribution to getting this page out.
I made the following changes to the page, to make clear that it is the road type group of the last segment before and first segment after the possible detour which determines the max detour length for BDP.
Thanks for the clarification, I’d offer one slight wordsmith, below.
I’d make the change myself as I think it is non-controversial, but for some reason my edit-wiki view contains many buttons labeled in, apparently, Samoan (or Fijian?). I could figure it out and have done so several times before, but I don’t feel like it right now :mrgreen: There’s probably a :ugeek: fix that most people already know, if someone takes pity on me perhaps they could clue me in.
Thanks. I made the suggested change.
To fix your language on the USA wazeopedia:
Go to https://wazeopedia.waze.com/wiki/USA/Special:Preferences
In the second box from the top, you can choose your language.
It’s hard to know how to get there if you can’t read the links!
You’re a lifesaver voludu2, thanks. Yes, it didn’t occur to me to click on “Na Vosa Vakaviti” to change the language! How Wazeopedia decided I’d prefer to interact in Fijian is beyond me.
Some wordsmithing has been going on from the top down to the section headed “Criteria”.
Please compare the current version to the draft at https://wazeopedia.waze.com/wiki/USA/index.php?title=User:Voludu2/Detour_Prevention_Mechanisms
Is this getting easier to read? Is it repetitious to give the definitions of detour, direct route, and alternate route twice?
I like the definitions, except that you define direct route two different ways. One of them is logical (what most users would expect) and one is how the routing server sees it (full name and type continuity). We may want to use different terms for those two things.
Additionally, I have done further testing nearby and confirmed with PZ that my results show that a detour is only checked for name and type discontinuity between its last segment and the first segment after the detour, probably to conserve computing resources. I think we should include an “as of” phrase in the detour discontinuity subsections, just like what is in the subsection on the direct route that says Waze does a full continuity check on it. As we know, BDP can change, but at least we can say that for now the direct route gets a full continuity check, while the detour only gets the last segment checked. I really like how the page defines the concepts of name and type continuity but gives a little flexibility in case the algorithm is changed again.
The definitions at the top are meant as introductions so the reader understands the terms. The criteria give the nitty-gritty details, to the best of our knowledge. I don’t know whether or not the criteria is giving things “as the routing server sees it” because I don’t know in which order it checkes everything.
Do you think there is some simple way to make this more clear?
To me, it seems pretty clear, so I think I need somebody else’s input.
I’ll look forward to your proposed rewording of the criteria with the “as of” statement.
BDP has been such a moving target. While I was doing this rewrite, I had to list three different versions of the continuity checks listed for the direct route and try to decide what to do about it.
As for definitions, I would do the same thing with direct route that you did with detour vs. preventable detour. Just like not all detours will be penalized, not all direct routes (i.e. continuous routes that most users would expect to use) will be recognized by the detour prevention algorithm, especially now that it is checking for full name and type continuity. I would call criterion III “Confirmed direct route” to indicate that it is a direct route that has been confirmed to be valid for the purposes of detour penalization.
As for the discontinuity checks, I like what is written now, but I think we should append this statement to both IIa and IIb:
Then we would have accurate and easily-understood info! We could even add a statement at the end of the criteria section saying something like
That sounds like it would work. And it doesn’t change the numbering, which some readers who are trying to learn BDP from this page may appreciate.
And using similar naming for both routes seems liek it will make the whole thing easier to understand, too.
Let’s try to get some opinions on this change, and if we don’t get any objections, make it so.
Quick note: need to remove references to Shortest route, since this has been removed from the app.
I’ll have more to say on this page in the near future. (not intending to sound ominous)
Done. What else you got, Tony?
Changes have been made to the draft Voludu2 has been working on. It is hosted on their user page here: https://wazeopedia.waze.com/wiki/USA/User:Voludu2/Detour_Prevention_Mechanisms.
The primary changes:
Overall:
-
Changed the definition of “BDP” to be consistent throughout as “big detour prevention” and used “big detour prevention (BDP) penalty” where applicable.
-
Criteria:
-
Updated to reflect the latest changes, based on testing conducted by Kartografer, with input from PesachZ
-
Wording has been clarified and a flowchart added - please comment on how understandable the latest version is.
-
Added the term bracketing segments to define the segments immediately before and immediately after a detour. This term is used in the criteria section as well as the flowchart. Note: this term is confined to BDP only and is not intended for overall glossary inclusion.
Primarily all changes are within the Criteria section. This is the section we are looking for feedback on. The “Notes” section and SDP (small detour prevention) have not been updated at this time and do not need feedback.
My first comments, on a quick read:
- This is, so far, big steps forward. Nice work!
- I would very much prefer calling a “preventable detour” a “penalized detour”, in order to further enforce the concept that BDP is not, strictly, detour prevention, rather, detour discouragement. I realize that naming was done in an effort for consistency, but I’ll vote for most opportunities to un-confuse people. The usage, elsewhere in the page, of the word, “penalty” is a huge step in the right direction, but some people have a tendency to read right past things like that, when not called out.
Sent from my Pixel using Tapatalk
The only issue with calling it a “penalized detour” is that it isn’t necessarily penalized at that point. If there isn’t a alternate route that is direct, the detour is not penalized.
Sent from my iPhone using Tapatalk