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 = 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 county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 49 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Big Stone, Benton, Carlton, Carver, Cass, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Isanti, Itasca, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright.

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.

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.

Note 3/13/2024: This data pipeline was recently updated. If you notice any issues, please email support@datasf.org, or fill out the form located at Actions->Contact dataset owner.

Recorded parcel geography, both active and retired, with date recorded parcel was added, date recorded parcel was dropped/retired, date was added, dropped or altered re map layer. Contains geography created since the inception of the basemap in 1995, with some exceptions. Zoning District columns reflect current zoning, which can be found here: https://data.sfgov.org/d/xvjh-uu28

This parcels dataset is a spatial representation of tax lots for Gloucester County, New Jersey that have been extracted from the NJ statewide parcels composite by the NJ Office of Information Technology, Office of GIS (NJOGIS). Parcels at county boundaries have been modified to correspond with the NJ county boundaries and the parcels in adjacent counties.Each parcel contains a field named PAMS_PIN based on a concatenation of the county/municipality code, block number, lot number and qualification code. Using the PAMS_PIN, the dataset can be joined to the MOD-IV database table that contains supplementary attribute information regarding lot ownership and characteristics. Due to irregularities in the data development process, duplicate PAMS_PIN values exist in the parcel records. Users should avoid joining MOD-IV database table records to all parcel records with duplicate PAMS_PINs because of uncertainty regarding whether the MOD-IV records will join to the correct parcel records. There are also parcel records with unique PAMS_PIN values for which there are no corresponding records in the MOD-IV database tables. This is mostly due to the way data are organized in the MOD-IV database.The polygons delineated in the dataset do not represent legal boundaries and should not be used to provide a legal determination of land ownership. Parcels are not survey data and should not be used as such.The MOD-IV system provides for uniform preparation, maintenance, presentation and storage of property tax information required by the Constitution of the State of New Jersey, New Jersey Statutes and rules promulgated by the Director of the Division of Taxation. MOD-IV maintains and updates all assessment records and produces all statutorily required tax lists for property tax bills. This list accounts for all parcels of real property as delineated and identified on each municipality's official tax map, as well as taxable values and descriptive data for each parcel. Tax List records were received as raw data from the Taxation Team of NJOIT which collected source information from municipal tax assessors and created the statewide table. This table was subsequently processed for ease of use with NJ tax parcel spatial data and split into an individual table for each county.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.

File Geodatabase - Click here.Shapefile - Click hereThis dataset contains current parcel boundaries and related attributes for approximately 2.4 million parcels maintained by the Los Angeles County Assessor (updated monthly on the second of every month). Due to the size of the data, it is only available for download as a zipped file geodatabase or shapefile at this time. For additional annual assessment roll history and attribute metadata descriptions, please visit the L.A. County Open Data Portal and search for Assessor. To better understand individual data elements, or to interactively view individual parcel information, please visit the Assessor’s Portal. A public-facing parcel map cache can be accessed here (updated weekly): https://public.gis.lacounty.gov/public/rest/services/LACounty_Cache/LACounty_Parcel/MapServer/0All inquiries should be directed to the Mapping & GIS Services Section, LA County Office of the Assessor at gisinfo@assessor.lacounty.gov

The County parcels 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 (multi-PID parcels). It is the combination of the parcel base dataset and the multiple parcel base dataset with attributes from a monthly extract of the property tax information system. The PID field contains the property ID number for each parcel.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.For more information about this dataset, please view metadata.

Official Parcel boundaries in the City of Los Angeles created and maintained by the Bureau of Engineering / GIS Mapping Division.

