In the image you can see the message.
Thanks,
You’re right, I’ll take a look.
I’ve also asked that a couple of times ( https://www.waze.com/forum/viewtopic.php?p=812036#p812036 ) but I guess OyyoDams hadn’t had time to figure it out. Or it got lost in the actrive thread 
Does yours fit the reverse a-b b-a theory on the neighbouring segments?
This node is being suppressed by Toolbox even though one of the adjacent segments has a different alternate name. Both segments are in the same A->B direction.
This node is not being suppressed even though both segments have identical attributes, and it is flagged by validator as unneeded. However these segments are in opposing A->B directions.
This error message comes when there are 2 identical city names in a country. This will look something like this:
You will also get a double proposal when manually entering the city name in WME:
Before you ask: no, the two city names are absolutely identical, no extra whitespaces.
This can be solved by either manually changing the city entries of one of the city names, or by requesting for a “Merge city” with the support, using the same current and new city name.
So it’s not a Toolbox bug, it’s a feature! 
@bellhouse Thanks for your answer. I will request that Waze Merge the City.
Is it possible to include an option to see L1 locks? It helps when a segment had its restriction temporarily lowered but for one reason or another it was forgotten as a L1 segment, and nobody notices until it’s too late and something bad happens to the map… 
Aren’t L1 locks by definition everything on the map that’s not L2-L5 locks? Here, 90+% of the map would be highlighted.
That’s right, but there are situations where there is a highway L4 for example, and a specific segment was lowered to L1 so an editor can connect a street to it… the L4 editor simply forgot to reinstate the lock… it’s easier to highlight the L1’s on the map and locate matches on the highway than filtering >L2 and looking for a gap with bare eyes
It even easier to use the select segments tool (green checkmark), and only filter by segment type and lock level, then select all freeway R1 segments in one click. You’ll see how many there are and they will be highlighted. Then you can relock in one step too.
Highlighting R1 locks may put too much strain on the browser.
Hi, all the links to external maps (at least G Maps) that I tried are not working at the moment. Tell me if it is reproduceable or you need more details.
If you’re using Validator, you can use a custom template to highlight incorrectly locked segments. Here in the UK, we have a locking policy that states all Freeway should be locked at 5 and all Major highway should be locked at 4. I use the following in Validator:
- Custom template: ${type}:${lock}
- Custom RegExp: /6:[^4]|3:[^5]/
That will highlight all segments with road type 6 (major highway) that aren’t locked at 4 and all segments with road type 3 (freeway) that aren’t locked at 5.
Note that you need the underscore characters on either side of the road type because there are some 2-digit road types in the map model - and you don’t want to match, say, 3 and 13. If you want to add minor highways, you’ll have to do some experimenting to find out what the internal road type number is for minor highway.
Hi iainhouse, hi PesachZ!
Thank you for your insight on the problem. From your suggestions, the conclusions I can get is:
- There is INDEED better already available solutions than “visually searching for a gap in >L2 segments along a highway”;
- The solution go through table filtering in WME Toolbox (like a dynamic table for those familiar with Excel) or a regexp in Validator;
- Both solutions starts with the premise that the segments lowered to L1 maintained any highway type. If the segment changes to Service, Private or any other, it’s “invisible” to both solutions.
Since the possibility to enable a L1 option to WME Toolbox may possibly put too much strain on browsers (specially on slower machines), the solution for now is adopt either solutions and check routing of highways on a regular basis.
I will think a bit more on the subject and maybe come up with some script specific to that.
Thank you all!
Hi,
They work for me…
I fear I may be getting a little too off-topic here, but I will note that this will also highlight freeways locked at 6 and major highways locked at 5/6 as if they are wrong, when they might just be locked that way for a certain reason.
To highlight MH and Fway locks that are too low (lower than 4 or 5, respectively), with the same template as above, use the following custom regexp:
/6:[^4-6]|3:[^56]/
If the highway segment was changed to a non highway segment it should be very easy to visually locate just based on the default colors of WME for road type. A highway segment will be blue red or yellow, non highway will be white or gray. If you see white or gray along a highway stretch you know you have a problem to fix (or an HOV lane)
Hi, I found out that it “collides” with some of my scripts mostly used by the italian community. With the new editor I had to “prepend” instead of “append” something to the permalink bar to make the link visibile, so toolbox doesn’t find the permalink where it expects it to be (at the first position).
Could you change your code to this to retrieve the permalink? It should be equivalent and maybe more robust.
$('.WazeControlPermalink a.icon-link')[0].href;When I select an segment, the ‘Cut segment’ do ‘add node’ in “random position”. This position is chosen by the script.
I will like to choose the position where the node is added. Like in “insert new segment”.
This would be perfect to define segments that have elevation <> 0.
Thank you.
Ok will be fixed in 1.4.4.1
Thanks for the suggestion. However it’s hard to implement, so not for now.