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, Lake, Marshall, McLeod, Meeker, Mille Lacs, Mower, Norman, Olmsted, Otter Tail, Polk, Pope, Ramsey, Renville, Rice, Scott, Sherburne, Stearns, Steele, St. Louis, Traverse, Waseca, Washington, Wilkin, 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

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.

The Digital Bedrock Geologic-GIS Map of Voyageurs National Park and Vicinity, Minnesota is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (voya_bedrock_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (voya_bedrock_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (voya_bedrock_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (voya_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (voya_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (voya_bedrock_geology_metadata_faq.pdf). Please read the voya_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Minnesota Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (voya_bedrock_geology_metadata.txt or voya_bedrock_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

This file geodatabase contains datasets that represent place locations.

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

Place Address Points: loc_address.html

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 resource is a member of a series. 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 tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

A number of counties in Minnesota have created an open data web site, but are not yet publishers on the Commons. In order to assist users in finding data from these organizations, MnGeo has created application resources with links to those sites, along with tags about the kind of information that can be found. While MnGeo is sponsoring the publication of these links, users should understand that the content of the individual websites is published by those counties. This resource provides such a link to the open data website for Carver County.

The vector data is updated utilizing positions calculated from plats using coordinate geometry programs. Plated, Public road centerlines are captured within this database. Private roads may not be shown.

The centerlines usually represent the center of the physical roadway pavement. The center of physical roadway pavement may or may not represent the center of the road right of way. Road right of ways may taper or change width.

This file has been further modified using several sources including survey field data and digitizing off aerial photos. Attributes have been included to allow geo-coding and the support of Washington County Sheriff's Office Communication Center. Regional Data is available through the MN Geocommons. https://gisdata.mn.gov/dataset/us-mn-state-metrogis-trans-road-centerlines-gac

This resource is a member of a series. 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 All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

This map portrays our current geologic understanding of the temporal and geographic distribution of units within major Precambrian terranes and of the Phanerozoic strata. The state wide data is mapped at a scale of 1:500,000 and the county bedrock datasets (Becker, Brown, Meeker, Isanti, Cass) are mapped at a 1:100,000 scale. A Story Map displaying this data can be found at Minnesota's Bedrock Geology story map.The western part of the mapped Precambrian terrane in the state wide dataset is inferred largely from geophysical maps, anchored locally by drilling. In many places, contacts are drawn between units of the same or similar apparent rock type (and same unit label); these are recognized as geometrically distinct, though geophysically or lithologically similar. Digital files for the state wide bedrock (http://hdl.handle.net/11299/101466) corresponding to this map allow removal of Cretaceous, Paleozoic, and some parts of Mesoproterozoic strata to reveal an interpretation of the underlying Precambrian bedrock.

For additional state wide data see: (http://hdl.handle.net/11299/98043) which contains files associated with Bedrock Topography, Depth to Bedrock, and locations of Outcrop and Geochronologic analyses. Individual county bedrock can be found and downloaded at the University of Minnesota's Digital Conservancy.

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. Primary roads are generally divided, limited-access highways within the interstate highway system or under State management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. The MAF/TIGER Feature Classification Code (MTFCC) is S1100 for primary roads. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, and/or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not bedivided, and usually have at-grade intersections with many other roads and driveways. They usually have both a local name and a route number. The MAF/TIGER Feature Classification Code (MTFCC) is S1200 for secondary roads.

The "Map Image Layer - Minnesota Administrative and Watershed Boundaries" is a Map Image Layer of the Minnesota Administrative and 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 Digital Geologic-GIS Map of Saint Croix National Riverway and Vicinity, Minnesota and Wisconsin is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (sacn_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (sacn_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (sacn_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (sacn_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (sacn_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (sacn_geology_metadata_faq.pdf). Please read the sacn_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Minnesota Geological Survey, Wisconsin Geological and Natural History Survey and National Park Service. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (sacn_geology_metadata.txt or sacn_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:250,000 and United States National Map Accuracy Standards features are within (horizontally) 127 meters or 416.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Scott County Parcels represent property tax boundaries and were created, and are maintained, by the Survey department. The tax boundaries are joined to the Assessor's CAMA data using the PID field providing field attributes for each property. For a list of field descriptions, click here.

Climate change has been shown to influence lake temperatures globally. To better understand the diversity of lake responses to climate change and give managers tools to manage individual lakes, we modelled daily water temperature profiles for 10,774 lakes in Michigan, Minnesota and Wisconsin for contemporary (1979-2015) and future (2020-2040 and 2080-2100) time periods with climate models based on the Representative Concentration Pathway 8.5, the worst-case emission scenario. From simulated temperatures, we derived commonly used, ecologically relevant annual metrics of thermal conditions for each lake. We included all available supporting metadata including satellite and in-situ observations of water clarity, maximum observed lake depth, land-cover based estimates of surrounding canopy height and observed water temperature profiles (used here for validation). This unique dataset offers landscape-level insight into the future impact of climate change on lakes. This data set contains the following parameters: site_id, Prmnn_I, GNIS_ID, GNIS_Nm, ReachCd, FType, FCode, which are defined below.

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 dataset is a compilation of tax parcel polygon and point layers from the seven Twin Cities, Minnesota metropolitan area counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington. The seven counties were assembled into a common coordinate system. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties will 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. The primary example of this is the condominium. 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 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.

Polygon and point counts for each county are as follows (based on the January, 2005 dataset):

Anoka = 124,042 polygons, 124,042 points
Carver = 32,910 polygons, 32,910 points
Dakota = 130,989 polygons, 141,444 points
Hennepin = 353,759 polygons, 399,184 points
Ramsey = 148,266 polygons, 163,376 points
Scott = 49,958 polygons, 49,958 points
Washington = 93,794 polygons, 96,570 points

This is a MetroGIS Regionally Endorsed dataset.

Each of the seven Metro Area counties has entered into a multiparty agreement with the Metropolitan Council to assemble and distribute the parcel data for each county as a regional (seven county) parcel dataset.

A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2005 document.

Additional information may be available in the individual metadata for 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 listed in the individual county metadata.

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: http://www.hennepin.us/gisopendata

Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

A feature service is also available here: https://gis.ducks.org/datasets/duinc::minnesota-restorable-wetlandsHISTORY: In October 2000, a Restorable Wetlands Working Group formed to begin mapping all of the restorable wetlands in the glaciated tallgrass Prairie Pothole Region of Minnesota and Iowa. Today, fewer than 10% of the original wetlands - once of unparalleled importance to continental waterbird populations - are left in existence. Fortunately, wetlands once drained for agriculture may be restored to many of their historic functions. Restoration of multiple wetland functions is of utmost effectiveness when focused at priority restoration landscapes, therefore data on the historic distribution of wetlands is an integral part of developing strategic regional habitat restoration plans.Opportunistic wetland restorations often fail to attain out expectations for wetland function. Nevertheless, between $70 - $100,000,000 are spent annually in Minnesota for wetland restoration. A strategic plan for wetland restoration can make these expenditures more effective; however, a strategic wetland restoration plan requires a priori information on the distribution and extent of restorable wetlands. The collective goal of the Restorable Wetlands Working Group is the eventual development of a set of multi-agency decision support tools that collectively comprise a comprehensive environmental management plan for wetlands - all based on the same base data layers and developed in joint consultation. An effort is underway to delineate restorable wetlands in all intensively farmed areas of MN and IA.A pilot project determined the best technique to map drained wetlands in agricultural landscapes was photointerpretation. This pilot project evaluated the accuracy of three potential delineation techniques: digital hydric soils databases, digital elevation models, and manual stereoscopic photointerpretation on high-altitude color infrared aerial photographs. The project covered nearly 4,000 square miles of different land forms and wetland characteristics. After mapping was completed, some 1,500 drained wetlands were observed in the field to assess the accuracy of each technique. Only photointerpretation provided reliable results.One area that fell into the pilot study was the Okabena quadrangle in east-central Jackson County in Minnesota. Okabena vividly illustrates the potential of humans to alter the natural landscape. While Okabena historically encompassed more than 8,940 acres of depressional wetland - 27% of the total area of Okabena - after nearly 100 years of agricultural drainage only 1,280 acres of those original wetlands remain, representing an 86% reduction. When empirical models used to estimate duck pairs on individual wetlands are applied to the change from historic to current wetland habitat within Okabena, they estimate a 92% reduction in the habitat potential for common dabbling duck species.The Okabena quadrangle's wetland density once exceeded that of most of the remaining U.S. Prairie Pothole Region. Without strong incentives for wetland conservation and effective methods to delineate high-priority landscapes for restoration, the Okabena quadrangle foretells one possible future for much of the mixed-grass Prairie Pothole Region further west.The Final Status map was completed in 2012.Contact Information:Rex JohnsonUnited States Fish and Wildlife Service21932 State Highway 210Fergus Falls, MN 56537(218) 736-0606rex_johnson@fws.govPhotointerpretationNational Aerial Photography Program (NAPP) (1:40,000 scale) color infrared (CIR) photographs acquired in April and May, 1991 and 1992, were viewed in stereo pairs at 5X magnification using a Cartographic Engineering stereoscope. A Mylar overlay was mounted on one photo of each stereo pair and a rectangular work area was delineated on the overlay comprising one-quarter of a USGS 7.5 min topographic quadrangle. A minimum of 4 fiduciary marks were placed on the overlay to enable geographic rectification of digital data covering the work area. One fiduciary mark was placed at the corner of the US Geological Survey (USGS) 7.5 min quadrangle and others at conspicuous road intersections near the other 3 corners of the work area. Drained depressional wetlands were delineated on the Mylar overlay within the work area using a 6X0 (.13 mm diameter) rapidograph pen and indelible ink. Collateral data was consulted during the delineation process. These data consisted of published county soil surveys and descriptions of hydric soils, USDA Farm Service Agency compliance slides (aerial 35 mm slides) acquired in 1993 (immediately after a period of intense precipitation), USGS 7.5 min topographic maps, and National Wetlands Inventory (NWI) maps. Black and white NAPP photographs (1:40,000 scale) acquired primarily in August and September, 1996, were reviewed and rejected as collateral data because they were acquired under dry conditions.Other specific photointerpretation protocols were:1. All drained depressional wetlands, regardless of size, were delineated.2. NWI-delineated wetlands with a Ad@ (partially drained) modifier in the classification code were not delineated unless the original delineation failed to encompass the complete historic wetland area.3. NWI-delineated wetlands that did not contain a Ad@ modifier in the classification code were delineated if the original delineation did not include the entire historic wetland area.4. Wetlands identified on NWI maps which did not exhibit wetland characteristics (i.e. hydrology, hydrophytes, etc) on new (1992) CIR photography were delineated even if no evidence of drainage was apparent.5. Wetlands not delineated on NWI maps, and in cropland, were delineated.6. Wetlands not delineated on NWI maps, and in grassland, were not delineated unless evidence of drainage was observed on the aerial photo.7. Wetlands not delineated on NWI maps, and in trees, were not delineated.Tolerances:Scanned line data were converted to a polygon using a 6 m fuzzy tolerance. Open polygons were manually closed and cleaned with a 1.2 m fuzzy tolerance which was used for all subsequent data processing.Datafile Description and Attribute Definitions[County_Name]_nwx - National Wetlands Inventory delineations (see https://www.fws.gov/program/national-wetlands-inventory/wetlands-mapper for NWI delineation standards). Note: Wetland classifications in these data often differ slightly from the original NWI classification. NWI wetland classifications were simplified for these data by removing mixed classes and multiple special modifiers, and by standardizing letter case. In each case of mixed classes and multiple special modifiers, the first class or special modifier was retained.AttributesRestorable - 0 = Islands and the Universal Polygon100 = Restorable depressional wetland delineated using protocols described aboveCounty Name – The name of the county in which the center of the polygon is located.State Name – The name of the state.FIPS – The FIPS code.

Police Department locations in Hennepin County. Police Department locations were captured for Emergency Mangement.
* Includes main police station but does not include substations. * Phone numbers are non-emergency contact numbers. * WebUrl is for main city website.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/Police%20Stations.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data.

© This dataset is maintained by the Hennepin County Emergency Management Office. This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data.

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 All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.