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 petervdveen
Question about the error 'too short segment'.
If I'm correct all segments should be longer then 5 meters. So 6 is the minimum.
I'm not getting the error anymore if the segment is 4 meters long.
petervdveen
Coordinators
Coordinators
Posts: 10370
Has thanked: 212 times
Been thanked: 847 times
Send a message
Coordinator Waze Netherlands

Click here to sign-up for slack, our communication platform

Contact by email: NL - BE - Lux - Benelux

Post by petervdveen
berestovskyy wrote:Let me know if I shall increase the value for the too short segments for BeNeLux.
I would change it globally.
Waze has stated in the globalchamps forum that segments should never be shorter than 5 meters (so 6 meters as safe minimum) because of routing problems.

Even at complex junctions 6 meters is the minimum in my opinion.

For benelux change it to 6 meters as minimum (so 0-5 meters should give a report), but my advice is to enable it globally. ;)
petervdveen
Coordinators
Coordinators
Posts: 10370
Has thanked: 212 times
Been thanked: 847 times
Send a message
Coordinator Waze Netherlands

Click here to sign-up for slack, our communication platform

Contact by email: NL - BE - Lux - Benelux

Post by petervdveen
Look at this page:
https://wiki.waze.com/wiki/Minimum_segment_length

The minimum segment length is 5 meters.
I would like to have a minimum of 6 meters (to be sure) in the benelux.
petervdveen
Coordinators
Coordinators
Posts: 10370
Has thanked: 212 times
Been thanked: 847 times
Send a message
Coordinator Waze Netherlands

Click here to sign-up for slack, our communication platform

Contact by email: NL - BE - Lux - Benelux

Post by petervdveen
ˆˆ Maybe this could be made an option?
petervdveen
Coordinators
Coordinators
Posts: 10370
Has thanked: 212 times
Been thanked: 847 times
Send a message
Coordinator Waze Netherlands

Click here to sign-up for slack, our communication platform

Contact by email: NL - BE - Lux - Benelux

Post by PHIL-IP63
Since this morning, after installing the new version of Firefox (44) Validator don't work anymore :cry:
No highlight and it don't appear in the left panel.
Tested on versions 32 and 64 bits of Firefox (and Firefox Beta) and under WME prod and WME Beta
No problem with Chrome.
PHIL-IP63
State Manager
State Manager
Posts: 785
Has thanked: 113 times
Been thanked: 87 times
Send a message

Post by PHIL-IP63
For me on Firefox 46.0.1 I have no problem with the old version 1.1.16, working fine.
But... with the new one 1.1.17 Validator don't work (no display) :(
Very strange.....
PHIL-IP63
State Manager
State Manager
Posts: 785
Has thanked: 113 times
Been thanked: 87 times
Send a message
Last edited by PHIL-IP63 on Thu Jun 02, 2016 5:15 am, edited 1 time in total.

Post by pjlasl
I noticed that street names that begin with numbers (i.e. 8th Steet) are being flagged with the following message: #170 The street name starts with a lowercase word.

I would also exclude the word "to" from the lower case filter selection as shown here
pjlasl
Area Manager
Area Manager
Posts: 378
Has thanked: 12 times
Been thanked: 103 times
Send a message
[img]https:///EcBKq[/img] [img]https:///L6ziL[/img] [img]https:///pIzEJ8[/img]
AM: Texas
CM: USA
Champ: USA
Mentor: USA

Best Practices for Map Editing | Texas Wiki| Unlock Request for US | Mentoring

Post by pjlasl
Found an interesting issue related to #170 (lowercase). The validation is flagging (W L D Lockett Rd) as lower case. See Here
pjlasl
Area Manager
Area Manager
Posts: 378
Has thanked: 12 times
Been thanked: 103 times
Send a message
[img]https:///EcBKq[/img] [img]https:///L6ziL[/img] [img]https:///pIzEJ8[/img]
AM: Texas
CM: USA
Champ: USA
Mentor: USA

Best Practices for Map Editing | Texas Wiki| Unlock Request for US | Mentoring

Post by pjlasl
It appears the latest update to beta has broken Validator :(

When u zoom in, you see everything as shown in the image and validator throws the message that there are "too many issues reported".

This behavior is not present in the normal version.

pjlasl
Area Manager
Area Manager
Posts: 378
Has thanked: 12 times
Been thanked: 103 times
Send a message
[img]https:///EcBKq[/img] [img]https:///L6ziL[/img] [img]https:///pIzEJ8[/img]
AM: Texas
CM: USA
Champ: USA
Mentor: USA

Best Practices for Map Editing | Texas Wiki| Unlock Request for US | Mentoring

Post by pjlasl
I just opened up the new beta editor and after some investigation noticed that everytime I have Validator turned on and the beta editor loads the following error is thrown.

Uncaught TypeError: Cannot read property 'da' of null editor-beta.waze.com/editor/:1

If I turn off the extension, I no longer see this error.
pjlasl
Area Manager
Area Manager
Posts: 378
Has thanked: 12 times
Been thanked: 103 times
Send a message
[img]https:///EcBKq[/img] [img]https:///L6ziL[/img] [img]https:///pIzEJ8[/img]
AM: Texas
CM: USA
Champ: USA
Mentor: USA

Best Practices for Map Editing | Texas Wiki| Unlock Request for US | Mentoring