The view of the Google Place icons has been improved to provide more information at first sight: a round pin with a corresponding category icon will appear on the map.
The team updated the map behavior when selecting a Google Place from the sidebar. The map will no longer center or ‘jump’ to the location of the selected place automatically. We expect this to improve the experience when reviewing Google Places.
Drawing Shortcuts Improvement: The team has streamlined the drawing process by ensuring that using a shortcut automatically activates the relevant layer group and layers inside it if they were in a disabled state.
For example, pressing ‘I’ now checks the Roads (Segments) layer so you can begin editing immediately.
You can still draw roads with the Roads layer toggled off. To do this, first press ‘I’, then manually uncheck the Roads layer in the layer switcher and start drawing. Snapping to existing roads remains functional even while the layer is hidden.
This same logic also applies to other editing actions within the Roads group. Selecting a Suggestion (related to segments properties changes) or adding a closure will now automatically enable the Roads group and relevant layers. This ensures the feature you want to use is immediately visible and ready for editing.
Featured Tasks: We refined the task card view by placing the article items for ‘Helpful links’ in the dropdown.
Add menu: To unify the view of House Numbers in WME, the ‘House Number’ menu icon has been enhanced by adding the number sign (#).
SDK improvements: please refer to the change log for the latest updates.
Bug fixes:
We released 3 bug fixes:
Layers: The team resolved the issue where city names appeared on the map even when the Cities layer and Display group were disabled.
Issue tracker: A fix was added for the problem where the PUR card closed automatically after clicking on the “Next” button several times.
UR icon: The icon for the UR pin on the map was improved to prevent its pixelation when zoomed in.
Could you please share whether the counter of unread messages is present and whether the chat button is grayed out? Or does it look normally but nothing happens when clicking on it?
Additionally, please let me know if any error message appears in console when you try to open the chat.
Changing High-speed crossing to Pedestrian crossing. I’m pretty sure the US asked for the change, but someone else obviously asked for High-speed crossing because it makes sense to them.
@Kasia-staff It opens normally, but nothing happens when you tap on it. Also, I should mention that it opens without any issues when accessed via Discuss.
Are we supposed to map all pedestrian crossings on all road types? This is pretty significant change in mapping Hyperlocal Permanent Hazards that differs from the instructionsin this mapping manual.
Yes, the US requested the language change, because we don’t have our own specific version of “english”; other countries can localize the terms as needed. Nothing substantively changes in terms of guidance.
Thread
Click to expand thread
Answers to questions
The “High Speed Crosswalk/Crossing” language didn’t fit the context of the intended hazard in the US, so we requested the change to “Pedestrian Crossing”. Actually, we had requested that “Pedestrian Crossing” be the language for several years before the PH was released, but that’s a long story.
However, HQ doesn’t have a “US English” language for the app. Only “generic” English. So, any change that impacts the US, becomes the default in the rest of the world. However, every (other) country has the opportunity to change their local translations via the Localization volunteers/team.
As far as I am aware, this does not constitute a change of guidance. Actually, it allows the US to be more specific in our guidance. A “high speed crosswalk” in the US implied all crosswalks on high speed roads should be added as a hazard. By switching to “Pedestrian Crossing”, we can define the specific situations that warrant adding a hazard. For example, a mid-block crossing designed by specific signage or having specific markings.
I disagree that this is simply a localization change for the US. Since HQ rolled this out globally across multiple languages, it effectively turned a single country’s localization request into a global feature redesign, undermining the feature’s core functionality.
Once users get tired of receiving alerts at every routine crosswalk, they will likely disable pedestrian crossing warnings altogether. As a result, they won’t be warned when approaching genuinely dangerous crossings on high-speed roads.
This change defeats the original purpose of this Permanent Hazard (PH), which was created specifically to warn drivers about dangerous pedestrian crossings on highways or high-speed roads. While I understand that these situations might be rare in the US, that could have been handled differently. For speed bumps, we have a checkbox to set them as destructive that determines how to trigger the alert.
If HQ changed an existing localization of other non-English languages, that is a bug that would be opened and resolved with the Localization team.
As far as I know, there is no change to the intent of the PH as described in documentation. The only intended change was to clarify the English name, as “high speed crossing” would be inaccurate to Waze’s intended implementation in the US. Has anyone told you to change your mapping guidelines?