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 dbraughlr
Previously, unneeded nodes were reported for those used for change of elevation and road type also. I haven't re-tested.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by dbraughlr
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.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by dbraughlr
Please update the FAQ. In particular, it should not use the word flashing.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by dbraughlr
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.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by dbraughlr
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.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by dbraughlr
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.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by dbraughlr
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?
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by dbraughlr
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.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by dbraughlr
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".
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message

Post by dbraughlr
A Railroad segment must not be at a junction with another type.

A Runway/taxiway segment must not be at a junction with another type.

There must not be a junction with any drivable type and any non-drivable type.

A ramp must be connected at both ends and the junction at one end must have a freeway/highway/ramp segment.
dbraughlr
Posts: 569
Has thanked: 164 times
Been thanked: 98 times
Send a message