Web App. Use the tabs provided to discover information about map features and capabilities. Link to Metadata. A variety of searches can be performed to find the parcel of interest. Use the Query Tool to build searches. Click Apply button at the bottom of the tool.Query by Name (Last First) (e.g. Bond James)Query by Address (e.g. 41 S Central)Query by Locator number (e.g. 21J411046)Search results will be listed under the Results tab. Click on a parcel in the list to zoom to that parcel. Click on the parcel in the map and scroll through the pop-up to see more information about the parcel. Click the ellipse in the Results tab or in the pop-up to view information in a table. Attribute information can be exported to CSV file. Build a custom Filter to select and map properties by opening the Parcels attribute table:1. Click the arrow tab at the bottom middle of the map to expand the attribute table window2. Click on the Parcels tab3. Check off Filter by map extent4. Open Options>Filter5. Build expressions as needed to filter by owner name or other variables6. Select the needed records from the returned list7. Click Zoom to which will zoom to the selected recordsPlease note that as the map zooms out detailed layers, such as the parcel boundaries will not display.In addition to Search capabilities, the following tools are provided:MeasureThe measure tool provides the capabilities to draw a point, line, or polygon on the map and specify the unit of measurement.DrawThe draw tool provides the capabilities to draw a point, line, or polygon on the map as graphics. PrintThe print tool exports the map to either a PDF or image file. Click Settings button to configure map or remove legend.Map navigation using mouse and keyboard:Drag to panSHIFT + CTRL + Drag to zoom outMouse Scroll Forward to zoom inMouse Scroll Backward to zoom outUse Arrow keys to pan+ key to zoom in a level- key to zoom out a levelDouble Click to Zoom inFAQsHow to select a parcel: Click on a parcel in the map, or use Query Tool to search for parcel by owner, address or parcel id.How to select more than one parcel: Go to Select Tool and choose options on Select button.How to clear selected parcel(s): Go to Select Tool and click Clear.

Parcels and property data maintained and provided by Lee County Property Appraiser are converted to points. Property attribute data joined to parcel GIS layer by Lee County Government GIS. This dataset is generally used in spatial analysis.Process description: Parcel polygons, condominium points and property data provided by the Lee County Property Appraiser are processed by Lee County's GIS Department using the following steps:Join property data to parcel polygons Join property data to condo pointsConvert parcel polygons to points using ESRI's ArcGIS tool "Feature to Point" and designate the "Source" field "P".Load Condominium points into this layer and designate the "Source" field "C". Add X/Y coordinates in Florida State Plane West, NAD 83, feet using the "Add X/Y" tool.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. See https://leepa.org/Docs/Codes/DOR_Code_List.pdf


 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

Zillow Properties Listing dataset to access detailed real estate listings, including property prices, locations, and features. Popular use cases include market analysis, property valuation, and investment decision-making in the real estate sector.

Use our Zillow Properties Listing Information dataset to access detailed real estate listings, including property features, pricing trends, and location insights. This dataset is perfect for real estate agents, investors, market analysts, and property developers looking to analyze housing markets, identify investment opportunities, and assess property values.

Leverage this dataset to track pricing patterns, compare property features, and forecast market trends across different regions. Whether you're evaluating investment prospects or optimizing property listings, the Zillow Properties dataset offers essential information for making data-driven real estate decisions.

Dataset Features

