The attribute information for this layer includes links to the respective neighborhood associations. If there are questions regrading this data layer, you can either contact the City of Minneapolis Neighborhood & Community Relations office, or Minneapolis GIS.

To navigate this web map, please click on the 'Legend' tab to view the legend for the layer you're viewing. Click on the 'Layers' tab to toggle each layer on or off. If you click on a neighborhood, the popups will automatically appear in the side panel!Please view our story map for more background information!Web map created for a University of Minnesota Course: Urban GIS (Spring 2021) in order to create an accessible visualization of some of the Social Determinants of Health in Minneapolis aggregated to the neighborhood level.

In February 2019, we updated the neighborhood assignment with regards to the new police record system.

The data set is refreshed on the third day of the month at 8:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.

Feature layer generated from running the Enrich layer solution. Minneapolis_Neighborhoods were enriched

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.

NCED is currently involved in researching the effectiveness of anaglyph maps in the classroom and are working with educators and scientists to interpret various Earth-surface processes. Based on the findings of the research, various activities and interpretive information will be developed and available for educators to use in their classrooms. Keep checking back with this website because activities and maps are always being updated. We believe that anaglyph maps are an important tool in helping students see the world and are working to further develop materials and activities to support educators in their use of the maps.

This website has various 3-D maps and supporting materials that are available for download. Maps can be printed, viewed on computer monitors, or projected on to screens for larger audiences. Keep an eye on our website for more maps, activities and new information. Let us know how you use anaglyph maps in your classroom. Email any ideas or activities you have to ncedmaps@umn.edu

Anaglyph paper maps are a cost effective offshoot of the GeoWall Project. Geowall is a high end visualization tool developed for use in the University of Minnesota's Geology and Geophysics Department. Because of its effectiveness it has been expanded to 300 institutions across the United States. GeoWall projects 3-D images and allows students to see 3-D representations but is limited because of the technology. Paper maps are a cost effective solution that allows anaglyph technology to be used in classroom and field-based applications.

Maps are best when viewed with RED/CYAN anaglyph glasses!

A note on downloading: "viewable" maps are .jpg files; "high-quality downloads" are .tif files. While it is possible to view the latter in a web-browser in most cases, the download may be slow. As an alternative, try right-clicking on the link to the high-quality download and choosing "save" from the pop-up menu that results. Save the file to your own machine, then try opening the saved copy. This may be faster than clicking directly on the link to open it in the browser.

World Map: 3-D map that highlights oceanic bathymetry and plate boundaries.

Continental United States: 3-D grayscale map of the Lower 48.

Western United States: 3-D grayscale map of the Western United States with state boundaries.

Regional Map: 3-D greyscale map stretching from Hudson Bay to the Central Great Plains. This map includes the Western Great Lakes and the Canadian Shield.

Minnesota Map: 3-D greyscale map of Minnesota with county and state boundaries.

Twin Cities: 3-D map extending beyond Minneapolis and St. Paul.

Twin Cities Confluence Map: 3-D map highlighting the confluence of the Mississippi and Minnesota Rivers. This map includes most of Minneapolis and St. Paul.

Minneapolis, MN: 3-D topographical map of South Minneapolis.

Bassets Creek, Minneapolis: 3-D topographical map of the Bassets Creek watershed.

North Minneapolis: 3-D topographical map highlighting North Minneapolis and the Mississippi River.

St. Paul, MN: 3-D topographical map of St. Paul.

Western Suburbs, Twin Cities: 3-D topographical map of St. Louis Park, Hopkins and Minnetonka area.

Minnesota River Valley Suburbs, Twin Cities: 3-D topographical map of Bloomington, Eden Prairie and Edina area.

Southern Suburbs, Twin Cities: 3-D topographical map of Burnsville, Lakeville and Prior Lake area.

Southeast Suburbs, Twin Cities: 3-D topographical map of South St. Paul, Mendota Heights, Apple Valley and Eagan area.

