The formatting for the records in the UA TIGER files are a little
different than the previous release so you won't get the correct results
using the TIGER tools in Arc 8.
If you do convert the UA TIGER files with ArcTools you will notice that
the first 4 of the 5 digits for the 2000 UA Code end up in field UA90
and last digit in UR90.
You can see why this happens if you compare the formatting of the
ArcInfo result for Record Type A to the Census Documentation for Record
Type A (Chapter 6, p.12).
In other words UA90+UR90=UA.
So, you can get a look at the Urban Areas if you relate Record Type A
to the Census Geography using CENPOLID and concatenate fields UA90 and
But I personally am going to hold off doing much more work with the UA
TIGER files until ESRI updates the conversion tools.
I'm sure there are other formatting changes that I'm not aware of.
GIS Trivia Question:
The GIS software maker Idrisi was named after:
Cartographer born 1099 A.D. in Morocco
Their CEO's son
A city in Egypt
Madison Area Metropolitan Planning Organization,
City of Madison Planning Unit
121 S. Pinckney Street, Suite 400
Madison, WI 53703
>> Kendis Willet <kwillet(a)ardc.org>
05/08/02 10:52AM >>>
So, if you are using Arcview 3.2 and ArcInfo 8.1 and
are not able to
third party software, a person can't process these UA boundaries off
Metropolitan Interstate Committee