• zpid: Unique property identifier assigned by Zillow.
• city: The name of the city where the property is located.
• state: The state in which the property is located.
• homeStatus: Indicates the current status of the property
• address: The full address of the property, including street, city, and state.
• isListingClaimedByCurrentSignedInUser: This field shows if the current Zillow user has claimed ownership of the listing.
• isCurrentSignedInAgentResponsible: This field indicates whether the currently signed-in real estate agent is responsible for the listing.
• bedrooms: Number of bedrooms in the property.
• bathrooms: Number of bathrooms in the property.
• price: Current asking price of the property.
• yearBuilt: The year the home was originally constructed.
• streetAddress: Specific street address (usually excludes city/state/zip).
• zipcode: The postal ZIP code of the property.
• isCurrentSignedInUserVerifiedOwner: This field indicates if the signed-in user has verified ownership of the property on Zillow.
• isVerifiedClaimedByCurrentSignedInUser: Indicates whether the user has claimed and verified the listing as the current owner.
• listingDataSource: The original source of the listing. Important for data lineage and trustworthiness.
• longitude: The longitudinal geographic coordinate of the property.
• latitude: The latitudinal geographic coordinate of the property.
• hasBadGeocode: This indicates whether the geolocation data is incorrect or problematic.
• streetViewMetadataUrlMediaWallLatLong: A URL or reference to the Street View media wall based on latitude and longitude.
• streetViewMetadataUrlMediaWallAddress: A similar URL reference to the Street View, but based on the property’s address.
• streetViewServiceUrl: The base URL to Google Street View or similar services. Enables interactive visuals of the property’s surroundings.
• livingArea: Total internal living area of the home, typically in square feet.
• homeType: The category/type of the home.
• lotSize: The size of the entire lot or land the home is situated on.
• lotAreaValue: The numerical value representing the lot area is usually tied to a measurement unit.
• lotAreaUnits: Units in which the lot area is measured (e.g., sqft, acres).
• livingAreaValue: The numeric value of the property's interior living space.
• livingAreaUnitsShort: Abbreviated unit for living area (e.g., sqft), useful for compact displays.
• isUndisclosedAddress: Boolean indicating if the full property address is hidden, typically used for privacy reasons.
• zestimate: Zillow’s estimated market value of the home, generated via its proprietary model.
• rentZestimate: Zillow’s estimated rental price per month, is helpful for rental market analysis.
• currency: Currency used for price, Zestimate, and rent estimate (e.g., USD).
• hideZestimate: Indicates whether the Zestimate is hidden from public view.
• dateSoldString: The date when the property was last sold, in string format (e.g., 2022-06-15).
• taxAssessedValue: The most recent assessed value of the property for tax purposes.
• taxAssessedYear: The year in which the property was last assessed.
• country: The country where the property is located.
• propertyTaxRate: The most recent tax rate.
• photocount: This column provides a photo count of the property.
• isPremierBuilder: Boolean indicating whether the builder is listed as a premier (trusted) builder on Zillow.
• isZillowOwned: Indicates whether the property is owned or managed directly by Zillow.
• ssid: A unique internal Zillow identifier for the listing (not to be confused with network SSID).
• hdpUrl: URL to the home’s detail page on Zillow (Home Details Page).
• tourViewCount: Number of times users have viewed the property tour.
• hasPublicVideo: This

Analysis of ‘OC Land Use 2007’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/e1c17acd-2569-45c2-b7f0-0489589c07fe on 28 January 2022.

--- Dataset description provided by original source is as follows ---

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE.

--- Original source retains full ownership of the source dataset ---

Approximate boundaries for all land parcels in New Brunswick. The boundaries are structured as Polygons. The Property Identifier number or PID is included for each parcel.

This parcel data represents pacels of land in Jamaica together with their Parish, Folio number, aproximate area, and other useful statistics. It is a subset of the full dataset and only contains records for St. Andrew.

We plan to update this dataset. Please visit the NLA website for further information.

In 2023, about 886,391 offenders in the United States were arrested for a property crime. This is a significant decrease from 1990 levels, when about 2.22 million people were arrested for property crimes in the country.

DATA SOURCES:

1. ONLY state sources (city/county/state administration, federal agencies, ministries, etc.). We DO NOT use unverified databases
2. Over 2300 sources. We use even the smallest sources, because they contain valuable data. This allows us to provide our users with the most complete data

DATA RELEVANCE:

1. Our data is updated daily, weekly, monthly depending on the sources
2. We collect, process and store all data, regardless of their relevance. Historical data is also valuable

