New WME v.2.297

We hope you’re all doing well.

We’ve just released a new version of WME, v2.297.

Below you can find a summary of the release.

New features/enhancements:

1. We’re excited to announce the release of the new feature Suggestions on Turns!

  • This new feature allows users to propose changes to turns, even if they don’t have editing permissions. It’s a helpful tool for newer editors to contribute and learn, while giving experienced editors a way to review suggestions and keep the map accurate.
  • For more information, please visit the feature post. We encourage you to give it a try and share your thoughts and feedback in the comments there.

2. Map Events Filtering / Duplicating: Editors can now duplicate any saved Major Traffic Event—past or future—to quickly create a new one based on it. The new event includes a reference to the original event and allows copying all associated closures, streamlining the setup process and saving valuable time. (You can read more in the feature post). Give it a try and share your thoughts and feedback with us.

3. Map Clusters feature: To improve clarity and usability, the team added a cluster marker tooltip that displays the number of markers within the cluster on mouseover, along with the marker type.

4. House Numbers (HN) Revamp: House Numbers (HN) Revamp: We’ve addressed the issue where clicking the trashcan while a HN was the most recently selected object would delete the entire segment with the HN (and permanent hazard if available). Now, only the selected HN is removed.

5. WME Userscripts tab: The WME Userscripts tab in the sidebar now includes a link to the SDK documentation, in addition to the existing link to the old API docs.

6. SDK improvements: please refer to the change log to check the SDK additions.

7. Performance: We added an adjustment to the map area buffer size in ROW and NA environments, which should result in faster map load times.

8. Permanent Hazard: We’re making a change to Permanent Hazards so that each type can have its own settings for each country, instead of using one shared set of settings. This will fix issues caused by the old “default” setup and will meet long-standing requests from the Community to reduce or increase lock level of a specific permanent hazard, for example only for speed bumps. For specific lock level changes, coordinators can complete a form that has been shared with them here (only visible for community leadership)

Bug fixes:

We released 5 bug fixes:

1. House Numbers (HN) Revamp: Resolved a bug where an error “Something went wrong” appeared when enabling the layer using Shift + H.
2. School Zones & Scheduler: Fixed the issue with scheduler visibility — the schedule is now always viewable, but can be edited only by editors with the appropriate permissions.
3. School Zones & Scheduler: Resolved an issue that time frames weren’t ordered chronologically in the scheduler menu.
4. Street View: Resolved a bug where closing Street View caused the map to jump back to the previous location.
5. On Segment suggestions and Suggest an edit: we added an improvement and made the whole “Magic select”chip clickable.

Known issues:

  1. Turn popup appears over the instruction popup and turn closures pop-up when opening the street view
  2. Suggested closure is not highlighted on the map after hovering it
  3. Map comments: tapping the map comment sometimes causes the WME map area to freeze.
  4. After accepting or rejecting a Suggested Edit the card does not reflect the updated status.
  5. When suggesting the change for the city of a named segment, the resulting suggestion may incorrectly display “A segment without a street name” instead of showing the updated address.

You can read more here

We look forward to hearing your feedback! :disguised_face:

Thank you,
Nataliia

29 Likes

Thank you for this update. Bug fix #4 is much appreciated :smiley:

6 Likes

thank you for #7
the pothole error pop up greatly reduced

4 Likes

Thank you @Nataliia_Staff

3 Likes

This doesn’t seem to be fixed. I’m still experiencing street view jumping back to a previous location.

2 Likes

Awesome: duplicate a closure that has finished previously!

6 Likes

Thank you for the Fixes it really helps a lot. :+1:

1 Like

Seems to be working for me

It works more often but I have had it go to the previous location a couple times now.

The issue seems to be some kind of cache issue with WME. When you drop the street view it briefly shows the old location and sometimes it will stick at the location and jump the WME to that location.

Here is a video from incognito with no extensions / scripts. If you watch carefully you can see the street view going to the previos location every time. Look in the attached video on slow motion. you will see at 4 sec the video briefly shows the last place I used street view, this image:


Then it goes to the correct location, this image:

You can see it again at 11sec where it shows the previous location, this image:

Then it quick goes to the correct location, this image:

Video:

2 Likes

I seem to be having an issue with the Community Scheduler now, when I go create a new community schedule and set it up so that there is no expiration date, I’m getting an issue where when I go to publish it, it’s failing to generate the schedule:

Start:

Go to publish:

When I go back to the scheduling times:

I was able to duplicate this. I reported the bug here

1 Like

Hi @ojlaw / OJ,

Thank you for the report and for the video. We will check this misbehaviour with the team.

Regards,
Nataliia

Hi @TheDarkAngel7,

Thank you for flagging this issue.

Hi @jm6087,

Thank you for trying to reproduce and creating a separate bug for this problem. The team will investigate it.

Regards,
Nataliia

1 Like

Why instead of my reported bug One more Street view issue - WME Beta Community / WME Beta BUGs - Waze Discuss there is reference to another created later and they are not merged?

3 Likes

Hi @ypcyc,

Thank you for the question :slightly_smiling_face:. The report you mentioned is in the WME beta bugs section, which isn’t accessible to all editors. That’s why I only included the link to the production bugs section in the release notes.

Let me know if you have any other questions.

Regards,
Nataliia

Thank you for clarification! So, it’s not possible to merge beta and production bugs and next time I need to create same one for production?

Hi,
It seems that event filtering doesn’t always work as expected.
Let’s say I filter on this:


I should expect to see events in the future and not items like this:

Or am I interpreting it wrongly?
Cheers,
Eddy

Thank you!

1 Like