New Waze Map Editor - Official Feedback Thread

[AggieJM]

Something that's always bugged me but I haven't noticed anyone else report before (so maybe it's just me) is that nearly horizontal roads on the screen are difficult to select. It's like there are 1 or 2 pixels that you can click on to select the road, and they can be next to impossible to locate. This is an old issue, so not specific to this update. Running FF v9.

Firefox isn't officially supported, only Chrome is, which doesn't have this problem.

Having said that, this issue seems to be less of a problem with the new editor and FF10.

I've noticed the same with the old editor and FF9. Unfortunately, the extended tools only worked correctly to multi-select the road segments by name in FF and not in Chrome. So I've been using both Firefox and Chrome when editing lately depending on what I was trying to do.

Does anyone know if the extended tools work better in Chrome now with the new editor than they did in the past?

[AlanOfTheBerg]

To further this: IF you select a junction that can't be deleted, and use the keyboard shortcut OR press the trashcan icon.. all future edits are ignored. they add up in the unsaved edits counter, but when you hit save, they don't actually apply.

....

A couple of the Beta testers saw a similar behavior, on a couple of occasions during testing. Waze was unable to reproduce this issue.

Well, maybe. Not only did I provide two videos of this happening, I did it live at the meetup with Ehud watching. Same with the disappearing street name.

[AlanOfTheBerg]

Can more information about the cones be provided in the map editor? I know this is the editing level you have on Waze but I'm confused about it. It tells me I'm level 4. This can't be right as I don't even have 10000 map edits. Have the guidelines for the levels changed?

viewtopic.php?f=10&t=15400

[AlanOfTheBerg]

Scruffy, for now the best option there is is to use the statewise RSS feeds. That's all I've used for over six months.

[AlanOfTheBerg]

New issue with aerial layer not updating reliably after a fresh permalink load which includes zoom=8, which is most update requests.

http://youtu.be/io0O8wS27mg?hd=1

[AlanOfTheBerg]

OMGosh! How lame! 2nd try!



Lame you can't force embed HD.

[AlanOfTheBerg]

Maybe, but the loading of images behaves differently sometimes. The aerials there in my example are pretty good and quite recent. My house, which isn't too far from there, has images from this past summer. Clearly the browser, for whatever reason, isn't loading the image as I pan until I zoom out. This is bad behavior.

[AlanOfTheBerg]

I would like to try the new map editor but it want let me sign on

That seems a bit strange since the same account is used to login to the forums. Are you getting an error message?

Did you clear out your cache and cookies? Then restart the browser? That seems to be necessary with these upgrades. Also, username and password are case-sensitive. Then, after hitting login, be patient. Sometimes I've had to wait 15 seconds for it to look like something was happening.

[AlanOfTheBerg]

lasermi, the deleted roads should refresh if not right away, after a short time. There is a cache database between Waze Map Editor and the actual street table, so sometimes it will lag. This issue has come and gone with the previous version as well. If you get one which lags for more than an hour, you may need to open a ticket with support.

As for city names, they often will stick around forever. However, when the livemap/app map updates, the cities layer shape should change around the same time. The city coloring in the Editor will not change right away. There's an update process for that.

[AlanOfTheBerg]

Does shift + ? work ? He doesn't work on my azerty keyboard.

That's weird. You should just do what you normally do for typing a question mark. shift+? is not actually correct, as on QWERTY keyboard it is Shift+/ (forward slash).

Focus is important, because if you are in the URL field, search field, or any text field on the page, it's not going to work, which is by design. As others have noted, the code may not be correct depending on your keyboard type.