This polygon shapefile provides county or county-equivalent boundaries for the conterminous United States and was created specifically for use with the data tables published as Selected Items from the Census of Agriculture for the Conterminous United States, 1950-2012 (LaMotte, 2015). This data layer is a modified version of Historic Counties for the 2000 Census of Population and Housing produced by the National Historical Geographic Information System (NHGIS) project, which is identical to the U.S. Census Bureau TIGER/Line Census 2000 file, with the exception of added shorelines. Excluded from the CAO_STCOFIPS boundary layer are Broomfield County, Colorado, Menominee County, Wisconsin, and the independent cities of Virginia with the exception of the 3 county-equivalent cities of Chesapeake City, Suffolk, and Virginia Beach. The census of agriculture was not taken in the District of Columbia for 1959, but available data indicate few if any farms in that area, the polygon was left ...

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

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

This is a polygon dataset for county boundaries as well as for city, township and unorganized territory (CTU) boundaries in the Twin Cities 7-county metropolitan area. The linework for this dataset comes from individual counties and is assembled by the Metropolitan Council for the MetroGIS community. This is a MetroGIS Regionally Endorsed dataset https://metrogis.org/.

The County CTU Lookup Table here https://gisdata.mn.gov/dataset/us-mn-state-metc-bdry-counties-and-ctus-lookup
is also included in this dataset and contains various data related to cities, townships, unorganized territories (CTUs) and any divisions created by county boundaries splitting them is also included in the dataset.

This dataset is updated quarterly. This dataset is composed of three shape files and one dbf table.
- Counties.shp = county boundaries
- CTUs.shp = city, township and unorganized territory boundaries
- CountiesAndCTUs.shp = combined county and CTU boundaries
- CountyCTULookupTable.dbf = various data related to CTUs and any divisions created by county boundaries splitting them is also included in the dataset, described here: https://gisdata.mn.gov/dataset/us-mn-state-metc-bdry-counties-and-ctus-lookup

NOTES:

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lake St. Croix Beach was incorrect. It was changed from 2394379 to 2395599 to match GNIS.

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lilydale was incorrect. It was changed from 2394457 to 2395708 to match GNIS.

- On 11/9/2010 it was discovered that the CTU ID used for the City of Crystal was incorrect. It was changed from 2393541 to 2393683 to match GNIS.

- Effective April 2008, a change was made in GNIS to match the FIPS place codes to the "civil" feature for each city instead of the "populated place" feature. Both cities and townships are now "civil" features within GNIS. This means that the official GNIS unique ID for every city in Minnesota has changed.

- The five digit CTU codes in this dataset are identical to the Federal Information Processing Standard (FIPS) ''Place'' codes. They are also used by the Census Bureau and many other organizations and are proposed as a MN state data coding standard.

- Cities and townships have also been referred to as ''MCDs'' (a census term), however this term technically refers to the part of each city or township within a single county. Thus, a few cities in the metro area that are split by county boundaries are actually comprised of two different MCDs. This was part of the impetus for a proposed MN state data standard that uses the ''CTU'' terminology for clarity.

- The boundary line data for this dataset comes from each county.

- A variety of civil divisions of the land exist within the United States. In Minnesota, only three types exist - cities, townships and unorganized territories. All three of these exist within the Twin Cities seven county area. The only unorganized territory is Fort Snelling (a large portion of which is occupied by the MSP International Airport).

- Some cities are split between two counties. Only those parts of cities within the 7-county area are included.

- Prior to the 2000 census, the FIPS Place code for the City of Greenwood in Hennepin County was changed from 25928 to 25918. This dataset reflects that change.

