Title 23 of the Grant County Code is comprised of Chapters 23.04 – Zoning Districts, 23.08 – Performance and Use-specific Standards, and 23.12 – Development Standards, and official zoning maps, and shall be known as the zoning code of Grant County, Washington.The zoning code is intended to carry out the goals and policies of the Grant County Comprehensive Plan, and to benefit the public as a whole and not any specific person or class of persons. The zoning code classifies, designates, and regulates the development of land for agriculture, mineral resource extraction, residential, commercial, industrial, recreation, tourism and public land uses for the unincorporated area of Grant County.Last update1/17/2020 – Comprehensive plan amendments of 2019:Parcel 201542000 converted from Urban Commercial 2 to Urban Residential 1Parcel 201358008 converted from Rural Residential 1 to AgriculturalParcel 160788000 converted from Rural Residential 1 to Urban Residential 2Parcel 151107000 converted from Rural Residential 1 to AgriculturalParcel 170983000 converted from Rural Remote to Urban Heavy IndustrialParcel 313169000 converted from Rural Urban Reserve to Urban Commercial 2Parcel 211912000 converted from Agricultural to Rural Residential 15/17/2019 – the boundary between AG and RC was corrected to follow the north parcel line of 201370001. The parcel boundary of 201370001 had changed in 2007 but the zoning wasn’t adjusted at that time.3/25/2019 – small areas within the Desert Aire open space area were corrected because they were inadvertently missed during the 7/2/2018 update.1/17/2019 - a small portion of Desert Aire zoning was changed from RVOC to RVC.8/1/2018 – minor designation errors were corrected.7/2/2018 – a new Comprehensive Plan was adopted.

Polygons representing the tax appraisal neighborhoods and appraisal revaluation areas in Grant County, Washington.

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 59 counties that have opted-in as of the publication date of this dataset: Aitkin County, Anoka County, Becker County, Benton County, Big Stone County, Carlton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Clearwater County, Cook County, Crow Wing County, Dakota County, Douglas County, Fillmore County, Grant County, Hennepin County, Houston County, Isanti County, Itasca County, Jackson County, Koochiching County, Lac qui Parle County, Lake County, Lake of the Woods County, Lyon County, Marshall County, McLeod County, Mille Lacs County, Morrison County, Mower County, Murray County, Norman County, Olmsted County, Otter Tail County, Pennington County, Pipestone County, Polk County, Pope County, Ramsey County, Red Lake County, Renville County, Rice County, Scott County, Sherburne County, St. Louis County, Stearns County, Steele County, Stevens County, Traverse County, Wabasha County, Waseca County, Washington County, Wilkin County, Winona County, Wright County, and Yellow Medicine County.

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.

Parcels - this layer shows the outer boundary of the land parcel. Be aware that the polygons representing land parcels are based on survey data, but do not always exactly represent the survey data. This data is only a representation of the location and size of land parcels. You are invited to submit corrections to the Data Steward. Polygons are edited continuously as land is subdivided and segregated. Updates are usually posted bi-monthly.OwnerListing - this table lists the owner names associated with each parcel. There can be multiple owners per parcel, and ownership changes over time.