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.

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

This 2020 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 2020 TIGER/Line files.

The Metropolitan Council downloaded this data from the Census Bureau's FTP site and created block, block group, tract, county subdivision (city), and county datasets from the original data. The block dataset was updated on Jan. 12, 2023 to add new Census Bureau urban and rural designations.

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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

2010 US Census Block Groups for Hennepin County with subset of PL94-171 demographic data. The Hennepin County GIS Office downloaded US Census data from the following sites:Shapefiles:http://www.census.gov/cgi-bin/geo/shapefiles2010/main PL94-171:http://www.census.gov/rdo/data/2010_census_redistricting_data_pl_94-171_summary_files.html PL94-171 tabular data was post processed per instructions and stored in an Access database. Records and a subset of the 290 plus fields were extracted from the master tables using SQL statements. A copy of the statement has been included in the Lineage section of metadata. Tables were registered as a geodatabase and copied to a File Geodatabase. Shapefiles were imported into the File Geodatabase and projected to UTM Zone 15 N. The feature classes were joined to the tabular data and saved as the final US Census layer.The feature classes underwent visual inspection. The number of records were compared and checked. The attribute values were compared to existing Maptitude US Census data. Please contact the Hennepin GIS Office if you require additional PL94-171 fields. Hennepin County GIS Office A-705 Government Center Minneapolis, Minnesota 55487-075 GIS.Info@co.hennepin.mn.us Phone: 612-596-9484 FAX: 612-348-2837 The original metadata is contained below. 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.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/2010%20Census%20Block%20Groups.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data.

© US Census Bureau. See additional information in Abstract and Use Limitations. This data was modified by the Hennepin County GIS Office. This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..

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 American Community Survey (ACS) provides detailed demographic, social, economic, commuting and housing statistics based on continuous survey data collection. Data collected over the most recent 5 years are batched, summarized and published the following December.

These files contain summary data for Census Block Groups (CensusACSBlockGroup.xlsx), Tracts (CensusACSTract.xlsx), minor civil divisions (CensusACSMCD.xlsx), school districts (CensusACSSchoolDistrict.xlsx), and ZIP code tabulation areas (CensusACSZipCode.xlsx). No shapefiles are included, but these data files can be joined to associated shapefile datasets available elsewhere on this site. To facilitate this, the data files are also available as DBF tables and in a geodatabase.

Starting with the 2016-2020 data, tract and block group boundaries are those used in the 2020 Census. Starting with the 2017-2021 data, ZIP Code Tabulation Areas are those defined based on the 2020 Census. If you need the most recent ACS data for the tract and block group boundaries used in the 2010 Census, contact Matt Schroeder (information below).

This dataset provides equity-relevant characteristics for each census tract in the Twin Cities region. Formerly known as the Areas of Concentrated Poverty dataset, it has been greatly expanded to provide a more nuanced portrait of neighborhoods, with data on: demographic and socioeconomic characteristics (including multiple income levels); racial/ethnic/cultural groups; historical data on discriminatory practices; facets of housing markets; land use, environment/climate, amenities, and employment/commuting patterns. Our intention is to call attention to broader patterns of economic segregation and their root causes, and to show that census tracts are much more multifaceted than a narrow focus on poverty rates would imply.

