Table contains total population and population density summarized at county, city, zip code, and census tract level. Population density is defined as number of people residing per square mile of area. Data are presented for zip codes (ZCTAs) fully within the county. Source: U.S. Census Bureau, 2016-2020 American Community Survey 5-year estimates, Table B01001; data accessed on April 11, 2022 from https://api.census.gov. The 2020 Decennial geographies are used for data summarization.METADATA:notes (String): Lists table title, notes, sourcesgeolevel (String): Level of geographyGEOID (String): Geography IDNAME (String): Name of geographyt_pop (Numeric): Total populationpop_density (Numeric): Area in square milesarea (Numeric): Population density

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau across all standard and custom geographies at statewide summary level where applicable. For a deep dive into the data model including every specific metric, see the ACS 2017-2021 Data Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics. Find naming convention prefixes/suffixes, geography definitions and user notes below.Prefixes:NoneCountpPercentrRatemMedianaMean (average)tAggregate (total)chChange in absolute terms (value in t2 - value in t1)pchPercent change ((value in t2 - value in t1) / value in t1)chpChange in percent (percent in t2 - percent in t1)sSignificance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computedSuffixes:_e21Estimate from 2017-21 ACS_m21Margin of Error from 2017-21 ACS_e102006-10 ACS, re-estimated to 2020 geography_m10Margin of Error from 2006-10 ACS, re-estimated to 2020 geography_e10_21Change, 2010-21 (holding constant at 2020 geography)GeographiesAAA = Area Agency on Aging (12 geographic units formed from counties providing statewide coverage)ARC21 = Atlanta Regional Commission modeling area (21 counties merged to a single geographic unit)ARWDB7 = Atlanta Regional Workforce Development Board (7 counties merged to a single geographic unit)BeltLine (buffer)BeltLine Study (subareas)Census Tract (statewide)CFGA23 = Community Foundation for Greater Atlanta (23 counties merged to a single geographic unit)City (statewide)City of Atlanta Council Districts (City of Atlanta)City of Atlanta Neighborhood Planning Unit (City of Atlanta)City of Atlanta Neighborhood Planning Unit STV (3 NPUs merged to a single geographic unit within City of Atlanta)City of Atlanta Neighborhood Statistical Areas (City of Atlanta)City of Atlanta Neighborhood Statistical Areas E02E06 (2 NSAs merged to single geographic unit within City of Atlanta)County (statewide)Georgia House (statewide)Georgia Senate (statewide)MetroWater15 = Atlanta Metropolitan Water District (15 counties merged to a single geographic unit)Regional Commissions (statewide)SPARCC = Strong, Prosperous And Resilient Communities ChallengeState of Georgia (single geographic unit)Superdistrict (ARC region)US Congress (statewide)UWGA13 = United Way of Greater Atlanta (13 counties merged to a single geographic unit)WFF = Westside Future Fund (subarea of City of Atlanta)ZIP Code Tabulation Areas (statewide)The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2017-2021). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2017-2021Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the data manifest: https://garc.maps.arcgis.com/sharing/rest/content/items/34b9adfdcc294788ba9c70bf433bd4c1/data

A dataset listing North Carolina zip codes by population for 2024.

The 2022 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. 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 and beyond, 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 2019 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program. The 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.

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 2013 Rural-Urban Continuum Codes form a classification scheme that distinguishes metropolitan counties by the population size of their metro area, and nonmetropolitan counties by degree of urbanization and adjacency to a metro area. The official Office of Management and Budget (OMB) metro and nonmetro categories have been subdivided into three metro and six nonmetro categories. Each county in the U.S. is assigned one of the 9 codes. This scheme allows researchers to break county data into finer residential groups, beyond metro and nonmetro, particularly for the analysis of trends in nonmetro areas that are related to population density and metro influence. The Rural-Urban Continuum Codes were originally developed in 1974. They have been updated each decennial since (1983, 1993, 2003, 2013), and slightly revised in 1988. Note that the 2013 Rural-Urban Continuum Codes are not directly comparable with the codes prior to 2000 because of the new methodology used in developing the 2000 metropolitan areas. See the Documentation for details and a map of the codes. An update of the Rural-Urban Continuum Codes is planned for mid-2023.

