yippeekyaa wrote:skbun, what you are saying make sense. In one area I had a "k" city layer. Using WME highlighter tool, i found the offending K named streets and corrected them last week. The K is still showing as being in the area but when I turn on the city option on WME it's not showing as a colored polygon anywhere on the map. But alas, the K is still there.
yippeekyaa wrote:I have a layer incorrectly named "flat rock(2)". I've changed every street to the correct city name yet the flat rock(2) layer still remains.
yippeekyaa wrote:I've spent a couple hours scanning for any remaining incorrect city names and none appears to exist. Does the city layer use alternate addresses to determine this layer? someone mentioned that the highlighter can highlight the alternate addresses, yet I can't seem to figure out how exactly that is done. Advice?
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): BOTH
Waze Livemap: Only the placement of city names
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.
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...
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.
Mike-1323 wrote:. . . And which layer would I turn on to see the tile boundries?
Mike-1323 wrote: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?
Users browsing this forum: Google [Bot], penttiSeg