herrchin wrote:I have two bugfixes, and I also made some customizations that USA editors may like, as it is geared towards common USA speeds, and also tweaks the label visibility a bit.

Will this work for us in the UK as well?
We use imperial units too, and would benefit from a larger separation of colours for limits that are only 10 mph different. However, common speed limits here are all multiples of 10, i.e. 20, 30, 40, 50, etc.

jchiarav wrote:Hi. Where is the configuration option? Thanks.

At the bottom where it says "Street Vector Layer".

Sent from my Wileyfox Swift using Tapatalk

wlodek76/FZ69617 Rout Speeds get transit speeds from data returned by livemap router, show this data for all displayed roads would be very very slow.

Works great on ubuntu 14.04. Chrome and Firefox.

So long as Waze continue to keep their heads stuck in the sand apparently not listening to any of the (mostly valid) criticisms of the new road layer, then this script could become very important to quite a few editors, myself included, and it's something I would have almost certainly ended up trying to write myself if no-one else had done so. So I'd say it's very definitely worth continuing with, and if there's anything I can help out with please don't hesitate to get in touch. PM has already been sent

This looks like a startup sequencing problem between SVL and the native Waze code. On my PC at home SVL initialises cleanly, whereas on my slower PC at work it fails exactly as described above. A quick poke around in the code shows that it's failing in wbwGlobals() at the point where it tries to read the Waze.map.zoom attribute, because at the point at which this line of code is executed on this particular PC, the parent Waze.map object hasn't yet been created...

If you have a look in the uroRealWazeBits() function in URO+ you'll see the method I've used to ensure all the necessary Waze bits are present before attempting to access them - I'd suggest modifying your corresponding wbwWazeBits() function to provide similar object-existence testing before allowing SVL to continue initialising, and also call wbwWazeBits() *before* wbwGlobals() so that you then know Waze.map.zoom must exist.

Batman!

It does, but you can't do anything with them - they're rendered only in the static bitmap tiles used for the native road layers, the corresponding segment data that WME (and SVL) requires to let you actually edit the segments isn't however loaded until you zoom in a bit.

bedo2991 wrote:(I need a permalink of a 2-way street with 2 different speed limit set, please).

PM sent...

I keep getting this error message: "Street Vector Layer failed to initialize. Please check that you have the latest version installed and then report the error on the Waze forum. Thank you!"

I have the latest version installed. Anyone else having this issue?