Page 61 of 245
Re: [Script] WME Validator 1.1.6 / 06.01.2015
Posted: Thu Mar 05, 2015 12:40 pm
by crazycaveman
Your elevation not ground regex should be !/0/, with the exclamation outside the forward slash, otherwise it will try to match a literal "!0"
Re: [Script] WME Validator 1.1.6 / 06.01.2015
Posted: Fri Mar 06, 2015 3:12 pm
by crazycaveman
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:
Code: Select all
Name: Main St
Alt 0: US-321
Alt 1: SC-47
Alt 2: Downtown Ave
Validator will expand the check as follows:
Code: Select all
#Main St@#US-321@#SC-47@#Downtown Ave@
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.
Re: [Script] WME Validator 1.1.7 / 06.03.2015
Posted: Tue Mar 10, 2015 2:57 am
by crazycaveman
dougp01 wrote: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
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.
thanks!
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...
Re: [Script] WME Validator 1.1.7 / 06.03.2015
Posted: Sun Apr 05, 2015 7:06 pm
by crazycaveman
You could try using a
negative lookahead. In this case, it would look something like
Code: Select all
${typeRank}:${street}
/1[01]:((?!State |The |$)|(?!.* Rd|.* St)$)/
I think this will work, but haven't had a chance to test it yet
Re: [Script] WME Validator 1.1.7 / 06.03.2015
Posted: Mon Apr 06, 2015 1:30 pm
by crazycaveman
I think I might have been making it too complicated... How about this:
Code: Select all
/1[01]:(?!State |The |.* Rd$|.* St$|$)/
Re: [Script] WME Validator 1.1.8 / 07.05.2015
Posted: Fri Jun 19, 2015 10:41 am
by crazycaveman
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
Try this:
Code: Select all
Template: ${typeRank}:${altStreet[1]}
Regexp: /1[01]:.+/
Re: [Script] WME Validator 1.1.8 / 07.05.2015
Posted: Fri Jun 19, 2015 7:32 pm
by crazycaveman
PesachZ wrote:crazycaveman wrote: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
Try this:
Code: Select all
Template: ${typeRank}:${altStreet[1]}
Regexp: /1[01]:.+/
Would that also match segments with only one alt name?
Sent using Tapatalk for Android
No, because arrays in JavaScript are 0 based, so an array index of 1 is actually the second element
Re: [Script] WME Validator 1.1.8 / 07.05.2015
Posted: Fri Sep 04, 2015 12:54 am
by crazycaveman
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.
Re: [Script] WME Validator 1.1.13 / 16.11.2015
Posted: Tue Nov 17, 2015 12:00 am
by crazycaveman
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).
Re: [Script] WME Validator 1.1.13 / 16.11.2015
Posted: Wed Nov 18, 2015 4:06 pm
by crazycaveman
berestovskyy wrote:
Wow that's a nice piece of work there!
So I guess we miss a support for states, right?
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.