Objective: The objective of this lab is to keep you going with ArcMap. You will: import text files with point coordinates as maps; convert them to shapefiles; join tabular data in text files to shapefiles using both spatial and attribute joining; and use selection, sorting, summarizing, and descriptive statistics to answer some more questions. You will also learn a bit about the US Census Bureau's Census2010 data and web-access mechanisms.
Idea: It is really handy to be able to map and analyze data from a text files containing coordinate points and attributes. That is what this part is about.
(Here's a hint for an up-coming "Write"... Notice that these are just comma separated text files (ASCII BCD) that you can 'type' and edit with editors like 'vi', 'notepad' or 'edit', with just a few formatting conventions. Notice especially the quoted strings as column headings, the ".txt" extension. To see how close two points can be in ArcMap try typing a file of points that get very, very, very close to each other and then seeing what "ArghGIS" does with them.)
Pre-set-up: First, examine the three text files with a text editor or the DOS/CMD "more" or "type" commands, to see what's in them and how they are layed-out.
Set-up: Start with an empty ArcMap project. Maybe - set the data frame properties to use world geographic coordinates (WGS84). Add the three text files to the project (with the add data button).
Display each as a table (rt clk, view table).
Display each as a map:
Convert each to a shapefile in your (U:/) directory:
and add the shapefiles into your project and remove the text files.
Part One Questions:
Census geography. The US census is collected and reported on a hierarchical spatial partitioning scheme. From top to bottom the hierarchy is:
Nation > Regions > Divisions > States > Counties > Tracts > Block Groups > Blocks
Census Summary Files. (Old School) SF1, SF2, SF3, and SF4 refer to particular releases of Census data, that differ in the topics and levels of detail included, and in the time required to release them. To understand them you should read their documentation, an example of which, for the 2010 SF1 data, can be found here: www.census.gov/prod/cen2010/doc/sf1.pdf.
The up-shot of that document is that the census data are distributed across a set of files (segments). The segments each contain a couple of hundred columns of data comprising several census tables, each of which might contain several variables, and report the variables at several levels of aggregation (blocks up to state). One of the segments contains geographic reference information. The data for each geographic unit can be linked across segments by Logical Record Numbers. This is the "old school" approach.
Idea: Joining tables to shapefiles lets one access tabular data when needed without having to have it stored "in" the shapefile. I.e., one shapefile can be used with many different tables without having to become a huge single shapefile nor multiple shapefiles. Joining depends on two tables each having columns that contain matching "keys", so that records whose keys match can be joined together. The columns can have different names. It is the data in the columns that are used to make the join.
In this case, you'll join the two datasets below by the logical record numbers, an attribute join.
hi00042010sf1.txt is "Segment 4" of the 2010 SF1 data, containing Census tables P10, P11, P12, P13 and P14 for Hawaii. There are 33,600 rows (33,599 plus one adding column names) and 244 columns of data. These census tables cover some race and age characteristic variables documented around page 6-30 in the pdf documentation noted above.
higeo2010sf1-extract.txt are several columns of the geographic reference segment of the 2010 SF1 release, converted to csv with column labels added. NB: in Spring 2013 one quotation mark is missing in the first line of the file... add it back in!
Before set-up: Skim through the sf1.pdf description of the census data, especially Chapter 5 and Chapter 7. In Chapter 7, the Table (Matrix) Section is especially useful for locating particular data. It points to the segment file and gives the reference variable name for the particular data. Page 6-30 gets to the data tables for this exercise.
Set-up: Start with a blank ArcMap project, set the frame coordinate system, add the higeo2010sf1-extract.text file to the project. Select the SUMLEV that you want (probably 140 tract level, but for other uses 150=block-group and 101=block might be good, see page 4-1 of the documentation to see all the options) and convert those points to a shapefile (rt ckl name, Data, Export, selected features). Add that shapefile to the project and remove the cruft.
(Attribute) Join the hi00042010sf1.txt file to it.
The steps in a tabular join are:
The example above should add the attribute data to the points. (NB, if you had a shapefile of polygons it would work the same way.)
Part Two Questions:
Objectives: Get shapefile data from the Census Bureau. Load the shapefile. "Attribute join" to link the csv file.
This is a fairly easy way to get a shapefile of census geometry, but seems to limit you to only one attribute. And the default file naming ("thematicdata.csv"?) that they use complicate keeping data straight.
Background. The Census is changing everything. No more decennial dumps... continuous ACS... Data winnowing access...
Using American Factfinder 2 In the Blue Tabs to the left: 1. select geographies Census tracts Hawaii state Honolulu county All tracts (can you do all tracts for the state?) 2. select topics e.g. DP02 (social), DP03 (economic), or DP04 (housing) 3. View Tab 4. Create a Map Tab select a variable to map (click on the data in the table) show map download the shapefile in zip format 5. extract the files into your directory 6. check what is in the CSV file. 7. open the shapefile and link the data in the CSV file to it. 8. symbolize the data.
Part Three Questions
The census is experimenting with distributing the geometry side of their data as "kml" files. They seem to be doing it oddly --- devoid of links (like logical record numbers) to the attribute side of the data. We can use "spatial join" to join them based on location.
Objectives: Get KML (Keyhole Markup Language) data from the Census Bureau. Load KML data into ArcGIS. Use Spatial join to relate data to census geography units.
See www.census.gov/geo/maps-data/data/tiger-kml.html and www2.census.gov/geo/tiger/KML/2010_Proto/Readme.txt for an overview and download the detailed Hawaii census tracts from: www2.census.gov/geo/tiger/KML/2010_Proto/2010tract_dt/. - these are detailed 2010 Census tracts in kml for each state - Hawaii is state "15"
Import the kml file into Arc... Turn on the "Data Interoperability" extension license... ToolBox -> Conversion Tools -> From KML -> KML to Layer (it will want to make a geodatabase, let it) Notice that Census has provided neither LOGRECNO nor FIPS codes to link data to this geometry. Spatial join the Tract centroid points to these tract polygons. (You may want to select them first... SUMLEV=???) Symbolize a data variable from the P10, P11, P12, P13, or P14 tables of your choice.
Part Four Questions