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. The United States census dataset includes nationwide population counts from the 2000 and 2010 censuses. Data is broken out by gender, age and location using zip code tabular areas (ZCTAs) and GEOIDs. ZCTAs are generalized representations of zip codes, and often, though not always, are the same as the zip code for an area. GEOIDs are numeric codes that uniquely identify all administrative, legal, and statistical geographic areas for which the Census Bureau tabulates data. GEOIDs are useful for correlating census data with other censuses and surveys. This public dataset is hosted in Google BigQuery and is included in BigQuery's 1TB/mo of free tier processing. This means that each user receives 1TB of free BigQuery processing every month, which can be used to run queries on this public dataset. Watch this short video to learn how to get started quickly using BigQuery to access public datasets. What is BigQuery .

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 IPUMS 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.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 1940 census data was collected in April 1940. 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 IPUMS 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 SPLIT40, reconstructed using the variable SERIAL40, and the original count is found in the variable NUMPREC40.
• Some variables are missing from this data set for specific enumeration districts. The enumeration districts with missing data can be identified using the variable EDMISS. These variables will be added in a future release.
• Coded variables derived from string variables are still in progress. These variables include: occupation, industry and migration status.
• Missing observations have been allocated and some inconsistencies have been edited for the following variables: Missing observations have been allocated and some inconsistencies have been edited for the following variables: SURSIM, SEX, SCHOOL, RELATE, RACE, OCC1950, MTONGUE, MBPL, FBPL, BPL, MARST, EMPSTAT, CITIZEN, OWNERSHP. 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 many variables. In particular, the variables GQ, and GQTYPE have known inconsistencies and will be improved with the next r

The census of population and housing, taken by the Census Bureau in years ending in 0 (zero). Article I of the Constitution requires that a census be taken every ten years for the purpose of reapportioning the U.S. House of Representatives. Title 13 of the U. S. Code provides the authorization for conducting the census in Puerto Rico and the Island Areas. After each decennial census, the results are released to the public in a variety of ways, including publishing multiple series of reports titled Census of Population and Housing. The abbreviation for these reports was CPH for some decades (including 1990 and 2010) and PHC for some decades (including 1970 and 2000).

