This dataset attempts to represent the point locations of every educational program in the state of Minnesota that is currently operational and reporting to the Minnesota Department of Education. It can be used to identify schools, various individual school programs, school districts (by office location), colleges, and libraries, among other programs. Please note that not all school programs are statutorily required to report, and many types of programs can be reported at any time of the year, so this dataset is by nature an incomplete snapshot in time.

Maintenance of these locations are a result of an ongoing project to identify current school program locations where Food and Nutrition Services Office (FNS) programs are utilized. The FNS Office is in the Minnesota Department of Education (MDE). GIS staff at MDE maintain the dataset using school program and physical addresses provided by local education authorities (LEAs) for an MDE database called "MDE ORG". MDE GIS staff track weekly changes to program locations, along with comprehensive reviews each summer. All records have been reviewed for accuracy or edited at least once since January 1, 2020.

Note that there may remain errors due to the number of program locations and inconsistency in reporting from LEAs and other organizations. In particular, some organization types (such as colleges and treatment programs) are not subject to annual reporting requirements, so some records included in this file may in fact be inactive or inaccurately located.

Note that multiple programs may occur at the same location and are represented as separate records. For example, a junior and a senior high school may be in the same building, but each has a separate record in the data layer. Users leverage the "CLASS" and "ORGTYPE" attributes to filter and sort records according to their needs. In general, records at the same physical address will be located at the same coordinates.

This data is now available in CSV format. For that format only, OBJECTID and Shape columns are removed, and the Shape column is replaced by Latitude and Longitude columns.

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

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees.

This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate system from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

NOTICE: The standard set of attributes changed to the MN Parcel Data Transfer Standard on 1/1/2019.
https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

See section 5 of the metadata for an attribute summary.

Detailed information about the attributes can be found in the Metro Regional Parcel Attributes document.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

This is a MetroGIS Regionally Endorsed dataset.

Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

Anoka = http://www.anokacounty.us/315/GIS
Caver = http://www.co.carver.mn.us/GIS
Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
Hennepin = https://gis-hennepin.hub.arcgis.com/pages/open-data
Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
Scott = http://opendata.gis.co.scott.mn.us/
Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

The DNR Hydrography Dataset is the centralized SDE data storage for master versions of DNR hydrographic spatial features (effective 2012). It includes the authoritative versions of the following statewide feature classes:

• DNR Hydrography - DNR Watersheds - Level 08 - All Catchments (polygons) https://gisdata.mn.gov/dataset/geos-dnr-watersheds


• DNR Hydrography - All Water Features (polygons)


• DNR Hydrography - Public Waters Basins (polygons) https://gisdata.mn.gov/dataset/water-mn-public-waters


• DNR Hydrography - Stream Routes with Kittle Numbers and Mile Measures (measured polyline routes) https://gisdata.mn.gov/dataset/water-measured-kittle-routes


• DNR Hydrography - Hydrologic Points of Interest (HPOI) (points) - in development

The DNR Hydrography Dataset is a collection of the "best available" DNR spatial features representing MN surficial hydrology. These features originate from multiple sources representing a range of scales and accuracies. All feature classes are (will eventually be) topologically related and will function as an integrated set of statewide features. Most DNR hydro-related layers are (will eventually be) derived from this central data storage so that master features may be edited once and then remain synchronized among all derived layers.

NOTE: The DNR Hydrography dataset replaces the older DNR 24K and DNR 100K data layers, including those derived layers listed below. Users should discontinue use of these older layers.

100K: dnr_100k_hydro_area_features, dnr_100k_hydro_stream_centerlines, lake_dnrpy2, wetl_dnrpy2, strm_usgsln2
24K: dnr_24k_lakes_and_open_water, dnr_24k_rivers_and_streams, dnr_24k_perennial_stream, lake_openwpy3, strm_baseln3, strm_pwiln3

