This file identifies likely public ownership based on several categorizations. These include the City of Detroit, the Detroit Land Bank Authority, the Michigan Land Bank Fast Track Authority, the State of Michigan, Wayne County, the United States Government, the Detroit Water and Sewerage Department, and Detroit Public Schools. The ownership information generally dates from 2013 to early 2014; see the field description metadata for further information.DISCLAIMER: This file seeks to identify parcels that are owned by a governmental or other public entity. However, ownership of properties changes frequently, particularly between public entities, and the data sources that this file is built from date from 2013 through the spring of 2014. Since there has been considerable time for the ownership of some of these properties to change, D3 is producing this file as an indicator of Likely Public Ownership.This file is intended to help highlight the breadth and scale of public ownership in the City of Detroit, and any decisions based off of this file should be confirmed through investigating legal ownership records.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.

This layer is a reproduction of the non-motorized transportation projects that have been completed, are in progress or in planning as issued by the City of Detroit Department of Public Works - Traffic Engineering Division as of 2014.

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.

This data is intended as a reference material of street and alley openings, but not designed for survey, accurate positioning, or legal documents. It is created as polygon feature class, dedicated information based on field measurements, types of Right of Way, and citations of Journal of the Common Council (J.C.C.) and legal description are included. The paper maps of the Street and Alley Openings, 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 spatial reference is: WGS 1984 Web Mercator Auxiliary SphereThe street and alley openings were recorded from 1831 to 2022 throughout the whole city, and it will be updated weekly. The existed and/or active street and alley openings are ready to view, the authors are working on missing and historical records.Note: Special values within the 'Jurisdiction' field:"2" means that the feature was approved under Wayne County or the State of Michigan jurisdiction, No City record on file. "1" means that the feature was approved under City of Detroit jurisdiction."0" means the feature was approved per circuit court decision. No City record on file.

Historical PDF copy of tax maps of City of RiverviewDisclaimer: 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.

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)

Historical PDF copy of tax maps of City of Lincoln Park

Historical PDF copy of tax maps of City of Dearborn

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 Grosse Pointe WoodsDisclaimer: 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 Wyandotte

Historical PDF copy of tax maps of City of Taylor

Historical PDF copy of tax maps of City of Inkster

Historical PDF copy of tax maps of City of River RougeDisclaimer: 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 Northville

Historical PDF copy of tax maps of City of PlymouthDisclaimer: 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.

Click here for metadata (descriptions of the fields).

Historical PDF copy of tax maps of City of Romulus

Historical PDF copy of tax maps of City of Dearborn Heights

Historical PDF copy of tax maps of City of Harper Woods