A broad and generalized selection of 2014-2018 US Census Bureau 2018 5-year American Community Survey population data estimates, obtained via Census API and joined to the appropriate geometry (in this case, New Mexico Census tracts). The selection is not comprehensive, but allows a first-level characterization of total population, male and female, and both broad and narrowly-defined age groups. In addition to the standard selection of age-group breakdowns (by male or female), the dataset provides supplemental calculated fields which combine several attributes into one (for example, the total population of persons under 18, or the number of females over 65 years of age). The determination of which estimates to include was based upon level of interest and providing a manageable dataset for users.The U.S. Census Bureau's American Community Survey (ACS) is a nationwide, continuous survey designed to provide communities with reliable and timely demographic, housing, social, and economic data every year. The ACS collects long-form-type information throughout the decade rather than only once every 10 years. The ACS combines population or housing data from multiple years to produce reliable numbers for small counties, neighborhoods, and other local areas. To provide information for communities each year, the ACS provides 1-, 3-, and 5-year estimates. ACS 5-year estimates (multiyear estimates) are “period” estimates that represent data collected over a 60-month period of time (as opposed to “point-in-time” estimates, such as the decennial census, that approximate the characteristics of an area on a specific date). ACS data are released in the year immediately following the year in which they are collected. ACS estimates based on data collected from 2009–2014 should not be called “2009” or “2014” estimates. Multiyear estimates should be labeled to indicate clearly the full period of time. While the ACS contains margin of error (MOE) information, this dataset does not. Those individuals requiring more complete data are directed to download the more detailed datasets from the ACS American FactFinder website. This dataset is organized by Census tract boundaries in New Mexico. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program. 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. 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, 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 Bureau of the Census has released Census 2000 Summary File 1 (SF1) 100-Percent data. The file includes the following population items: sex, age, race, Hispanic or Latino origin, household relationship, and household and family characteristics. Housing items include occupancy status and tenure (whether the unit is owner or renter occupied). SF1 does not include information on incomes, poverty status, overcrowded housing or age of housing. These topics will be covered in Summary File 3. Data are available for states, counties, county subdivisions, places, census tracts, block groups, and, where applicable, American Indian and Alaskan Native Areas and Hawaiian Home Lands. The SF1 data are available on the Bureau's web site and may be retrieved from American FactFinder as tables, lists, or maps. Users may also download a set of compressed ASCII files for each state via the Bureau's FTP server. There are over 8000 data items available for each geographic area. The full listing of these data items is available here as a downloadable compressed data base file named TABLES.ZIP. The uncompressed is in FoxPro data base file (dbf) format and may be imported to ACCESS, EXCEL, and other software formats. While all of this information is useful, the Office of Community Planning and Development has downloaded selected information for all states and areas and is making this information available on the CPD web pages. The tables and data items selected are those items used in the CDBG and HOME allocation formulas plus topics most pertinent to the Comprehensive Housing Affordability Strategy (CHAS), the Consolidated Plan, and similar overall economic and community development plans. The information is contained in five compressed (zipped) dbf tables for each state. When uncompressed the tables are ready for use with FoxPro and they can be imported into ACCESS, EXCEL, and other spreadsheet, GIS and database software. The data are at the block group summary level. The first two characters of the file name are the state abbreviation. The next two letters are BG for block group. Each record is labeled with the code and name of the city and county in which it is located so that the data can be summarized to higher-level geography. The last part of the file name describes the contents . The GEO file contains standard Census Bureau geographic identifiers for each block group, such as the metropolitan area code and congressional district code. The only data included in this table is total population and total housing units. POP1 and POP2 contain selected population variables and selected housing items are in the HU file. The MA05 table data is only for use by State CDBG grantees for the reporting of the racial composition of beneficiaries of Area Benefit activities. The complete package for a state consists of the dictionary file named TABLES, and the five data files for the state. The logical record number (LOGRECNO) links the records across tables.

The Economic Census is the U.S. Government's official five-year measure of American business and the economy. It is conducted by the U.S. Census Bureau, and response is required by law. In October through December of the census year, forms are sent out to nearly 4 million businesses, including large, medium and small companies representing all U.S. locations and industries. Respondents were asked to provide a range of operational and performance data for their companies. This dataset presents company, establishments, value of shipments, value of product shipments, percentage of product shipments of the total value of shipments, and percentage of distribution of value of product shipments.

Context

This dataset expands on my earlier New York City Census Data dataset. It includes data from the entire country instead of just New York City. The expanded data will allow for much more interesting analyses and will also be much more useful at supporting other data sets.

Content

The data here are taken from the DP03 and DP05 tables of the 2015 American Community Survey 5-year estimates. The full datasets and much more can be found at the American Factfinder website. Currently, I include two data files:

1. acs2015_census_tract_data.csv: Data for each census tract in the US, including DC and Puerto Rico.
2. acs2015_county_data.csv: Data for each county or county equivalent in the US, including DC and Puerto Rico.

The two files have the same structure, with just a small difference in the name of the id column. Counties are political subdivisions, and the boundaries of some have been set for centuries. Census tracts, however, are defined by the census bureau and will have a much more consistent size. A typical census tract has around 5000 or so residents.

The Census Bureau updates the estimates approximately every year. At least some of the 2016 data is already available, so I will likely update this in the near future.

Acknowledgements

The data here were collected by the US Census Bureau. As a product of the US federal government, this is not subject to copyright within the US.

Inspiration

There are many questions that we could try to answer with the data here. Can we predict things such as the state (classification) or household income (regression)? What kinds of clusters can we find in the data? What other datasets can be improved by the addition of census data?

