City polygon layer has updated (NA)

by **AlanOfTheBerg** » Mon Nov 26, 2012 10:41 pm

yippeekyaa wrote:Maybe they are recalculating the city layer nightly?

Perhaps, though we've not heard. Frankly, I'd be happy with as often as the regular map updates, as changing the city layer which then possibly doesn't match the segment layer would be confusing.

by **AlanOfTheBerg** » Wed Nov 28, 2012 6:29 am

Client city layer is different than the editor one, if I remember correctly...

by **AlanOfTheBerg** » Thu Nov 29, 2012 3:23 am

Mike-1323 wrote:. . . And which layer would I turn on to see the tile boundries?

Hmmm... Interesting layer idea... Shift+t for Tile Boundaries...

by **AlanOfTheBerg** » Thu Nov 29, 2012 3:57 am

ohiostmusicman wrote:
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?

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.

by **AndyPoms** » Sun Nov 18, 2012 8:46 pm

I'm seeing updates in CT... The addition of the City of "W" and the Town of "gr" due to mislabeled segments (now fixed)... :roll:

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.

by **AndyPoms** » Sun Nov 18, 2012 10:44 pm

jasonh300 wrote:Yeah, you can't get rid of those by removing all the segments. I have one here that's a CDP that nobody actually refers to, and I changed them all over a year ago. There's no more geometric outline, but the name still appears on the map. There's two city layers...one that we can have an effect on, and one that came from the basemap that's not dependent on segments with city names. There's more details about that in a very recent thread (yesterday) about the basemap import which has all the corresponding city names and even the smudges that have given us all grief.

We've been able to get rid of some of these, but not all of them... We still have a large list to work on (made much easier by the Highlighter Tools) and once we're done with that list, I'll pass the info onto support in one big request...

by **AndyPoms** » Mon Nov 19, 2012 11:14 pm

gerben wrote:I am so glad I live in a small country... A year ago, we added all official cities to the map (600 or so) by naming a few segments. This took a few weeks between several CM's and AM's. After that, all wrong cities were deleted directly in the database by Waze, and the database has been locked to prevent the addition of new citynames. Since then, smudges and false names could only be added through Cartouche, which most editors did not know about.

Now that Cartouche is retired, there will be a final cleanup of the database, and we will never have a smudge again .

Hmmm...

That would be nice to do in a small state such as Connecticut...

by **AndyPoms** » Tue Nov 20, 2012 7:50 am

skbun wrote:Yeah...unfortunately, it appears that allowNewCities is a property on a country, and doesn't exist on a state. They'd probably have to mess with the database internals to allow that to happen on a state level, below 'United States'. Not that I'd object if they did!

I was leaning more towards the automatic removal of a specific set of data (i.e. I can provide the official list of Cities & Towns, and Waze can removed everything not on that list from City & Alt Name fields)... The locking would be nice, but once we have the map correct, we can then easily see when new (incorrect) cities are added & just manually handle them...

skbun wrote:The U.S. is the fifth largest country in the world by area, even without Alaska. Add Alaska in, and we're up to #4. Then you compare that to the Netherlands, which is the size of only Virginia, in area.

Connecticut is even smaller...

by **fvwazing** » Sat Dec 01, 2012 12:40 pm

@skbun: different zoomlevels of the livemap are generated at different times with different data, which is kind of fun if you think of it. The routes that are planned in the livemap use the same/newest dataset as the client does.

To force an update for a citysmear it may be an idea to draw a railroad where the smear shows. After the next mapupdate the railroad can be removed et voila - smear disappear.

by **gerben** » Mon Nov 19, 2012 11:09 pm

I am so glad I live in a small country... A year ago, we added all official cities to the map (600 or so) by naming a few segments. This took a few weeks between several CM's and AM's. After that, all wrong cities were deleted directly in the database by Waze, and the database has been locked to prevent the addition of new citynames. Since then, smudges and false names could only be added through Cartouche, which most editors did not know about.

Now that Cartouche is retired, there will be a final cleanup of the database, and we will never have a smudge again

.