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)

Disclaimer: Wayne County is not responsible for the content or accuracy of the data contained in the shapefiles. The information is as of 2015, and is provided for reference only and WITHOUT WARRANTY of any kind, expressed or inferred. Please contact the local municipality if you believe there are errors in this data.

Historical PDF copy of tax maps of City of Wayne

Vector polygon map data of property parcels from New York State containing 2,789,211 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.

Additional metadata, including field descriptions, can be found at the NYS GIS Clearinghouse: http://gis.ny.gov/gisdata/inventories/details.cfm?DSID=1300.

© Contributing counties, NYS Office of Information Technology Services GIS Program Office (GPO) and NYS Department of Taxation and Finance’s Office of Real Property Tax Services (ORPTS).

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.

This data is intended as a reference material of street and alley vacations, but not designed for survey, accurate positioning, or legal documents. It is created as polygon feature class, vacation information based on field measurements, types of Right of Way, and citations of Journal of the Common Council (J.C.C.) and the plat Liber and Page is listed under the column titled 'Sub_Plat'. The paper maps of the Street and Alley Vacation, the raster layer version of those maps (Linen Map Markup Mosaic), and the Detroit parcel layer are used as base maps to create this data.

The street and alley vacations were recorded from 1831 to 2022 throughout the whole city, and it will be updated weekly. The existed and/or active street and alley vacations are ready to view, the authors are working on pending and historical records.

Spatial Reference: WGS 1984 Web Mercator Auxiliary Sphere

Historical PDF copy of tax maps of City of DearbornDisclaimer: Wayne County is not responsible for the content or accuracy of the data contained in the tax maps. The information is as of 2010, and is provided for reference only and WITHOUT WARRANTY of any kind, expressed or inferred. Please contact the local municipality if you believe there are errors in this data.

Publication Date: April 2025 2024 Parcel Data. Updated annually, or as needed. The data can be downloaded here: https://gis.ny.gov/parcels#data-download. This feature service has two layers: 1) NYS Tax Parcels Public, and 2) NYS Tax Parcels Public Footprint which contains polygons representing counties for which tax parcel polygons are available in the NYS Tax Parcels Public layer. County footprint polygons display when zoomed out beyond 1:37,050-scale. Tax parcel polygons display when zoomed in below 1:37,051-scale. The NYS Tax Parcels Public layer contains 2024 parcel data only for NY State counties which gave NYS ITS Geospatial Services permission to share this data with the public. Work to obtain parcel data from additional counties, as well as permission to share the data, is ongoing. To date, 36 counties have provided Geospatial Services permission to share their parcel data with the public. Parcel data for counties which do not allow Geospatial Services to redistribute their data must be obtained directly from those counties. Geospatial Services' goal is to eventually include parcel data for all counties in New York State. Parcel geometry was incorporated as received from County Real Property Departments. No attempt was made to edge-match parcels along adjacent counties. County attribute values were populated using 2024 Assessment Roll tabular data the NYS ITS Geospatial Services obtained from the NYS Department of Tax and Finance’s Office of Real Property Tax Services (ORPTS). Tabular assessment data was joined to the county provided parcel geometry using the SWIS & SBL or SWIS & PRINT KEY unique identifier for each parcel. Detailed information about assessment attributes can be found in the ORPTS Assessor’s Manuals available here: https://www.tax.ny.gov/research/property/assess/manuals/assersmanual.htm. New York City data comes from NYC MapPluto which can be found here: https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-mappluto.page. Thanks to the following counties that specifically authorized Geospatial Services to share their GIS tax parcel data with the public: Albany, Cayuga, Chautauqua, Cortland, Erie, Genesee, Greene, Hamilton, Lewis, Livingston, Montgomery, NYC- Bronx, NYC- Kings (Brooklyn), NYC- New York (Manhattan), NYC- Queens, NYC- Richmond (Staten Island), Oneida, Onondaga, Ontario, Orange, Oswego, Otsego, Putnam, Rensselaer, Rockland, Schuyler, St Lawrence, Steuben, Suffolk, Sullivan, Tioga, Tompkins, Ulster, Warren, Wayne, and Westchester. Geometry accuracy varies by contributing county. This map service is available to the public. The State of New York, acting through the New York State Office of Information Technology Services, makes no representations or warranties, express or implied, with respect to the use of or reliance on the Data provided. The User accepts the Data provided “as is” with no guarantees that it is error free, complete, accurate, current or fit for any particular purpose and assumes all risks associated with its use. The State disclaims any responsibility or legal liability to Users for damages of any kind, relating to the providing of the Data or the use of it. Users should be aware that temporal changes may have occurred since this Data was created.

