Editor Version Dec 19th Official Feedback Thread

[Twister_UK]

This is going to take FOREVER to clear, and since they are UR's, its going to be tough to find actual User Requests mixed in with all the auto-URs.

I haven't been able to find any to test with, but if the description text used by these auto-URs contains a specific keyword/phrase, then it should be possible to hide them using my UROverview script (if you're a Chrome or Firefox+Greasemonkey user)...

http://userscripts.org/scripts/show/145186

If anyone does come across a fresh batch of these URs, can you please send me a permalink so I can try grabbing some info about them before any eager editors clear them up - it may be possible for the script to handle them directly, in the same way it deals with other specific types of UR (Missing exit, Turn not allowed etc.)

[Twister_UK]

https://www.waze.com/editor/?zoom=5&lat ... TTTFTTTTFT

Three in that area now, but don't know how long they will be there...

Excellent, thanks! I've added a specific filtering option to the latest version of the script, anyone who's interested should pay a visit to its thread here (world server) or here (usa server)

[Twister_UK]

Have the segment colours changed with the latest iteration of the editor (thinking about the recent change to the International editor, which has only just gone over to the new typeface etc. that the US editor has had for a while), because whilst doing some recent editing work on segments designated as "Major Highway", it looks as if the red used for this type of segment has darkened down a bit. It also looks as if the blue arrows used to denote one-way segments have become less clear in general (certainly look thinner, and possibly also a darker shade of blue too), so when combined with the apparently darker red segment background my colourblindness kicked in and made it damn near impossible to tell the difference between the one-way segments and the adjacent two-way ones...

I don't recall ever having this much difficulty in the past, and I haven't changed anything to do with the display setup on my PC, so it does seem as if it's the new editor that's to blame.

[Twister_UK]

I've compared the current colours to some screengrabs of the older WME I found in the UK Editing wiki, and surprisingly not only are both the "Major Highway" red and "One-way Arrow" blue are identical, but the size/stroke width of the arrows is the same too...

Discovered a useful trick though - reducing the contrast between the segment colours and the background colour by simply switching on the aerial images layer significantly improves the perceived contrast between the red and blue segment colourings. Manually setting the background colour attribute of the WazeMap element in WME to black makes the segments really stand out nicely too - I might have to add that as an option to one of my scripts

[umopapisdn]

what's not really clear to me is how to answer the request, solved or not a problem.

what exactly am i telling the system if i say it's solved? am i simply saying i found a problem in the area and corrected it? am i saying that the users ignoring waze routing are choosing the optimal route?

if i'm closing it with 'not a problem,' how does waze interpret my answer? is the route the wazers are taking not a problem, or is the fact that waze is giving bad instructions not a problem?

seems to me that the editor needs to be asking a different question: "which route is correct?" as it stands, the question asked really doesn't fit with the available answers.


now, i will say that with the help of the colour highlights plugin this new error type has let me to a few previously undetected u-turns and soft turns. unfortunately that seems to be the limit to its usefulness at this time, unless we get to see more of the route the users actually took. it'll be interesting to see how this evolves.

[vectorspace]

After some time using the new editor, I've noticed a benign bug that seems to lock up functionality until the browser is reloaded. Sorry if this has already been reported, but I didn't see anything in a quick scan.

I usually use Chrome under Windows XP or W7. When I am editing, sometimes the editor functionality seems to become unresponsive. For instance, when I highlight a road, then the road details will not display in the left window area. Sometimes when they do display, when I try to edit a road, the country field will be blank and editable. Nothing is available to select. Same for other fields.

This can happen with a fresh editor screen after a save, but it usually can happen after a number of edits that still need to be saved. One can save the edits already made. At that point, I have to reload the browser to overcome the issue.

Thanks!

[vectorspace]

Has anyone else been having issues with getting alternate names to stay after putting them in? I've been having to double-check saves and going back over the past couple days because the alternate name didn't save. It's been happening on single segment edits as well as multiple segment edits for me...

I didn't catch tis post until now. I have noticed some anomalous behavior here too, which is probably me not reading docs, but couldn't find them. I have been trying to fix some alt names in NM, such as the notorious route 666 that was renamed.

When you select the whole road length with Ctrl-A, it seems to list every alt name in the many segments selected.... So if 20 segments were selected, but only one segment had an alt of 666, that alt would appear in the list. That makes sense. Now deleting that alt and applying that change to all 20 segments has not always resulted in 666 from being deleted from that one... Or so it seems. I have not had time to try to debug this.

Anyone know the answer?

[vectorspace]

(1) When clicking on any UR, as the map zooms to the location the roads layer is not in sync with the Bing Aerials. I attempt to remedy this by click on the Permalink link, reloading the page, but the layers are still out of sync. ...

I have started having this problem and it has come and gone. The road layer is offset the width of a node or so to the right from the areal. I thought it might have been my large display and the graphics card. Anyone know?

[vectorspace]

I have started having this problem and it has come and gone. The road layer is offset the width of a node or so to the right from the areal. I thought it might have been my large display and the graphics card. Anyone know?

This is usually related to your browser zoom function. When it happens I usually find that my browser has somehow changed the zoom level. Make sure you reset the zoom to 100% and reload. ...

Wow, thanks mssusa! That was exactly it. I use Chrome, and the zoom level was offset. Zooming to 100 didn't work until reload, as you said. I appreciate it!

[Webs101]

When selecting this problem - you'll notice a purple line representing Waze's suggested route and green lines representing the routes selected by the users + a number of users who selected this route.

You need to put a key to explain this in the editing UI.