Census Acs Codebook

[Lucrecio Poinson]

Thefollowing links provide PDF versions of all available original census sample codebooks used as input for the IPUMS data series. These codebooks do not apply to the completed IPUMS data, but describe the source samples. They are particularly useful in conjunction with the translation tables in Volumes 4 and 5 to review the IPUMS data transformations.

To browse the J2J data files in their directory structure or to access them with a FTP program (must be able to access HTTP), go to: lehd.ces.census.gov/data/j2j/. J2J data can also be accessed via Job-to-Job Flows Explorer. This analysis and visualization tool allows for the construction of tables, maps, and charts to compare, aggregate and analyze flows by worker and firm characteristics. A research release of NAICS subsector J2J tabulations can be found at lehd.ces.census.gov/data/j2j_subsector_research.html.

LEHD Origin-Destination Employment Statistics (LODES) used by OnTheMap are available for download below. Version 8 of LODES was enumerated by 2020 census blocks. Previous versions of LODES were enumerated with 2010 census blocks (LODES7) or 2000 census blocks (LODES5).

Post-Secondary Employment Outcomes (PSEO) is a new set of statistics on the earnings and employment outcomes of graduates of select post-secondary institutions in the United States, and is constructed using LEHD data. Earnings Outcomes reports earnings by institution, degree field, degree level and graduation cohort for 1, 5 and 10 years after graduation. Employment Flows tabulations provide the destination industry and geography of employment for graduates of an institution by degree level, degree field, and graduation cohort, for one, five, and 10 years after graduation. A limited number of institutions are available as part of the pilot release, but future updates will include additional post-secondary institutions. Data coverage details and data files can be found here: lehd.ces.census.gov/data/pseo_experimental.html. Methodology and data source information can be found here: lehd.ces.census.gov/data/pseo_documentation.html.

PSEO data can also be accessed via the PSEO Explorer visualization tool. This interactive tool allows for comparisons of employment outcomes through dynamic grouped bar charts and employment flows through Sankey diagrams.

The Quarterly Workforce Indicators (QWI) are a set of economic indicators including employment, job creation, earnings, and other measures of employment flows. The QWI are reported based on detailed firm characteristics (geography, industry, age, size) and worker demographics information (sex, age, education, race, ethnicity) and are available tabulated to national*, state, metropolitan/micropolitan areas, county, and Workforce Investment Board (WIB) areas.

The Census Bureau's Veteran Employment Outcomes (VEO) are new statistics on Army veterans' labor market outcomes one, five, and 10 years after discharge, by military occupation, rank, demographics (age, sex, race, ethnicity, education), industry and geography of employment. These statistics are generated by linking veteran records provided by the U.S. Army to national administrative data on jobs at the U.S. Census Bureau. Coverage of the data is all enlisted soldiers in the Army who completed their initial term of service and were discharged between 2000 and 2015 (about 650,000 veterans). Although VEO currently covers only Army veterans, these statistics could potentially be expanded to other service branches. Documentation and CSV files are available for download here: lehd.ces.census.gov/data/veo_experimental.html

In addition to public-use data products, LEHD microdata are available for research use in approved projects. Researchers interested in using restricted-use LEHD data must submit a proposal to conduct research at a secure Federal Statistical Research Data Center (FSRDC). LEHD data available in the FSRDCs includes job-level quarterly earnings history data, person-level demographic data, establishment-level firm characteristics, and establishment-level Quarterly Workforce Indicators. Detailed information about restricted-use LEHD data, including available states and years, is on the CES LEHD Data page. Additional details are also available in the LEHD Snapshot documentation.

U.S. Census Bureau. (CURRENT YEAR). Job-to-Job Flows Data (2000-2023) [computer file]. Washington, DC: U.S. Census Bureau, Longitudinal-Employer Household Dynamics Program [distributor], accessed on CURRENT DATE at DATA VERSION [version]

U.S. Census Bureau. (CURRENT YEAR). LEHD Origin-Destination Employment Statistics Data (2002-2021) [computer file]. Washington, DC: U.S. Census Bureau, Longitudinal-Employer Household Dynamics Program [distributor], accessed on CURRENT DATE at LODES 8.1 [version]

U.S. Census Bureau. (CURRENT YEAR). Post-Secondary Employment Outcomes Data (Experimental) (2001-2020) [computer file]. Washington, DC: U.S. Census Bureau, Longitudinal-Employer Household Dynamics Program [distributor], accessed on CURRENT DATE at _experimental.html. DATA VERSION [version]

