[Script] WME Validator v2025.02.26 (+ PLACES BETA)

I started getting cams wider than Zoom-3 when I installed it.

Odd, its certainly not an intended bit of functionality, and I can’t think which bit of the script might be responsible. Sure it isn’t another script you might have installed at the same time?

JNF makes cameras visible at zoom 0, if you have that installed

I only get them at 0 if they were already visible at 3 and I zoom out. If I pan around the map, new ones don’t appear at 0.

I’ll see if I can find the thread where I complained about them only being visible at 3+ and the suggestion.

Confirmed… it’s JNF, but not at “0”… just “1” or higher.

Looks like the latest Toolbox may have broken Validator.
I loaded Firefox and decided to run a report to pick up the Revcons that we couldn’t see the last couple of weeks.
It began the auto-scan but only got through one or two tile sets before locking up.

I moved to Chrome and it scanned fine at zoom-0, then I realized that I had not forced the Toolbox update.
After updating, I ran another report and the same thing happened.
I’ve tried this all the way down to Zoom-4 and it’ll scan the first tile set, then lock up on the 2nd set.

When running in normal mode, it of course does not report the Toolbox Revcon error… which is why I wanted to run the report. I like it picking up Toolbox errors.

Strange because another local editor is running without a problem, but mine consistently “broke” after the Toolbox update.

+1

I can confirm this is caused by a compatibility issue with Toolbox (since its latest update). I will try to push an update of Toolbox.

Toolbox 1.4.6.2 is released, which should fix the compatibility issue with the Validator scan function.

Would it be possible to add a check for service roads in the USA? They have been deprecated and aren’t to be used. Having them be highlighted (even if it’s just as a note) would make it easier to remove them.

You can achieve that with the following custom check:

Custom template: ${typeRank}
Custom regexp: 9

Yeah, I’ve been using that. I was just thinking that, since this is a country-wide guideline, it would help more people be aware not to use that road type. Also, it would free up one of my custom checks :smiley:

You can also use WME Color Highlights for this.

+1

I understand what you’re saying there, but - given that Validator’s purpose is to highlight things which need attention, and given that “service road” is a type that they want us to avoid using in the US, wouldn’t it make more sense to add it as a check within Validator?

Agreed, a “service road” check would be nice. According to staff, the entire type is going to be removed, but then again they’ve been saying that for two and a half years…

I think that service road check would not be nice: when the service road type is removed, soon (?), then staff is run the search/replace “service road” by street type. So, the change may be transparent, without need to search, manually edit, and change this type in WME.
Perhaps, this check can be placed in the localization package, to be applied and used by all editors;
I think that checks #44, #45 and #50 are more important to restore.

Yea, “soon.” How long now have they been saying that they were going to get rid of the service road type as a selection? :wink:

That they’re going to do this change “soon” is no reason to not have Validator look for it and help us find those types of road now, while it is still something we have to deal with. The check can always be removed later once Waze has removed it and changed all of the roads so that “service road” is no longer on the map.

The advantage to highlighting is that you could set it correctly.

Service roads may well be streets or parking lot roads, depending on usage.

When (if?) the type disappears, it is likely the will all become one other type… And I’m going to bet it would be “street” as that is how service roads are routed now.

The problem is some service roads that have been added in my area should be sweet as private roads and not street. I’d prefer to find them and set the correctly before Waze changes all of them to street and starts trying to route on them. By my reckoning, it should be easy to add, but I wholly agree that those other checks are more needed and should be fixed first.

The goal of validator is checking and do alarm in real problems.
In actual environment, what is the real problem with “service roads”? Resp. Nothing ! :wink: :slight_smile: