Selected demographic, social, economic, and housing estimates data by community district/PUMA (Public Use Micro Data Sample Area). Three year estimates of population data from the Census Bureau's American Community Survey

Analysis of ‘Housing Database by PUMA’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/92b1001f-5c85-4a75-8b2d-ce9e5957b1fa on 13 February 2022.

--- Dataset description provided by original source is as follows ---

Net change in housing units arising from new buildings, demolitions, or alterations for NYC PUMAs since 2010. The NYC Department of City Planning’s (DCP) Housing Database provide the 2010 census count of housing units, the net change in Class A housing units since the census, and the count of units pending completion for commonly used political and statistical boundaries. These tables are aggregated from the DCP Housing Database, which is derived from Department of Buildings (DOB)-approved housing construction and demolition jobs filed or completed in NYC since January 1, 2010. Net housing unit change is calculated as the sum of all three construction job types that add or remove residential units: new buildings, major alterations, and demolitions, and can be used to determine the change in legal housing units across time and space.

All previously released versions of this data are available at a BYTES of the BIG APPLE- Archive

--- Original source retains full ownership of the source dataset ---

Four tables of ACS demographic profiles for 2012 to 2016 at the PUMA level. Four profiles include demographics, economic, housing and sociological. Column headers in this database are abbreviated. Please see the data dictionary (shown in worksheet entitled “Dictionary”) for an explanation of these abbreviated headers.

The NYC Department of City Planning’s (DCP) Housing Database Aggregate Tables provide the 2010 census count of housing units, the net change in Class A housing units since the census, and the count of units pending completion for commonly used political and statistical boundaries. These tables are aggregated from the DCP Housing Database, which is derived from Department of Buildings (DOB)-approved housing construction and demolition jobs filed or completed in NYC since January 1, 2010. Net housing unit change is calculated as the sum of all three construction job types that add or remove residential units: new buildings, major alterations, and demolitions, and can be used to determine the change in legal housing units across time and space.

The American Community Survey (ACS) Public Use Microdata Sample (PUMS) contains a sample of responses to the ACS. The ACS PUMS dataset includes variables for nearly every question on the survey, as well as many new variables that were derived after the fact from multiple survey responses (such as poverty status).Each record in the file represents a single person, or, in the household-level dataset, a single housing unit. In the person-level file, individuals are organized into households, making possible the study of people within the contexts of their families and other household members. Individuals living in Group Quarters, such as nursing facilities or college facilities, are also included on the person file. ACS PUMS data are available at the nation, state, and Public Use Microdata Area (PUMA) levels. PUMAs are special non-overlapping areas that partition each state into contiguous geographic units containing roughly 100,000 people each. ACS PUMS files for an individual year, such as 2020, contain data on approximately one percent of the United States population

The American Community Survey (ACS) Public Use Microdata Sample (PUMS) contains a sample of responses to the ACS. The ACS PUMS dataset includes variables for nearly every question on the survey, as well as many new variables that were derived after the fact from multiple survey responses (such as poverty status).Each record in the file represents a single person, or, in the household-level dataset, a single housing unit. In the person-level file, individuals are organized into households, making possible the study of people within the contexts of their families and other household members. Individuals living in Group Quarters, such as nursing facilities or college facilities, are also included on the person file. ACS PUMS data are available at the nation, state, and Public Use Microdata Area (PUMA) levels. PUMAs are special non-overlapping areas that partition each state into contiguous geographic units containing roughly 100,000 people each. ACS PUMS files for an individual year, such as 2019, contain data on approximately one percent of the United States population.

Abstract (en): The Public Use Microdata Sample (PUMS) 1-Percent Sample contains household and person records for a sample of housing units that received the "long form" of the 1990 Census questionnaire. Data items include the full range of population and housing information collected in the 1990 Census, including 500 occupation categories, age by single years up to 90, and wages in dollars up to $140,000. Each person identified in the sample has an associated household record, containing information on household characteristics such as type of household and family income. All persons and housing units in the United States. A stratified sample, consisting of a subsample of the household units that received the 1990 Census "long-form" questionnaire (approximately 15.9 percent of all housing units). 2006-01-12 All files were removed from dataset 85 and flagged as study-level files, so that they will accompany all downloads.2006-01-12 All files were removed from dataset 83 and flagged as study-level files, so that they will accompany all downloads.2006-01-12 All files were removed from dataset 82 and flagged as study-level files, so that they will accompany all downloads.2006-01-12 All files were removed from dataset 81 and flagged as study-level files, so that they will accompany all downloads.2006-01-12 All files were removed from dataset 80 and flagged as study-level files, so that they will accompany all downloads.1998-08-28 The following data files were replaced by the Census Bureau: the state files (Parts 1-56), Puerto Rico (Part 72), Geographic Equivalency File (Part 84), and Public Use Microdata Areas (PUMAS) Crossing State Lines (Part 99). These files now incorporate revised group quarters data. Parts 201-256, which were separate revised group quarters files for each state, have been removed from the collection. The data fields affected by the group quarters data revisions were POWSTATE, POWPUMA, MIGSTATE and MIGPUMA. As a result of the revisions, the Maine file (Part 23) gained 763 records and Part 99 lost 763 records. In addition, the following files have been added to the collection: Ancestry Code List, Place of Birth Code List, Industry Code List, Language Code List, Occupation Code List, and Race Code List (Parts 86-91). Also, the codebook is now available as a PDF file. (1) Although all records are 231 characters in length, each file is hierarchical in structure, containing a housing unit record followed by a variable number of person records. Both record types contain approximately 120 variables. Two improvements over the 1980 PUMS files have been incorporated. First, the housing unit serial number is identified on both the housing unit record and on the person record, allowing the file to be processed as a rectangular file. In addition, each person record is assigned an individual weight, allowing users to more closely approximate published reports. Unlike previous years, the 1990 PUMS 1-Percent and 5-Percent Samples have not been released in separate geographic series (known as "A," "B," etc. records). Instead, each sample has its own set of geographies, known as "Public Use Microdata Areas" (PUMAs), established by the Census Bureau with assistance from each State Data Center. The PUMAs in the 1-Percent Sample are based on a distinction between metropolitan and nonmetropolitan areas. Metropolitan areas encompass whole central cities, Primary Metropolitan Statistical Areas (PMSAs), Metropolitan Statistical Areas (MSAs), or groups thereof, except where the city or metropolitan area contains more than 200,000 inhabitants. In that case, the city or metropolitan area is divided into several PUMAs. Nonmetropolitan PUMAs are based on areas or groups of areas outside the central city, PMSA, or MSA. PUMAs in this 1-Percent Sample may cross state lines. (2) The codebook is provided as a Portable Document Format (PDF) file. The PDF file format was developed by Adobe Systems Incorporated and can be accessed using PDF reader software, such as the Adobe Acrobat Reader. Information on how to obtain a copy of the Acrobat Reader is provided through the ICPSR Website on the Internet.

PUMA data Gross rent as % of House Hold Income (30% or more)

The Public Use Microdata Sample (PUMS) for Puerto Rico (PR) contains a sample of responses to the Puerto Rico Community Survey (PRCS). The PRCS is similar to, but separate from, the American Community Survey (ACS). The PRCS collects data about the population and housing units in Puerto Rico. Puerto Rico data is not included in the national PUMS files. It is published as a state equivalent file and has a State FIPS code of “72”. The file includes variables for nearly every question on the survey, as well as many new variables that were derived after the fact from multiple survey responses (such as poverty status). Each record in the file represents a single person, or, in the household-level dataset, a single housing unit. In the person-level file, individuals are organized into households, making possible the study of people within the contexts of their families and other household members. Individuals living in Group Quarters, such as nursing facilities or college facilities, are also included on the person file. Data are available at the state and Public Use Microdata Area (PUMA) levels. PUMAs are special non-overlapping areas that partition Puerto Rico into contiguous geographic units containing roughly 100,000 people each. The Puerto Rico PUMS file for an individual year, such as 2019, contain data on approximately one percent of the Puerto Rico population.