This is the authoritative public subset of the compiled Minnesota statewide parcel dataset. By authoritative, we mean this is the official source of statewide parcel data compiled from the counties that have opted-in to be included. Counties are the authoritative source and owner of parcel data. Quarterly, MnGeo compiles and standardizes the county data using the Minnesota Geospatial Advisory Council's parcel data standard. In the compilation process, some data content is standardized or otherwise modified (capitalization and address parsing are the most common changes). The full opt-in compiled parcel metadata record can be found on the Minnesota Geospatial Commons.To obtain the most current and authoritative data in its original form, users are referred back to the respective county. Links to each county's downloadable and/or web-viewable data, where known, are available in the accompanying spatial metadata dataset.Known limitations:Data provided by counties are often limited to a subset of fields and may not be the same fields across all counties. The fields provided by a given county may change by quarter.The USECLASS and XUSECLASS fields, while often consistent within a county, are not standardized between counties.The OWN_ADDR_# and TAX_ADDR_# fields are often populated in ways not consistent with the standard. In particular, an address number/street address may not be in Line 1, and city/state/zip cannot be relied on to be in Line 3. Even within a single county, the city/state/zip line may not be in a consistent field.Parcels with addresses on fractional streets (5-1/2th Ave) cause issues for our address parser when parsing is needed for aggregation and may be missing some or all of the address data. Certain other oddly named streets can also cause this behavior.A maximum record count has been set on the mapping service. This limits the number of features that can be returned in a single request. It is set to balance usability and response time.

This dataset represents the county boundaries, as recognized by the Minnesota Department of Transportation. There are 87 counties in Minnesota.

Check other metadata records in this package for more information on County Boundaries Information.


Link to ESRI Feature Service:

County Boundaries in Minnesota: County Boundaries

The Minnesota Geospatial Image Service provides versatile access to Minnesota air photos, hillshades, and scanned topographic maps using a Web Map Service (WMS). Using this service means you don't need to download and store these very large files on your own computer.

For a list of imagery data sets available through this service, see https://www.mngeo.state.mn.us/chouse/wms/wms_image_server_layers.html.

For technical specifications for using this service, see https://www.mngeo.state.mn.us/chouse/wms/wms_image_server_specs.html.

For information on how to use a Web Map Service (WMS), see https://www.mngeo.state.mn.us/chouse/wms/how_to_use_wms.html.

Polygon features representing lakes, rivers, and wetlands in Beltrami County, MN. This dataset is maintained independently by Beltrami County, but contains many of the same or similar attribute fields that exist in the MN DNR hydrography dataset available on the Minnesota Geospatial Commons.

Facilities (schools, colleges, etc.) used for the instruction of enrolled students. Representations of Schools are derived from local knowledge of facilities, and tabular data, such as enrollment and grades, comes from the Minnesota Geospatial Commons and Minnesota Department of Education.

This dataset was created by a joint collaborative project involving the technical and managerial GIS staff from the ten Metropolitan Counties of the Twin Cities in Minnesota (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne and Washington), the Metropolitan Emergency Services Board (MESB), MetroGIS and the Metropolitan Council. Core needs this dataset are intended to satisfy include:

- Vehicular routing;
- Address geocoding;
- Next Generation 911 call routing and location validation;
- Emergency services dispatching;
- Linear referencing uses;
- Cartographic representation of road features;

For specific questions regarding centerline alignments or attributes, please contact the county below
Anoka: https://www.anokacounty.us/315/GIS
Carver: gis@co.carver.mn.us
Chisago: gisservices@chisagocountymn.gov
Dakota: gis@co.dakota.mn.us
Hennepin: gis.info@hennepin.us
Isanti: Nate.Kirkwold@co.isanti.mn.us
Ramsey: RCGISMetaData@co.ramsey.mn.us
Sherburne: gis@co.sherburne.mn.us
Scott: gis@co.scott.mn.us
Washington: gis@co.washington.mn.us

Minnesota interpretation of the boundaries of the federal recognized tribes within Minnesota.

Check other metadata records in this package for more information on Tribal Government Information.


Link to ESRI Feature Service:

Tribal Government in Minnesota: Tribal Government

The MNDNR Watershed Suite is a collection of watershed delineations at various levels, flow network lines, and pour points. This is the newest version updated in 2023. Follow the links below to the individual metadata pages for each layer:

MNDNR Watersheds
MNDNR Level 01 - HUC 02: dnr_watersheds_dnr_level_01_huc_02.html
MNDNR Level 02 - HUC 04: dnr_watersheds_dnr_level_02_huc_04.html
MNDNR Level 04 - HUC 08 - Majors: dnr_watersheds_dnr_level_04_huc_08_majors.html
MNDNR Level 07 - Minors: dnr_watersheds_dnr_level_07_minors.html
MNDNR Level 08 - All Catchments: dnr_watersheds_dnr_level_08_all_catchments.html
MNDNR Level 09 - DNR AutoCatchments: dnr_watersheds_auto_catchments.html

