This dataset contains boundaries of individual parcels in Allegheny County, including the county block and lot number. As this is a very large dataset, you may wish to use our property information extractor (http://tools.wprdc.org/parcels-n-at/) to download filtered versions of this parcel dataset. The most authoritative source for this data is now the PASDA page (https://www.pasda.psu.edu/uci/DataSummary.aspx?dataset=1214), which includes links to historical versions of the shapefile representations of this data.

Land parcel data for all properties in the City of Detroit from the Office of the Assessor. These are the parcel boundaries for the 2024 tax year.The Parcels data set from the City of Detroit Office of the Assessor is updated daily with land parcel data for all properties within the City of Detroit. Records in this data set describe the assessed values, rights, ownership interests, most recent sales data, physical descriptions, and addresses associated with each parcel. Parcels are distinguished from lots or plots of land in that property ownership rights are the fundamental units of division between parcels. The graphic depiction of land parcels represents real property ownership within the City for both privately and publicly owned properties.Data maintenance note: Databases used by the Office of the Assessor for parcels data are checked for updates daily. If an update is detected, the published Parcels dataset is then updated to reflect the most recent data available. Similarly, Zoning data provided by the Buildings, Safety Engineering, and Environmental Department (BSEED) Zoning Division is checked for updates daily. If any updates are available, values in the Zoning field are updated to reflect the most recent zoning data available. The "Data Updated" date for the Parcels dataset reflects the most recent date any data updates were detected and incorporated into the Parcels dataset. The GIS / Land Records Maintenance Division in the Office of the Assessor manages the data integrity of the parcel file.

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

These are lands still within the District of Columbia that has never been subdivided into either Record or Tax Lots through the two offices that manage land records (OS & RPTA), this land is referred to as Parcels, expressed as fractions (Ex Parcel 117/36). In this example, the number “36” would be the 36th out conveyance from original Parcel 117. The tracking of parcels was started in 1905 when, by Act of Congress, all the District’s unsubdivided properties which were mostly rural farms at the time were given parcel numbers. Their boundaries were also depicted (in many cases approximated), in large books in DCRA's Office of the Surveyor. Until the late 1960s, building permits were routinely issued by the city for new construction on Parcels, but today all Parcels, like Tax Lots, must be converted into subdivision Lots of Record before permits will be issued for exterior work. Parcels are only found in the old “County of Washington,” north of Florida Ave and east of the Anacostia River. There are no Parcels found within the original city limits or Georgetown. Parcels are not in Squares. There are examples where parcel land may be physically located in the middle of a city Square, but Parcels are not considered part of a Square until they are duly subdivided by the D.C. Surveyor’s Office.

"Due to the size of this dataset, both Shapefile and Spreadsheet download options will not work as expected. The File Geodatabase is an alternative option for this data download"This is SCAG's 2019 Annual Land Use (ALU v. 2019.1) at the parcel-level, updated as of February 2021. This dataset has been modified to include additional attributes in order to feed SCAG's Housing Element Parcel Tool (HELPR), version 2.0. The dataset will be further reviewed and updated as additional information is released. Please refer to the tables below for data dictionary and SCAG’s land use classification.Field NameData TypeField DescriptionPID19Text2019 SCAG’s parcel unique IDAPN19Text2019 Assessor’s parcel numberCOUNTYTextCounty name (based on 2016 county boundary)COUNTY_IDDoubleCounty FIPS code (based on 2016 county boundary)CITYTextCity name (based on 2016 city boundary)CITY_IDDoubleCity FIPS code (based on 2016 city boundary)MULTIPARTShort IntegerMultipart feature (the number of multiple polygons; '1' = singlepart feature)STACKLong IntegerDuplicate geometry (the number of duplicate polygons; '0' = no duplicate polygons)ACRESDoubleParcel area (in acreage)GEOID20Text2020 Census Block Group GEOIDSLOPEShort IntegerSlope information1APN_DUPLong IntegerDuplicate APN (the number of multiple tax roll property records; '0' = no duplicate APN)IL_RATIODoubleRatio of improvement assessed value to land assessed valueLU19Text2019 existing land useLU19_SRCTextSource of 2019 existing land use2SCAGUID16Text2016 SCAG’s parcel unique IDAPNText2016 Assessor’s parcel numberCITY_GP_COText2016 Jurisdiction’s general plan land use designationSCAG_GP_COText2016 SCAG general plan land use codeSP_INDEXShort IntegerSpecific plan index ('0' = outside specific plan area; '1' = inside specific plan area)CITY_SP_COText2016 Jurisdiction’s specific plan land use designationSCAG_SP_COText2016 SCAG specific plan land use codeCITY_ZN_COText2016 Jurisdiction’s zoning codeSCAG_ZN_COText2016 SCAG zoning codeLU16Text2016 existing land useYEARLong IntegerDataset yearPUB_OWNShort IntegerPublic-owned land index ('1' = owned by public agency)PUB_NAMETextName of public agencyPUB_TYPETextType of public agency3BF_SQFTDoubleBuilding footprint area (in square feet)4BSF_NAMETextName of brownfield/superfund site5BSF_TYPETextType of brownfield/superfund site5FIREShort IntegerParcel intersects CalFire Very High Hazard Local Responsibility Areas or State Responsibility Areas (November 2020 version) (CalFIRE)SEARISE36Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)1 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)SEARISE72Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)2 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)FLOODShort IntegerParcel intersects with a FEMA 100 Year Flood Plain data from the Digital Flood Insurance Rate Map (DFIRM), obtained from Federal Emergency Management Agency (FEMA) in August 10, 2017EQUAKEShort IntegerParcel intersects with an Alquist-Priolo Earthquake Fault Zone (California Geological Survey; 2018)LIQUAFAShort IntegerParcel intersects with a Liquefaction Susceptibility Zone (California Geological Survey; 2016)LANDSLIDEShort IntegerParcel intersects with a Landslide Hazard Zone (California Geological Survey; 2016)CPADShort IntegerParcel intersects with a protected area from the California Protected Areas Database(CPAD) – www.calands.org (accessed April 2021)RIPARIANShort IntegerParcel centroid falls within Active River Areas(2010)or parcel intersects with a Wetland Area in the National Wetland Inventory(Version 2)WILDLIFEShort IntegerParcel intersects with wildlife habitat (US Fish & Wildlife ServiceCritical Habitat, Southern California Missing Linkages, Natural Lands & Habitat Corridors from Connect SoCal, CEHC Essential Connectivity Areas,Critical Coastal Habitats)CNDDBShort IntegerThe California Natural Diversity Database (CNDDB)includes the status and locations of rare plants and animals in California. Parcels that overlap locations of rare plants and animals in California from the California Natural Diversity Database (CNDDB)have a greater likelihood of encountering special status plants and animals on the property, potentially leading to further legal requirements to allow development (California Department of Fish and Wildlife). Data accessed in October 2020.HCPRAShort IntegerParcel intersects Natural Community & Habitat Conservation Plans Reserve Designs from the Western Riverside MHSCP, Coachella Valley MHSCP, and the Orange County Central Coastal NCCP/HCP, as accessed in October 2020WETLANDShort IntegerParcel intersects a wetland or deepwater habitat as defined by the US Fish & Wildlife Service National Wetlands Inventory, Version 2.UAZShort IntegerParcel centroid lies within a Caltrans Adjusted Urbanized AreasUNBUILT_SFDoubleDifference between parcel area and building footprint area expressed in square feet.6GRCRY_1MIShort IntegerThe number of grocery stores within a 1-mile drive7HEALTH_1MIShort IntegerThe number of healthcare facilities within a 1-mile drive7OPENSP_1MIShort IntegerQuantity of open space (roughly corresponding to city blocks’ worth) within a 1-mile drive7TCAC_2021TextThe opportunity level based on the 2021 CA HCD/TCAC opportunity scores.HQTA45Short IntegerField takes a value of 1 if parcel centroid lies within a 2045 High-Quality Transit Area (HQTA)JOB_CTRShort IntegerField takes a value of 1 if parcel centroid lies within a job centerNMAShort IntegerField takes a value of 1 if parcel centroid lies within a neighborhood mobility area.ABS_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within an absolute constraint area. See the Sustainable Communities Strategy Technical Reportfor details.VAR_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within a variable constraint area. See the Sustainable Communities Strategy Technical Reportfor details.EJAShort IntegerField takes a value of 1 if parcel centroid lies within an Environmental Justice Area. See the Environmental Justice Technical Reportfor details.SB535Short IntegerField takes a value of 1 if parcel centroid lies within an SB535 Disadvantaged Community area. See the Environmental Justice Technical Reportfor details.COCShort IntegerField takes a value of 1 if parcel centroid lies within a Community of Concern See the Environmental Justice Technical Reportfor details.STATEShort IntegerThis field is a rudimentary estimate of which parcels have adequate physical space to accommodate a typical detached Accessory Dwelling Unit (ADU)8.SBShort IntegerIndex of ADU eligibility according to the setback reduction policy scenario (from 4 to 2 feet) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SMShort IntegerIndex of ADU eligibility according to the small ADU policy scenario (from 800 to 600 square feet ADU) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)PKShort IntegerIndex of ADU eligibility according to parking space exemption (200 square feet) policy scenario (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SMShort IntegerIndex of ADU eligibility according to both the setback reduction and small ADU policy scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_PKShort IntegerIndex of ADU eligibility according to both the setback reduction and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SM_PKShort IntegerIndex of ADU eligibility according to both the small ADU policy and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SM_PKShort IntegerIndex of ADU eligibility according to the setback reduction, small ADU, and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)1. Slope: '0' - 0~4 percent; '5' - 5~9 percent; '10' - 10~14 percent; '15' = 15~19 percent; '20' - 20~24 percent; '25' = 25 percent or greater.2. Source of 2019 existing land use: SCAG_REF- SCAG's regional geospatial datasets;ASSESSOR- Assessor's 2019 tax roll records; CPAD- California Protected Areas Database (version 2020a; accessed in September 2020); CSCD- California School Campus Database (version 2018; accessed in September 2020); FMMP- Farmland Mapping and Monitoring Program's Important Farmland GIS data (accessed in September 2020); MIRTA- U.S. Department of Defense's Military Installations, Ranges, and Training Areas GIS data (accessed in September 2020)3. Type of public agency includes federal, state, county, city, special district, school district, college/university, military.4. Based on 2019 building footprint data obtained from BuildingFootprintUSA (except that 2014 building footprint data was used for Imperial County). Please note that 2019 building footprint data does not cover the entire SCAG region (overlapped with 83% of parcels in the SCAG Region).5. Includes brownfield/superfund site whose address information are matched by SCAG rooftop address locator. Brownfield data was obtained from EPA's Assessment, Cleanup and Redevelopment Exchange System (ACRES) database, Cleanups in my community (CIMC), DTSC brownfield Memorandum of Agreement (MOA). Superfund site data was obtained from EPA's Superfund Enterprise Management System (SEMS) database.6. Parcels with a zero value for building footprint area are marked as NULL to indicate this field is not reliable.7. These values are intended as a rudimentary indicator of accessibility developed by SCAG using 2016 InfoUSA business establishment data and 2017 California Protected Areas data. See documentation for details.8. A detailed study conducted by Cal Poly Pomona (CPP) and available hereconducted an extensive review of state and local requirements and development trends for ADUs in the SCAG region and developed a baseline set of assumptions for estimating how many of a jurisdiction’s parcels

