Well yeah, but thatâs looking for just anyone, not a specific someone.
My point was that if someone was really going to be that determined to find a specific someone, there are ways other than Waze to get you close enough to do that. Maybe even closer.
The unfortunate fact of the matter is that any kind of real privacy, in this day and age, is pretty much reduced to myth status.
Please keep in mind that this is a thread about WME Validator.
Yeah, maybe this brawl belongs in the âLocalizationâ forum. 
I know that the Localization forum is not about this.
I canât seem to find any info on the ${roundabout} template â iâve tried true, false, 1, 0, yes, no, roundabout⌠what can I regex on to highlight roundabouts?
The following works fine with me (highlights roundabout segments):
Template: ${roundabout}
RegExp: D/1/
You donât have to âguessâ. Just add D at the very beginning of RegExp (just like above), then open JS console (Ctrl+Shift+J) and check the debug log. Here is an example:
[code]WME Validator v0.9.8 debug log for segment 248090636, check #128:
- Expand template: ${roundabout} -> 0
- Match RegExp: /1/ -> null
=> skip the segment
WME Validator v0.9.8 debug log for segment 248091485, check #128: - Expand template: ${roundabout} -> 1
- Match RegExp: /1/ -> [â1â]
=> REPORT the segment as #128 âUser-defined custom check (green)â [/code]
So you can easily figure out that ${roundabout} expands to 0 or 1.
A special case to submit youâŚ
#79 Too short U-turn connector (slow)
In this case I think that Validator shouldnât report an error:
https://www.waze.com/it/editor/?lon=17.9282&lat=40.62452&zoom=7&layers=2023&env=row&segments=250442108
You may not turn left two times.
Hi,
an error highlight that could be implemented:
time or vehicle restriction on a single direction segment with restriction in the wrong direction:
For example the segment is A->B but it has restriction that are for B->A. Those are invisible when editing them, you have to change the segment direction to be able to remove them.
I have a problem that canât possibly be unique. Rule 78 about âSame endpoints drivable segmentsâ correctly highlights segments that should have at least one junction point added to them for routing to perform correctly. If you add a junction point to those segments then rule 118 or 119 catches the two segments saying the junction point is unneeded.
Is there some way to correct this behavior? Am I not interpreting the results correctly?
For now, I have disabled rule 78.
Unfortunately, once a node goes off-screen in WME, there is just a partial information available about the node.
Iâll try to fix the issue, but excluding âUnneeded node A/Bâ checks for segments with off-screen nodes seems to be the only wayâŚ
I appreciate all your efforts but I think maybe there is a little bit of misunderstanding. None of the nodes are âoff screenâ.
Sorry, I just tried to split/merge same endpoints segments on different zoom levels, but the only way I can reproduce the issue is when both of the nodes are off-screen.
Pardon me for putting this in the Validator thread. I thought a thread for regexps to be put in the optional checks in Validator had been broken out, but I canât find it.
I am editing an area where, for some reason, a lot of the rural roads in the basemap are shown as one-way (when theyâre actually two-way roads). Often this ends up with a one-way road going to a dead-end/cul-de-sac/however you like to phrase this.
Is there a regexp phrase I can concoct that will highlight segments that are one way and donât connect to a road at the âtoâ end of their one-way-ed-ness? In other words, if a road is set to A->B, and B doesnât have any road connected to it, I want that segment highlighted for review.
Thanks!
Iâd like to make a request for Validator. In Pennsylvania we have a lot of roads that have not had their primary names updated since the base map. For the example here the roads primary name is currently âT493â however the actual primary name is in the alternative âHanny Beaver Rdâ Is there a way you can color roads that are a letter & number? Iâm no programmer or script writer but my guess is the script would be something like <If street name = character (T)(integer)(integer)(integer) then color = Lime Green> Is this possible to add? If not an âalways onâ feature then something that can be turned off and on.
You can add the following custom check:
Template:
${street}Custom RegExp:
[A-Z][0-9]{3}Is it always T followed by 3 digits and thatâs it?
If so, set this in your custom check:
custom template:${street}custom regexp:/^T[0-9]{3}$/That will report every instance where the road name is âT###â exactly, nothing before or after, not even a space. (It seems to be working for this example.)
If you remove only the â$â it will report everything that starts with âT###â regardless of what follows, if you remove only the â^â it will report everything that ends with âT###â regardless of what comes before, and if you remove both ^ and $ it will report everything that has T### in it at all.
1 Like
It must be already highlighted as #44/#45 âNo inward/outward connectivityâ :?
Just in case you still need the custom check to highlight one-way dead-ends:
Template: ${deadEnd}:${direction}
RegExp: /1:[12]/
Excuse me⌠what about this?
I clicked âThanksâ to inform you that Iâve read your message. No questions. The bug will be fixed 
Great! Youâre number 1, really.