blockgrouphomevalues # Context A home purchase is among the most import decisions, and potentially risk investments, in a person's life. Their choice can reflect interest in long term gains, housing costs and, in the U.S., part of the American Dream. Analytics of home values and rental costs, however, are commonly limited to highest level geographic aggregates and broad, even annual, periods of time. This publication produces a data file shared in the Block Groups Datasets dataverse hosted on https://dataverse.harvard.edu/dataverse/blockgroupdatasets. The data is shared under a Common Commons, open source license, without warranties, share alike, non commercial and by attribution. Method This publication attempts to cast home values down to U.S. Census block group geographies, by inheriting and averaging the measures from ZIP code level estimates. On the whole, block groups with a few hundred households are considerably smaller than ZIP code areas with several thousand. In addition, the two geographies are managed by separate Federal agencies, the U.S. Postal Service and the Census Bureau, so they are inherently dissimilar. The simplest method of projection involves overlaying the two geographies, having a block group inherit the estimates of the ZIP code level that covers it. When the block group spans ZIP code boundaries, an average is appropriate, weighted by land area lying in each parent. Data Zillow is recognized as an innovator in predicting home values, serving real estate agents, home buyers, and home sellers. Their research service publishes several estimates at a ZIP code level including measures of home value (Zillow Home Value Index ZHVI) and rental costs (Zillow Observed Rent Index ZORI). The ZHVI is broken down by housing type: single family homes and condominiums. And, each of their publications has monthly frequency dating, in some cases, to 2000. Block group geographic boundariess are maintained by the US Census' TIGER (Topologically Integrated Geographic Encoding and Referencing) publication. ZIP code boundaries are not generally published, but shared from a private company, Dotlas, in various retail marketing solutions. ZIP codes, also, have long been problematic for demographic analytics. Their boundaries span counties and states, so you cannot tiethem to familar geographies including Census tracts and block groups. The Census Bureau tries to address this by using ZIP Code Tabulation Areas (ZCTAs). These are coded very much like 5 digit ZIP codes and are equal to them most of the time. When A ZIP code geography crosses a county line, though, new ZCTAs are invented to represent each side of the split area. So, while ZIP codes cannot be aggregated, ZCTAs can total into counties, states, divisions and regions. The blockgrouphomevalues dataset offers the following columns: Column Data Type Description STATEFP string The 2-digit State FIPS code of the block group COUNTYFP string The 3-digit County FIPS code of the block group TRACTCE string The 6-digit Census Tract of the block group BLKGRPCE string The 1-digit Block Group of the block group GEOID string 12 digit concatenation of State, County, Tract and Block Group codes GEOIDFQ string The 'fully qualified' GEOID with US country prefix ALAND integer The land area if the block group in square meters AWATER integer The area if the block group, covered by water, in square meters INTPTLAT float Latitude of the block groups centroid point INTPTLON float Longitude of the block groups centroid point ZIP Codes Overlaying list List of the ZIP codes that overlay the block group ZHVI All Housing Types float Zillow Home Value Index, attributed to the block group, all housing types ZHVI Single Family Homes float Zillow Home Value Index, attributed to the block group, single family homes ZHVI Condos/Coops float Zillow Home Value Index, attributed to the block group, condominiums and cooperatively owned ZORI All Housing Types float Zillow Observed Rent Index, attributed to the block group Additional Notes When the Block Group Code BLKGRPCE is '0', that block group is under water. Block groups cover the Great Lakes, for example, making a confusing visual for chloropleth maps. To support visualization, the code also uses Census definitions of cities called Combined Statitical Areas, which group counties together. The CSA for New York includes 22 counties, distinguished as Central or Outlying. The Delineation Files publication includes the geographic IDs of state and county FIPS codes in each major city. Maps of these results may be visually biased. New York City and San Francisco Bay areas have extreme housing values, but they have small land areas. Denver by contrast has higher then median housing values with very large land areas. As a result, western Colorado looks like the dominating location of home values. When more than one ZIP code overlays a block group, values are attributed by the shared land area. This assumes that housing is uniform over...

This feature layer contains census tracts for the San Francisco Bay Region for Census 2000. The features were extracted from a statewide data set downloaded from the United States Census Bureau by Metropolitan Transportation Commission staff.The purpose of this feature layer is for the production of feature sets for public access and download to avoid licensing issues related to the agency's base data.Source data downloaded from https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html_The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the United States Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the Census 2000 Participant Statistical Areas Program (PSAP). 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,500 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, etc. may require boundary revisions before a census. 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 are always 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.

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

This 'Redistricting' version of the census data is the first release of the data.