Northeast Suburbs, Twin Cities: 3-D topographical map of White Bear Lake, Maplewood and Roseville area.

Northwest Suburbs, Mississippi River, Twin Cities: 3-D topographical map of North Minneapolis, Brooklyn Center and Maple Grove area.

Blaine, MN: 3-D map of Blaine and the Mississippi River.

White Bear Lake, MN: 3-D topographical map of White Bear Lake and the surrounding area.

Maple Grove, MN: 3-D topographical mmap of the NW suburbs of the Twin Cities.

In 1934, the Federal Housing Administration created a financial mortgage system that rated mortgage risks for properties based on various criteria but was centered on race and ethnicity. This rating system propagated racial segregation that in many ways persists today.

The FHA Underwriting Handbook incorporated color-coded real estate investment maps that classified neighborhoods based on assumptions about a community, primarily their racial and ethnic composition, and not on the financial ability of the residents to satisfy the obligations of a mortgage loan. These maps, created by the Home Owners Loan Corporation (HOLC) were used to determine where mortgages could or could not be issued.

The neighborhoods were categoriezed into four types:
Type A : Best - newer or areas stil in demand
Type B : Still Desirable - areas expected to remain stable for many years
Type C : Definitely Declining - areas in transition
Type D : Hazardous - older areas considered risky

Neighborhoods shaded red were deemed too hazardous for federally-back loans. These "red-lined" neighborhoods were where most African American residents lived.

Many have argued tha the HOLC maps institutionalized discriminating lending practices which not only perpetuated racial segregation but also led to neighborhood disinvestment. Today, neighborhoods classified as Type C and Type D in 2934 make up the majority of neighborhoods in 2016 that are Areas of Concentrated Poverty where 50% or More are People of Color.

This data set provides a statewide view of telephone exchange service area boundaries.

In addition, LATAs (local access and transport areas) and wire centers are included. At the time of the Bell System breakup, Bell operating companies were restricted to operations within specific areas called LATAs. Wire centers or 'wire center serving area', refers to the area to which local service is provided by one or more switches located at a single point. The wire center serving area is often the same area as the exchange, but a wire center can be equal to a portion of an exchange or to several exchanges combined.

The data was compiled in cooperation with the Minnesota Department of Commerce and the Minnesota incumbent local exchange carriers.

Feature layer generated from running the Buffer Features solution. Input from Minneapolis Neighborhoods - HENNEPIN.GIS.BOUNDARY_MPLS_NEIGHBORHOODS were buffered by [0.01] Feet

This dataset shows electric utility service area boundaries for the State of Minnesota. The original source data were lines hand-drawn on county highway maps. The maps were scanned and georeferenced to serve as a background for on-screen digitizing. The utilities were then given an opportunity to review and correct the service areas. Changes filed with the Public Utilities Commission (eDockets) were also reviewed to update the areas.

Race, Ethnicity, Gender - Demographic Indicators (From 2010 Census)Link: https://www2.minneapolismn.gov/census/2010/index.htm Household IncomeLinks:Poverty GuidelinesACS 2019 5 Year Estimates Household Income Disability - One or more people with disability per household vs no people with disabilityLink: ACS 2019 5 Year Estimates Disability by Household Sex and AgeLink: Sex by Age ACS 2019 5 Year Estimates

The MUSA Composite dataset depicts current and future boundaries of the Urban Service Areas (sewer service areas) based on communities' comprehensive plans for the seven-county metropolitan area of the Twin Cities of Minneapolis and Saint Paul. The dataset does not depict the precise location of current urban services (Sewer service). In other words, the Urban Service Areas designate areas that might be serviced, it does not represent the urban areas that are serviced. The depiction of Urban Service Areas provides a framework in which known urban development and anticipated future development can exist with adequate sewer capacity at efficient service levels. Seven other datasets are derived from these data: MUSA_2020, MUSA_2020_Outline, MUSA_2030, MUSA_2030_Outline, MUSA_2040, MUSA_2040_Outline, MUSA_2050, MUSA_2050_Outline, MUSA Undesignated_Reserve (see below). NOTE: As of August 2020, the derived dataset MUSA_Undesignated is no longer being used as a desingation but remain in the Attributes for an unknown period of time for historical comparison purposes but there will no longer be a designated layer as part of any download.

