I know .... That's what I find it quite irksome that they don't address this. I have reported this issue since I started editing, probably over a year ago.
I have come up with a patch for Tim's script that will allow highlighting of states, and have been using it this evening quite successfully, so the good news is hat it's definitely doable. I have submitted it to Tim in the hopes that he might include it in the next release.
Heh! That's awesome. I was poking around the code a bit myself. That Tim doesn't have
a state field where he is explains a behavior we see in North America. (I hacked on the 'get city names' script a little)...
I find myself wishing that the city pulldowns also had the state (if it exists), and Waze's internal ID alongside. One, it makes 'the right city in this area' obvious when there are several with the same name, and two, because I wonder if they could be used somehow to find and identify segments that cause city smudges. (See http://www.waze.com/wiki/index.php/Fixing_%22smudged%22_cities
This would -especially- be true if you can set one city as persistent, and be allowed to zoom out and just say 'Is this blah blah city ID anywhere in this range?'
If you consider the permalink https://www.waze.com/editor/?zoom=3&lat ... TTTFTTTTFT
...and modify the highlights script to dump out City IDs to the console.log, you get something like this:
Federal Way 23608
Federal Way 23877
Lakeland South 23878
Federal Way 50088
Federal Way 51273
* Washington 100000040
* That last one is the correct state.
Of course, without the IDs, you see four 'Federal Way's, all shown as the same city. This said, I'm pretty sure three of the four have different incorrect states behind them: Alabama, and Oregon. All evidence of a city smudge, but not the ID number that might help trace it. (How to USE said ID I'm not sure yet. Anyone have any ideas?)