This dataset provides the State and Union Territory level administrative boundaries for India in a Shape file format. Rendered in the industry-standard coordinate reference system, EPSG:4326 (WGS84), this dataset ensures precision and compatibility.

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. American Indian tribal subdivisions are administrative subdivisions of federally recognized American Indian reservations/off-reservation trust lands or Oklahoma tribal statistical areas (OTSAs). These entities are internal units of self-government and/or administration that serve social, cultural, and/or economic purposes for the American Indian tribe or tribes on the reservations/off-reservation trust lands or OTSAs. The Census Bureau obtains the boundary and attribute information for tribal subdivisions on federally recognized American Indian reservations and off-reservation trust lands from federally recognized tribal governments through the Census Bureau's Boundary and Annexation Survey (BAS). For the 2020 Census, the boundaries for tribal subdivisions on OTSAs were also obtained from federally recognized tribal governments through the Participant Statistical Areas Program (PSAP). Note that tribal subdivisions do not exist on all reservations/off-reservation trust lands or OTSAs, rather only where they were submitted to the Census Bureau by the federally recognized tribal government for that area. The boundaries for American Indian tribal subdivisions are as of January 1, 2020, as reported by the federally recognized tribal governments through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries for tribal subdivisions on OTSAs are those reported as of January 1, 2020 through PSAP.

Full journal article published hereDesignating Airsheds in India for Urban and Regional Air Quality Managementhttps://doi.org/10.3390/air2030015

[Summary presentation download]

Datasets used for proposing India's 15 regional airsheds for air quality management are the following

PM2.5 DatasetsRaw data source: https://sites.wustl.edu/acag/datasets/surface-pm2-5

Gridded 0.1 degree resolution source apportionment results from WUSTL's global model simulationsFile: india_data_pm25_wustl_source_cont_0p1deg.xlsxAggregated Source definitions used in this presentation

1. DUST = Anthropogenic dust = AFCID

2. WINDUST = Wind erosion (dust storms) = WDUST

3. WASTE = Waste burning = WST

4. RESI = All commercial and residential cooking, lighting, and heating = RCOC + RCOO + RCORbiofuel + RCORcoal + RCORother

5. TRANS = All transport (excluding aviation) = ROAD + NRTR + SHP

6. POWER = Energy generation = ENEcoal + ENEother

7. INDUS = All industries and product use = INDcoal + INDother + SLV

8. BIOB = Biomass burning, including forest fires and agricultural waste burning = GFEDoburn + GFEDagburn

9. AGR = Agricultural activities (excluding agricultural waste burning) = AGR

10. OTHER = All others = OTHER

Gridded 0.1 degree resolution, reanalysis data from WUSTL's global model simulationsFile: india_data_pm25_wustl_reanalysis_0p1deg.xlsxTime period: 1998 to 2022, annual averages

Gridded 0.1 degree achive for monthly averages from WUSTL's global model simulationsFile: Download-44MB

Population DatasetsRaw data source: https://landscan.ornl.gov

Gridded 0.1 degree resolution population density dataFile: india_data_population_2021_0p1deg.xlsx

GIS databases used in this study

ESRI shapefile of 0.1 x 0.1 degree mesh file for the Indian Subcontinent covering longitudes from 67E to 99E and latitudes from 7N to 39NFile: india_gis_grids-0.1x0.1deg.rar

ESRI shapefile of India administrative level 2 data - 28 states and 8 union territories (as of December 2023)File: india_gis_states28+8_2023.rar