These data were developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau across all standard and custom geographies at statewide summary level where applicable. .
For a deep dive into the data model including every specific metric, see the ACS 2018-2022 Data Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics. Find naming convention prefixes/suffixes, geography definitions and user notes below.Prefixes:NoneCountpPercentrRatemMedianaMean (average)tAggregate (total)chChange in absolute terms (value in t2 - value in t1)pchPercent change ((value in t2 - value in t1) / value in t1)chpChange in percent (percent in t2 - percent in t1)sSignificance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computedSuffixes:_e22Estimate from 2018-22 ACS_m22Margin of Error from 2018-22 ACS_e102006-10 ACS, re-estimated to 2020 geography_m10Margin of Error from 2006-10 ACS, re-estimated to 2020 geography_e10_22Change, 2010-22 (holding constant at 2020 geography)GeographiesAAA = Area Agency on Aging (12 geographic units formed from counties providing statewide coverage)ARC21 = Atlanta Regional Commission modeling area (21 counties merged to a single geographic unit)ARWDB7 = Atlanta Regional Workforce Development Board (7 counties merged to a single geographic unit)BeltLineStatistical (buffer)BeltLineStatisticalSub (subareas)Census Tract (statewide)CFGA23 = Community Foundation for Greater Atlanta (23 counties merged to a single geographic unit)City (statewide)City of Atlanta Council Districts (City of Atlanta)City of Atlanta Neighborhood Planning Unit (City of Atlanta)City of Atlanta Neighborhood Statistical Areas (City of Atlanta)County (statewide)Georgia House (statewide)Georgia Senate (statewide)HSSA = High School Statistical Area (11 county region)MetroWater15 = Atlanta Metropolitan Water District (15 counties merged to a single geographic unit)Regional Commissions (statewide)State of Georgia (single geographic unit)Superdistrict (ARC region)US Congress (statewide)UWGA13 = United Way of Greater Atlanta (13 counties merged to a single geographic unit)ZIP Code Tabulation Areas (statewide)The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2018-2022). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2018-2022Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the data manifest: https://opendata.atlantaregional.com/documents/3b86ee614e614199ba66a3ff1ebfe3b5/about

Note: These layers were compiled by Esri's Demographics Team using data from the Census Bureau's American Community Survey. These data sets are not owned by the City of Rochester.Overview of the map/data: This map shows the percentage of the population living below the federal poverty level over the previous 12 months, shown by tract, county, and state boundaries. Estimates are from the 2018 ACS 5-year samples. This service is updated annually to contain the most currently released 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. Current Vintage: 2019-2023ACS Table(s): B17020, C17002Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 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:This layer will be updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), 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 census tracts, the water cutouts are derived from a subset of the 2010 AWATER (Area Water) boundaries offered by TIGER. 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.Census tracts with no population are removed from this data service (Census Tracts beginning with 99).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 file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -555555...) have been set to null. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small. NOTE: any calculated percentages or counts that contain estimates that have null margins of error yield null margins of error for the calculated fields.

This file contains the National Statistics Postcode Lookup (NSPL) for the United Kingdom as at August 2022 in Comma Separated Variable (CSV) and ASCII text (TXT) formats. To download the zip file click the Download button. The NSPL relates both current and terminated postcodes to a range of current statutory geographies via ‘best-fit’ allocation from the 2021 Census Output Areas (national parks and Workplace Zones are exempt from ‘best-fit’ and use ‘exact-fit’ allocations) for England and Wales. Scotland and Northern Ireland has the 2011 Census Output AreasIt supports the production of area based statistics from postcoded data. The NSPL is produced by ONS Geography, who provide geographic support to the Office for National Statistics (ONS) and geographic services used by other organisations. The NSPL is issued quarterly. (File size - 184 MB).

Overview The PCCF+ is a SAS control program and set of associated datasets derived from the PCCF, a 2021 postal code population weight file, the Geographic Attribute File, Health Region boundary files, and other supplementary data. PCCF+ automatically assigns a range of Statistics Canada standard geographic areas and other geographic identifiers based on postal codes. PCCF+ differs from the PCCF in that it: Uses population-weighted random allocation for many postal codes that link to more than one geographic area. Options are available for institutional postal codes. Procedures are included to link partial postal codes to geographic identifiers where possible. Problem records and diagnostics are provided in the program output, along with reference information for possible solutions. The geographic coordinates, which represent the standard geostatistical areas linked to each postal code on the PCCF, are commonly used to map the distribution of data for spatial analysis (e.g., clients, activities). In April 1983, the Geography Division released the first version of the PCCF, which linked postal codes to 1981 census geographic areas and included geographic coordinates. PCCF+ was first created using the 1986 census and has been updated regularly with population weight files calculated for each census from 1991 through 2021. Purpose of PCCF+ The purpose of the PCCF+ is to provide a link between six-character postal codes produced by the Canada Post Corporation (CPC), standard 2021 Census geographic areas (such as dissemination areas, census subdivisions, and census tracts) produced by Statistics Canada, and supplementary administrative areas and neighbourhood income quintiles. Postal codes do not respect census geographic boundaries and so may be linked to more than one standard geographic area, or assigned to more than one set of coordinates. Therefore, one postal code may be represented by more than one record. The PCCF product, produced by Statistics Canada, provides links between postal codes and all recorded matches to census geography. PCCF+ uses the PCCF but provides additional functionality in that it uses a population-weighted matching process for some residential postal codes where more than one geographic code is possible. PCCF+ also provides routines for institutional postal codes and for historic postal codes. The PCCF+ Version 8B includes a population-weighting file calculated from the 2021 Census population counts Neighbourhood income quintiles and deciles have been calculated from 2021 Census population data. The routine that allowed geocoding of historical postal codes in British Columbia (V1H, V9G, prior 1998) has been removed.

Find Massachusetts health data by community, county, and region, including population demographics. Build custom data reports with over 100 health and social determinants of health data indicators and explore over 28,000 current and historical data layers in the map room.