I’d like to submit a small bug with WME Validator, which has to do with a regex being apparently too broad and reporting a street name in France as containing a wrong abbreviation.
The “Rue du Mal Assis” is reported with “The street name has incorrect abbreviation.”. From what I can tell, WME Validator catches the “Mal” portion and, probably due to the “[Mm]al” portion of the regex, thinks this is an incorrect abbreviation. In this case, though, it’s an actual French word, not an abbreviation.
Is there any way to change that regex to avoid that false positive without breaking anything? If not, it’s fine if it stays like that, it is really minor.
I’m running into a strange issue with user-defined checks, but I’m not sure if it’s due to the order the checks are run. For some reason, when Waze did the base map import, several roads in South Carolina have been assigned to the state of Georgia. I’ve cleaned up most of these, but there are a few stragglers, so I entered the regex /Georgia/ with the template ${state}, ran the report, and got 18 hits. I then thought, “what if there are others that should be set to South Carolina that currently aren’t?” So I changed the regex to !/South Carolina/, ran the report, and got none (using the exact same view)! I ran the initial report (Georgia) with duplicates and non-editables excluded and ran the second report with non-editables excluded and with and without duplicates, but got similar results (as stated above). Is there a reason one regex works properly while the other one doesn’t? Am I missing something with regards to negated regex’s?
Your regex looks fine. To confirm, I straddled the Hudson River between NY and NJ and set the following…
This highlights everything on the NY side:
${state}
/New York/
This highlights everything on the NJ side:
${state}
!/New York/
If you are stuck, try resetting the validator. Make sure “Exclude non-editable segments” is not checked after your reset, and set the custom filter again. Once you have verified manually that it is highlighting as expected, you can run a report. If you want to only see the custom filter results, set the “Reported as” filter to 128 (green) or 129 (blue) or 128,129 (green and blue)
The report is cleared automatically once you change either a template or a regexp field. I guess you changed your custom check after the scan has been completed. This is my best guess. A permalink would help.
I was thinking on something, Validator is still in BETA, but beta is designed to track bugs.
AFAIK, there is no bug in Validator.
Maybe some adjustments are required for every country but its not a bug.
And the personnal check should be something as optionnal and for advanced editors, no?
There is no any harm having them available for all editors. The information to match is limited. For instance, there is no way to match editor’s name.
Also there is no relation between editor’s level and the ability to use regexps. Some people (with IT background, I guess) understand those regexps, some people don’t. But anyone can ask for a help and then just copy-paste two lines.
That is what the Custom Check in Validator for - gets the job done. Instantly
Thanks for the suggestion! I tested the regex at a border and it seemed fine, but didn’t know you could run a report with just the custom checks. Doing that seemed to find all of them correctly.
I ran a report, changed my custom check, and then ran it again, assuming, as you’ve verified, that the report would clear itself. I’ll try running the report again while manually clearing it out. This is the area I’m running the report in, if you want to try it yourself.
EDITED: I think I have narrowed it down to Highliter script. Unless it just magically starting working again.
OP:
I have run into an issue that I am not entirely sure is a Validator issue or not so I will explain.
My two setups:
Mac OS 10.6.8/Chrome
Samsung Laptop/Windows 8/Chrome
With #2 I do not have any issues with Validator at all so here are my issues with #1:
This occurs in either the production editor or beta editor.
When running a Validator Report it seems to hang out the very end. I have let it run for a few minutes longer thinking it may be processing something. If I hit pause the Report comes up. Show report and start checking things.
Everything appears to be working except for two things.
1a) If I delete a segment it does not show up as an edit by the save icon. Now if the next thing I do is change a geometry point or do a q/w then that edit will show. It will save just fine (no errors thrown)
1b) If I try to delete an extra node (not geometry point) it will not show up as an edit and validator then throws up the segment has no connectivity and that it is an overlapping segment. If I try to change a geometry point or a q/w like above it will still throw a save error.
This does not occur if just running validator while panning around and editing with it. Everything appears to be working as expected. Also regarding 1B if I log out and log back in I can edit normally and Validator throws the appropriate errors and corrections as warranted.
I cannot tell you in which version this first started occuring because I haven’t run a report from this particular setup in probably about a month. This occurs with Toolbox running or not.
Any ideas if it is my setup would be greatly appreciated.
Public segment being defined as freeway, major highway, minor highway, primary street, street, ramp, dirt road.
This would highlight, for example, a public segment that only connected to a parking lot at either end, or a private road at either end. This would help to highlight errant public segments amidst large parking lots or private road networks.
