Abstract

This dataset includes all individuals from the 1860 US census.

Before Manuscript Submission

All manuscripts (and other items you'd like to publish) must be submitted to

phsdatacore@stanford.edu for approval prior to journal submission.

We will check your cell sizes and citations.

For more information about how to cite PHS and PHS datasets, please visit:

https:/phsdocs.developerhub.io/need-help/citing-phs-data-core

Documentation

This dataset was developed through a collaboration between the Minnesota Population Center and the Church of Jesus Christ of Latter-Day Saints. The data contain demographic variables, economic variables, migration variables and race variables. Unlike more recent census datasets, pre-1900 census datasets only contain individual level characteristics and no household or family characteristics, but household and family identifiers do exist.

The official enumeration day of the 1860 census was 1 June 1860. The main goal of an early census like the 1860 U.S. census was to allow Congress to determine the collection of taxes and the appropriation of seats in the House of Representatives. Each district was assigned a U.S. Marshall who organized other marshals to administer the census. These enumerators visited households and recorder names of every person, along with their age, sex, color, profession, occupation, value of real estate, place of birth, parental foreign birth, marriage, literacy, and whether deaf, dumb, blind, insane or “idiotic”.

Sources: Szucs, L.D. and Hargreaves Luebking, S. (1997). Research in Census Records, The Source: A Guidebook of American Genealogy. Ancestry Incorporated, Salt Lake City, UT Dollarhide, W.(2000). The Census Book: A Genealogist’s Guide to Federal Census Facts, Schedules and Indexes. Heritage Quest, Bountiful, UT

Abstract

The Integrated Public Use Microdata Series (IPUMS) Complete Count Data include more than 650 million individual-level and 7.5 million household-level records. The microdata are the result of collaboration between IPUMS and the nation’s two largest genealogical organizations—Ancestry.com and FamilySearch—and provides the largest and richest source of individual level and household data.

Before Manuscript Submission

All manuscripts (and other items you'd like to publish) must be submitted to

phsdatacore@stanford.edu for approval prior to journal submission.

We will check your cell sizes and citations.

For more information about how to cite PHS and PHS datasets, please visit:

https:/phsdocs.developerhub.io/need-help/citing-phs-data-core

Documentation

Historic data are scarce and often only exists in aggregate tables. The key advantage of historic US census data is the availability of individual and household level characteristics that researchers can tabulate in ways that benefits their specific research questions. The data contain demographic variables, economic variables, migration variables and family variables. Within households, it is possible to create relational data as all relations between household members are known. For example, having data on the mother and her children in a household enables researchers to calculate the mother’s age at birth. Another advantage of the Complete Count data is the possibility to follow individuals over time using a historical identifier.

In sum: the historic US census data are a unique source for research on social and economic change and can provide population health researchers with information about social and economic determinants.

The historic US 1920 census data was collected in January 1920. Enumerators collected data traveling to households and counting the residents who regularly slept at the household. Individuals lacking permanent housing were counted as residents of the place where they were when the data was collected. Household members absent on the day of data collected were either listed to the household with the help of other household members or were scheduled for the last census subdivision.

Notes

• We provide household and person data separately so that it is convenient to explore the descriptive statistics on each level. In order to obtain a full dataset, merge the household and person on the variables SERIAL and SERIALP. In order to create a longitudinal dataset, merge datasets on the variable HISTID.

• Households with more than 60 people in the original data were broken up for processing purposes. Every person in the large households are considered to be in their own household. The original large households can be identified using the variable SPLIT, reconstructed using the variable SPLITHID, and the original count is found in the variable SPLITNUM.

• Coded variables derived from string variables are still in progress. These variables include: occupation and industry.

• Missing observations have been allocated and some inconsistencies have been edited for the following variables: SPEAKENG, YRIMMIG, CITIZEN, AGE, BPL, MBPL, FBPL, LIT, SCHOOL, OWNERSHP, MORTGAGE, FARM, CLASSWKR, OCC1950, IND1950, MARST, RACE, SEX, RELATE, MTONGUE. The flag variables indicating an allocated observation for the associated variables can be included in your extract by clicking the ‘Select data quality flags’ box on the extract summary page.

• Most inconsistent information was not edited for this release, thus there are observations outside of the universe for some variables. In particular, the variables GQ, and GQTYPE have known inconsistencies and will be improved with the next release.

%3C!-- --%3E

Section 2

This dataset was created on 2020-01-10 18:46:34.647 by merging multiple datasets together. The source datasets for this version were:

IPUMS 1920 households: This dataset includes all households from the 1920 US census.

IPUMS 1920 persons: This dataset includes all individuals from the 1920 US census.

IPUMS 1920 Lookup: This dataset includes variable names, variable labels, variable values, and corresponding variable value labels for the IPUMS 1920 datasets.

Website alows the public full access to the 1940 Census images, census maps and descriptions.

The data sets in this repository allow users to link people among the U.S. decennial censuses, using the "histid" identifier. The census data sets users will need are indexed by Ancestry.com and are hosted by IPUMS at https://usa.ipums.org/usa-action/samples. Users will need to download the full-count census for each year and be sure to select the "histid" variable that is available under the Person/Historical Technical drop-down menu.As of 7/12/21, links are available between the 1900-1910, 1910-1920, and 1900-1920 censuses.A detailed account of how these links are created and a description of the data and its characteristics are available in the following article:Price, J., Buckles, K., Van Leeuwen, J., & Riley, I. (2021). Combining family history and machine learning to link historical records: The Census Tree data set. Explorations in Economic History, 80, 101391.https://www.sciencedirect.com/science/article/pii/S0014498321000024

Context :

The United States census count (also known as the Decennial Census of Population and Housing) is a count of every resident of the US. The census occurs every 10 years and is conducted by the United States Census Bureau. Census data is publicly available through the census website, but much of the data is available in summarized data and graphs. The raw data is often difficult to obtain, is typically divided by region, and it must be processed and combined to provide information about the nation as a whole. Update frequency: Historic (none)

Dataset source

United States Census Bureau

Sample Query

SELECT zipcode, population FROM bigquery-public-data.census_bureau_usa.population_by_zip_2010 WHERE gender = '' ORDER BY population DESC LIMIT 10

Terms of use

This dataset is publicly available for anyone to use under the following terms provided by the Dataset Source - http://www.data.gov/privacy-policy#data_policy - and is provided "AS IS" without any warranty, express or implied, from Google. Google disclaims all liability for any damages, direct or indirect, resulting from the use of the dataset.

See the GCP Marketplace listing for more details and sample queries: https://console.cloud.google.com/marketplace/details/united-states-census-bureau/us-census-data

The Census Tree is the largest-ever database of record links among the historical U.S. censuses, with over 700 million links for people living in the United States between 1850 and 1940. These links allow researchers to construct a longitudinal dataset that is highly representative of the population, and that includes women, Black Americans, and other under-represented populations at unprecedented rates. This project contains the files necessary to closely replicate the links between the 1900 and 1910 censuses. For more information, consult the included Read Me file, and visit https://censustree.org.

This data layer is an element of the Oregon GIS Framework. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

The Census Tree is the largest-ever database of record links among the historical U.S. censuses, with over 700 million links for people living in the United States between 1850 and 1940. These links allow researchers to construct a longitudinal dataset that is highly representative of the population, and that includes women, Black Americans, and other under-represented populations at unprecedented rates. Each .csv file consists of a crosswalk between the two years indicated in the filename, using the IPUMS histids. For more information, consult the included Read Me file, and visit https://censustree.org.

Notice: The U.S. Census Bureau is delaying the release of the 2016-2020 ACS 5-year data until March 2022. For more information, please read the Census Bureau statement regarding this matter. -----------------------------------------This layer shows population broken down by race and Hispanic origin. This layer shows Census data from Esri's Living Atlas and is clipped to only show Tempe census tracts. This layer is symbolized to show the predominant race living within an area. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right (in ArcGIS Online). Data is from US Census American Community Survey (ACS) 5-year estimates. Vintage: 2015-2019 ACS Table(s): B03002 (Not all lines of this ACS table are available in this feature layer.) Data downloaded from: Census Bureau's API for American Community Survey Date of Census update: December 10, 2020 National Figures: data.census.gov Additional Census data notes and data processing notes are available at the Esri Living Atlas Layer: https://tempegov.maps.arcgis.com/home/item.html?id=23ab8028f1784de4b0810104cd5d1c8f&view=list&sortOrder=desc&sortField=defaultFSOrder#overview (Esri's Living Atlas always shows latest data)

About this dataset

Context

The dataset tabulates the Lake View population distribution across 18 age groups. It lists the population in each age group along with the percentage population relative of the total population for Lake View. The dataset can be utilized to understand the population distribution of Lake View by age. For example, using this dataset, we can identify the largest age group in Lake View.

Key observations

The largest age group in Lake View, SC was for the group of age 45 to 49 years years with a population of 81 (12.25%), according to the ACS 2019-2023 5-Year Estimates. At the same time, the smallest age group in Lake View, SC was the 85 years and over years with a population of 9 (1.36%). Source: U.S. Census Bureau American Community Survey (ACS) 2019-2023 5-Year Estimates

Content

When available, the data consists of estimates from the U.S. Census Bureau American Community Survey (ACS) 2019-2023 5-Year Estimates

Age groups:

• Under 5 years
• 5 to 9 years
• 10 to 14 years
• 15 to 19 years
• 20 to 24 years
• 25 to 29 years
• 30 to 34 years
• 35 to 39 years
• 40 to 44 years
• 45 to 49 years
• 50 to 54 years
• 55 to 59 years
• 60 to 64 years
• 65 to 69 years
• 70 to 74 years
• 75 to 79 years
• 80 to 84 years
• 85 years and over

Variables / Data Columns

• Age Group: This column displays the age group in consideration
• Population: The population for the specific age group in the Lake View is shown in this column.
• % of Total Population: This column displays the population of each age group as a proportion of Lake View total population. Please note that the sum of all percentages may not equal one due to rounding of values.

Good to know

Margin of Error

Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.

Custom data

If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.

Inspiration

Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.

Recommended for further research

This dataset is a part of the main dataset for Lake View Population by Age. You can refer the same here

This dataset contains data from the P.L. 94-171 2020 Census Redistricting Program. The 2020 Census Redistricting Data Program provides states the opportunity to delineate voting districts and to suggest census block boundaries for use in the 2020 Census redistricting data tabulations (Public Law 94-171 Redistricting Data File). In addition, the Redistricting Data Program will periodically collect state legislative and congressional district boundaries if they are changed by the states. The program is also responsible for the effective delivery of the 2020 Census P.L. 94-171 Redistricting Data statutorily required by one year from Census Day. The program ensures continued dialogue with the states in regard to 2020 Census planning, thereby allowing states ample time for their planning, response, and participation. The U.S. Census Bureau will deliver the Public Law 94-171 redistricting data to all states by Sept. 30, 2021. COVID-19-related delays and prioritizing the delivery of the apportionment results delayed the Census Bureau’s original plan to deliver the redistricting data to the states by April 1, 2021.

Data in this dataset contains information on population, diversity, race, ethnicity, housing, household, vacancy rate for 2020 for various geographies (county, MCD, Philadelphia Planning Districts (referred to as county planning areas [CPAs] internally, Census designated places, tracts, block groups, and blocks)

For more information on the 2020 Census, visit https://www.census.gov/programs-surveys/decennial-census/about/rdo/summary-files.html

PLEASE NOTE: 2020 Decennial Census data has had noise injected into it because of the Census's new Disclosure Avoidance System (DAS). This can mean that population counts and characteristics, especially when they are particularly small, may not exactly correspond to the data as collected. As such, caution should be exercised when examining areas with small counts. Ron Jarmin, acting director of the Census Bureau posted a discussion of the redistricting data, which outlines what to expect with the new DAS. For more details on accuracy you can read it here: https://www.census.gov/newsroom/blogs/director/2021/07/redistricting-data.html

2020 Census data for the city of Boston, Boston neighborhoods, census tracts, block groups, and voting districts. In the 2020 Census, the U.S. Census Bureau divided Boston into 207 census tracts (~4,000 residents) made up of 581 smaller block groups. The Boston Planning and Development Agency uses the 2020 tracts to approximate Boston neighborhoods. The 2020 Census Redistricting data also identify Boston’s voting districts.

For analysis of Boston’s 2020 Census data including graphs and maps by the BPDA Research Division and Office of Digital Cartography and GIS, see 2020 Census Research Publications

For a complete official data dictionary, please go to 2020 Census State Redistricting Data (Public Law 94-171) Summary File, Chapter 6. Data Dictionary. 2020 Census State Redistricting Data (Public Law 94-171) Summary File

2020 Census Tracts In Boston

2020 Census Block Groups In Boston

Boston Neighborhood Boundaries Approximated By 2020 Census Tracts

Boston Voting District Boundaries

The City Census Viewer uses data from the American Community Survey (ACS) on the census tract, neighborhood, and city ward level. Data in this application is filtered for Cuyahoga county, and users can filter further by cities within the county. All data in this viewer is exportable.InstructionsClick on a census tract to view more information about the data.Click the "Export Data" button to view and export the table that supports the active map.Click the "Menu" button to view additional data categories.Release DateAugust 2023Update FrequencyThis dataset is updated every year, when the newest vintage of the American Community Survey is released.ContactsReport errors or issues to Samuel Martinez, Spatial Data Analyst at City of Cleveland Urban AI

2010-2018. US Census Annual Estimates of the Resident Population for Selected Age Groups by Sex for the United States. The estimates are based on the 2010 Census and reflect changes to the April 1, 2010 population due to the Count Question Resolution program and geographic program revisions. Median age is calculated based on single year of age. For population estimates methodology statements, see http://www.census.gov/popest/methodology/index.html.

This is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. The units of geography used for the 2010 Census maps displayed here are the Census tracts. Census tracts generally have a population size between 1 - 200 and 8 - 000 people - with an optimum size of 4 - 000 people. When first delineated - census tracts were designed to be homogeneous with respect to population characteristics - economic status - and living conditions. Census tract boundaries generally follow visible and identifiable features. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances - a census tract may consist of noncontiguous areas. The data collected on the short form survey are general demographic characteristics such as age - race - ethnicity - household relationship - housing vacancy and tenure (owner/renter).Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Demographics/MD_CensusData/FeatureServer ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

These data comprise Census records relating to the Alaskan people's population demographics for the State of Alaskan Salmon and People (SASAP) Project. Decennial census data were originally extracted from IPUMS National Historic Geographic Information Systems website: https://data2.nhgis.org/main(Citation: Steven Manson, Jonathan Schroeder, David Van Riper, and Steven Ruggles. IPUMS National Historical Geographic Information System: Version 12.0 [Database]. Minneapolis: University of Minnesota. 2017. http://doi.org/10.18128/D050.V12.0). A number of relevant tables of basic demographics on age and race, household income and poverty levels, and labor force participation were extracted.

  These particular variables were selected as part of an effort to understand and potentially quantify various dimensions of well-being in Alaskan communities.
  The file "censusdata_master.csv" is a consolidation of all 21 other data files in the package. For detailed information on how the datasets vary over different years, view the file "readme.docx" available in this data package.

  The included .Rmd file is a script which combines the 21 files by year into a single file (censusdata_master.csv). It also cleans up place names (including typographical errors) and uses the
  USGS place names dataset and the SASAP regions dataset to assign latitude and longitude values and region values to each place in the dataset. Note that some places were not assigned a region or
  location because they do not fit well into the regional framework.

  Considerable heterogeneity exists between census surveys each year. While we have attempted to combine these datasets in a way that makes sense, there may be some discrepancies or unexpected values.
  Please send a description of any unusual values to the dataset contact.

This API returns the US Census Block geography ID information given a passed Latitude and Longitude.

analyze the current population survey (cps) annual social and economic supplement (asec) with r the annual march cps-asec has been supplying the statistics for the census bureau's report on income, poverty, and health insurance coverage since 1948. wow. the us census bureau and the bureau of labor statistics ( bls) tag-team on this one. until the american community survey (acs) hit the scene in the early aughts (2000s), the current population survey had the largest sample size of all the annual general demographic data sets outside of the decennial census - about two hundred thousand respondents. this provides enough sample to conduct state- and a few large metro area-level analyses. your sample size will vanish if you start investigating subgroups b y state - consider pooling multiple years. county-level is a no-no. despite the american community survey's larger size, the cps-asec contains many more variables related to employment, sources of income, and insurance - and can be trended back to harry truman's presidency. aside from questions specifically asked about an annual experience (like income), many of the questions in this march data set should be t reated as point-in-time statistics. cps-asec generalizes to the united states non-institutional, non-active duty military population. the national bureau of economic research (nber) provides sas, spss, and stata importation scripts to create a rectangular file (rectangular data means only person-level records; household- and family-level information gets attached to each person). to import these files into r, the parse.SAScii function uses nber's sas code to determine how to import the fixed-width file, then RSQLite to put everything into a schnazzy database. you can try reading through the nber march 2012 sas importation code yourself, but it's a bit of a proc freak show. this new github repository contains three scripts: 2005-2012 asec - download all microdata.R down load the fixed-width file containing household, family, and person records import by separating this file into three tables, then merge 'em together at the person-level download the fixed-width file containing the person-level replicate weights merge the rectangular person-level file with the replicate weights, then store it in a sql database create a new variable - one - in the data table 2012 asec - analysis examples.R connect to the sql database created by the 'download all microdata' progr am create the complex sample survey object, using the replicate weights perform a boatload of analysis examples replicate census estimates - 2011.R connect to the sql database created by the 'download all microdata' program create the complex sample survey object, using the replicate weights match the sas output shown in the png file below 2011 asec replicate weight sas output.png statistic and standard error generated from the replicate-weighted example sas script contained in this census-provided person replicate weights usage instructions document. click here to view these three scripts for more detail about the current population survey - annual social and economic supplement (cps-asec), visit: the census bureau's current population survey page the bureau of labor statistics' current population survey page the current population survey's wikipedia article notes: interviews are conducted in march about experiences during the previous year. the file labeled 2012 includes information (income, work experience, health insurance) pertaining to 2011. when you use the current populat ion survey to talk about america, subract a year from the data file name. as of the 2010 file (the interview focusing on america during 2009), the cps-asec contains exciting new medical out-of-pocket spending variables most useful for supplemental (medical spending-adjusted) poverty research. confidential to sas, spss, stata, sudaan users: why are you still rubbing two sticks together after we've invented the butane lighter? time to transition to r. :D

Geolytics Census 2000 Long Form dataset. The Geolytics Census 2000 Long Form is a comprehensive source of detailed information about the people, housing, and economy of the United States. The Census 2000 Long Form offers the entire US Census Bureau's SF3 dataset. This dataset contains variables such as income, housing, employment, language spoken, ancestry, education, poverty, rent, mortgage, commute to work, etc. There are 5,500 variables at the Block Group level. A select portion of the Geolytics Census data was joined to GDT spatial data by block group and some census attributes were aggregated. See the attached txt file for a description of the attributes. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The Census of Agriculture is a complete count of U.S. farms and ranches and the people who operate them. Even small plots of land - whether rural or urban - growing fruit, vegetables or some food animals count if $1,000 or more of such products were raised and sold, or normally would have been sold, during the Census year. The Census of Agriculture, taken only once every five years, looks at land use and ownership, operator characteristics, production practices, income and expenditures. For America's farmers and ranchers, the Census of Agriculture is their voice, their future, and their opportunity. The Census Data Query Tool (CDQT) is a web-based tool that is available to access and download table level data from the Census of Agriculture Volume 1 publication. The data found via the CDQT may also be accessed in the NASS Quick Stats database. The CDQT is unique in that it automatically displays data from the past five Census of Agriculture publications. The CDQT is presented as a "2017 centric" view of the Census of Agriculture data. All data series that are present in the 2017 dataset are available within the CDQT, and any matching data series from prior Census years will also display (back to 1997). If a data series is not included in the 2017 dataset, then data cells will remain blank in the tool. For example, one of the data series had a label change from "Operator" to "Producer." This means that data from prior Census years labelled "Operator" will not show up where the label has changed to “Producer” for 2017. The new Census Data Query Tool application can be used to query Census data from 1997 through 2017. Data are searchable by Census table and are downloadable as CSV or PDF files. 2017 Census Ag Atlas Maps are also available for download. Resources in this dataset:Resource Title: 2017 Census of Agriculture - Census Data Query Tool (CDQT). File Name: Web Page, url: https://www.nass.usda.gov/Quick_Stats/CDQT/chapter/1/table/1 The Census Data Query Tool (CDQT) is a web based tool that is available to access and download table level data from the Census of Agriculture Volume 1 publication. The data found via the CDQT may also be accessed in the NASS Quick Stats database. The CDQT is unique in that it automatically displays data from the past five Census of Agriculture publications. The CDQT is presented as a "2017 centric" view of the Census of Agriculture data. All data series that are present in the 2017 dataset are available within the CDQT, and any matching data series from prior Census years will also display (back to 1997). If a data series is not included in the 2017 dataset, then data cells will remain blank in the tool. For example, one of the data series had a label change from "Operator" to "Producer." This means that data from prior Census years labelled "Operator" will not show up where the label has changed to "Producer" for 2017. Using CDQT:

Upon entering the CDQT, a data table is present. Changing the parameters at the top of the data table will retrieve different combinations of Census Chapter, Table, State, or County (when selecting Chapter 2). For the U.S., Volume 1, US/State Chapter 1 will include only U.S. data; Chapter 2 will include U.S. and State level data. For a State, Volume 1 US/State Level Data Chapter 1 will include only the State level data; Chapter 2 will include the State and county level data. Once a selection is made, press the “Update Grid” button to retrieve the new data table. Comma-separated values (CSV) download, compatible with most spreadsheet and database applications: to download a CSV file of the data as it is currently presented in the data grid, press the "CSV" button in the "Export Data" section of the toolbar. When CSV is chosen, data will be downloaded as numeric. To view the source PDF file for the data table, press the "View PDF" button in the toolbar.