DATA TYPES:

1. Specifications
2. Owners
3. Permits
4. Sales
5. Inspections
6. Violations
7. Assessed values
8. Taxes
9. Risks
10. Foreclosures
11. Property Tax Liens
12. Deed Restrictions

NUMBERS:

1. 2300 data sources in total
2. 155,000,000 properties in total
3. 4 billion records (listed in the "data types" block above) in total
4. 2 million new records every day

DATA USAGE:

1. Property check, investigation (even the smallest events are stored in our database)
2. Prospecting (more than 100 parameters to find the required records)
3. Tracking (our data allows us to track any changes)

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

This dataset contains the parcels, parcel number and districts from the existing data model ALKIS. They have been transformed into the INSPIRE target model. In the official property cadastre information system (ALKIS®) all data of the property cadastre are merged and maintained integrated. This means that data from the former property map, the former property register and the border certificate are included in ALKIS. The basis for ALKIS® is a technical concept developed by the Association of Surveying Administrations of the Länder of the Federal Republic of Germany (AdV) for the management of all basic data of official surveying (see reference). All federal states have undertaken to maintain an ALKIS basic database according to this concept. In addition, there are country-specific additional data according to the data model.

This record contains selected data: Land parcels, land parcel number, districts

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.

This dataset represents the boundary of each parcel of land in Fulton County recorded for the purpose of aiding in the appraisal of real property and the determination of property tax. A parcel dataset is created each year in association with that year's tax digest. The parcel dataset for any given year is not considered final until the completion of the digest, which generally occurs around mid-year. Until the completion of the digest, the parcel dataset is considered to be a work in progress. Any necessary corrections and omissions may continue to be made even after the completion of the digest. The parcel dataset in its published form incorporates information from the CAMA (computer-aided mass appraisal) database. The CAMA information included with the published dataset is selected based on its value to the typical consumer of the data and includes the parcel identification number, the property address, property owner, owner's mailing address, tax district, assessed and appraised value for land and improvements, the number of livable units, acreage, property class and land use class. The information in this data set represents the completed 2023 digest.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE.

A spatial representation of land use. The polygons contained in this feature class were derived from the Oakland County Tax Parcel feature class. Each parcel was categorized by its land use. When a parcel has multiple land uses, the dominant land use is shown. Assessing records and orthophotography were the main sources used to attribute each tax parcel with land use information. The data was collected in 2016. Key attributes are the land use and key pin (Sidwell number). Land Use stores the Land Use description for each parcel. The Key Pin is the unique Parcel Identification Number (Pin) used to link the parcel to the parcel attributes which are stored and maintained in Oakland County Land Records.

The Inventory of Owned and Leased Properties (IOLP) allows users to search properties owned and leased by the General Services Administration (GSA) across the United States, Puerto Rico, Guam and American Samoa. The Owned and Leased Data Sets include the following data except where noted below for Leases: Location Code - GSA’s alphanumeric identifier for the building Real Property Asset Name - Allows users to find information about a specific building Installation Name - Allows users to identify whether a property is part of an installation, such as a campus Owned or Leased - Indicates the building is federally owned (F) or leased (L) GSA Region - GSA assigned region for building location Street Address/City/State/Zip Code - Building address Longitude and Latitude - Map coordinates of the building (only through .csv export) Rentable Square Feet - Total rentable square feet in building Available Square Feet - Vacant space in building Construction Date (Owned Only) - Year built Congressional District - Congressional District building is located Senator/Representative/URL - Senator/Representative of the Congressional District and their URL Building Status (Owned Only) - Indicates building is active Lease Number (Leased Only) - GSA’s alphanumeric identifier for the lease Lease Effective/Expiration Dates (Leased Only) - Date lease starts/expires Real Property Asset Type - Identifies a property as land, building, or structure

Description

