jasonh300 wrote:The city polygons have updated again. The couple of experimental things that I didn't want anymore in the area here are now gone, and then an inexperienced editor created a city right in the middle of New Orleans called "New" with a street created yesterday.
And D'Lberville is gone now...only about 10 hours after I removed it from the editor!
Update, yay! (Goes to check his own changes...)
This is just me thinking out loud here...so this may be a completely silly idea anyway.
I wonder how bad it would really be if we DID lock the U.S. down to allowNewCities:no, and ask Waze to remove the sticky/uneditable/basemap city layer after that's done, so all cities are generated by segment hits. We're in a unique position in the United States, because cities were pulled in BY the basemap import. (In most countries, this was not the case, I think?)
- The rampant creation of false cities would end
- With the sticky layer gone, we can in practice delete unwanted cities by deleting all their segments
How cities are added after that, maybe Waze could help, if and when the time came? Locked down to high level editors, or something.
On a different subject, granting it is completely impossible for us to get this information without scraping the United States ten square miles at a time, I wonder how hard it'd be for Waze to dump out a table that's like CityID---CityName---State---Country---Lat/Long of name put on map---*Number of assigned streets
* (Number of assigned streets is only practical if CityIDs are keyed in such a way that you can say 'Tell me streets associated with this CityID' in the database. Very helpful but not strictly necessary.)