Your elevation not ground regex should be !/0/, with the exclamation outside the forward slash, otherwise it will try to match a literal "!0"
So I just realized something with the ${altStreet[]} array that makes it a lot easier to code templates; I'm not sure if this is a general javascript thing or if anyone else uses this trick or has posted about it before. Whatever you put in the brackets is what separates the values, unless you put a number (obviously). So, if you set your template to for a street with the following properties:
Validator will expand the check as follows:
It doesn't add the separator before the first or last items in the array, so you still need to add a separator in the template, but I figured I'd share that as all the other examples I've seen have all the number added in manually, which can be tedious.
Code: Select all
#${street}@#${altStreet[@#]}@
Code: Select all
Name: Main St
Alt 0: US-321
Alt 1: SC-47
Alt 2: Downtown Ave
Code: Select all
#Main St@#US-321@#SC-47@#Downtown Ave@
https://s.waze.tools/lcus.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
This is not an issue with validator, but with WME itself. What I have done is assign the legacy road layer a shortcut of All+R through the shortcut menu (press Shift+?, click the roads label, and press Alt and R and release); gives you an easy way to toggle them. Also, post in the WME 1.9 release thread asking for a fix, that's the only way to hope that this gets changed...dougp01 wrote:I think this might be okay except the Shift-R functionality has been overwritten with experimental roads. I for one am a big user of shortcuts and dutifully navigating menus with my mouse is a bit of a pain. I therefore am attempting to use experimental roads as much as possible and this validator layers problem is a continuous issue for me.crazycaveman wrote:If you have the experimental road layer enabled and the legacy roads disabled, no roads will be displayed because the experimental layer does not yet get enabled through a permalink. Might be best to enable the roads layer before running a scan so you don't have to enable them with every permalink to follow
thanks!
https://s.waze.tools/lcus.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
You could try using a negative lookahead. In this case, it would look something like
I think this will work, but haven't had a chance to test it yet
Code: Select all
${typeRank}:${street}
/1[01]:((?!State |The |$)|(?!.* Rd|.* St)$)/
https://s.waze.tools/lcus.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
I think I might have been making it too complicated... How about this:
Code: Select all
/1[01]:(?!State |The |.* Rd$|.* St$|$)/
https://s.waze.tools/lcus.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
Try this:ispyisail wrote:Hi all
I'm looking for a custom search that will find all "Street" and "Primary Street" that have more than one "alternate name"
as always
Thanks
Code: Select all
Template: ${typeRank}:${altStreet[1]}
Regexp: /1[01]:.+/
https://s.waze.tools/lcus.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
No, because arrays in JavaScript are 0 based, so an array index of 1 is actually the second elementPesachZ wrote:Would that also match segments with only one alt name?crazycaveman wrote:Try this:ispyisail wrote:Hi all
I'm looking for a custom search that will find all "Street" and "Primary Street" that have more than one "alternate name"
as always
ThanksCode: Select all
Template: ${typeRank}:${altStreet[1]} Regexp: /1[01]:.+/
Sent using Tapatalk for Android
https://s.waze.tools/lcus.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
If I'm remembering correctly, there's no way to tell if a segment has untouched HNs or not until the HN editor is loaded, so for that to work, validator would have to load the HN editor for each segment to see what needs highlighting, which is impractical. Also, green highlighting is a custom highlight you (or a localization script) has setup.
https://s.waze.tools/lcus.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
Nice. That repository will be handy to help keep my localizations up to date. I have framework localizations for a number of states, Hawaii is in there, if you want to use that to tweak the existing checks to your needs (out disable then completely).
https://s.waze.tools/lcus.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
If you were to add support for states (or even multiple states in one localization), that would be great! I know quite a few states now have localization packs and it might make things easier when coding those.berestovskyy wrote: Wow that's a nice piece of work there!
So I guess we miss a support for states, right?
https://s.waze.tools/lcus.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
https://s.waze.tools/beta.png
https://s.waze.tools/betc.png
https://s.waze.tools/c6s.png
Re: [Script] WME Validator 1.1.6 / 06.01.2015