The PARCELS layer depicts mapped land parcels or real estate properties within Chester County. This data contains geometric representations capturing the general size, shape and location for all of the real estate properties, which can be mapped, on the County's land surface.

ContactsTim Cassel, County of Chester

Tcassel@chesco.org, 610-344-5441, 313 W. Market St Suite 5302 West Chester, PA 19380ResourceUpdate frequency of dataset: Weekly Last Update Date: August 2023Accuracy of attribute: Attributes are correct as per County of Chester Assessment DepartmentPositional accuracy of dataset:The PARCELS layer (and derived copies PARCEL_PUBLISH and PRCL_POLY) was originally created through a conversion process of digitizing hand drawn tax maps into digital form and orientating the tax map sheets and parcels to the features depicted in the 1993 orthophotos. These parcel polygon features were adjusted based on aerial photography dated April 7, 1993, and road centerlines, right-of-way lines and other physical features generated from the same photography. While the imagery has a pixel resolution of 1.5 square feet, a positional accuracy of +/- 5 feet and is designed for use at a scale of 1 inch = 200 feet, the resulting PARCELS horizontal accuracy varies from reasonably accurate in the best cases to less accurate in the worst cases. Subsequent and current map update processes include metes and bounds entry from subdivision and deed information, as well as property corner locations based on GPS points and the utilization of our newest imagery datasets. While the update processes include more accurate methods, the resultant overall accuracy is still dependent on the surrounding parcel fabric's varied accuracy. Planimetric coordinates are based on the Pennsylvania State Plane Coordinate System South Zone and North American Datum 1983 Spatial ReferenceType: ProjectedGeographic Coordinate Reference: GCS North America 1983Projected Coordinate System: NAD 1983 State Plane Pennsylvania SouthLinear Unit: US Survey Feet

