Minnesota's original public land survey plat maps were created between 1848 and 1907 during the first government land survey of the state by the U.S. Surveyor General's Office. This collection of more than 3,600 maps includes later General Land Office (GLO) and Bureau of Land Management maps up through 2001. Scanned images of the maps are available in several digital formats and most have been georeferenced.

The survey plat maps, and the accompanying survey field notes, serve as the fundamental legal records for real estate in Minnesota; all property titles and descriptions stem from them. They also are an essential resource for surveyors and provide a record of the state's physical geography prior to European settlement. Finally, they testify to many years of hard work by the surveying community, often under very challenging conditions.

The deteriorating physical condition of the older maps (drawn on paper, linen, and other similar materials) and the need to provide wider public access to the maps, made handling the original records increasingly impractical. To meet this challenge, the Office of the Secretary of State (SOS), the State Archives of the Minnesota Historical Society (MHS), the Minnesota Department of Transportation (MnDOT), MnGeo and the Minnesota Association of County Surveyors collaborated in a digitization project which produced high quality (800 dpi), 24-bit color images of the maps in standard TIFF, JPEG and PDF formats - nearly 1.5 terabytes of data. Funding was provided by MnDOT.

In 2010-11, most of the JPEG plat map images were georeferenced. The intent was to locate the plat images to coincide with statewide geographic data without appreciably altering (warping) the image. This increases the value of the images in mapping software where they can be used as a background layer.

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.

DCGIS is an interactive map that provides increased functionality for advanced users as well as access to about 150 layers of GIS data, including parcel information, contour lines, aerial photography, county park amenities, park trails, bikeways, county road construction, roundabouts, floodplains and more. It allows you to create a map at any scale you wish.
The Interactive GIS Map is intended for use on any device - mobile or desktop - with high speed access.

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 data set features polygons that represent tax parcels in Aitkin County, Minnesota. Polygons are identified by Parcel Identification Number (PIN). Polygons were mapped using the legal description on file in the Recorder's Office. Redundant geometries exist for condomimiums and undivided interests. Undivided ownership occurs when two or more parties have an ownership interest in the same parcel.

This file geodatabase contains parcel data including plat boundaries, tax parcels, easements and road right of ways. Attributed Parcel Point and Polygon data represent property descriptions (legal descriptions) and land ownership in Ramsey County joined to tax parcels.

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

Attributed Parcel Point: plan_attributedparcelpoint.html
Attributed Parcel Poly: plan_attributedparcelpoly.html
Common Interest: plan_commoninterest.html
Subdivision: plan_subdivision.html
Tax Parcels: plan_taxparcel.html
Manufactured Home: plan_manufacturedhome.html
Personal Property: plan_personalproperty.html
Real Property: plan_realproperty.html
State Assessed Property: plan_stateassessedproperty.html
Conveyance Division: plan_conveyancedivision.html
Special Survey: plan_specialsurvey.html
Parcel Info: plan_parcelinfo.html
Easement: plan_easement.html
Landtie: plan_landtie.html
Right of Way: plan_rightofway.html
Historic Right of Way: plan_historicrightofway.html

In addition to search by address or parcel identification number, this site provides access to many GIS layers. These layers can be toggled on/off. The site displays information from Assessor, Land Records, Recorder and Surveyor offices within Washington County.

This dataset includes high quality (800 Dots Per Inch - DPI), 24 bit color images of Minnesota's original Public Land Survey (PLS) plats created during the first government land survey of the state from 1848 to 1907. Currently housed at the Office of the Secretary of State, these plats were created by the U.S. Surveyor General's Office. This collection of more than 3,600 maps also includes later General Land Office (GLO) and the Bureau of Land Management (BLM) maps - up to the year 2001.

Minnesota's survey plat maps serve as the fundamental legal records for real estate in the state; all property titles and descriptions stem from them. They also serve as an essential resource for surveyors and as an analytical tool for the state's physical geography prior to European settlement. Finally, they serve as a testimony to years and years of hard work by the surveying community, often under challenging conditions.

In recent years the deteriorating physical condition of the older maps and the needs of technologically more sophisticated researchers, who require access to the maps, have made handling the original paper records increasingly less practical. To meet this challenge, the Office of the Secretary of State, the State Archives of the Minnesota Historical Society, the Minnesota Department of Transportation, MnGeo (formerly the Land Management Information Center - LMIC) and the Minnesota Association of County Surveyors collaborated in a digitization project which produced images of the maps in standard TIFF, JPEG and PDF formats - nearly 1.5 terabytes worth of data. Funding was provided by the Minnesota Department of Transportation.

