Is the Validator encrypted or only minify?
Validator always reports "No Type Set" for Parking Lots, e.g. here
Bill Walton
https://sign.waze.tools/beta.pnghttps://sign.waze.tools/betc.pnghttps://s.waze.tools/s0100.pnghttps://sign.waze.tools/c3s.pnghttps://s.waze.tools/am.png
https://sign.waze.tools/beta.pnghttps://sign.waze.tools/betc.pnghttps://s.waze.tools/s0100.pnghttps://sign.waze.tools/c3s.pnghttps://s.waze.tools/am.png
https://www.waze.com/editor/?zoom=7&lat ... s=47698044
Validator flags the segment with a 'turn too sharp' at the north end when that end has the restricted turn (yellow) 24/7, but passes it when the turn is forbidden (red).
I am not sure this behavior is bad, but it seemed a bit strange.
Validator flags the segment with a 'turn too sharp' at the north end when that end has the restricted turn (yellow) 24/7, but passes it when the turn is forbidden (red).
I am not sure this behavior is bad, but it seemed a bit strange.
Area Manager, Louisiana https://media.discordapp.net/attachment ... nknown.png
In the hope that someone 'killing red arrows' would be less likely to 'enable all turns' there.jemay wrote:....
Why set it as TBTR (24/7) when it should be just a red arrow?
(yeah, I know I can just lock it, but 'stuff happens' sometimes. And I wanted to see how well the idea works. When I noticed the slightly strange validator action, I thought I'd report it.)
Area Manager, Louisiana https://media.discordapp.net/attachment ... nknown.png
constant 'too many issues reported' flag showing up when any segment selected.
Area Manager, Louisiana https://media.discordapp.net/attachment ... nknown.png
Clearing the report does not remove the message. It pops up ANYTIME I select any segment in the Houston texas area.
Area Manager, Louisiana https://media.discordapp.net/attachment ... nknown.png
The bug fix fixed it.
Area Manager, Louisiana https://media.discordapp.net/attachment ... nknown.png
I think the point was that IF the segment is locked above YOUR level (so you can't touch it anyway, without help) AND it has been updated recently, THEN it won't be flagged.olestas wrote:Sorry, did not see that discussion. And no one seemed to discuss it actuallySo you will get the issues on the "old" locked segments, but never on recently updated segments.
I don't think new updated and locked segments should not be touched. Higher level users also make errors, and don't always leave the best of it all.
That way, you don't see a bunch of 'errors' that YOU can't fix.
In other words, higher level editors will still see the errors flagged.
Area Manager, Louisiana https://media.discordapp.net/attachment ... nknown.png
But the problem is that many of those problems are 'false positives' that lower level editors don't have the experience to ignore.olestas wrote:The problem is.. If I don't report the problem.. no one will
Validator can't distinguish them from valid errors.
Perhaps the option to hid them should be an 'on by default' option that can be turned off by 'skilled lower level editors' that are able to tell which need to be passed on for fixing.
Area Manager, Louisiana https://media.discordapp.net/attachment ... nknown.png
Is it possible to add a custom template field for {editorID} or {CreatedBy} {EditedBy} ?
so we could do something like
${EditedBy}
/(user1|user2|user3)$/i
to highlight segments edited by any of a list of editors?
so we could do something like
${EditedBy}
/(user1|user2|user3)$/i
to highlight segments edited by any of a list of editors?
Area Manager, Louisiana https://media.discordapp.net/attachment ... nknown.png
Re: [Script] WME Validator 1.1.20 / 03.11.2016