The Public Use Microdata Sample (PUMS) for Puerto Rico (PR) contains a sample of responses to the Puerto Rico Community Survey (PRCS). The PRCS is similar to, but separate from, the American Community Survey (ACS). The PRCS collects data about the population and housing units in Puerto Rico. Puerto Rico data is not included in the national PUMS files. It is published as a state equivalent file and has a State FIPS code of "72". The file includes variables for nearly every question on the survey, as well as many new variables that were derived after the fact from multiple survey responses (such as poverty status). Each record in the file represents a single person, or, in the household-level dataset, a single housing unit. In the person-level file, individuals are organized into households, making possible the study of people within the contexts of their families and other household members. Individuals living in Group Quarters, such as nursing facilities or college facilities, are also included on the person file. Data are available at the state and Public Use Microdata Area (PUMA) levels. PUMAs are special non-overlapping areas that partition Puerto Rico into contiguous geographic units containing roughly 100,000 people each. The Puerto Rico PUMS file for an individual year, such as 2020, contain data on approximately one percent of the Puerto Rico population.

The American Community Survey (ACS) Public Use Microdata Sample (PUMS) contains a sample of responses to the ACS. The ACS PUMS dataset includes variables for nearly every question on the survey, as well as many new variables that were derived after the fact from multiple survey responses (such as poverty status).Each record in the file represents a single person, or, in the household-level dataset, a single housing unit. In the person-level file, individuals are organized into households, making possible the study of people within the contexts of their families and other household members. Individuals living in Group Quarters, such as nursing facilities or college facilities, are also included on the person file. ACS PUMS data are available at the nation, state, and Public Use Microdata Area (PUMA) levels. PUMAs are special non-overlapping areas that partition each state into contiguous geographic units containing roughly 100,000 people each. ACS PUMS files for an individual year, such as 2020, contain data on approximately one percent of the United States population

The Public Use Microdata Sample (PUMS) for Puerto Rico (PR) contains a sample of responses to the Puerto Rico Community Survey (PRCS). The PRCS is similar to, but separate from, the American Community Survey (ACS). The PRCS collects data about the population and housing units in Puerto Rico. Puerto Rico data is not included in the national PUMS files. It is published as a state equivalent file and has a State FIPS code of "72". The file includes variables for nearly every question on the survey, as well as many new variables that were derived after the fact from multiple survey responses (such as poverty status). Each record in the file represents a single person, or, in the household-level dataset, a single housing unit. In the person-level file, individuals are organized into households, making possible the study of people within the contexts of their families and other household members. Individuals living in Group Quarters, such as nursing facilities or college facilities, are also included on the person file. Data are available at the state and Public Use Microdata Area (PUMA) levels. PUMAs are special non-overlapping areas that partition Puerto Rico into contiguous geographic units containing roughly 100,000 people each. The Puerto Rico PUMS file for an individual year, such as 2021, contain data on approximately one percent of the Puerto Rico population.

