[Script] WME Color Highlights - 2.33 Sept 2020

[Kuhlkatz]

Except that unsplitting shouldn't result in the removal of any roads... when you follow the instructions here:
https://wiki.waze.com/wiki/Best_map_edi ... -Way_Roads

That section is to preserve the House numbering.
I'm referring to mostly main arterials in suburbs that usually has very little or no house numbers assigned to it (in my case). In this case I'd prefer to keep the original speed info for both A->B and B->A on the original segments instead of merging the 2 and polluting the A->B and B->A for the resulting segments after the unsplit & merge.

If you merge them the 'Wiki way' to retain the House Numbering, only the speed info for the longest of the 2 segments seems to be preserved, which looks like it screws up historic data for either the A->B or the B->A if one of the newly added segments was the longest.

[laacz]

Since latest WME update, script has an issue:

Code: Select all

Error getting features TypeError: Cannot read property 'attributes' of null
    at e.initCityList (userscript.html?id=c5ada5fd-22f1-4da7-b8c5-a65ab140a843:828)
    at initialize.triggerEvent (vendor-128e35596d1c3032ab2e.js:1)
    at e.mergeGetResponse (app-06965e3429a84617f923.js:1)
    at app-06965e3429a84617f923.js:1


Line in question:

Code: Select all

  var thisName = thisCity.attributes.name;

They obviously removed already deprecated W.model.topCityID attribute in favour of W.model.getTopCityId().

[Laakkus]

First, thank you for this awesome script!

I was wondering if it is possible to add the possibility to highlight segments which have house numbers added? Me thinks there is a need for such a feature.

[ldriveskier]

With the release of the "unpaved" attribute, it would be great to have an option to show streets with it.

Thanks,

Under the "Highlight a Road Type" selection, one of the choices is "Unpaved". I've been using it and it works fine.

[ldriveskier]

Thanks to JustinS83, you can temporarily patch your Tampermonkey script until it gets officially updated by changing line 164 to the following:

var hasRestrictions = (attributes.restrictions.length > 0);

If you are running the Chrome extension, you will need to wait for an update (or download the script version).

[LeighGr]

Thanks Tim

Figured out why mine wasn't updating. I was running a modified version, where I've enabled name checking for South Africa and added a few mangled spellings, from a source on my pc. As soon as I removed that one, I was able to install the latest version, and I've got the ave speed data back again. Now to go add the local checks back again.

On slightly different point, what is the asterix at the end of the line: "Average speed for segment*" for? Since info is only displayed when a single segment is selected, it's not a wildcard.

[LeighGr]

Thanks Carel. Another Doh! moment.

[Lenamax07]

As it looks like there is a problem with the WME Colour Highlights App since short time.
It doesn't highlight anymore anything.

Best Regards
LenaMax07

P.S. A great thank you for that fantastic tool!

[LennyNRPD]

Thank you Justin for the patch on that, and Timbones for updating! Back to working.

[lg1992]

I see that the script doesn't work anymore in the new beta version of WME on Chrome. All checkboxes are clean; marking them doesn't change anything and isn't saved. Am I the only one who met this problem?