Big thanks to FZ69617 - he make new version.
Now you can see both speeds on segments who have different speed.
Add Polish language translation.
Fix some bugs and stability issues.
Thank you!
Maybe it is possible to show different speeds on same segment not with dashed line, but with two lines on different sides of segment? To know which direction which speeds is?
Sure, everything is possible having enough amount of time. 
Drawing a separate speed limit indicators at each side of the segment was also my initial idea. 
But, aside even non-trivial task related to implement it, the result would probably cause a slow down in rendering of the map. I also afraid, that it would not finally help too much, since you can easily check what a speed limit for each direction is with a single click selecting the segment.
The primary intent behind a dashed/dotted lines is in a quick visual indication that something is potentially wrong with a speed limits specified, and likely requires the editor’s intervention.
Here are an examples of the line styles indicating various speed limit combinations you can see on the map, together with a short description:
– Edit –
Replaced picture attachement somehow externally changed.
I’m having some issues with the newest version of the script. In the Netherlands, Private Roads cannot be set to a certain speed limit, however when using the script to highlight segments without speed limits set, the private roads get tagged too.
When using the script in this mode, the option to use a transparent overlay doesn’t work either. These two issues combined make it pretty much impossible to work with this script, as private roads are used fairly frequently, and we’re at 80-90% for speed limits for all normal segments. Could these issues be addressed?
Thanks,
Martijn
In no country a Private Road segment’s SL can be set directly, but it is possible when temporarily using other segment type.
If the real roads (for which you are using Private segments) do have speed limits, and I assume they do, I’d recommend setting them (with the mentioned workaround) and help us convincing the devs and Support to remove this weird limitation from “Other-drivables” segments.
Sure they do. A Private Road segment has its SL attribute like any other segment type.
The script would possibly require a bit more checkboxes and a different highlighting logic.
Sent from a touch display, which took care of perfectly scrambling my thoughts.
@MartijnKeizer, I just submitted a new version of the script to the @martinkolar’s source code repository. A new version adds transparency option support to all the highlights the script provides. I believe this will solve your issue.
Is there any way I can modify something so that I can see the speeds of small streets when I’m zoomed out a bit further than it works for now? I like to scan for whole subdivisions that have no speeds and that would be easier if I could zoom out 1 or 2 more steps from where they stop showing up currently.
Or possibly not because the editor doesn’t send that date for those segments when you’re zoomed out. 
I’ll try zooming the whole browser and see what that does.
Thanks.
I believe Martijn’s point is that tagging missing speed limits is very helpful in finding segments that should be updated.
However, since private roads should not have speed limits, it isn’t helpful to tag them.
Rather than tagging “no speed limit”, it should be “no speed limit on a segment that should have a speed limit”.
I understand you, I just strongly disagree with both parts of your sentence:
This was just a very bad idea on Waze side to block the possibility to directly set these segment types’ SL.
Sent from a touch display, which took care of perfectly scrambling my thoughts.
I see black and white dashed line on segments without speedlimits, please add option to disable it… it block view of segment types…
This script causes the popup to give the message: “TypeError: Cannot read property ‘checked’ of null”. It always occurs when I change from Event Mode to Default Mode. It will continue to give the same error when I change back to Event Mode. Here is the following console log:
[code]www.waze.com/:169 Uncaught TypeError: Cannot read property ‘checked’ of null
at initialize.highlightSpeedsSegments (eval at <anonymous> (:2:297), <anonymous>:169:58)
at initialize.triggerEvent (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:101:6363)
at initialize.moveTo (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:105:30966)
at initialize.setCenter (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:105:27363)
at initialize.updateSize (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:105:25413)
at https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:99:14924
Uncaught TypeError: Cannot read property ‘checked’ of null
at n.highlightSpeedsSegments (eval at <anonymous> (:2:297), <anonymous>:169:58)
at f (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:2:23736)
at M (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:2:23528)
at h (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:2:21471)
at n.l.trigger (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:2:23421)
at s.a.events.on.loadend (https://www.waze.com/assets-editor/js/app-331809ae6037103cf5c5.js:4:18025)
at initialize.triggerEvent (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:101:6363)
at s.e.onLoadEnd (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:104:25392)
at initialize.triggerEvent (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:101:6363)
at initialize.onImageLoad (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:107:10712)
highlightSpeedsSegments @ VM10072:169
f @ vendor-30792e8….js:2
M @ vendor-30792e8….js:2
h @ vendor-30792e8….js:2
l.trigger @ vendor-30792e8….js:2
a.events.on.loadend @ app-331809a….js:4
triggerEvent @ vendor-30792e8….js:101
e.onLoadEnd @ vendor-30792e8….js:104
triggerEvent @ vendor-30792e8….js:101
onImageLoad @ vendor-30792e8….js:107
initImage @ vendor-30792e8….js:107
renderTile @ vendor-30792e8….js:107
draw @ vendor-30792e8….js:107
drawTileFromQueue @ vendor-30792e8….js:104
(anonymous) @ vendor-30792e8….js:99
i.(anonymous function) @ vendor-30792e8….js:99
2017-02-14 19:50:46.354 VM10072:169 Uncaught TypeError: Cannot read property ‘checked’ of null
at highlightSpeedsSegments (eval at <anonymous> (:2:297), <anonymous>:169:58)
at initialize.changeLayer (eval at <anonymous> (:2:297), <anonymous>:471:5)
at initialize.triggerEvent (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:101:6363)
at Object.<anonymous> (https://www.waze.com/assets-editor/js/app-331809ae6037103cf5c5.js:15:24236)
at d (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:26:22569)
at Object.fireWith [as resolveWith] (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:26:23337)
at s (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:27:26413)
at XMLHttpRequest.<anonymous> (https://www.waze.com/assets-editor/js/vendor-30792e8abebc80c177fa.js:28:232)
highlightSpeedsSegments @ VM10072:169
changeLayer @ VM10072:471
triggerEvent @ vendor-30792e8….js:101
(anonymous) @ app-331809a….js:15
d @ vendor-30792e8….js:26
fireWith @ vendor-30792e8….js:26
s @ vendor-30792e8….js:27
(anonymous) @ vendor-30792e8….js:28[/code]
Hi. With the latest update in WME, I can’t turn the script layer on to use it.
Thank you
Hi, new version for updated WME is out!
Doesn’t seem to be working for me. Have Tampermonkey installed, script installed, tab is visible in left, but roads aren’t coloured. Ideas?
I’m getting problems whenever I try to change from Default Mode to Event Mode:
- Popup message: http://www.waze.com says TypeError: Cannot read property ‘checked’ of null
- Top panel of WME is blanked out (except for the Waze logo), so I can’t change back to Default Mode, change layers, etc.
- Feed in left panel is now blank
The only way to restore back to normal is by refreshing the entire page.
Tested in latest Chrome 67.0.3396.87 (Official Build) (64-bit), with WME Speedlimits 0.4.3.6 installed via Tampermonkey 4.6, all other Tampermonkey scripts disabled and all other WME-related extensions disabled.
Also, now that the script has changed name to WME Speedlimits, it’d be good to update the thread title too.
Thanks!
Hey there! I’m happy to see most of the references to the Waze object in this script have been replaced with the W object. There is still one line that need changing to have this script fully ready though:
525: if (typeof(Waze) === 'undefined') {Otherwise the script will never initialize.
Also, please be aware that today’s update will affect the several repository APIs, which will also affect this script:
185: var segment = W.model.segments.get(seg); // <- should become .getObjectByIdDone.
The add-on fails to start in the latest WME on Chrome. I’ve found the following error in the console:
Uncaught TypeError: W.map.getMapEventsListener is not a function
at initialiseSpeedsHighlights (userscript.html?id=a46cf566-6add-4522-9d51-12b568821d7c:626)
The latest version seems to have bug. I found that if you downgrade to version 0.4.4 it works.
I’ve found it’s enough to replace the code W.map.getMapEventsListener().register… to W.map.events.register… to make the script work again.