[Script] WME Place Interface Enhancements

But URO+ already has that option, it can also hide/show area/point venues.

So sort of a hybrid between PIE and Quick HN?

As I’m mapping some RPPs in a shopping center, I’m using PIE’s copy function to create the new PP. However, I still have to enter the HN (or use the copy/paste function from WMEPH) onto the new place. Is there anything I’m missing, or is it possible to have the checkbox attributes that exist in WMEPH to be copied/pasted onto the new place?

Yes, could also be good if the stores are increasing in consistent number pattern. Just a thought to take two cool scripts and combine the power…

Boa tarde… Nao estou conseguindo atualizar, ao abrir o Editor abre a pagina para Atualizar ai vou la reinstalo e ao sair blza… Depois vou entrar novamente da isso para instalar, oque pode esta acontecendo. Poderiam me ajudar.

To usando o Chrome.

Sem mais… AbraƧos a todos

Update released - 2018-03.12.01

Implemented MapOMatic’s Google Link Enhancer library.

This allows highlighting of Places with linked Google POI that is marked permanently closed in Google Maps, is >400m from the Waze Place, Place with a bad link or if a Place has a Google link that is linked in other Places.

You can see from the screenshot below that this Place has an invalid link, signified by the outer red ring. When you select the Place the invalid link is highlighted in red as well.

Below is a list of what is highlighted by the GLE library:

  • red = Google POI closed
  • teal = Google POI >400m from Place
  • magenta = bad link
  • orange (link field) = linked to more than one Place
  • gray (auto-complete dropdown) = already linked

This option can be toggled in the Map Changes section

2 Likes

Thanks for incorporating that, Justin!

A word of caution: Make sure the Google link was actually linked to the correct place, then verify the place was actually closed (do not rely on this flag as your only source – Google is not perfect). Follow your local guidance for handling closed places. For USA: https://wazeopedia.waze.com/wiki/USA/Places#Closed

1 Like

So I have been running MoM’s separate script for some time and it was working earlier today. I updated to the new PIE release, disabled the standalone script, and refreshed getting an error on the console. This is on Firefox and TamperMonkey.

PIE error:

SyntaxError: JSON.parse: expected ':' after property name in object at line 1 column 78 of the JSON data [Learn More] vendor-667ad18bc0086df37c16.js:24:56631 de.parseJSON https://editor-assets.waze.com/production/js/vendor-667ad18bc0086df37c16.js:24:56631 GoogleLinkEnhancer moz-extension://92e3fba6-b3ce-4ff2-b8f8-51a527939080/userscript.html:3532:41 init moz-extension://92e3fba6-b3ce-4ff2-b8f8-51a527939080/userscript.html:4485:15 bootstrap moz-extension://92e3fba6-b3ce-4ff2-b8f8-51a527939080/userscript.html:4475:13 bootstrap/< moz-extension://92e3fba6-b3ce-4ff2-b8f8-51a527939080/userscript.html:4477:37

I then switched back to the Google Link Enhancer script to troubleshoot and it also won’t load now:

SyntaxError: JSON.parse: expected ':' after property name in object at line 1 column 78 of the JSON data [Learn More] vendor-667ad18bc0086df37c16.js:24:56631 de.parseJSON https://editor-assets.waze.com/production/js/vendor-667ad18bc0086df37c16.js:24:56631 GoogleLinkEnhancer moz-extension://92e3fba6-b3ce-4ff2-b8f8-51a527939080/userscript.html:40:41 init moz-extension://92e3fba6-b3ce-4ff2-b8f8-51a527939080/userscript.html:930:19 bootstrap moz-extension://92e3fba6-b3ce-4ff2-b8f8-51a527939080/userscript.html:941:9 bootstrap/< moz-extension://92e3fba6-b3ce-4ff2-b8f8-51a527939080/userscript.html:943:26 f</< https://www.waze.com/en-US/editor/:2:477 ga/c[d] https://www.waze.com/en-US/editor/:54:125

Very awesome inclusion, Justin. Thank you SO much!

Excellent addition. Already finding problem places needing attention, that would otherwise be missed without a place-by-place review in an area.

This enhancement really helps editing PP’s especially in urban areas! Appreciate the ā€œheads upā€ given by the colored ring! A quick check of the web and one is set! Thanks!

Such an excellent addition! Thanks Justin and MoM!

Sent from my iPhone using Tapatalk

LOVE the new Google Place Link Enhancer. Definitely helps in finding problematic Google Links and flagging us to submit issues to Google Maps also. THANKS

Awesome addition to an already awesome script! Thanks!

So now that you created this awesome addition, is there any chance WME provides you the ability to have a mouse-over bubble to act as a legend? :slight_smile:

You mean the tooltip that already exists? :lol:

Hey guys, I just recently discovered this nice tool. Excellent job!

However, since I installed the script, I keep having issues with WME, making segment and place selection impossible. It’s like there is an invisible layer blocking access to everything underneath. Others have reported this as well, in the Benelux.

A refresh doesn’t help, I need to disable WME PIE, then refresh, then re-enable WME PIE, and then it works again for some time.

Hope you can look at it. If you need more info or a screenshot, let me know. Also available on Discord, if that’s handy :wink:

Does this happen across the entire map area, or only on one small portion? There is a bug in WME (reported to staff) associated with the Google Street View control. This means there is a 100x100 pixel area on the screen at all times that prevents selection of anything underneath it. This area starts in the top left corner, but moves around as you pan the map, resetting it’s position when you change zoom. After a number of saves without refreshing the browser window, this area can also obstruct WME controls like zoom, my location and - ironically - the GSV control.

WME FixUI includes a ā€œShow map-blocking WME bugsā€ function to make this problematic area visible, so you know where it’s interfering.

Ian, I have the WME FU ā€œred squaresā€ active/visible, so I’m pretty sure it’s not that, although the behaviour is similar. It’s all over the screen/map.

I’ve never seen anything like this before and cannot reproduce. > 1600 installs and you are the first one to report something along these lines so I’d say it’s probably a unique setup that is causing this. Have you checked the console for red errors that might be related to this script?

[Edited] Sorry duplicated post, please read next