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 file geodatabase contains parcel data including plat boundaries, tax parcels, easements and road right of ways. Attributed Parcel Point and Polygon data represent property descriptions (legal descriptions) and land ownership in Ramsey County joined to tax parcels.

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

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

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.

This dataset contains polygons representing individual taxed parcels or individual tax-exempt parcels tracked for taxing purposes. It also contains polygons representing the locations of multiple tax properties. In the case of multiple tax properties, several parcel polygons may be stacked on top of one another. These are multiple tax parcels that cannot be delineated on a two-dimensional map, including both taxed and tax-exempt parcels. The parcels are represented with identical geometries but have different parcel IDs and associated tax attributes. The PID field contains the property ID number for each parcel.Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/County%20Tax%20Parcels.pdf

© This dataset is compiled monthly by the Hennepin County GIS Office from parcel geometry that is created and maintained by the Hennepin County Resident and Real Estate Services Survey Division and tax attributes extracted from the Hennepin County Real Estate Services property tax information system.

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.

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.

About this itemThanks for your interest in our public access GIS hub site. This site brings many of our most popular mapping resources together in one place for easy access. Users can quickly find the content they need and discover other areas of interest by exploring a series of Map Galleries. For those seeking GIS data, an open data portal with a growing collection of local datasets is just a click or tap away. Author/ContributorKyle ObergOrganizationCook CountyOrg Websiteco.cook.mn.us

The published representation of real property areas, combined with assessing and tax information from CAMA and Tax systems, and organized for consumption in desktop and web applications.

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

This dataset 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.

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://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.

This is an annual version of the MetroGIS Regional Parcel Dataset that can be used with other annual versions to do change analysis and time series investigations. This dataset is intended to contain all updates to each county's parcel data through the end of 2004. It was originally published as the 'January 1, 2005' version of the dataset. See the Currentness Reference below and the Entity and Attribute information in Section 5 for more information about the dates for specific aspects of the dataset.

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

Improving the quality of water discharged from agricultural watersheds requires comprehensive and adaptive approaches for planning and implementing conservation practices. These measures will need to consider landscape hydrology, distributions of soil types, land cover, and crop distributions in an integrated manner. The two most consistent challenges to these efforts will be consistency and reliability of data, and the capacity to translate conservation planning from watershed to farm and field scales. The translation of scale is required because, while conservation practices can be planned based on a watershed scale framework, they must be implemented by landowners in specific fields and riparian sites that are under private ownership. To support these goals, it has been necessary to develop planning approaches, high-resolution spatial datasets, and conservation practice assessment tools that will allow the agricultural and conservation communities to characterize and mitigate these challenges. The field boundary dataset represents a spatial framework for assembling and maintaining geospatial data to support conservation planning at the scale where conservation practices are implemented. This field boundaries dataset has been assembled to support field-scale agricultural conservation planning using the USDA/ARS Agricultural Conservation Planning Framework (ACPF). The original data used to create this database are the pre-2008 Farm Bill FSA common land unit (CLU) datasets. A portion of metadata found herein pertains to the USDA FSA CLU. The remaining information has been developed to reflect the repurposing of the data in its aggregated form. It is important to note that all USDA programmatic and ownership information that was associated with the original data have been removed. Beyond that, these data has been extensively edited to reflect crop-specific land use consistent with 2015 land cover as derived from 2015 NASS Crop Data Layer datasets and 2015 aerial photography, and no longer reflects discrete ownership patterns. Resources in this dataset:Resource Title: Agricultural land use by field: Minnesota 2010-2019. File Name: MN_ACPFfields2019.zipResource Description: This field boundaries dataset has been assembled to support field-scale agricultural conservation planning using the USDA/ARS Agricultural Conservation Planning Framework (ACPF).Resource Software Recommended: ArcGIS,url: https://www.esri.com/en-us/home Resource Title: Minnesota Field Boundaries 2019. File Name: MN_ACPF_fieldBoundaries_2019.pdfResource Description: Minnesota Field Boundaries 2019Resource Title: Minnesota ACPF Crop History 2010-2019. File Name: MN_ACPFfields_CropHistory2010_2019.pdfResource Description: Minnesota ACPF Crop History 2010-2019Resource Title: Minnesota ACPF Land Use 2014-2019. File Name: MN_ACPFfields_LandUse2014_2019.pdfResource Description: Minnesota ACPF Land Use 2014-2019

Scott County Parcel Points represent the center of 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.

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

The approximate representation of real property areas in Lake County, Minnesota.