U.S. Census Bureau. (CURRENT YEAR). Quarterly Workforce Indicators (1990-2023) [computer file]. Washington, DC: U.S. Census Bureau, Longitudinal-Employer Household Dynamics Program [distributor], accessed on CURRENT DATE at DATA VERSION [version]

U.S. Census Bureau. (CURRENT YEAR). Veteran Employment Outcomes Data (Experimental) (2001-2015) [computer file]. Washington, DC: U.S. Census Bureau, Longitudinal-Employer Household Dynamics Program [distributor], accessed on CURRENT DATE at _experimental.html. DATA VERSION [version]

State and county names included on the file provide initial help in locating census tracts of interest (all census tracts are nested within counties). To determine the census tract for a particular location within a county, please see the Federal Financial Institutions Examination Council's FFIEC Geocoding/Mapping System.

Errata: On July 3, 2019, the Rural-Urban Commuting Area (RUCA) Codes data product was revised to correct a programming error affecting the 2010 secondary RUCA codes. The revision corrects the secondary codes of 10,909 of 74,002 census tracts. Secondary RUCA codes may be used to classify census tracts into rural and urban categories. The revised secondary codes result in an increase in the number of census tracts classified as rural. The 2010 primary RUCA codes were not affected by this revision.

In the LNGI case,the PUMS data field contains the value "0" which it turns means N/A (GQ/vacant). You can guess this because there are no " " fields in the PUMS data and "0" value doesn't appear in the codebook. By doing a little detective work using the codebook and some downloaded data you can figure this out. However, "0" isn't used for the "b" in the code book for all variables because sometimes "0" is a valid non-missing value (i.e. not N/A).

When I asked the people at ACSO they sent me a SAS format statement for LNGI which makes everything clear in the case of this one variable. But wouldn't it be nice if the Census published their PUMS SAS format catalog so we don't have to keep guessing what data value corresponds to "N/A" Do people have another way to find out what data value corresponds to "b" in the codebook? Some PUMS variables have over 100 coded values. If I'm working late on Friday, do I have to wait until Monday to get an answer ? How about a holiday weekend ?

I can't help, but I can say that all the different values for 0 or N/A etc are truly terrible. I had a conversation with Donna Daily a few weeks back and she said that data.census was a work in progress. However, it's not just that platform, regardless of the tool, there are lots of issues. I sent a follow-up email with the following text

I'd like to get her on a zoom meeting with a few key people in this group (not me, as I'm clueless). There is a specific person in her department who is supposed to be working on these issues (I wasn't given a name). I just want all the percentages formatted with a % and have a field name with the word percent in it. (which should be low-hanging fruit).

It could help but when I check LNGI field in the file you referenced, it shows ' ' 4 blanks as the "missing value." The comment at the head of the formats file indicates that it is from 2008 and thus it would not be current. In the 5 year 2020 PUMS codebook it indicates a 1 character field. The email that I got from the people at ACSO was correct and it indicates that "missing - GQ/vacant" corresponds to "0." for the 5 year 2020 vintage PUMS data. So at this point the only way that I can see to proceed is to download some data and do what I call "data archaeology" to figure out which code in the downloaded data does not appear in the codebook. For fields with a lot of codes when you download some data all the codes in the codebook might not appear in the downloaded data and you will be "stuck." Hopefully someone in this group will have experience with this.

I realize that when dealing with "the government" it can be frustrating at times. The last 2 sentences at the end of my initial posting expressed some of this. My comments were inappropriate and I am apologizing to all of the intelligent, hard working, dedicated people who work at the Census. All of my interactions with the people at the Census have been very professional and their responses prompt and detailed. Earlier in my career I spent some time at NASA. The people at NASA were the same. I've also emailed, talked with or interviewed with people at the FDA (Food and Drug Administration), the NCI (National Cancer Institute) and the CDC (Centers for Disease Control and Prevention). Even the IRS. When I get frustrated, I "take out a piece of paper," i.e. start a word processing document, and I write my two Senators and my Representative. I let my letter "sit" for a day or two. Then I end the letter with my suggestions as to how to improve the situation. I sign the letter with my name and address and then email a scan of the signed letter. Ultimately Congress is responsible for how our Federal agencies are funded and whether there is adequate staffing. I know this this reply is "off topic." But I think that it needs to be said.

3a8082e126