Download In State Plane Projection Here ** In addition to the Tax Parcel polygons feature class, the hyperlink download above also contains a parcel point data layer ** Parcel boundaries are developed from deeds, plats of subdivision and other legal documents going back to the mid 1800's, following generally accepted practices used in Public Land Survey System states, and following guidelines established by the Illinois Department of Revenue and the International Association of Assessment Officials. Lake County's parcel coverage is based on resolving the accumulated evidence of all of the legal documents surrounding a particular parcel or subdivision, and not the result of a countywide resurvey. These parcel boundaries are intended to be a visual inventory of property for tax and other administrative purposes; they are not intended to be used in place of an on-site survey or for the precise determination of property corners or PLSS features based on GIS coordinates. In Illinois, only a registered professional land surveyor is authorized to determine boundary locations. Included are the tax parcel boundaries, represented as polygons and centroids, for all changes resulting from legal records submitted to the Recorder of Deeds up to December 31st of the preceding year, as well as any court orders, municipal annexations and other transactions which impact the tax parcel boundaries. NOTE: The ONLY attribute included is the Property Index Number, or PARCEL_NUM. Additional assessment attribute data can be downloaded here This parcel layer is used for tax assessment purposes and for a variety of other local government functions. It changes often, both spatially and in its attribution, based on divisions or consolidations, the sale of property and other transactions. Example: PIN 08-17-304-014 can be interpreted as follows: Township 08, Section 17, Block 304, Parcel 014. Note that the first digit of block, "3" in this example, signifies that the parcel lies in quarter section 3. The quarter sections are labeled from 1 through 4, representing the northwest, northeast, southwest and southeast quarter sections, respectively. Update Frequency: This dataset is updated on a weekly basis.