This dataset lists the total population 18 years and older by census block in Connecticut before and after population adjustments were made pursuant to Public Act 21-13. PA 21-13 creates a process to adjust the U.S. Census Bureau population data to allow for most individuals who are incarcerated to be counted at their address before incarceration. Prior to enactment of the act, these inmates were counted at their correctional facility address. The act requires the CT Office of Policy and Management (OPM) to prepare and publish the adjusted and unadjusted data by July 1 in the year after the U.S. census is taken or 30 days after the U.S. Census Bureau’s publication of the state’s data. A report documenting the population adjustment process was prepared by a team at OPM composed of the Criminal Justice Policy and Planning Division (OPM CJPPD) and the Data and Policy Analytics (DAPA) unit. The report is available here: https://portal.ct.gov/-/media/OPM/CJPPD/CjAbout/SAC-Documents-from-2021-2022/PA21-13_OPM_Summary_Report_20210921.pdf Note: On September 21, 2021, following the initial publication of the report, OPM and DOC revised the count of juveniles, reallocating 65 eighteen-year-old individuals who were incorrectly designated as being under age 18. After the DOC released the updated data to OPM, the report and this dataset were updated to reflect the revision.

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

Context

There are a number of Kaggle datasets that provide spatial data around New York City. For many of these, it may be quite interesting to relate the data to the demographic and economic characteristics of nearby neighborhoods. I hope this data set will allow for making these comparisons without too much difficulty.

Exploring the data and making maps could be quite interesting as well.

Content

This dataset contains two CSV files:

1. nyc_census_tracts.csv

   This file contains a selection of census data taken from the ACS DP03 and DP05 tables. Things like total population, racial/ethnic demographic information, employment and commuting characteristics, and more are contained here. There is a great deal of additional data in the raw tables retrieved from the US Census Bureau website, so I could easily add more fields if there is enough interest.

   I obtained data for individual census tracts, which typically contain several thousand residents.

2. census_block_loc.csv

   For this file, I used an online FCC census block lookup tool to retrieve the census block code for a 200 x 200 grid containing New York City and a bit of the surrounding area. This file contains the coordinates and associated census block codes along
   with the state and county names to make things a bit more readable to users.

   Each census tract is split into a number of blocks, so one must extract the census tract code from the block code.

Acknowledgements

