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.

On the Census Data Hub, CSO Census 2022 and 2016 datasets have been combined with Tailte Éireann official boundary data. Almost 800 variables across 15 themes can be retrieved to make powerful visualisations for both statistical and statutory boundaries. This guide will show you how to view, and quickly visualise data, based on a variable of your choice.Topics covered include: View Census countsSearching for data Viewing Census count data on a map Filtering by location Multiple filters

The U.S. Census counts every resident in the United States. It is mandated by Article I, Section 2 of the Constitution and takes place every 10 years. The basic purpose of the census is apportionment and redistricting. "Apportionment" is the process of dividing the 435 memberships, or seats, in the House of Representatives among the 50 states based on the population figures collected during the decennial census. "Redistricting" is the process of geographically defining state legislative districts. The census data allow state officials to realign congressional and state legislative districts in their states, taking into account population shifts since the last census and assuring equal representation for their constituents in compliance with the “one-person, one-vote” principle of the 1965 Voting Rights Act.

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

1940 Population Census Data for Baltimore, Maryland. Refer to the 1940 codebook (codebook_1940.pdf) for more information. 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 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

A global database of Census Data that provides an understanding of population distribution at administrative and zip code levels over 55 years, past, present, and future.

Leverage up-to-date census data with population trends for real estate, market research, audience targeting, and sales territory mapping.

Self-hosted commercial demographic dataset curated based on trusted sources such as the United Nations or the European Commission, with a 99% match accuracy. The global Census Data is standardized, unified, and ready to use.

Use cases for the Global Census Database (Consumer Demographic Data)

• Ad targeting

• B2B Market Intelligence

• Customer analytics

• Real Estate Data Estimations

• Marketing campaign analysis

• Demand forecasting

• Sales territory mapping

• Retail site selection

• Reporting

• Audience targeting

Census data export methodology

Our consumer demographic data packages are offered in CSV format. All Demographic data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Product Features

• Historical population data (55 years)

• Changes in population density

• Urbanization Patterns

• Accurate at zip code and administrative level

• Optimized for easy integration

• Easy customization

• Global coverage

• Updated yearly

• Standardized and reliable

• Self-hosted delivery

• Fully aggregated (ready to use)

• Rich attributes

Why do companies choose our demographic databases

• Standardized and unified demographic data structure

• Seamless integration in your system

• Dedicated location data expert

Note: Custom population data packages are available. Please submit a request via the above contact button for more details.

Although the American Community Survey (ACS) produces population, demographic and housing unit estimates, the decennial census is the official source of population totals for April 1st of each decennial year. In between censuses, the Census Bureau's Population Estimates Program produces and disseminates the official estimates of the population for the nation, states, counties, cities, and towns and estimates of housing units and the group quarters population for states and counties..Information about the American Community Survey (ACS) can be found on the ACS website. Supporting documentation including code lists, subject definitions, data accuracy, and statistical testing, and a full list of ACS tables and table shells (without estimates) can be found on the Technical Documentation section of the ACS website.Sample size and data quality measures (including coverage rates, allocation rates, and response rates) can be found on the American Community Survey website in the Methodology section..Source: U.S. Census Bureau, 2023 American Community Survey 1-Year Estimates.ACS data generally reflect the geographic boundaries of legal and statistical areas as of January 1 of the estimate year. For more information, see Geography Boundaries by Year..Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted roughly as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see ACS Technical Documentation). The effect of nonsampling error is not represented in these tables..Users must consider potential differences in geographic boundaries, questionnaire content or coding, or other methodological issues when comparing ACS data from different years. Statistically significant differences shown in ACS Comparison Profiles, or in data users' own analysis, may be the result of these differences and thus might not necessarily reflect changes to the social, economic, housing, or demographic characteristics being compared. For more information, see Comparing ACS Data..Households not paying cash rent are excluded from the calculation of median gross rent..Estimates of urban and rural populations, housing units, and characteristics reflect boundaries of urban areas defined based on 2020 Census data. As a result, data for urban and rural areas from the ACS do not necessarily reflect the results of ongoing urbanization..Explanation of Symbols:- The estimate could not be computed because there were an insufficient number of sample observations. For a ratio of medians estimate, one or both of the median estimates falls in the lowest interval or highest interval of an open-ended distribution. For a 5-year median estimate, the margin of error associated with a median was larger than the median itself.N The estimate or margin of error cannot be displayed because there were an insufficient number of sample cases in the selected geographic area. (X) The estimate or margin of error is not applicable or not available.median- The median falls in the lowest interval of an open-ended distribution (for example "2,500-")median+ The median falls in the highest interval of an open-ended distribution (for example "250,000+").** The margin of error could not be computed because there were an insufficient number of sample observations.*** The margin of error could not be computed because the median falls in the lowest interval or highest interval of an open-ended distribution.***** A margin of error is not appropriate because the corresponding estimate is controlled to an independent population or housing estimate. Effectively, the corresponding estimate has no sampling error and the margin of error may be treated as zero.