US Census American Community Survey (ACS) 2020, 5-year estimates of the key housing characteristics of Public Use Microdata Areas (PUMA) geographic level in Orange County, California. The data contains 406 fields for the variable groups H01: Housing occupancy (universe: total housing units, table X25, 3 fields); H02: Units in structure (universe: total housing units, table X25, 11 fields); H03: Population in occupied housing units by tenure by units in structure (universe: total population in occupied housing units, table X25, 13 fields); H04: Year structure built (universe: total housing units, table X25, 15 fields); H05: Rooms (universe: total housing units, table X25, 18 fields); H06: Bedrooms (universe: total housing units, table X25, 21 fields); H07: Housing tenure by race of householder (universe: occupied housing units, table X25, 51 fields); H08: Total population in occupied housing units by tenure (universe: total population in occupied housing units, table X25, 3 fields); H09: Vacancy status (universe: vacant housing units, table X25, 8 fields); H10: Occupied housing units by race of householder (universe: occupied housing units, table X25, 8 fields); H11: Year householder moved into unit (universe: occupied housing units, table X25, 18 fields); H12: Vehicles available (universe: occupied housing units, table X25, 18 fields); H13: Housing heating fuel (universe: occupied housing units, table X25, 10 fields); H14: Selected housing characteristics (universe: occupied housing units, table X25, 9 fields); H15: Occupants per room (universe: occupied housing units, table X25, 13 fields); H16: Housing value (universe: owner-occupied units, table X25, 32 fields); H17: Price asked for vacant for sale only, and sold not occupied housing units (universe: vacant for sale only, and sold not occupied housing units, table X25, 28 fields); H18: Mortgage status (universe: owner-occupied units, table X25, 10 fields); H19: Selected monthly owner costs, SMOC (universe: owner-occupied housing units with or without a mortgage, table X25, 45 fields); H20: Selected monthly owner costs as a percentage of household income, SMOCAPI (universe: owner-occupied housing units with or without a mortgage, table X25, 26 fields); H21: Contract rent distribution and rent asked distribution in dollars (universe: renter-occupied housing units paying cash rent and vacant, for rent, and rented not occupied housing units, table X25, 7 fields); H22: Gross rent (universe: occupied units paying rent, table X25, 28 fields), and; X23: Gross rent as percentage of household income (universe: occupied units paying rent, table X25, 11 fields). The US Census geodemographic data are based on the 2020 TigerLines across multiple geographies. The spatial geographies were merged with ACS data tables. See full documentation at the OCACS project GitHub page (https://github.com/ktalexan/OCACS-Geodemographics).

Animals’ fear of people is widespread across taxa and can mitigate the risk of human-induced mortality, facilitating coexistence in human-dominated landscapes. However, humans can be unpredictable predators and anthropogenic cues that animals perceive may not be reliable indicators of the risk of being killed. In these cases, animal fear responses may be ineffective and may even exacerbate the risk of anthropogenic mortality. Here, we explore these questions using a 10-year dataset of movement and mortality events for the puma (Puma concolor) population in the fragmented Santa Cruz Mountains of California, for whom the leading cause of death was retaliatory killings by people following livestock loss. We modeled retaliatory killing risk and puma habitat selection relative to residential housing density to evaluate whether puma avoidance of human cues reflected their risk of being killed. We documented a mismatch between human cues, fear responses, and actual risk. Rather than scaling directly with housing density, retaliatory killings occurred at intermediate levels of human development and at night. Pumas avoided these areas during the day but selected for these high-risk areas at night, resulting in a mismatch between cue and risk impacting 17% of the study area. These results are unlikely to be driven by puma hunting behavior: livestock constitute a very small proportion of puma diets, and we found no evidence for the alternative hypothesis that state-dependent foraging drove depredation of livestock and subsequent retaliatory killings. Our findings indicate that puma responses to human cues are not sufficient to enable human-carnivore coexistence in this area and suggest that reducing risk from humans in places with few perceptible human cues would facilitate carnivore conservation in human-dominated landscapes. Furthermore, a mismatch between human cues and responses by carnivores can lead to selection rather than avoidance of risky areas, which could result in an ecological trap. Methods We captured adult and subadult pumas from 2009-2019 and fit pumas with GPS collars set to record a GPS location every 4 hours. For animals that died during the study, we recorded date, location, and cause of death. We 1) modeled overall and cause-specific mortality rates using the Kaplan-Meier procedure and non-parametric cumulative incidence functions, 2) modeled habitat selection using step selection functions, 3) modeled spatial predictors of the distribution of sites where retaliatory killings occurred, and 4) compared time since last predicted deer kill and body weights between animals killed after depredating livestock and the overall puma population. Included in this data product are the time-to-event data (tte_cause.csv) for analysis 1, covariate information for 4-hour puma locations (ssf_data.csv) for analysis 2, covariate information for locations of retaliatory killings (rk_rsf_data.csv) and other sources of mortality (other_mort_rsf_data.csv) for analysis 3, body weight data (body_weight_data.csv) and kill rate data (times_since_last_kill.csv and kill_rates.csv) for analysis 4. Please see Nisi AC, Benson JF, Wilmers CC. 2022. Puma responses to unreliable human cues suggest an ecological trap in a fragmented landscape. Oikos: 10.1111/oik.09051 for a full description of data collection methods, and the README file for detailed descriptions of each dataset.

