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 EnviroAtlas dataset estimates the intersection density of walkable roads within a 750 meter radius of any given 10 meter pixel in the community. Intersections are defined as any point where 3 or more roads meet and density is calculated using kernel density, where closer intersections are weighted higher than further intersections. Intersection density is highly correlated with walking for transportation. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

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.

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.

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 shows areas where population and jobs growth will be concentrated in the District through the year 2045.

This dataset was used to conduct all analyses in the working paper, "Short-term associations of road density and road features with in-vehicle PM2.5 during daily trips" by Jenna R. Krall, Jonathan Thornburg, Ting Zhang, Anna Z. Pollack, Yi-Ching Lee, Michelle McCombs, and Lucas R. F. Henneman (2023+). This dataset is restricted to N=25 commuters with at least 15 minutes of consecutive GPS and air pollution data. Each row corresponds to a one-minute observation for a trip within day within commuter. The data contains 2311 rows and 29 variables. These data are provided as a .csv file, generated using R (v 4.2).

Using Census data, the Low English Proficiency Populations Index shows Census blocks classified into five categories based on the population of persons with low English proficiency as a percentage of the total population. Persons with low English proficiency are persons identified by the Census as speaking English less than “very well.” An index score of five indicates a higher density of persons with low English proficiency.

This dataset contains the modeling results GIS data (maps) of the study “Sustainable Human Population Density in Western Europe between 560.000 and 360.000 years ago” by Rodríguez et al. (2022). The NPP data (npp.zip) was computed using an empirical formula (the Miami model) from palaeo temperature and palaeo precipitation data aggregated for each timeslice from the Oscillayers dataset (Gamisch, 2019), as defined in Rodríguez et al. (2022, in review). The Population densities file (pop_densities.zip) contains the computed minimum and maximum population densities rasters for each of the defined MIS timeslices. With the population density value Dc in logarithmic form log(Dc). The Species Distribution Model (sdm.7z) includes input data (folder /data), intermediate results (folder /work) and results and figures (folder /results). All modelling steps are included as an R project in the folder /scripts. The R project is subdivided into individual scripts for data preparation (1.x), sampling procedure (2.x), and model computation (3.x). The habitat range estimation (habitat_ranges.zip) includes the potential spatial boundaries of the hominin habitat as binary raster files with 1=presence and 0=absence. The ranges rely on a dichotomic classification of the habitat suitability with a threshold value inferred from the 5% quantile of the presence data. The habitat suitability (habitat_suitability.zip) is the result of the Species Distribution Modelling and describes the environmental suitability for hominin presence based on the sites considered in this study. The values range between 0=low and 1=high suitability. The dataset includes the mean (pred_mean) and standard deviation (pred_std) of multiple model runs.

Using Census data, the Low English Proficiency Populations Index shows Census blocks classified into five categories based on the population of persons with low English proficiency as a percentage of the total population. Persons with low English proficiency are persons identified by the Census as speaking English less than “very well.” An index score of five indicates a higher density of persons with low English proficiency.

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 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 purpose of the design review process is to: Allow for special projects to be approved by the Zoning Commission after a public hearing and a finding of no adverse impact; Recognize that some areas of the District of Columbia warrant special attention due to particular or unique characteristics of an area or project; Permit some projects to voluntarily submit themselves for design review in exchange for flexibility because the project is superior in design but does not need extra density; Promote high-quality, contextual design; and Provide for flexibility in building bulk control, design, and site placement without an increase in density or a map amendment.