Each community (city or township) in the seven-county Twin Cities metropolitan area is required to complete a comprehensive plan for approval by the Metropolitan Council per the Metropolitan Land Planning Act of 1995 (Minn. Stat 473.864, Subd 2 and 473.175, Subd 1). The comprehensive plan must include a depiction of current and future boundaries of the Urban Service Areas (i.e., 2040, 2050, Post-2050).

As of March 2011, a new designation area was created specifically to address the agreed upon development plan for southeastern Scott County between the county, the city of Elko New Market and the town of New Market : 'Undesignated MUSA Reserve.' This is an area where an agreed upon acreage of urban sewer service can be added to the current MUSA by 2040 through their 2040 Comprehensive Plan. The distinction between 'Undesignated MUSA' and 'Undesignated MUSA Reserve' is that 'Undesignated MUSA' is an area within a municipal boundary defined by that municipality's comprehensive plan, whereas, 'Undesignated MUSA Reserve' is an area beyond the current municipal boundary (i.e., surrounding township) that is designated in a joint agreement by the city, town, and county to accommodate future municipal growth. Urban sewer services will not be provided to these areas until they have been annexed by the municipality (i.e., Elko New Market).

Although the Metropolitan Council provides the majority of the urban sewer service in the seven-county metropolitan area, several smaller, free-standing rural communities in the region (primarily in Carver and Scott Counties), private systems, and independent nations (Shakopee Mdewakanton Sioux Community) provide their own urban services. Where information on their urban service areas are available, it is included in this dataset.

Although the information included in this dataset is derived from the communities' 2008 and 2018 comprehensive plans, subsequent plan amendments are intended to be current within 4 months, for exact MUSA information, please contact the community.

When referring to CURRENT MUSA extent, this includes areas up to 2025 MUSA. For communities who have had their 2040 Comprehensive Plan adopted (Benchmark 2040), this includes areas up to 2030 MUSA.

These data were previously incorporated in the Comprehensive Plan Composite dataset.

This is a 15-meter raster dataset of a land cover and impervious surface classification for 2013, level two classification. The classification was created using a combination of multitemporal Landsat 8 data and LiDAR data with Object-based image analysis. By using objects instead of pixels we were able to utilize multispectral data along with spatial and contextual information of objects such as shape, size, texture and LiDAR-derived metrics to distinguish different land cover types. While OBIA has become the standard procedure for classification of high resolution imagery we found that it works equally well with Landsat imagery. For the objects classified as urban or developed, a regression model relating the Landsat greenness variable to percent impervious was developed to estimate and map the percent impervious surface area at the pixel level.

This dataset was funded by the the Minnesota Environment and Natural Resources Trust Fund (ENRTF).

Feature layer generated from running the Summarize Within solution. MinneapolisCoffeeShops_Address were summarized within Minneapolis_Neighborhoods

Feature layer generated from running the Enrich layer solution. Minneapolis_Neighborhoods were enriched

Feature layer generated from running the Summarize Within solution. MinneapolisCoffeeShops_Address were summarized within Minneapolis_Neighborhoods

The Federal Emergency Managment Agency and the MNDNR produce Digital Flood Insurance Rate Maps (DFIRM) for selected counties in the state. These maps are often referred to as FEMA Floodplain maps.

A DFIRM is the offical digital map of a community on which FEMA has delineated the special flood hazard areas, i.e., the floodplain areas where flood insurance is required for loans and where communities will administer floodplain regulations. (Note: Communities may regulate additional flood prone areas that are not on the FIRM).