Population and other demographic information is collected by the US Census Bureau.

View the US Census Bureau's Quick Facts page about Bloomington, Indiana at https://www.census.gov/quickfacts

The Demographic Profile and other data for Bloomington can be viewed or downloaded from the American FactFinder search tool: https://factfinder.census.gov/bkmk/cf/1.0/en/place/Bloomington city, Indiana/POPULATION/DECENNIAL_CNT

The Census Bureau is creating a new platform for data. This site is in a preview stage and some parts are under construction. Here is a link for Bloomington: https://data.census.gov/cedsci/results/all?q=Bloomington%20city,%20Indiana&g=1600000US1805860&ps=app*from@SINGLE_SEARCH

The City webpage for Census data contains other related information: https://bloomington.in.gov/about/census-data

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. The RMarkdown document SASAPWebsiteGraphicsCensus.Rmd is used to generate a variety of figures using these data, including the additional file Chignik_population.png. An additional set of 25 figures showing regional trends in population and income metrics are also included.

The Census 2011 Microdata Teaching File for Scotland data collection forms part of the statistical outputs from the 2011 UK Census. The Teaching File is an open access dataset constructed from the safeguarded microdata sample of individuals (see SNs 7834 and 7835 for background information). Converted by the UK Data Service Census Support Service, it is an SPSS/Stata version of the spreadsheet Microdata Teaching File for Scotland produced by National Records of Scotland (NRS), drawn from data collected in the 2011 Census. The file was produced by NRS with a variables list and a user guide – all of which are considered the essential and definitive companions to the data. The original spreadsheet format Microdata Teaching File is an open government file is available from the NRS Census 2011 Microdata Teaching File webpage.

More information about the teaching file and Census 2011, including forms and links to other Census data, are available both on the NRS site or via the UK Data Service Census Support webpages.

Historical population as enumerated and corrected from 1790 through 2020. North Carolina was one of the 13 original States and by the time of the 1790 census had essentially its current boundaries. The Census is mandated by the United States Constitution and was first completed for 1790. The population has been counted every ten years hence, with some limitations. In 1790 census coverage included most of the State, except for areas in the west, parts of which were not enumerated until 1840. The population for 1810 includes Walton County, enumerated as part of Georgia although actually within North Carolina. Historical populations shown here reflect the population of the respective named county and not necessarily the population of the area of the county as it was defined for a particular census. County boundaries shown in maps reflect boundaries as defined in 2020. Historic boundaries for some counties may include additional geographic areas or may be smaller than the current geographic boundaries. Notes below list the county or counties with which the population of a currently defined county were enumerated historically (Current County: Population counted in). The current 100 counties have been in place since the 1920 Census, although some modifications to the county boundaries have occurred since that time. For historical county boundaries see: Atlas of Historical County Boundaries Project (newberry.org)County Notes: Note 1: Total for 1810 includes population (1,026) of Walton County, reported as a Georgia county but later determined to be situated in western North Carolina. Total for 1890 includes 2 Indians in prison, not reported by county. Note 2: Alexander: *Iredell, Burke, Wilkes. Note 3: Avery: *Caldwell, Mitchell, Watauga. Note 4: Buncombe: *Burke, Rutherford; see also note 22. Note 5: Caldwell: *Burke, Wilkes, Yancey. Note 6: Cleveland: *Rutherford, Lincoln. Note 7: Columbus: *Bladen, Brunswick. Note 8: Dare: *Tyrrell, Currituck, Hyde. Note 9: Hoke: *Cumberland, Robeson. Note 10: Jackson: *Macon, Haywood. Note 11: Lee: *Moore, Chatham. Note 12: Lenoir: *Dobbs (Greene); Craven. Note 13: McDowell: *Burke, Rutherford. Note 14: Madison: *Buncombe, Yancey. Note 15: Mitchell: *Yancey, Watauga. Note 16: Pamlico: *Craven, Beaufort. Note 17: Polk: *Rutherford, Henderson. Note 18: Swain: *Jackson, Macon. Note 19: Transylvania: *Henderson, Jackson. Note 20: Union: *Mecklenburg, Anson. Note 21: Vance: *Granville, Warren, Franklin. Note 22: Walton: Created in 1803 as a Georgia county and reported in 1810 as part of Georgia; abolished after a review of the State boundary determined that its area was located in North Carolina. By 1820 it was part of Buncombe County. Note 23: Watauga: *Ashe, Yancey, Wilkes; Burke. Note 24: Wilson: *Edgecombe, Nash, Wayne, Johnston. Note 25: Yancey: *Burke, Buncombe. Note 26: Alleghany: *Ashe. Note 27: Haywood: *Buncombe. Note 28: Henderson: *Buncombe. Note 29: Person: Caswell. Note 30: Clay: Cherokee. Note 31: Graham: Cherokee. Note 32: Harnett: Cumberland. Note 33: Macon: Haywood.