All data needed to evaluate the conclusions in the paper are present in the paper and/or the Supplementary Materials. Datasets and code for analyses and generation of figures are available via FigShare (doi: 10.6084/m9.figshare.22266046) and a public GitHub repository (https://github.com/rumschsl/MacroBiodivTrends). This dataset is associated with the following publication: Rumschlag, S., M. Mahon, D. Jones, W. Battaglin, J. Behrens, E. Bernhardt, P. Bradley, E. Brown, F. De Laender, R. Hill, S. Kunz, S. Lee, E. Rosi, R. Schafer, T. Schmidt, M. Simonin, K. Smalling, K. Voss, and J. Rohr. Density declines, richness increases, and composition shifts in stream macroinvertebrates. Science Advances. American Association for the Advancement of Science (AAAS), Washington, DC, USA, 9(18): eadf4896, (2023).

This map uses dot density patterns to indicate which population is larger in each area: urban (green) or rural (blue). 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.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 with all green dots, and 100% rural areas in dark blue dots. Areas with mixed urban/rural population have a proportional mix of green and blue dots 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.

Disclaimer: These data are updated by the author and are not an official product of the Federal Reserve Bank of Cleveland.This project provides two sets of migration estimates for the major US metro areas. The first series measures net migration of people to and from the urban neighborhoods of the metro areas. The second series covers all neighborhoods but breaks down net migration to other regions by four region types: (1) high-cost metros, (2) affordable, large metros, (3) midsized metros, and (4) small metros and rural areas. These series were introduced in a Cleveland Fed District Data Brief entitled “Urban and Regional Migration Estimates: Will Your City Recover from the Pandemic?"The migration estimates in this project are created with data from the Federal Reserve Bank of New York/Equifax Consumer Credit Panel (CCP). The CCP is a 5 percent random sample of the credit histories maintained by Equifax. The CCP reports the census block of residence for over 10 million individuals each quarter. Each month, Equifax receives individuals’ addresses, along with reports of debt balances and payments, from creditors (mortgage lenders, credit card issuers, student loan servicers, etc.). An algorithm maintained by Equifax considers all of the addresses reported for an individual and identifies the individual’s most likely current address. Equifax anonymizes the data before they are added to the CCP, removing names, addresses, and Social Security numbers (SSNs). In lieu of mailing addresses, the census block of the address is added to the CCP. Equifax creates a unique, anonymous identifier to enable researchers to build individuals’ panels. The panel nature of the data allows us to observe when someone has migrated and is living in a census block different from the one they lived in at the end of the preceding quarter. For more details about the CCP and its use in measuring migration, see Lee and Van der Klaauw (2010) and DeWaard, Johnson and Whitaker (2019). DefinitionsMetropolitan areaThe metropolitan areas in these data are combined statistical areas. This is the most aggregate definition of metro areas, and it combines Washington DC with Baltimore, San Jose with San Francisco, Akron with Cleveland, etc. Metro areas are combinations of counties that are tightly linked by worker commutes and other economic activity. All counties outside of metropolitan areas are tracked as parts of a rural commuting zone (CZ). CZs are also groups of counties linked by commuting, but CZ definitions cover all counties, both metropolitan and non-metropolitan. High-cost metropolitan areasHigh-cost metro areas are those where the median list price for a house was more than $200 per square foot on average between April 2017 and April 2022. These areas include San Francisco-San Jose, New York, San Diego, Los Angeles, Seattle, Boston, Miami, Sacramento, Denver, Salt Lake City, Portland, and Washington-Baltimore. Other Types of RegionsMetro areas with populations above 2 million and house price averages below $200 per square foot are categorized as affordable, large metros. Metro areas with populations between 500,000 and 2 million are categorized as mid-sized metros, regardless of house prices. All remaining counties are in the small metro and rural category.To obtain a metro area's total net migration, sum the four net migration values for the the four types of regions.Urban neighborhoodCensus tracts are designated as urban if they have a population density above 7,000 people per square mile. High density neighborhoods can support walkable retail districts and high-frequency public transportation. They are more likely to have the “street life” that people associate with living in an urban rather than a suburban area. The threshold of 7,000 people per square mile was selected because it was the average density in the largest US cities in the 1930 census. Before World War II, workplaces, shopping, schools and parks had to be accessible on foot. Tracts are also designated as urban if more than half of their housing units were built before WWII and they have a population density above 2,000 people per square mile. The lower population density threshold for the pre-war neighborhoods recognizes that many urban tracts have lost population since the 1960s. While the street grids usually remain, the area also needs su

Aryandoust, A., van Vliet, O. & Patt, A. City-scale car traffic and parking density maps from Uber Movement travel time data. Scientific Data 6, 158 (2019). https://doi.org/10.1038/s41597-019-0159-6

This dataset includes density, temperature, grain size, and layer thickness measurements collected from various projects available on USAP-DC. Depth listings were recalculated to reflect measurements from the surface of the ice to the deep ice if they were not listed as such in the original dataset. Non-linear least-squares regression was performed on the data to find parameters to existing depth-dependent density and grain size models and the regression results are provided in this dataset. Data is made available in MATLAB and XLSX files. See “insituData_readMe” for more details.

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.