I've just read this topic. I spotted something similar to the problem you're referring to. I think it's got a lot to do with something I called "grey area bug" and there's an ongoing discussion at http://www.waze.com/forum/viewtopic.php?f=3&t=7336
Besides, the waze client seems to automatically insert names into new roads that haven't been edited yet. In Poland I usually get everything attributed as "Kurów" - bizzare! New roads before edit should be without any name. If this happens the client presumes that the whole country/region is just one big city!!! Definitely, tech help needed here.

RallyChris wrote:It helps if you provide a permalink when looking at map issues.

The design is that city boundaries are defined by the segments that have that city name assigned to them.

I've seen two ways that things go wrong with this

1) Someone accidentally assigns the wrong city name to a road segment we can get cities in the wrong area.
2) Square geometry areas that have no road segments that have a city name assigned to them.

For #1 unfortunately at our level there isn't tools (yet?) to help us ferret out this kinds of issues. At this point you would have to look in the area of the phantom city and find the segments missed labeled.

For #2 waze support has said that this is something they can fix in the backend.

Is Permalinking possible on the client? I have seen this only on the device as of now, will see if I get it in the Live Map too.

Also wanted to add that the wrong name shows up in grey letters, and my map scheme is Map Editors.

It helps if you provide a permalink when looking at map issues.

The design is that city boundaries are defined by the segments that have that city name assigned to them.

I've seen two ways that things go wrong with this

1) Someone accidentally assigns the wrong city name to a road segment we can get cities in the wrong area.
2) Square geometry areas that have no road segments that have a city name assigned to them.

For #1 unfortunately at our level there isn't tools (yet?) to help us ferret out this kinds of issues. At this point you would have to look in the area of the phantom city and find the segments missed labeled.

For #2 waze support has said that this is something they can fix in the backend.

If the city boundaries are squarish, and also seem to change size based on zoom level, then you are seeing issue #2, that I reported in another post and support said they could fix.