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

The TRS digital data set represents the Township, Range, and Section boundaries of the state. Beginning in the late 1840s, the federal government began surveying Minnesota as part of the Public Land Survey System (PLSS). The resulting network of land survey lines divided the state into townships, ranges, sections, quarter sections, quarter-quarter sections and government lots, and laid the groundwork for contemporary land ownership patterns.

The township, range and section boundaries were digitized at MnGeo (formerly known as the Land Management Information Center - LMIC) from stable base mylars of the U.S. Geological Survey (USGS) 30-minute latitude by 60-minute longitude map series (1:100,000-scale). All survey lines were extended across water bodies despite the fact that U.S. Geological Survey base maps depict them only on land. This addition allows all sections and townships to be represented as closed areas (polygons) ensuring that township and range location can be determined for any point in the state. It also means that the data set is not affected if lake levels change over time.

This map shows the free and open data status of county public geospatial (GIS) data across Minnesota. The accompanying data set can be used to make similar maps using GIS software.

Counties shown in this dataset as having free and open public geospatial data (with or without a policy) are: Aitkin, Anoka, Becker, Beltrami, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Grant, Hennepin, Hubbard, Isanti, Itasca, Kittson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Meeker, Mille Lacs, Morrison, Mower, Norman, Olmsted, Otter Tail, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Scott, Sherburne, Stearns, Steele, Stevens, St. Louis, Traverse, Waseca, Washington, Wilkin, Winona, Wright and Yellow Medicine.

To see if a county's data is distributed via the Minnesota Geospatial Commons, check the Commons organizations page: https://gisdata.mn.gov/organization

To see if a county distributes data via its website, check the link(s) on the Minnesota County GIS Contacts webpage: https://www.mngeo.state.mn.us/county_contacts.html

description: The TRSQ digital data set represents the Township, Range, Section, Quarter section, and Quarter-quarter section divisions of the state. Beginning in the late 1840s, the federal government began surveying Minnesota as part of the Public Land Survey System (PLSS). The resulting network of land survey lines divided the state into townships, ranges, sections, quarter sections, quarter-quarter sections and government lots, and laid the groundwork for contemporary land ownership patterns. The quarter-quarter section remains an important subdivision for rural Minnesota since these lines are used to define local boundaries, roads, and service areas. All survey lines were extended across water bodies despite the fact that U.S. Geological Survey (USGS) base maps depict them only on land. This addition allows all sections and townships to be represented as closed areas ensuring that township and range location can be determined for any point in the state. It also means that the data is not affected if lake levels change over time. The township, range and section boundaries were digitized at MnGeo (formerly the Land Management Information Center - LMIC) from the USGS 30' x 60' map series (1:100,000-scale). Quarter section and quarter-quarter section subdivisions were calculated using the section lines. They were not digitized from original plat book survey lines or from the meandered lines that surveyors laid out around water bodies. The existence of government lots within a quarter-quarter section is recorded in the data set; however, the government lot boundaries were not digitized. If a quarter-quarter section contains more than one government lot, the number of lots is recorded -- see Lineage, Section 2, for more detail. Note: For most uses, TRSQ has been superseded by the Minnesota Department of Natural Resources (DNR) 1:24,000-scale 'Control Point Generated PLS' data set which is free online. See https://gisdata.mn.gov/dataset/plan-mndnr-public-land-survey for more information. Also, many county surveyors offices have more accurate PLS (Public Land Survey) data sets. For county webpages and contact information, see http://www.mngeo.state.mn.us/cty_contacts.html .; abstract: The TRSQ digital data set represents the Township, Range, Section, Quarter section, and Quarter-quarter section divisions of the state. Beginning in the late 1840s, the federal government began surveying Minnesota as part of the Public Land Survey System (PLSS). The resulting network of land survey lines divided the state into townships, ranges, sections, quarter sections, quarter-quarter sections and government lots, and laid the groundwork for contemporary land ownership patterns. The quarter-quarter section remains an important subdivision for rural Minnesota since these lines are used to define local boundaries, roads, and service areas. All survey lines were extended across water bodies despite the fact that U.S. Geological Survey (USGS) base maps depict them only on land. This addition allows all sections and townships to be represented as closed areas ensuring that township and range location can be determined for any point in the state. It also means that the data is not affected if lake levels change over time. The township, range and section boundaries were digitized at MnGeo (formerly the Land Management Information Center - LMIC) from the USGS 30' x 60' map series (1:100,000-scale). Quarter section and quarter-quarter section subdivisions were calculated using the section lines. They were not digitized from original plat book survey lines or from the meandered lines that surveyors laid out around water bodies. The existence of government lots within a quarter-quarter section is recorded in the data set; however, the government lot boundaries were not digitized. If a quarter-quarter section contains more than one government lot, the number of lots is recorded -- see Lineage, Section 2, for more detail. Note: For most uses, TRSQ has been superseded by the Minnesota Department of Natural Resources (DNR) 1:24,000-scale 'Control Point Generated PLS' data set which is free online. See https://gisdata.mn.gov/dataset/plan-mndnr-public-land-survey for more information. Also, many county surveyors offices have more accurate PLS (Public Land Survey) data sets. For county webpages and contact information, see http://www.mngeo.state.mn.us/cty_contacts.html .

