Switch to full style
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.

Forum rules

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

DO NOT START a new thread unless it is about a new idea. Keep discussion of existing tools within the main thread for that tool.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.
Post a reply

Re: elevation -5 must be used exclusively for railroads

Tue Feb 04, 2014 8:02 pm

sketch wrote:Where?
...
https://www.waze.com/wiki/Road_Types_(USA)


Yes, I quoted from the Railroad section. Of course, -5 is guaranteed to be different from any road it crosses.

Re: unneded nodes

Wed Feb 05, 2014 9:17 pm

Previously, unneeded nodes were reported for those used for change of elevation and road type also. I haven't re-tested.

Re: [Script] WME Validator 0.6.1 (BETA) / 05.02.2014

Wed Feb 05, 2014 9:22 pm

As for me, I like having a node at the gate. It makes it easier to find the point of access control between the public side and the private side even though there might be no reason to drive up to the gate when it is closed and it makes an "unneeded" node.

Re: WME Validator FAQ

Thu Feb 06, 2014 1:26 am

Please update the FAQ. In particular, it should not use the word flashing.

Re: same end points is insufficient to find overlays

Fri Feb 07, 2014 10:29 pm

berestovskyy wrote:- DISABLED for ALL: 'Same endpoints drivable segments'


I still receive this warning for segments with very distinct paths, often with one being much longer than the other. I think Kent is correct. It matters when the geometry of one segment is completely overlapped by the geometry of other segments. If the segments are several meters apart, then one cannot hide the other.

A segment which has a geometry point at least 5 m from any point along any other segment cannot be hidden by that segment.

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Fri Feb 07, 2014 11:22 pm

berestovskyy wrote:It was enabled back in 0.5.8. At the moment this check does not report roundabouts.

I think it should not report any unless one of the junction angles is 0. I see the error when the junction angles are 90 degrees or more.

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Sat Feb 08, 2014 4:05 am

enhket wrote:what would be superb is if validator was able to suggest people to "downgrade" or "upgrade" a road type based in road classification rules and ... speed


This would be quite easy to do. But it is not something that we would want where roads are classified by function not speed.

Perhaps the branch to take here is to make an api for the Validator so that people can customize what validations they want. It should be easy to insert your function CustomValidations() into the array of functions that Validator calls for each segment. People could script and share all the "validations" they like.

Re: parallel paths to the same endpoints

Sun Feb 09, 2014 9:38 pm

sketch wrote:it's because of known navigation errors when segments share end-nodes.


Let's consider first a one-way terminal loop.

What is the known navigation error in this situation?
How do you correct it?

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Thu Feb 13, 2014 2:49 am

robindlc wrote:Do you think it could be possible to link the language of Validator to the one selected in the WME


This could be a problem because as I understand localization, the rules applicable to roads in Spain cite the Spanish wiki and the corresponding validation messages are in Spanish.

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Sat Feb 15, 2014 6:07 am

ituajr wrote:Does this mean errors on nodes outside the user's editable area are not supposed to be flagged?

Please specify that you checked the option "Exclude non-editable segments".
Post a reply