Facebook
TwitterWashington 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.
Facebook
TwitterIn 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.
Facebook
TwitterExterior 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
Facebook
TwitterAddress points maintained by Washington County. Current data set updated last in August 2025.Driveways are maintained as time allows.The building footprints are from 2017 aerials.
Facebook
TwitterThis 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 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. The 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.
Polygon and point counts for each county are as follows (based on the January 2012 dataset unless otherwise noted):
polygons / points
Anoka - 129385 / 129385
Carver - 38699 / 38699
Dakota - 136792 / 150666
Hennepin - 424702 / 424702
Ramsey - 148978 / 166846
Scott - 55227 / 55227
Washington - 106841 / 106841
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 2011 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
Facebook
TwitterTo launch this map, visit http://maps.co.washington.mn.us/CountyFacilities/ .This map is designed to help identify the location of various Washington County facilities. Descriptions with details of the facility (location, contact information, photographs, maps, handicap accessibility, rental availability, etc.) display within each county facility’s listing.
Facebook
TwitterBuilding footprints interpolated from 2016 and 2017 aerial imagery.
Facebook
TwitterMeasurements were taken from roadway construction plan typical sections and confirmed using the measuring tool in ArcGIS. A single line segment was drawn down the county road centerline to represent areas where shoulders are 3 feet or wider. There are two fields within the attribute information which represent the left and right shoulder widths (in feet). The left and right shoulder widths were determined by working from west to east and from south to north. Any areas where the shoulder was less than 3 feet on both side of the road were not included within this mapping file.
Facebook
TwitterThis 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 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. The 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.
Polygon and point counts for each county are as follows (Updated annually, current as of 1/08/2016):
polygons / points
Anoka - 131121 / 131121
Carver - 40510 / 40509
Dakota - 140770 / 154109
Hennepin - 429241 / 429241
Ramsey - 154512 / 166225
Scott - 56219 / 56219
Washington - 106045 / 106045
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 2015 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
Facebook
TwitterThis 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, 2007 dataset):
Anoka = 129,392 polygons, 129,392 points
Carver = 37,021 polygons, 37,021 points
Dakota = 135,586 polygons, 148,952 points
Hennepin = 358,064 polygons, 419,736 points
Ramsey = 148,967 polygons, 166,280 points
Scott = 54,741 polygons, 54,741 points
Washington = 97,922 polygons, 102,309 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 2006 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
Facebook
TwitterThis 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
Facebook
Twitter
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.
Facebook
TwitterThe 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
Facebook
TwitterCirculator routes and local transportation options within Washington County, MN.Twin Cities Metro Transit route data provided by Metropolitan Council.This map is used by the Transportation Finder application
Facebook
TwitterThis section celebrates the development of commerce in Washington County. There were many lumber mills built and sustained in the 1800s. To serve the growing population, many of them working men, clothing, mattress, home goods, and shoe factories emerged and hotels opened for temporary housing. Entertainment also sprung up to engage the community—some of this amusement was beneficial, such as the leisure facility of Wildwood Park, others were not as constructive. Supporting the Victorian ideal of progressive social uplift, we see the beginning of a social system developing with one of the first hospitals in Stillwater. Due to lack of space, this section is remiss in not including some commercial gems such as Stillwater’s Commander Mill, the Freight House, the now lost Tamarack House, and the Langdon Butter and Cheese Factory of Cottage Grove, one of the first creameries in Minnesota.
Facebook
TwitterThis 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 systems 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. (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. Summary attribute information is in the Attributes Overview. Detailed information about the attributes can be found in the MetroGIS Regional Parcels 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.
Polygon and point counts for each county are as follows (Updated annually, current as of 12/31/2016):
polygons / points
Anoka - 131708 / 131708
Carver - 41204 / 41203
Dakota - 142121 / 154945
Hennepin - 430449 / 430449
Ramsey - 158207 / 166343
Scott - 56533 / 56533
Washington - 106849 / 106849
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 = 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
Facebook
TwitterLooking back at our collective histories we see a number of changes in our natural and built environments. Some structures built 170 years ago are still standing in Washington County while others are not. This section reflects just a few of the lost, but not forgotten, structures. We have included sites and buildings that played an important part of our communities’ history.
Facebook
TwitterA County Geologic Atlas (CGA) project is a study of a county's geology, and its mineral and ground-water resources. The information collected during the project is used to develop maps, data-base files, and reports. This same information is also produced as digital files. The map information is formatted as geographic information system (GIS) files with associated data bases. The maps and reports are also reproduced as portable document files (PDFs) that can be opened on virtually any computer using the free Acrobat Reader from Adobe.com. All of the digital files for the CGA's can be downloaded from the University of Minnesota Digital Conservancy. The majority of the files can also be viewed and queried through the use of this Story Map.Atlas information is commonly used in planning and environmental protection programs, as an educational resource, and by industries involved in water and mineral resources. It represents a comprehensive, detailed compilation of geologic data and interpretations within a county. The distribution and character of geologic materials determine how and where water enters the earth, and where it is stored in aquifers that can supply our needs. Geologic maps are a key element in delineating those flow paths and in relating land use to water quality. The atlas also provides a framework and terminology to support more detailed, site-specific studies. The records of water wells drilled in the area are an important source of data for constructing the maps and for understanding the distribution and use of ground water in the county. A data base of the information from those wells is one of the atlas products, and it can be queried with the GIS files to yield valuable insights for managing the ground-water resource.The atlas is also useful to non-professionals who simply wish to learn more about the geology of the county. It is a one-stop, comprehensive collection of information in a variety of forms and styles that should be useful to anyone with an interest in earth science or the county.The geologic data and maps are produced and distributed by the Minnesota Geological Survey (MGS) as Part A of an Atlas. The Minnesota Department of Natural Resources follows with an investigation of the quantity, quality, and pollution sensitivity of ground water. Their products are distributed as Part B of the atlas, at a later date. If necessary, a report with additional information that was not possible to include on the limited space of the printed maps is produced by MGS as Part C of, or included as a supplement to, an atlas. The Atlas CD or DVD, which is available online at the Digital Conservancy, includes all the atlas products developed by the Minnesota Geological Survey.
Facebook
TwitterFugro 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.
Facebook
TwitterMap of soil survey 2006. Source NRCS
Facebook
TwitterWashington 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.