If there are any issues with the data in this map, service, or shp file please contact the Minneapolis GIS office.

This medium-scale (nominally 1:24,000) dataset represents the boundaries of cities, townships, and unorganized territories (CTUs) in Minnesota. The Minnesota Geospatial Information Office created the initial CTU dataset by updating a municipal boundary file maintained by the Minnesota Department of Transportation (MnDOT). Update information was gathered primarily from boundary adjustment records maintained by the Office of Administrative Hearings, Municipal Boundary Adjustment Unit. MnDOT has maintained the file since 2014.

Note: Cities and Townships represented in this dataset are political (civil) townships as recognized by the State of MN, not congressional or public land survey townships. Unorganized territory subdivisions are those defined by the U.S. Bureau of the Census, which often differ from those defined by a county.

Check other metadata records in this package for more information on CTUInformation.


Link to ESRI Feature Service:

City, Township, and Unorganized Territory in Minnesota: City, Township, and Unorganized Territory

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.

This layer depicts the city boundary for the City of Saint Paul.

This is the feature map service for the City of Minneapolis Election Precinct Boundaries Adopted March 24, 2022.

The major water bodies within the Minneapolis city limits. Includes polygons for the Mississippi River, major lakes, and streams. If there are any issues with the data in this map, service, or shp file please contact the Minneapolis GIS office.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2022, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census, but some CDPs were added or updated through the 2022 BAS as well.

Jurisdictional crosswalk is a combination of data from federal sources and legacy MnDOT data. It creates a crosswalk or translation between various ID systems for city, township, and unorganized territories within the State of Minnesota.

Check other metadata records in this package for more information on Jurisdiction Lookup Information.


Links to ESRI Feature Services:

City Boundaries in Minnesota: City Boundaries

Jurisdiction Lookup for Minnesota: Jurisdiction Lookup

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.

In general terms, MS4s are publicly owned or operated stormwater infrastructure, used solely for stormwater, and which are not part of a publicly owned wastewater treatment system. Examples of stormwater infrastructure include curbs, ditches, culverts, stormwater ponds and storm sewer pipes.

By federal rule, stormwater systems in urban areas are labeled Mandatory MS4s. By state rule, permit applicability is based on urbanized area as defined by the latest decennial census, population, and proximity to special receiving waters (e.g., trout streams, Outstanding Resource Value Waters, and impaired waters). In addition, Minnesota requires MS4s located at least partially within an urbanized area that have resident capacity, bed count, or average daily user population of 1,000 or more to obtain a permit. These are referred to as non-traditional MS4s.

MS4 owners must establish stormwater pollution prevention programs that include public education and involvement, illicit discharge elimination, construction-site runoff controls, and stormwater best management practices.

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.

This is the feature map service for the City of Minneapolis City Council Ward Boundaries that were redistricted and adopted in April 1st of 1992.

This layer defines the district boundaries for the Metropolitan Council members.

NOTES:
- The Metropolitan Council Districts were enacted on May 19, 2023, using plan MC2023-2.
- Council member names and spellings are taken directly from the Metropolitan Council web site and press releases.
- Hanover, New Prague, Northfield, and Rockford have been removed from the district boundaries.
- Cities of Minneapolis, St. Paul, Edina, Maplewood and Woodbury have populations split into more than one Council District.
- The actual descriptions of Metropolitan Council District boundaries were taken from Minnesota Statutes 2022, 473.123 http://www.revisor.leg.state.mn.us/stats/473/123.html
- The 2023 plan files, details and components passed by the 2023 MN Legislature can be found at https://www.gis.lcc.mn.gov/redist2020/MetCouncil/mc2023_2/.
- For the map and data available from the Metropolitan Council, district boundaries were adjusted to conform to existing geography employed by the Metropolitan Council.
- Adjustments for district boundaries that fall on city/township boundaries are updated on a quarterly basis with data from counties.
- Met Council Districts are defined every 10 years.

This file geodatabase contains datasets that represent municipal boundaries, commissioner district boundaries and park boundaries.

The following links can be used to obtain individual metadata pages:

Municipal Boundaries: bdry_city.html
2012 County Commissioner Districts: bdry_commissionerdist2012.html
Park Boundaries: bdry_park.html

This map of Minnesota cities, townships, and counties was published by MnGeo in January 2019. The primary data set for the map is the "Cities, Townships, and Unorganized Territories" (MnCTU) data maintained by the Minnesota Department of Transportation. Other reference data on the map include County Seats and Other Cities, County Boundaries, Interstate, US Trunk, and State Trunk Highways, Major Rivers, Lakes, County and State Boundaries. The download is a PDF file with embedded layers that can be printed at E-scale (36" x 48").

This feature class is basically a representation of all cities/towns and townships within Douglas County.This is the most up to date boundary for Douglas County with annexations for Alexandria City. Current boundary used in apps.

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.

This dataset indicates areas designated as eligible for resources provided through the Great Streets Neighborhood Business District Program. Eligible areas were designated in The Minneapolis Plan for Sustainable Growth and consist of Activity Centers, Commercial Nodes, Commercial Corridors, and LRT Station Areas. Exact parcel boundaries of Activity Centers and Commercial Nodes are identified in The Minneapolis Plan. Commercial Corridor areas are generally defined as a one block radius from designated corridors. LRT Station Areas are defined as a ½ mile radius from each LRT station outside of downtown. Some staff discretion was used in determining precise boundaries for Commercial Corridors and LRT Station Areas in cases where roadways or other natural boundaries made exact definitions unclear.

Each area is categorized based on a number of metrics used to determine its economic health and opportunity. Varying levels of Great Streets program resources are available, based on this categorization. These categories are defined as:

Intervene: Areas that are experiencing weak development interest or significant obstacles to attaining the City’s commercial development or business investment goals.

Support: Areas showing signs of strength, but that remain fragile and have some barriers to market development and business investment.

Monitor: Areas with strong market development and business activity.

For more information, please see the City of Minneapolis Great Streets Program website: http://www.ci.minneapolis.mn.us/cped/ba/cped_great_streets_home

Sector

Location within the city. Program resources are administered by different City staff based on Sector.

Category

Categorical classification of area’s economic health and opportunity.

AreaType

Geographic type, based on Minneapolis Plan designations.

Name

Name of specific geographic area.

This is the feature map service for the City of Minneapolis City Park Commissioner District Boundaries that were redistricted and adopted in March 2nd, 2022. These boundaries also serve as the Minneapolis Public School Board Districts.

This layer defines the district boundaries for the Metropolitan Council members.

NOTES:
- The current Metropolitan Council Districts were enacted in 2013.
- Council member names and spellings are taken directly from the Metropolitan Council web site and press releases.
- Hanover, New Prague, Northfield, and Rockford have been removed from the district boundaries.
- Only the cities of Minneapolis and St. Paul have significant populations split into more than one Council District. Chanhassen, Hastings and Spring Lake Park have small areas accross county boundaries in another Council district.
- The actual descriptions of Metropolitan Council District boundaries were taken from Minnesota Statutes 2012, 473.123 http://www.revisor.leg.state.mn.us/stats/473/123.html
- Adjustments for district boundaries that fall on city/township boundaries are updated on a quarterly basis with data from counties.
-The 2013 plan files, details and components passed by the 2013 MN Legislature can be found at http://www.gis.leg.mn/html/redistricting.html
-For the map and data available from the Metropolitan Council, district boundaries were adjusted to conform to existing geography employed by the Metropolitan Council.