So it now starts for me but after about fifteen minutes I gave up on it (it's been saying "Finishing in a minute most of that time). So I tried the stop button and it doesn't respond.
It worked for me after I restarted the browser. At first it just got stuck scanning. Thank's for all the help.
I just ran a test. It didn't find a bad segment I planted in the middle of nowhere.
I am getting the same message with the same browser. It's not happening with Chrome, however.
Cost is relative and somewhat arbitrary, especially considering the "specials" in downtown areas that even mentioning it might be superfluous. It costs or doesn't. Then consider that many venues may validate parking. I can't even think through this much less imagine an effective algorithm.
I don't think that Validator is going to get an update. I've checked the forum profile page for berestovskyy. There is no last seen date. Also, his editor profile shows his last edit was 505 days ago. I'd say that indicates he's inactive. Is there anyone that can take over this script?
[img]https:///2F37zR[/img] [img]https:///ZPXMBb[/img]
Seconded, sorta: https://www.waze.com/editor/?zoom=6&lat ... 4,38759657ditchi56 wrote:Minor problem: the script is reporting time restrictions as expired on the last day for while they apply. It should wait one more day before flagging them as expired.
None of the restrictions I added there even take affect for another 21 hours, and are already flagged as "expired" by WME Validator.
ssl-3
Got that also frequently.
Global Champ - Country Manager Belgium, The Netherlands and Luxembourg - Coördinator Belgium and Luxembourg
stefaan@wazebelgium.be
https://www.waze.com/wiki/images/d/d5/GP_icon_23x21.png https://www.waze.com/wiki/images/c/c3/FB_icon_23x21.png https://world.waze.com/wiki/images/d/d3/TW_icon_23x21.png https://www.waze.com/wiki/images/1/10/WI_icon_23x21.png
stefaan@wazebelgium.be
https://www.waze.com/wiki/images/d/d5/GP_icon_23x21.png https://www.waze.com/wiki/images/c/c3/FB_icon_23x21.png https://world.waze.com/wiki/images/d/d3/TW_icon_23x21.png https://www.waze.com/wiki/images/1/10/WI_icon_23x21.png
Is it possible to highlight freeways without Speedlimit?
Lg Stefan
CM-Austria
https://www.waze.com/wiki/images/8/87/RWrsig.png
Österreich Wiki:https://world.waze.com/wiki/images/1/10/WI_icon_23x21.png
Waze Austria auf: https://wiki.waze.com/wiki/images/c/c3/FB_icon_23x21.png https://wiki.waze.com/wiki/images/d/d5/GP_icon_23x21.png https://wiki.waze.com/wiki/images/d/d3/TW_icon_23x21.png
CM-Austria
https://www.waze.com/wiki/images/8/87/RWrsig.png
Österreich Wiki:https://world.waze.com/wiki/images/1/10/WI_icon_23x21.png
Waze Austria auf: https://wiki.waze.com/wiki/images/c/c3/FB_icon_23x21.png https://wiki.waze.com/wiki/images/d/d5/GP_icon_23x21.png https://wiki.waze.com/wiki/images/d/d3/TW_icon_23x21.png
Would like to recommend a change to validator.
Based on this forum post Waze does not use the base import HNs unless just about everything else is missing. (Applicable to USA since no base import in other countries like Germany). So to prevent the URs that say my house is over on the other street or why was I routed to the loading dock of this store (all from bad Google Maps import)
I would recommend that instead of having streets with HNs as clear and streets with no HNs as green. That instead you have 1) a color for streets with HNs that are only base imports, 2) a color for there are some base import HNs and some bumped HNs, 3) green for streets with no HNs (either bumped or base import.
Main reason for 2) above is I have heard in the routing GHO that Waze does not interpolate HN locations so you can't just do a HN at either end of the block.
I am not a script expert, but figure this would combine the validator with WME HN Tool script and be more powerful and allow people to not have to select each clear road to see if the HNs are bumped/touched by an editor or not.
Thanks, I think that this would help us figure out a little quicker on the URs about routing and also give the new editors a way to zero in and fix the map. HNs are very important for final routing, yes I know they don't get a lot of hype or editing credit count. But as the Boston Map Raid showed they can help routing a lot.
Keep on Waz'n' Subs5
Based on this forum post Waze does not use the base import HNs unless just about everything else is missing. (Applicable to USA since no base import in other countries like Germany). So to prevent the URs that say my house is over on the other street or why was I routed to the loading dock of this store (all from bad Google Maps import)
I would recommend that instead of having streets with HNs as clear and streets with no HNs as green. That instead you have 1) a color for streets with HNs that are only base imports, 2) a color for there are some base import HNs and some bumped HNs, 3) green for streets with no HNs (either bumped or base import.
Main reason for 2) above is I have heard in the routing GHO that Waze does not interpolate HN locations so you can't just do a HN at either end of the block.
I am not a script expert, but figure this would combine the validator with WME HN Tool script and be more powerful and allow people to not have to select each clear road to see if the HNs are bumped/touched by an editor or not.
Thanks, I think that this would help us figure out a little quicker on the URs about routing and also give the new editors a way to zero in and fix the map. HNs are very important for final routing, yes I know they don't get a lot of hype or editing credit count. But as the Boston Map Raid showed they can help routing a lot.
Keep on Waz'n' Subs5
https://storage.googleapis.com/wazeoped ... anager.pnghttps://s.waze.tools/c5s.pnghttps://s.waze.tools/s2000.pnghttps://s.waze.tools/beta.pnghttps://storage.googleapis.com/wazeoped ... master.pnghttps://storage.googleapis.com/wazeoped ... entors.pnghttps://storage.googleapis.com/wazeoped ... _small.png
Re: [Script] WME Validator 1.1.20 / 03.11.2016