In 2023, Washington, D.C. had the highest population density in the United States, with 11,130.69 people per square mile. As a whole, there were about 94.83 residents per square mile in the U.S., and Alaska was the state with the lowest population density, with 1.29 residents per square mile. The problem of population density Simply put, population density is the population of a country divided by the area of the country. While this can be an interesting measure of how many people live in a country and how large the country is, it does not account for the degree of urbanization, or the share of people who live in urban centers. For example, Russia is the largest country in the world and has a comparatively low population, so its population density is very low. However, much of the country is uninhabited, so cities in Russia are much more densely populated than the rest of the country. Urbanization in the United States While the United States is not very densely populated compared to other countries, its population density has increased significantly over the past few decades. The degree of urbanization has also increased, and well over half of the population lives in urban centers.

This map shows population density of the United States. Areas in darker magenta have much higher population per square mile than areas in orange or yellow. Data is from the U.S. Census Bureau’s 2020 Census Demographic and Housing Characteristics. The map's layers contain total population counts by sex, age, and race groups for Nation, State, County, Census Tract, and Block Group in the United States and Puerto Rico. From the Census:"Population density allows for broad comparison of settlement intensity across geographic areas. In the U.S., population density is typically expressed as the number of people per square mile of land area. The U.S. value is calculated by dividing the total U.S. population (316 million in 2013) by the total U.S. land area (3.5 million square miles).When comparing population density values for different geographic areas, then, it is helpful to keep in mind that the values are most useful for small areas, such as neighborhoods. For larger areas (especially at the state or country scale), overall population density values are less likely to provide a meaningful measure of the density levels at which people actually live, but can be useful for comparing settlement intensity across geographies of similar scale." SourceAbout the dataYou can use this map as is and you can also modify it to use other attributes included in its layers. This map's layers contain total population counts by sex, age, and race groups data from the 2020 Census Demographic and Housing Characteristics. This is shown by Nation, State, County, Census Tract, Block Group boundaries. Each geography layer contains a common set of Census counts based on available attributes from the U.S. Census Bureau. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis.Vintage of boundaries and attributes: 2020 Demographic and Housing Characteristics Table(s): P1, H1, H3, P2, P3, P5, P12, P13, P17, PCT12 (Not all lines of these DHC tables are available in this feature layer.)Data downloaded from: U.S. Census Bureau’s data.census.gov siteDate the Data was Downloaded: May 25, 2023Geography Levels included: Nation, State, County, Census Tract, Block GroupNational Figures: included in Nation layer The United States Census Bureau Demographic and Housing Characteristics: 2020 Census Results 2020 Census Data Quality Geography & 2020 Census Technical Documentation Data Table Guide: includes the final list of tables, lowest level of geography by table and table shells for the Demographic Profile and Demographic and Housing Characteristics.News & Updates This map is ready to be used in ArcGIS Pro, ArcGIS Online and its configurable apps, Story Maps, dashboards, Notebooks, Python, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the U.S. Census Bureau when using this data. Data Processing Notes: These 2020 Census boundaries come from the US Census TIGER geodatabases. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For Census tracts and block groups, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract and block group boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2020 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are unchanged and available as attributes within the data table (units are square meters).  The layer contains all US states, Washington D.C., and Puerto Rico. Census tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99). Block groups that fall within the same criteria (Block Group denoted as 0 with no area land) have also been removed.Percentages and derived counts, are calculated values (that can be identified by the "_calc_" stub in the field name). Field alias names were created based on the Table Shells file available from the Data Table Guide for the Demographic Profile and Demographic and Housing Characteristics. Not all lines of all tables listed above are included in this layer. Duplicative counts were dropped. For example, P0030001 was dropped, as it is duplicative of P0010001.To protect the privacy and confidentiality of respondents, their data has been protected using differential privacy techniques by the U.S. Census Bureau.

Census Tracts from 2020. The TIGER/Line shapefiles are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2020 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 2010 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.

This layer shows Population. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the point by Population Density and size of the point by Total Population. The size of the symbol represents the total count of housing units. Population Density was calculated based on the total population and area of land fields, which both came from the U.S. Census Bureau. Formula used for Calculating the Pop Density (B01001_001E/GEO_LAND_AREA_SQ_KM). To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2018-2022ACS Table(s): B01001, B09020Data downloaded from: Census Bureau's API for American Community Survey Date of API call: January 18, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census: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 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 Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