Note: There is a difference between land use code and zoning. Land management occurs via a land use designation which determines the land use code. This designation specifies how land and resources within it is managed. Zoning designations define how a property can be developed and used and it is controlled by each township/borough. See below for list of codes.Field DescriptionUPI - Uniform Parcel Identification Number, a unique value given to each parcelPIN_MAP - A Tie-back parcel identification number used to link UPI values to the parcel on which they residePIN_COMMON - A variation of UPI which adds and E for Exempt, U for Utility or T for TrailerPIN_ASMNT - A long form of the UPI number used for assessment purposesCODE (see below for list of codes)MULTI_POLY - Number listing for each parcel of a Multi-Poly parcel. (Example 1 of 20, 2 of 20)POLY_PER_PARCEL - Number of polygons that make up a parcel (0 indicates it is just one polygon)SQFT_PLAN_TOT - The square footage of a parcel (taken from the recorded plan or deed)ACRE_PLAN_TOT - The acreage of a parcel (taken from the recorded plan or deed)ACRE_PLAN_POLY - The acreage of the polygon depicting the parcel, derived by mapping softwareXCOORD - X coordinate of the centroid of the polygonYCOORD - Y coordinate of the centroid of the polygonLOC_ADDRESS - The location address for a parcelMUNI - The municipality the parcel resides inST_NUM - Street Number of the Situs AddressNUM_SUF - Street Number Suffix of the Situs AddressDIR - Street directional of the Situs Address (N, E, S, W)ST_NAME - Street Name of the Situs AddressST_TYPE - Street thorough fair type of the Situs AddressUNIT - Unit Type (see codes below)UNIT_N - Unit numberAD_ROLE - Situs Address Functional Role (see below for list of codes)NO_ADDR_CODE - No longer usedTILE_1200 - Outdated reference system, no longer usedTILE_2400 - Outdated reference system, no longer usedSUBDIV_NUMBER - Number assigned by Recorder of Deeds to a recorded documentLOT - Lot number given to parcel on the recorded planLAND_DEV_ID - Number assigned by Planning Commission for their tracking purposesCREATE_DATE - Date the parcel was mapped into the inactive parcel layerACTIVE_DATE - Date the parcel was added to the active parcel layerOWN1 - Owner of recordOWN2 - Owner of record if more than oneADDR1 - Component of the mailing address on recordADDR2 - Component of the mailing address on recordADDR3 - Component of the mailing address on recordZIP1 - Zipcode of mailing address on recordTAXYR - For Assessment purposesJURIS - Municipality Number where parcel is taxedBOOK - The book number of the recorded deedPAGE - The page number of the recorded deedDEED_REC_DATE - Date the latest deed was recordedLEGAL1 - Description of property location according to the deedLEGAL2 - Description of the taxable property and buildings according to the deedLUC - Landuse code assigned by assessment office. (unrelated to municipal zoning of a parcel) ((see below for list of codes))CLASS - General landuse classification assigned by assessment office (see below for list of codes)LOT_ASSESS - Assessed value of the landPROP_ASSESS - Assessed value of the structuresTOT_ASSESS - Assessed value of the combination of land and structuresFMV319 - Fair Market Value if not under 319FMV515 - Fair Market Value if not under 515LAST_SALE_PRICE - Last recorded sale priceASMNT_DATE - For Assessment Department use onlySCHDIST - The school district within which the parcel resides (see below for list of codes)SUBDIV_NAME - Name of the recorded planPLAN_NUM - Number assigned by the Planning Commission for their tracking purposesMODIFY_DATE - Last edit date of the parcel Data Dictionary Code1000= Parcel1010= Condominium (mother or host parcel)1011= Common Law Condo1020= Hydrography1031= Paper ROW1033= Land polygon with a ROW1034= Land dedicated to an existing ROW1035=- Private Road1040= Open Space1042= Common Area1043= Open Space owned by Homeowners Association1710= Parcel Assessed in Lancaster County but located in Chester County1711= Parcel Assessed in Berks County but located in Chester County1712= Parcel Assessed in Montgomery County but located in Chester County1713= Parcel Assessed in Delaware County but located in Chester County1714= Parcel Assessed in New Castle County but located in Chester County1715= Parcel Assessed in Cecil County but located in Chester County2000= Parcel bisected by a ROW (Duplicate Pin)2040= Open Space (Duplicate Pin)2042= Common Area (Duplicate Pin)2043= Open Space owned by Homeowners Association2010= Condominium (Duplicate Pin) LUCC-10= Banks, Savings&LoanC-20= Gas StationC-30= Restaurants, Stores (Retail)C-35= Condominium StoresC-40= Motels, HotelsC-41= Nursing HomesC-50= Shopping CentersC-60= Office Bldgs/Laboratory/LibraryC-65= Office CondoC-67= Office Condo Common LawC-70= Commercial Garage/Shop/Car DealersC-80= WarehouseC-81= Storage TanksC-90= Entertainment, RecreationC-91= Recreation (Private)C-92= Mobile Home Parks (4+)C-93= Burial Grounds/MausoleumC-94= AirportsC-95= Private SchoolsC-96= Commercial OBY onlyE-10= ChurchesE-11= CemetariesE-12= Service ConnectedE-13= Chester County PropertyE-20= SchoolsE-30= Public UtilitiesE-40= RailroadsE-50= Hospitals, etcE-60= StateE-61= State ParksE-62= FederalE-63= FederalE-70= Local Government (Townships & Boroughs)E-71= Local Government ParksE-80= Non-Profit OrganizationsE-90= Fire CompaniesF-10= Farm 10-19.99 AcresF-20= Farm 20-79.99 AcresF-40= Farm 80 Acres and overM-10= Heavy IndustrialM-20= Light IndustrialM-25= Light Industrial CondominiumM-30= Quarry/LandfillN-01= Not assessed in Chester CountyR-10= Single Family/CabinR-20= Two FamilyR-30= Multi Family/Dorms/SingleR-40= Apartments (4-19 Units)R-50= CodominiumR-55= Town House (Common Law Condo)R-60= Dwelling W/Comm Use Primary RR-61= Dwelling W/Comm Use Primary CR-70= Mobile HomeR-80= Barns, Stables, Pools, Misc BldgR-90= Apartment Complex (20 or more units)R-95= Common Elements (Not Open Space)T-10= Trailers and Mobile HomesU-03= Public UtilitiesU-04= RailroadsV-10= Vacant Land ResidentialV-11= Vacant Land CommercialV-12= Open SpaceV-13= Road Beds, Right of Way, Access WayV-14= Basins, Drainage ControlV-35= Condo Store/Vacant Common ElementV-50= Condo/Vacant Common ElementV-55= Condo Common Law/Common AreaV-65= Condo Office/Vacant Common ElementV-67= Condo Common Law Office/Common AreaClassA= ApartmentC= CommercialE= ExemptF= FarmI= IndustrialR= ResidentialU= Utility

