New Waze Map Editor - Official Feedback Thread

[TonyG-UK]

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.

[gettingthere]

Is there no way to add text to an UR, to inform the reporter what's being done, or get into contact with them?

Not currently.

[WeeeZer14]

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

I think this depends on the quality of the images available at the specific location. See here where there is a seam between older and newer images. Each source acts slightly differently at different zoom levels.

https://www.waze.com/cartouche/?zoom=8&lon=-74.15657&lat=40.83274&layers=BFTFTTTTTTFTTTTFTTTTT

[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.

[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?

[underdog28]

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

[gettingthere]

Keep in mind that the Extended Tools are not provided by Waze. The Waze Map Editor is officially supported in Chrome or Chrome Frame for Internet Explorer. It may work or partially work in other browsers - but Waze has not stated official support for other browsers.

Yes, the Extended Tools add some nice functionality, but you should not expect the Waze Map Editor to function properly in Firefox just because Firefox is the better browser for the Extended Tools. The author of the Extended Tools could enhance their usability by ensuring that they work properly in Chrome. (maybe they do work better in Chrome now, I haven't tried)

[khaytsus]

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

Extended Tools 1.2.8 or whatever the last version was worked fine in Chrome. The first versions with the "lasso", 1.2.5-1.2.7 however did not.

I don't use Firefox for Waze editing anymore because of the "damn near impossible to click segments" bug, but I haven't tried FF10 on it yet.

[gettingthere]

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?

[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.