39 datasets found
  1. d

    ACS 5 Year Data by Community Area

    • catalog.data.gov
    • data.cityofchicago.org
    Updated Jun 7, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    data.cityofchicago.org (2025). ACS 5 Year Data by Community Area [Dataset]. https://catalog.data.gov/dataset/acs-5-year-data-by-community-area
    Explore at:
    Dataset updated
    Jun 7, 2025
    Dataset provided by
    data.cityofchicago.org
    Description

    Selected variables from the most recent ACS Community Survey (Released 2023) aggregated by Community Area. Additional years will be added as they become available. The underlying algorithm to create the dataset calculates the % of a census tract that falls within the boundaries of a given community area. Given that census tracts and community area boundaries are not aligned, these figures should be considered an estimate. Total population in this dataset: 2,647,621 Total Chicago Population Per ACS 2023: 2,664,452 % Difference: -0.632% There are different approaches in common use for displaying Hispanic or Latino population counts. In this dataset, following the approach taken by the Census Bureau, a person who identifies as Hispanic or Latino will also be counted in the race category with which they identify. However, again following the Census Bureau data, there is also a column for White Not Hispanic or Latino. Code can be found here: https://github.com/Chicago/5-Year-ACS-Survey-Data Community Area Shapefile: https://data.cityofchicago.org/Facilities-Geographic-Boundaries/Boundaries-Community-Areas-current-/cauq-8yn6 Census Area Python Package Documentation: https://census-area.readthedocs.io/en/latest/index.html

  2. a

    Census Tracts: 2018

    • gis.data.alaska.gov
    • alaska-economic-data-dcced.hub.arcgis.com
    • +4more
    Updated Jul 30, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Dept. of Commerce, Community, & Economic Development (2019). Census Tracts: 2018 [Dataset]. https://gis.data.alaska.gov/datasets/DCCED::census-tracts-2018
    Explore at:
    Dataset updated
    Jul 30, 2019
    Dataset authored and provided by
    Dept. of Commerce, Community, & Economic Development
    Area covered
    Description

    Census tracts as of 2018."Census Tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity that are updated by local participants prior to each decennial census as part of the Census Bureau's Participant Statistical Areas Program. The Census Bureau delineates census tracts in situations where no local participant existed or where state, local, or tribal governments declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of statistical data.Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. A census tract usually covers a contiguous area; however, the spatial size of census tracts varies widely depending on the density of settlement. Census tract boundaries are delineated with the intention of being maintained over a long time so that statistical comparisons can be made from census to census. Census tracts occasionally are split due to population growth or merged as a result of substantial population decline.Census tract boundaries generally follow visible and identifiable features. They may follow nonvisible 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. Tribal census tracts are a unique geographic entity defined within federally recognized American Indian reservations and off-reservation trust lands and can cross state and county boundaries. Tribal census tracts may be completely different from the census tracts and block groups defined by state and county.Census Tract Codes and Numbers—Census tracts are identified by an up to four-digit integer number and may have an optional two-digit suffix; for example 1457.02 or 23. The census tract codes consist of six digits with an implied decimal between the fourth and fifth digit corresponding to the basic census tract number but with leading zeroes and trailing zeroes for census tracts without a suffix. The tract number examples above would have codes of 145702 and 002300, respectively."- US Census Bureau For information about US Census Bureau geographies, click here. USE CONSTRAINTS: The Alaska Department of Commerce, Community, and Economic Development (DCCED) provides the data in this application as a service to the public. DCCED makes no warranty, representation, or guarantee as to the content, accuracy, timeliness, or completeness of any of the data provided on this site. DCCED shall not be liable to the user for damages of any kind arising out of the use of data or information provided. DCCED is not the authoritative source for American Community Survey data, and any data or information provided by DCCED is provided "as is". Data or information provided by DCCED shall be used and relied upon only at the user's sole risk.

  3. Agriculture; labour force by region

    • data.overheid.nl
    • staging.dexes.eu
    • +2more
    atom, json
    Updated Mar 28, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Centraal Bureau voor de Statistiek (Rijk) (2025). Agriculture; labour force by region [Dataset]. https://data.overheid.nl/dataset/3941-agriculture--labour-force-by-region
    Explore at:
    atom(KB), json(KB)Available download formats
    Dataset updated
    Mar 28, 2025
    Dataset provided by
    Statistics Netherlands
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    This table contains data at regional level on the number of persons employed on agricultural holdings, the corresponding annual work units (AWUs) and the number of holdings with workers.

    The figures in this table are derived from the agricultural census. Data collection for the agricultural census is part of a combined data collection for a.o. agricultural policy use and enforcement of the manure law.

    Regional breakdown is based on the main location of the holding. Due to this the region where activities (crops, animals) are allocated may differ from the location where these activities actually occur.

    The agricultural census is also used as the basis for the European Farm Structure Survey (FSS). Data from the agricultural census do not fully coincide with the FSS. In the FSS years (2000, 2003, 2005, 2007 and 2010) additional information was collected to meet the requirements of the FSS.

    Data on labour force refer to the period April to March of the year preceding the agricultural census.

    In 2022, equidae are not part of the Agricultural Census. This affects the farm type and the total number of farms in the Agricultural Census. Farms with horses, ponies and donkeys that were previously classified as ‘specialist grazing livestock' could be classified, according to their dominant activity, as another farm type in 2022.

    From 2018 onwards the number of calves for fattening, pigs for fattening, chicken and turkey are adjusted in the case of temporary breaks in the production cycle (e.g. sanitary cleaning). The agricultural census is a structural survey, in which adjustment for temporary breaks in the production cycle is a.o. relevant for the calculation of the economic size of the holding, and its farm type. In the livestock surveys the number of animals on the reference day is relevant, therefore no adjustment for temporary breaks in the production cycle are made. This means that the number of animals in the tables of the agricultural census may differ from those in the livestock tables (see ‘links to relevant tables and relevant articles).

    From 2017 onwards, animal numbers are increasingly derived from I&R registers (Identification and Registration of animals), instead of by means of the combined data collection. The I&R registers are the responsibility of RVO (Netherlands Enterprise Agency). Since 2017, cattle numbers are derived from I&R cattle, and from 2018 sheep, goats and poultry are also derived from the relevant I&R registers. The registration of cattle, sheep and goats takes place directly at RVO. Poultry data is collected via the designated database Poultry Information System Poultry (KIP) from Avined. Avined is a branch organization for the egg and poultry meat sectors. Avined passes the data on to the central database of RVO. Due to the transition to the use of I&R registers, a change in classification will occur for sheep and goats from 2018 onwards.

    Since 2016, information of the Dutch Business Register is used to define the agricultural census. Registration in the Business Register with an agricultural standard industrial classification code, related to NACE/ISIC, (in Dutch SBI: ‘Standaard BedrijfsIndeling’) is leading to determine whether there is an agricultural holding. This aligns the agricultural census as closely as possible to the statistical regulations of Eurostat and the (Dutch) implementation of the definition of 'active farmer' as described in the common agricultural policy.

    The definition of the agricultural census based on information from the Dutch Business Register mainly affects the number of holdings, a clear deviation of the trend occurs. The impact on areas (except for other land and rough grazing) and the number of animals (except for sheep, and horses and ponies) is limited. This is mainly due to the holdings that are excluded as a result of the new delimitation of agricultural holdings (such as equestrian centres, city farms and organisations in nature management).

    In 2011 there were changes in geographic assignment of holdings with a foreign main seat. This may influence regional figures, mainly in border regions.

    Until 2010 the economic size of agricultural holdings was expressed in Dutch size units (in Dutch NGE: 'Nederlandse Grootte Eenheid'). From 2010 onwards this has become Standard Output (SO). This means that the threshold for holdings in the agricultural census has changed from 3 NGE to 3000 euro SO. For comparable time series the figures for 2000 up to and including 2009 have been recalculated, based on SO coefficients and SO typology. The latest update was in 2016.

    Data available from: 2000

    Status of the figures: The figures are final.

    Changes as of March 28, 2025: the final figures for 2024 have been added.

    When will new figures be published? According to regular planning provisional figures for the current year are published in November and the definite figures will follow in March of the following year.

  4. a

    Race by Age Groups (B01001A-I)

    • data-seattlecitygis.opendata.arcgis.com
    • data.seattle.gov
    • +1more
    Updated Sep 7, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Seattle ArcGIS Online (2023). Race by Age Groups (B01001A-I) [Dataset]. https://data-seattlecitygis.opendata.arcgis.com/datasets/SeattleCityGIS::race-by-age-groups-b01001a-i
    Explore at:
    Dataset updated
    Sep 7, 2023
    Dataset authored and provided by
    City of Seattle ArcGIS Online
    Description

    Table from the American Community Survey (ACS) B01001A-I sex by age by race - data is grouped into three age group categories for each race, under 18, 18-64 and 65 and older. These are multiple, nonoverlapping vintages of the 5-year ACS estimates of population and housing attributes starting in 2010 shown by the corresponding census tract vintage. Also includes the most recent release annually.Data on total number of people by each race alone and in combination by each census tract has been transposed to support dashboard visualizations.King County, Washington census tracts with nonoverlapping vintages of the 5-year American Community Survey (ACS) estimates starting in 2010. Vintage identified in the "ACS Vintage" field.The census tract boundaries match the vintage of the ACS data (currently 2010 and 2020) so please note the geographic changes between the decades. Tracts have been coded as being within the City of Seattle as well as assigned to neighborhood groups called "Community Reporting Areas". These areas were created after the 2000 census to provide geographically consistent neighborhoods through time for reporting U.S. Census Bureau data. This is not an attempt to identify neighborhood boundaries as defined by neighborhoods themselves.Vintages: 2010, 2015, 2020, 2021, 2022, 2023ACS Table(s): B01001Data downloaded from: Census Bureau's Explore Census Data The 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 US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). 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 erased for cartographic and mapping purposes. For census tracts, 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 level 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 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 RicoCensus tracts with no population that occur in areas of water, such as oceans, 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., -4444...) have been set to null, with the exception of -5555... which has been set to zero. 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.

  5. w

    R2 & NE: Tract Level 2006-2010 ACS Language Summary

    • data.wu.ac.at
    • datadiscoverystudio.org
    • +1more
    tgrshp (compressed)
    Updated Jan 13, 2018
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Environmental Protection Agency (2018). R2 & NE: Tract Level 2006-2010 ACS Language Summary [Dataset]. https://data.wu.ac.at/schema/data_gov/MzIyOGVkM2ItMzc2MS00NmU3LTgyZmMtZjhiZDc2Y2E1NWJh
    Explore at:
    tgrshp (compressed)Available download formats
    Dataset updated
    Jan 13, 2018
    Dataset provided by
    U.S. Environmental Protection Agency
    License

    U.S. Government Workshttps://www.usa.gov/government-works
    License information was derived automatically

    Area covered
    09629b3bf1aec9ae51a4dc246ad39acae76c852d
    Description

    The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File 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 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.

    This table contains data on language ability and linguistic isolation from the American Community Survey 2006-2010 database for tracts. Linguistic isolation is defined as no one 14 and over speaks English only or speaks English "very well". The American Community Survey (ACS) is a household survey conducted by the U.S. Census Bureau that currently has an annual sample size of about 3.5 million addresses. ACS estimates provides communities with the current information they need to plan investments and services. Information from the survey generates estimates that help determine how more than $400 billion in federal and state funds are distributed annually. Each year the survey produces data that cover the periods of 1-year, 3-year, and 5-year estimates for geographic areas in the United States and Puerto Rico, ranging from neighborhoods to Congressional districts to the entire nation. This table also has a companion table (Same table name with MOE Suffix) with the margin of error (MOE) values for each estimated element. MOE is expressed as a measure value for each estimated element. So a value of 25 and an MOE of 5 means 25 +/- 5 (or statistical certainty between 20 and 30). There are also special cases of MOE. An MOE of -1 means the associated estimates do not have a measured error. An MOE of 0 means that error calculation is not appropriate for the associated value. An MOE of 109 is set whenever an estimate value is 0. The MOEs of aggregated elements and percentages must be calculated. This process means using standard error calculations as described in "American Community Survey Multiyear Accuracy of the Data (3-year 2008-2010 and 5-year 2006-2010)". Also, following Census guidelines, aggregated MOEs do not use more than 1 0-element MOE (109) to prevent over estimation of the error. Due to the complexity of the calculations, some percentage MOEs cannot be calculated (these are set to null in the summary-level MOE tables).

    The name for table 'ACS10LANTRMOE' was added as a prefix to all field names imported from that table. Be sure to turn off 'Show Field Aliases' to see complete field names in the Attribute Table of this feature layer. This can be done in the 'Table Options' drop-down menu in the Attribute Table or with key sequence '[CTRL]+[SHIFT]+N'. Due to database restrictions, the prefix may have been abbreviated if the field name exceded the maximum allowed characters.

  6. D

    2020 Census Tracts; PA, NJ, DE & MD

    • catalog.dvrpc.org
    • staging-catalog.cloud.dvrpc.org
    • +1more
    api, geojson, html +1
    Updated May 23, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    DVRPC (2025). 2020 Census Tracts; PA, NJ, DE & MD [Dataset]. https://catalog.dvrpc.org/dataset/2020-census-tracts-pa-nj-de-md
    Explore at:
    xml, html, api, geojsonAvailable download formats
    Dataset updated
    May 23, 2025
    Dataset provided by
    Delaware Valley Regional Planning Commissionhttps://www.dvrpc.org/
    Authors
    DVRPC
    Area covered
    New Jersey, Pennsylvania
    Description

    USE geoid TO JOIN DATA DOWNLOADED FROM DATA.CENSUS.GOV The TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) System (MTS). The TIGER/Line Shapefiles contain a standard geographic identifier (GEOID) for each entity that links to the GEOID in the data from censuses and surveys. The TIGER/Line Shapefiles do not include demographic data from surveys and censuses (e.g., Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program). Other, non-census, data often have this standard geographic identifier as well. Data from many of the Census Bureau’s surveys and censuses, including the geographic codes needed to join to the TIGER/Line Shapefiles, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/). Census Tracts are small, relatively permanent statistical subdivisions of a county or statistically equivalent entity that can be updated by local participants prior to each decennial census as part of the Census Bureau’s Participant Statistical Areas Program (PSAP). The Census Bureau delineates census tracts in situations where no local participant responded or where state, local, or tribal governments declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of statistical data. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. A census tract usually covers a contiguous area; however, the spatial size of census tracts varies widely depending on the density of settlement. Census tract boundaries are delineated with the intention of being maintained over a long time so that statistical comparisons can be made from census to census. Census tracts occasionally are split due to population growth or merged as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow nonvisible 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. Tribal census tracts are a unique geographic entity defined within federally recognized American Indian reservations and off-reservation trust lands and can cross state and county boundaries. The tribal census tracts may be completely different from the standard county-based census tracts defined for the same area. (see “Tribal Census Tract”). Downloaded from https://www2.census.gov/geo/tiger/TIGER2022/TRACT/ on June 22, 2023

  7. a

    2020 Census Block Groups Top 50 American Community Survey Data with Seattle...

    • hub.arcgis.com
    Updated Feb 6, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Seattle ArcGIS Online (2024). 2020 Census Block Groups Top 50 American Community Survey Data with Seattle Neighborhoods [Dataset]. https://hub.arcgis.com/datasets/ff59dc88bfab4eb3bc4cd11eaf67ec2a
    Explore at:
    Dataset updated
    Feb 6, 2024
    Dataset authored and provided by
    City of Seattle ArcGIS Online
    Area covered
    Description

    U.S. Census Bureau 2020 block groups within the City of Seattle with American Community Survey (ACS) 5-year series data of frequently requested topics. Data is pulled from block group tables for the most recent ACS vintage. Seattle neighborhood geography of Council Districts, Comprehensive Plan Growth Areas are also included based on block group assignment.The census block groups have been assigned to a neighborhood based on the distribution of the total population from the 2020 decennial census for the component census blocks. If the majority of the population in the block group were inside the boundaries of the neighborhood, the block group was assigned wholly to that neighborhood.Feature layer created for and used in the Neighborhood Profiles application.The attribute data associated with this map is updated annually to contain the most currently released American Community Survey (ACS) 5-year data and contains estimates and margins of error. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Vintages: 2023ACS Table(s): Select fields from the tables listed here.Data downloaded from: Census Bureau's Explore Census Data The 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 US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). 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 erased for cartographic and mapping purposes. For census tracts, 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 level 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 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 RicoCensus tracts with no population that occur in areas of water, such as oceans, 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., -4444...) have been set to null, with the exception of -5555... which has been set to zero. 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.

  8. c

    Population

    • data.clevelandohio.gov
    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    Updated Aug 21, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Cleveland | GIS (2023). Population [Dataset]. https://data.clevelandohio.gov/datasets/population/explore
    Explore at:
    Dataset updated
    Aug 21, 2023
    Dataset authored and provided by
    Cleveland | GIS
    License

    Open Database License (ODbL) v1.0https://www.opendatacommons.org/licenses/odbl/1.0/
    License information was derived automatically

    Area covered
    Description

    This layer shows total population count by sex and age group. This is shown by tract, county, and state boundaries. 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. This layer is symbolized to show the percentage of the population that are considered dependent (ages 65+ and <18). 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): B01001Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 7, 2023The 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. For more information about ACS layers, visit the FAQ. 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 is 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, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). 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 erased for cartographic and mapping purposes. For census tracts, 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 level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2022 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. 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 RicoCensus tracts with no population that occur in areas of water, such as oceans, 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., -4444...) have been set to null, with the exception of -5555... which has been set to zero. 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.

  9. u

    American Community Survey

    • gstore.unm.edu
    csv, geojson, gml +5
    Updated Mar 6, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Earth Data Analysis Center (2020). American Community Survey [Dataset]. https://gstore.unm.edu/apps/rgis/datasets/92f102fa-5d6c-41b6-8cf9-132f78a30e02/metadata/FGDC-STD-001-1998.html
    Explore at:
    csv(5), zip(5), json(5), gml(5), geojson(5), xls(5), shp(5), kml(5)Available download formats
    Dataset updated
    Mar 6, 2020
    Dataset provided by
    Earth Data Analysis Center
    Time period covered
    2017
    Area covered
    New Mexico, West Bounding Coordinate -109.050173 East Bounding Coordinate -103.001964 North Bounding Coordinate 37.000293 South Bounding Coordinate 31.332172
    Description

    A broad and generalized selection of 2013-2017 US Census Bureau 2017 5-year American Community Survey population data estimates, obtained via Census API and joined to the appropriate geometry (in this case, New Mexico Census tracts). The selection is not comprehensive, but allows a first-level characterization of total population, male and female, and both broad and narrowly-defined age groups. In addition to the standard selection of age-group breakdowns (by male or female), the dataset provides supplemental calculated fields which combine several attributes into one (for example, the total population of persons under 18, or the number of females over 65 years of age). The determination of which estimates to include was based upon level of interest and providing a manageable dataset for users.The U.S. Census Bureau's American Community Survey (ACS) is a nationwide, continuous survey designed to provide communities with reliable and timely demographic, housing, social, and economic data every year. The ACS collects long-form-type information throughout the decade rather than only once every 10 years. The ACS combines population or housing data from multiple years to produce reliable numbers for small counties, neighborhoods, and other local areas. To provide information for communities each year, the ACS provides 1-, 3-, and 5-year estimates. ACS 5-year estimates (multiyear estimates) are “period” estimates that represent data collected over a 60-month period of time (as opposed to “point-in-time” estimates, such as the decennial census, that approximate the characteristics of an area on a specific date). ACS data are released in the year immediately following the year in which they are collected. ACS estimates based on data collected from 2009–2014 should not be called “2009” or “2014” estimates. Multiyear estimates should be labeled to indicate clearly the full period of time. While the ACS contains margin of error (MOE) information, this dataset does not. Those individuals requiring more complete data are directed to download the more detailed datasets from the ACS American FactFinder website. This dataset is organized by Census tract boundaries in New Mexico. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

  10. o

    Agriculture; crops, livestock and land use by general farm type, region

    • data.overheid.nl
    • open.staging.dexspace.nl
    • +3more
    atom, json
    Updated Mar 28, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Centraal Bureau voor de Statistiek (Rijk) (2025). Agriculture; crops, livestock and land use by general farm type, region [Dataset]. https://data.overheid.nl/dataset/3940-agriculture--crops--livestock-and-land-use-by-general-farm-type--region
    Explore at:
    json(KB), atom(KB)Available download formats
    Dataset updated
    Mar 28, 2025
    Dataset provided by
    Centraal Bureau voor de Statistiek (Rijk)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    This table contains data on land use, arable farming, horticulture, grassland, grazing livestock and housed animals, at regional level, by general farm type.

    The figures in this table are derived from the agricultural census. Data collection for the agricultural census is part of a combined data collection for a.o. agricultural policy use and enforcement of the manure law.

    Regional breakdown is based on the main location of the holding. Due to this the region where activities (crops, animals) are allocated may differ from the location where these activities actually occur.

    The agricultural census is also used as the basis for the European Farm Structure Survey (FSS). Data from the agricultural census do not fully coincide with the FSS. In the FSS years (2000, 2003, 2005, 2007 and 2010) additional information was collected to meet the requirements of the FSS.

    Reference date for livestock is 1 April and for crops 15 May.

    In 2022, equidae are not part of the Agricultural Census. This affects the farm type and the total number of farms in the Agricultural Census. Farms with horses, ponies and donkeys that were previously classified as ‘specialist grazing livestock' could be classified, according to their dominant activity, as another farm type in 2022.

    From 2020 onwards, the SO2017, based on the years 2015 to 2019, will apply (see also the explanation for SO: Standard Output).

    From 2018 onwards the number of calves for fattening, pigs for fattening, chicken and turkey are adjusted in the case of temporary breaks in the production cycle (e.g. sanitary cleaning). The agricultural census is a structural survey, in which adjustment for temporary breaks in the production cycle is a.o. relevant for the calculation of the economic size of the holding, and its farm type. In the livestock surveys the number of animals on the reference day is relevant, therefore no adjustment for temporary breaks in the production cycle are made. This means that the number of animals in the tables of the agricultural census may differ from those in the livestock tables (see ‘links to relevant tables and relevant articles).

    From 2017 onwards, animal numbers are increasingly derived from I&R registers (Identification and Registration of animals), instead of by means of the combined data collection. The I&R registers are the responsibility of RVO (Netherlands Enterprise Agency). Since 2017, cattle numbers are derived from I&R cattle, and from 2018 sheep, goats and poultry are also derived from the relevant I&R registers. The registration of cattle, sheep and goats takes place directly at RVO. Poultry data is collected via the designated database Poultry Information System Poultry (KIP) from Avined. Avined is a branch organization for the egg and poultry meat sectors. Avined passes the data on to the central database of RVO. Due to the transition to the use of I&R registers, a change in classification will occur for sheep and goats from 2018 onwards.

    Since 2016, information of the Dutch Business Register is used to define the agricultural census. Registration in the Business Register with an agricultural standard industrial classification code (SIC), related to NACE/ISIC, (in Dutch SBI: ‘Standaard BedrijfsIndeling’) is leading to determine whether there is an agricultural holding. This aligns the agricultural census as closely as possible to the statistical regulations of Eurostat and the (Dutch) implementation of the definition of 'active farmer' as described in the common agricultural policy.

    The definition of the agricultural census based on information from the Dutch Business Register mainly affects the number of holdings, a clear deviation of the trend occurs. The impact on areas (except for other land and rough grazing) and the number of animals (except for sheep, horses and ponies) is limited. This is mainly due to the holdings that are excluded as a result of the new delimitation of agricultural holdings (such as equestrian centres, city farms and organisations in nature management).

    In 2011 there were changes in geographic assignment of holdings with a foreign main seat. This may influence regional figures, mainly in border regions.

    Until 2010 the economic size of agricultural holdings was expressed in Dutch size units (in Dutch NGE: 'Nederlandse Grootte Eenheid'). From 2010 onwards this has become Standard Output (SO). This means that the threshold for holdings in the agricultural census has changed from 3 NGE to 3000 euro SO. For comparable time series the figures for 2000 up to and including 2009 have been recalculated, based on SO coefficients and SO typology. The latest update took place in 2016.

    Data available from: 2000

    Status of the figures: The figures are final.

    Changes as of March 28, 2025: the final figures for 2024 have been added.

    When will new figures be published? According to regular planning provisional figures are published in November and the definite figures will follow in March of the following year.

  11. d

    COVID-19 Vaccinations by Census Tract - ARCHIVED

    • catalog.data.gov
    • data.ct.gov
    Updated Aug 12, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    data.ct.gov (2023). COVID-19 Vaccinations by Census Tract - ARCHIVED [Dataset]. https://catalog.data.gov/dataset/covid-19-vaccinations-by-census-tract-3a35f
    Explore at:
    Dataset updated
    Aug 12, 2023
    Dataset provided by
    data.ct.gov
    Description

    NOTE: As of 2/16/2023, this page is not being updated. For data on updated (bivalent) COVID-19 booster vaccination click here: https://app.powerbigov.us/view?r=eyJrIjoiODNhYzVkNGYtMzZkMy00YzA3LWJhYzUtYTVkOWFlZjllYTVjIiwidCI6IjExOGI3Y2ZhLWEzZGQtNDhiOS1iMDI2LTMxZmY2OWJiNzM4YiJ9 This table shows the number and percent of people that have initiated COVID-19 vaccination and are fully vaccinated by CT census tract (including residents of all ages). It also shows the number of people who have not received vaccine and who are not yet fully vaccinated. All data in this report are preliminary; data for previous dates will be updated as new reports are received and data errors are corrected. A person who has received at least one dose of any vaccine is considered to have initiated vaccination. A person is considered fully vaccinated if they have completed a primary series by receiving 2 doses of the Pfizer, Novavax or Moderna vaccines or 1 dose of the Johnson & Johnson vaccine. The fully vaccinated are a subset of the number who have received at least one dose. The percent with at least one dose many be over-estimated and the percent fully vaccinated may be under-estimated because of vaccine administration records for individuals that cannot be linked because of differences in how names or date of birth are reported. Population data obtained from the 2019 Census ACS (www.census.gov) Geocoding is used to determine the census tract in which a person lives. People for who a census tract cannot be determined based on available address data are not included in this table. DPH recommends that these data are primarily used to identify areas that require additional attention rather than to establish and track the exact level of vaccine coverage. Census tract coverage estimates can play an important role in planning and evaluating vaccination strategies. However, inaccuracies in the data that are inherent to population surveillance may be magnified when analyses are performed down to the census tract level. We make every effort to provide accurate data, but inaccuracies may result from things like incomplete or inaccurate addresses, duplicate records, and sampling error in the American Community Survey that is used to estimate census tract population size and composition. These things may result in overestimates or underestimates of vaccine coverage. Some census tracts are suppressed. This is done if the number of people vaccinated is less than 5 or if the census population estimate is considered unreliable (coefficient of variance > 30%). Coverage estimates over 100% are shown as 100%. Connecticut COVID-19 Vaccine Program providers are required to report information on all COVID-19 vaccine doses administered to CT WiZ, the Connecticut Immunization Information System. Data on doses administered to CT residents out-of-state are being added to CT WiZ jurisdiction-by-jurisdiction. Doses administered by some Federal entities (including Department of Defense, Department of Correction, Department of Veteran’s Affairs, Indian Health Service) are not yet reported to CT WiZ. Data reported here reflect the vaccination records currently reported to CT WiZ. Caution should be used when interpreting coverage estimates in towns with large college/university populations since coverage may be underestimated. In the census, college/university students who live on or just off campus would be counted in the college/university town. However, if a student was vaccinated while studying remotely in his/her hometown, the student may be counted as a vaccine recipient in that town. As part of continuous data quality improvement efforts, duplicate records were removed from the COVID-19 vaccination data during the weeks of 4/19/2021 and 4/26/2021. As of 1/13/2021, census tract level data are provider by town for all ages. Data by age group is no longer available.

  12. a

    Selected Demographic and Housing Estimates (DP05)

    • data-seattlecitygis.opendata.arcgis.com
    • data.seattle.gov
    Updated Aug 11, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Seattle ArcGIS Online (2023). Selected Demographic and Housing Estimates (DP05) [Dataset]. https://data-seattlecitygis.opendata.arcgis.com/datasets/SeattleCityGIS::selected-demographic-and-housing-estimates-dp05
    Explore at:
    Dataset updated
    Aug 11, 2023
    Dataset authored and provided by
    City of Seattle ArcGIS Online
    Description

    Data from: American Community Survey, 5-year SeriesKing County, Washington census tracts with nonoverlapping vintages of the 5-year American Community Survey (ACS) estimates starting in 2010 from the U.S. Census Bureau's demographic and housing estimates (DP05). Also includes the most recent release annually with the vintage identified in the "ACS Vintage" field.The census tract boundaries match the vintage of the ACS data (currently 2010 and 2020) so please note the geographic changes between the decades. Tracts have been coded as being within the City of Seattle as well as assigned to neighborhood groups called "Community Reporting Areas". These areas were created after the 2000 census to provide geographically consistent neighborhoods through time for reporting U.S. Census Bureau data. This is not an attempt to identify neighborhood boundaries as defined by neighborhoods themselves.Vintages: 2010, 2015, 2020, 2021, 2022, 2023ACS Table(s): DP05Data downloaded from: Census Bureau's Explore Census Data The 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 US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). 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 erased for cartographic and mapping purposes. For census tracts, 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 level 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 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 RicoCensus tracts with no population that occur in areas of water, such as oceans, 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., -4444...) have been set to null, with the exception of -5555... which has been set to zero. 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.

  13. undefined undefined: undefined | undefined (undefined)

    • data.virginia.gov
    • data.census.gov
    Updated Apr 26, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    United States Census Bureau (2024). undefined undefined: undefined | undefined (undefined) [Dataset]. https://data.virginia.gov/gl/dataset/census-bureau-household-size-by-vehicles-available/resource/5c268dc5-e1bf-47cf-a0b3-099276694bc3
    Explore at:
    Dataset updated
    Apr 26, 2024
    Dataset provided by
    United States Census Bureauhttp://census.gov/
    License

    CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
    License information was derived automatically

    Description

    Although the American Community Survey (ACS) produces population, demographic and housing unit estimates, it is the Census Bureau's Population Estimates Program that produces and disseminates the official estimates of the population for the nation, states, counties, cities, and towns and estimates of housing units for states and counties..Supporting documentation on code lists, subject definitions, data accuracy, and statistical testing can be found on the American Community Survey website in the Technical Documentation section.Sample size and data quality measures (including coverage rates, allocation rates, and response rates) can be found on the American Community Survey website in the Methodology section..Source: U.S. Census Bureau, 2019 American Community Survey 1-Year Estimates.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 roughly 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 ACS Technical Documentation). The effect of nonsampling error is not represented in these tables..Workers include members of the Armed Forces and civilians who were at work last week..The 2019 American Community Survey (ACS) data generally reflect the September 2018 Office of Management and Budget (OMB) delineations of metropolitan and micropolitan statistical areas. In certain instances the names, codes, and boundaries of the principal cities shown in ACS tables may differ from the OMB delineations due to differences in the effective dates of the geographic entities..Estimates of urban and rural populations, housing units, and characteristics reflect boundaries of urban areas defined based on Census 2010 data. As a result, data for urban and rural areas from the ACS do not necessarily reflect the results of ongoing urbanization..Explanation of Symbols:An "**" entry in 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.An "-" entry in the estimate column indicates that 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, or the margin of error associated with a median was larger than the median itself.An "-" following a median estimate means the median falls in the lowest interval of an open-ended distribution.An "+" following a median estimate means the median falls in the upper interval of an open-ended distribution.An "***" entry in the margin of error column indicates that the median falls in the lowest interval or upper interval of an open-ended distribution. A statistical test is not appropriate.An "*****" entry in the margin of error column indicates that the estimate is controlled. A statistical test for sampling variability is not appropriate. An "N" entry in the estimate and margin of error columns indicates that data for this geographic area cannot be displayed because the number of sample cases is too small.An "(X)" means that the estimate is not applicable or not available.

  14. w

    R2 & NE: Block Group Level 2006-2010 ACS Population Summary

    • data.wu.ac.at
    tgrshp (compressed)
    Updated Jan 13, 2018
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Environmental Protection Agency (2018). R2 & NE: Block Group Level 2006-2010 ACS Population Summary [Dataset]. https://data.wu.ac.at/odso/data_gov/MDllYzM1ZDktNTk5MS00MTk5LThkYzYtNTU3MzRiNWJkMjU5
    Explore at:
    tgrshp (compressed)Available download formats
    Dataset updated
    Jan 13, 2018
    Dataset provided by
    U.S. Environmental Protection Agency
    License

    U.S. Government Workshttps://www.usa.gov/government-works
    License information was derived automatically

    Area covered
    03894b011bd08c1bbe3251854fa7524ce8fd568a
    Description

    The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.

    This table contains data on race, age, sex, and marital status from the American Community Survey 2006-2010 database for block groups. The American Community Survey (ACS) is a household survey conducted by the U.S. Census Bureau that currently has an annual sample size of about 3.5 million addresses. ACS estimates provides communities with the current information they need to plan investments and services. Information from the survey generates estimates that help determine how more than $400 billion in federal and state funds are distributed annually. Each year the survey produces data that cover the periods of 1-year, 3-year, and 5-year estimates for geographic areas in the United States and Puerto Rico, ranging from neighborhoods to Congressional districts to the entire nation. This table also has a companion table (Same table name with MOE Suffix) with the margin of error (MOE) values for each estimated element. MOE is expressed as a measure value for each estimated element. So a value of 25 and an MOE of 5 means 25 +/- 5 (or statistical certainty between 20 and 30). There are also special cases of MOE. An MOE of -1 means the associated estimates do not have a measured error. An MOE of 0 means that error calculation is not appropriate for the associated value. An MOE of 109 is set whenever an estimate value is 0. The MOEs of aggregated elements and percentages must be calculated. This process means using standard error calculations as described in "American Community Survey Multiyear Accuracy of the Data (3-year 2008-2010 and 5-year 2006-2010)". Also, following Census guidelines, aggregated MOEs do not use more than 1 0-element MOE (109) to prevent over estimation of the error. Due to the complexity of the calculations, some percentage MOEs cannot be calculated (these are set to null in the summary-level MOE tables).

    The name for table 'ACS10POPBGMOE' was added as a prefix to all field names imported from that table. Be sure to turn off 'Show Field Aliases' to see complete field names in the Attribute Table of this feature layer. This can be done in the 'Table Options' drop-down menu in the Attribute Table or with key sequence '[CTRL]+[SHIFT]+N'. Due to database restrictions, the prefix may have been abbreviated if the field name exceded the maximum allowed characters.

  15. a

    LANGUAGE SPOKEN AT HOME FOR THE POPULATION 5 YEARS AND OVER (C16001)

    • data-seattlecitygis.opendata.arcgis.com
    • hub.arcgis.com
    Updated Sep 3, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Seattle ArcGIS Online (2023). LANGUAGE SPOKEN AT HOME FOR THE POPULATION 5 YEARS AND OVER (C16001) [Dataset]. https://data-seattlecitygis.opendata.arcgis.com/datasets/SeattleCityGIS::language-spoken-at-home-for-the-population-5-years-and-over-c16001
    Explore at:
    Dataset updated
    Sep 3, 2023
    Dataset authored and provided by
    City of Seattle ArcGIS Online
    Description

    Table from the American Community Survey (ACS) C16001 of language spoken at home for the population 5 years and over. These are multiple, nonoverlapping vintages of the 5-year ACS estimates of population and housing attributes starting in 2010 shown by the corresponding census tract vintage. Also includes the most recent release annually.King County, Washington census tracts with nonoverlapping vintages of the 5-year American Community Survey (ACS) estimates starting in 2010. Vintage identified in the "ACS Vintage" field.The census tract boundaries match the vintage of the ACS data (currently 2010 and 2020) so please note the geographic changes between the decades. Tracts have been coded as being within the City of Seattle as well as assigned to neighborhood groups called "Community Reporting Areas". These areas were created after the 2000 census to provide geographically consistent neighborhoods through time for reporting U.S. Census Bureau data. This is not an attempt to identify neighborhood boundaries as defined by neighborhoods themselves.Vintages: 2010, 2015, 2020, 2021, 2022, 2023ACS Table(s): C16001Data downloaded from: Census Bureau's Explore Census Data The 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 US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). 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 erased for cartographic and mapping purposes. For census tracts, 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 level 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 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 RicoCensus tracts with no population that occur in areas of water, such as oceans, 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., -4444...) have been set to null, with the exception of -5555... which has been set to zero. 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.

  16. D

    ARCHIVED: COVID-19 Cases by Population Characteristics Over Time

    • data.sfgov.org
    • healthdata.gov
    • +1more
    application/rdfxml +5
    Updated Jun 8, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2021). ARCHIVED: COVID-19 Cases by Population Characteristics Over Time [Dataset]. https://data.sfgov.org/Health-and-Social-Services/ARCHIVED-COVID-19-Cases-by-Population-Characterist/j7i3-u9ke
    Explore at:
    xml, csv, json, application/rdfxml, tsv, application/rssxmlAvailable download formats
    Dataset updated
    Jun 8, 2021
    License

    ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
    License information was derived automatically

    Description

    A. SUMMARY This archived dataset includes data for population characteristics that are no longer being reported publicly. The date on which each population characteristic type was archived can be found in the field “data_loaded_at”.

    B. HOW THE DATASET IS CREATED Data on the population characteristics of COVID-19 cases are from:  * Case interviews  * Laboratories  * Medical providers    These multiple streams of data are merged, deduplicated, and undergo data verification processes.  

    Race/ethnicity * We include all race/ethnicity categories that are collected for COVID-19 cases. * The population estimates for the "Other" or “Multi-racial” groups should be considered with caution. The Census definition is likely not exactly aligned with how the City collects this data. For that reason, we do not recommend calculating population rates for these groups.

    Gender * The City collects information on gender identity using these guidelines.

    Skilled Nursing Facility (SNF) occupancy * A Skilled Nursing Facility (SNF) is a type of long-term care facility that provides care to individuals, generally in their 60s and older, who need functional assistance in their daily lives.  * This dataset includes data for COVID-19 cases reported in Skilled Nursing Facilities (SNFs) through 12/31/2022, archived on 1/5/2023. These data were identified where “Characteristic_Type” = ‘Skilled Nursing Facility Occupancy’.

    Sexual orientation * The City began asking adults 18 years old or older for their sexual orientation identification during case interviews as of April 28, 2020. Sexual orientation data prior to this date is unavailable. * The City doesn’t collect or report information about sexual orientation for persons under 12 years of age. * Case investigation interviews transitioned to the California Department of Public Health, Virtual Assistant information gathering beginning December 2021. The Virtual Assistant is only sent to adults who are 18+ years old. https://www.sfdph.org/dph/files/PoliciesProcedures/COM9_SexualOrientationGuidelines.pdf">Learn more about our data collection guidelines pertaining to sexual orientation.

    Comorbidities * Underlying conditions are reported when a person has one or more underlying health conditions at the time of diagnosis or death.

    Homelessness Persons are identified as homeless based on several data sources: * self-reported living situation * the location at the time of testing * Department of Public Health homelessness and health databases * Residents in Single-Room Occupancy hotels are not included in these figures. These methods serve as an estimate of persons experiencing homelessness. They may not meet other homelessness definitions.

    Single Room Occupancy (SRO) tenancy * SRO buildings are defined by the San Francisco Housing Code as having six or more "residential guest rooms" which may be attached to shared bathrooms, kitchens, and living spaces. * The details of a person's living arrangements are verified during case interviews.

    Transmission Type * Information on transmission of COVID-19 is based on case interviews with individuals who have a confirmed positive test. Individuals are asked if they have been in close contact with a known COVID-19 case. If they answer yes, transmission category is recorded as contact with a known case. If they report no contact with a known case, transmission category is recorded as community transmission. If the case is not interviewed or was not asked the question, they are counted as unknown.

    C. UPDATE PROCESS This dataset has been archived and will no longer update as of 9/11/2023.

    D. HOW TO USE THIS DATASET Population estimates are only available for age groups and race/ethnicity categories. San Francisco population estimates for race/ethnicity and age groups can be found in a view based on the San Francisco Population and Demographic Census dataset. These population estimates are from the 2016-2020 5-year American Community Survey (ACS).

    This dataset includes many different types of characteristics. Filter the “Characteristic Type” column to explore a topic area. Then, the “Characteristic Group” column shows each group or category within that topic area and the number of cases on each date.

    New cases are the count of cases within that characteristic group where the positive tests were collected on that specific specimen collection date. Cumulative cases are the running total of all San Francisco cases in that characteristic group up to the specimen collection date listed.

    This data may not be immediately available for recently reported cases. Data updates as more information becomes available.

    To explore data on the total number of cases, use the ARCHIVED: COVID-19 Cases Over Time dataset.

    E. CHANGE LOG

    • 9/11/2023 - data on COVID-19 cases by population characteristics over time are no longer being updated. The date on which each population characteristic type was archived can be found in the field “data_loaded_at”.
    • 6/6/2023 - data on cases by transmission type have been removed. See section ARCHIVED DATA for more detail.
    • 5/16/2023 - data on cases by sexual orientation, comorbidities, homelessness, and single room occupancy have been removed. See section ARCHIVED DATA for more detail.
    • 4/6/2023 - the State implemented system updates to improve the integrity of historical data.
    • 2/21/2023 - system updates to improve reliability and accuracy of cases data were implemented.
    • 1/31/2023 - updated “population_estimate” column to reflect the 2020 Census Bureau American Community Survey (ACS) San Francisco Population estimates.
    • 1/5/2023 - data on SNF cases removed. See section ARCHIVED DATA for more detail.
    • 3/23/2022 - ‘Native American’ changed to ‘American Indian or Alaska Native’ to align with the census.
    • 1/22/2022 - system updates to improve timeliness and accuracy of cases and deaths data were implemented.
    • 7/15/2022 - reinfections added to cases dataset. See section SUMMARY for more information on how reinfections are identified.

  17. d

    Hazard Mitigation and Capacity in Utah Census Places

    • search.dataone.org
    • hydroshare.org
    • +1more
    Updated Dec 5, 2021
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Matthew Wheelwright (2021). Hazard Mitigation and Capacity in Utah Census Places [Dataset]. https://search.dataone.org/view/sha256%3A53553db07527f46d88b4709cc347747e9f5b2a3f2827b4818a50d9cf152aedfa
    Explore at:
    Dataset updated
    Dec 5, 2021
    Dataset provided by
    Hydroshare
    Authors
    Matthew Wheelwright
    Time period covered
    Jan 1, 2015 - Dec 31, 2015
    Area covered
    Description

    This dataset contains important categories (per an extensive literature review) in relation to vulnerability to water hazards within Utah at the Census Place level (i.e. cities). Although social and physical vulnerability to water hazards (i.e. flooding) data has been collected extensively in many coastal areas, this is a costly problem in Utah and many other non-coastal regions. The variables shown here are categorized by type and collection method. 1. General data is shown for all Census Places in Utah including County, Geocode, and Total Population. These are taken from the 2010 Census. 2. Literature suggests that there are various approaches which local governments take to mitigate the impacts of flood events. Indicators of these approaches are captured in the section entitled Web Survey. A web survey was conducted of each and every census place in Utah. The data includes evaluations of content including water hazard education, land use restrictions described in the code, freeboard requirements, and emergency operations plan implementations. 3. Information about the local government including their planning and building inspector staff was collected using a phone survey along with emails and website investigations. 4. FEMA data was consolidated from FEMA's website showing census places with current insurance premium discounts achieved by demonstrating compliance with certain federal requirements. It also includes data on policies and losses. 5. A social vulnerability index was created by our team for this project and details can be found here: http://repository.iutahepscor.org/dataset/social-vulnerability-at-the-census-place-level. This dataset includes summary findings from the SoVI index. 6. As housing is recognized in the literature as a contributer to natural hazard vulnerability, important housing statistics were defined and created from Census data. These include housing age, median value, and renter occupied statistics. A standardized rating of building code effectiveness is also included from a recent Utah Hazard Mitigation Report. 7. Event data is summarized for number of events and estimated monetary damages from another of our team's datasets found here: http://repository.iutahepscor.org/dataset/noaa-storm-events. This NOAA dataset helps us understand the nature of past experience and physical exposure to water hazards. 8. As this dataset is focused on water hazard exposure, two measurements were calculated for each census place reflecting the percentage area of the city included in the defined special flood hazard area.

    Together these data paint a picture of Utah's vulnerabilities to flood hazards and potential exposure to other natural hazard events. County level statistics were also collected and add insight at that spatial scale. they can be found here: http://repository.iutahepscor.org/dataset/utah-s-counties-sensitivity-to-water-hazards. The variables are different as prescribed in the readme file there.

    Further details of the data collection methods can be found in the data dictionary within the spreadsheet workbook or in the ReadMe file included as a resource here.

  18. a

    Justice40 Disadvantaged or Partially Disadvantaged Tracts by Race/Ethnicity...

    • atlas-connecteddmv.hub.arcgis.com
    • regionaldatahub-brag.hub.arcgis.com
    • +1more
    Updated Jun 10, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    ArcGIS Living Atlas Team (2022). Justice40 Disadvantaged or Partially Disadvantaged Tracts by Race/Ethnicity (Archive) [Dataset]. https://atlas-connecteddmv.hub.arcgis.com/maps/945b3f2e39a64569ab2d0700a527361b
    Explore at:
    Dataset updated
    Jun 10, 2022
    Dataset authored and provided by
    ArcGIS Living Atlas Team
    Area covered
    Description

    This map uses an archive of Version 1.0 of the CEJST data as a fully functional GIS layer. See an archive of the latest version of the CEJST tool using Version 2.0 of the data released in December 2024 here.This map shows Census tracts throughout the US based on if they are considered disadvantaged or partially disadvantaged according to Justice40 Initiative criteria. This is overlaid with the most recent American Community Survey (ACS) figures from the U.S. Census Bureau to communicate the predominant race that lives within these disadvantaged or partially disadvantaged tracts. Predominance helps us understand the group of population which has the largest count within an area. Colors are more transparent if the predominant race has a similar count to another race/ethnicity group. The colors on the map help us better understand the predominant race or ethnicity:Hispanic or LatinoWhite Alone, not HispanicBlack or African American Alone, not HispanicAsian Alone, not HispanicAmerican Indian and Alaska Native Alone, not HispanicTwo or more races, not HispanicNative Hawaiian and Other Pacific Islander, not HispanicSome other race, not HispanicSearch for any region, city, or neighborhood throughout the US, DC, and Puerto Rico to learn more about the population in the disadvantaged tracts. Click on any tract to learn more. Zoom to your area, filter to your county or state, and save this web map focused on your area to share the pattern with others. You can also use this web map within an ArcGIS app such as a dashboard, instant app, or story. This map uses these hosted feature layers containing the most recent American Community Survey data. These layers are part of the ArcGIS Living Atlas, and are updated every year when the American Community Survey releases new estimates, so values in the map always reflect the newest data available.Note: Justice40 tracts use 2010-based boundaries, while the most recent ACS figures are offered on 2020-based boundaries. When you click on an area, there will be multiple pop-ups returned due to the differences in these boundaries. From Justice40 data source:"Census tract geographical boundaries are determined by the U.S. Census Bureau once every ten years. This tool utilizes the census tract boundaries from 2010 because they match the datasets used in the tool. The U.S. Census Bureau will update these tract boundaries in 2020.Under the current formula, a census tract will be identified as disadvantaged in one or more categories of criteria:IF the tract is above the threshold for one or more environmental or climate indicators AND the tract is above the threshold for the socioeconomic indicatorsCommunities are identified as disadvantaged by the current version of the tool for the purposes of the Justice40 Initiative if they are located in census tracts that are at or above the combined thresholds in one or more of eight categories of criteria.The goal of the Justice40 Initiative is to provide 40 percent of the overall benefits of certain Federal investments in [eight] key areas to disadvantaged communities. These [eight] key areas are: climate change, clean energy and energy efficiency, clean transit, affordable and sustainable housing, training and workforce development, the remediation and reduction of legacy pollution, [health burdens] and the development of critical clean water infrastructure." Source: Climate and Economic Justice Screening toolPurpose"Sec. 219. Policy. To secure an equitable economic future, the United States must ensure that environmental and economic justice are key considerations in how we govern. That means investing and building a clean energy economy that creates well‑paying union jobs, turning disadvantaged communities — historically marginalized and overburdened — into healthy, thriving communities, and undertaking robust actions to mitigate climate change while preparing for the impacts of climate change across rural, urban, and Tribal areas. Agencies shall make achieving environmental justice part of their missions by developing programs, policies, and activities to address the disproportionately high and adverse human health, environmental, climate-related and other cumulative impacts on disadvantaged communities, as well as the accompanying economic challenges of such impacts. It is therefore the policy of my Administration to secure environmental justice and spur economic opportunity for disadvantaged communities that have been historically marginalized and overburdened by pollution and underinvestment in housing, transportation, water and wastewater infrastructure, and health care." Source: Executive Order on Tackling the Climate Crisis at Home and AbroadUse of this Data"The pilot identifies 21 priority programs to immediately begin enhancing benefits for disadvantaged communities. These priority programs will provide a blueprint for other agencies to help inform their work to implement the Justice40 Initiative across government." Source: The Path to Achieving Justice 40

  19. [Archived] COVID-19 Deaths by Population Characteristics Over Time

    • healthdata.gov
    • data.sfgov.org
    • +1more
    application/rdfxml +5
    Updated Apr 8, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    data.sfgov.org (2025). [Archived] COVID-19 Deaths by Population Characteristics Over Time [Dataset]. https://healthdata.gov/dataset/-Archived-COVID-19-Deaths-by-Population-Characteri/hs5f-amst
    Explore at:
    csv, json, xml, application/rssxml, tsv, application/rdfxmlAvailable download formats
    Dataset updated
    Apr 8, 2025
    Dataset provided by
    data.sfgov.org
    Description

    As of July 2nd, 2024 the COVID-19 Deaths by Population Characteristics Over Time dataset has been retired. This dataset is archived and will no longer update. We will be publishing a cumulative deaths by population characteristics dataset that will update moving forward.

    A. SUMMARY This dataset shows San Francisco COVID-19 deaths by population characteristics and by date. This data may not be immediately available for recently reported deaths. Data updates as more information becomes available. Because of this, death totals for previous days may increase or decrease. More recent data is less reliable.

    Population characteristics are subgroups, or demographic cross-sections, like age, race, or gender. The City tracks how deaths have been distributed among different subgroups. This information can reveal trends and disparities among groups.

    B. HOW THE DATASET IS CREATED As of January 1, 2023, COVID-19 deaths are defined as persons who had COVID-19 listed as a cause of death or a significant condition contributing to their death on their death certificate. This definition is in alignment with the California Department of Public Health and the national https://preparedness.cste.org/wp-content/uploads/2022/12/CSTE-Revised-Classification-of-COVID-19-associated-Deaths.Final_.11.22.22.pdf">Council of State and Territorial Epidemiologists. Death certificates are maintained by the California Department of Public Health.

    Data on the population characteristics of COVID-19 deaths are from: *Case reports *Medical records *Electronic lab reports *Death certificates

    Data are continually updated to maximize completeness of information and reporting on San Francisco COVID-19 deaths.

    To protect resident privacy, we summarize COVID-19 data by only one characteristic at a time. Data are not shown until cumulative citywide deaths reach five or more.

    Data notes on each population characteristic type is listed below.

    Race/ethnicity * We include all race/ethnicity categories that are collected for COVID-19 cases.

    Gender * The City collects information on gender identity using these guidelines.

    C. UPDATE PROCESS Updates automatically at 06:30 and 07:30 AM Pacific Time on Wednesday each week.

    Dataset will not update on the business day following any federal holiday.

    D. HOW TO USE THIS DATASET Population estimates are only available for age groups and race/ethnicity categories. San Francisco population estimates for race/ethnicity and age groups can be found in a view based on the San Francisco Population and Demographic Census dataset. These population estimates are from the 2016-2020 5-year American Community Survey (ACS).

    This dataset includes many different types of characteristics. Filter the “Characteristic Type” column to explore a topic area. Then, the “Characteristic Group” column shows each group or category within that topic area and the number of deaths on each date.

    New deaths are the count of deaths within that characteristic group on that specific date. Cumulative deaths are the running total of all San Francisco COVID-19 deaths in that characteristic group up to the date listed.

    This data may not be immediately available for more recent deaths. Data updates as more information becomes available.

    To explore data on the total number of deaths, use the COVID-19 Deaths Over Time dataset.

    E. CHANGE LOG

    • 9/11/2023 - on this date, we began using an updated definition of a COVID-19 death to align with the California Department o

  20. d

    COVID-19 Deaths by Population Characteristics

    • catalog.data.gov
    • data.sfgov.org
    • +3more
    Updated May 24, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    data.sfgov.org (2025). COVID-19 Deaths by Population Characteristics [Dataset]. https://catalog.data.gov/dataset/covid-19-deaths-by-population-characteristics
    Explore at:
    Dataset updated
    May 24, 2025
    Dataset provided by
    data.sfgov.org
    Description

    A. SUMMARY This dataset shows San Francisco COVID-19 deaths by population characteristics. This data may not be immediately available for recently reported deaths. Data updates as more information becomes available. Because of this, death totals may increase or decrease. Population characteristics are subgroups, or demographic cross-sections, like age, race, or gender. The City tracks how deaths have been distributed among different subgroups. This information can reveal trends and disparities among groups. B. HOW THE DATASET IS CREATED As of January 1, 2023, COVID-19 deaths are defined as persons who had COVID-19 listed as a cause of death or a significant condition contributing to their death on their death certificate. This definition is in alignment with the California Department of Public Health and the national Council of State and Territorial Epidemiologists. Death certificates are maintained by the California Department of Public Health. Data on the population characteristics of COVID-19 deaths are from: Case reports Medical records Electronic lab reports Death certificates Data are continually updated to maximize completeness of information and reporting on San Francisco COVID-19 deaths. To protect resident privacy, we summarize COVID-19 data by only one population characteristic at a time. Data are not shown until cumulative citywide deaths reach five or more. Data notes on select population characteristic types are listed below. Race/ethnicity * We include all race/ethnicity categories that are collected for COVID-19 cases. Gender * The City collects information on gender identity using these guidelines. C. UPDATE PROCESS Updates automatically at 06:30 and 07:30 AM Pacific Time on Wednesday each week. Dataset will not update on the business day following any federal holiday. D. HOW TO USE THIS DATASET Population estimates are only available for age groups and race/ethnicity categories. San Francisco population estimates for race/ethnicity and age groups can be found in a dataset based on the San Francisco Population and Demographic Census dataset.These population estimates are from the 2018-2022 5-year American Community Survey (ACS). This dataset includes several characteristic types. Filter the “Characteristic Type” column to explore a topic area. Then, the “Characteristic Group” column shows each group or category within that topic area and the number of cumulative deaths. Cumulative deaths are the running total of all San Francisco COVID-19 deaths in that characteristic group up to the date listed. To explore data on the total number of deaths, use the COVID-19 Deaths Over Time dataset. E. CHANGE LOG

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
data.cityofchicago.org (2025). ACS 5 Year Data by Community Area [Dataset]. https://catalog.data.gov/dataset/acs-5-year-data-by-community-area

ACS 5 Year Data by Community Area

Explore at:
Dataset updated
Jun 7, 2025
Dataset provided by
data.cityofchicago.org
Description

Selected variables from the most recent ACS Community Survey (Released 2023) aggregated by Community Area. Additional years will be added as they become available. The underlying algorithm to create the dataset calculates the % of a census tract that falls within the boundaries of a given community area. Given that census tracts and community area boundaries are not aligned, these figures should be considered an estimate. Total population in this dataset: 2,647,621 Total Chicago Population Per ACS 2023: 2,664,452 % Difference: -0.632% There are different approaches in common use for displaying Hispanic or Latino population counts. In this dataset, following the approach taken by the Census Bureau, a person who identifies as Hispanic or Latino will also be counted in the race category with which they identify. However, again following the Census Bureau data, there is also a column for White Not Hispanic or Latino. Code can be found here: https://github.com/Chicago/5-Year-ACS-Survey-Data Community Area Shapefile: https://data.cityofchicago.org/Facilities-Geographic-Boundaries/Boundaries-Community-Areas-current-/cauq-8yn6 Census Area Python Package Documentation: https://census-area.readthedocs.io/en/latest/index.html

Search
Clear search
Close search
Google apps
Main menu