paulwelch23 wrote:This polygon covers the ENTIRE city of Nashville as well as many of of it major suburbs.
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.
AndyPoms wrote:I'm seeing updates in CT... The addition of the City of "W" and the Town of "gr" due to mislabeled segments (now fixed)... Still appearing on the map are the neighborhood of "Blue Hills" (all segments removed over 6 months ago), and "Canaan" (the neightborhood in the town of North Canaan") which was removed (relabeled "North Canaan") so we could label the actual Town of Canaan as "Canaan" as it was never labeled in the first place.
skbun wrote:The offending 'city' is 'M, Ohio'. If you scroll around the borders, especially with the help of the WME highlighting tool if you are an AM, you'll be able to identify and reassign those segments.
Waze? I can't help but notice that both of these occurred in cities beginning with M, Marblehead, and Maumee. It's pointing to a problem I've had myself, with the WME city completion. Cities are given in the dropdown using cities.get, and one is highlighted. A user will often assume that hitting tab or similar will autocomplete it, but it won't. Instead, you get...this. I don't really think this is the user's fault. The editor can be clumsy about this.
Can we make the 'Cities' blank into an explicit 'Select' choices dropdown, whose last option is 'New city', where THEN a user gets a blank where they can fill in their own field? Or, if not that, at least just pop up a warning saying 'You are trying to create a new city, 'M, Ohio'. Are you sure you want to do that?'
jasonh300 wrote:I don't see any reason why it shouldn't work that way. However, there has also been talk about wanting to get rid of the Country, State and City fields and just let the hidden layer handle all that, but allow the polygons to be editable by CMs. If we had such a thing, I'd be willing to be that the Champs could get the state and country polygons for the U.S. and Canada fixed within a week. (Same with the country polygons for ROTW.) In that case, the cities would have to be tackled on a case-by-case basis. This may just be a pipe-dream though. I don't know if it's feasible or not, but it's been suggested more than once.
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.
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?
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.
Users browsing this forum: No registered users