GIS Map view look up parcel information including owner, taxes, market value and more.Important Mailing Label Information:The "Mailing Labels" button is is copy of the Parcels Layer and is intended to be turned OFF on the map, and is there just for the "Public Notification" Widget. This widget obtains information on the pop-up of a selected layer to create "Mailing Labels." This said, this layer contains the Owners Mailing Address information. Below is Arcaded used to customize the pop-up:Made three custom Arcade Lines below: Proper($feature["OWNER_NAM1"]) + Proper($feature["OWNER_NAM2"])Proper($feature["OWNER_ADDR"])Proper($feature["OWNER_CITY"]) + ',' + $feature["OWNER_STAT"] + ',' + $feature["OWNER_ZIP"]Below is the custom pop-up:{expression/expr0}{expression/expr1}{expression/expr2}

Webmap of Allegheny municipalities and parcel data. Zoom for a clickable parcel map with owner name, property photograph, and link to the County Real Estate website for property sales information.

This dataset is designed to represent and identify the property boundaries in Lexington-Fayette County. The original dataset was created in late 1990's by a third party that converted existing paper maps to digital GIS files. The data has since been updated by georeferencing recorded plats for corrections and new additions. In cases where the plats do not appear accurate, aerial photos are utilized in attempt to properly locate the property lines. The only except for this process are changes to highway right-of-way in which calls are run from deeds. The geometry of this data is not of survey quality and should not be used for survey purposes. The data is intended for general reference purposes only.As part of the basemap data layers, the parcel boundary map layer is an integral part of the Lexington Fayette-Urban County Government Geographic Information System. Basemap data layers are accessed by personnel in most LFUCG divisions for basic applications such as viewing, querying, and map output production. More advanced user applications may focus on thematic mapping, summarization of data by geography, or planning purposes (including defining boundaries, managing assets and facilities, integrating attribute databases with geographic features, spatial analysis, and presentation output).

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.

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

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.

The Cumberland County GIS Data Viewer provides the general public with parcel, zoning, hydrology, soils, utilities and topographic data. You can search for a specific address, street name, parcel number (PIN), or by the owner's name.

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)

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

Vector polygon map data covering property parcels from Orange County, California containing 699,877 features.

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

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

Vector polygon map data of property parcels from Los Angeles County, California containing 2,405,987 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.

Map Index Sheets from Block and Lot Grid of Property Assessment and based on aerial photography, showing 1983 datum with solid line and NAD 27 with 5 second grid tics and italicized grid coordinate markers and outlines of map sheet boundaries. Each grid square is 3500 x 4500 feet. Each Index Sheet contains 16 lot/block sheets, labeled from left to right, top to bottom (4 across, 4 down): A, B, C, D, E, F, G, H, J, K, L, M, N, P, R, S. The first (4) numeric characters in a parcelID indicate the Index sheet in which the parcel can be found, the alpha character identifies the block in which most (or all) of the property lies.

Montgomery County Parcel Data Tax Parcel shape files are available to download. Features were prepared for assessment administration purposes only. As such, the data is intended for that purpose only. Absolutely no accuracy or completeness guarantee is implied or intended. All information is subject to such variations and corrections that may result from further investigation, survey or abstract of title. Spatial Reference of Source Data: NAD 83 State Plane – New York East. Data current as of July 2024. Contact Information: Montgomery County Real Property Tax Service 20 Park Street P.O. Box 1500Fonda, New York 12068 PH: 518-853-3996 FAX: 518-853-8358 Senior Tax Mapper: Michael Burns (518)-853-3996 mburns@co.montgomery.ny.us

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)

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

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

[Metadata] Description: Tax Map Key Parcels for Hawaii County as of April, 2025. Source: County of Hawaii, May 16, 2025.State projected county layer into State"s standard projection/datum of UTM Zone 4 NAD 83 HARN and recalculated GIS_Acres field. The parcel boundaries are intended to provide a visual reference only and do not represent legal or survey level accuracy. Attributes are for assessment purposes only and are subject to change at any time. For more information, please refer to metadata at https://files.hawaii.gov/dbedt/op/gis/data/niparcels.pdf or contact Hawaii Statewide GIS Program, Office of Planning and Sustainable Development, State of Hawaii; PO Box 2359, Honolulu, Hi. 96804; (808) 587-2846; email: gis@hawaii.gov; Website: https://planning.hawaii.gov/gis.

Tax Parcel shape files, metadata, and geodatabases by town and city available to download: https://gisdata.ny.gov/GISData/County/Greene/Parcel_Data/Greene_County_Tax_Parcels.zip Database was prepared for assessment administration purposes only. It is not intended for use in the conveyance of land. Absolutely no accuracy or completeness is implied or intended. All the information is subject to such variations and corrections that may result from an accurate instrument survey and or abstract of title Spatial Reference of Source Data: NAD 83 State Plane – New York East.Spatial Reference of Web Service: WGS 1984 Web Mercator Auxiliary Sphere. Data current as of July 2025. Contact Information:Greene County Real Property Tax Service411 Main Street Suite 447Catskill, New York 12414PH: 518-719-3525FAX: 518-719-3791rpts@greenecountyny.gov

Vector polygon map data of property parcels from Harris County, Texas containing 1,410,276 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 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.