When tagging boundaries, I think you'll find it worthwhile to look at the US Census Bureau's 2012 Census of Governments[0], which lists all incorporated governmental units by state. It's is a comprehensive listing by state, of all governmental units. It's indispensable for understanding the relationship between various units of government and how they are established, and should be a big help in assigning the correct admin_level for a particular set of boundaries.
HTH, SEJ [0] http://www2.census.gov/govs/cog/2012isd.pdf -- SEJ -- twitter: @geomantic -- skype: sejohnson8 There are two types of people in the world. Those that can extrapolate from incomplete data. On Tue, Oct 15, 2013 at 8:16 PM, Richard Welty <rwe...@averillpark.net>wrote: > On 10/15/13 8:01 PM, Chris Lawrence wrote: > > > <http://en.wikipedia.org/wiki/Las_Vegas> > > Defining an alt_name or loc_name of "Las Vegas" on each of the > surrounding CDP boundaries/relations may help Nominatim geocode these cases > better. But the CDPs are not part of the city (aside from any areas that > may have been annexed, which should be reflected in the new TIGER 2013 > boundaries) and should not be conflated with the city boundary. > > right. whatever gets done with boundaries should be done on something > that at least tries to reflect facts, and not based on notions. that's why > i suggested going to TIGER 2013 as, while it may not perfectly reflect > the exact legal boundaries, it should be pretty close, as the Census > Bureau does actually care about getting the headcounts right. > > richard > > > > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > >
_______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