For more background on this file, please see our website ( https://metrocouncil.org/research/place-basedequity ) -- in particular, the User Guide.

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. Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, 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. The BG boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

The Lawrence Group, under contract with Metropolitan Council, created a 1990 Census Bureau block polygon dataset for the Twin Cities Metropolitan Area (Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington Counties). This dataset is coincident with and developed using the TLG Street Centerline and Landmarks databases where 1990 block boundaries fall on those features. For those block boundaries that are defined by features not included in TLG databases, TLG used other digital resources to generate these boundaries, such as orthophotography or additional features from city and county GIS databases. TLG used it's best judgement to digitize block boundaries when the block boundaries followed nonvisible features or street extensions.

This is a MetroGIS Regionally Endorsed dataset.

This data is was downloaded from the USDA Food Access Research Atlas (11/10/2021) and joined to 2010 census tract boundaries for use in a story map for PA5885 Fall 2021.

This map provides a spatial illustration of different means by which racial segregation was historically reinforced across the cities of Minneapolis and Saint Paul. The map focuses largely on data from the 1940s, and includes the following data layers:Population by Race - Data based on 1940 US Census that shows the percentage of the non-white population at the census tract level. This data was downloaded from NHGIS, with a spatial join performed to combine the census table and historic tracts (Citation: Steven Manson, Jonathan Schroeder, David Van Riper, Katherine Knowles, Tracy Kugler, Finn Roberts, and Steven Ruggles, IPUMS National Historical Geographic Information System: Version 18.0. Minneapolis, MN: IPUMS. 2023).HOLC Map Zones by Number of Covenants - This layer displays a summary of the number of racially exclusive covenants within the area of zones designated by grade on HOLC redlining maps. The polygons of each grade zone were digitized by the Mapping Inequality Project (University of Richmond Digital Scholarship Lab) and are symbolized by the grade colors on the original maps. The data on racially exclusive covenants in Twin Cities neighborhoods was downloaded from the Mapping Prejudice Project (University of Minnesota) and is symbolized by the size of each feature.Greenbook Locations - This layer displays locations included on Greenbook travel guides from the 1940s, which indicate safe businesses for African American travelers to American Cities. This data comes from a service layer created by Shana Crosson (University of Minnesota).This spatial extent of this map is limited to the cities of Minneapolis and Saint Paul. It was created as part of an in-class exercise in February of 2024.

NCompass Technologies, under contract with Metropolitan Council, created a 2010 Census Bureau block polygon dataset for the Twin Cities Metropolitan Area (Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington Counties). This dataset is coincident with and developed using the NCT Street Centerline and Landmarks databases where 2010 block boundaries fall on those features. For those block boundaries that are defined by features not included in NCT databases, NCT used other digital resources to generate these boundaries, such as orthophotography or additional features from city and county GIS databases. NCT used it's best judgement to digitize block boundaries when the block boundaries followed nonvisible features or street extensions. Polygon centroid points were also generated by the Metropolitan Council for blocks, block groups and tracts (Census2010RealignBlockGroupPoints, Census2010RealignBlockPoints, Census2010RealignTractPoints).

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. Public Use Microdata Areas (PUMAs) are decennial census areas that permit the tabulation and dissemination of Public Use Microdata Sample (PUMS) data, American Community Survey (ACS) data, and data from other census and surveys. For the 2020 Census, the State Data Centers (SDCs) in each state, the District of Columbia, and the Commonwealth of Puerto Rico had the opportunity to delineate PUMAS within their state or statistically equivalent entity. All PUMAs must nest within states and have a minimum population threshold of 100,000 persons. 2020 PUMAs consist of census tracts and cover the entirety of the United States, Puerto Rico and Guam. American Samoa, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands do not contain any 2020 PUMAs because the population is less than the minimum population requirement. Each PUMA is identified by a 5-character numeric census code that may contain leading zeros and a descriptive name. The 2020 PUMAs will appear in the 2022 TIGER/Line Shapefiles.

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. Public Use Microdata Areas (PUMAs) are decennial census areas that permit the tabulation and dissemination of Public Use Microdata Sample (PUMS) data, American Community Survey (ACS) data, and data from other census and surveys. For the 2020 Census, the State Data Centers (SDCs) in each state, the District of Columbia, and the Commonwealth of Puerto Rico had the opportunity to delineate PUMAS within their state or statistically equivalent entity. All PUMAs must nest within states and have a minimum population threshold of 100,000 persons. 2020 PUMAs consist of census tracts and cover the entirety of the United States, Puerto Rico and Guam. American Samoa, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands do not contain any 2020 PUMAs because the population is less than the minimum population requirement. Each PUMA is identified by a 5-character numeric census code that may contain leading zeros and a descriptive name. The 2020 PUMAs will appear in the 2022 TIGER/Line Shapefiles.

2010 US Census block boundaries attributed with a subset of the PL94-171 demographic data released March 2011. Please contact the Hennepin GIS Office if you require additional PL94-171 fields. Downloaded the 2010 US Census block boundary shapefile from the US Census Bureau at the following address: http://www.census.gov/cgi-bin/geo/shapefiles2010/main Downloaded the PL94-171 demographic data from the following address: http://www.census.gov/rdo/data/2010_census_redistricting_data_pl_94-171_summary_files.html Post processed the demographic data per instructions. Stored in Access database. Set up SQL Query to create a subset of the data based on feedback from HSPHD and the GIS Office. Database documentation on file at the GIS Office. Imported the shapefile and demographic data into a File geodatabase. Joined and saved the data sets. Performed error checking by comparing against State and Maptitude versions. 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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/2010%20Census%20Blocks.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data.

© Hennepin County GIS Office This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..

The Lawrence Group, under contract with Metropolitan Council, created a 2000 Census Bureau block polygon dataset for the Twin Cities Metropolitan Area (Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington Counties). This dataset is coincident with and developed using the TLG Street Centerline and Landmarks databases where 2000 block boundaries fall on those features. For those block boundaries that are defined by features not included in TLG databases, TLG used other digital resources to generate these boundaries, such as orthophotography or additional features from city and county GIS databases. TLG used it's best judgement to digitize block boundaries when the block boundaries followed nonvisible features or street extensions.

Geospatial Analysis of Population Demographics and Traffic Density in MinneapolisIntroductionThis interactive web map provides a geospatial analysis of population distribution and traffic density for the city of Minneapolis, Minnesota. By integrating demographic data at the census tract level with real-time traffic information, the application serves as a critical tool for urban planning, transportation management, and sociological research.Data Visualization and SymbologyThe map employs distinct color schemes to represent the core datasets, allowing for intuitive visual analysis: Traffic Density: The city's road network is symbolized using a color gradient to indicate traffic volume. Segments rendered in deep red represent a high traffic density index, signifying areas of significant vehicular congestion. This transitions to a light yellow for segments experiencing lower traffic flow. Population Density: The demographic landscape is visualized using a green color ramp applied to census tract polygons. Dark green shades correspond to areas with a high population concentration, whereas lighter green shades denote regions with a lower population density. Analytical Utility and ApplicationsThe juxtaposition of these datasets reveals spatial correlations between residential density and transportation bottlenecks. This allows for data-driven inquiry into key urban challenges. The patterns visualized can help city planners and transportation authorities identify specific corridors where infrastructure investment could be most effective. Strategic improvements in these areas have the potential to optimize traffic flow, reduce commuter travel times, and decrease vehicle fuel consumption and emissions, thereby enhancing the overall sustainability and livability of Minneapolis.Interactive Features and Data ExplorationUsers are encouraged to engage with the map's interactive features for a deeper understanding of the data: Layers and Legend: Utilize the "Layers" and "Legend" tools to deconstruct the map's composition and understand the specific values associated with the color symbology. Pop-up Information: Click on individual census tracts or road segments to activate pop-up windows. These provide detailed attribute information, such as total population counts, demographic breakdowns, household income statistics, and spatial relationship metrics like nearest neighbor analysis. This application is built upon a foundational demographic data layer for Minneapolis and is enhanced by the integration of a dynamic traffic layer from the ArcGIS Living Atlas of the World.

ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists.

Users are encouraged to refer to the U.S. Census website for more information on ZCTAs: https://www.census.gov/programs-surveys/geography/guidance/geo-areas/zctas.html
and to the U.S. Postal Service for more information on ZIP Codes: https://faq.usps.com/

Which Twin Cities Metro census tracts are cost-burdened? The U.S. Department of Housing and Urban Development states that housing is “affordable” if no more than 30% of a household’s monthly income is needed for rent, mortgage payments and utilities. Households who pay more than 30% of their income on housing costs are considered cost-burdened.This map shows Median Gross Rent as a percentage of Median Household Income for Renters. Click on the census tracts to see the percentage, as well as Monthly Median Household Income for Renters and Median Gross Rent for that area.Source: American Community Survey, 2013 5-year estimates, Tables B25064 (Median Gross Rent), B25119 (Median Household Income by Tenure).Map made by CURA staff, Feb 2015.

This resouce contains two spatial datasets.

MPCA Environmental Justice Areas
MPCA Census Tribal Areas

These data represent areas of consideration for MPCA environmental justice efforts. Our goal is to highlight regions where community members are disproportionately impacted by environmental issues. The data fields in this layer are a mix of American Community Survey (ACS) 5-year estimates and calculations performed by MPCA staff. Margins of error are not considered when determining potential areas of consideration.

As an attempt to highlight environmental justice areas of concern, we show census tracts where the estimated percentage of the population that identify as people of color is 40% or greater, the estimated percentage of economically disadvantaged community members is 35% or greater, as well as the estimated percentage of the population that has limited English proficiency is 40% or greater. We also include language information for each census tract and highlight the top three estimated languages spoken by those who report that they do not speak English well.

Income Threshold:
The federal government defines poverty thresholds on an annual basis (https://www.census.gov/data/tables/time-series/demo/income-poverty/historical-poverty-thresholds.html). For MPCA use, we show an income threshold at 2 times the federal poverty threshold.

2022:
2 x $13,590 = $27,180 (individual)
2 x $27,750 = $55,500 (family of four)

This resource also contains Tribal Areas. These areas are derived by taking the maximum extent of two spatial datasets: the U.S. Census Bureau's 2022 TIGER/Line Shapefiles, Current American Indian/Alaska Native/Native Hawaiian Areas for United States; and Minnesota Department of Transportation's Tribal Government in Minnesota.