[Script] WME Place Interface Enhancements

I have noticed that enabling PIE, moving on the map has serious problems, is anyone having the same problem?

Time to time - while working on PURs or adding new places WME will froze - after reloading WME place is added/updated. PIE disable and I have same problem. Problem is intermittent so hard to troubleshoot.

1 Like

I’m observing the same. I can’t determine if PIE has to something with it.

1 Like

The script has been updated to 2025.01.13.01, and now it doesn’t show the location of a linked Google place and doesn’t marks far or closed places with colors.

2 Likes

There is a comment in the script: - Per Waze on 1/12/2025, they prefer we don’t surface Google info in WME. Disabling this code, maybe permanently.

There is a comment in the script: - Per Waze on 1/12/2025, they prefer we don’t surface Google info in WME. Disabling this code, maybe permanently.

Would be nice if they disabled showing Google Maps items if there is a Waze place. Would solve a lot of URs that way and solve some very old Bug reports.

6 Likes

That option was very good while adding external providers or moving PPs to new spots… :frowning:

Also thanks to that option (WME showing linked place on GM) I was able to fix many bad locations on Google Maps :smiley:
So no more reports to GM…

8 Likes

So sad, the most important and useful feature of this script now has gone.

5 Likes

Yeah, I don’t understand why Waze would include Google Places if Waze has a Place. I thought originally it was stated that the idea was that Google would be used if it existed and Waze didn’t have a confirmed Place at a location, and then use the Waze Place if it was. Sadly, it looks like the corporate masters are calling the shots now… :frowning:

The extension is considerably less useful now, though certainly not completely useless. But like Jorge-RC said, one of the most important features of the plugin is gone. I don’t blame the script author; he’s just following the request from Waze that was most likely dictated by Google.

Edit: That was in reply to Subs5. I can’t seem to see the function to quote the message that you’re replying to. It does seem to have one, since I can see at least one where people are quoting; I’m just blind, I guess… :thinking: :laughing:

3 Likes

You can click on the top left corner while replying to quote original message

Original post will show extra button

And link to original post in your reply :smiley:

1 Like

It also seems funny that Waze is now dictating what is in scripts. For years they were so anti-script. Scripts do bring a lot of functionality that should be inherent in WME

I understand that Waze is working with the script writers a lot more now. Which is good, but the whole purpose of scripts is to have functionality that we find useful or actually need like junction angles. etc.

Don’t blame the script writers from removing the feature since it was requested but just seems strange that they requested that one feature, but won’t fix the Waze search.

4 Likes

[quote=ā€œkrzycholub, post:871, topic:217315, full:trueā€]
You can click on the top left corner while replying to quote original message

Original post will show extra button[/quote]

Ah, ok, I see that now. Thanks! :saluting_face:

Edit: Um, ok that didn’t work as expected. I guess I’ve got some more experimenting to do, to figure out what I’m doing wrong. :laughing:

1 Like

Well, this one appears to be quoting ok… :man_shrugging: lol

Yeah, I agree. The whole point of scripts is so that features that are missing from WME that are useful to the editing community can be added. Seems like it kind of defeats the purpose if Waze is now dictating what scripts can and can’t do to this degree. From people writing those scripts for free (I.E. aren’t Waze employees)…

But no, I absolutely don’t blame any script writer for following the directives of Waze. :+1:

2 Likes

The people that are saying ā€œif Waze is now dictating what scripts can and can’t doā€¦ā€ clearly have no idea what has happened in the last 10+ years. This isn’t new. They have numerous times come out and said we cannot do something. They have to if it brings copyrighted data into their environment and potentially puts them in legal hot water, which is the implication in this case (no, it doesn’t make sense to me either).

The main issue with this change, however, is we have had no less than 4 other Waze employees tell us that we can use the API as we were (after requesting them to review it for acceptability), encouraged it, and used it in the scripts themselves. Now we have been told we can’t use it.

There isn’t enough communication on the Waze side when these decisions are made and we get conflicting answers from multiple employees. While frustrating, it also isn’t a new phenomenon.

Unfortunately, I don’t know the right person to complain to anymore.

5 Likes

Yeah, I just knew my intent didn’t come across right. I tried adding ā€œto this degreeā€ as a way to indicate that I was aware that they’ve always been able to do so. Clearly, I failed in that. Sorry.

I understand about copyright issues and so on, but with Google owning them, and they seem to have no problems with pulling data from Waze maps to add to Google Maps, it just strikes me as odd that they would suddenly have issues with our using information from the GM side (such as ways of tying a Google Place marker with a Waze Place, to confirm for the driver that they’ve got the right location). And as someone else mentioned, that feature which showed where the Google Place marker was gave us a chance to go to the GM side of things and put in a suggested correction for a place that’s located wrong. Now, there’s no way to do that.

Waze’s communications on things like this have never been particularly good, but these are the sorts of things that make no sense as to why after all this time it’s suddenly a problem for Google - and you’re going to have a hard time convincing me (and probably many others) that it wasn’t due to an edict that came down from Google.

Well, whatever. Nothing we can do about it, but we don’t have to like it. I’ll stop here, since I’ve pretty much said what I want to say on the subject.

4 Likes

Alphabet is the company that owns Waze and Maps
Maps takes information from waze and the press (in France) has just announced that more and more users are moving to maps.
And now, waze prevents maps updates to be used in waze?
Does Alphabet want waze to die?

It would be interesting if a waze manager could come and answer here so that all volunteer editors can know exactly how they will be treated in the future.

2 Likes

Total nonsense from Waze…

2 Likes

I’ve asked again just to make sure we weren’t misunderstanding each other, and the answer was the same: we should not be using the Google Maps API to pull in any extra data – for legal reasons. I have no clue what the legal reasons are, and it makes no sense to me, but I also don’t have a legal team that can look into these things :smirk:

Maybe I’d get a different answer if I asked someone else at Waze today. As Justin mentioned, we got a different answer from others previously. And other editors have said that staff at meetups said it was fine to use Google Maps information (though that was likely not in the context of pulling that data from the API and displaying it in WME, which is a different legal question). But the person I’m working with is our designated point of contact for scripting, so I’m assuming it’s the current official Waze answer.

Having said that, they are aware of our complaints and are working with the Google team to find a solution. Unfortunately it’s still early so they can’t give details or a timeline yet.

I spent a lot of time writing that code and used it regularly. I really hated to disable it. But if it was one of the things that helped prompt them to come up with a solution that isn’t a ā€œscript hackā€, I’m fine with all of it. I just hope the solution is what we really need, and not what they think we really need.

18 Likes

Just seems strange that the app can use the Google Maps location but we can’t see what it is with the script. smh…

5 Likes