Historical PDF copy of tax maps of City of Flat Rock

Wayne County follows a relatively fixed process for initiating tax foreclosures. The county serves notice to any parcel that is more than three years delinquent on property tax payments, and these properties are then sold to the highest bidder in two auctions - one in early September, and one in October. While there have been some exceptions to this schedule (a June 2012 auction of unsold foremost among them), properties listed in the September tax auction represent a strong proxy for identifying the universe of tax-foreclosed properties. This file identifies parcels within the City of Detroit that were listed in the September Wayne County tax foreclosure auction in any year from 2002 through 2013. It contains information on year of foreclosure, as well as the total number of times that a property has been subject to tax foreclosure. The work to produce this dataset was conducted in September 2013, and the data were subsequently integrated into the Motor City Mapping project. The purpose of this file is to help provide information on how Detroit's tax foreclosure crisis has developed over time, enabling community members and decision-makers to make more informed decisions when developing strategies to combat this growing problem. Metadata associated with this file includes field description metadata and a narrative summary detailing the creation of the dataset. For more information on the Motor City Mapping project, please visit www.motorcitymapping.org, and to learn more about the Wayne County Tax Foreclosure process, please visit this website: http://www.waynecounty.com/treasurer/783.htm.

Historical PDF copy of tax maps of City of Belleville

Historical PDF copy of tax maps of Township of RedfordDisclaimer: Wayne County is not responsible for the content or accuracy of the data contained in the tax maps. The information is as of 2010, and is provided for reference only and WITHOUT WARRANTY of any kind, expressed or inferred. Please contact the local municipality if you believe there are errors in this data.

Historical PDF copy of tax maps of City of Allen Park

Polygon vector map data covering city boundaries for City of Detroit, Michigan containing 1 feature.

Boundary GIS (Geographic Information System) data is spatial information that delineates the geographic boundaries of specific geographic features. This data typically includes polygons representing the outlines of these features, along with attributes such as names, codes, and other relevant information.

Boundary GIS data is used for a variety of purposes across multiple industries, including urban planning, environmental management, public health, transportation, and business analysis.

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.

Analysis of ‘Archival Tax Foreclosures in Detroit, 2002 - 2013’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/a9b41b43-62f7-4416-a818-f59d2ee32e39 on 28 January 2022.

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

Wayne County follows a relatively fixed process for initiating tax foreclosures. The county serves notice to any parcel that is more than three years delinquent on property tax payments, and these properties are then sold to the highest bidder in two auctions - one in early September, and one in October. While there have been some exceptions to this schedule (a June 2012 auction of unsold foremost among them), properties listed in the September tax auction represent a strong proxy for identifying the universe of tax-foreclosed properties.

This file identifies parcels within the City of Detroit that were listed in the September Wayne County tax foreclosure auction in any year from 2002 through 2013. It contains information on year of foreclosure, as well as the total number of times that a property has been subject to tax foreclosure. The work to produce this dataset was conducted in September 2013, and the data were subsequently integrated into the Motor City Mapping project.

The purpose of this file is to help provide information on how Detroit's tax foreclosure crisis has developed over time, enabling community members and decision-makers to make more informed decisions when developing strategies to combat this growing problem.

Metadata associated with this file includes field description metadata and a narrative summary detailing the creation of the dataset. For more information on the Motor City Mapping project, please visit www.motorcitymapping.org, and to learn more about the Wayne County Tax Foreclosure process, please visit this website: http://www.waynecounty.com/treasurer/783.htm.

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

Historical PDF copy of tax maps of City of HamtramckDisclaimer: Wayne County is not responsible for the content or accuracy of the data contained in the tax maps. The information is as of 2010, and is provided for reference only and WITHOUT WARRANTY of any kind, expressed or inferred. Please contact the local municipality if you believe there are errors in this data.

Property lines including the PIN, current owner(s), mailing address, and other property information

Historical PDF copy of tax maps of City of Plymouth

The dataset provided includes line data for use in geographic information systems that represents all of the standard gauge freight and passenger railroad track in North Carolina, and contains the following information: owner, operator, track type, branch, beginning milepost, ending milepost, in service status, and out of service date (where applicable). The linework was digitized based on the most recent statewide aerial photography provided by the State of North Carolina.Select areas of inactive track have been added to the dataset to aid in preserved and future corridor analysis.