The data here was taken from the American Community Survey 2015 5-year estimates (https://factfinder.census.gov/faces/nav/jsf/pages/index.xhtml).

The census block coordinate data was taken from the FCC Census Block Conversions API (https://www.fcc.gov/general/census-block-conversions-api)

As public data from the US government, this is not subject to copyright within the US and should be considered public domain.

Context

The United States Census is a decennial census mandated by Article I, Section 2 of the United States Constitution, which states: "Representatives and direct Taxes shall be apportioned among the several States ... according to their respective Numbers."
Source: https://en.wikipedia.org/wiki/United_States_Census

Content

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.

The United States census dataset includes nationwide population counts from the 2000 and 2010 censuses. Data is broken out by gender, age and location using zip code tabular areas (ZCTAs) and GEOIDs. ZCTAs are generalized representations of zip codes, and often, though not always, are the same as the zip code for an area. GEOIDs are numeric codes that uniquely identify all administrative, legal, and statistical geographic areas for which the Census Bureau tabulates data. GEOIDs are useful for correlating census data with other censuses and surveys.

Fork this kernel to get started.

Acknowledgements

https://bigquery.cloud.google.com/dataset/bigquery-public-data:census_bureau_usa

https://cloud.google.com/bigquery/public-data/us-census

Dataset Source: United States Census Bureau

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.

Banner Photo by Steve Richey from Unsplash.

Inspiration

What are the ten most populous zip codes in the US in the 2010 census?

What are the top 10 zip codes that experienced the greatest change in population between the 2000 and 2010 censuses?

https://cloud.google.com/bigquery/images/census-population-map.png" alt="https://cloud.google.com/bigquery/images/census-population-map.png"> https://cloud.google.com/bigquery/images/census-population-map.png

The Travel Time to Work indicator compares the mean, or average, commute time for Champaign County residents to the mean commute time for residents of Illinois and the United States as a whole. On its own, mean travel time of all commuters on all mode types could be reflective of a number of different conditions. Congestion, mode choice, changes in residential patterns, changes in the location of major employment centers, and changes in the transit network can all impact travel time in different and often conflicting ways. Since the onset of the COVID-19 pandemic in 2020, the workplace location (office vs. home) is another factor that can impact the mean travel time of an area. We don’t recommend trying to draw any conclusions about conditions in Champaign County, or anywhere else, based on mean travel time alone.

However, when combined with other indicators in the Mobility category (and other categories), mean travel time to work is a valuable measure of transportation behaviors in Champaign County.

Champaign County’s mean travel time to work is lower than the mean travel time to work in Illinois and the United States. Based on this figure, the state of Illinois has the longest commutes of the three analyzed areas.

The year-to-year fluctuations in mean travel time have been statistically significant in the United States since 2014, and in Illinois in 2021 and 2022. Champaign County’s year-to-year fluctuations in mean travel time were statistically significant from 2021 to 2022, the first time since this data first started being tracked in 2005.

Mean travel time data was sourced from the U.S. Census Bureau’s American Community Survey (ACS) 1-Year Estimates, which are released annually.

As with any datasets that are estimates rather than exact counts, it is important to take into account the margins of error (listed in the column beside each figure) when drawing conclusions from the data.

Due to the impact of the COVID-19 pandemic, instead of providing the standard 1-year data products, the Census Bureau released experimental estimates from the 1-year data in 2020. This includes a limited number of data tables for the nation, states, and the District of Columbia. The Census Bureau states that the 2020 ACS 1-year experimental tables use an experimental estimation methodology and should not be compared with other ACS data. For these reasons, and because data is not available for Champaign County, no data for 2020 is included in this Indicator.

For interested data users, the 2020 ACS 1-Year Experimental data release includes a dataset on Travel Time to Work.

Sources: U.S. Census Bureau; American Community Survey, 2023 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using data.census.gov; (16 October 2024).; U.S. Census Bureau; American Community Survey, 2022 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using data.census.gov; (10 October 2023).; U.S. Census Bureau; American Community Survey, 2021 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using data.census.gov; (17 October 2022).; U.S. Census Bureau; American Community Survey, 2019 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using data.census.gov; (29 March 2021).; U.S. Census Bureau; American Community Survey, 2018 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using data.census.gov; (29 March 2021).; U.S. Census Bureau; American Community Survey, 2017 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (13 September 2018).; U.S. Census Bureau; American Community Survey, 2016 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (14 September 2017).; U.S. Census Bureau; American Community Survey, 2015 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (19 September 2016).; U.S. Census Bureau; American Community Survey, 2014 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).; U.S. Census Bureau; American Community Survey, 2013 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).; U.S. Census Bureau; American Community Survey, 2012 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).; U.S. Census Bureau; American Community Survey, 2011 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).; U.S. Census Bureau; American Community Survey, 2010 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).; U.S. Census Bureau; American Community Survey, 2009 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).; U.S. Census Bureau; American Community Survey, 2008 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).; U.S. Census Bureau; American Community Survey, 2007 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).; U.S. Census Bureau; American Community Survey, 2006 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).; U.S. Census Bureau; American Community Survey, 2005 American Community Survey 1-Year Estimates, Table S0801; generated by CCRPC staff; using American FactFinder; (16 March 2016).