This dataset includes one file for each of the 51 counties that were collected, as well as a CA_Merged file with the parcels merged into a single file.Note – this data does not include attributes beyond the parcel ID number (PARNO) – that will be provided when available, most likely by the state of California.DownloadA 1.6 GB zipped file geodatabase is available for download - click here.DescriptionA geodatabase with parcel boundaries for 51 (out of 58) counties in the State of California. The original target was to collect data for the close of the 2013 fiscal year. As the collection progressed, it became clear that holding to that time standard was not practical. Out of expediency, the date requirement was relaxed, and the currently available dataset was collected for a majority of the counties. Most of these were distributed with minimal metadata.The table “ParcelInfo” includes the data that the data came into our possession, and our best estimate of the last time the parcel dataset was updated by the original source. Data sets listed as “Downloaded from” were downloaded from a publicly accessible web or FTP site from the county. Other data sets were provided directly to us by the county, though many of them may also be available for direct download. Â These data have been reprojected to California Albers NAD84, but have not been checked for topology, or aligned to county boundaries in any way. Tulare County’s dataset arrived with an undefined projection and was identified as being California State Plane NAD83 (US Feet) and was assigned by ICE as that projection prior to reprojection. Kings County’s dataset was delivered as individual shapefiles for each of the 50 assessor’s books maintained at the county. These were merged to a single feature class prior to importing to the database.The attribute tables were standardized and truncated to include only a PARNO (APN). The format of these fields has been left identical to the original dataset. The Data Interoperablity Extension ETL tool used in this process is included in the zip file. Where provided by the original data sources, metadata for the original data has been maintained. Please note that the attribute table structure changes were made at ICE, UC Davis, not at the original data sources.Parcel Source InformationCountyDateCollecDateCurrenNotesAlameda4/8/20142/13/2014Download from Alamenda CountyAlpine4/22/20141/26/2012Alpine County PlanningAmador5/21/20145/14/2014Amador County Transportation CommissionButte2/24/20141/6/2014Butte County Association of GovernmentsCalaveras5/13/2014Download from Calaveras County, exact date unknown, labelled 2013Contra Costa4/4/20144/4/2014Contra Costa Assessor’s OfficeDel Norte5/13/20145/8/2014Download from Del Norte CountyEl Dorado4/4/20144/3/2014El Dorado County AssessorFresno4/4/20144/4/2014Fresno County AssessorGlenn4/4/201410/13/2013Glenn County Public WorksHumboldt6/3/20144/25/2014Humbodt County AssessorImperial8/4/20147/18/2014Imperial County AssessorKern3/26/20143/16/2014Kern County AssessorKings4/21/20144/14/2014Kings CountyLake7/15/20147/19/2013Lake CountyLassen7/24/20147/24/2014Lassen CountyLos Angeles10/22/201410/9/2014Los Angeles CountyMadera7/28/2014Madera County, Date Current unclear likely 7/2014Marin5/13/20145/1/2014Marin County AssessorMendocino4/21/20143/27/2014Mendocino CountyMerced7/15/20141/16/2014Merced CountyMono4/7/20144/7/2014Mono CountyMonterey5/13/201410/31/2013Download from Monterey CountyNapa4/22/20144/22/2014Napa CountyNevada10/29/201410/26/2014Download from Nevada CountyOrange3/18/20143/18/2014Download from Orange CountyPlacer7/2/20147/2/2014Placer CountyRiverside3/17/20141/6/2014Download from Riverside CountySacramento4/2/20143/12/2014Sacramento CountySan Benito5/12/20144/30/2014San Benito CountySan Bernardino2/12/20142/12/2014Download from San Bernardino CountySan Diego4/18/20144/18/2014San Diego CountySan Francisco5/23/20145/23/2014Download from San Francisco CountySan Joaquin10/13/20147/1/2013San Joaquin County Fiscal year close dataSan Mateo2/12/20142/12/2014San Mateo CountySanta Barbara4/22/20149/17/2013Santa Barbara CountySanta Clara9/5/20143/24/2014Santa Clara County, Required a PRA requestSanta Cruz2/13/201411/13/2014Download from Santa Cruz CountyShasta4/23/20141/6/2014Download from Shasta CountySierra7/15/20141/20/2014Sierra CountySolano4/24/2014Download from Solano Couty, Boundaries appear to be from 2013Sonoma5/19/20144/3/2014Download from Sonoma CountyStanislaus4/23/20141/22/2014Download from Stanislaus CountySutter11/5/201410/14/2014Download from Sutter CountyTehama1/16/201512/9/2014Tehama CountyTrinity12/8/20141/20/2010Download from Trinity County, Note age of data 2010Tulare7/1/20146/24/2014Tulare CountyTuolumne5/13/201410/9/2013Download from Tuolumne CountyVentura11/4/20146/18/2014Download from Ventura CountyYolo11/4/20149/10/2014Download from Yolo CountyYuba11/12/201412/17/2013Download from Yuba County

City of Phoenix parcel boundaries and details are shown for use to provide the best readability when used with different basemaps or aerial photos. Not intended for surveying, legal or engineering purposes. For non-commercial purposes only! This data is updated monthly.

City of Boston 2020 parcels created by the Assessing Department. To add ownership information please join the Property Assessment CSV file in Analyze Boston with Parcels 2020 geospatial data using PID_LONG and GIS_ID fields.