This dataset was developed to provide accurate parcel boundaries for Indiana, as part of Indiana's annual GIS Data harvest Data Sharing Initiative (IDSI) of the Indiana Geographic Information Office (IGIO).This data layer is an Esri file geodatabase polygon feature class that contains parcel boundaries maintained by county agencies in Indiana. It was released by the Indiana Geographic Information Office (IGIO) on November 13, 2024. The IGIO compiled the data as part of the Indiana Data Harvest program between the Indiana Geographic Information Council (IGIC) and Indiana local governments to provide the most accurate framework data for the citizens of Indiana. These layers include address points, street centerlines, land parcels, and governmental boundaries.

Parcel Viewer makes searching for King County parcel information easy. You can search by address, search by parcel number, or you can just zoom in on the map and click on a parcel. Once a parcel is selected, you will get direct links to the King County Assessor’s eReal Property report and the Districts and Development Conditions report.

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

REQUIRED: A brief narrative summary of the data set.

Parcels are identified by an Assessor's Parcel Number (APN) consisting of a three digit Book number, a two digit Map number, a three digit Item number, possibly a Split letter. This dataset contains all active parcels within Maricopa County. State and Federal lands are not represented. Vertical parcels are annotated using the Floor field.

There are approximately 2.6 million agricultural land parcels in England, and the Parcel Points (England) point dataset represents the approximate centres, or centroids of these parcels. The number of agricultural parcels varies over time as fields are split or joined consequently creating new fields with new centroids. Some parcels may be sold for development and are no longer available for agricultural use, occasionally land that was previously developed may return to agriculture, e.g. disused airfields.