The Cape Shirreff Phocid Census (CS-PHOC) dataset is part of long-term monitoring efforts at Cape Shirreff, Livingston Island. The National Oceanic and Atmospheric Administration (NOAA) United States Antarctic Marine Living Resources Program (U.S. AMLR) and the Chilean Antarctic Institute (INACH) have conducted synoptic, weekly counts of Southern Ocean phocids hauled out on Cape Shirreff during most austral summers since 1997-98. These census data, which will continue to be collected by the U.S. AMLR program and thus updated yearly, provide a rare and valuable source of information about changes in population trends and area use by Southern Ocean phocids in a climate change hot spot. CS-PHOC is a sampling event type dataset published as open data with technical support provided by SCAR Antarctic Biodiversity Portal (biodiversity.aq) (BELSPO project RT/23/ADVANCE). This dataset is described in the paper “CS-PHOC: weekly census counts of Southern Ocean phocids at Cape Shirreff, Livingston Island” (Woodman et al., 2024). This dataset contains records of Hydrurga leptonyx, Leptonychotes weddellii, Lobodon carcinophagus, and Mirounga leonina census counts at Cape Shirreff, Livingston Island (62.47° S, 60.77° W). All census records were collected by field biologists using binoculars during field expeditions at Cape Shirreff in the austral summers from December 1997 to February 2023. The data is published as a standardized Darwin Core Archive, which contains presence, absence, sex and life stage of Southern Ocean phocids observed in each survey. This dataset is published under the license CC0 1.0. Please follow the guidelines from the SCAR Data Policy (SCAR, 2023) when using the data. A manuscript describing the CS-PHOC dataset is currently in review; if you are interested in the project or have any questions regarding this dataset, please contact us via the contact information provided in the metadata or via data-biodiversity-aq@naturalsciences.be. Issues with dataset can be reported at https://github.com/us-amlr/cs-phoc This dataset is part of the U.S. Antarctic Marine Living Resources program funded by NOAA.

The AHS is the largest, regular national housing sample survey in the United States. The U.S. Census Bureau conducts the AHS to obtain up-to-date housing statistics for the Department of Housing and Urban Development (HUD). The AHS national survey was conducted annually from 1973-1981 and biennially (every two years) since 1983. Metropolitan area surveys have been conducted annually or biennially since 1974.

