With the latest update to WME, when you select a segment, the segment IDs are now at the top of the side panel.
This is fine when you only select one segment, but when you select several segments, it makes the left panel virtually unusable.

We are constantly selecting multiple segments for various reasons like closing a stretch of road, adding speed limits to several segments, etc.

Please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please, please consider moving the segment IDs back to the bottom of the left panel. You can leave the number of segments selected at the top as that is useful information.

In some cases, it would be helpful to select an entire street not by its main name, but by one of the alternative names that it may have.

For instance, here in Portugal we have a big mountain area where it is needed to apply recurrent road closures due to bad weather (heavy snow). Because road closures are carried out by the authorities in perfectly delimited areas, the Portuguese community decided to put exactly the same name on ALL roads of a same area, even if the real street name is a different one. By doing this, the option ‘Select entire street’ permits to apply road closures easily and quickly, without the doubt if all segments of the area are, in fact, selected or not.

The option to have the possibility to select an entire street by any of its alternative names, would allow proceeding the same way as described above and, at the same time, keep the REAL street name on the main address.

Thanks in advance

Please add a way to mark some Map Comment (MC) points as "critical" (as opposed to "informational"), with increased visibility. Instead of a small white dot, for example, you could display a slightly larger black-and-white or red-and-white bullseye. You could perhaps even add (gentle!) animation, such as gradual pulsing.

Why do I suggest this? Several times now, I have encountered oversights by editors who seemed to have missed important information in a nearby MC Point. These well-intentioned but uninformed edits degraded the driver experience until they were discovered and repaired. I've asked around and have come to three conclusions:

(1) MC Points are not sufficiently visible to be sure of getting editors' attention.

(2) As a result of MC Points' poor visibility, some editors choose to create MC Areas instead of MC Points. But MC Areas are more intrusive than MC Points, so the proliferation of MC Areas degrades the editing experience and encourages editors to turn off the Comment layer more often.

3) Some MC Points provide less-important background information, for example the location of a mile marker that might be used by emergency services to identify that position on the roadway. It would be distracting for these background MC Points to be given high visibility, thus the need to differentiate between "critical" and "informational" MC Points.

Increasing the visibility of critical MC Points would improve their chances of being noticed and respected by visiting editors. It would also make MC Points an attractive alternative to MC Areas, leading to more judicious use of MC Areas.

When a warning such as a segment is part of a junction box a is displayed in the left panel the warning does not scroll away in the current WME beta. The previous behavior used to allow this warning to be scrolled away. The new behavior is for this warning to stay persistent. The new behavior makes it so there is very limited space to see the segment properties. This is especially problematic when trying to edit things like lanes where it is necessary to see what lanes are being assigned to each road.

The suggestion is to revert the current behavior to the previous behavior, let the warning be scrolled away.

Here is a video of the previous behavior- https://drive.google.com/file/d/1z-FAgdlmry3PcTV48Z-dzecBP4l_P3OR/view?usp=sharing

Here is a video of the new behavior- https://drive.google.com/file/d/1iOcYFE_vhNCjJuToO8RrgTm6HMWqW-RN/view?usp=sharing

Several years ago the decision was made to use the postal city as an alternate city name for routing to addresses in rural areas. According to Wazeopedia "Waze founder and CTO Ehud stated in a US meetup that a search algorithm is so much work to build correctly and maintain, that Waze does not want to spend the time, money or energy to build their own, and are happy to stack the Waze matching process on top of the Google search algorithm." As a result, WME editors have spent untold time and energy adding the postal cities to these segments. There are literally hundreds of thousands (perhaps millions) of segments that still don't have don't have the postal cities added and this results in thousands of "Incorrect Address" URs that editors have to spend even more time and energy fixing. At the current rate, it will take many years to add postal cities to the segments that do not yet have them. Does Waze staff still believe this is the best solution? Are there plans to increase collaboration with Google to rectify the discrepancies between our addresses and theirs?

When adding Places, especially outdoor places (such as parks, playgrounds, beaches, etc), there are often posted hours saying the Place is open only sunrise to sunset, or conversely that the Place is closed sunset to sunrise. Unfortunately, the existing Place hours interface doesn't allow for these kinds of hours, only HH:mm times. As sunrise and sunset times change constantly, and in some places drastically due to orbital motion of the earth and time changes due to daylight savings times, it is impractical to estimate open/closing times using HH:mm formats.

It would be beneficial to both app users and map editors to allow for the app to determine/reference local sunset/sunrise times (which it already does for dark/light app modes) and use this to mark the venues as open/closed.

Possible mock-up of feature in WME:
https://i.imgur.com/TYAa7vn.png

I’d like to suggest in the WME a switch (perhaps in the user control panel) for downgrading the own editor level.

For example:
If I’m a level 5 Editor, but only want to edit simple streets which are only on level 1, i can switch my own editor level to something lower than 5 for this action. This would prevent myself for accidental editing more important street e.g. highways.
Compare this with an account in the IT… Even if I am an administrator… I shouldn’t be logged in always as an admin but just as a normal user with rights just for my actions.

An other example:
Some tools, edits and so on are only available for higher levels of editing. To support a newbie with level 1 or 2 I should be able to switch also to this level to offer more or better support.