Parcel Points is a simple point dataset that uses the centres of agricultural parcels attributed only with the parcel reference ID. Parcel points are categorised according to county and are available as England-wide coverage too.

Users can use the data as supplied or attach their own attributes. When viewed overlying other publicly available data, e.g. satellite imagery (Google earth), OS open data, OpenStreetMap, etc. that may feature agricultural land the points provide a useful reference point to identify the approximate centre of agricultural parcels.

Parcel Points uses the Open Government Licence v3.0 as used by other publicly accessible data on the Defra Data Services Platform and will be updated every 6 months.

Coverage will be for agricultural land parcels in England only.

Users should be aware that client-side constraints associated WFS and OGC API, such as maximum feature limits, may affect the loading and display of parcel points. Parcel Points WMS are not affected to the same extent.

What is Land Parcel Data?

Land parcel data refers to a collection of spatially referenced information about individual land parcels or lots within a specified area. It includes attributes such as parcel ID, owner information, legal descriptions, acreage, zoning classifications, tax assessments, and geographic coordinates. This data is typically sourced from government agencies, cadastral surveys, and private entities, then compiled and organized into a structured dataset suitable for analysis and visualization.

Land Parcel Data Details:

• 157 Million nationwide parcel records and geometries
• Approximately 100 attributes (standard schema)
• Tax assessment fields
• Universal parcel ID
• Monthly rolling updates
• Standardized land use codes
• USPS validated address data with residential property & vacancy indicators
• Building counts & footprint square footage attributes
• Right-of-way (ROW) parcel indicator
• Placekey - Location identifier
• Flood zones and school districts
• Homesteads exemption
  • Crop data layer fields
  • Public access status

