[Script] WME Toolbox

[la-colle]

Since yesterday after each launch of WME Beta with WME toolbox I have that message : “WME Junction Node Fixer (in Toolbox) has failed to load due to API check: FeatureVectorSegment” no other scripts activated.

[BellHouse]

@la-colle

Since yesterday after each launch of WME Beta with WME toolbox I have that message : “WME Junction Node Fixer (in Toolbox) has failed to load due to API check: FeatureVectorSegment” no other scripts activated.

Yup, that is caused by a code update of WME, we’re on that one.

[iainhouse]

@SeveriorumPatrem

Don’t know if it has ever come up in the past… 162 pages is a lot to go through… but has there ever been discussion on the feasability/merits of adding a flag for problem turn angles at junctions? To highlight when a turn angle is at ~45 or ~168 degrees (the conditions which generate the warning yellow background in the JAI bubble)?

I don’t believe it has - not least because, as you point out, JAI already highlights these turns.

I’m guessing you want the turns highlighted without selecting them. There’s actually a fairly quick way of finding them. Use CTRL+SHIFT+mouse drag to select a large number of segments. JAI will show you hundreds of turn angles and any yellow ones will stick out like a sore thumb. If you see a yellow bubble, focus in to find it. If not, move on to the next chunk of segments. You can check hundreds of junctions very quickly like this. I always try to remember to do it as part of my “finishing” process.

[SeveriorumPatrem]

@iainhouse

I don’t believe it has - not least because, as you point out, JAI already highlights these turns.

I’m guessing you want the turns highlighted without selecting them. There’s actually a fairly quick way of finding them. Use CTRL+SHIFT+mouse drag to select a large number of segments. JAI will show you hundreds of turn angles and any yellow ones will stick out like a sore thumb. If you see a yellow bubble, focus in to find it. If not, move on to the next chunk of segments. You can check hundreds of junctions very quickly like this. I always try to remember to do it as part of my “finishing” process.

Yeah, that will work. The request crossed my mind when I was reading some more debate about the disappearance of the RevCon flags, and thought it would be nice to get some sort of similar passive visual alert for these bad turn angles without having to make an active attempt to find them. But not a big deal, probably higher priorities out there. That you, sir.

[BellHouse]

@denysdgcf

@aureozb

the function “Cut segment” is disabled in prod and beta ?

I did some tests:

1. If the segment has a “node”, the “cut segment” function divides the segment.

2. If the segment does not have a “node”, the “cut segment” function does not divide the segment.

Thank you.

Found the bug, will be fixed in next release.

[TWBudrys]

Does that option “Highlight of manual locks (greater, equal, less than automatic lock)” works fine?

[james890526]

—Comments removed, not sure why I posted here—

[dspille]

@TWBudrys

Does that option “Highlight of manual locks (greater, equal, less than automatic lock)” works fine?

Make sure the lock icon on the toolbar is toggled to green

[Phipsi]

Hi,
For some time past the function “Auto fix reverse connections, dead-end and unterminated roads” is not longer working for L3 user. I asked someone with L5 status and he can see this point in the list. I can’t see it.
Please can you add it for L3 users again?
Thanks

[vince1612]

@Phipsi

Hi,
For some time past the function “Auto fix reverse connections, dead-end and unterminated roads” is not longer working for L3 user. I asked someone with L5 status and he can see this point in the list. I can’t see it.
Please can you add it for L3 users again?
Thanks

See here: https://www.waze.com/forum/viewtopic.php?f=819&t=145570&start=1570#p1750983

[Keith_KJ]

I’ve done a search for ‘Edge’ in this thread, but I’ve not found anything.

I’ve always found Chrome a memory hog, and Firefox not much better. Are there any intentions of doing an Edge extension for Toolbox (if at all possible)?

This is the only thing that’s preventing me from editing on Edge, as Tampermonkey works fine on Edge, with all the other scripts available.

[Keith_KJ]

I’ve done a search for ‘Edge’ in this thread, but I’ve not found anything.

I’ve always found Chrome a memory hog, and Firefox not much better. Are there any intentions of doing an Edge extension for Toolbox (if at all possible)?

