Census Tracts from the 2020 US Census for New York City clipped to the shoreline. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. Because some census tracts are under water not all census tracts are contained in this file, only census tracts that are partially or totally located on land have been mapped in this file. All previously released versions of this data are available at the DCP Website: BYTES of the BIG APPLE.

Census Tracts from the 2020 US Census for New York City including portions under water. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. All previously released versions of this data are available at the DCP Website: BYTES of the BIG APPLE.

2020 Census Tracts from the US Census for New York City. These boundary files are derived from the US Census Bureau's TIGER data products and have been geographically modified to fit the New York City base map. All previously released versions of this data are available at BYTES of the BIG APPLE- Archive.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

2020 Census Tracts from the US Census for New York City. These boundary files are derived from the US Census Bureau's TIGER data products and have been geographically modified to fit the New York City base map. All previously released versions of this data are available at BYTES of the BIG APPLE- Archive.

Analysis of ‘2020 Census Tracts - Tabular’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/2114cf4d-ecc2-42a9-b9df-9245e71837b1 on 13 February 2022.

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

2020 Census Tracts from the US Census for New York City. These boundary files are derived from the US Census Bureau's TIGER data products and have been geographically modified to fit the New York City base map. All previously released versions of this data are available at BYTES of the BIG APPLE- Archive.

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

Analysis of ‘2010 Census Tracts (water areas included)’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/1879efb0-6ec3-4e0f-9054-9f7d539f8c9d on 13 February 2022.

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

2010 Census Tracts (water areas included) from the US Census for New York City. These boundary files are derived from the US Census Bureau's TIGER data products and have been geographically modified to fit the New York City base map. All previously released versions of this data are available at BYTES of the BIG APPLE- Archive.

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

Note: These layers were compiled by Esri's Demographics Team using data from the Census Bureau's American Community Survey. These data sets are not owned by the City of Rochester.Overview of the map/data: This map shows the percentage of the population living below the federal poverty level over the previous 12 months, shown by tract, county, and state boundaries. Estimates are from the 2018 ACS 5-year samples. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. Current Vintage: 2019-2023ACS Table(s): B17020, C17002Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer will be updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2010 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico.Census tracts with no population are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -555555...) have been set to null. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small. NOTE: any calculated percentages or counts that contain estimates that have null margins of error yield null margins of error for the calculated fields.

Dataset Summary About this data: This layer presents the USA 2020 Census tracts within the City of Rochester boundary. The geography is sourced from US Census Bureau 2020 TIGER FGDB (National Sub-State) and cut by the City of Rochester boundary. Data Dictionary: STATE_ABBR: The two-letter abbreviation for a state (such as NY). STATE_FIPS: The two-digit Federal Information Processing Standards (FIPS) code assigned to each US state. New York State is 36. COUNTY_FIP: The three-digit Federal Information Processing Standards (FIPS) code assigned to each US county. Monroe County is 055. STCO_FIPS: The five-digit Federal Information Processing Standards (FIPS) code assigned to iedntify a unique county, typically as a concatenation of the State FIPS code and the County FIPS code. TRACT_FIPS: The six-digit number assigned to each census tract in a US county. FIPS: A unique geographic identifier, typically as a concatenation of State FIPS code, County FIPS code, and Census tract code. POPULATION: The population of a census tract. POP_SQMI: The population per square mile of a census tract. SQMI: The size of a census tract in square miles. Division: The name of the City of Rochester data division that the census tract falls in to. Source: This data comes from the Census Bureau.

Census Tracts from the 2010 US Census for New York City including portions under water. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map.

The 2020 NYC Public Use Microdata Areas (PUMAs) are statistical geographic areas defined for the dissemination of 2020 Public Use Microdata Sample (PUMS) data. PUMAs have a minimum population of 100,000, are aggregated from census tracts, and approximate Community Districts (CDs), or combinations of CDs (There are 59 CDs and only 55 NYC PUMAs because of such combinations). These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. All previously released versions of this data are available on the DCP Website: BYTES of the BIG APPLE.

Census Tracts from the 2010 US Census for New York City including portions under water. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. Because some census tracts are under water not all census tracts are contained in this file, only census tracts that are partially or totally located on land have been mapped in this file. All previously released versions of this data are available at DCP Website: BYTES of the BIG APPLE.

Analysis of ‘2010 Public Use Microdata Areas (PUMAs)’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/accc5826-c40d-46a1-8348-c46f77740ea2 on 12 February 2022.

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

The 2010 NYC Public Use Microdata Areas (PUMAs) are statistical geographic areas defined for the dissemination of Public Use Microdata Sample (PUMS) data. PUMAs have a minimum population of 100,000 and were aggregated from 2010 census tracts. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map.

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

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

Census Tracts from the 2010 US Census for New York City clipped to the shoreline. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. All previously released versions of this data are available at DCP Website: BYTES of the BIG APPLE.

Incorporated PlacesThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau, displays Incorporated Places (legal entities). Per USCB, "The legal designations, powers, and functions of incorporated places vary from state to state. Incorporated places include cities, towns (except in New England, New York, and Wisconsin where the Census Bureau recognizes towns as MCDs for census purposes), boroughs (except in Alaska, where the Census Bureau recognizes boroughs as equivalents of counties, and New York, where the Census Bureau recognizes the five boroughs that constitute New York City as MCDs), villages, and other lesser known identifiers."Trenton, New JerseyData currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Incorporated Places) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 88 (Series Information for Census Tract State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (Incorporated Places) copy this link to embed it in OGC Compliant viewersFor more information, please visit: Series Information for Place State-based TIGER/Line Shapefiles, CurrentFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

The 2010 NYC Public Use Microdata Areas (PUMAs) are statistical geographic areas defined for the dissemination of Public Use Microdata Sample (PUMS) data. PUMAs have a minimum population of 100,000 and were aggregated from 2010 census tracts. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. All previously released versions of this data are available at BYTES of the BIG APPLE- Archive