This 2000 census redistricting geography database of the 7 county metropolitan area and the additional 12 collar county area was developed from the U.S. Census Bureau's Redistricting Census 2000 TIGER/Line files.

The Metropolitan Council downloaded this data from the Census Bureau's FTP site, imported it into ArcInfo coverage format, added a few items to the coverage, then created block, block group, tract, county subdivision (city), county, taz and water coverages and shape files from the original data.

This raster dataset represents the agricultural census data quality for harvested areas of cinnamon, crops. Data quality categories include (0= missing, 0.25= county level census data, 0.5= interpolated with census data from within 2 degrees of latitude/longitude, 0.75= state level census data, 1= country level census data). Croplands cover ~15 million km2 of the planet and provide the bulk of the food and fiber essential to human well-being. Most global land cover datasets from satelites group croplands into just a few categories, thereby excluding information that is critical for answering key questions ranging from biodiversity conservation to food security to biogeochemical cycling. Information about agricultural land use practices like crop selection, yield, and fertilizer use is even more limited.Here we present land use data sets created by combining national, state, and county level census statistics with a recently updated global data set of croplands on a 5 minute by 5 minute (~10km x 10 km) latitude/longitude grid. Temporal resolution: Year 2000- based of average of census data between 1997-2003.

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.

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

This raster dataset represents the agricultural census data quality for harvested areas of tangerine crops. Data quality categories include (0= missing, 0.25= county level census data, 0.5= interpolated with census data from within 2 degrees of latitude/longitude, 0.75= state level census data, 1= country level census data). Croplands cover ~15 million km2 of the planet and provide the bulk of the food and fiber essential to human well-being. Most global land cover datasets from satelites group croplands into just a few categories, thereby excluding information that is critical for answering key questions ranging from biodiversity conservation to food security to biogeochemical cycling. Information about agricultural land use practices like crop selection, yield, and fertilizer use is even more limited.Here we present land use data sets created by combining national, state, and county level census statistics with a recently updated global data set of croplands on a 5 minute by 5 minute (~10km x 10 km) latitude/longitude grid. Temporal resolution: Year 2000- based of average of census data between 1997-2003.

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.

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

This raster dataset represents the agricultural census data quality for harvested areas of grain crops. Data quality categories include (0= missing, 0.25= county level census data, 0.5= interpolated with census data from within 2 degrees of latitude/longitude, 0.75= state level census data, 1= country level census data). Croplands cover ~15 million km2 of the planet and provide the bulk of the food and fiber essential to human well-being. Most global land cover datasets from satelites group croplands into just a few categories, thereby excluding information that is critical for answering key questions ranging from biodiversity conservation to food security to biogeochemical cycling. Information about agricultural land use practices like crop selection, yield, and fertilizer use is even more limited.Here we present land use data sets created by combining national, state, and county level census statistics with a recently updated global data set of croplands on a 5 minute by 5 minute (~10km x 10 km) latitude/longitude grid. Temporal resolution: Year 2000- based of average of census data between 1997-2003.

This raster dataset represents the agricultural census data quality for harvested areas of sugar crops. Data quality categories include (0= missing, 0.25= county level census data, 0.5= interpolated with census data from within 2 degrees of latitude/longitude, 0.75= state level census data, 1= country level census data). Croplands cover ~15 million km2 of the planet and provide the bulk of the food and fiber essential to human well-being. Most global land cover datasets from satelites group croplands into just a few categories, thereby excluding information that is critical for answering key questions ranging from biodiversity conservation to food security to biogeochemical cycling. Information about agricultural land use practices like crop selection, yield, and fertilizer use is even more limited.Here we present land use data sets created by combining national, state, and county level census statistics with a recently updated global data set of croplands on a 5 minute by 5 minute (~10km x 10 km) latitude/longitude grid. Temporal resolution: Year 2000- based of average of census data between 1997-2003.

Abstract

The purpose of the SEPHER data set is to allow for testing, assessing and generating new analysis and metrics that can address inequalities and climate injustice. The data set was created by Tedesco, M., C. Hultquist, S. E. Char, C. Constantinides, T. Galjanic, and A. D. Sinha.

