Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.
Post by Paulvdwyn
berestovskyy wrote:Hi guys!

A minor update:

v2020.10.25:
- davidakachaos: updated Wiki links for BE/NL
Most of the Wiki links for Be don't work. Where can I change them?
Paulvdwyn
Waze Global Champs
Waze Global Champs
Posts: 791
Has thanked: 57 times
Been thanked: 75 times
Send a message

Post by Paulvdwyn
berestovskyy wrote:The source code and built in localization files are all on GitHub:
https://github.com/WMEValidator/

I’ll help if you have any questions.
Thanks,

Can I edit this file or who is responsible for the Belgium updates?
Paulvdwyn
Waze Global Champs
Waze Global Champs
Posts: 791
Has thanked: 57 times
Been thanked: 75 times
Send a message

Post by PesachZ
bummerdude69 wrote:- Should there be a check for elevation? I'm thinking everything 'should' be Ground (0), unless it's actually going over/ under something (except railroads, etc).

- I'm using custom Template ${elevation} and RegExp D!/0/ Is there a better way to check for elevation?

Thanks
As sketch mentioned, Toolbox does already do this (light green >Ground, light red <Ground
PesachZ
Wiki Master
Wiki Master
Posts: 4518
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
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

Post by PesachZ
CBenson wrote:We were changing self connectivity at dead ends before the direct ability to edit them was in the editor and most seem to be continuing to do so now. If the underlying routing issues have not changed, I don't see why the validator check should change. Its no different than warning us about reverse connectivity on one way roads, which can't be directly edited in editor either.
Only because pass asked is to stop disallowing the u-turns at dead end nodes, so that they can see if their fix is working, and tweak it to work better anytime, its found to have failed. This will only be possible though if the turns are allowed, and we rely on the algorithm to control it. Having then allowed will also fix other minor routing buffs discussed in the new WME feedback thread.
PesachZ
Wiki Master
Wiki Master
Posts: 4518
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
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

Post by PesachZ
CBenson wrote:
PesachZ wrote:Only because pass asked is to stop disallowing the u-turns at dead end nodes, so that they can see if their fix is working, and tweak it to work better anytime, its found to have failed.
Has staff actually clearly stated this, because if so I missed it? I continue to see the same issues I always have with u-turns allowed at dead end nodes. I also see no change with those that are currently disallowed. If turns aren't allowed now and they have removed the ability to directly edit them, then how do they expect the turns to be allowed for testing? There was some talk about them being all allowed with the removal of the ability to edit, but that doesn't appear to be the case to me.
It was implied by several champs here
PesachZ
Wiki Master
Wiki Master
Posts: 4518
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
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

Post by PesachZ
Poncewattle wrote:
CBenson wrote: I find it now somewhat critical that this indication remain in Validator so I can troubleshoot and report problems with enabled or disabled dead-end roads.
Right now the validator reports it as a (yellow) warning if the u-turn is enabled to get around the bug documented in the wiki that says "Due to a bug in Waze, we need to make sure that Waze thinks that a U-turn is not allowed on a dead-end, even though in reality it must be." (which was before they hid it from us of course):

https://wiki.waze.com/wiki/Map_Editing_ ... nd-streets

What I am inferring from what I hear you saying is, iff Waze ever fixes that bug, then the validator should then be changed to report it as an error for the OPPOSITE condition -- if the u-turn is in fact disabled, since after the bug is fixed the u-turns in most cases should in fact be ENABLED.

Am I understanding this right?
It would seem given the new stance from Waze that this wiki should be changed. I will bring this up in the wiki update forum.

EDIT: Scratch that, the wiki you quoted has already been updated to read
wiki wrote:As of July 2014, U-turns at dead ends or cul-de-sacs, no longer need to be adjusted in a particular way. WME no longer provides a link to adjust it.
PesachZ
Wiki Master
Wiki Master
Posts: 4518
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
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

Post by PesachZ
All the U-turns and unconfirmed turn highlighting has been removed. Thank you.
PesachZ
Wiki Master
Wiki Master
Posts: 4518
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
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

Post by PesachZ
doomedtx wrote:FWIW, in my work Chrome install I had to remove the script and re-install it. There was no obvious way to upgrade from 1.0.2 to 1.0.3. It's probably because the browsing restrictions at work prevented automatic upgrading.

(So I can edit during my lunch break and never while I'm being paid to be here) ;)
Chrome updates automatically on a schedule, if you want to force an update you have to go into the Extensions tab, enable developer mode, and click the button at the top to update extensions. Otherwise it will update on its own after several hours.
PesachZ
Wiki Master
Wiki Master
Posts: 4518
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
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

Post by PesachZ
marcedli wrote:
iainhouse wrote:
PesachZ wrote:All the U-turns and unconfirmed turn highlighting has been removed. Thank you.
Could we please have the highlighting of dead-end u-turns turned back on for the UK, please?

As discussed elsewhere on the forums, we still consider them a real problem. We had Waze mass-disable every u-turn on the UK map. Unfortunately, the routing engine keeps enabling new ones where the disabled u-turn is "soft". With the arrows already removed, it will be difficult to diagnose problems involving u-turns unless we can see them, not to mention the routing problems we still see them causing.
anyway...why are these features removed?

please explain
Because the Waze staff Ohad and Noam have asked us in the feedback thread for the WME v1.6 to no longer manipulate the turns on dead end nodes. The functionality to adjust those U-turns and soft turns has been removed from the WME UI with the latest to discourage editors from trying to change them, but validator was still highlighting them as a problem. Being highlighted was causing many editors to try and find workarounds to change the turns to keep validator happy. So they were removed from validator, to comply with the vision Waze staff have for the map.

For more detailed info about why this change has been made see the WME feedback thread.
PesachZ
Wiki Master
Wiki Master
Posts: 4518
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
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

Post by PesachZ
ispyisail wrote:
No, not yet anyway, as this goes against staff's express wishes. So far I believe the UK is the only country to get any sort of special permission from staff to leave them off.
Can you link to any reference for this?

I just want to go through the logic

and the reason why wazeHQ thinks it OK for the UK?
The conversation regarding u-turns at dead end segments has been happening in the WME v1.6 feedback thread. Here is the latest posting from staff regarding the UK exception


redviper26 wrote:
Dave2084 wrote: This whole conversation is at odds with the understanding the UK Champs have regarding dead end U-Turns.

The UK Champs asked Waze to run a job a few months ago which disabled every dead end U-Turn in the UK. It soon became evident that (misguided) users would enable them again and re-introduce the routing errors that come with them since the Waze client has no U-Turn instruction. This is one of the reasons (if not the main reason) behind the disabling of U-Turns on a dead end node in WME.
The situation in the UK is unique, and we did disable U-turns there following the community's request. For other countries, U-turns should be left as they are, and we intend to enable them in the future.

Thanks,

Noam
PesachZ
Wiki Master
Wiki Master
Posts: 4518
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
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