This is the only thing that’s preventing me from editing on Edge, as Tampermonkey works fine on Edge, with all the other scripts available.

[BellHouse]

Toolbox 1.8.4 is released for Chrome and Firefox:

1.8.4 (20180227) Fix: Place list did not show city name (#432) Fix: Minimap showed scrollbar and Waze footer (#430) Fix: WME produced error message "WMETB-JNF: failed API check, exiting: FeatureVectorSegment" (#429) Fix: Split segment failed if segment has only 2 geonodes (#428) Fix: Waze header was visible in minimap (#426) Fix: Internal JNF failed to remove u-turns (console error) (#425) Fix: Create junctions tool failed with console error (#424) Fix: Bugfix internal JNF: copying address on roundabouts Fix: Incompatibility of copy segment attributes function with other scripts Fix: FancyPermalink bugfix when reading configuration file Fix: Renamed Waze and OpenLayers objects for future compatibility (had produced a crash in beta WME for some time) Update: Auto-fix u-turns now (also) works on selected segments only (#412) Update: Updated country rights settings for Bangladesh and Iran

[denysdgcf]

@BellHouse

@denysdgcf

@aureozb

the function “Cut segment” is disabled in prod and beta ?

I did some tests:

1. If the segment has a “node”, the “cut segment” function divides the segment.

2. If the segment does not have a “node”, the “cut segment” function does not divide the segment.

Thank you.

Found the bug, will be fixed in next release.

Fixed.

Thank you

[helifino206]

@BellHouse

Toolbox 1.8.4 is released for Chrome and Firefox:

I get an error in FF 58.0-mint1.0 -

Error: WME ToolBox: can't detect WME main JS WME_Toolbox.prod.min.js%20line%20937%20%3E%20Function:9:8 anonymous moz-extension://d7f5f57b-e57e-43ff-812a-10aeeab59a02/scripts/WME_Toolbox.prod.min.js%20line%20937%20%3E%20Function:9:8 <anonymous> moz-extension://d7f5f57b-e57e-43ff-812a-10aeeab59a02/scripts/WME_Toolbox.prod.min.js:937:122 <anonymous> moz-extension://d7f5f57b-e57e-43ff-812a-10aeeab59a02/scripts/WME_Toolbox.prod.min.js:2:2

[helifino206]

@BellHouse

Toolbox 1.8.4 is released for Chrome and Firefox:

I get an error in FF 58.0-mint1.0 -

Error: WME ToolBox: can't detect WME main JS WME_Toolbox.prod.min.js%20line%20937%20%3E%20Function:9:8 anonymous moz-extension://d7f5f57b-e57e-43ff-812a-10aeeab59a02/scripts/WME_Toolbox.prod.min.js%20line%20937%20%3E%20Function:9:8 <anonymous> moz-extension://d7f5f57b-e57e-43ff-812a-10aeeab59a02/scripts/WME_Toolbox.prod.min.js:937:122 <anonymous> moz-extension://d7f5f57b-e57e-43ff-812a-10aeeab59a02/scripts/WME_Toolbox.prod.min.js:2:2

[atrophicshiner]

Toolbox currently highlights segments that have the new ghost Walking Trail node as simplifiable. If you use the Toolbox tool to removed this node the Walking Trail / segment node can no longer be moved and throws a save error, I assume as the node no longer exists.

Any way to stop this highlight when a Walking Trail in part of the (ghost)node.

[BellHouse]

@atrophicshiner

Toolbox currently highlights segments that have the new ghost Walking Trail node as simplifiable. If you use the Toolbox tool to removed this node the Walking Trail / segment node can no longer be moved and throws a save error, I assume as the node no longer exists.

Any way to stop this highlight when a Walking Trail in part of the (ghost)node.

Thanks for pointing that out! Registered as issue #433.

[anon33958190]

Toolbox strips out junction boxes and major traffic events from Permalinks. Can this be changed? I understand that MTE permalinks require mode=1 as well as the majortrafficevent ID

[BellHouse]

@Kartografer

Toolbox strips out junction boxes and major traffic events from Permalinks. Can this be changed? I understand that MTE permalinks require mode=1 as well as the majortrafficevent ID

Yes, it can and will (#435).