description: The TRS digital data set represents the Township, Range, and Section boundaries of the state. Beginning in the late 1840s, the federal government began surveying Minnesota as part of the Public Land Survey System (PLSS). The resulting network of land survey lines divided the state into townships, ranges, sections, quarter sections, quarter-quarter sections and government lots, and laid the groundwork for contemporary land ownership patterns. The township, range and section boundaries were digitized at MnGeo (formerly known as the Land Management Information Center - LMIC) from stable base mylars of the U.S. Geological Survey (USGS) 30-minute latitude by 60-minute longitude map series (1:100,000-scale). All survey lines were extended across water bodies despite the fact that U.S. Geological Survey base maps depict them only on land. This addition allows all sections and townships to be represented as closed areas (polygons) ensuring that township and range location can be determined for any point in the state. It also means that the data set is not affected if lake levels change over time.; abstract: The TRS digital data set represents the Township, Range, and Section boundaries of the state. Beginning in the late 1840s, the federal government began surveying Minnesota as part of the Public Land Survey System (PLSS). The resulting network of land survey lines divided the state into townships, ranges, sections, quarter sections, quarter-quarter sections and government lots, and laid the groundwork for contemporary land ownership patterns. The township, range and section boundaries were digitized at MnGeo (formerly known as the Land Management Information Center - LMIC) from stable base mylars of the U.S. Geological Survey (USGS) 30-minute latitude by 60-minute longitude map series (1:100,000-scale). All survey lines were extended across water bodies despite the fact that U.S. Geological Survey base maps depict them only on land. This addition allows all sections and townships to be represented as closed areas (polygons) ensuring that township and range location can be determined for any point in the state. It also means that the data set is not affected if lake levels change over time.

Washington County, MN Tax Parcels. An independent manual check of the parcel data was made at the time of its initial development whereby all geo-coded parcel legal descriptions in a PLSS section were reinterpreted and examined for accuracy and completeness on the hard copy check plot. As each new plat or lot division occurs, a similar process is repeated for the new additions during the maintenance period. Multiple lines of ownership indicating ambiguity in property line location are merged into a single line if falling within 3 feet of each other. Gaps or overlaps in these situations are not shown. In some cases where two lines converge; e.g., where at one end the two lot lines are within 0.50 feet of each other and at the other end they are within 6.00 feet of each other they may be merged because the average discrepancy is 3 feet or less. Where gaps or overlaps exist in excess of approximately 3 feet in width, they are shown with text notation indicating APPARENT GAP or AREA OF DISCREPANCY.

This layer is a component of Natural resources interactive map.

A downloadable, printable 8.5 x 11 inch PDF map of Camden Township and surrounding area.

This set of GeoTIFF and EPPL7 files represents the Minnesota Department of Transportation's County Highway Map Series in georeferenced image formats. These images of the standard Mn/DOT County Highway Map product can be used in GIS systems and overlayed with other GIS information. The origin of this data is Mn/DOT's Microstation CAD system, where all linework, feature type coding, and symbolization is stored and updated. To produce these data sets, Mn/DOT exported the data from Microstation into postscript files. LMIC then imported the data into GIS systems for georeferencing and further processing. The GeoTIFF data are distributed in both County Highway Map map sheet and full county extents; EPPL7 data sets are distributed only as full county files. Map collars have been removed. This data set represents the Mn/DOT County Highway Map as of January 1, 2002.

Map Catalog is powered by the Memento Server software and provides a continuous view across multiple geospatial PDFs. The PDF maps currently available are 1K USNG (topo and aerial) maps from four metro counties(Anoka, Carver, Dakota and Ramsey), 1K USNG Topo of cities and state parks in Minnesota, 10K USNG Aerial maps for Minnesota, US Topo for the metro and Dakota County Park maps, City Street maps and Half Section maps. Map update frequency varies.