The American Community Survey (ACS) Public Use Microdata Sample (PUMS) contains a sample of responses to the ACS. The ACS PUMS dataset includes variables for nearly every question on the survey, as well as many new variables that were derived after the fact from multiple survey responses (such as poverty status). Each record in the file represents a single person, or, in the household-level dataset, a single housing unit. In the person-level file, individuals are organized into households, making possible the study of people within the contexts of their families and other household members. Individuals living in Group Quarters, such as nursing facilities or college facilities, are also included on the person file. ACS PUMS data are available at the nation, state, and Public Use Microdata Area (PUMA) levels. PUMAs are special non-overlapping areas that partition each state into contiguous geographic units containing roughly 100,000 people each. ACS PUMS files for an individual year, such as 2022, contain data on approximately one percent of the United States population.

The American Community Survey (ACS) Public Use Microdata Sample (PUMS) contains a sample of responses to the ACS. The ACS PUMS dataset includes variables for nearly every question on the survey, as well as many new variables that were derived after the fact from multiple survey responses (such as poverty status). Each record in the file represents a single person, or, in the household-level dataset, a single housing unit. In the person-level file, individuals are organized into households, making possible the study of people within the contexts of their families and other household members. Individuals living in Group Quarters, such as nursing facilities or college facilities, are also included on the person file. ACS PUMS data are available at the nation, state, and Public Use Microdata Area (PUMA) levels. PUMAs are special non-overlapping areas that partition each state into contiguous geographic units containing roughly 100,000 people each. ACS PUMS files for an individual year, such as 2020, contain data on approximately one percent of the United States population.

The Public Use Microdata Sample (PUMS) for Puerto Rico (PR) contains a sample of responses to the Puerto Rico Community Survey (PRCS). The PRCS is similar to, but separate from, the American Community Survey (ACS). The PRCS collects data about the population and housing units in Puerto Rico. Puerto Rico data is not included in the national PUMS files. It is published as a state equivalent file and has a State FIPS code of "72". The file includes variables for nearly every question on the survey, as well as many new variables that were derived after the fact from multiple survey responses (such as poverty status). Each record in the file represents a single person, or, in the household-level dataset, a single housing unit. In the person-level file, individuals are organized into households, making possible the study of people within the contexts of their families and other household members. Individuals living in Group Quarters, such as nursing facilities or college facilities, are also included on the person file. Data are available at the state and Public Use Microdata Area (PUMA) levels. PUMAs are special non-overlapping areas that partition Puerto Rico into contiguous geographic units containing roughly 100,000 people each. The Puerto Rico PUMS file for an individual year, such as 2020, contain data on approximately one percent of the Puerto Rico population.