Note 34: Catawba: Lincoln. Note 35: Gaston: Lincoln. Note 36: Cabarrus: Mecklenburg.
Note 37: Stanly: Montgomery. Note 38: Pender: New Hanover. Note 39: Alamance: Orange.
Note 40: Durham: Orange, Wake. Note 41: Scotland: Richmond. Note 42: Davidson: Rowan. Note 43: Davie: Rowan.Note 44: Forsyth: Stokes. Note 45: Yadkin: Surry.
Note 46: Washington: Tyrrell.Note 47: Ashe: Wilkes. Part III. Population of Counties, Earliest Census to 1990The 1840 population of Person County, NC should be 9,790. The 1840 population of Perquimans County, NC should be 7,346.

A. SUMMARY This dataset contains population and demographic estimates and associated margins of error obtained and derived from the US Census. The data is presented over multiple years and geographies. The data is sourced primarily from the American Community Survey. B. HOW THE DATASET IS CREATED The raw data is obtained from the census API. Some estimates as published as-is and some are derived. C. UPDATE PROCESS New estimates and years of data are appended to this dataset. To request additional census data for San Francisco, email support@datasf.org D. HOW TO USE THIS DATASET The dataset is long and contains multiple estimates, years and geographies. To use this dataset, you can filter by the overall segment which contains information about the source, years, geography, demographic category and reporting segment. For census data used in specific reports, you can filter to the reporting segment. To use a subset of the data, you can create a filtered view. More information of how to filter data and create a view can be found here

This study was conducted under the auspices of the Center for Studies in Demography and Ecology at the University of Washington. It is a nationally representative sample of the population of the United States in 1900, drawn from the manuscript returns of individuals enumerated in the 1900 United States Census. Household variables include region, state and county of household, size of household, and type and ownership of dwelling. Individual variables for each household member include relationship to head of household, race, sex, age, marital status, number of children, and birthplace. Immigration variables include parents' birthplace, year of immigration and number of years in the United States. Occupation variables include occupation, coded by both the 1900 and 1950 systems, and number of months unemployed. Education variables include number of months in school, whether respondents could read or write a language, and whether they spoke English.

About this dataset

Context

The dataset tabulates the Southern View population by age. The dataset can be utilized to understand the age distribution and demographics of Southern View.

Content

The dataset constitues the following three datasets

• Southern View, IL Age Group Population Dataset: A complete breakdown of Southern View age demographics from 0 to 85 years, distributed across 18 age groups
• Southern View, IL Age Cohorts Dataset: Children, Working Adults, and Seniors in Southern View - Population and Percentage Analysis
• Southern View, IL Population Pyramid Dataset: Age Groups, Male and Female Population, and Total Population for Demographics Analysis

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/.

1940 Age Census Data for Baltimore, Maryland. Refer to the 1940 codebook (codebook_1940.pdf) for more information. 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.