PROBLEM AND OPPORTUNITY In the United States, voting is largely a private matter. A registered voter is given a randomized ballot form or machine to prevent linkage between their voting choices and their identity. This disconnect supports confidence in the election process, but it provides obstacles to an election's analysis. A common solution is to field exit polls, interviewing voters immediately after leaving their polling location. This method is rife with bias, however, and functionally limited in direct demographics data collected. For the 2020 general election, though, most states published their election results for each voting location. These publications were additionally supported by the geographical areas assigned to each location, the voting precincts. As a result, geographic processing can now be applied to project precinct election results onto Census block groups. While precinct have few demographic traits directly, their geographies have characteristics that make them projectable onto U.S. Census geographies. Both state voting precincts and U.S. Census block groups: are exclusive, and do not overlap are adjacent, fully covering their corresponding state and potentially county have roughly the same size in area, population and voter presence Analytically, a projection of local demographics does not allow conclusions about voters themselves. However, the dataset does allow statements related to the geographies that yield voting behavior. One could say, for example, that an area dominated by a particular voting pattern would have mean traits of age, race, income or household structure. The dataset that results from this programming provides voting results allocated by Census block groups. The block group identifier can be joined to Census Decennial and American Community Survey demographic estimates. DATA SOURCES The state election results and geographies have been compiled by Voting and Election Science team on Harvard's dataverse. State voting precincts lie within state and county boundaries. The Census Bureau, on the other hand, publishes its estimates across a variety of geographic definitions including a hierarchy of states, counties, census tracts and block groups. Their definitions can be found here. The geometric shapefiles for each block group are available here. The lowest level of this geography changes often and can obsolesce before the next census survey (Decennial or American Community Survey programs). The second to lowest census level, block groups, have the benefit of both granularity and stability however. The 2020 Decennial survey details US demographics into 217,740 block groups with between a few hundred and a few thousand people. Dataset Structure The dataset's columns include: Column Definition BLOCKGROUP_GEOID 12 digit primary key. Census GEOID of the block group row. This code concatenates: 2 digit state 3 digit county within state 6 digit Census Tract identifier 1 digit Census Block Group identifier within tract STATE State abbreviation, redundent with 2 digit state FIPS code above REP Votes for Republican party candidate for president DEM Votes for Democratic party candidate for president LIB Votes for Libertarian party candidate for president OTH Votes for presidential candidates other than Republican, Democratic or Libertarian AREA square kilometers of area associated with this block group GAP total area of the block group, net of area attributed to voting precincts PRECINCTS Number of voting precincts that intersect this block group ASSUMPTIONS, NOTES AND CONCERNS: Votes are attributed based upon the proportion of the precinct's area that intersects the corresponding block group. Alternative methods are left to the analyst's initiative. 50 states and the District of Columbia are in scope as those U.S. possessions voting in the general election for the U.S. Presidency. Three states did not report their results at the precinct level: South Dakota, Kentucky and West Virginia. A dummy block group is added for each of these states to maintain national totals. These states represent 2.1% of all votes cast. Counties are commonly coded using FIPS codes. However, each election result file may have the county field named differently. Also, three states do not share county definitions - Delaware, Massachusetts, Alaska and the District of Columbia. Block groups may be used to capture geographies that do not have population like bodies of water. As a result, block groups without intersection voting precincts are not uncommon. In the U.S., elections are administered at a state level with the Federal Elections Commission compiling state totals against the Electoral College weights. The states have liberty, though, to define and change their own voting precincts https://en.wikipedia.org/wiki/Electoral_precinct. The Census Bureau practices "data suppression", filtering some block groups from demographic publication because they do not meet a population threshold. This practice...

About this dataset

Context

The dataset tabulates the population of Bothell by gender, including both male and female populations. This dataset can be utilized to understand the population distribution of Bothell across both sexes and to determine which sex constitutes the majority.

Key observations

There is a slight majority of female population, with 50.62% of total population being female. 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.

Scope of gender :

Please note that American Community Survey asks a question about the respondents current sex, but not about gender, sexual orientation, or sex at birth. The question is intended to capture data for biological sex, not gender. Respondents are supposed to respond with the answer as either of Male or Female. Our research and this dataset mirrors the data reported as Male and Female for gender distribution analysis. No further analysis is done on the data reported from the Census Bureau.

Variables / Data Columns

• Gender: This column displays the Gender (Male / Female)
• Population: The population of the gender in the Bothell is shown in this column.
• % of Total Population: This column displays the percentage distribution of each gender as a proportion of Bothell 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 Bothell Population by Race & Ethnicity. You can refer the same here

About this dataset

Context

The dataset tabulates the population of Mcclusky by gender, including both male and female populations. This dataset can be utilized to understand the population distribution of Mcclusky across both sexes and to determine which sex constitutes the majority.

Key observations

There is a slight majority of female population, with 52.31% of total population being female. 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.

Scope of gender :

Please note that American Community Survey asks a question about the respondents current sex, but not about gender, sexual orientation, or sex at birth. The question is intended to capture data for biological sex, not gender. Respondents are supposed to respond with the answer as either of Male or Female. Our research and this dataset mirrors the data reported as Male and Female for gender distribution analysis. No further analysis is done on the data reported from the Census Bureau.

Variables / Data Columns

• Gender: This column displays the Gender (Male / Female)
• Population: The population of the gender in the Mcclusky is shown in this column.
• % of Total Population: This column displays the percentage distribution of each gender as a proportion of Mcclusky 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 Mcclusky Population by Race & Ethnicity. You can refer the same here

VITAL SIGNS INDICATOR Displacement Risk (EQ3)

