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.

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.

This dataset is a compilation of tax parcel information for Dakota County, MNThe layer contains one record for each real estate/tax parcel polygon within the county. Condominiums are not included in the polygon layer. If condominiums are desired, use the tax parcel point layer in combination with this polygon layer.In many places a one-to-one relationship does not exist between these parcel polygons 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. Currently, only tax parcel ownership (and taxpayer information) is displayed for this dataset.
Tax Parcel - Polygons
Tax Parcel - Points
Tax Parcel - Lines

Partial and County wide ortho photography at various pixel resolutions from a variety of years from 1927 - 2022.
Horizontal Accuracy Report

Geospatial data about Dakota County, Minnesota Railroads. Export to CAD, GIS, PDF, CSV and access via API.

This dataset is a compilation of tax parcel information for Dakota County, MNThe layer contains one record for each real estate/tax parcel polygon within the county. Condominiums are not included in the polygon layer. If condominiums are desired, use the tax parcel point layer in combination with this polygon layer.In many places a one-to-one relationship does not exist between these parcel polygons 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. Currently, only tax parcel ownership (and taxpayer information) is displayed for this dataset.
Tax Parcel - Polygons
Tax Parcel - Points

Geospatial data about Dakota County, Minnesota Water Table. Export to CAD, GIS, PDF, CSV and access via API.

The types, locations, and density of information used to prepare the Dakota County atlas are shown on this map. The Database Map serves as a guide to the precision of the other maps in the atlas. It shows where data are sparse or lacking and interpretation and extrapolation were required to prepare the maps.