Methodology

SEPHER draws upon four major source datasets: CDC Social Vulnerability Index, FEMA National Risk Index, Home Mortgage Disclosure Act, and Evictions datasets. The data from these source datasets have been merged, cleaned, and standardized and all of the variables documented in the data dictionary.

CDC Social Vulnerability Index

CDC Social Vulnerability Index (SVI) dataset is a dataset prepared for the Centers for Disease Control and Prevention for the purpose of assessing the degree of social vulnerability of American communities to natural hazards and anthropogenic events. It contains data on 15 social factors taken or derived from Census reports as well as rankings of each tract based on these individual factors, groups of factors corresponding to four related themes (Socioeconomic, Household Composition & Disability, Minority Status & Language, and Housing Type & Transportation) and overall. The data is available for the years 2000, 2010, 2014, 2016, and 2018.

FEMA National Risk Index

The National Risk Index (NRI) dataset compiled by the Federal Emergency Management Agency (FEMA) consists of historic natural disaster data from across the United States at a tract-level. The dataset includes information about 18 natural disasters including earthquakes, tsunamis, wildfires, volcanic activity and many others. Each disaster is detailed out in terms of its frequency, historic impact, potential exposure, expected annual loss and associated risk. The dataset also includes some summary variables for each tract including the total expected loss in terms of building loss, human loss and agricultural loss, the population of the tract, and the area covered by the tract. It finally includes a few more features to characterize the population such as social vulnerability rating and community resilience.

Home Mortgage Disclosure Act

The Home Mortgage Disclosure Act (HMDA) dataset contains loan-level data for home mortgages including information on applications, denials, approvals, and institution purchases. It is managed and expanded annually by the Consumer Financial Protection Bureau based on the data collected from financial institutions. The dataset is used by public officials to make decisions and policies, uncover lending patterns and discrimination among mortgage applicants, and investigate if lenders are serving the housing needs of the communities. It covers the period from 2007 to 2017.

Evictions

The Evictions dataset is compiled and managed by the Eviction Lab at Princeton University and consists of court records related to eviction cases in the United States between 2000 and 2016. Its purpose is to estimate the prevalence of court-ordered evictions and compare eviction rates among states, counties, cities, and neighborhoods. Besides information on eviction filings and judgments, the dataset includes socioeconomic and real estate data for each tract including race/ethnic origin, household income, poverty rate, property value, median gross rent, rent burden, and others.

In 2023, Washington, D.C. had the highest population density in the United States, with 11,130.69 people per square mile. As a whole, there were about 94.83 residents per square mile in the U.S., and Alaska was the state with the lowest population density, with 1.29 residents per square mile. The problem of population density Simply put, population density is the population of a country divided by the area of the country. While this can be an interesting measure of how many people live in a country and how large the country is, it does not account for the degree of urbanization, or the share of people who live in urban centers. For example, Russia is the largest country in the world and has a comparatively low population, so its population density is very low. However, much of the country is uninhabited, so cities in Russia are much more densely populated than the rest of the country. Urbanization in the United States While the United States is not very densely populated compared to other countries, its population density has increased significantly over the past few decades. The degree of urbanization has also increased, and well over half of the population lives in urban centers.

This raster dataset represents the agricultural census data quality for harvested areas of fonio crops. Data quality categories include (0= missing, 0.25= county level census data, 0.5= interpolated with census data from within 2 degrees of latitude/longitude, 0.75= state level census data, 1= country level census data). Croplands cover ~15 million km2 of the planet and provide the bulk of the food and fiber essential to human well-being. Most global land cover datasets from satelites group croplands into just a few categories, thereby excluding information that is critical for answering key questions ranging from biodiversity conservation to food security to biogeochemical cycling. Information about agricultural land use practices like crop selection, yield, and fertilizer use is even more limited.Here we present land use data sets created by combining national, state, and county level census statistics with a recently updated global data set of croplands on a 5 minute by 5 minute (~10km x 10 km) latitude/longitude grid. Temporal resolution: Year 2000- based of average of census data between 1997-2003.