FULL MEASURE NAME Share of lower-income households living in tracts at risk of displacement

LAST UPDATED December 2018

DESCRIPTION Displacement risk refers to the share of lower-income households living in neighborhoods that have been losing lower-income residents over time, thus earning the designation “at risk”. While “at risk” households may not necessarily be displaced in the short-term or long-term, neighborhoods identified as being “at risk” signify pressure as reflected by the decline in lower-income households (who are presumed to relocate to other more affordable communities). The dataset includes metropolitan area, regional, county and census tract tables.

DATA SOURCE U.S. Census Bureau: Decennial Census 1980-1990 Form STF3 https://nhgis.org

U.S. Census Bureau: Decennial Census 2000 Form SF3a https://nhgis.org

U.S. Census Bureau: Decennial Census 1980-2010 Longitudinal Tract Database http://www.s4.brown.edu/us2010/index.htm

U.S. Census Bureau: American Community Survey 2010-2015 Form S1901 5-year rolling average http://factfinder2.census.gov

U.S. Census Bureau: American Community Survey 2010-2017 Form B19013 5-year rolling average http://factfinder2.census.gov

CONTACT INFORMATION vitalsigns.info@bayareametro.gov

METHODOLOGY NOTES (across all datasets for this indicator) Aligning with the approach used for Plan Bay Area 2040, displacement risk is calculated by comparing the analysis year with the most recent year prior to identify census tracts that are losing lower-income households. Historical data is pulled from U.S. Census datasets and aligned with today’s census tract boundaries using crosswalk tables provided by LTDB. Tract data, as well as regional income data, are calculated using 5-year rolling averages for consistency – given that tract data is only available on a 5-year basis. Using household tables by income level, the number of households in each tract falling below the median are summed, which involves summing all brackets below the regional median and then summing a fractional share of the bracket that includes the regional median (assuming a simple linear distribution within that bracket).

Once all tracts in a given county or metro area are synced to today’s boundaries, the analysis identifies census tracts of greater than 500 lower-income people (in the prior year) to filter out low-population areas. For those tracts, any net loss between the prior year and the analysis year results in that tract being flagged as being at risk of displacement, and all lower-income households in that tract are flagged. To calculate the share of households at risk, the number of lower-income households living in flagged tracts are summed and divided by the total number of lower-income households living in the larger geography (county or metro). Minor deviations on a year-to-year basis should be taken in context, given that data on the tract level often fluctuates and has a significant margin of error; changes on the county and regional level are more appropriate to consider on an annual basis instead.

VITAL SIGNS INDICATOR Displacement Risk (EQ3)

FULL MEASURE NAME Share of lower-income households living in tracts at risk of displacement

LAST UPDATED December 2018

DESCRIPTION Displacement risk refers to the share of lower-income households living in neighborhoods that have been losing lower-income residents over time, thus earning the designation “at risk”. While “at risk” households may not necessarily be displaced in the short-term or long-term, neighborhoods identified as being “at risk” signify pressure as reflected by the decline in lower-income households (who are presumed to relocate to other more affordable communities). The dataset includes metropolitan area, regional, county and census tract tables.

DATA SOURCE U.S. Census Bureau: Decennial Census 1980-1990 Form STF3 https://nhgis.org

U.S. Census Bureau: Decennial Census 2000 Form SF3a https://nhgis.org

U.S. Census Bureau: Decennial Census 1980-2010 Longitudinal Tract Database http://www.s4.brown.edu/us2010/index.htm

U.S. Census Bureau: American Community Survey 2010-2015 Form S1901 5-year rolling average http://factfinder2.census.gov

U.S. Census Bureau: American Community Survey 2010-2017 Form B19013 5-year rolling average http://factfinder2.census.gov

CONTACT INFORMATION vitalsigns.info@bayareametro.gov