SchDist1= Avon Grove2= Coatesville3= Downingtown4= Kennett Consolidated5= Octorara6= Owen J. Roberts7= Oxford8= Phoenixville9= Twin Valley10= Unionville Chaddsford11= West Chester12= Great Valley13= Tredyffrin-Easttown14= Springford

State of Alaska tax parcel data by authoritative data source. This map is for use within the Alaska Geospatial Council Cadastre Technical Working Group's Hub site.

This feature class combines Parcel geography information with land ownership data from the city's Computer Aided Mass Appraisal (CAMA) system. In instances of multiple ownership records (PINs) for one parcel feature, each parcel will be duplicated or "stacked."Nomenclature:cads_- short for "cadastral" - the prefix used to identify GIS data related to property and property assessment.Parcel- each geometry is a single parcel feature.Asr- short for Assessor.View- This feature class is generated from a SQL spatial view of property records and parcel geometry.The schema definition of the feature class is as follows:ParcelID - UniqueID for a Parcel.PIN - Property Identification Number.CountOfPIN - Number of PIN values per parcel.OwnerName - Name of the property owner.AsrLocationBldgNo - Address number of the property.MailAddress - Property Owner mailing address.MailCity - Property Owner mailing address city.MailState - Property Owner mailing address state.MailZip - Property Owner mailing address Zip Code.AssessmentDate - Date of the last property assessment.LandValue - Total valuation of the land.DwellingValue - Total valuation of the dwelling.TotalValue - LandValue + DwellingValue. Total value of the property.LandSqFt - Square footage of the land.ProvalAsmtNhood - The "Assessment Neighborhood" code that city of Richmond property assessors use to identify distinct neighborhoods. Proval is the name of the city's CAMA system.TaxExemptCode - Tax-exempt property code, if applicable.PropertyClassID - City property class code.PropertyClass - City property class name. Corresponds to PropertyClassID.LandUse - Land use.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpageunder 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, OtherSalt Lake County Tax Exempt codes below:AE - Airport - ExemptCC - Commercial Common AreaCE - Conservation EasementCM - CemeteryEC - Exempt CharitableEE - Exempt EducationER - Exempt ReligiousGB - GreenbeltHE - Homeowners Assoc ExemptIL - In LieuIR - Irrigation CompanyMC - Master CardOE - Owner ExemptPE - Part ExemptPR - Pro-RatedPT - Privilege TaxPY - Privilege Tax on a YieldSA - State AssessedSC - State and Cnty AssessedSE - Special - ExemptSU - Salt Lake - Utah CntyTD - Divided Tax DistrictUI - Undivided_Interest TAX_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. ResidentialSalt Lake County Property Class codes below:R - Residential / CondoC - CommercialI - IndustrialRE - RecreationalA - AgriculturalMH - Multi HousingMore information about the PROP_CLASS and PROP_TYPE for Salt Lake County can be found at http://slco.org/assessor/new/queryproptyp.cfmPROP_TYPE (expected) Text 100 - Single Family Res.,Townhome, CondoPRIMARY_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)