Well, apparently this is their back-end solution: I started scrolling further away from major developed areas, and this is what I got. This is going to take FOREVER to clear, and since they are UR's, its going to be tough to find actual User Requests mixed in with all the auto-URs.

https://www.waze.com/editor/?zoom=0&lat ... FTTFTTTTFT

Another new "Waze Automatic" script creating User Reports, or at least a modification on the old one:

Waze Automatic: We suspect that this segment is associated with a different city than the one it is currently in. PLEASE don't leave it without street / city name

So far, all of the ones I have found
A) Did have the correct city
B) Were un-named
C) Were set to street type

And they should have been left unnamed, but probably should have been set to private road. 2 were roads inside a rock quarry, and the other was a road running through an apartment/condo complex.

Just an update, I went back to two of them and turned the city layer on. It looks like there's either a smudge, or just the way Waze handles city borders, doesn't like the curvy twisty borders that sometimes crop up where multiple cities merge together.

I'll need to poke around later, as well as try to figure out what the official border lines are.

If anyone has a resource for finding the exact city borders in California cities, I'd appreciate it. (Real borders, not mailing address/zip code borders, which often don't match the actual city limits)
Update: Here's a city zoning map from one of the cities, to give you an idea of how messy things are in this area.
https://www.cityofindustry.org/pdf/zoningmap.pdf

skbun wrote: Does this mean some or most of the PV smudge is supposed to be gone? I've got some up in Trinity county and near Mendocino, still. Maybe the script is still running?

I spent an hour today manually cleaning up PV segments in the SoCal desert today. So no, they haven't gone anywhere.

No, I'll have to give that a shot. Would have made things easier.

If you wait 30-60 seconds and click on "Permalink", you should find that the changes were made. It is as though the changes submitted by WME are queued up and taking longer than usual to commit. In the meantime, WME reloads the map as soon as it has finished transmitting the latest changes, and you see the map pre-change.

There seems to be a bug related to cameras and mph vs kph.

In the centre of this permalink are 2 cameras with a speed limit of 40mph/64kph.

At zoom level 4, these cameras correctly show as 40mph in the details pane when selected. If I then zoom in twice (either by double-clicking on the map or using my scroll wheel or by using the zoom slider) and re-select the camera, it now shows as 64kph - still the correct value, but the wrong units. Hitting the permalink will correct the problem.

As best I can tell, this only happen when zooming in twice from zoom level 4, but I have not tested all combinations!

Yeah, I get this too.

If the node is "stuck" to the mouse, or the cursor has changed to crosshairs, wave it over the segment where you accidentally picked it up and it will drop.

If it just follows each mouse click, click back where you picked it up. It will then turn into an edit which you can undo.

This evening I noticed road name font is broken. Diacritic symbols of Latvian language are way too big and not in place.
https://world.waze.com/editor/?zoom=3&l ... TTTFTTTTFT

Hi !

can you help ?
I always worked on Macs but they installed me a PC at work
Well, no way to launch editor on FF (up to date, no GreaseMonkey), I've got a blankpage, here's a screenshot
http://hpics.li/bcc0422

A bug with the editor or with my FF ?

Thanks