This layer shows Population. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the point by Population Density and size of the point by Total Population. The size of the symbol represents the total count of housing units. Population Density was calculated based on the total population and area of land fields, which both came from the U.S. Census Bureau. Formula used for Calculating the Pop Density (B01001_001E/GEO_LAND_AREA_SQ_KM). To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2018-2022ACS Table(s): B01001, B09020Data downloaded from: Census Bureau's API for American Community Survey Date of API call: January 18, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census: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 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 Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, 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 Africa Population Distribution Database provides decadal population density data for African administrative units for the period 1960-1990. The databsae was prepared for the United Nations Environment Programme / Global Resource Information Database (UNEP/GRID) project as part of an ongoing effort to improve global, spatially referenced demographic data holdings. The database is useful for a variety of applications including strategic-level agricultural research and applications in the analysis of the human dimensions of global change.

This documentation describes the third version of a database of administrative units and associated population density data for Africa. The first version was compiled for UNEP's Global Desertification Atlas (UNEP, 1997; Deichmann and Eklundh, 1991), while the second version represented an update and expansion of this first product (Deichmann, 1994; WRI, 1995). The current work is also related to National Center for Geographic Information and Analysis (NCGIA) activities to produce a global database of subnational population estimates (Tobler et al., 1995), and an improved database for the Asian continent (Deichmann, 1996). The new version for Africa provides considerably more detail: more than 4700 administrative units, compared to about 800 in the first and 2200 in the second version. In addition, for each of these units a population estimate was compiled for 1960, 70, 80 and 90 which provides an indication of past population dynamics in Africa. Forthcoming are population count data files as download options.

African population density data were compiled from a large number of heterogeneous sources, including official government censuses and estimates/projections derived from yearbooks, gazetteers, area handbooks, and other country studies. The political boundaries template (PONET) of the Digital Chart of the World (DCW) was used delineate national boundaries and coastlines for African countries.

