This data layer is an element of the Oregon GIS Framework. 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 and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

The Census Bureau (https://www.census.gov/) maintains geographic boundaries for the analysis and mapping of demographic information across the United States. Every 10 years the Census Bureau counts the population of the United States as mandated by Constitution. The Census Bureau releases the results of this county as demographic data with geographic identifiers so that maps and analysis can be performed on the US population. There are little more Census Tracts within Los Angeles County in 2020 Census TIGER/Line Shapefiles, compared to 2010.Created/Updated: Updated on September 2023, to merged Long Beach Breakwater land-based tracts silver polygons into bigger tract 990300 as per 2022 TIGER Line Shapefiles, and to update Santa Catalina Islands and San Clemente Islands tract boundary based on DPW City boundaries (except 599000 tract in Avalon). Updated on Sep 2022 and Dec 2022, to align tract boundary along city boundaries. Created on March 2021. How was this data created? This geographic file was downloaded from Census Bureau website: https://www2.census.gov/geo/tiger/TIGER2020PL/STATE/06_CALIFORNIA/06037/on February, 2021 and customized for LA County. Data Fields:1. CT20 (TRACTCE20): 6-digit census tract number, 2. Label (NAME20): Decimal point census tract number.

This resource is a member of a series. 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.

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

Census Current (2022) Legal and Statistical Entities Web Map Service; January 1, 2022 vintage.

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 non-visible 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 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.

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

The 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 2020 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2010 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area.

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.

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.

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. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for almost all geographic areas for which the Census Bureau tabulates data for both the 2010 Census and Census 2000. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

Blocks are typically bounded by streets, roads or creeks. In cities, a census block may correspond to a city block, but in rural areas where there are fewer roads, blocks may be limited by other features. The Census Bureau established blocks covering the entire nation for the first time in 1990.There are less number of Census Blocks within Los Angeles County in 2020 Census TIGER/Line Shapefiles, compared in 2010.Updated:1. June 2023: This update includes 2022 November Santa Clarita City annexation and the addition of "Kinneloa Mesa" community (was a part of unincorporated East Pasadena). Added new data fields FIP_CURRENT to CITYCOMM_CURRENT to reflect new/updated city and communities. Updated city/community names and FIP codes of census blocks that are in 2022 November Santa Clarita City annexation and new Kinneloa Mesa community (look for FIP_Current, City_Current, Comm_Current field values)2. February 2023: Updated few Census Block CSA values based on Demographic Consultant inquiry/suggestions3. April 2022: Updated Census Block data attribute values based on Supervisorial District 2021, Service Planning Area 2022, Health District 2022 and ZIP Code Tabulation Area 2020Created: March 2021How This Data is Created? This census geographic file was downloaded from Census Bureau website: https://www2.census.gov/geo/tiger/TIGER2020PL/STATE/06_CALIFORNIA/06037/ on February 2021 and customized for LA County. New data fields are added in the census blocks 2020 data and populated with city/community names, LA County FIPS, 2021 Supervisorial Districts, 2020 Census Zip Code Tabulation Area (ZCTA) and some administrative boundary information such as 2022 Health Districts and 2022 Service Planning Areas (SPS) are also added. "Housing20" field value and "Pop20" field value is populated with PL 94-171 Redistricting Data Summary File: Decennial Census P.L. 94-171 Redistricting Data Summary Files. Similarly, "Feat_Type" field is added and populated with water, ocean and land values. Five new data fields (FIP_CURRENT to CITYCOMM_CURRENT) are added in June 2023 updates to accommodate 2022 Santa Clarita city annexation. City/community names and FIP codes of census blocks affected by 2022 November Santa Clarita City annexation are assigned based on the location of block centroids. In June 2023 update, total of 36 blocks assigned to the City of Santa Clarita that were in Unincorporated Valencia and Castaic. Note: This data includes 3 NM ocean (FEAT_TYPE field). However, user can use a definition query to remove those. Data Fields: 1. STATE (STATEFP20): State FIP, "06" for California, 2. COUNTY (COUNTYFP20): County FIP "037" for Los Angeles County, 3. CT20: (TRACTCE20): 6-digit census tract number, 4. BG20: 7-digit block group number, 5. CB20 (BLOCKCE20): 4-digit census block number, 6. CTCB20: Combination of CT20 and CB20, 7. FEAT_TYPE: Land use types such as water bodies, ocean (3 NM ocean) or land, 8. FIP20: Los Angeles County FIP code, 9. BGFIP20: Combination of BG20 and FIP20, 10. CITY: Incorporated city name, 11. COMM: Unincorporated area community name and LA City neighborhood, also known as "CSA", 12. CITYCOMM: City/Community name label, 13. ZCTA20: Parcel specific zip codes, 14. HD12: 2012 Health District number, 15. HD_NAME: Health District name, 16. SPA22: 2022 Service Planning Area number, 17. SPA_NAME: Service Planning Area name, 18. SUP21: 2021 Supervisorial District number, 19. SUP_LABEL: Supervisorial District label, 20. POP20: 2020 Population (PL 94-171 Redistricting Data Summary File - Total Population), 21. HOUSING20: 2020 housing (PL 94-171 Redistricting Data Summary File - Total Housing),22. FIP_CURRENT: Los Angeles County 2023 FIP code, as of June 2023,23. BG20FIP_CURRENT: Combination of BG20 and 2023 FIP, as of June 2023,24. CITY_CURRENT: 2023 Incorporated city name, as of June 2023,25. COMM_CURRENT: 2023 Unincorporated area community name and LA City neighborhood, also known as "CSA", as of June 2023,26. CITYCOMM_CURRENT: 2023 City/Community name label, as of June 2023.

A Block Group usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within the census tract. Within the standard census geography hierarchy, BGs never cross state, county, or census tract boundaries but may cross the boundaries of any other geographic entity. There are little more number of Census Block Groups within Los Angeles County in 2020 Census TIGER/Line Shapefiles, compared in 2010.BGs are generally define to contain between 600 to 3,000 people and 240 and 1,200 housing units. BGs are the smallest geographic unit for which the Census Bureau tabulates sample data. Created/Updated: Updated on September 2023, to merged Long Beach Breakwater land-based block group silver polygons into bigger block group 9903000 as per 2022 TIGER Line Shapefiles, and to update Santa Catalina Islands and San Clemente Islands block group boundary based on DPW City boundaries (except 5990002 tract in Avalon). Updated on Sep 2022 and Dec 2022, to align tract boundary along city boundaries.Created on March 2021.How This Data is Created? This geographic file was downloaded from Census Bureau website: https://www2.census.gov/geo/tiger/TIGER2020PL/STATE/06_CALIFORNIA/06037/ on February, 2021 and customized for LA County. Data Fields:1. BG20 (BLKGRPCE20): 7 digit census tracts and block group number, 2. CT20 (TRACTCE20): 6-digit census tract number, 3. Label (NAMELSAD20): Block group number label

Census tracts are small, relatively permanent geographic entities within counties (or the statistical equivalents of counties) delineated by a committee of local data users. Generally, census tracts have between 2,500 and 8,000 residents and boundaries that follow visible features. When first established, census tracts are to be as homogeneous as possible with respect to population characteristics, economic status, and living conditions. (www.census.gov)

Standard block groups are clusters of blocks within the same census tract that have the same first digit of their 4-character census block number (e.g., Blocks 3001, 3002, 3003 to 3999 in census tract 1210.02 belong to block group 3). Current block groups do not always maintain these same block number to block group relationships due to boundary and feature changes that occur throughout the decade. For example, block 3001 might move due to a change in the census tract boundary. Even if the block is no longer in block group 3, the block number (3001) will not change. However, the GEOID for that block, identifying block group 3, would remain the same in the attribute information in the TIGER/Line Shapefiles because block GEOIDs are always built using the decennial geographic codes.Block groups delineated for the 2020 Census generally contain 600 to 3,000 people. Local participants delineated most block groups as part of the Census Bureau's PSAP. The Census Bureau delineated block groups only where a local or tribal government declined to participate or where the Census Bureau could not identify a potential local participant.A block group usually covers a contiguous area. Each census tract contains one or more block groups and block groups have unique numbers within census tract. Within the standard census geographic hierarchy, block groups never cross county or census tract boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and AIANNH areas.Block groups have a valid range of zero (0) through nine (9). Block groups beginning with a zero generally are in coastal and Great Lakes water and territorial seas. Rather than extending a census tract boundary into the Great Lakes or out to the 3-mile territorial sea limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore.

What is unique about LA County’s data?It is clipped to the ocean boundary. Raw Census data includes a 3 mile buffer into the ocean, which impacts cartography.IMPORTANT! It has been updated to the 2012 Census Geography Update, which merged Tracts 1370.00 and 9304.01 into the combined tract 1370.00. So the CT10 field actually reflects the 2012 Census update, which is used for all population products 2012 and later.How was this data created?This data was downloaded from Census Bureau website: http://www.census.gov/cgi-bin/geo/shapefiles2010/file-download and clipped to the County Boundary using ESRI’s ArcGIS Desktop. Two new fields were added in census tract data – area in square feet and shape length in feet. This dataset has unique identifier field “GEOID10” for each record and the census tract number fields “CT10” and “LABEL” (6-digit number and 6-digit number with decimal point, respectively).

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.

Context

There are a number of Kaggle datasets that provide spatial data around New York City. For many of these, it may be quite interesting to relate the data to the demographic and economic characteristics of nearby neighborhoods. I hope this data set will allow for making these comparisons without too much difficulty.

Exploring the data and making maps could be quite interesting as well.

Content

This dataset contains two CSV files:

1. nyc_census_tracts.csv

   This file contains a selection of census data taken from the ACS DP03 and DP05 tables. Things like total population, racial/ethnic demographic information, employment and commuting characteristics, and more are contained here. There is a great deal of additional data in the raw tables retrieved from the US Census Bureau website, so I could easily add more fields if there is enough interest.

   I obtained data for individual census tracts, which typically contain several thousand residents.

2. census_block_loc.csv

   For this file, I used an online FCC census block lookup tool to retrieve the census block code for a 200 x 200 grid containing New York City and a bit of the surrounding area. This file contains the coordinates and associated census block codes along
   with the state and county names to make things a bit more readable to users.

   Each census tract is split into a number of blocks, so one must extract the census tract code from the block code.

Acknowledgements

The data here was taken from the American Community Survey 2015 5-year estimates (https://factfinder.census.gov/faces/nav/jsf/pages/index.xhtml).

The census block coordinate data was taken from the FCC Census Block Conversions API (https://www.fcc.gov/general/census-block-conversions-api)

As public data from the US government, this is not subject to copyright within the US and should be considered public domain.

Tracts; January 1, 2019 vintage; Generalized

Features provide a view of 2020 Census tracts for the San Francisco Bay Region. Features are a subset of the Census Tracts 500k service at https://data.bayareametro.gov/dataset/Census-Tracts-500K/dg5p-pxcu.

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 or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy.

In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous.

For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

The Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Local participants have an opportunity to review the existing census tracts before each census. If local participants split a census tract, the split parts usually retain the basic number, but receive different suffixes. In a few counties, local participants request major changes to, and renumbering of, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes.

Relationship to Other Geographic Entities—Within the standard census geographic hierarchy, census tracts never cross state or county boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian, Alaska Native, and Native Hawaiian areas.

2010 Census tracts for the San Francisco Bay Region. Features were extracted from California 2018 TIGER/Line shapefile by the Metropolitan Transportation Commission.Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and are reviewed and updated by local participants prior to each decennial census as part of the Census Bureau’s Participant Statistical Areas Program (PSAP). The Census Bureau updates census tracts in situations where no local participant existed or where 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 decennial census data.Census tracts generally have a population size between 1,200 and 8,000 people with an optimum size of 4,000 people. The spatial size of census tracts varies widely depending on the density of settlement. Ideally, census tract boundaries remain stable over time to facilitate statistical comparisons from census to census. However, physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, significant changes in population may result in splitting or combining census tracts.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 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.Census Tract Codes and Numbers—Census tract numbers have up to a 4-character basic number and may have an optional 2-character suffix; for example, 1457.02. The census tract numbers (used as names) eliminate any leading zeroes and append a suffix only if required. The 6-character numeric census tract codes, however, include leading zeroes and have an implied decimal point for the suffix. Census tract codes range from 000100 to 998999 and are unique within a county or equivalent area. The Census Bureau assigned a census tract code of 9900 to represent census tracts delineated to cover large bodies of water. In addition, census tract codes in the 9400s represent American Indian Areas and codes in the 9800s represent special land use areas.The Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Local participants have an opportunity to review the existing census tracts before each census. If local participants split a census tract, the split parts usually retain the basic number, but receive different suffixes. In a few counties, local participants request major changes to, and renumbering of, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes.Relationship to Other Geographic Entities—Within the standard census geographic hierarchy, census tracts never cross state or county boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian, Alaska Native, and Native Hawaiian areas.