I’ve seen that text too, but the UR in question is outside my editing area so I’m waiting for an UR to pop up somewhere closer.
There is a bug in this version of WME, which also affects Beta. The substance of the bug is that there is a 100px square area in the top, left-hand corner of the map screen where segments cannot be selected. You can find a more detailed description here.
I am reporting this here so that the wider editing community can be aware. I have reported a bug in the Beta forums here (only accessible to Beta WME users).
I saw this in the first post saying “* Changes in permissions: L1 editors cannot close URs”. However, I see remarks yesterday saying that “You need to be level 3 or higher to handle Update Requests” at the bottom of the UR pop-up window. Thank you.
The level 3 there is an error, I’ve come to conclude. It should say 2 instead. There’s a bit of configuration set incorrectly. This issue has been reported and will hopefully be fixed soon (even though it’s purely a visual mistake).
Thank you very much for your kind assistance.
Just a quick question sir and/or ma’am,
What is a difficult turn? :?:
Intersections?
Roundabouts?
It is possible to identify a certain turn as ‘difficult’, which will apply a routing penalty on it if you have this option enabled in the app (enabled by default). See this wiki page (which is still a work in progress) for more details: https://wiki.waze.com/wiki/User:AlanOfTheBerg/Difficult_Turns
That makes sense.
Always wondered what that clock thing in those segments are.
Although, didn’t know there was such a feature.
Thank you sir Glodenox.
Could it be that it’s still possible for the author of a user request to close their own report if they are level 1? We just had a level 1 editor close a user request and that’s the only explanation I can think of for now.
I’m not sure whether this should be seen as an issue or working as intended. Seeing that it can’t be abused to get points, it probably won’t cause problems. On the other hand it does deny the person who handled the user request the points he/she deserves for the effort.
I logged out of my app and created a new user account to test things like this. I left a UR with it and was able to close it in the editor. This R1 acccount can’t close any other URs. I don’t know if this is working as intended or not, but your explanation is certainly valid.
It would appear to be similar to the fact that they can’t delete segments unless they are the creator, so it’s probably following the same logic, can’t handle URs unless they created them.
I don’t necessarily see this as a huge problem, at least now when a L1 user closes a UR we’ll know he was the author/reporter, before we were never really sure.
I saw this happen this morning and thought oh no a bug. But your idea that they can close their own makes sense. I think we will have to take a good look around to see what they “fixed” to make sure it followed the Wazeo i.e. not restricting valid turns because they might seem to take longer.
Still glad to have the new restrictions in place.
Sent from my iPhone using Tapatalk
I think I found a bug.
when merging 2 segments, it doesn’t keep some attributes
elevation level
toll restriction
haven’t seen other attributes yet, but might be possible. The elevation level already disappeared two versions ago when merging segments.
There is an open bug for this (generally about merging when parameters are different):
https://www.waze.com/forum/viewtopic.php?f=1524&t=246131
It is also when the 2 segments both have toll or elevation level is equal. I made a post in the bugs topic
Thanks!