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.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under Basic Parcels."Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.

The purpose of this web application is to keep the public informed on current sale values for property within Washington County, Arkansas. All data used to generate this web application is public except for the basemap which would need expressed permission from the Assessor's Office to use. There is a report function within this appliction that can be used to generate a csv file of the sales that are selected.

The Florida Department of Revenue’s Property Tax Oversight(PTO) program collects parcel level Geographic Information System (GIS) data files every April from all of Florida’s 67 county property appraisers’ offices. This GIS data was exported from these file submissions in August 2025. The GIS parcel polygon features have been joined with thereal property roll (Name – Address – Legal, or NAL)file. No line work was adjusted between county boundaries.The polygon data set represents the information property appraisers gathered from the legal description on deeds, lot layout of recorded plats, declaration of condominium documents, recorded and unrecorded surveys.Individual parcel data is updated continually by each county property appraiser as needed. The GIS linework and related attributions for the statewide parcel map are updated annually by the Department every August. The dataset extends countywide and is attribute by Federal Information Processing Standards (FIPS) code.DOR reference with FIPS county codes and attribution definitions - https://fgio.maps.arcgis.com/home/item.html?id=55e830fd6c8948baae1601fbfc33a3b2If you discover the inadvertent release of a confidential record exempt from disclosure pursuant to Chapter 119, Florida Statutes, public records laws, immediately notify the Department of Revenue at 850-717-6570 and your local Florida Property Appraisers’ Office. Please contact the county property appraiser with any parcel specific questions: Florida Property Appraisers’ Offices:Alachua County Property Appraiser – https://www.acpafl.org/Baker County Property Appraiser – https://www.bakerpa.com/Bay County Property Appraiser – https://baypa.net/Bradford County Property Appraiser – https://www.bradfordappraiser.com/Brevard County Property Appraiser – https://www.bcpao.us/Broward County Property Appraiser – https://bcpa.net/Calhoun County Property Appraiser – https://calhounpa.net/Charlotte County Property Appraiser – https://www.ccappraiser.com/Citrus County Property Appraiser – https://www.citruspa.org/Clay County Property Appraiser – https://ccpao.com/Collier County Property Appraiser – https://www.collierappraiser.com/Columbia County Property Appraiser – https://columbia.floridapa.com/DeSoto County Property Appraiser – https://www.desotopa.com/Dixie County Property Appraiser – https://www.qpublic.net/fl/dixie/Duval County Property Appraiser – https://www.coj.net/departments/property-appraiser.aspxEscambia County Property Appraiser – https://www.escpa.org/Flagler County Property Appraiser – https://flaglerpa.com/Franklin County Property Appraiser – https://franklincountypa.net/Gadsden County Property Appraiser – https://gadsdenpa.com/Gilchrist County Property Appraiser – https://www.qpublic.net/fl/gilchrist/Glades County Property Appraiser – https://qpublic.net/fl/glades/Gulf County Property Appraiser – https://gulfpa.com/Hamilton County Property Appraiser – https://hamiltonpa.com/Hardee County Property Appraiser – https://hardeepa.com/Hendry County Property Appraiser – https://hendryprop.com/Hernando County Property Appraiser – https://hernandocountypa-florida.us/Highlands County Property Appraiser – https://www.hcpao.org/Hillsborough County Property Appraiser – https://www.hcpafl.org/Holmes County Property Appraiser – https://www.qpublic.net/fl/holmes/Indian River County Property Appraiser – https://www.ircpa.org/Jackson County Property Appraiser – https://www.qpublic.net/fl/jackson/Jefferson County Property Appraiser – https://jeffersonpa.net/Lafayette County Property Appraiser – https://www.lafayettepa.com/Lake County Property Appraiser – https://www.lakecopropappr.com/Lee County Property Appraiser – https://www.leepa.org/Leon County Property Appraiser – https://www.leonpa.gov/Levy County Property Appraiser – https://www.qpublic.net/fl/levy/Liberty County Property Appraiser – https://libertypa.org/Madison County Property Appraiser – https://madisonpa.com/Manatee County Property Appraiser – https://www.manateepao.gov/Marion County Property Appraiser – https://www.pa.marion.fl.us/Martin County Property Appraiser – https://www.pa.martin.fl.us/Miami-Dade County Property Appraiser – https://www.miamidade.gov/pa/Monroe County Property Appraiser – https://mcpafl.org/Nassau County Property Appraiser – https://ncpafl.com/Okaloosa County Property Appraiser – https://okaloosapa.com/Okeechobee County Property Appraiser – https://www.okeechobeepa.com/Orange County Property Appraiser – https://ocpaweb.ocpafl.org/Osceola County Property Appraiser – https://www.property-appraiser.org/Palm Beach County Property Appraiser – https://www.pbcgov.org/papa/index.htmPasco County Property Appraiser – https://pascopa.com/Pinellas County Property Appraiser – https://www.pcpao.org/Polk County Property Appraiser – https://www.polkpa.org/Putnam County Property Appraiser – https://pa.putnam-fl.com/Santa Rosa County Property Appraiser – https://srcpa.gov/Sarasota County Property Appraiser – https://www.sc-pa.com/Seminole County Property Appraiser – https://www.scpafl.org/St. Johns County Property Appraiser – https://www.sjcpa.gov/St. Lucie County Property Appraiser – https://www.paslc.gov/Sumter County Property Appraiser – https://www.sumterpa.com/Suwannee County Property Appraiser – https://suwannee.floridapa.com/Taylor County Property Appraiser – https://qpublic.net/fl/taylor/Union County Property Appraiser – https://union.floridapa.com/Volusia County Property Appraiser – https://vcpa.vcgov.org/Wakulla County Property Appraiser – https://mywakullapa.com/Walton County Property Appraiser – https://waltonpa.com/Washington County Property Appraiser – https://www.qpublic.net/fl/washington/Florida Department of Revenue Property Tax Oversight https://floridarevenue.com/property/Pages/Home.aspx

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

