I used the TIGER Reader extension for ArcView and found the same thing. It
reads the 2000 UA, but labels the field UA90, and it truncates the last
digit (gives only 4, should be 5) of the UA code.
I loaded in the 1990 Urban Area .shp file as well,
(downloaded from census website http://www.census.gov/geo/www/cob/ua1990.html
to be certain. The area I was looking at is a UA in 2000, but
wasn't in 1990. So this confirmed that the TIGER Reader extension is
reading in the UA 2000 boundaries, it just labels them UA90.
Thanks to everyone who has posted on this subject so far. It made my job
Leigh Oesterling, Transportation Planner
Modeling & Forecasting Section
Office of Technical Services
Ohio Department of Transportation
(614) 752-5747 FAX (614) 752-8646
Brian Lakeman <Blakeman(a)gtcmpo.org>
Sent by: owner-ctpp-news(a)chrispy.net
05/08/02 03:41 PM
To: "'Banette Kritzky'"
Subject: RE: [CTPP] UA conversion
I too have found this. I had someone with Arc/Info graciously convert a
counties worth of 2000UA data for me. When I ran TIGER Reader in ArcView
chose "Urbanized Areas 1990" as the field to extract, the results matched
exactly with the Arc/Info converted files. Has anyone else noticed this?
appears that TIGER Reader may be doing the conversion correctly, even
the field is named incorrectly.
Genesee Transportation Council
From: Banette Kritzky [mailto:email@example.com]
Sent: Wednesday, May 08, 2002 2:50 PM
To: kwillet(a)ardc.org; ctpp-news(a)chrispy.net;
Subject: Re: [CTPP] UA conversion
I also used the Tiger Reader in ArcView 3.2a in an attempt to extract
the UAs. I am, however, puzzled by the following: a) if this Reader only
extracts 1990 data, why was one of the layers titled ALR/LUCA 2000; and b)
after reprojecting the extracted UA90 layer and overlaying my block2000
census data, why do the boundaries match up almost exactly (except for a
couple of donut holes) ? Could it be possible the Reader actually
the 2000 data, but is using the old field naming convention?
This list serve has been a great relief knowing there are others out
there trying to work through the same problems.
Mn/DOT Office of Investment Management
MS 440, 3rd Floor, Mn/DOT Central Office
395 John Ireland Blvd
St. Paul, MN 55155
>> "Tom Reinauer"
<treinauer(a)edd.uct.usm.maine.edu> 5/8/2002 12:08:26 PM
I tried using Tiger Reader in ArcView 3.2a and have had no luck. The UA
data record also appears to be 1990, not 2000.
We have cross-border issues and split urbanized areas and would really
to see the new boundaries before the Fall.
Someone out there must know of a fairly simple process(or develop a simple
process) to convert the boundary data into an ArcView shape file,
considering the proliferation of ESRI products.
Tom Reinauer, Transportation Director
Southern Maine RPC
21 Bradeen St. Suite 304
Springvale, ME 04083
----- Original Message -----
From: "Kendis Willet" <kwillet(a)ardc.org>
Sent: Wednesday, May 08, 2002 11:52 AM
Subject: [CTPP] UA conversion
So, if you are using Arcview 3.2 and ArcInfo 8.1 and
are not able to buy
third party software, a person can't process these
UA boundaries off the
Metropolitan Interstate Committee