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)

Geospatial data about Wayne County, Michigan Parcels. Export to CAD, GIS, PDF, CSV and access via API.

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

Historical PDF copy of tax maps of City of Dearborn

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 Belleville

Historical PDF copy of tax maps of City of Westland

Historical PDF copy of tax maps of City of Taylor

Historical PDF copy of tax maps of City of Plymouth

Historical PDF copy of tax maps of City of Flat Rock

The feature class Wayne County Commision Districts is created by Wayne County to show the boundaries of each of the fifteen commisioner districts in Wayne County. The current districts are based on the 2010 census. They were effective for the November 2012 election for the two-year term that started Jan. 1, 2013. The districts are adjusted every 10 years.The file also includes the name of the commissioner for each district at the time of publication. Further information on the Wayne County Commision and Commissioners can be found on their website, http://www.waynecounty.com/commission/index.htm.Metadata available for download here.

A web map used to access tax parcel, boundary, ownership, acreage, survey, zoning and tax information. Errors and Omissions Do Exist.The information provided is for reference only and subject to independent verification. User assumes all responsibility for its use.https://www.fayette-co-oh.com/Fayette County ProfileFayette County is a county located in the U.S. state of Ohio. Its county seat is Washington Court House. Fayette County was formed on March 1, 1810 from portions of Highland County and Ross County. It was named after Marie-Joseph Motier, Marquis de La Fayette, a French general and politician who took the side of the Colonials during the American Revolutionary War and who played an important role in the French Revolution.Fayette County is a part of the Virginia Military survey, which was reserved in 1783, to be allotted to Virginia soldiers. This district includes the entire counties of Adams, Brown, Clermont, Clinton, Highland, Fayette, Madison and Union; and a portion of the counties of Scioto, Pike, Ross, Pickaway, Franklin, Delaware, Marion, Hardin, Logan, Champaign, Clarke, Greene, Warren and Hamilton.Fayette County was formed January 19, 1810 (took effect March 1st) from Ross and Highland counties. Beginning at the southwest corner of Pickaway, running north “with the line of said county to the corner of Madison; thence west with the line of said Madison county to the line of Greene county; thence south with the line of Greene county to the southeast corner thereof; thence east five miles; thence south to the line of Highland county; thence east with said line to Paint Creek; thence in a straight line to the beginning.” All the lower portion was taken from Highland and the upper from Ross.The first portion of land entered within the territory of what is now Fayette county, was a part of original surveys Nos. 243 and 772, lying partly in Clinton county. The first survey lying wholly within Fayette county was No. 463, in what is now Madison township, surveyed for Thomas Overton by John O’Bannon June 30, 1776.The original townships were Jefferson, Greene, Wayne, Madison, Paint and Union. Concord township was formed in April 1818, from Greene. Marion township was formed in June, 1840 from Madison. Perry township was formed June 4, 1845, from Wayne and Greene. Jasper township was formed from Jefferson and Concord December 2, 1845.Washington C.H. was laid out originally on a part of entry 757, which contained 1200 acres and belonged to Benjamin Temple, of Logan county, Kentucky, who donated 150 acres to Fayette county, on condition that it be used as the site of the county seat. The deed of conveyance was made December 1, 1810, by Thomas S. Hind, attorney for Temple, to Robert Stewart, who was appointed by the legislature as director for the town of Washington. The town was laid off some time between December 1, 1810, and February 26, 1811, the latter being the date of the record of the town plat.Bloomingburg (originally called New Lexington) was laid out in 1815, by Solomon Bowers, and originally contained 34 and ¾ acres. On March 4, 1816, Bowers laid out and added twenty more lots. The name of the town was later changed to Bloomingburg by act of the legislature. The town was incorporated by act of the legislature, February 5, 1847.Jeffersonville was laid out March 1, 1831, by Walter B. Write and Chipman Robinson, on 100 acres of land belonging to them, they started selling the lots at $5 each. The town incorporated March 17, 1838. The first house was erected by Robert Wyley.The first railroad, now the C. & M. V., was completed in 1852; the second, now the Detroit Southern, in 1875; the third, now the C.H. & D. in 1879; and the fourth, now the B. & O. S. W., in 1884.The first permanent settler (probably) was a Mr. Wolf who settled in what is now Wayne township, in about the year 1796. - Circa 1886 - Map of Fayette County, Ohio. Issued by the Fayette County Record.

This dataset consists of a map depicting the landcover of the Natchez Trace Parkway. The mapping output was created using mosaiced color infrared aerial photography of the Parkway. The map shows the distribution of 18 landcover classes based on the National Vegetation Classification Standard. Ground-based vegetation classification was provided by the National Park Service (NPS). The mapping output delineates grasses, road-developed areas, scrub-shrub, shrubland, plantation, water bodies, areas of white oak, oak, pine-oak, pine-cedar, pine-sweetgum, sweetgum (including sweetgum-oak), scattered trees, swamp forest, irregular classes, aquatic vegetation, invasive species, canopy gaps, and clouds.

Total mapped area includes a 100 m buffer outside the park boundary. 235 digital orthophoto quarter quadrangles (DOQQs) were required to cover the entire 715 km long Parkway. For ease of use, the DOQQs were grouped into 11 mosaics, each covering a section of the Parkway. At the request of the NPS, each mosaic was divided into ten tiles to allow for efficient loading on less robust computers.

Historical PDF copy of tax maps of City of Southgate

Historical PDF copy of tax maps of City of River Rouge

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information