This TNC Lands spatial dataset represents the lands and waters in which The Nature Conservancy (TNC) currently has, or historically had, an interest, legal or otherwise in Minnesota, North Dakota, & South Dakota. The system of record for TNC Lands is the Legal Records Management (LRM) system, which is TNC’s database for all TNC land transactions.TNC properties should not be considered open to the public unless specifically designated as being so. TNC may change the access status at any time at its sole discretion. It's recommended to visit preserve-specific websites or contact the organization operating the preserve before any planned visit for the latest conditions, notices, and closures. TNC prohibits redistribution or display of the data in maps or online in any way that misleadingly implies such lands are universally open to the public.The types of current land interests represented in the TNC Lands data include: Fields and Attributes included in the public dataset:Field NameField DefinitionAttributesAttribute Definitions Public NameThe name of the tract that The Nature Conservancy (TNC) Business Unit (BU) uses for public audiences.Public name of tract if applicableN/A TNC Primary InterestThe primary interest held by The Nature Conservancy (TNC) on the tractFee OwnershipProperties where TNC currently holds fee-title or exclusive rights and control over real estate. Fee Ownership can include TNC Nature Preserves, managed areas, and properties that are held for future transfer. Conservation EasementProperties on which TNC holds a conservation easement, which is a legally binding agreement restricting the use of real property for conservation purposes (e.g., no development). The easement may additionally provide the holder (TNC) with affirmative rights, such as the rights to monitor species or to manage the land. It may run forever or for an expressed term of years. Deed RestrictionProperties where TNC holds a deed restriction, which is a provision placed in a deed restricting or limiting the use of the property in some manner (e.g., if a property goes up for sale, TNC gets the first option). TransferProperties where TNC historically had a legal interest (fee or easement), then subsequently transferred the interest to a conservation partner. AssistProperties where TNC assisted another agency/entity in protecting. Management Lease or AgreementAn agreement between two parties whereby one party allows the other to use their property for a certain period of time in exchange for a periodic fee. Grazing Lease or PermitA grazing lease or permit held by The Nature Conservancy Right of WayAn access easement or agreement held by The Nature Conservancy. OtherAnother real estate interest or legal agreement held by The Nature Conservancy Fee OwnerThe name of the organization serving as fee owner of the tract, or "Private Land Owner" if the owner is a private party. If The Nature Conservancy (TNC) primary interest is a "Transfer" or "Assist", then this is the fee owner at the time of the transaction.Fee Owner NameN/A Fee Org TypeThe type of organization(s) that hold(s) fee ownership. Chosen from a list of accepted values.Organization Types for Fee OwnershipFED:Federal, TRIB:American Indian Lands, STAT:State,DIST:Regional Agency Special District, LOC:Local Government, NGO:Non-Governmental Organization, PVT:Private, JNT:Joint, UNK:Unknown, TERR:Territorial, DESG:Designation Other Interest HolderThe name of the organization(s) that hold(s) a different interest in the tract, besides fee ownership or TNC Primary Interest. This may include TNC if the Other Interest is held or co-held by TNC. Multiple interest holders should be separated by a semicolon (;).Other Interest Holder NameN/A Other Interest Org TypeThe type of organization(s) that hold(s) a different interest in the tract, besides fee ownership. This may include TNC if the Other Interest is held or co-held by TNC. Chosen from a list of accepted values.Organization Types for interest holders:FED:Federal, TRIB:American Indian Lands, STAT:State,DIST:Regional Agency Special District, LOC:Local Government, NGO:Non-Governmental Organization, PVT:Private, JNT:Joint, UNK:Unknown, TERR:Territorial, DESG:Designation Other Interest TypeThe other interest type held on the tract. Chosen from a list of accepted values.​Access Right of Way; Conservation Easement; Co-held Conservation Easement; Deed Restriction; Co-held Deed Restriction; Fee Ownership; Co-held Fee Ownership; Grazing Lease or Permit; Life Estate; Management Lease or Agreement; Timber Lease or Agreement; OtherN/A Preserve NameThe name of The Nature Conservancy (TNC) preserve that the tract is a part of, this may be the same name as the as the "Public Name" for the tract.Preserve Name if applicableN/APublic AccessThe level of public access allowed on the tract.Open AccessAccess is encouraged on the tract, trails are maintained, signage is abundant, and parking is available. The tract may include regular hours of availability.Open with Limited AccessThere are no special requirements for public access to the tract, the tract may include regular hours of availability with limited amenities.Restricted AccessThe tract requires a special permit from the owner for access, a registration permit on public land, or has highly variable times or conditions to use.Closed AccessNo public access is allowed on the tract.UnknownAccess information for the tract is not currently available.Gap CategoryThe Gap Analysis Project (GAP) code for the tract. Gap Analysis is the science of determining how well we are protecting common plants and animals. Developing the data and tools to support that science is the mission of the Gap Analysis Project (GAP) at the US Geological Survey. See their website for more information, linked in the field name.1 - Permanent Protection for BiodiversityPermanent Protection for Biodiversity2 - Permanent Protection to Maintain a Primarily Natural StatePermanent Protection to Maintain a Primarily Natural State3 - Permanently Secured for Multiple Uses and in natural coverPermanently Secured for Multiple Uses and in natural cover39 - Permanently Secured and in agriculture or maintained grass coverPermanently Secured and in agriculture or maintained grass cover4 - UnsecuredUnsecured (temporary easements lands and/or municipal lands that are already developed (schools, golf course, soccer fields, ball fields)9 - UnknownUnknownProtected AcresThe planar area of the tract polygon in acres, calculated by the TNC Lands geographic information system (GIS).Total geodesic area of polygon in acresProjection: WGS 1984 Web Mercator Auxiliary SphereOriginal Protection DateThe original protection date for the tract, from the Land Resource Management (LRM) system record.Original protection dateN/AStateThe state within the United States of America or the Canadian province where the tract is located.Chosen from a list of state names.N/ACountryThe name of the country where the tract is located.Chosen from a list of countries.N/ADivisionThe name of the TNC North America Region Division where the tract is located. Chosen from a list of TNC North America DivisionsN/A

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

Land cover data set based on the Minnesota Land Cover Classification System (MLCCS) coding scheme. This data was produced using a combination of aerial photograph interpretation and field surveys. There is a minimum mapping unit of 1 acre for natural vegetation and 2 acres for artificial cover types.Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/MLCCS.pdf Data updated: dailyUse 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. General questions about this data set, including errors, omissions, corrections and/or updates should be directed to the Hennepin County Department of Environment & Energy (612-348-3777).

These are the corners of the PLSS. This data set contains summary information about the coordinate location and reliability of corner coordinate information.

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