ohiostmusicman wrote:If this is the case, then why is M, Ohio still appearing in the client?

Even though "M" is not showing at this zoom level, that giant kite shape laying waste to the great state of Ohio is the aforementioned "M, Ohio". GizmoGuy and I took care of this by Nov. 19, it no longer appears in the colored WME City layer, and here it is still in the client. And yes, I refreshed the tiles...

Hm. I can't see the M blotch easily on my client, zooming in and out some. What if you completely wipe your cache and data, maybe...?

This isn't completely related to city tiles in WME, but it's something else I noticed while troubleshooting a UR - and, anyway, at least related to the general topic of tile generation.

Is it my imagination, or is the Livemap's functions kind of 'half there', in that if you know two exact points to use on the map, you can use the Livemap to test routes with it - but that the visual appearance of the livemap tiles themselves is weeks out of date? (I worked this out by trial and error by like...moving to points beyond where segment structures had changed and I knew a predictable route should begin, and got this to work.)

I can't tell precisely how far back, but I'm fairly certain it's not showing changes from 'after at least October 13'.

AlanOfTheBerg wrote:All the segments responsible for the smudge must be fixed, of course. Then, any tile the smudge went through would need at least one segment trivially updated, like a geometry node delete or add. Nothing fancy.

gerben wrote:For the client, the city layer is only updated for tiles that had at least one edit during the last update cycle, so to get rid of it, every tile covered by the smudge needs an edit.

. . . And which layer would I turn on to see the tile boundries?

Does this mean we'd have to basically re-save a majority of roads as they are in order for the massive smudge to be gone on the next tile update?

All the segments responsible for the smudge must be fixed, of course. Then, any tile the smudge went through would need at least one segment trivially updated, like a geometry node delete or add. Nothing fancy.

skbun wrote:Okay. So there is a gray cities layer, and a layer that shows names of cities for the gray layer. If memory serves me, they're 'cities_01' and 'cities_names'. As best I can reverse engineer, these are only generated at map tile generation time. They're used in the following ways:Waze client (Android at least): BOTHWaze Livemap: Only the placement of city names

If this is the case, then why is M, Ohio still appearing in the client?

Even though "M" is not showing at this zoom level, that giant kite shape laying waste to the great state of Ohio is the aforementioned "M, Ohio". GizmoGuy and I took care of this by Nov. 19, it no longer appears in the colored WME City layer, and here it is still in the client. And yes, I refreshed the tiles...

There are seemingly random squares of "M, Ohio" that appear regularly along my commute between Bowling Green & Toledo. Even better, depending on the zoom level, some disappear while others appear. These segments all have no city attached to them (confirmed in WME).

skbun wrote:If the above is how this works, and Waze could tell us either way, right?, IMHO, it'd be to our advantage to have cities_p update as often as Waze will do it. Two big reasons:1. The closer to real time this layer is run, the more often we can check the cities layer to see if smears have been resolved or new bogus cities have appeared - particularly if they increase the number of colors and boldness of borders to make them easier to see; and they may be caught/removed before they're ever even seen on the clients. But, especially,2. I'm almost certain that 'The highlighted road is too far from the city it was added to' is dependant on the cities_p layer, not the one we see on the live map tiles. Put another way, if the city polygon layer for WME were run with each edit, we'd never have the 'M, Ohio covers half the state' problem ever again**. In any case, the more often it runs, the less we'll see it. I can happily add a fictitious 'T, California' on two segments, between saves, 150 miles away from one another, so this really leans toward 'It's about that multicolored polygon layer'. To me, it seems Waze doesn't know 'how far too far is' unless there's a polygon to check against.

Personally, I don't understand why the WME & client city layers couldn't be the same thing. Editable polygons that could be fixed by CMs as needed and then left. After all, how many city boundaries change on a weekly basis? Then, the need to type in a city for a segment is eliminated and, therefore, these phantom cities. I know I'm not a fan of city boundaries being determined by city names per segment.