DOUGLAS COUNTY SURVEY/GISGIS PARCEL MAPPING GUIDELINES FOR PARCEL DISCREPANCIESIt is the intent of the Douglas County GIS Parcel Mapping to accurately identify the areas of land parcels to be valued and taxed 1. Discrepancies in areas• The Auditor/Assessor (tax) acreage areas started with the original US General Land Office (GLO) township plat maps created from the Public Land Survey (PLS) that was done between 1858 and 1871. The recovery of the PLS corners and the accurate location of these corners with GPS obtained coordinates has allowed for accurate section subdivisions, which results in accurate areas for parcels based on legal descriptions, which may be significantly different than the original areas. (See Example 2)• Any parcel bordering a meandered lake and/or a water boundary will likely have a disparity of area between the Auditor/Assessor acreages and the GIS acreages because of the inaccuracy of the original GLO meander lines from which the original areas were determined. Water lines are not able to be drafted to the same accuracy as the normal parcel lines. The water lines are usually just sketched on a survey and their dimensions are not generally given on a land record. The water boundaries of our GIS parcels are located from aerial photography. This is a subjective determination based on the interpretation by the Survey/GIS technician of what is water. Some lakes fluctuate significantly and the areas of all parcels bordering water are subject to constant change. In these cases the ordinary high water line (OHW) is attempted to be identified. Use of 2-foot contours will be made, if available. (See Example 1)• Some land records do not accurately report the area described in the land description and the description area is ignored. (See Example 3)• The parcel mapping has made every attempt to map the parcels based on available survey information as surveyed and located on the ground. This may conflict with some record legal descriptions.Solutions• If an actual survey by a licensed Land Surveyor is available, it will be utilized for the tax acreage.• If the Auditor/Assessor finds a discrepancy between the tax and GIS areas, they will request a review by the County Survey/GIS department.• As a starting guideline, the County Survey/GIS department will identify all parcels that differ in tax area versus GIS parcel area of 10 % or more and a difference of at least 5 acres. (This could be expanded later after the initial review.)• Each of these identified parcels will be reviewed individually by the County Survey/GIS department to determine the reason for the discrepancy and a recommendation will be made by the County Survey/GIS department to the Auditor/Assessor if the change should be made or not.• If a change is to be made to the tax area, a letter will be sent to the taxpayer informing them that their area will be changed during the next tax cycle, which could affect their property valuation. This letter will originate from the Auditor/Assessor with explanation from the County Survey/GIS department. 2. Gaps and Overlaps• Land descriptions for adjoining parcels sometimes overlap or leave a gap between them.o In these instances the Survey/GIS technician has to make a decision where to place this boundary. A number of circumstances are reviewed to facilitate this decision as these dilemmas are usually decided on a case by case basis. All effort will be made to not leave a gap, but sometimes this is not possible and the gap will be shown with “unknown” ownership. (Note: The County does not have the authority to change boundaries!)o Some of the circumstances reviewed are: Which parcel had the initial legal description? Does the physical occupation of the parcel line as shown on the air photo more closely fit one of the described parcels? Interpretation of the intent of the legal description. Is the legal description surveyable?Note: These overlaps will be shown on the GIS map with a dashed “survey line” and accompanying text for the line not used for the parcel boundary. 3. Parcel lines that do not match location of buildings Structures on parcels do not always lie within the boundaries of the parcel. This may be a circumstance of building without the benefit of a survey or of misinterpreting these boundaries. The parcel lines should be shown accurately as surveyed and/or described regardless of the location of structures on the ground. NOTE: The GIS mapping is not a survey, but is an interpretation of parcel boundaries predicated upon resources available to the County Survey/GIS department.Gary Stevenson Page 1 7/21/2017Example 1Example 2A Example 2B Example 3

Easy to navigate and search for property information. Features a large map area and a printable property card. It also includes additional map features such as streets, lakes and parks.

The 2022 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The cartographic boundary files 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 generalized boundaries of most incorporated places in this file are based on those as of January 1, 2022, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CDPs are based on those delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 55 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Becker, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Houston, Isanti, Itasca, Jackson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Murray, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.

If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.

County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.

This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.

There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.

The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.

DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public open space and voluntarily provided, private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastral Theme (http://www.fgdc.gov/ngda-reports/NGDA_Datasets.html). PAD-US is an ongoing project with several published versions of a spatial database of areas dedicated to the preservation of biological diversity, and other natural, recreational or cultural uses, managed for these purposes through legal or other effective means. The geodatabase maps and describes public open space and other protected areas. Most areas are public lands owned in fee; however, long-term easements, leases, and agreements or administrative designations documented in agency management plans may be included. The PAD-US database strives to be a complete “best available” inventory of protected areas (lands and waters) including data provided by managing agencies and organizations. The dataset is built in collaboration with several partners and data providers (http://gapanalysis.usgs.gov/padus/stewards/). See Supplemental Information Section of this metadata record for more information on partnerships and links to major partner organizations. As this dataset is a compilation of many data sets; data completeness, accuracy, and scale may vary. Federal and state data are generally complete, while local government and private protected area coverage is about 50% complete, and depends on data management capacity in the state. For completeness estimates by state: http://www.protectedlands.net/partners. As the federal and state data are reasonably complete; focus is shifting to completing the inventory of local gov and voluntarily provided, private protected areas. The PAD-US geodatabase contains over twenty-five attributes and four feature classes to support data management, queries, web mapping services and analyses: Marine Protected Areas (MPA), Fee, Easements and Combined. The data contained in the MPA Feature class are provided directly by the National Oceanic and Atmospheric Administration (NOAA) Marine Protected Areas Center (MPA, http://marineprotectedareas.noaa.gov ) tracking the National Marine Protected Areas System. The Easements feature class contains data provided directly from the National Conservation Easement Database (NCED, http://conservationeasement.us ) The MPA and Easement feature classes contain some attributes unique to the sole source databases tracking them (e.g. Easement Holder Name from NCED, Protection Level from NOAA MPA Inventory). The "Combined" feature class integrates all fee, easement and MPA features as the best available national inventory of protected areas in the standard PAD-US framework. In addition to geographic boundaries, PAD-US describes the protection mechanism category (e.g. fee, easement, designation, other), owner and managing agency, designation type, unit name, area, public access and state name in a suite of standardized fields. An informative set of references (i.e. Aggregator Source, GIS Source, GIS Source Date) and "local" or source data fields provide a transparent link between standardized PAD-US fields and information from authoritative data sources. The areas in PAD-US are also assigned conservation measures that assess management intent to permanently protect biological diversity: the nationally relevant "GAP Status Code" and global "IUCN Category" standard. A wealth of attributes facilitates a wide variety of data analyses and creates a context for data to be used at local, regional, state, national and international scales. More information about specific updates and changes to this PAD-US version can be found in the Data Quality Information section of this metadata record as well as on the PAD-US website, http://gapanalysis.usgs.gov/padus/data/history/.) Due to the completeness and complexity of these data, it is highly recommended to review the Supplemental Information Section of the metadata record as well as the Data Use Constraints, to better understand data partnerships as well as see tips and ideas of appropriate uses of the data and how to parse out the data that you are looking for. For more information regarding the PAD-US dataset please visit, http://gapanalysis.usgs.gov/padus/. To find more data resources as well as view example analysis performed using PAD-US data visit, http://gapanalysis.usgs.gov/padus/resources/. The PAD-US dataset and data standard are compiled and maintained by the USGS Gap Analysis Program, http://gapanalysis.usgs.gov/ . For more information about data standards and how the data are aggregated please review the “Standards and Methods Manual for PAD-US,” http://gapanalysis.usgs.gov/padus/data/standards/ .

The published representation of real property areas, combined with assessing and tax information from CAMA and Tax systems.

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

Exterior boundary, Annexation boundary, and County boundary coverages are examined to remove all overshoots, unwanted intersections; insure polygons are closed; and to see that there are no missing or duplicate polygon labels. Each symbolic layer is individually examined for completeness. There is no line duplication in exterior or annexation coverages. MCD's with detached or non-contiguous units (polygons) have the same polygon link/label code in each of their units. Completeness in the checking process is examined through the examination and comparison of all detail collected by County Staff. Sources used included: City Clerks, County Auditor's Office, Washington County Historical Courthouse, MN State Historical Society, Secretary of State, Minnesota Municipal Board, and MNDOT. https://www.co.washington.mn.us/1609/Municipal-Boundaries

The "Map Image Layer - Watershed Boundaries" is the Map Image Layer of Watershed Boundaries. It has been designed specifically for use in ArcGIS Online (and will not directly work in ArcMap or ArcPro). This data has been modified from the original source data to serve a specific business purpose. This data is for cartographic purposes only.The Watershed Boundaries Data Group contains the following layers: DNR Catchments (MnDNR)HUC 12 Boundaries (USGS)HUC 12 IWM Group Boundaries (MPCA)HUC 10 Boundaries (USGS)HUC 8 Boundaries (USGS): HUC 8s represent part or all of a surface drainage basin, a combination of drainage basins, or a distinct hydrologic feature. There are 80 HUC 2s in Minnesota. (i.e. Zumbro (07040004))HUC 6 Boundaries (USGS): HUC 6s are areas which divide the subregions into more than 350 hydrologic accounting units. Minnesota has 17 of the nations hydrologic accounting units: Northwestern Lake Superior (040101), St. Louis (040102), Southwestern Lake Superior (040103), Mississippi Headwaters (070101), Upper Mississippi-Crow-Rum (070102), Minnesota (070200), St. Croix (070300), Upper Mississippi-Black-Root (070400), Upper Mississippi-Maquoketa-Plum (070600), Upper Mississippi-Skunk-Wapsipinicon (070801), Iowa (070802), Des Moines (071000), Upper Red (090201), Lower Red (090203), Rainy (090300), Big Sioux (101702), Missouri-Little Sioux (102300).HUC 4 Boundaries (USGS): HUC 4s are geographic subregions which are drained by a river system, a reach of river and its tributaries in that reach, a closed basin, or a group of streams forming a coastal drainage areas. Minnesota has 12 of the nations 222 subregions: Western Lake Superior (0401), Mississippi Headwaters (0701), Minnesota (0702), St. Croix (0703), Upper Mississippi-Black-Root (0704), Upper Mississippi-Maquoketa-Plum (0706), Upper Mississippi-Iowa-Skunk-Wapsipinicon (0708), Des Moines (0710), Red (0902), Rainy (0903), Missouri-Big Sioux (1017), Missouri-Little Sioux (1023).HUC 2 Boundaries (USGS): HUC 2s are geographic regions which contain the drainage of a major river or a series of rivers. Minnesota has 4 of the nations 21 regions: Great Lakes (R04), Upper Mississippi (R07), Souris-Red-Rainy (R09), and Missouri (R10).These datasets have not been optimized for fast display (but rather they maintain their original shape/precision), therefore it is recommend that filtering is used to show only the features of interest. For more information about using filters please see "Work with map layers: Apply Filters": https://doc.arcgis.com/en/arcgis-online/create-maps/apply-filters.htmFor additional information about the Watershed Boundary Dataset please see:United States Geological Survey Water-Supply Paper 2294: https://pubs.usgs.gov/wsp/wsp2294/Hydrologic Units, The National Atlas of the United State of America: https://pubs.usgs.gov/gip/hydrologic_units/pdf/hydrologic_units.pdfNational Hydrography Dataset, Watershed Boundary Dataset: https://www.usgs.gov/core-science-systems/ngp/national-hydrography/watershed-boundary-dataset

This resource is a compilation of density and magnetic susceptibility measurements from outcrops and drill holes in Minnesota. This web map application is made available by Minnesota Geological Survey; see http://www.mngs.umn.edu/service.htm for more information. Layers provided include bedrock geology and faults, county boundaries, topographic properties, and rock property locations. This information was provided by the Minnesota Geological Survey and made available for distribution through the National Geothermal Data System.

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!

Minnesota Valley NWR units. Minnesota Valley National Wildlife Refuge offers close to 50 miles of trails along the Minnesota River from Bloomington to Henderson. Learn more about the trails and current conditions below. Click here to view an interactive map. Or, download one of the following trail maps to print or save to your device. Visit our units like Black Dog: Open season: Open year round - walking spring to fall, snowshoeing, cross-country skiing and fat tire biking in the winter. This trail is open to cycling. Length: 1.5 miles one way. Location of trail: Louisville Swamp Unit, Jordan. Natural surface. Middle Road passes through areas of marsh, crosses a large stream, and passes the junction with the Mazomani Trail South, then wanders through restored prairie and forest until it meets the State Trail junction heading south. This trail experiences seasonal flooding. Trailhead address: 3801 W 145th St, Shakopee, MN 55379.