I understand the differences, but there is something else going on. Take a look at https://imgur.com/a/Ze0Bvqp. I created a small scan area for test purposes, which is highlighted on the map. There are 8 visible PUR markers within this area. The scan results visible on the left side of the image show only 4 PURs. The WKT definition of this area is as follows, if you want to try to reproduce this: POLYGON ((-73.9741784449 40.763326337202,-73.970037114181 40.761546684029,-73.971710812607 40.759263132309,-73.975980889358 40.761026593739,-73.9741784449 40.763326337202)) This is on the NA server.
Yes, I’ve been choosing “Clear all” between scans. Not doing so keeps blacklisted URs from reappearing. Thanks, Dennis!
When creating place, the cursor gets stuck on the place and can click many times. See video.
Oh !
WME bêta was updated…
Sorry I don’t test it under the bêta editor.
The fix is for the next update.
I see your comment but let me one time for have a look !
Thank.
Gotcha, thanks for trying! Ok, one more question. So would it be possible to just show the current total and not show the ones rejected/resolved?
Apparently, adding custom areas is currently broken. Since I tried downgrading the script to add a new area and the problem persisted, I’m assuming a Chrome update maybe behind this.
-
If I try to add an area from the populated list, I get “Error while getting area from server. Please, retry later”
-
If I try any of the subsequent methods (unsaved POI, BBox, WKT or JSON), nothing happens.
Will investigate some more.
For which country / region?
Maybe a problem on the server.
Is it possible to send me, by PM, a copy of the Java console. With only active URMPT.
Thank you !
Ok, so I further investigated, and apparently some of the previous updates corrupted the locally stored data of the script, to an extent that adding new scan areas (both from the server or custom areas) was failing, with no error presented in debug console.
What I did to solve was simply open the storage area of URMPT from Tampermonkey control panel and delete everything, then reload WME so that config data was recreated. Yes, I lost all UR/MP/MC/PUR scanned data, previously added areas (had the WKT’s backed up though) and customizes config parameters. But everything was working again. Yay!
I think some of the previous updates corrupted stored data. Since I don’t mess with custom areas that often, didn’t realized till now. Guess I’ll never know what triggered the error… :roll:
I performed a scan this morning for the area of Arizona and received what I thought were good results. A few minutes later, I accidentally clicked the scan Editable Area and it yielded even more results, most of which were the 1 day old PURs, not new, zero-day PURs. Since I am a state manager, my EA and the State area should be identical and yield the same results.
Any ideas?
Orville
A new situation: after PUR scan, whenever I click over a PUR PL in the tab, my map is centered in the PUR. When I click over the PUR pin, the corresponding PUR entry in the tab is not marked as visited, but the next one instead. Not a single message appeared in the console.
So I did as suggested and clicked Clear All in UR-MP. Then performed a scan using AZ. 618 total PURs. Then performed a scan using Editable Area and I now have 1373 PURs. Mind you, my EA and AZ are the same areas since I have not left the state in the past 90 days.
Here is a link to a video showing what happened between the 2 scans.
https://drive.google.com/open?id=1JZSrBOgw-rFrZqJl0LwvgAKaeNEGdIbh
Hi all,
For your information, the problem is due to a non limitation of the numbers of PURs returned by waze’s server, unlike the UR which they are limited to 500. This has an impact on the script.
I do not explain the difference between editable zone / state scan yet. Except perhaps the size or position of the driving zone that would overflow the managed area …
But:
The fix is almost ready but, let me one or two days for test and adjust it. 
Or if you want i can downgrade ? :mrgreen:
At the moment, I just tested and performed a scan of Arizona. I found 1574 PURs.
Today’s WME version update appears to have triggered a bug in WMEURMPT. Whenever I try to drag an RPP stop point or a HN marker, I get the same error message in the console; the save counter fails to update and the save button remains disabled:
Uncaught TypeError: Cannot read property 'length' of undefined
at e.WMEURMPT_Injected.WMEURMPT.newActionAdded (<anonymous>:5693:35)
at initialize.triggerEvent (vendor-7241bd10db1542b6eac4.js:73)
at e.value (app-d27185e0eb1f30c039a7.js:1)
at F.s.onDragEnd (app-d27185e0eb1f30c039a7.js:1)
at initialize.triggerEvent (vendor-7241bd10db1542b6eac4.js:73)
at e.dragging.done (app-d27185e0eb1f30c039a7.js:1)
at e.value (app-d27185e0eb1f30c039a7.js:1)
at e.value (app-d27185e0eb1f30c039a7.js:1)
at e.value (app-d27185e0eb1f30c039a7.js:1)
at initialize.triggerEvent (vendor-7241bd10db1542b6eac4.js:73)
Yes i know, i work on it.
Thank you again for your efforts with this script. Unfortunately since the new WME version yesterday I am having a couple of other issues when running this script:
-
Updating two-way speed limits
When you add both A-B and B-A speed limits only the edit for one direction is recognised and gets saved, leaving the other speed limit blank. -
Drawing new roads
When you draw new road and terminate it with a double-click the cursor remains as a circle and you need to press ‘Esc’ to be able do any other edits.
Also cannot close URs, dialog remains open, and cannot create speed camera… it keeps mouse tied to speed cam…
Probably it is all tied to new api.
https://www.waze.com/forum/viewtopic.php?f=819&p=1849886#p1849886
v3.7.6 released.
- Improvement of PUR management in high concentration areas.
- Optimization of MC management.
Big improvement in the handling, clearing, etc. of PURs. Really sped up the process. Thanks for the changes and updates. This essential tool got much better when PURs were added.
Thanks for the updates and a huge thank you for including PURs.