NOTE: As of 2/16/2023, this page is not being updated. For data on updated (bivalent) COVID-19 booster vaccination click here: https://app.powerbigov.us/view?r=eyJrIjoiODNhYzVkNGYtMzZkMy00YzA3LWJhYzUtYTVkOWFlZjllYTVjIiwidCI6IjExOGI3Y2ZhLWEzZGQtNDhiOS1iMDI2LTMxZmY2OWJiNzM4YiJ9 This table shows the number and percent of people that have initiated COVID-19 vaccination and are fully vaccinated by CT census tract (including residents of all ages). It also shows the number of people who have not received vaccine and who are not yet fully vaccinated. All data in this report are preliminary; data for previous dates will be updated as new reports are received and data errors are corrected. A person who has received at least one dose of any vaccine is considered to have initiated vaccination. A person is considered fully vaccinated if they have completed a primary series by receiving 2 doses of the Pfizer, Novavax or Moderna vaccines or 1 dose of the Johnson & Johnson vaccine. The fully vaccinated are a subset of the number who have received at least one dose. The percent with at least one dose many be over-estimated and the percent fully vaccinated may be under-estimated because of vaccine administration records for individuals that cannot be linked because of differences in how names or date of birth are reported. Population data obtained from the 2019 Census ACS (www.census.gov) Geocoding is used to determine the census tract in which a person lives. People for who a census tract cannot be determined based on available address data are not included in this table. DPH recommends that these data are primarily used to identify areas that require additional attention rather than to establish and track the exact level of vaccine coverage. Census tract coverage estimates can play an important role in planning and evaluating vaccination strategies. However, inaccuracies in the data that are inherent to population surveillance may be magnified when analyses are performed down to the census tract level. We make every effort to provide accurate data, but inaccuracies may result from things like incomplete or inaccurate addresses, duplicate records, and sampling error in the American Community Survey that is used to estimate census tract population size and composition. These things may result in overestimates or underestimates of vaccine coverage. Some census tracts are suppressed. This is done if the number of people vaccinated is less than 5 or if the census population estimate is considered unreliable (coefficient of variance > 30%). Coverage estimates over 100% are shown as 100%. Connecticut COVID-19 Vaccine Program providers are required to report information on all COVID-19 vaccine doses administered to CT WiZ, the Connecticut Immunization Information System. Data on doses administered to CT residents out-of-state are being added to CT WiZ jurisdiction-by-jurisdiction. Doses administered by some Federal entities (including Department of Defense, Department of Correction, Department of Veteran’s Affairs, Indian Health Service) are not yet reported to CT WiZ. Data reported here reflect the vaccination records currently reported to CT WiZ. Caution should be used when interpreting coverage estimates in towns with large college/university populations since coverage may be underestimated. In the census, college/university students who live on or just off campus would be counted in the college/university town. However, if a student was vaccinated while studying remotely in his/her hometown, the student may be counted as a vaccine recipient in that town. As part of continuous data quality improvement efforts, duplicate records were removed from the COVID-19 vaccination data during the weeks of 4/19/2021 and 4/26/2021. As of 1/13/2021, census tract level data are provider by town for all ages. Data by age group is no longer available.

The U.S. Census Bureau TIGER/Line® files in this data collection were originally distributed by the Inter-university Consortium for Political and Social Research (ICPSR) through its TIGER/Line file web site, which was decommissioned in 2018 (archived version: https://web.archive.org/web/20090924181858/http://www.icpsr.umich.edu/TIGER/index.html). There, users could download various versions of the U.S. Census Bureau's TIGER (Topologically Integrated Geographic Encoding and Referencing) database. The TIGER/Line files do not include demographic data, but they do contain geographic information that can be linked to the Census Bureau’s demographic data. Due to file number limitations in openICPSR, the original data collections have been bundled into single zip packages. A single TIGER_directory.txt file listing the original files and the original directory structure is included with the root directory. Documentation files are also included as standalone subdirectories in each collection so users do not need to download entire zip bundles to view documentation. The TIGER/Line data are stored in compressed format in subdirectories by state name. There is one TIGER/Line file (in a compressed format) for each county or county equivalent. The file names consist of TGR + the 2-digit state FIPS (Federal Information Processing Standards) code + the 3-digit county FIPS code (i.e. TGR01031.ZIP for Coffee County, Alabama). Each state folder contains individual county files.The individual county files include one file for each record type included for that county with the following name convention: tgr01031.rt1. The convention follows the order described above with each file having a suffix which includes 'rt' (record type) followed by its designation (in this case record type 1). Each county file also contains its own metadata record.If present, documentation files for the TIGER/Line data are stored in a directory named '0docs' which is located in the 'Parent Directory'. This directory appears at the top of the index of state subdirectories for each edition of the TIGER/Line files. The documentation includes a complete list of FIPS state and county codes.