Moderators: Unholy, bextein, Glodenox, JustinS83
Forum rules
Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.
DO NOT START a new thread unless it is about a new idea. Keep discussion of existing tools within the main thread for that tool.
The official index of these tools is the
Community Plugins, Extensions and Tools wiki page.
by steveinark » Sun May 06, 2018 8:20 pm
I did delete the old script version. Following the instructions carefully, I believe. After pressing INSTALL, Tampermonkey comes back with a text box stating:
Unable to parse this! Any advice is welcomed.

[ img ]Arkansas State Mgr (SM)South Central Region Multi-State Mgr (MSM): AR + Louisiana - Mississippi - Oklahoma - TexasSteve (Eureka Springs, AR)
-
steveinark
- State Manager

-
- Posts: 403
- Joined: Sat Apr 19, 2014 1:52 pm
- Location: Eureka Springs, AR, USA
- Has thanked: 512 times
- Been thanked: 168 times
by steveinark » Sun May 06, 2018 8:49 pm
Still getting the same parse error on what I think is manually loading the script. Sure I am doing something wrong, LOL.
Will work to resolve it later. Got a little local help from JM. 1.0.98 loaded. Thanks for the continued support of this great script, dbcm!
Last edited by
steveinark on Sun May 06, 2018 9:39 pm, edited 1 time in total.
[ img ]Arkansas State Mgr (SM)South Central Region Multi-State Mgr (MSM): AR + Louisiana - Mississippi - Oklahoma - TexasSteve (Eureka Springs, AR)
-
steveinark
- State Manager

-
- Posts: 403
- Joined: Sat Apr 19, 2014 1:52 pm
- Location: Eureka Springs, AR, USA
- Has thanked: 512 times
- Been thanked: 168 times
by Stochiero » Sun Nov 19, 2017 11:10 am
I can't install magic either.

-
Stochiero
- Emeritus Local Champ

-
- Posts: 607
- Joined: Thu Dec 05, 2013 6:39 pm
- Location: Belo Horizonte/MG
- Has thanked: 370 times
- Been thanked: 447 times
by Stochiero » Sun Nov 26, 2017 11:37 am
jdtech4u wrote:I had problems installing it also. After some recommendations from Discord chat I opened the .js script that downloaded with Notepad. I "select all" the body of the document, created a new script in TamperMonkey and pasted the contents from the Notepad Document and saved it. The script ran fine after that.
I could only install today following these steps.
Thank's
-
Stochiero
- Emeritus Local Champ

-
- Posts: 607
- Joined: Thu Dec 05, 2013 6:39 pm
- Location: Belo Horizonte/MG
- Has thanked: 370 times
- Been thanked: 447 times
by subs5 » Tue Jul 04, 2017 3:27 am
Any way to get ramps and private roads to not highlight as need SL in USA?
-
subs5
- Country Manager

-
- Posts: 1931
- Joined: Sun Aug 17, 2014 7:05 pm
- Location: Virginia, USA
- Has thanked: 669 times
- Been thanked: 962 times
by subs5 » Thu Feb 08, 2018 6:34 pm
For the warning that segment is not protected I have noticed an errors:
This
minor highway (mH) roundabout is flagged as not protected when locked to L3, which is the correct level for the MidAtlantic Region (MAR). Notice that the
mH segments from RA are not flagged even though they are L3 too. Not sure what is causing this flag.
-
subs5
- Country Manager

-
- Posts: 1931
- Joined: Sun Aug 17, 2014 7:05 pm
- Location: Virginia, USA
- Has thanked: 669 times
- Been thanked: 962 times
by subs5 » Fri Feb 09, 2018 5:46 am
ldriveskier wrote:It is being flagged due to the ramp attached to the SW part of that roundabout being locked at L4.
So is that a Magic rule that the RA has to be locked to the highest level attached to it? Normally it is locked to the regions rules for the lock level of the road type.
-
subs5
- Country Manager

-
- Posts: 1931
- Joined: Sun Aug 17, 2014 7:05 pm
- Location: Virginia, USA
- Has thanked: 669 times
- Been thanked: 962 times
by subs5 » Fri Feb 09, 2018 4:02 pm
jm6087 wrote:It is a setting per state/region in the US. WV selected Highest Connected on the
Magic Setup Tab[ img ]
Thanks will bring it up with the MAR leadership since this is not a rule that we typically have in MAR. Will see what people want prior to doing anything to change.
-
subs5
- Country Manager

-
- Posts: 1931
- Joined: Sun Aug 17, 2014 7:05 pm
- Location: Virginia, USA
- Has thanked: 669 times
- Been thanked: 962 times
by subs5 » Sun Feb 18, 2018 5:41 am
Should the High Importance - Small (less than 5 m) segments be changed to check for <6 m?
The new minimum length is 6 m.
Here is the
wazeopedia reference that says 19.69 ft (6 m).
-
subs5
- Country Manager

-
- Posts: 1931
- Joined: Sun Aug 17, 2014 7:05 pm
- Location: Virginia, USA
- Has thanked: 669 times
- Been thanked: 962 times
by subs5 » Sat Mar 24, 2018 1:39 am
Can we get the error message title for the min length of a segment changed to be "Small (less than 6m) segments : ⁉️ 511164363 " vice the current 5 m?
Here is the reference wazeopedia page for
minimum segment length.
Magic properly highlights a segment less than 6 m, and states "Make this segment minimum 6m long or more. If you can't it may be worth connecting it on the closest node rather than leaving a micro segment on the map." but the title still lists 5 m.
-
subs5
- Country Manager

-
- Posts: 1931
- Joined: Sun Aug 17, 2014 7:05 pm
- Location: Virginia, USA
- Has thanked: 669 times
- Been thanked: 962 times
Return to Addons, Extensions, and Scripts
Who is online
Users browsing this forum: Mapman44