11/22/2024- County-wide road updates were completed in Golden Valley and Billings Counties. Intersecting routes throughout the state were cartographically realigned in preparation of MIRE intersections 6/27/2024 - The data was prepared for HPMS submittal which included updated 2023 AADT values and to keep certain segments consistent with HPMS segments, mainly sample sections and the NHS, values of "BOTH", "NHS" and "SAMPLE" were added to the field HPMS_ROUTE_ID to distinguish these segments from other segments. 3/19/2024 - Miscellaneous updates were done in Dunn County. County wide updates to Grand Forks and Golden Valley counties along with route realignments at intersections throughout the state.12/04/2023 - County wide updates to Walsh, Dunn and Grand Forks Counties and various updates to county/local roads throughout the state including street names in Westhope8/23/2023 - Function Class changes were updated in McLean and Mountrail Counties. Function Class updates also occurred in the cities of Fargo, Valley City, West Fargo and Williston. County-wide updates completed for: Towner, Cavalier, Pembina, Pierce, Benson, Ramsey. 2022 AADTs updated. A road was also removed in Bottineau County at the request off a landowner.5/19/22 - Dunn County contacted the NDDOT with data updates ,Rolette County was updated, and the 2021 AADT's were updated. 2/14/22 - Contacted by the Dunn County Road Dept., updates were made on newly paved road segments. 1/20/2022 - Since the August 2021 update, Morton, Stark, Hettinger, Bowman, Adams, Slope, Grant and Sioux Counties have been updated using 2020 imagery. Surface type has been checked and updated on all functionally classified roads statewide. Function Class changes have been made in the Bismarck/Mandan Metro, Grand Forks County and Burleigh County.6/15/21 - Since the 2019 update, trails and seldom used trails were updated statewide using 2018,and 2019 imagery. Steele, Traill and Griggs Counties have also been updated using 2020 imagery. Surface type has been checked and updated on all functionally classified roads statewide New roads added includes roads in the Fargo, West Fargo, Grand Forks, Jamestown, Bismarck, Mandan, Minot, Dickinson, Watford City and Williston. Ownership on Federal jurisdiction roads were also updated based on an dataset received for FHWA in conjunction with the HPMS submittal. HPMS (Highway Performance Monitoring System) fields were also added in an effort to integrate the roads county data into HPMS and MIRE (Model Inventory Roadway Elements). 9/14/20 - Added the following fields - AADT, AADT_YR, HPMS_MAINTENANCE_OPERATIONS, HPMS_THROUGH_LANES, FUNCTIONAL_CLASS (replaces FUNCTION_CLASS)8/13/19 - The following counties were updated by using a variety of aerial photography: Eddy, Foster and Barnes. Seldom used trails have been added to Barnes, Benson, Billings, Bottineau, and Bowman Counties. Mercer County had (2) 61STAvenues, this has been corrected.12/26/18 - The following counties have had their roads updated by a variety of aerial photography, McHenry, Wells, Kidder, Cass (with aid of Cass county website) and McKenzie (with aid of McKenzie County GIS Coordinator)8/14/18 - Counties updated using 2017 NAIP Imagery are Ward, Mountrail, Burke and Renville counties. Seldom used trails are also being digitized into the dataset. They are being added as counties are being checked, so it will take some time for all seldom used trails to be added statewide. Also since the last update, all local roads that are in the corporate boundaries have been broken at the boundaries so it is easier to query to determine which roads go with each community.5/21/18 - removed CITY_INT_ID column - no longer used because of CITY_FIPS and HPMS_URBAN_CODE attributes. Removed SERVICE_LEVEL field, never used/maintained.4/19/18 - added HPMS_OWNERSHIP and HPMS_FACILITY fields for HPMS submittal1/24/18 - added CITY_FIPS and HPMS_URBAN_CODE attributes/domains. These columns will replace CITY_INT_ID and SOURCE_ID columns (eventually).11/15/17 - Williams, Divide and Bottineau counties have been updated. Great effort has been taken to update attributes and QC null fields. Functional Classified roads in Bismarck and Mandan have been updated as have local roads in Bismarck, Mandan, Williston, Fargo – West Fargo and Minot. 1/25/17 - started to maintain roads in Esri's Road and Highways. The shapes now contain measures in miles along with the associated linear referencing/roads and highways fields. Removed INSET_ASSOC field and added COUNTY_FIPS field.Updates include the counties of Emmons, Logan, McIntosh, Lamoure, Dickey, Ransom, Sargent and Richland. These counties were updated using a combination of the available NAIP aerials, the DES aerials, and by car within the insets. In addition to these updates, the whole county dataset was edited using Data Reviewer checks. The checks ran included unnecessary nodes, non-linear segments, invalid geometry, Duplicate vertices with a tolerance of .5 meters, polyline closes of self, checked for cutbacks using a 15 degree minimum angle, checked for polyline length check using a distance less than 10 meters, checked for multipart lines, inspected dangles with a tolerance of 10 meters, and checked for orphans. All checks were inspected and fixed where appropriate.7/16/14 - updates include: Traill, Barnes, Stutsman, Kidder, Bowman, Slope, Stark, Hettinger, Adams, Grant, Sioux and Morton. These datasets were updated using a combination of the available NAIP aerials, the DES aerials, and by car within the insets.10/22/12 - city streets were updated in Bismarck, Dickinson, Minot and Williston. GIS data from the city of Bismarck was used to update Bismarck, GIS data and 2012 aerial photography was used to update the city of Williston, Minot’s city map and the 2010 aerial photography from Ward County was used to update Minot, and 2011 aerial photography and Dickinson’s "working" city map was used to update Dickinson. The counties updated were Williams, Burke, Bottineau, Mountrail, Ward, Wells, Eddy, Foster, Griggs, Steele, and Cass. At the time of this updated, approximately 50% of Stutsman and 50% of Traill Counties are updated. Williams, Bottineau, Ward, and Mountrail roads were inspected from the air and the 2009 NAIP photos were also used to assist the updates. The roads in Williams County were also recoded to match Williams County naming conventions. Williams County CADD map which is on the Williams county web site was used in updating the road names. In Ward County, the 2010 image from Ward County was used to assist in updating Ward County. The 2010 NAIP photos were used to update Wells, Eddy, Foster, Griggs and Steele Counties. Cass was updated with the assistance of the Cass County GIS layer and the 2011 Cass county imagery. 10/3/2011 - County roads were edited in the cities of Fargo, West Fargo, Horace, Minot, Bismarck, Devils Lake, Grafton, Williston, Valley City, and Dickinson. Also, a part of Ward and Mchenry Counties was edited and the county of Renville has been updated. The business routes through Bismarck and Jamestown were also edited. 5/9/2011 - Updated streets in Bismarck, Mandan, Jamestown, Dickinson, West Fargo ( not quite finished yet), and Valley City. Also, corrected the north - south roads in Township 144N Ranges 49 - 53 E, (in Traill County) 10/5/10 - The original Roads_County data was maintained in two separate ArcInfo coverages and then combined each year and exported to the NDHUB infrastructure. These two coverages have now been combined into one SDE feature class and is being edited within the SDE environment. The following changes have been made to feature class. Deleted all the A1 and A2 Fields so a person would have to hunt back and forth to find a road name. Road names consist of the following fields: RTE_ID, STR_TYP, SUF_DIR, & LAN_DIR. The CMC route numbers were moved from the A1_ prefixed fields to the CMC field to better track the CMC route. Created a County Highway field so we can enter the county road number. It consists of the counties name and number. This is still a work in progress. Created FS_RD_Number and FS_RD_Name fields to better track Forest Service roads. Created Bia-RD_Number and BIA_RD_Name fields to better track Bureau of Indian Affairs roads. The following field changes are used for NDDOT specific processes: Created a service level field which is something that may be used in the future. Currently it contains how Walsh County prioritizes their roads. Created a Through and Connecting Route field so we can so select routes through the towns and cities. This was created exclusively for the county base maps. Created an Inset Associated field. This was created so the information in the rd_misc would come into the county routes. In the future, it is planned to be deleted. 6/18/09 - Updated county routes from aerial observation and photo interpretation using 2003, 2005, 2006 NAIP photos and 2008 photography from Designs camera. Counties updated were Golden Valley, Billings, McKenzie, Dunn, Mercer, Oliver, McLean, Sheridan and Burleigh. City streets were rectified in these counties using the 2003 NAIP photos. Observations were performed by Steven Nelson. 4/17/08 - Updated road surface types in NE. Rolette, Pierce, Benson, Towner, Ramsey, Cavalier, Pembina, Walsh, Grand Forks and Nelson from the 2006 aerial observations by Dewaine Olson 2/13/07 - Updated via 2004 NAIP photos: Barnes, Cass, Eddy, Foster, Griggs, Kidder, Steele, Stutsman, Traill, Wells. Combined Misc Roads and County Roads. Blank fields mean unknown attribute. Use P_STREET_NAME for dynamic labeling. We are also in the process of removing all proposed roads. 12/28/05 - Counties updated: Emmons, Logan, Mcintosh, Lamoure, Dickey, Ransom, Sargent, Richland, Divide, Williams, Burke, Mountrail, Ward, Renville, Bottineau, and Mchenry This data came from the NDDOT's Mapping Section. The original data was digitized from hand scribed maps and registered

