Sorry, I had a bad version online. :oops:
I uploaded now the correct version. If you see in the menu “Alt-Names” insted of “Speed View”, you should have the correct version.
This version works for me correct with Firefox and Chrome. Let me hear, if there are still any problems. 
LG Alex 
Does this work for the US or is the US in the works?
I think, there would be some little changes necessary (because you have states, the country for which it is available, have not). If you have a list of correct cities (for a state or for US), I will try.
The other features (beside the city check) should work everywhere.
Kindly regards
Alex
Oh man alive. There are an estimated 19-30,000 incorporated cities in the U.S. Then there are Census Designated Places that don’t meet town/city criteria but are recognized. That’s on hell of a list.
Seems like a challenge I need to taken on.
Sent from my DROID4 using Tapatalk
i’ve uploaded italian cities updated to 3.3.14
:arrow: http://www.cortinovis.eu/waze/Italy.txt
I have adapted the highlighting of landmarks (places) for the new WME.
FYI: any segment shorter than 5m will almost certainly cause problems with routing.
Thank you!
I think 5 is between 0 and 99.
But I can set 4 (the largest value which is smaller than 5) as default value.
Gesendet von meinem GT-I9100 mit Tapatalk
Sure, I was more meaning that anything shorter than 5 should be really bright and flashy as it is a real problem.
ist this link
http://userscripts.org/scripts/show/175260
broken ?
Try this link :arrow: http://userscripts-mirror.org/scripts/show/175260
I don’t know whats the matter with userscripts.org.
Until it is fixed again, you can use this link 175260.user.js.
Cool! I will change my links, until the original userscripts.org works again. 
Hi,
Your script is bugged. Don’t know why exactly, but since I’m catching javascript errors in Toolbox, Toolbox reports errors due to Highlighter City when they’re used together.
You have to replace all Waze.model.landmarks by Waze.model.venues in your script because Waze.model.landmarks is not used anymore and returns an invalid object.
Thank you for your info. I use your Toolbox together with my Highlighter City with no problems. But I use the ß-version …18 of where the old landmarks are never used. A reason more to release this version and remove the landmark completely (they are only in it for historical and compatibility reasons). They places (venues are used since version 1.7.1.17).
And also thank you for your new Toolbox feature copy segment attribures, it is great!
New in version: 2.0.0.0 / 1.7.1.18
Level Highlighter (brown <0 / green >0 - different intensities by level)
Lock level changed (dashed red - lock by user / straight red - auto lock)
Better compatibilty to original highlighter
Removed old landmark highlighting (places are still available)
You told me to ask so… here I am!
We have some problems here in Brazil with City names spelled in two different ways.
e.g: “Santa Bárbara d’Oeste” and “Santa Barbara D’Oeste”
Some times the same street have two different cities. It sucks 
Your script can do something to help us so we can erradicate the misspeled version?
Tks in advance
The only thing I need is a list of your correct spelled city names. If you have it in any form send it to me.
New in version: 2.0.0.1* / 1.7.1.19
Outdated restrictions are now shown in dark violet
The area size of a selected landmark is now shown
The script should now be able to work at countries with states (I still have no city list from such a country)
All console.log messages should now begin with "HiLiCi: "