The 2010 Summary File 2 (SF2) profile was developed by the State Data Center (SDC) Network. This profile allows users to run a profile on any race/ethnic group listed in the SF2, as long as there are 100 or more people of that specific group in a particular geographic area. We would like to thank John Blodgett of the University of Missouri for his excellent work converting the SF2 data files to SAS datasets. This has made the job of generating the 2010 SF2 profile much easier and more efficient. We would also like to thank Xan Wedel of the University of Kansas who graciously helped with the SAS coding and proofreading the profile.
Download the SAS programs that can be used to generate the 11-page SF2 profile. A copy of the SF2 profile for Nevada is also provided in the zipped file as an example.
The programs are designed to run in two-phases:
Step 1: Conversion phase: convert SF2 data files to SAS data sets. You can download the 2010 SF2 data files from the census FTP site at ftp://ftp2.census.gov/census_2010/ and run the conversion program (cnvtsf2.sas) to get the data converted to SAS data sets. The cnvtsf2.sas program is attached and can also be accessed at http://mcdc2.missouri.edu/cgi-bin/uexplore?/pub/data/sf22010/Tools.
Step 2: Profile generation phase: Generate the profile using the SAS data files output from Step 1 as input.
- SF2_main_2010_pdf.sas. This is the main SAS program used to run the profile. It is set up so the user can select to run only the section(s) of interest and comment out the other sections. This code controls all of the other modules – you will only change this file when you run the profile. The instructions on how to run the profile are included in the program.
- Genprof1.sas contains the SAS code to generate the General Profile.
- Genprof2.sas contains the SAS code to generate the Age Profile.
- PageTOC.sas contains the SAS code to generate the Table of Contents.
- Formats.sas – This file is used by the main routine. Note that in the program Formats.sas, the specific geography (place and county) is for CA only so you will need to add the codes for your state.
The 2010 Summary File 1 (SF1) profile was developed by the State Data Center (SDC) Network. The 2010 profile generally uses the same formats as the 2000 SF1 profile.
The SAS programs that are used to generate the 58-page SF1 profile are available in the zipped file below. Last revised 8/15/2011.
Here are the minutes from a conference call with Decennial Management Division (DMD) on March 2, 2010. This conference call was used to discuss the letter from the Census Bureau Director, dated January 13, 2010, in response to the Steering Committee’s letter regarding the Enhanced Planning Database.
Using the “Track Participation Rate” option on the Take 10 map, you can grab a widget to display the daily rate for your specific geography, but it doesn’t actually give you all the code you need.
Here is the code it gives you, which is really just a URL link:
Here is the full code you need to add to your webpage in order to actually display this as part of a page, as seen on Indiana’s site:
A few things to note
- You’ll change the “src=” URL in the above code to the URL you get from the “Track Participation Rate” link on the Take 10 map . (Alternatively, the last piece of the URL “loc=” refers to state, county, township, or tract FIPS code so you could just change it and skip the Take10 map step).
- At the moment, there doesn’t seem to be a way to use this widget for places (not sure if that’s intentional or just a bug). If you’re on a place on the Take10 map and click “Track Participation Rate,” you just receive the link for the state rate. And manually adding in the FIPS code doesn’t seem to work either.
UPDATE: Clifford Holley pointed out that the FIPS option is now working for places (example). Update the “loc=” command to use the 2-digit state FIPS plus the 5-digit place FIPS. (For those who don’t know city/town FIPS off the top of your head, the Missouri Data Center has compiled them for easy reference: http://mcdc2.missouri.edu/pub/webrepts/commoncodes/)
- You can set the width bigger, but 200 pixels wide is as small as this will go without doing some nasty things with text wrapping.
- All the quote marks in the code should be straight quotes and not curly quotes (I can’t get WordPress to accurately render them). If this gives you an encoding error when you try to paste it into your site, simply replace the quote marks.