Link to the GIS Open Data site for Minnehaha County, South Dakota.

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.

County Geologic Atlases (CGAs) are prepared jointly by the Minnesota Geological Survey (MGS) and the Minnesota Department of Natural Resources (DNR). Part A of each county atlas is completed by the MGS and provides a detailed account of geologic materials in the county. Part B of each county atlas is completed by the Minnesota DNR and shows groundwater and hydrology information. The CGA provides information essential to sustainable management of groundwater resources for applications such as monitoring, water allocation, permitting, remediation, and well construction. The maps and GIS data define aquifer properties and boundaries, as well as the connection of aquifers to the land surface and to the surface-water resources. It also provides a broad range of information on county geology, mineral resources (including construction materials), and natural history.

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

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

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 2008 dataset unless otherwise noted):

Anoka = 130,675 polygons, 130,675 points
Carver = 37,715 polygons, 37,715 points
Dakota = 135,771 polygons, 149,925 points
Hennepin = 359,042 polygons, 425,562 points
Ramsey = 149,093 polygons, 166,939 points
Scott = 55,242 polygons, 55,242 points
Washington = 98,812 polygons, 10,687points

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 2007 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

Geospatial data about Dakota County, Minnesota Ditches (County). Export to CAD, GIS, PDF, CSV and access via API.

This map includes three-dimensional models that show the distribution of the Quaternary sand and gravel deposits that are potential aquifers in Dakota County, Minnesota. Geologists interpreted the three-dimensional models and related sand and gravel deposits to the glacial events that formed them. Although the models and interpretations are based on the best available data, they are unavoidably incomplete due to a lack of data in some areas.

Trends with more people driving alone to work are filled in red and dark red.

Fugro Horizons Inc. acquired highly accurate Light Detection and Ranging (lidar) elevation data for the Twin Cities metropolitan region in east-central Minnesota in Spring and Fall 2011, with some reflights in Spring 2012. The data cover Anoka, Benton, Carver, Dakota, Goodhue, Hennepin, Isanti, Kanabec, Meeker, Mille Lacs, Morrison, Ramsey, Scott, Sherburne and Washington counties.

Most of the data was collected at 1.5 points/square meter. Smaller areas were collected with 2 points/square meter and with 8 points/square meter:
1. 1.5 points/square meter covers Morrison, Mille Lacs, Benton, Isanti, Sherburne, Anoka, Meeker, Hennepin, Washington, Carver, Scott, and Goodhue counties.
2. 2 points/square meter covers the Dakota Block (southern 2/3 of Dakota County)
3. 8 points/square meter covers portions of Minneapolis/St. Paul and the City of Maple Grove
See map of block boundaries: https://www.mngeo.state.mn.us/chouse/elevation/metro_data_delivery_dates.pdf

Data are in the UTM Zone 15 coordinate system, NAD83 (HARN), NAVD88 Geoid09, meters. The tiling scheme is 16th USGS 1:24,000 quadrangle tiles.

The vendor delivered the data to the Minnesota Department of Natural Resources (DNR) in several formats:

1. One-meter digital elevation model
2. Edge-of-water breaklines
3. Classified LAS formatted point cloud data

DNR staff quality-checked the data and created three additional products: two-foot contours, building outlines and hillshades.

This metadata record was created at the Minnesota Geospatial Information Office using information supplied by the vendor and by DNR.

The Bedrock Topography map represents the elevation (in feet above mean sea level) of the top of bedrock and the bottom of Quaternary sediments mapped in Dakota County, Minnesota. The Depth to Bedrock map portrays the thickness (in feet) of Quaternary sediments overlying the bedrock surface. The depth to bedrock is equal to the depth from the land surface to the underlying bedrock surface.