[Script] WME Toolbox (until 1.5.9, now archived)

[sketch]

@doctorkb

It was tweaked very slightly – the simplify(0.5) was leaving far too many in rounded curve areas, but after experimentation, I settled on 0.8. I didn’t change any of the other code.

EDIT: oh yeah, the other change is that it stops when the edit count hits 100, and follows standard TB integration with that edit count monitoring. It alerts in the same way TB does, rather than the method used by the original (which also wouldn’t stop at 150, but would only do 150 for each of the executions of the bookmarklet)

Got it. Though it’s not to my taste, that should be fine.

Also – does it retain the part of the code where, if segments are selected, it will simplify only those segments?

[doctorkb]

@sketch

Got it. Though it’s not to my taste, that should be fine.

Also – does it retain the part of the code where, if segments are selected, it will simplify only those segments?

Yup.

If it were desired, we could probably split it into two functions: one that does all segments (and is available to higher-level editors) and one that only does selected segments (is available to all editors).

Would that be desirable?

[PesachZ]

@doctorkb

@sketch

Got it. Though it’s not to my taste, that should be fine.

Also – does it retain the part of the code where, if segments are selected, it will simplify only those segments?

Yup.

If it were desired, we could probably split it into two functions: one that does all segments (and is available to higher-level editors) and one that only does selected segments (is available to all editors).

Would that be desirable?

I think so

Sent using Tapatalk for Android 4.4.2

[doctorkb]

@PesachZ

@doctorkb

If it were desired, we could probably split it into two functions: one that does all segments (and is available to higher-level editors) and one that only does selected segments (is available to all editors).

Would that be desirable?

I think so

Ok, so we’re clear, right now this feature is only available to AMrank3+, CM and Rank 5+. These are the same permissions as the “suppress unneeded junction nodes” feature.

Because of the safety (i.e. I have yet to see it make a change that is inappropriate) and the massive improvements this can have for the map database, I don’t want to further restrict that.

The question is: do we want a separate function that is also available to Rank 1-2 and Rank 3-4 (non-AMs) that only works on selected segments?

[PesachZ]

@doctorkb

@PesachZ

@doctorkb

If it were desired, we could probably split it into two functions: one that does all segments (and is available to higher-level editors) and one that only does selected segments (is available to all editors).

Would that be desirable?

I think so

Ok, so we’re clear, right now this feature is only available to AMrank3+, CM and Rank 5+. These are the same permissions as the “suppress unneeded junction nodes” feature.

Because of the safety (i.e. I have yet to see it make a change that is inappropriate) and the massive improvements this can have for the map database, I don’t want to further restrict that.

The question is: do we want a separate function that is also available to Rank 1-2 and Rank 3-4 (non-AMs) that only works on selected segments?

I misunderstood then, but I could still agree with your proposal, if it is deemed truly safe. Though it could be combined with the TB segment select tool to then be used on hundreds of segments at a time, and possible point farming, if that’s a concern.

Sent using Tapatalk for Android 4.4.2

[sketch]

I think it should stay as-is. It’d be too easy to get around by using “select within landmark” anyway.

Now that we have this it’d be nice if the simple segment highlight code was either removed or realigned to match the segment simplifier.

[doctorkb]

@sketch

I think it should stay as-is. It’d be too easy to get around by using “select within landmark” anyway.

Or the select segment list.

Now that we have this it’d be nice if the simple segment highlight code was either removed or realigned to match the segment simplifier.

Yes. That’s a consideration. Interestingly, there are segments I’d like to see simplified (that get highlighted) but they aren’t touched by the simplify code. The trouble is that some of the ones that get highlighted shouldn’t be changed, so it’s not a matter of just increasing the action of the simplify code.

[Thortok2000]

Are there any tools in the toolbox to help with the monitoring, selection, and correction of alternate street names?

[doctorkb]

@Thortok2000

Are there any tools in the toolbox to help with the monitoring, selection, and correction of alternate street names?

Nope. What sort of tool are you thinking of?

[Thortok2000]

I want to verify the names of US, state, and county roads (or the equivalent in our state), make sure that they’re on every segment and not interspersed, verify city names, remove duplicates, etc.

I’d also like to be able to select all segments with the same alternate name in case some segments are mislabeled, etc. And be able to mass-edit the alternate names only while leaving all the other properties (including multiple different main names if necessary) intact.

Basically everything you can do with the main name of the street, search, select, mass edit, etc.

[PesachZ]

@Thortok2000

I want to verify the names of US, state, and county roads (or the equivalent in our state), make sure that they’re on every segment and not interspersed, verify city names, remove duplicates, etc.

I’d also like to be able to select all segments with the same alternate name in case some segments are mislabeled, etc. And be able to mass-edit the alternate names only while leaving all the other properties (including multiple different main names if necessary) intact.

Basically everything you can do with the main name of the street, search, select, mass edit, etc.

Be careful there some segments purposefully have no names for proper instructions. Like Wayfinders for example

Sent using Tapatalk for Android 4.4.2

