Can u add a filter. To filter out Mm or a other fixed distants. Because I edit in 2 country's And it should be nice that I could filter out Ur's more than Mm from were i am editing.

I must be missing something with this script. I have Auto scan checked and the only scan area I have is "editable area". When I first load my browser and WME I assume it scans my area. However, as I scroll around I see URs that were not on the UR-MP list until I scrolled by them. Even clicking to manually scan doesn't help. I would think that if it scans my editable area (AM area) it would find all URs. Am I doing something wrong?

Thanks for the info Alan and Timbones. I obviously had some misconceptions about how it works.

Any chance of being able to create areas with more than two points? (UL and LR) Rectangles just don't always fit our editing areas.

Drawing a POI area and converting it then deleting the poi would be excellent! I understand about the time problem. Thanks for all you do!

Olestas wrote:Hmm.. recently URs in list stop responding. Map is not centered on UR. Probably caused by some other scripts updates..

I'm seeing this also. After scanning an area I can select one UR. Then I can no longer select another ur, sort, filter or anything. It's like WME UR-MP Tracking just freezes.

BTW, creating an area from an unsaved POI Area is a great addition to this tool.

Yes, I'm also getting the "Error: can't download data from waze server" error. Bummer!

bz2012 wrote:A problem I have been noticing: many 'closed' URs are appearing without the 'green' color and despite the fact I have the 'hide closed' box checked.

This becomes clear when I click on one of the links and the URComments box comes up with its green on.

The 'hide closed' box DOES work, because if I uncheck the box, then MANY greens show up.
And I think that sometimes when I close a UR, it DOES get handled properly.

Not sure when it doesn't, yet.

Could this be for URs that have been closed since you last scanned? Without a fresh scan, the script doesn't "know" they've been closed. If you have "hide closed" ticked and you target a closed UR, you should see it immediately disappear from the list as the script detects it's closed.

A similar thing happens when you comment on a UR. The script doesn't pick up this fact. You need to save or refresh the map layers, then "target" the UR again for the comment count to increase (and for it to be hidden if you're hiding URs with comments).

This sounds to me like a problem that's also affecting Toolbox - specifically highlighting of segment elevations. After saving edits, you'll find that many segments are highlighted as having non-ground elevation. If you select these segments, the elevation value will be missing. It's necessary to use the refresh button in the layers menu - generally at least twice - to get the missing values to appear.

It's been said over in the Toolbox thread that this is due to recent changes in JNF. JNF is not the cause of the problem - just the opposite. It seems that JNF was forcing a data reload after saving to get around this problem, which is inherent to WME. The most recent version of JNF (which is also incorporated within Toolbox) removed this feature to see if WME was still working poorly - and it is.

Back to the true hero of this thread - UR-MP Tracker. This problem does affect the script in one way. If you comment on a UR and hit "send", this doesn't require saving. Re-targeting the UR in the UR-MP list does not update the number of comments. URO+ is similarly affected - the comment count bubble doesn't increase/appear. Until you refresh the page or use the layer reload.

However, the original problem mentioned (closed URs not showing green/being hidden by UR-MP) may still be due to the way the script works, rather than the WME bug. The data that goes into the UR-MP lists is only updated by 3 things: a manual scan, having "Auto scan" turned on or "targeting" a UR in the list. I generally manually scan the country once a week and run with auto scan turned off. So, as I get to the end of the week, more and more of the non-green URs I select in the list turn out to be solved when I target them.

Twister-UK wrote:W.m.uRS therefore appears to be pretty much useless - the only time we can be certain it contains valid data is immediately following a WME session reload, and since WME itself doesn't seem to be using it then I have to wonder why it even exists...

Ssshhh! They might hear you and remove it - then we'll really be stuffed.