Parcels and property data maintained and provided by Lee County Property Appraiser. This dataset includes condominium units. Property attribute data joined to parcel GIS layer by Lee County Government GIS.Projected coordinate system name: NAD_1983_StatePlane_Florida_West_FIPS_0902_FeetGeographic coordinate system name: GCS_North_American_1983

 Name
 Type
 Length
 Description


 STRAP
 String
 25
 17-digit Property ID (Section, Township, Range, Area, Block, Lot)


 BLOCK
 String
 10
 5-digit portion of STRAP (positions 9-13)


 LOT
 String
 8
 Last 4-digits of STRAP


 FOLIOID
 Double
 8
 Unique Property ID


 MAINTDATE
 Date
 8
 Date LeePA staff updated record


 MAINTWHO
 String
 20
 LeePA staff who updated record


 UPDATED
 Date
 8
 Data compilation date


 HIDE_STRAP
 String
 1
 Confidential parcel ownership


 TRSPARCEL
 String
 17
 Parcel ID sorted by Township, Range & Section


 DORCODE
 String
 2
 Department of Revenue property classification code


 CONDOTYPE
 String
 1
 Type of condominium: C (commercial) or R (residential)


 UNITOFMEAS
 String
 2
 Type of Unit of Measure (ex: AC=acre, LT=lot, FF=frontage in feet)


 NUMUNITS
 Double
 8
 Number of Land Units (units defined in UNITOFMEAS)


 FRONTAGE
 Integer
 4
 Road Frontage in Feet


 DEPTH
 Integer
 4
 Property Depth in Feet


 GISACRES
 Double
 8
 Total Computed Acres from GIS


 TAXINGDIST
 String
 3
 Taxing District of Property


 TAXDISTDES
 String
 60
 Taxing District Description


 FIREDIST
 String
 3
 Fire District of Property


 FIREDISTDE
 String
 60
 Fire District Description


 ZONING
 String
 10
 Zoning of Property


 ZONINGAREA
 String
 3
 Governing Area for Zoning


 LANDUSECOD
 SmallInteger
 2
 Land Use Code


 LANDUSEDES
 String
 60
 Land Use Description


 LANDISON
 String
 5
 BAY,CANAL,CREEK,GULF,LAKE,RIVER & GOLF


 SITEADDR
 String
 55
 Lee County Addressing/E911


 SITENUMBER
 String
 10
 Property Location - Street Number


 SITESTREET
 String
 40
 Street Name


 SITEUNIT
 String
 5
 Unit Number


 SITECITY
 String
 20
 City


 SITEZIP
 String
 5
 Zip Code


 JUST
 Double
 8
 Market Value


 ASSESSED
 Double
 8
 Building Value + Land Value


 TAXABLE
 Double
 8
 Taxable Value


 LAND
 Double
 8
 Land Value


 BUILDING
 Double
 8
 Building Value


 LXFV
 Double
 8
 Land Extra Feature Value


 BXFV
 Double
 8
 Building Extra Feature value


 NEWBUILT
 Double
 8
 New Construction Value


 AGAMOUNT
 Double
 8
 Agriculture Exemption Value


 DISAMOUNT
 Double
 8
 Disability Exemption Value


 HISTAMOUNT
 Double
 8
 Historical Exemption Value


 HSTDAMOUNT
 Double
 8
 Homestead Exemption Value


 SNRAMOUNT
 Double
 8
 Senior Exemption Value


 WHLYAMOUNT
 Double
 8
 Wholly Exemption Value


 WIDAMOUNT
 Double
 8
 Widow Exemption Value


 WIDRAMOUNT
 Double
 8
 Widower Exemption Value


 BLDGCOUNT
 SmallInteger
 2
 Total Number of Buildings on Parcel


 MINBUILTY
 SmallInteger
 2
 Oldest Building Built


 MAXBUILTY
 SmallInteger
 2
 Newest Building Built


 TOTALAREA
 Double
 8
 Total Building Area


 HEATEDAREA
 Double
 8
 Total Heated Area


 MAXSTORIES
 Double
 8
 Tallest Building on Parcel


 BEDROOMS
 Integer
 4
 Total Number of Bedrooms


 BATHROOMS
 Double
 8
 Total Number of Bathrooms / Not For Comm


 GARAGE
 String
 1
 Garage on Property 'Y'


 CARPORT
 String
 1
 Carport on Property 'Y'


 POOL
 String
 1
 Pool on Property 'Y'


 BOATDOCK
 String
 1
 Boat Dock on Property 'Y'


 SEAWALL
 String
 1
 Sea Wall on Property 'Y'


 NBLDGCOUNT
 SmallInteger
 2
 Total Number of New Buildings on ParcelTotal Number of New Buildings on Parcel


 NMINBUILTY
 SmallInteger
 2
 Oldest New Building Built


 NMAXBUILTY
 SmallInteger
 2
 Newest New Building Built


 NTOTALAREA
 Double
 8
 Total New Building Area


 NHEATEDARE
 Double
 8
 Total New Heated Area


 NMAXSTORIE
 Double
 8
 Tallest New Building on Parcel


 NBEDROOMS
 Integer
 4
 Total Number of New Bedrooms


 NBATHROOMS
 Double
 8
 Total Number of New Bathrooms/Not For Comm


 NGARAGE
 String
 1
 New Garage on Property 'Y'


 NCARPORT
 String
 1
 New Carport on Property 'Y'


 NPOOL
 String
 1
 New Pool on Property 'Y'


 NBOATDOCK
 String
 1
 New Boat Dock on Property 'Y'


 NSEAWALL
 String
 1
 New Sea Wall on Property 'Y'


 O_NAME
 String
 30
 Owner Name


 O_OTHERS
 String
 120
 Other Owners


 O_CAREOF
 String
 30
 In Care Of Line


 O_ADDR1
 String
 30
 Owner Mailing Address Line 1


 O_ADDR2
 String
 30
 Owner Mailing Address Line 2


 O_CITY
 String
 30
 Owner Mailing City


 O_STATE
 String
 2
 Owner Mailing State


 O_ZIP
 String
 9
 Owner Mailing Zip


 O_COUNTRY
 String
 30
 Owner Mailing Country


 S_1DATE
 Date
 8
 Most Current Sale Date > $100.00


 S_1AMOUNT
 Double
 8
 Sale Amount


 S_1VI
 String
 1
 Sale Vacant or Improved


 S_1TC
 String
 2
 Sale Transaction Code


 S_1TOC
 String
 2
 Sale Transaction Override Code


 S_1OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_2DATE
 Date
 8
 Previous Sale Date > $100.00


 S_2AMOUNT
 Double
 8
 Sale Amount


 S_2VI
 String
 1
 Sale Vacant or Improved


 S_2TC
 String
 2
 Sale Transaction Code


 S_2TOC
 String
 2
 Sale Transaction Override Code


 S_2OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_3DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_3AMOUNT
 Double
 8
 Sale Amount


 S_3VI
 String
 1
 Sale Vacant or Improved


 S_3TC
 String
 2
 Sale Transaction Code


 S_3TOC
 String
 2
 Sale Transaction Override Code


 S_3OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_4DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_4AMOUNT
 Double
 8
 Sale Amount


 S_4VI
 String
 1
 Sale Vacant or Improved


 S_4TC
 String
 2
 Sale Transaction Code


 S_4TOC
 String
 2
 Sale Transaction Override Code


 S_4OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 LEGAL
 String
 255
 Full Legal Description (On Deed)


 GARBDIST
 String
 3
 County Garbage Hauling Area


 GARBTYPE
 String
 1
 County Garbage Pick-up Type


 GARBCOMCAT
 String
 1
 County Garbage Commercial Category


 GARBHEADER
 String
 1
 Garbage Header Code


 GARBUNITS
 Double
 8
 Number of Garbage Units


 CREATEYEAR

