Hey everyone! ![]()
We hope everyone is doing well.
The new version of WME v2.325 has just been released ![]()
Check out what’s changed below:
Community Suggestions:
1. Online Editors – visible by default on first login: We are implementing changes so that, during a user’s first login to the Waze Map Editor (WME), their online status will be automatically set to “Visible”.
- To communicate this change, a simple message (tip/pop-up) will be displayed during the first session, confirming the online status.
- Once the user dismisses this initial message, it won’t appear again.
- If the editor hasn’t manually changed their status to invisible, they will now be visible by default.
- Users can still manually change their status to “Invisible” at any time in the WME settings.
- Community suggestion: “In WME: Force L1 & L2 editors to be ‘visible’
- Thanks to @kodi75 for the suggestion and to everyone who voted!
2. Venue Matching Flow: In this version, we’ve improved the matching flow between venues and external providers. From now on, when you select an item from the dropdown menu, the venue will be automatically matched, without the need to click “Add” or “Cancel”.
- Thanks to @YanisKyr for raising this suggestion in the topic “Let’s Empower Our New Editors with Targeted MapRaids!” (access restricted to Community Coordinators and Global Champs).
New features and improvements:
1. Issues Tracker – new API pagination logic: We are performing internal structural updates to make the Issues Tracker faster when handling large lists of issues in the Resolve tab.
Previously, the backend loaded batches of 500 items for the issue list on the screen. We displayed all 500, and upon reaching the end and moving to the next page, the spinner would appear to load the next batch.
Now, the loading limit is set to 240 items (8 pages), allowing for faster loading. As you scroll through these items, the spinner will appear again, and you will also see the exact number of items found in the tabs and pagination.
For the issue count, if you have fewer than 1,000 reports, you will see the exact number. If the count is 1,000 or more, we will display a rounded number (e.g., “1K+”, “1.5K+”), always rounded down to the nearest 0.5K increment for better performance.
For example:
Note: PURs are not part of this change and will temporarily remain as “500+K”.
2. Issues Tracker Interface: In this version, we introduced changes to UR icons, related to a future pre-beta process mentioned in this Announcement topic.
We have already received valuable feedback regarding the sizing of the new icons during beta testing and have passed it on to the team for evaluation.
3. Performance Improvement: We have changed how WME handles map markers (permanent alert icons, house numbers, closures, etc.). This improves memory usage when the related layers are enabled, making the experience smoother, especially during long sessions.
Please observe these changes and share feedback if you notice any improvements or issues.
4. SDK Improvements: Check the change log for updates related to the SDK.
Bug fixes:
We have released 4 bug fixes:
1. Segment Attribute Suggestions:
- We fixed an issue where edit suggestion mode prevented Level 4–6 editors from saving new segments directly in their area.
- Also fixed a case where users were unable to split a segment by creating a new one (the change was being reverted).
2. Place Update Requests: We fixed a case where the house number was not displayed in Place Update Requests (PURs).
3. Closures: Fixed an issue where the “Source” field was automatically associated with the “French Community,” even when the “None” option was selected.
- This issue was raised by the French Community.
Known issues:
1. UR Icons:
- The chat bubble with three dots appears near the UR pin only after the first comment and disappears when refreshing the map >> a fix is already in progress.
- Icons for URs closed as “Not Identified” are being displayed with incorrect and inconsistent sizes on the map.
You can read more about this version here.
We look forward to your feedback! ![]()
Thanks,
By: Olesya


