|
|
| GeoCommunity Mailing List |
| |
| Mailing List Archives |
| Subject: | Re: [gislist] Census Boundary Files Origin |
| Date: |
10/25/2003 11:25:01 AM |
| From: |
Robert Heitzman |
|
|
Note that theCensus Designiated Places boundaries do not follow
administrative boundaries except where the Census Blocks were defined to
follow admin boundaries. Whiile it is policy that blocks follow admin
boundaries it is not a legal requirement. Census needs would trump accurate
administrative area definition. Ditto for the other area layers provided via
TIGER and COB.
My guess is that the procedure use to define Census Designiated Places was
to accept input from local representatives (County level most likely) as to
which Census Blocks should be associated with a "place".
The LSAD_TRANS attribute value 'city' will most closely represent admin
boundaries. 'CDP' records represent unincorporated "places" and they do not
represent an administrative division of land.
Another guess is that the Populated Places layer was developed more for map
annotation and as a general navigation referenece, not as a layer to
describe admin boundaries.
>1990 Census Boundary file (or 2000, it doesn't matter) of say a populated
>place. Does that reflect the boundary present in 1990, or was it actually
>created in/represents 1989 (etc) but was released in 1990
>
>
_________________________________________________________________
Never get a busy signal because you are always connected with high-speed
Internet access. Click here to comparison-shop providers.
https://broadband.msn.com
_______________________________________________
gislist mailing list
gislist@lists.geocomm.com
http://lists.geocomm.com/mailman/listinfo/gislist
_________________________________
This list is brought to you by
The GeoCommunity
http://www.geocomm.com/
Get Access to the latest GIS & Geospatial Industry RFPs and bids
http://www.geobids.com
|
|
Sponsored by:
For information
regarding
advertising rates
Click Here!
|
