New WME v2.352

[LihtsaltMats]

@Kasia-staff

the view you shared is expected. The Super-Resolution Sentinel 2 layer was implemented to provide the most recent global data. While it might be not as clear as other layers, but it is continuously refreshing globally. Please cross-reference this layer with other sources, as we are aware that in some cases it might not be 100% accurate.

The clarity isn’t the problem. The problem was that the layer wasn’t loading and most of the screen was gray.

Seems like something has changed because it’s loading now and it’s actually usable.

The spots on this screenshot actually resolved now.

[searchjaunt]

@Kasia-staff

@searchjaunt , could you please check if clearing browser cache would help? I’d like to exclude the option of caching problem.

It’s occurring on different systems an OSes, so probably not cache related

[G_W1Z]

This may not be a WME prod version issue, but the Waze3rdParty account is messing up gas station places. They are removing categories, such as convenience store, car wash and ATM, as well as street names.

Here are examples:

https://waze.com/en-US/editor?env=usa&lat=40.26877&lon=-76.74793&marker=true&zoomLevel=19&venues=185663891.1856311227.65269

https://waze.com/en-US/editor?env=usa&lat=40.13137&lon=-76.21728&zoomLevel=19&venues=185991569.1859784621.41172

[turbomkt]

@searchjaunt

The new messages indicator doesn’t reset anymore after reading the messages. This used to work though, but now the only way to reset is to read the messages via the app which is a bit odd. There isn’t any function to mark the messages read either.

A long term issue has been that muted chats still alert.

[searchjaunt]

It is not muted though. The not read indicator doesn’t change when the messages are read. A mark as read indicator would be a nice functionality

[AndyLaode]

@Kasia-staff

Connecting existing segments will now behave the same as drawing new ones:

What I like about this release, the new feature “Connecting existing segments will now behave the same as drawing new ones,” is a productivity killer for remote areas that need a lot of drawing. However, I see that the bug regarding the typo in WME and SDK, “CULTURE_AND_ENTERTAINEMENT,” has not been fixed. The index.d.ts of the SDK still contains the typo, as does the WME.

issue tracker

[RafaCintron]

@Kasia-staff

could you please specify if the filter is not applied or if the option is missing? Also, it would be helpful if you could share some screenshots for better understanding.

Never mind. It was my fault. I had the 0 comments selected, and it was showing me all new URs with automated comments.

But is that WAD?
I would like to see automated comments older than 2 days, and this filter is not doing it. If I select 0 comments, it brings all of them, even the newer ones.

[RafaCintron]

This doesn’t work either. It just brings everything, not just the ones older than 2 days.

[RafaCintron]

@sh-oded

This feature should be applied also to the situation of no (0) comments to allow handle/close old URs that no one has responded to

This is exactly what we need. 2 days after an automated comment (or no comment) we have to send a “reminder” to the reporter. Right now we can’t.

[Lizton42]

@turbomkt Looks like my analysis was premature… I got great images the first few hours, then everywhere I went was out of focus or cloudy.

[turbomkt]

Wait. Let it load. It will take a long time.

[Nataliia_Staff]

@G_W1Z

This may not be a WME prod version issue, but the Waze3rdParty account is messing up gas station places. They are removing categories, such as convenience store, car wash and ATM, as well as street names.

Here are examples:

https://waze.com/en-US/editor?env=usa&lat=40.26877&lon=-76.74793&marker=true&zoomLevel=19&venues=185663891.1856311227.65269

https://waze.com/en-US/editor?env=usa&lat=40.13137&lon=-76.21728&zoomLevel=19&venues=185991569.1859784621.41172

Hi @G_W1Z,

Thank you for flagging this issue. Could you please check the examples you have listed? I can see categories other than “Gas stations” assigned to both of them.

Maybe you have fresh examples of misbehavior?

And I want to add that the team is currently addressing this problem, I will update you when they share news.

Regards,
Nataliia

[G_W1Z]

Thank you for looking into this.

The examples I provided now have their categories back, but their street names are still missing.

[Nataliia_Staff]

@G_W1Z

The examples I provided now have their categories back, but their street names are still missing.

Thank you @G_W1Z for the comment. I have checked with the team. They are working on restoring the data; the work is in progress. I will update you when I have more information to share.

Regards,
Nataliia

[mudge42]

This has begun appearing in some Place Update Requests:

[turbomkt]

I’m seeing the same thing. The number displayed is not the number added to the place. What’s added does seem to be what the Wazer adds to the PUR. I have not yet checked if this is script based or native.

[tbrks]

There’s a bug open for it here: https://www.waze.com/discuss/t/edit-venue-fields-updated-on-in-purs-unix-timestamps/405394

[Kasia-staff]

Hello everyone,

Thank you for the feedback.

@LihtsaltMats

The clarity isn’t the problem. The problem was that the layer wasn’t loading and most of the screen was gray.

@LihtsaltMats , could you please confirm if now the layer loads fully?

@searchjaunt

It’s occurring on different systems an OSes, so probably not cache related

@searchjaunt , thank you for the information. Could you please also share if the problem is reproducible for all chats or only group ones and the issue you experience is similar to this?

@AndyLaode

What I like about this release, the new feature “Connecting existing segments will now behave the same as drawing new ones,” is a productivity killer for remote areas that need a lot of drawing.

@AndyLaode , I would appreciate it if you could share more on how this feature makes productivity worse. As for the SDK issue, it’s still under investigation.

@RafaCintron

But is that WAD?
I would like to see automated comments older than 2 days, and this filter is not doing it. If I select 0 comments, it brings all of them, even the newer ones.

@RafaCintron , the ‘Above the number of days’ filter indeed can’t be applied to the URs with no comments or automated comments so this is expected behavior. Could you please confirm if you want to have such URs hidden from the results or if the feature you would like to have is similar to this suggestion? Also, it would help a lot if you could submit a UserVoice suggestion and link it here.

@mudge42

This has begun appearing in some Place Update Requests:

@turbomkt

I’m seeing the same thing. The number displayed is not the number added to the place. What’s added does seem to be what the Wazer adds to the PUR. I have not yet checked if this is script based or native.

@mudge42 and @turbomkt , thank you for sharing your reports. Could you please upvote this thread?

@tbrks

There’s a bug open for it here: Edit.venue.fields.updated On in PURs - Unix Timestamps

@tbrks , thank you for linking the parent issue.

Kind regards,
Kasia

[RafaCintron]

@Kasia-staff

or if the feature you would like to have is similar to this suggestion?

Yes, I would like to have the filter applied to URs with 0 comments (automatic comment or no comments).
Here’s the uservoice link:
New filter “Older than” should apply for URs with no comments – Waze Suggestion Box

[searchjaunt]

@Kasia-staff

@searchjaunt , thank you for the information. Could you please also share if the problem is reproducible for all chats or only group ones and the issue you experience is similar to this?

It seems to happen less currently, so hard to reproduce now. It concerns the Belgian local editors group. It sounds similar to the reported bug although there is no clear indication there either