polygons / points
Anoka - 129271 / 129271
Carver - 38205 / 38205
Dakota - 136067 / 150436
Hennepin - 424182 / 424182
Ramsey - 149101 / 168152
Scott - 55213 / 55213
Washington - 98933 / 104100 (October 2009)

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

County assessor's online applications for searching and rviewing data about parcels and proprties.

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.

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

King County GIS data is at: https://gis-kingcounty.opendata.arcgis.com/ (new KCGIS Open Data site) OR http://www5.kingcounty.gov/gisdataportal/ (legacy KCGIS data FTP download portal)

Tax parcel polygons throughout Pierce County, including condos, but not including mobile homes which can be found in the "Mobile Home" layer instead. Parcel number is the unique identifier and additional parcel attribution can be found here (https://www.piercecountywa.gov/736/Data-Downloads) Click the link for Use Code Descriptions (https://www.piercecountywa.gov/DocumentCenter/View/604/Use-Code-Listing?bidId=) Please read metadata (https://matterhorn.piercecountywa.gov/GISmetadata/pdbparc_taxparcel.html) for additional information. Any data download constitutes acceptance of the Terms of Use (https://matterhorn.piercecountywa.gov/Disclaimer/PierceCountyGISDataTermsofUse.pdf) If you have questions or need supplemental information, please call the Assessor-Treasurer Operations Team at 253-798-3134.

Unincorporated Urban Growth Areas (UGA) as defined by the Growth Management Act (GMA). The annual update is conducted by collecting UGA polygons directly from each of Washington's 39 counties. As of 2025, there are 27 counties with UGAs.All UGA polygons are normalized against the Department of Revenue's (DOR) "City Boundaries" layer (shared to the Washington Geoportal a.k.a. the GIS Open Data site: geo.wa.gov). The City Boundaries layer was processed into this UGA layer such that any overlapping area of UGA polygons (from authoritative individual counties) was erased. Since DOR polygons and county-sourced UGA polygons do not have perfect topology, many slivers resulted after the erase operation. These are attempted to be irradicated by these processing steps. "Multipart To Singlepart" Esri tool; exploded all polygons to be individualSlivers were mathematically identified using a 4 acre area threshold and a 0.3 "thinness ratio" threshold as described by Esri's "Polygon Sliver" tool. These slivers are merged into the neighboring features using Esri's "Eliminate" tool.Polygons that are less than 5,000 sq. ft. and not part of a DOR city (CITY_NM = Null) were also merged via the "Eliminate" tool. (many very small slivers were manually found yet mathematically did not meet the thinness ratio threshold)The final 8 polygons less than 25 sq. ft. were manually deleted (also slivers but were not lined up against another feature and missed by the "Eliminate" tool runs)Dissolved all features back to multipart using all fieldsAll UGAs polygons remaining are unincorporated areas beyond the city limits. Any polygon with CITY_NM populated originated from the DOR "City Boundaries" layer. The DOR's City Boundaries are updated quarterly by DOR. For the purposes of this UGA layer, the city boundaries was downloaded one time (4/24/2025) and will not be updated quarterly. Therefore, if precise city limits are required by any user of UGA boundaries, please refer to the city boundaries layer and conduct any geoprocessing needed. The DOR's "City Boundaries" layer is available here:https://www.arcgis.com/home/item.html?id=69fcb668dc8d49ea8010b6e33e42a13aData is updated in conjunction with the annual statewide parcel layer update. Latest update completed April 2025.

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

Represents both land parcels and any tax accounts associated with them. In the case of condominiums and mobile homes, this can result in many taxlots being stacked on top of one another. This layer is used for property assessment and taxation purposes and is updated on a weekly basis. Please note that taxlot boundaries are not surveys and cannot be used to determine the location of property lines on the ground. This is a version of our original Taxlots layer that is intended for public use. All property owner-related information has been removed to ensure compliance with Washington State Law, RCW 46.52.070(8), and Washington State Office of the Attorney General opinion AGO 2019 No. 3. Anyone who needs to obtain the property owner name data must submit an email request to the Clark County Treasurer's Office (treasoff@clark.wa.gov) which specifies that they are requesting access to the property owner name data that are maintained by Clark County GIS.See Clark County Metadata Data source: ..\FGDB\dw_clark.gdb\TaxlotsPublic

This is a comprehensive building address point layer for Pierce County, Washington. Every unique house number has a point located within the building footprint of the addressed structure (where possible). Multi-unit structures, mobile home parks, and buildings with the same street address are further identified by mailstop in the attribute table. Some vacant parcels may or may not have an assigned temporary address point. A permanent address will be assigned to a vacant parcel if a permitted structure is built on that parcel. Please read metadata for additional information (https://matterhorn.piercecountywa.gov/GISmetadata/pdbis_buildingaddress_public.html). Any use or data download constitutes acceptance of the Terms of Use (https://matterhorn.piercecountywa.gov/disclaimer/PierceCountyGISDataTermsofUse.pdf).

A bug has been logged for the 403 error which is generated when trying to download large datasets through the Download menu. As a workaround, the zipped file geodatabase is available here:https://www.arcgis.com/sharing/rest/content/items/d04a50e44fbd4497bb57830b52fe5a2b/dataThe Washington State Land Use coverage was produced from digital county tax parcel layers using Department of Revenue (DOR) two digit land use codes (see; WAC 458-53-030, Stratification of assessment rolls - real property). Land use attribute data has been normalized for all county parcel data to conform to the two digit DOR codes. All county parcel layers are dissolved using the normalized land use code. No county parcel information remains in this data other that what geometry remains from the dissolve process.

A web map used to access tax parcel, boundary, ownership, acreage, survey, zoning and tax information. Errors and Omissions Do Exist.The information provided is for reference only and subject to independent verification. User assumes all responsibility for its use.https://www.fayette-co-oh.com/Fayette County ProfileFayette County is a county located in the U.S. state of Ohio. Its county seat is Washington Court House. Fayette County was formed on March 1, 1810 from portions of Highland County and Ross County. It was named after Marie-Joseph Motier, Marquis de La Fayette, a French general and politician who took the side of the Colonials during the American Revolutionary War and who played an important role in the French Revolution.Fayette County is a part of the Virginia Military survey, which was reserved in 1783, to be allotted to Virginia soldiers. This district includes the entire counties of Adams, Brown, Clermont, Clinton, Highland, Fayette, Madison and Union; and a portion of the counties of Scioto, Pike, Ross, Pickaway, Franklin, Delaware, Marion, Hardin, Logan, Champaign, Clarke, Greene, Warren and Hamilton.Fayette County was formed January 19, 1810 (took effect March 1st) from Ross and Highland counties. Beginning at the southwest corner of Pickaway, running north “with the line of said county to the corner of Madison; thence west with the line of said Madison county to the line of Greene county; thence south with the line of Greene county to the southeast corner thereof; thence east five miles; thence south to the line of Highland county; thence east with said line to Paint Creek; thence in a straight line to the beginning.” All the lower portion was taken from Highland and the upper from Ross.The first portion of land entered within the territory of what is now Fayette county, was a part of original surveys Nos. 243 and 772, lying partly in Clinton county. The first survey lying wholly within Fayette county was No. 463, in what is now Madison township, surveyed for Thomas Overton by John O’Bannon June 30, 1776.The original townships were Jefferson, Greene, Wayne, Madison, Paint and Union. Concord township was formed in April 1818, from Greene. Marion township was formed in June, 1840 from Madison. Perry township was formed June 4, 1845, from Wayne and Greene. Jasper township was formed from Jefferson and Concord December 2, 1845.Washington C.H. was laid out originally on a part of entry 757, which contained 1200 acres and belonged to Benjamin Temple, of Logan county, Kentucky, who donated 150 acres to Fayette county, on condition that it be used as the site of the county seat. The deed of conveyance was made December 1, 1810, by Thomas S. Hind, attorney for Temple, to Robert Stewart, who was appointed by the legislature as director for the town of Washington. The town was laid off some time between December 1, 1810, and February 26, 1811, the latter being the date of the record of the town plat.Bloomingburg (originally called New Lexington) was laid out in 1815, by Solomon Bowers, and originally contained 34 and ¾ acres. On March 4, 1816, Bowers laid out and added twenty more lots. The name of the town was later changed to Bloomingburg by act of the legislature. The town was incorporated by act of the legislature, February 5, 1847.Jeffersonville was laid out March 1, 1831, by Walter B. Write and Chipman Robinson, on 100 acres of land belonging to them, they started selling the lots at $5 each. The town incorporated March 17, 1838. The first house was erected by Robert Wyley.The first railroad, now the C. & M. V., was completed in 1852; the second, now the Detroit Southern, in 1875; the third, now the C.H. & D. in 1879; and the fourth, now the B. & O. S. W., in 1884.The first permanent settler (probably) was a Mr. Wolf who settled in what is now Wayne township, in about the year 1796. - Circa 1886 - Map of Fayette County, Ohio. Issued by the Fayette County Record.

The Washington State Land Use coverage was produced from digital county tax parcel layers using Department of Revenue (DOR) two digit land use codes (see; WAC 458-53-030, Stratification of assessment rolls - real property). Land use attribute data has been normalized for all county parcel data to conform to the two digit DOR codes. All county parcel layers are dissolved using the normalized land use code. No county parcel information remains in this data other that what geometry remains from the dissolve process.

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