[Thortok2000]

Indeed. But if say US-25 is known as ‘Wade Hampton Blvd’ the only way to double-check that US-25 is an alternate name on every single segment is to look at every single segment individually. A tool would be so much better. =P

[doctorkb]

issues logged for simple segment highlight tweaks and alternate name examination.

[SkiDooGuy]

@Thortok2000

Indeed. But if say US-25 is known as ‘Wade Hampton Blvd’ the only way to double-check that US-25 is an alternate name on every single segment is to look at every single segment individually. A tool would be so much better. =P

You can do this with a custom Validator check as well.

Template: ${altStreet}
RegExp: /US-25/

Any parts that aren’t highlighted, don’t have it.

[Arnoniem]

@BellHouse

Yes, bug confirmed. Tb does not remove the node, if the 2 segments are connected by both A or B nodes, and they are oneway in a consecutive direction (i.e. the oneway arrows point in the same direction, if you look at the segments).

That’s an easy one. We’ll fix it.

Thanks! Couldn’t find an example. Tried to create one but that did get fixed:)

[Arnoniem]

@SuperDave1426

If you manually delete that node, you’ll notice that sometimes the directionality is correct, and sometimes it is not. This can (and has for me) mean that you have a chunk of unuseable one-way because it is pointing the wrong direction.

You don’t want Toolbox to auto fix this (along with who knows how many others on the screen) unless it could be known that it will certainly point in the correct direction.
I would definitely agree with this. A while back, I was doing clean up near a freeway and noticed that two segments of freeway were joined by an unneeded junction node. They had exactly the same properties, were (obviously) both going in the same direction, same elevation, etc. So I deleted the node.

As I continued to work, I suddenly noticed that both the eastbound and westbound lanes had arrows on them showing the exact same direction - the direction of the freeway where I had removed the junction node had reversed. (Yikes!) If that had gotten into a map tile update… :shock:

Since then, I’ve always been extra careful to watch for a directional change on any one-way road segment when getting rid of an unneeded junction node. If I had been using an automatic “delete unneeded junction node” function of a tool, it would have greatly increased the chances that I could have missed that.

Of course, I’m sure I would then notice when the area lit up like a X-Mas tree with URs complaining that they were routed through back-roads in the mountains instead of using the perfectly good freeway…

I’ve had this happen twice without noticing… Found out after map update and ur’s!
So I would love to hear that that is fixed now

[MGODLEW]

@Thortok2000

Are there any tools in the toolbox to help with the monitoring, selection, and correction of alternate street names?

Script Request Name Swapper?

[edsonajj]

@Arnoniem

I’ve had this happen twice without noticing… Found out after map update and ur’s!
So I would love to hear that that is fixed now

This seems to be a WME problem, not a toolbox one. Therefore we should probably pester the staff (Irad in particular) about it.

[myriades]

Hi all.
I mentionned it to Oyyodams a few times ago. There is a problem with jquery-ui-1.10.3.custom.min.js vs buttons to toggle point/area
With Chrome Uncaught Error: cannot call methods on button prior to initialization; attempted to call method 'toggle' libs-98780e26.js:1 lt.extend.error libs-98780e26.js:1 (anonymous function) jquery-ui-1.10.3.custom.min.js:6 lt.extend.each libs-98780e26.js:1 lt.fn.lt.each libs-98780e26.js:1 t.fn.(anonymous function) jquery-ui-1.10.3.custom.min.js:6 (anonymous function) libs-98780e26.js:142 lt.event.dispatch libs-98780e26.js:2 y.handle
With firefox[code] Error: cannot call methods on button prior to initialization; attempted to call method ‘toggle’
.error(e=“cannot call methods on b…to call method ‘toggle’”)libs-98780e26.js (ligne 1)
t.widget.bridge/t.fn[i]/<()jquery-…min.js (ligne 6)
.each(e=Object[label.btn.btn-default], t=function(), i=undefined)libs-98780e26.js (ligne 1)
lt.prototype.each(e=function(), t=undefined)libs-98780e26.js (ligne 1)
t.widget.bridge/t.fnijquery-…min.js (ligne 6)
libs-98780e26.js(t=Object { originalEvent=Event click, type=“click”, timeStamp=0, plus…})libs-98780e26.js (ligne 142)
lt.event.dispatch(e=Object { originalEvent=Event click, type=“click”, timeStamp=0, plus…})libs-98780e26.js (ligne 2)
lt.event.add/y.handle(e=click clientX=140, clientY=338)libs-98780e26.js (ligne 2)

... e)return!1;return!0},error:function(e){throw Error(e)},parseHTML:function(e,t,n...[/code]

[AlexN-114]

@Thortok2000

Indeed. But if say US-25 is known as ‘Wade Hampton Blvd’ the only way to double-check that US-25 is an alternate name on every single segment is to look at every single segment individually. A tool would be so much better. =P

Highlighter City can show you that there is an alternative name. [emoji1] But you don’t see the content of the alternative name.