I am having trouble extracting zipcode boundaries from the tiger census
line files. I extract the files matching the cfcc code F50 which is supposed
to correspond to the zip code boundaries but I get a total of 0 lines read
out. I don't think its a scripting/software problem because it works for
other cfcc codes (F10, F73, etc.).
My script (I am using GRASS) only looks at the files tgrXXXXX.f41 and tgrXXXXX.f42,
could this be the problem?
I would appreciate any help.
Thanks,
Oliver Weatherbee
oliver@earthview.cms.udel.edu
My understanding from talking with Census is that ZIP code info not a part
of TIGER. Some features (<1%) may have ZIP info. My efforts to build ZIP
polygons produced a few disconnected line segments. Census would like to
include this info in TIGER2000 but are under severe budget limitations.
Also: In detail ZIP boundaries are continually changing to meet mail
delivery needs.
If ZIPs are located between street blocks (along allyways) as are many
voter districts, the location would have to be moved to an existing TIGER
feature (not correct) or new featrues would have to be added to TIGER.
This could nearly double the size of highly urban county files - would it
be possible to handle Los Angeles County at over 300Mbytes? And TIGER
itself would increase at $250/CD-rom.
I too wish the ZIP data was in TIGER, but doing so might create a nightmare.
mgfleury@netcom.com (Mark Fleury) writes:
| My understanding from talking with Census is that ZIP code info not a part
| of TIGER. Some features (<1%) may have ZIP info. My efforts to build ZIP
| polygons produced a few disconnected line segments. Census would like to
| include this info in TIGER2000 but are under severe budget limitations.
| Also: In detail ZIP boundaries are continually changing to meet mail
| delivery needs.
| If ZIPs are located between street blocks (along allyways) as are many
| voter districts, the location would have to be moved to an existing TIGER
| feature (not correct) or new featrues would have to be added to TIGER.
| This could nearly double the size of highly urban county files - would it
| be possible to handle Los Angeles County at over 300Mbytes? And TIGER
| itself would increase at $250/CD-rom.
| I too wish the ZIP data was in TIGER, but doing so might create a nightmare.
GDT's DynaMap data products have most all of the zip code information
you'd want, since their database is maintained by cross-referencing
Tiger data with USPS data. They have also taken care to make sure
that the boundaries of various objects such as ZIP codes, cities,
tracts, etc. line up the way you'd expect. DynaMap costs more than
TIGER, but then you get what you pay for...
--
Tom Chatt \ Don't take offense, take action.
Internet: tom@flood.com \ Speak up. When we remain silent,
UUCP: ...!uunet!flood!tom / \ we oppress ourselves.