METHODOLOGY NOTES (across all datasets for this indicator) Aligning with the approach used for Plan Bay Area 2040, displacement risk is calculated by comparing the analysis year with the most recent year prior to identify census tracts that are losing lower-income households. Historical data is pulled from U.S. Census datasets and aligned with today’s census tract boundaries using crosswalk tables provided by LTDB. Tract data, as well as regional income data, are calculated using 5-year rolling averages for consistency – given that tract data is only available on a 5-year basis. Using household tables by income level, the number of households in each tract falling below the median are summed, which involves summing all brackets below the regional median and then summing a fractional share of the bracket that includes the regional median (assuming a simple linear distribution within that bracket).

Once all tracts in a given county or metro area are synced to today’s boundaries, the analysis identifies census tracts of greater than 500 lower-income people (in the prior year) to filter out low-population areas. For those tracts, any net loss between the prior year and the analysis year results in that tract being flagged as being at risk of displacement, and all lower-income households in that tract are flagged. To calculate the share of households at risk, the number of lower-income households living in flagged tracts are summed and divided by the total number of lower-income households living in the larger geography (county or metro). Minor deviations on a year-to-year basis should be taken in context, given that data on the tract level often fluctuates and has a significant margin of error; changes on the county and regional level are more appropriate to consider on an annual basis instead.

The South Shetland Antarctic fur seal pup census dataset is part of long-term monitoring efforts in the South Shetland Islands archipelago (SSI), based at Cape Shirreff, Livingston Island. These efforts, which include conducting annual synoptic census counts of South Shetland Antarctic fur seals (SSAFS) throughout the region, have been primarily carried out by the Chilean Antarctic Institute (INACH) and the National Oceanic and Atmospheric Administration (NOAA) United States Antarctic Marine Living Resources Program (U.S. AMLR). These census data will continue to be collected by the U.S. AMLR program, and updated yearly. Recent studies have demonstrated Antarctic fur seals (Arctocephalus gazella) are composed of at least four distinct subpopulations (Bonin et al. 2013, Paijmans et al. 2020), including one breeding throughout the SSI. These SSAFS are the highest latitude population of otariids in the world. As such, this subpopulation faces a unique array of environmental and ecological challenges, harbors a disproportionately large reservoir of genetic diversity for the species, and has experienced catastrophic population decline between 2008 and 2023 (Krause et al. 2023 and references therein). Therefore, ensuring access to accurate and updated population data for SSAFS is particularly important for managers and decision makers. Due to regular absences by foraging females throughout the breeding season, and the irregular haul out patterns of males and subadults, the most informative measure of fur seal population size is to annually count pups (Payne, 1979; Bengtson et al., 1990). This dataset consists of all known total synoptic Antarctic fur seal pup counts (i.e., live and dead pups) from the SSI during the austral summers since 1959. Counts from the subset breeding colonies at Cape Shirreff (CS, reported with standard deviation (±SD) where available) and the San Telmo Islets (STI) are also included. Data were collected by the U.S. AMLR Program, unless otherwise indicated. Most of these annual census counts were conducted during the optimal biological window (late December and early January) when the vast majority of pups are born, but have not yet been subject to substantial mortality (Krause et al. 2022). The authors are confident that all counts included in this dataset are comparable and representative of South Shetland Antarctic fur seal population trends. However, census dates, or at least best estimates of the census date, are included for all records for any parties wishing to apply correction factors. The data are published as a standardized Darwin Core Archive, which contains count data for SSAFS pups from the specified locations during the specified seasons. This dataset is published under the license CC0. Please follow the guidelines from the SCAR Data Policy (SCAR, 2023) when using the data. If you have any questions regarding this dataset, please contact us via the contact information provided in the metadata or via data-biodiversity-aq@naturalsciences.be. Issues with the dataset can be reported at https://github.com/us-amlr/ssafs-pup-census. This dataset is maintained by the U.S. Antarctic Marine Living Resources Program, funded by NOAA.