Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.
Post by jwe252
Cannot delete a place with this script enabled since the update.
jwe252
Country Manager
Country Manager
Posts: 164
Has thanked: 58 times
Been thanked: 55 times
Send a message

Post by kahlcolimon
It's necessary to update the initial link of the script of this forum. Go to version 1.0.2.
kahlcolimon
Coordinators
Coordinators
Posts: 2840
Has thanked: 585 times
Been thanked: 1893 times
Send a message
Kahl Colimon
Waze Colombia Coordinator/Waze Global Champ
Country Manager/First Responder Member
App Beta Leader/WME Beta Tester

https://s.waze.tools/gc.png

Post by KC-Guardrail
PsstDizel wrote:Thank you for the script, I just found out about it and it's great.

One minor issue though. It snaps to any segment type including non-driveable segments if available, I have one place where it's closest to a railroad and it snaps to that.

Maybe you can add a filter to only snap to driveable and non-routeable but not to non-driveable?
The easy solution is to add a PLR so it will snap to that road, instead of the RR track. I fill my day adding PLRs, so the user will get closer to the actual place.
KC-Guardrail
Posts: 305
Has thanked: 62 times
Been thanked: 123 times
Send a message

Post by KC-Guardrail
sketch wrote:
KC-Guardrail wrote:
PsstDizel wrote:Thank you for the script, I just found out about it and it's great.

One minor issue though. It snaps to any segment type including non-driveable segments if available, I have one place where it's closest to a railroad and it snaps to that.

Maybe you can add a filter to only snap to driveable and non-routeable but not to non-driveable?
The easy solution is to add a PLR so it will snap to that road, instead of the RR track. I fill my day adding PLRs, so the user will get closer to the actual place.
That's not a solution. Waze won't navigate you to a railroad anyway. The problem is not that the place would put you on a railroad, but that the script will put a place on a railroad.
Correct me if I'm wrong, but the script isn't putting it on the RR tracks, it's just showing where the closest segment is, related to where you put the place point. Without the script, the stop point will still be in the same spot.
KC-Guardrail
Posts: 305
Has thanked: 62 times
Been thanked: 123 times
Send a message

Post by kkesley
It is an excellent tool ;)
kkesley
Waze Mentor
Waze Mentor
Posts: 988
Has thanked: 1682 times
Been thanked: 495 times
Send a message


Primeiras Informações:
Leia Aqui Primeiro!|Novo no Waze? Se apresente Aqui!
Manuais e Fórum Brasil:
Manual do Edição|Fórum WazeBR

Consulte nossa: Wazeopedia

Post by lg1992
The modified extension also works on my Chrome under Tampermonkey, but only if I disable another extension, WME KeepMyLayers.
lg1992
Country Manager
Country Manager
Posts: 6855
Has thanked: 261 times
Been thanked: 1176 times
Send a message
Leonid, Country Manager, Israel

Post by lg1992
I've found that the script blocks modifying or deleting JB both in beta and production WME. When I select JB, the Delete button in the tool bar stays disabled. If I check on some route within JB, the buttons Save and Undo stay disabled.

Tested in Chrome on Windows, Israel server. Everything works properly if I disable WME Closest Segment in Tampermonkey dashboard and then reload WME.
lg1992
Country Manager
Country Manager
Posts: 6855
Has thanked: 261 times
Been thanked: 1176 times
Send a message
Leonid, Country Manager, Israel

Post by lg1992
I have the version 1.0.27. Just to be sure, I reinstalled it and disabled all other scripts and extensions. I still see the problem.
lg1992
Country Manager
Country Manager
Posts: 6855
Has thanked: 261 times
Been thanked: 1176 times
Send a message
Leonid, Country Manager, Israel

Post by lg1992
When I select JB, the following error appears in the console:

VM1300:214 Uncaught TypeError: Cannot read property 'navigationPoint' of null
at e.checkSelection (eval at <anonymous> (:2:297), <anonymous>:214:62)
at initialize.triggerEvent (https://www.waze.com/assets-editor/js/v ... s:100:6363)
at e.value (https://www.waze.com/assets-editor/js/a ... s:12:16171)
at initialize.triggerEvent (https://www.waze.com/assets-editor/js/v ... s:100:6363)
at initialize.select (https://www.waze.com/assets-editor/js/a ... s:15:13936)
at initialize.clickFeature (https://www.waze.com/assets-editor/js/a ... s:15:11904)
at initialize.callback (https://www.waze.com/assets-editor/js/v ... :101:27046)
at initialize.triggerCallback (https://www.waze.com/assets-editor/js/v ... s:102:8483)
at initialize.handle (https://www.waze.com/assets-editor/js/v ... s:102:8008)
at initialize.click (https://www.waze.com/assets-editor/js/v ... s:102:7119)

lg1992
Country Manager
Country Manager
Posts: 6855
Has thanked: 261 times
Been thanked: 1176 times
Send a message
Leonid, Country Manager, Israel

Post by lg1992
Resolved indeed. Many thanks.
lg1992
Country Manager
Country Manager
Posts: 6855
Has thanked: 261 times
Been thanked: 1176 times
Send a message
Leonid, Country Manager, Israel