ESRI shapefile of India administrative level 3 data - 755 districts (as of December 2023): district23 and states23 codes are re-designed for emissions and pollution mapping and data tracking purposesFile: India_gis_districts755_2023.rar (original source: https://projects.datameet.org/maps)

ESRI shapefile of India's Agro-Climatic zonesFile: india_gis_agroclimatic_zones.rar (original source: https://karnataka.data.gov.in/resource/boundaries-agro-climatic-regions

ESRI shapefile of India's meteorological sub-divisionsFile: india_gis_meteo_subdivisions.rar (original source: https://mausam.imd.gov.in)

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. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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. The American Indian/Alaska Native/Native Hawaiian (AIANNH) Areas Shapefile includes the following legal entities: federally recognized American Indian reservations and off-reservation trust land areas, state-recognized American Indian reservations, and Hawaiian home lands (HHLs). The statistical entities included are Alaska Native village statistical areas (ANVSAs), Oklahoma tribal statistical areas (OTSAs), tribal designated statistical areas (TDSAs), and state designated tribal statistical areas (SDTSAs). Joint use areas are also included in this shapefile refer to areas that are administered jointly and/or claimed by two or more American Indian tribes. The Census Bureau designates both legal and statistical joint use areas as unique geographic entities for the purpose of presenting statistical data. Note that tribal subdivisions and Alaska Native Regional Corporations (ANRCs) are additional types of American Indian/Alaska Native areas stored by the Census Bureau, but are displayed in separate shapefiles because of how they fall within the Census Bureau's geographic hierarchy. The State of Hawaii's Office of Hawaiian Home Lands provides the legal boundaries for the HHLs. The boundaries for ANVSAs, OTSAs, and TDSAs were delineated for the 2020 Census through the Participant Statistical Areas Program (PSAP) by participants from the federally recognized tribal governments. The Bureau of Indian Affairs (BIA) within the U.S. Department of the Interior (DOI) provides the list of federally recognized tribes and only provides legal boundary information when the tribes need supporting records, if a boundary is based on treaty or another document that is historical or open to legal interpretation, or when another tribal, state, or local government challenges the depiction of a reservation or off-reservation trust land. The boundaries for federally recognized American Indian reservations and off-reservation trust lands are as of January 1, 2020, as reported by the federally recognized tribal governments through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries for state-recognized American Indian reservations and for SDTSAs were delineated by a state governor-appointed liaisons for the 2020 Census through the State American Indian Reservation Program and PSAP respectively.

The India Village-Level Geospatial Socio-Economic Data Set: 1991, 2001 is a compilation of the finest level of administrative boundaries in India (village/town-level) and over 200 socio-economic variables collected during the Indian Census in 1991 and 2001. This data set was developed by digitizing village/town level boundaries from the official analog maps published by the Survey of India for 2001. This data set also utilized tabular data for 1991 and 2001 from the Primary Census Abstract (PCA) and Village Directory (VD) data series of the Indian census. The data are in UTM 44N projection and are distributed primarily as shapefiles. Separate files are provided for each of the 28 states (number of states during 1991 and 2001 census) and combined Union Territories for 1991 and 2001.

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 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. The American Indian / Alaska Native / Native Hawaiian (AIANNH) Areas Shapefile includes the following legal entities: federally recognized American Indian reservations and off-reservation trust land areas, State-recognized American Indian reservations, and Hawaiian home lands (HHLs). The statistical entities included are Alaska Native village statistical areas (ANVSAs), Oklahoma tribal statistical areas (OTSAs), tribal designated statistical areas (TDSAs), and State designated tribal statistical areas (SDTSAs). Joint use areas are also included in this shapefile and mean that the area is administered jointly and/or claimed by two or more American Indian tribes. The Census Bureau designates both legal and statistical joint use areas as unique geographic entities for the purpose of presenting statistical data. Note that tribal subdivisions and Alaska Native Regional Corporations (ANRCs) are additional types of American Indian / Alaska Native areas stored by the Census Bureau, but are displayed in separate shapefiles because of how the fall within the Census Bureau's geographic hierarchy. The 2010 Census boundaries for federally recognized American Indian reservations and off-reservation trust lands are as of January 1, 2010, as reported by the federally recognized tribal governments through the Census Bureau's Boundary and Annexation Survey (BAS). The State of Hawaii's Office of Hawaiian Home Lands provided the legal boundaries used in Census 2000 for the HHLs, but provided no updates since and none for the 2010 Census although there is strong evidence of HHL land acquisitions and large housing and commercial development on most HHLs. The boundaries for ANVSAs, OTSAs, and TDSAs were delineated for the 2010 Census through the Tribal Statistical Areas Program (TSAP) by participants from the federally recognized tribal governments. The Bureau of Indian Affairs (BIA) within the U.S. Department of the Interior (DOI) provides the list of federally recognized Tribes and only provides legal boundary information when the Tribes need supporting records, if a boundary is based on treaty or another document that is historical or open to legal interpretation, or when another Tribal, State, or local government challenges the depiction of a reservation or off-reservation trust land. The boundaries for State recognized American Indian reservations and for SDTSAs were delineated State governor appointed liaisons for the 2010 Census through the State American Indian Reservation Program and TSAP respectively.

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

This shows the boundaries for American Indian reservations, counties, tracts, block groups, blocks, military boundaries and political townships as of 2020. TIGER/Line shapefiles downloaded directly from the U.S. Census at 2020 TIGER/Line ShapefilesThe 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. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation.The full Kansas geospatial catalog is administered by the Kansas Data Access & Support Center (DASC) and can be found at the following URL: https://hub.kansasgis.org/

Publication Date: May 2025. Updated as needed. Current as of the Publication Date. The data can be downloaded here: https://gis.ny.gov/civil-boundaries#about-civil-boundaries. This feature service has polygon layers for the following boundary types: State, Counties, Cites, Towns, Cities and Towns combined, Villages, and Indian Territories. In addition, there are separate shoreline layers for the State layer and the County layer. Boundaries are at 1:24,000-scale positional accuracy except for the shoreline in State Shoreline and Counties Shoreline which is being adjusted to 1:24,000-scale positional accuracy as part of ongoing work. Boundary changes are made as needed and based on authoritative sources. See metadata for each layer for additional information. This map service is available to the public. The State of New York, acting through the New York State Office of Information Technology Services, makes no representations or warranties, express or implied, with respect to the use of or reliance on the Data provided. The User accepts the Data provided “as is” with no guarantees that it is error free, complete, accurate, current or fit for any particular purpose and assumes all risks associated with its use. The State disclaims any responsibility or legal liability to Users for damages of any kind, relating to the providing of the Data or the use of it. Users should be aware that temporal changes may have occurred since this Data was created.

The Census data utilized for developing the Community Layer used 2010 TIGER/Line shapefile datasets (TIGER = Topologically Integrated Geographic Encoding and Referencing). TIGER/Line shapefiles are available for free download from the US Census Bureau and include various legal and statistical geographic areas for which the Census tabulates data. The shapefiles are designed to be used in a GIS environment, with the ability to directly link the geographic areas to Census data via a unique GEOID number.The following TIGER/Line datasets should be used: - Counties and Equivalent Entities –primary legal divisions within each state (counties, parishes, etc)- County Subdivisions –includes both legal areas (Minor Civil Divisions or MCDs) and various statistical areas- Places –includes both legal areas (Incorporated Places) and statistical areas (Census Designated Places or CDPs)- Blocks –the smallest geographical area for which Census population counts are recorded; blocks never cross boundaries of any entity for which the Census Bureau tabulates data, including counties, county subdivisions, places, and American Indian, Alaska Native, and Native Hawaiian (AIANNH) areas- American Indian, Alaska Native, and Native Hawaiian (AIANNH) AreasExtracting and Formatting CIS DataA key component of the community layer is the ability to link CIS information spatially. Data from CIS cannot directly be joined with Census data. The two datasets have community name discrepancies which impede an exact match. Therefore, CIS data needs to be formatted to match Census community names. A custom report can be obtained from CIS to include a CID number, Community Name, County, State, Community Status, and Tribal status for all CIS records. Make sure all CID numbers are six digits and you follow the CIS community naming convention outlined in Table 4.2.1.1 in the Community Layer Update Technical Guide 20131206. Converting the CIS name“ADDISON, VILLAGE OF” to “ADDISON TOWN”involves removing unneeded spaces, comma, and preposition to make the join successful to the Census data. Using a comprehensive report at a national level gains efficiencies as bulk edits can be made. Data for each state should be extracted as needed by separating the CIS data into each type of community corresponding to the Census geography layers used, and a new JoinID column (e.g. ADDISON TOWN) can be created for each dataset allowing the CIS data to be joined to the Census data.

Mineral resource occurrence data covering the world, most thoroughly within the U.S. This database contains the records previously provided in the Mineral Resource Data System (MRDS) of USGS and the Mineral Availability System/Mineral Industry Locator System (MAS/MILS) originated in the U.S. Bureau of Mines, which is now part of USGS. The MRDS is a large and complex relational database developed over several decades by hundreds of researchers and reporters. While database records describe mineral resources worldwide, the compilation of information was intended to cover the United States completely, and its coverage of resources in other countries is incomplete. The content of MRDS records was drawn from reports previously published or made available to USGS researchers. Some of those original source materials are no longer available. The information contained in MRDS was intended to reflect the reports used as sources and is current only as of the date of those source reports. Consequently MRDS does not reflect up-to-date changes to the operating status of mines, ownership, land status, production figures and estimates of reserves and resources, or the nature, size, and extent of workings. Information on the geological characteristics of the mineral resource are likely to remain correct, but aspects involving human activity are likely to be out of date.

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.Information for SOILS data layer was derived from the Private Forest Land Grading system (PFLG) and subsequent soil surveys. PFLG was a five-year mapping program completed in 1980 for the purpose of forestland taxation. It was funded by the Washington State Department of Revenue. The Department of Natural Resources, Soil Conservation Service (now known as the Natural Resources Conservation Service or NRCS), USDA Forest Service and Washington State University conducted soil mapping cooperatively following national soil survey standards. Private lands having the potential of supporting commercial forests were surveyed along with interspersed small areas of State lands, Indian tribal lands, and federal lands. Because this was a cooperative soil survey project, agricultural and non-commercial forestlands were included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soil map unit delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were later added and are now available through associated lookup tables. SCS (NRCS) soils data on agricultural lands also have been subsequently added to this data layer. The SOILS data layer includes approximately 1,100 townships with wholly or partially digitized soils data. State and private lands which have the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soils survey project, agricultural and non-commercial forestlands were also included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soils delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were added at a later time and are now available through associated lookup tables. SCS soils data on agricultural lands also have subsequently been added to this data layer. This layer includes approximately 1, 100 townships with wholly or partially digitized soils data (2,101 townships would provide complete coverage of the state of Washington).-

The soils_sv resolves one to many relationships and as such is one of those special "DNR" spatial views ( ie. is implemented similar to a feature class). Column names may not match between SOILS_SV and the originating datasets. Use limitations

This Spatial View is available to Washingotn DNR users and those with access to the Washington State Uplands IMS site.

The following cautions only apply to one-to-many and many-to-many spatial views! Use these in the metadata only if the SV is one-to-many or many-to-many.

CAUTIONS: Area and Length Calculations: Use care when summarizing or totaling area or length calculations from spatial views with one-to-many or many-to-many relationships. One-to-many or many-to-many relationships between tabular and spatial data create multiple features in the same geometry. In other words, if there are two or more records in the table that correspond to the same feature (a single polygon, line or point), the spatial view will contain an identical copy of that feature's geometry for every corresponding record in the table. Area and length calculations should be performed carefully, to ensure they are not being exaggerated by including copies of the same feature's geometry.

Symbolizing Spatial Features:
Use care when symbolizing data in one-to-many or many-to-many spatial views. If there are multiple attributes tied to the same feature, symbolizing with a solid fill may mask other important features within the spatial view. This can be most commonly seen when symbolizing features based on a field with multiple table records.

Labeling Spatial Features: Spatial views with one-to-many or many-to-many relationships may present duplicate labels for those features with multiple table records. This is because there are multiple features in the same geometry, and each one receives a label.Soils Metadata

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) System (MTS). The MTS 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. Edges refer to the linear topological primitives that make up the MTS. The All Lines shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines shapefile are available in relationship (.dbf) files that users must download separately. The All Lines shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

The 2022 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 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 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. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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

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.