US Census American Community Survey (ACS) 2017, 5-year estimates of the key housing characteristics of Public Use Microdata Areas (PUMA) geographic level in Orange County, California. The data contains 406 fields for the variable groups H01: Housing occupancy (universe: total housing units, table X25, 3 fields); H02: Units in structure (universe: total housing units, table X25, 11 fields); H03: Population in occupied housing units by tenure by units in structure (universe: total population in occupied housing units, table X25, 13 fields); H04: Year structure built (universe: total housing units, table X25, 15 fields); H05: Rooms (universe: total housing units, table X25, 18 fields); H06: Bedrooms (universe: total housing units, table X25, 21 fields); H07: Housing tenure by race of householder (universe: occupied housing units, table X25, 51 fields); H08: Total population in occupied housing units by tenure (universe: total population in occupied housing units, table X25, 3 fields); H09: Vacancy status (universe: vacant housing units, table X25, 8 fields); H10: Occupied housing units by race of householder (universe: occupied housing units, table X25, 8 fields); H11: Year householder moved into unit (universe: occupied housing units, table X25, 18 fields); H12: Vehicles available (universe: occupied housing units, table X25, 18 fields); H13: Housing heating fuel (universe: occupied housing units, table X25, 10 fields); H14: Selected housing characteristics (universe: occupied housing units, table X25, 9 fields); H15: Occupants per room (universe: occupied housing units, table X25, 13 fields); H16: Housing value (universe: owner-occupied units, table X25, 32 fields); H17: Price asked for vacant for sale only, and sold not occupied housing units (universe: vacant for sale only, and sold not occupied housing units, table X25, 28 fields); H18: Mortgage status (universe: owner-occupied units, table X25, 10 fields); H19: Selected monthly owner costs, SMOC (universe: owner-occupied housing units with or without a mortgage, table X25, 45 fields); H20: Selected monthly owner costs as a percentage of household income, SMOCAPI (universe: owner-occupied housing units with or without a mortgage, table X25, 26 fields); H21: Contract rent distribution and rent asked distribution in dollars (universe: renter-occupied housing units paying cash rent and vacant, for rent, and rented not occupied housing units, table X25, 7 fields); H22: Gross rent (universe: occupied units paying rent, table X25, 28 fields), and; X23: Gross rent as percentage of household income (universe: occupied units paying rent, table X25, 11 fields). The US Census geodemographic data are based on the 2017 TigerLines across multiple geographies. The spatial geographies were merged with ACS data tables. See full documentation at the OCACS project github page (https://github.com/ktalexan/OCACS-Geodemographics).

This data set contains estimates of the percentage smoke detector utilization at the Census Tract level for the United States. Development of this data set is described in NIST TN 2020 (see references below). The zip file contains the data in shapefile format. Each record is a single census tract (using the 2013 Tiger files for census tracts) with associated data. Fields contained in the data set are: geoid: Geographic ID of the census tract. Format is '14000USXXYYYZZZZZZ', where XX is the FIPS code for the state, YYY is the FIPS code for the county, and ZZZZZZ is the census tract number. This field serves as a unique ID for the dataset. state: FIPS code for the state. county: FIPS code for the county. tract: Tract number. smsa: Standard Metropolitan Statistical Area as used in the American Housing Survey. PUMA: Public Use Microdata Area ID. region: Census region. dtctrs: Estimated fraction of households in the census tract with smoke detectors installed.

US Census American Community Survey (ACS) 2018, 5-year estimates of the key housing characteristics of Public Use Microdata Areas (PUMA) geographic level in Orange County, California. The data contains 406 fields for the variable groups H01: Housing occupancy (universe: total housing units, table X25, 3 fields); H02: Units in structure (universe: total housing units, table X25, 11 fields); H03: Population in occupied housing units by tenure by units in structure (universe: total population in occupied housing units, table X25, 13 fields); H04: Year structure built (universe: total housing units, table X25, 15 fields); H05: Rooms (universe: total housing units, table X25, 18 fields); H06: Bedrooms (universe: total housing units, table X25, 21 fields); H07: Housing tenure by race of householder (universe: occupied housing units, table X25, 51 fields); H08: Total population in occupied housing units by tenure (universe: total population in occupied housing units, table X25, 3 fields); H09: Vacancy status (universe: vacant housing units, table X25, 8 fields); H10: Occupied housing units by race of householder (universe: occupied housing units, table X25, 8 fields); H11: Year householder moved into unit (universe: occupied housing units, table X25, 18 fields); H12: Vehicles available (universe: occupied housing units, table X25, 18 fields); H13: Housing heating fuel (universe: occupied housing units, table X25, 10 fields); H14: Selected housing characteristics (universe: occupied housing units, table X25, 9 fields); H15: Occupants per room (universe: occupied housing units, table X25, 13 fields); H16: Housing value (universe: owner-occupied units, table X25, 32 fields); H17: Price asked for vacant for sale only, and sold not occupied housing units (universe: vacant for sale only, and sold not occupied housing units, table X25, 28 fields); H18: Mortgage status (universe: owner-occupied units, table X25, 10 fields); H19: Selected monthly owner costs, SMOC (universe: owner-occupied housing units with or without a mortgage, table X25, 45 fields); H20: Selected monthly owner costs as a percentage of household income, SMOCAPI (universe: owner-occupied housing units with or without a mortgage, table X25, 26 fields); H21: Contract rent distribution and rent asked distribution in dollars (universe: renter-occupied housing units paying cash rent and vacant, for rent, and rented not occupied housing units, table X25, 7 fields); H22: Gross rent (universe: occupied units paying rent, table X25, 28 fields), and; X23: Gross rent as percentage of household income (universe: occupied units paying rent, table X25, 11 fields). The US Census geodemographic data are based on the 2018 TigerLines across multiple geographies. The spatial geographies were merged with ACS data tables. See full documentation at the OCACS project github page (https://github.com/ktalexan/OCACS-Geodemographics).