Here are some of the feature classes included in the MNDNR's publication of the DFIRM Dataset:

FEMA DFIRM Base Flood Elevations
The Base Flood Elevation (BFE) table is required for any digital data where BFE lines will be shown on the corresponding Flood Insurance Rate Map (FIRM). Normally, if there are any riverine AE zones, BFE lines are required. The BFE table contains information about the BFEs within a study area. A spatial file with locational information also corresponds with this data table. BFE lines indicate the rounded whole-foot water-surface elevation of the 1-percent-annual-chance flood. The spatial elements representing BFE features are lines extending from Special Flood Hazard Area (SFHA) boundary to SFHA boundary. The BFE lines will have no visible gaps or overshoots between the SFHA boundary and the end of the BFE line at the publication scale of the DFIRM. However, the ends of the BFE lines are not necessarily snapped precisely to the SFHA boundary. Each BFE is represented by a single line. While BFE lines are depicted as wavy lines on the hardcopy FIRM, they should be primarily straight lines in the spatial data, although they may bend consistent with procedures described in Volume 1 of these Guidelines.

FEMA DFIRM Flood Hazard Zones
FEMA flood hazard delineations are used by FEMA to designate the SFHA and for insurance rating purposes. These data are the flood hazard areas that are or will be depicted on the FIRM.

FEMA DFIRM Panel Scheme Polygons
This layer contains information about the FIRM panel areas. The spatial entities representing FIRM panels are polygons. The polygon for the FIRM panel corresponds to the panel neatlines. As a result, the panels are generally rectangular. In situations where a portion of a panel lies outside of the jurisdiction being mapped, the user must refer to the S_POL_AR table to determine the portion of the panel area where the DFIRM database shows the effective flood hazard data for the mapped jurisdiction.

FEMA DFIRM Cross Sections
FEMA Cross Sections are required for any Digital Flood Insurance Rate Map database where cross sections are shown on the FIRM. Normally any FIRM that has associated flood profiles has cross sections. The corresponding attribute table contains information about cross section lines. A spatial file with locational information also corresponds with this data table. These lines represent the locations of channel surveys performed for input into the hydraulic model used to calculate flood elevations. These locations are also shown on the Flood Profiles in the Flood Insurance Study (FIS) report and can be used to cross reference the Flood Profiles to the planimetric depiction of the flood hazards. All cross sections for which a spatial location is available should be included in this table. The spatial elements representing cross sections are lines generally extending from outside the floodplain, across the entire floodplain and out the other side. Each cross section should be represented by a single line feature without the hexagons shown on each end on the hardcopy map. The location and shape of the lines should depict as accurately as possible the position of the cross section used. This is a modified Standard DFIRM Database table that includes Standard DFIRM Database items and Enhanced Database items. All items after SOURCE_CIT are Enhanced. The Enhanced DFIRM Database must contain all modeled cross sections, whether they are printed on the FIRM or not.

Extensive information regarding the source data can be found in these two documents:
FEMA DFIRM Doc Appendix L Part A.pdf
FEMA DFIRM Doc Appendix L Part B.pdf

Feature layer generated from running the Merge Layers solution.

This data contains boundaries for local general sales and use tax areas in Minnesota, along with rates and descriptions for each area. It was developed as a geographical representation of the boundaries of local general sales and use tax rates in Minnesota.

The data is updated each quarter as boundaries change and local jurisdictional units add or discontinue the implementation of local general sales and use taxes. This resource will always include the current quarter's taxing area boundaries. Updates are published thirty days in advance of the beginining of the quarter.

This dataset DOES NOT include special local taxes that may exist (lodging, entertainment, liquor, admissions and restaurant taxes).

To learn more about sales and use tax collected by the Minnesota Department of Revenue, visit this page.
https://www.revenue.state.mn.us

Feature layer generated from running the Enrich layer solution. Minneapolis Neighborhoods were enriched