A current-year-only universe of Cook County parcels with attached geographic, governmental, and spatial data. When working with Parcel Index Numbers (PINs) make sure to zero-pad them to 14 digits. Some datasets may lose leading zeros for PINs when downloaded. Additional notes:Non-taxing district data is attached via spatial join (st_contains) to each parcel's centroid. Tax district data (school district, park district, municipality, etc.) are attached by a parcel's assigned tax code. Centroids are based on Cook County parcel shapefiles. Older properties may be missing coordinates and thus also missing attached spatial data (usually they are missing a parcel boundary in the shapefile). Newer properties may be missing a mailing or property address, as they need to be assigned one by the postal service. This dataset contains data for the current tax year, which may not yet be complete or final. Assessed values for any given year are subject to change until review and certification of values by the Cook County Board of Review, though there are a few rare circumstances where values may change for the current or past years after that. Rowcount for a given year is final once the Assessor has certified the assessment roll all townships. Data will be updated monthly. Depending on the time of year, some third-party and internal data will be missing for the most recent year. Assessments mailed this year represent values from last year, so this isn't an issue. By the time the Data Department models values for this year, those data will have populated. Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time. Due to discrepancies between the systems used by the Assessor and Clerk's offices, tax_district_code is not currently up-to-date in this table. There are currently two different sources of parcel-level municipality available in this data set, and they will not always agree: tax and spatial records. Tax records from the Cook County Clerk indicate the municipality to which a parcel owner pays taxes, while spatial records, also from the Cook County Clerk, indicate the municipal boundaries within which a parcel lies. For more information on the sourcing of attached data and the preparation of this dataset, see the Assessor's Standard Operating Procedures for Open Data on GitHub. Read about the Assessor's 2025 Open Data Refresh.

These parcel boundaries represent legal descriptions of property ownership, as recorded in various public documents in the local jurisdiction. The boundaries are intended for cartographic use and spatial analysis only, and not for use as legal descriptions or property surveys. Tax parcel boundaries have not been edge-matched across municipal boundaries.

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)