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
Sat Oct 18, 2014 7:04 pm
Referencing this thread: https://www.waze.com/forum/viewtopic.php?f=8&t=112938
Is there any way Validator could check for a segment that is in the opposite direction of the ones surrounding it, perhaps limited to minor highways and above? Bugs like the one in the thread above have very significant routing implications and given the lack of user feedback, tracking these down is tedious and difficult to say the least.
That is a great idea, I wouldn't even want to see it limited to mH and above. It not that common for one-way roads to converge or separate outside of parking lots... but even then, this is something that should be looked at. It's not like the map would be covered with highlights.
Perhaps an option to ignore roads below "xxxxxx" so PLRs and private roads can be ignored manually.
Sun Oct 19, 2014 12:43 am
bart99gt wrote:My thought was that in an area that hasn't seen the light of an editor it may return a ton of errors on ordinary surface streets where the street directions are all out of whack. Since mH and above would be the most critical to routing, I thought that may be a good start, or at least as you mention, offer some kind of toggle to allow all street types to be considered if you wanted.
True, but we need to have those issues on the local roads brought to our attention as well.
Any editor working with MH would likely be L3+ and would have the understanding that the MH/mH/Primary need attention first.
Wed Oct 29, 2014 3:21 am
Separate the highlights and listings in the report for "one way" and "toll"
We have a BUNCH of split roads, so we have a lot of legitimate one-way, but we have very, very few legitimate "toll" roads and none that are editable by L4 and below.
I am frequently catching the "toll" flag set incorrectly, but Validator is not helpful in locating them.
Thu Oct 30, 2014 7:41 pm
Also, I seem to have lost the "No inward/outward connectivity of a driveable road"
I'm assuming this has to do with the WME changes that changed the attachment the turn restrictions to the junction vs segment (same thing that killed RevCon detections).
I'm hoping that this will be restored soon.
Fri Nov 07, 2014 4:12 am
ispyisail wrote:It appears that validator no longer finds disabled turn restrictions?
If this is true, is this a known issue?
The most Validator ever did was "No Inward/Outward Connectivity of a driveable road" but it only takes one permitted turn into and out of each 2-way junction (or one permitted turn either into or out of each 1-way junction) to quash that alert.
This, like the check for Revcons, was "broken" during the WME update a couple of months ago (the one that broke nearly every feature of Toolbox) because it changed how the turn restrictions were attached to the segment vs junction.
I don't think Validator itself ever alerted on turn restrictions in general.
The screencap in your message is the result of using Shift-Z and is a part of WME and has always worked.
Edit: On the N/A server... I can't say with any certainty on the ROTW server.
Fri Nov 07, 2014 4:32 am
Ya, I mentioned it a couple of days ago. I haven't seen it discussed before.
Fri Nov 07, 2014 4:38 am
"Known issue" as in I'm sure berestovskyy is aware that it was one of the functions broken.
Toolbox can reveal Revcons, that was nice when it was fixed, but improperly set turn restrictions are a big problem. We've also had a rash of new editors and they often are not setting turn restrictions properly, but if the segments are clean enough to not display on the Validator report, more experienced editors often miss them until the URs come in.
Last edited by taco909
on Fri Nov 07, 2014 4:47 am, edited 1 time in total.
Tue Nov 11, 2014 9:24 pm
CBenson wrote:They are highlighting for me here.
Mon Nov 24, 2014 5:52 am
SiewMeng98 wrote:The new version of the Validator when used for checking large areas - it stops and we have to press the report button and the play again to continue. Before this we did not need to. Is there any limitations to the number of segments built in or any zoom level where it would work optimally without having 3 or 4 breaks.
It's always been like this... at least since June.
For this reason, I generally don't run it at zoom-0, but it works just fine if you work the report, then continue.
As long as you aren't using Chrome
Sat Dec 06, 2014 4:34 am
I've been getting that issue off and on ever since the big WME update that broke just about every tool we have.
Powered by phpBB © phpBB Group.
phpBB Mobile / SEO by Artodia.