This is the standard Minnesota State County Boundary dataset that is used by MNDNR and many other state agencies. It is maintained by the MNDNR Lands and Minerals Division.

Please read at the accuracy and lineage sections of this metadata to make sure this dataset is appropriate for your application!

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.

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

Vector polygon map data of property parcels from Itasca County, Minnesota containing 77967 features.

​

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

​

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

​

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

About this itemThanks for your interest in our public access GIS hub site. This site brings many of our most popular mapping resources together in one place for easy access. Users can quickly find the content they need and discover other areas of interest by exploring a series of Map Galleries. For those seeking GIS data, an open data portal with a growing collection of local datasets is just a click or tap away. Author/ContributorKyle ObergOrganizationCook CountyOrg Websiteco.cook.mn.us

This layer is a component of Natural resources interactive map.

This dataset contains polygons representing individual taxed parcels or individual tax-exempt parcels tracked for taxing purposes. It also contains polygons representing the locations of multiple tax properties. In the case of multiple tax properties, several parcel polygons may be stacked on top of one another. These are multiple tax parcels that cannot be delineated on a two-dimensional map, including both taxed and tax-exempt parcels. The parcels are represented with identical geometries but have different parcel IDs and associated tax attributes. The PID field contains the property ID number for each parcel.Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/County%20Tax%20Parcels.pdf

© This dataset is compiled monthly by the Hennepin County GIS Office from parcel geometry that is created and maintained by the Hennepin County Resident and Real Estate Services Survey Division and tax attributes extracted from the Hennepin County Real Estate Services property tax information system.

Compilation of 100,000 scale bedrock maps from MGS County Atlas products beginning with C-08, Fillmore County and ending with the newest Atlas, the Bedrock Geology of Lake County Minnesota for a total of 45 100k maps. Because the maps have been created by different authors over a significant time period, the edges of each map do not always align with adjacent maps and for this project no attempt was made to harmonize them. In addition, the map units may also have been change or updated between products separated by several years. However, in this compilation a single attribute table has been developed that includes all of the map labels as well as descriptive text and other fields that allow interpretations to be made between maps. Many of the map units are also part of the 2011 bedrock geologic map of Minnesota which provides another method of interpretation and description. In addition, the source field identifies which Atlas the polygons were originally part of and which will have additional information available about the units. This map is the foundation of a database of 100,000 bedrock mapping in Minnesota that is intended to be updated as new County Atlas mapping is completed and as time permits to be used to develop a common index of bedrock geologic units in Minnesota.

This map allows users to access a variety of survey and survey related information and documents by following various links associated with map features such as Control Points, Public Land Survey Corners, Certificates of Survey, Parcel Maps, and Section Worksheets. Disclaimer The information available on this web site is a compilation of Washington County Records. The Washington County Surveyor's Office is not responsible for inaccuracies or timeliness of any of the information presented on this web site. Alteration of the data on this web is strictly prohibited and could result in penalty under law.

FEMA Framework Basemap datasets comprise six of the seven FGDC themes of geospatial data that are used by most GIS applications (Note: the seventh framework theme, orthographic imagery, is packaged in a separate NFIP Metadata Profile): cadastral, geodetic control, governmental unit, transportation, general structures, hydrography (water areas & lines. These data include an encoding of the geographic extent of the features and a minimal number of attributes needed to identify and describe the features. (Source: Circular A16, p. 13) This data set contains 3-band natural color imagery from the National Agricultural Imagery Program (NAIP). NAIP acquires digital ortho imagery during the agricultural growing seasons in the continental U.S. A primary goal of the NAIP program is to enable availability of ortho imagery within one year of acquisition. The source files are 1 meter ground sample distance (GSD) ortho imagery rectified to a horizontal accuracy of within +/- 5 meters of reference digital ortho quarter quads (DOQQ's) from the National Digital Ortho Program (NDOP) or from NAIP. The tiling format of NAIP imagery is based on a 3.75' x 3.75' quarter quadrangle with a 300 meter buffer on all four sides. NAIP imagery is formatted to the UTM coordinate system using NAD83. NAIP imagery may contain as much as 10% cloud cover per tile. This file was generated by compressing NAIP imagery that cover the county extent. MrSID compression was used. Target values for the compression ratio are (15:1). (Note: The Minnesota Geospatial Information Office (MnGeo) has created this metadata record to describe the entire NAIP2009 dataset, using information from Farm Service Agency metadata. Each county file is accompanied by the original FSA metadata for that county.)