Ya, I'm not getting anything except the yellow bubble in the lower left corner with either of them.
START READING HERE Getting Started The Manual Best Practices Common Mistakes New Editors Make
https://s.waze.tools/sm.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/betc.png
https://s.waze.tools/mapr.png
https://s.waze.tools/s0500.png https://s.waze.tools/c5s.pnghttps://j.mp/2R2740z https://j.mp/2wVQ4lF
https://s.waze.tools/sm.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/betc.png
https://s.waze.tools/mapr.png
https://s.waze.tools/s0500.png https://s.waze.tools/c5s.pnghttps://j.mp/2R2740z https://j.mp/2wVQ4lF
Ok, I don't know if this is working for anyone else but even with the most current Valfix and Chrome extension, the report is almost blank. None of the roads that should be getting flagged in the report are flagging at all. I have even thrown out some bad roads to test it and only 1 flagged and it only flagged as not having a name but showed up Blue instead of Red as it did in the past.
In the past, when I did a run of Denver, the report would pause at least 5 times due to "too many roads segments". Now it runs in less than 4 minutes (used to take over 15 for a full scan) and never pauses. I want to say it's missing about 90% of the road segments or something close to that.
So here's the question- Since this script is one of the core troubleshooting scripts out there, are we really going to just let this one die on the vine trying to "patch it" via external scripts? Does anyone have a plan to replace this with another script? I know that it would be a moderate to heavy undertaking and should be a community project like WMEPH is, but I think that this script is that important that something like this needs to be done.
And no, I'm not talking about taking the current Validator and "reverse engineering it".
Thoughts anyone?
In the past, when I did a run of Denver, the report would pause at least 5 times due to "too many roads segments". Now it runs in less than 4 minutes (used to take over 15 for a full scan) and never pauses. I want to say it's missing about 90% of the road segments or something close to that.
So here's the question- Since this script is one of the core troubleshooting scripts out there, are we really going to just let this one die on the vine trying to "patch it" via external scripts? Does anyone have a plan to replace this with another script? I know that it would be a moderate to heavy undertaking and should be a community project like WMEPH is, but I think that this script is that important that something like this needs to be done.
And no, I'm not talking about taking the current Validator and "reverse engineering it".
Thoughts anyone?
START READING HERE Getting Started The Manual Best Practices Common Mistakes New Editors Make
https://s.waze.tools/sm.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/betc.png
https://s.waze.tools/mapr.png
https://s.waze.tools/s0500.png https://s.waze.tools/c5s.pnghttps://j.mp/2R2740z https://j.mp/2wVQ4lF
https://s.waze.tools/sm.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/betc.png
https://s.waze.tools/mapr.png
https://s.waze.tools/s0500.png https://s.waze.tools/c5s.pnghttps://j.mp/2R2740z https://j.mp/2wVQ4lF
that's no problem if you are looking at a small town, but I'm talking Denver, Atlanta, LA. If you want to pan around at 500ft you are going to be panning for a week.
START READING HERE Getting Started The Manual Best Practices Common Mistakes New Editors Make
https://s.waze.tools/sm.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/betc.png
https://s.waze.tools/mapr.png
https://s.waze.tools/s0500.png https://s.waze.tools/c5s.pnghttps://j.mp/2R2740z https://j.mp/2wVQ4lF
https://s.waze.tools/sm.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/betc.png
https://s.waze.tools/mapr.png
https://s.waze.tools/s0500.png https://s.waze.tools/c5s.pnghttps://j.mp/2R2740z https://j.mp/2wVQ4lF
I have the same problem too. But as I see the problem is just on that objects, what I (or somebody) have edited in the last days.
I just finished my first mapraid, and it was really great having Validator back working! Thank you for all the work you put into getting it fixed!
Sean Julian
CM
SM: TX, LA, MS, AR, OK
AM: SE FL, Boston, MA, Brooklyn, NY, Bronx, NY, Manhattan, NY, Queens, NY, E CA, SW KS
CM
SM: TX, LA, MS, AR, OK
AM: SE FL, Boston, MA, Brooklyn, NY, Bronx, NY, Manhattan, NY, Queens, NY, E CA, SW KS
Thank you for fixing this again!
Sean Julian
CM
SM: TX, LA, MS, AR, OK
AM: SE FL, Boston, MA, Brooklyn, NY, Bronx, NY, Manhattan, NY, Queens, NY, E CA, SW KS
CM
SM: TX, LA, MS, AR, OK
AM: SE FL, Boston, MA, Brooklyn, NY, Bronx, NY, Manhattan, NY, Queens, NY, E CA, SW KS
Thank you for the fixes you have implemented!
Sean Julian
CM
SM: TX, LA, MS, AR, OK
AM: SE FL, Boston, MA, Brooklyn, NY, Bronx, NY, Manhattan, NY, Queens, NY, E CA, SW KS
CM
SM: TX, LA, MS, AR, OK
AM: SE FL, Boston, MA, Brooklyn, NY, Bronx, NY, Manhattan, NY, Queens, NY, E CA, SW KS
I am not sure if we have a "team" working to update validator, but it is flagging "E." in a street name. But, when it's Ave E. we need the period or it says Avenue East instead of Avenue E .... Thank you for anyone who looks into this.
Sean
Sean
Sean Julian
CM
SM: TX, LA, MS, AR, OK
AM: SE FL, Boston, MA, Brooklyn, NY, Bronx, NY, Manhattan, NY, Queens, NY, E CA, SW KS
CM
SM: TX, LA, MS, AR, OK
AM: SE FL, Boston, MA, Brooklyn, NY, Bronx, NY, Manhattan, NY, Queens, NY, E CA, SW KS
Re: [Script] WME Validator 1.1.17 / 01.06.2016