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.
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.
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.
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ā¦
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ā¦
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.
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.
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.
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.
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.
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
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.