This Esri File GeoDatabase (FGDB) contains digital tax parcel data for Maine Organized Towns and includes the following: Parcels (feature layer); Parcels_ADB (table); and GEOCODES (table).Within Maine, real property data is maintained by the government organization responsible for assessing and collecting property tax for a given location. Organized towns and townships maintain authoritative data for their communities and may voluntarily submit these data to the Maine GeoLibrary Parcel Project. Maine Parcels Organized Towns and Maine Parcels Organized Towns ADB are the product of these voluntary submissions. Communities provide updates to the Maine GeoLibrary on a non-regular basis, which affects the currency of Maine GeoLibrary parcels data; some data are more than ten years old. Another resource for real property transaction data is the County Registry of Deeds, although organized town data should very closely match registry information, except in the case of in-process property conveyance transactions.In Unorganized Territories (defined as those regions of the state without a local government that assesses real property and collects property tax), the Maine Revenue Service is the authoritative source for parcel data. Maine Parcels Unorganized Territory is the authoritative GIS data layer for the Unorganized Territories. However, it must always be used with auxiliary data obtained from the online resources of the Maine Revenue Service to compile up-to-date parcel ownership information.Property maps are a fundamental base for many municipal activities. Although GIS parcel data cannot replace detailed ground surveys, the data can assist municipal officials with functions such as accurate property tax assessment, planning and zoning. Towns can link maps to an assessor's database and display local information, while town officials can show taxpayers how proposed development or changes in municipal services and regulations may affect the community. In many towns, parcel data also helps to provide public notices, plan bus routes, and carry out other municipal services.This dataset contains municipality-submitted parcel data along with previously developed parcel data acquired through the Municipal Grants Project supported by the Maine Library of Geographic Information (MLGI). Grant recipient parcel data submissions were guided by standards presented to the MLGI Board on May 21, 2005,outlined in "Standards for Digital Parcel Files".GEOCODES is a table that lists standardized names and unique identifiers for Maine minor civil divisions and reservations, which represents the first official Standard Geographic Code endorsed and adopted by the Governor of Maine, on July 1, 1971.

This countywide composite of parcels (cadastral) data for Monmouth County represents digitized property boundaries that were developed from best available local and municipal tax maps data. The normalized parcels data are compatible with the New Jersey Department of Treasury MOD-IV system currently used by tax assessors. Stewardship and maintenance of the data continue under the purview of the Monmouth County GIS Office as well as local municipal tax authorities. Parcel attributes were normalized to a standard structure, specified in the New Jersey GIS Parcel Mapping Standard, to store parcel information and provide a PIN (parcel identification number) field common to the PIN that was to be stored in the PAMS (Property Assessment Management System) database to replace the MOD-IV database. Please note that this parcel dataset is not intended for use as tax maps nor for legal purposes. The dataset is intended to provide reasonable representations of parcel boundaries primarily for planning purposes and cartographic representation. Please note cautions when performing a join with this dataset and MOD-IV property records, specifically regarding duplicate and erroneous records. All records may not be provided for in the parcels data or MOD-IV (Tax List Search) tables because of how the data and tables are constructed, or for temporal mismatches. MOD-IV provides for the uniform preparation, maintenance, presentation and storage of property tax information required by the Constitution of the State of New Jersey, New Jersey Statutes and rules promulgated by the Director of Taxation. MOD-IV maintains and updates all assessment records, and produces all statutorily required tax lists. These lists account for all parcels of real property as delineated and identified on each municipality's official tax map, as well as taxable values and descriptive data for each parcel.

© GIS Office, Monmouth County Planning Board, New Jersey.

This dataset is a compilation of tax parcel information for Dakota County, MNThe layer contains one record for each real estate/tax parcel polygon within the county. Condominiums are not included in the polygon layer. If condominiums are desired, use the tax parcel point layer in combination with this polygon layer.In many places a one-to-one relationship does not exist between these parcel polygons and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Currently, only tax parcel ownership (and taxpayer information) is displayed for this dataset.
Tax Parcel - Polygons
Tax Parcel - Points
Tax Parcel - Lines

Additional Resources:Shapefile DownloadREST EndpointVirginia Parcels: Local Schema TablesThese parcel boundaries represent legal descriptions of property ownership, as recorded in various public documents in the local jurisdiction. Attribution is limited to locality identification and parcel id. Tax parcel boundaries have not been edge-matched across municipal boundaries. The parcel geography and attributes are intended for cartographic use and spatial analysis only, and not for use as legal descriptions or property surveys.GDB Version: 10.6.1View Parcels in ArcGIS Online Web Map

INSPIRE Cadastral Parcels is a dataset maintained and produced by the Registers of Scotland to comply with the INSPIRE Directive. It is a sub-set of the Cadastral Map and contains the location of ownership polygons at ground level in Scotland. The polygons contained within the dataset are shapes that show the position and indicative extent of ownership of the earth’s surface for each registered property. Each cadastral parcel has a unique identifier called the inspire id that relates to a registered title on Scotland’s Land Register. The extent of rights and land contained within a title registered in the land register cannot be established from the cadastral parcel. For more detailed information on land and property data in Scotland you can search free at https://scotlis.ros.gov.uk/.

Vector polygon map data of property parcels from the State of Arizona containing 1,422,231 features.

​

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

​

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

​

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

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