AndyPoms wrote: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...
You know, I slept on this, and I thought of another completely trivial thing Waze could implement inside the NA city creation routine that would solve 90% of these problems, forever."If the name of the city is less than three characters, and I'm being asked to create that city, throw an error and refuse to do it."
, here are all the cases in North America:B, a village in central Ohio, United States (Can't even find its location Googling for it)
D, a river in Oregon, United States (Landmark, doesn't matter, but once listed as 'shortest river in the world', which is pretty cool)
Y, a settlement in Alaska, United States (Exists on segments, done)
Ai, a ghost town in Ohio, United States (Doesn't matter)
Oz, a community in Kentucky, United States (https://www.waze.com/editor/?zoom=3&lat ... TTTTTTTTFT
- this one would need to be created on about three segments, and, done)
Ti, a settlement in Oklahoma, United States (https://www.waze.com/editor/?zoom=4&lat ... TTTTTTTTFT
- again, create a few segments, and I think we're done here)Yp, a desert in the western United States (Landmark, doesn't matter)
...and that's it. For that matter, there are only a couple hundred such places in the entire world, and THEY could probably be checked and created in a couple hours. Do a one time 'Delete any other CityIDs with two characters or less', and we're done here.