For more information on African population density and administrative boundary data sets, see metadata files at [http://na.unep.net/datasets/datalist.php3] which provide information on file identification, format, spatial data organization, distribution, and metadata reference.

References:

Deichmann, U. 1994. A medium resolution population database for Africa, Database documentation and digital database, National Center for Geographic Information and Analysis, University of California, Santa Barbara.

Deichmann, U. and L. Eklundh. 1991. Global digital datasets for land degradation studies: A GIS approach, GRID Case Study Series No. 4, Global Resource Information Database, United Nations Environment Programme, Nairobi.

UNEP. 1997. World Atlas of Desertification, 2nd Ed., United Nations Environment Programme, Edward Arnold Publishers, London.

WRI. 1995. Africa data sampler, Digital database and documentation, World Resources Institute, Washington, D.C.

This layer shows Population. This is shown by state and county boundaries. This service contains the 2017-2021 release of data from the American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the point by Population Density and size of the point by Total Population. The size of the symbol represents the total count of housing units. Population Density was calculated based on the total population and area of land fields, which both came from the U.S. Census Bureau. Formula used for Calculating the Pop Density (B01001_001E/GEO_LAND_AREA_SQ_KM). To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2017-2021ACS Table(s): B01001, B09020Data downloaded from: Census Bureau's API for American Community Survey Date of API call: February 16, 2023National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census: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 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 Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

A dataset listing Washington counties by population for 2024.

This data represents all ShotSpotter incidents that were classified as “Probable Gunfire”, “Single_Gunshot”, or “Multiple_Gunshots” occurring within one of the six coverage areas defined below since January 1, 2014. The Department plans to continue to release this data with quarterly updates. Classifications are assigned by ShotSpotter and represent their assessment of what kind of impulse noise occurred. Some impulses initially dismissed as non-gunfire are manually audited and resubmitted to the dataset after ground truth analysis.MPD began implementing the ShotSpotter system in 2006 and has added sensors and upgraded components of the system at various times. ShotSpotter has also enhanced their ability to distinguish gunshots from other impulse noises. For example, the number of impulse noises coded as gunshots during Independence Day celebrations have significantly decreased over the past four years.ShotSpotter does not provide coverage for the entire District of Columbia. Official coverage areas are designed by ShotSpotter in conjunction with MPD, to target high population density areas with frequent sounds of gunshots incidents.A ShotSpotter incident may involve one gunshot or multiple gunshots depending on the time elapsed between each shot. Each incident is given a serial number ID when it occurs.The Latitude and Longitude of the incidents are rounded to three decimal places due to privacy concerns. This roughly corresponds to a 100 meter resolution.

This layer shows Population. This is shown by state and county boundaries. This service contains the 2017-2021 release of data from the American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the point by Population Density and size of the point by Total Population. The size of the symbol represents the total count of housing units. Population Density was calculated based on the total population and area of land fields, which both came from the U.S. Census Bureau. Formula used for Calculating the Pop Density (B01001_001E/GEO_LAND_AREA_SQ_KM). To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2017-2021ACS Table(s): B01001, B09020Data downloaded from: Census Bureau's API for American Community Survey Date of API call: February 16, 2023National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census: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 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 Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

Urban rats are notorious invasive pests that thrive in cities by exploiting the resources accompanying high human population density. Identifying long-term trends in rat numbers and how they are shaped by environmental changes is critical for understanding their ecology, and projecting future vulnerabilities and mitigation needs. Here, we use trend analyses of public complaint and inspection data in 16 cities around the world to estimate trends in commensal rat populations. Eleven of 16 cities (69%) had significant increasing trends in rat numbers, including Washington D.C., New York, and Amsterdam. Just three cities experienced declines. Cities experiencing greater temperature increases over time saw larger increases in rat numbers. Cities with more dense human populations and more urbanization also saw larger increases in rats. Warming temperatures and more people living in cities may be expanding the seasonal activity periods and food resource availability for urban rats. Cities will..., , , # Increasing rat numbers in cities are linked to climate warming, urbanization and human population

https://doi.org/10.5061/dryad.3xsj3txrq

Description of the data and file structure

The dataset consists of an Excel file (with two sheets such as data and metadata).

Files and variables

File: Richardson_et_al_ScienceAdv_wild_rat_trend_analysis_data_19Apr24.xlsx

Description:Â Please see the "Metadata" sheet tab within this data file for more information on each variable, abbreviations, etc.Â

Code/Software

This is a basic spreadsheet file, viewable in Excel or Google Sheets. All subsequent analyses with these data were done in R.

To estimate county of residence of Filipinx healthcare workers who died of COVID-19, we retrieved data from the Kanlungan website during the month of December 2020.22 In deciding who to include on the website, the AF3IRM team that established the Kanlungan website set two standards in data collection. First, the team found at least one source explicitly stating that the fallen healthcare worker was of Philippine ancestry; this was mostly media articles or obituaries sharing the life stories of the deceased. In a few cases, the confirmation came directly from the deceased healthcare worker's family member who submitted a tribute. Second, the team required a minimum of two sources to identify and announce fallen healthcare workers. We retrieved 86 US tributes from Kanlungan, but only 81 of them had information on county of residence. In total, 45 US counties with at least one reported tribute to a Filipinx healthcare worker who died of COVID-19 were identified for analysis and will hereafter be referred to as “Kanlungan counties.” Mortality data by county, race, and ethnicity came from the National Center for Health Statistics (NCHS).24 Updated weekly, this dataset is based on vital statistics data for use in conducting public health surveillance in near real time to provide provisional mortality estimates based on data received and processed by a specified cutoff date, before data are finalized and publicly released.25 We used the data released on December 30, 2020, which included provisional COVID-19 death counts from February 1, 2020 to December 26, 2020—during the height of the pandemic and prior to COVID-19 vaccines being available—for counties with at least 100 total COVID-19 deaths. During this time period, 501 counties (15.9% of the total 3,142 counties in all 50 states and Washington DC)26 met this criterion. Data on COVID-19 deaths were available for six major racial/ethnic groups: Non-Hispanic White, Non-Hispanic Black, Non-Hispanic Native Hawaiian or Other Pacific Islander, Non-Hispanic American Indian or Alaska Native, Non-Hispanic Asian (hereafter referred to as Asian American), and Hispanic. People with more than one race, and those with unknown race were included in the “Other” category. NCHS suppressed county-level data by race and ethnicity if death counts are less than 10. In total, 133 US counties reported COVID-19 mortality data for Asian Americans. These data were used to calculate the percentage of all COVID-19 decedents in the county who were Asian American. We used data from the 2018 American Community Survey (ACS) five-year estimates, downloaded from the Integrated Public Use Microdata Series (IPUMS) to create county-level population demographic variables.27 IPUMS is publicly available, and the database integrates samples using ACS data from 2000 to the present using a high degree of precision.27 We applied survey weights to calculate the following variables at the county-level: median age among Asian Americans, average income to poverty ratio among Asian Americans, the percentage of the county population that is Filipinx, and the percentage of healthcare workers in the county who are Filipinx. Healthcare workers encompassed all healthcare practitioners, technical occupations, and healthcare service occupations, including nurse practitioners, physicians, surgeons, dentists, physical therapists, home health aides, personal care aides, and other medical technicians and healthcare support workers. County-level data were available for 107 out of the 133 counties (80.5%) that had NCHS data on the distribution of COVID-19 deaths among Asian Americans, and 96 counties (72.2%) with Asian American healthcare workforce data. The ACS 2018 five-year estimates were also the source of county-level percentage of the Asian American population (alone or in combination) who are Filipinx.8 In addition, the ACS provided county-level population counts26 to calculate population density (people per 1,000 people per square mile), estimated by dividing the total population by the county area, then dividing by 1,000 people. The county area was calculated in ArcGIS 10.7.1 using the county boundary shapefile and projected to Albers equal area conic (for counties in the US contiguous states), Hawai’i Albers Equal Area Conic (for Hawai’i counties), and Alaska Albers Equal Area Conic (for Alaska counties).20

Free-roaming domestic cats (Felis catus) are known to pose threats to ecosystem health via transmission of zoonotic diseases and predation of native wildlife. Likewise, free-roaming cats are also susceptible to predation or disease transmission from native wildlife. Physical interactions are required for many of these risks to be manifested, necessitating spatial and temporal overlap between cats and wildlife species. Therefore, knowledge of the location and extent of shared habitat and activity periods would benefit management programs. We used data from a 3-year camera trap survey to model species-specific occupancy and identify landscape variables that contribute to the distribution of free-roaming domestic cats and eight native mammal species in Washington, DC. (USA). Our analysis includes five species that are common prey items of domestic cats, and three species that are potential disease vectors or are otherwise known to be a risk to cats. We then predicted the probability of occupancy and estimated the probability of spatial overlap between cats and each native wildlife species at multiple scales. We also used kernel density estimations to calculate temporal overlap between cats and each native wildlife species. Across spatial scales, occupancy for potential disease vector species was generally positively correlated with canopy cover and open water. Prey species were also generally positively correlated with canopy cover, but displayed negative associations with human population density and inconsistent associations with average per capita income. Domestic cat occupancy was negatively correlated with natural habitat characteristics and positively correlated with human population density. Predicted spatial overlap between domestic cats and native wildlife was greatest for potential disease vector species. Temporal overlap was high (>0.50) between cats and all but two native wildlife species, indicating that temporal overlap is probable wherever species overlap spatially. Our findings indicate that the risk to and from domestic cats varies across urban landscapes, but primarily arises from human activities. As such, humans are implicated in the negative outcomes that result from cats interacting with wildlife. Data-driven management to reduce such interactions can aid in cat population management, biodiversity conservation, and public health campaigns.

This layer shows Population. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the point by Population Density and size of the point by Total Population. The size of the symbol represents the total count of housing units. Population Density was calculated based on the total population and area of land fields, which both came from the U.S. Census Bureau. Formula used for Calculating the Pop Density (B01001_001E/GEO_LAND_AREA_SQ_KM). To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2018-2022ACS Table(s): B01001, B09020Data downloaded from: Census Bureau's API for American Community Survey Date of API call: January 18, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census: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 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 Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

Many large carnivores occupy a wide geographic distribution, and face threats from habitat loss and fragmentation, poaching, prey depletion, and human wildlife-conflicts. Conservation requires robust techniques for estimating population densities and trends, but the elusive nature and low densities of many large carnivores make them difficult to detect. Spatial capture-recapture (SCR) models provide a means for handling imperfect detectability, while linking population estimates to individual movement patterns to provide more accurate estimates than standard approaches. Within this framework, we investigate the effect of different sample interval lengths on density estimates, using simulations and a common leopard (Panthera pardus) model system. We apply Bayesian SCR methods to 89 simulated datasets and camera-trapping data from 22 leopards captured 82 times during winter 2010–2011 in Royal Manas National Park, Bhutan. We show that sample interval length from daily, weekly, monthly or quarterly periods did not appreciably affect median abundance or density, but did influence precision. We observed the largest gains in precision when moving from quarterly to shorter intervals. We therefore recommend daily sampling intervals for monitoring rare or elusive species where practicable, but note that monthly or quarterly sample periods can have similar informative value. We further develop a novel application of Bayes factors to select models where multiple ecological factors are integrated into density estimation. Our simulations demonstrate that these methods can help identify the “true” explanatory mechanisms underlying the data. Using this method, we found strong evidence for sex-specific movement distributions in leopards, suggesting that sexual patterns of space-use influence density. This model estimated a density of 10.0 leopards/100 km2 (95% credibility interval: 6.25–15.93), comparable to contemporary estimates in Asia. These SCR methods provide a guide to monitor and observe the effect of management interventions on leopards and other species of conservation interest.

This layer shows Population. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the point by Population Density and size of the point by Total Population. The size of the symbol represents the total count of housing units. Population Density was calculated based on the total population and area of land fields, which both came from the U.S. Census Bureau. Formula used for Calculating the Pop Density (B01001_001E/GEO_LAND_AREA_SQ_KM). To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2018-2022ACS Table(s): B01001, B09020Data downloaded from: Census Bureau's API for American Community Survey Date of API call: January 18, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census: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 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 Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

This map's colors indicate which population is larger in each area: urban (green) or rural (yellow). The map's layers contain total population counts by sex, age, and race groups for Nation, State Legislative Districts Upper, State Legislative Districts Lower, Congressional District in the United States and Puerto Rico.The U.S. Census designates each census block as part of an urban area or as rural. Larger geographies in this map such as block group, tract, county and state can therefore have a mix of urban and rural population. This map illustrates the 100% urban areas in dark green, and 100% rural areas in dark yellow. Areas with mixed urban/rural population have softer shades of green or yellow, to give a visual indication of where change may be happening. From the Census:"The Census Bureau’s urban-rural classification is a delineation of geographic areas, identifying both individual urban areas and the rural area of the nation. The Census Bureau’s urban areas represent densely developed territory, and encompass residential, commercial, and other non-residential urban land uses. The Census Bureau delineates urban areas after each decennial census by applying specified criteria to decennial census and other data. Rural encompasses all population, housing, and territory not included within an urban area.For the 2020 Census, an urban area will comprise a densely settled core of census blocks that meet minimum housing unit density and/or population density requirements. This includes adjacent territory containing non-residential urban land uses. To qualify as an urban area, the territory identified according to criteria must encompass at least 2,000 housing units or have a population of at least 5,000." SourceAbout the dataYou can use this map as is and you can also modify it to use other attributes included in its layers. This map's layers contain total population counts by sex, age, and race groups data from the 2020 Census Demographic and Housing Characteristics. This is shown by Nation, State, County, Census Tract, Block Group boundaries. Each geography layer contains a common set of Census counts based on available attributes from the U.S. Census Bureau. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis.Vintage of boundaries and attributes: 2020 Demographic and Housing Characteristics Table(s): P1, H1, H3, P2, P3, P5, P12, P13, P17, PCT12 (Not all lines of these DHC tables are available in this feature layer.)Data downloaded from: U.S. Census Bureau’s data.census.gov siteDate the Data was Downloaded: May 25, 2023Geography Levels included: Nation, State, County, Census Tract, Block GroupNational Figures: included in Nation layer The United States Census Bureau Demographic and Housing Characteristics: 2020 Census Results 2020 Census Data Quality Geography & 2020 Census Technical Documentation Data Table Guide: includes the final list of tables, lowest level of geography by table and table shells for the Demographic Profile and Demographic and Housing Characteristics.News & Updates This map is ready to be used in ArcGIS Pro, ArcGIS Online and its configurable apps, Story Maps, dashboards, Notebooks, Python, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the U.S. Census Bureau when using this data. Data Processing Notes: These 2020 Census boundaries come from the US Census TIGER geodatabases. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For Census tracts and block groups, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract and block group boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2020 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are unchanged and available as attributes within the data table (units are square meters).  The layer contains all US states, Washington D.C., and Puerto Rico. Census tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99). Block groups that fall within the same criteria (Block Group denoted as 0 with no area land) have also been removed.Percentages and derived counts, are calculated values (that can be identified by the "_calc_" stub in the field name). Field alias names were created based on the Table Shells file available from the Data Table Guide for the Demographic Profile and Demographic and Housing Characteristics. Not all lines of all tables listed above are included in this layer. Duplicative counts were dropped. For example, P0030001 was dropped, as it is duplicative of P0010001.To protect the privacy and confidentiality of respondents, their data has been protected using differential privacy techniques by the U.S. Census Bureau.