skbun wrote:Would you suggest in that case just having all of the city polygons generated at tile update time (as I think it works on the World server)?
Personally, I think it would all be far more maintainable if city names didn't come from the segments, but were in a separate landmark layer that is only accessible to AMs & CMs.
[EDIT] The forum ate this post the first time I made it.
I see someone else has already suggested a city polygon layer [/EDIT]
Yeah, and I was in on that thread too. If Waze were willing, I would be totally
behind a CM-only editable 'state' and 'country' polygon layer. If it WORKED that way, renaming a city, or merging an annex into an existing one would be much much easier, city smudging would be a thing of the past, and much more effort would go toward segments and street (with alt street) naming, the heart of routing.
They could import the current 2010 Census base map polygons for cities in, and there DO exist 'Shapefiles representing states', that could go in its own layer.
Going that route would also put a leg up on say, Google maps, whose cities still show boundaries that ALSO look like they're from the 2000 Census import. Example. Google Maps's Auburn, WA? Still shows in Google in its pre-2008 annexation shape, where Lea Hill is a separate CDP.
City annexes, changes, whatever? The polygon layer gets changed by a CM, and it's up to date. In a week. And in the same way that roads get that feeling of 'keeping up fast'...then so do cities, right? Waze win.(Oh, also? Here's a vote for making 'waterways' current to 2010, incorporating all creeks, streams, seas, lakes, whatever...merging the current waterways on the landmarks level INTO said layer...and then this 'waterways' layer editable as well. I've named lots of waterways in my area and made most I've done accurate to about 20-100m, but ask me how long it takes to make those polygons from scratch...)