[Script] WME Color Highlights - 2.33 Sept 2020

[qwaletee]

Tim,

A few people reported that whenever a segment got wrong speed data, it will fail to route properly. For example, here:

image.png

The segment goes from B-A, but no speed is saved for that direction. It is saved for A-B as you can see. Creating the segment again usually fixes the problem (sometimes we have to replace a few more segments).

In order to detect the zones with problems, is there any way you can add a color for this kind of issue?

I've seen things like that from time to time, too. But I'm wondering - what exactly can we do about it if we find one? Do we have the ability to adjust the average speed or reset it (without deleting the segment and recreating)?

If the reversed direction is accurate, I suppose you could preserve the speed data by disconnecting the end and reconnecting to swapped positions. That would also preserve house numbers, though they might be reversed and need monkeying with.

If the data is completely bogus, you have to either delete it wor wait for it to get updated with legit data (which may never happen if some corrupts database entry is what is causing the bad speed data to begin with - so, yeah, delete it and recreate, but try to recreate house numbers if its is fully bogus).

[qwaletee]

Looks like it is time for an update for segment speed data.

I just got on my main computer and saw the issue for Colour Highlights on every segment. Toolbox's FwdSpeed and RevSpeed were also 0 for every segment. Once the script writers get wind of the issue, a fix should be possible using averageSpeed. I currently cannot tell if that is useful for both directions though...because I'm a SQL developer

[qwaletee]

You think they should ask the users if they find it useful?

Because the routing server uses much smaller timeslices and doesn't use average speed at all (that we've been told), I haven't found average speed to be of much use.

I've found it useful in evaluating whether a "detour" might be due to faster speeds recorded on a side road. Maybe inaccurate, but where it shows that information, gives you a good clue. Otherwise, we're left shooting in the dark.

[qwaletee]

How is what you're talking about different from simply pressing shift-Z within WME to show restricted turns?

I was thinking the same.....
And with Shift-Z you can also see the actual turns not allowed on the editor.

Regards from Concepción, Chile,

That's an extra step for someone to remember during scanning. And one that most editors won't do -- Shift-Z mode is great when I remember to do it, but most of the stuff I find with WMECH and Validator are incidental to editing things nearby to the issues they highlight for me. Normal editing has Shift-Z off.

[qwaletee]

Because dumb editors?

[qwaletee]

Toolbox already does this, but I find its UI to be too heavy. I would love thin, pastel lines, that don't obscure anything.

I would also love a quick on/off for the whole set or subsets.

[qwaletee]

My bad... I read the levels request as a rank request.

I do think highlighting by specific (grade) level, and road rank (level), editor rank are all good ideas.

I would also like an option to highlight combinations (AND instead of OR). Imagine -- I could highlight anything a particular user has done in the last day. I sometimes get problem editors in the areas I manage, and it is useful to see if they are back at it again, while excluding their older edits.

[qwaletee]

With of course the downside that if you nudge HN for a structure whose entrance is on its "side street" instead of frontage (address) road, you may get worse destination results after the nudge.

[qwaletee]

I'm currently not able to use Filter by Editor. In the drop down, it only shows my user name, not any of the editors whose names appear in the segments being shown.

[qwaletee]

It continued to behave that way even at closer zooms. I should have mentioned that. Turned off everything but TB.