Minnesota Hydrologic Units
Flow Network Lines: dnr_watersheds_catchment_flow_lines.html
Pour Points: dnr_watersheds_catchment_pour_points.html

This dataset is based on NOAA's Great Lakes Medium Resolution Digital Shoreline. The Lake Superior Shoreline was extracted and converted to a polygon feature class. Water and islands are differentiated. This layer is a medium-quality, general use digital vector dataset originally compiled from NOAA Nautical Charts, created by the Strategic Environmental Assessments Division of NOAA's Office of Ocean Resources, Conservation and Assessment. Nominal mapping scale is 1:70,000.

The Transit Routes layer contains all fixed routes serving the Twin Cities regional metropolitan area. One shape and one corresponding record exists for each individual transit route.

The line work for the dataset was derived from MRCC Street Centerlines and NCompass Centerlines for Sherburne and Wright County areas. A small number of line segments have been added to completely depict the network traveled by fixed-route transit vehicles.

This layer depicts open water features for lakes and rivers. The geography was initially created from the open water features depicted in the 2005 Generalized Land Use dataset developed by the Metropolitan Council. It is being updated over time with data from a variety of sources. It includes lakes larger than 3 acres and rivers wider than 200 feet. It may also include some smaller open water features as needed by the Metropolitan Council, including all lakes in the Council's lake monitoirng program. This layer does not depict the satutory Ordinary High Water Level of lakes.

NOTES:
- This dataset is derived from the Master Open Water Features dataset published by the Met Council.
- The extent of water features varies seasonally and annually with rainfall. The extent of water shown in this dataset may not reflect the current status of a particular water feature.
- When adding new polygons or modifying existing polygons, we will create boundaries based on recent imagery that we think depicts average water levels. We will NOT try to adjust the boundaries for seasonal variations in water levels.
- Wastewater stabilization ponds, which can be quite large, are not shown in this layer.

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 30 Meter Digital Elevation Model (DEM) is a copy of the USGS 1:24,000 scale Level 2 DEMs for the State.

There are three quadrangles known be be Level 1 DEM data: Town Line Lake (q1925), Grand Portage (q1261) and Grand Portage OE N (q1161).

This suite of data is a collection of layers that communicate the introduction risk, detection, bioControl, and response to Emerald Ash Borer (EAB) in Minnesota, including quarantined counties.

More information can be obtained at: http://www.mda.state.mn.us/eab

Follow the links below to the individual metadata pages for each layer:

Emerald Ash Borer Introduction Risk: eab_introduction_risk.html

Quarantine Boundaries: eab_quarantine_boundaries.html

Trees: eab_trees.html

Bio Control: eab_bio_control.html

This dataset is a subset of the statewide parcel dataset. The parcels in this dataset have been assigned a Government Ownership classification using the values "Federal", "State", "County Fee", "Tax Forfeit", or "Tribal" where it can be inferred from other fields in the parcel record. Only parcels from counties that have opted-in to sharing parcel data are included in this dataset.

For more information about the opt-in open parcel dataset, please refer to the opt-in open parcel compilation. https://gisdata.mn.gov/dataset/plan-parcels-open.

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.

This layer shows lakes meeting criteria for Lakes of Biological Significance (LBS) in Minnesota. Lakes were identified and classified by DNR subject matter experts on objective criteria for four community types (aquatic plants, fish, herptiles, birds).

Unique plant or animal presence was the primary measure of a lake's biological significance. Lakes were rated and grouped for each of the following communities: aquatic plants, fish, birds, and herptiles. Lakes were assigned one of three biological significance classes (outstanding, high, or moderate), which are defined in Section 5: Attributes (below). Many Minnesota lakes have not been sampled for plants and/or animals, so this list of lakes will be periodically revised as additional biological data become available.

The goal of this list was to identify lakes that exhibit the highest quality features within any of the four assessed biological communities (as opposed to identification of lakes that exhibit diversity across communities). Therefore, a lake needed to meet criteria for only one of the community types (aquatic plants, fish, birds, herptiles) to be identified as a Lake of Biological Significance. Occurrences of high-quality features within the community types determined the biological significance rank.

For a detailed description of criteria and analysis used, see: Lakes of Biological Significance 2025 (pdf, 169k)