Online mapping application showing parcels in Eaton County, Michigan, USA. Parcels are not currently survey-grade and are useful only as a general reference. For important decisions regarding property lines, a land surveyor should be consulted.

Oakland County's public-facing parcel viewer. Oakland County staff and CVTs can request free accounts by contacting the Oakland County Service Center (servicecenter@oakgov.com, 248-858-8812).

More information about the products available in Property Gateway can be found here: https://www.oakgov.com/propertygateway/Pages/default.aspx.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE.
A spatial representation of Tax Parcels. Key attributes include KeyPIN. The KeyPIN is the unique parcel identification number used to link the tax parcel to the parcel attributes which are stored and maintained in Oakland County land records.

There is no definite accuracy related to parcel boundaries. The information shown on these maps is for representation purposes only and is not intended to be a legally recorded map or survey. The information was compiled from a number of sources including recorded deeds, plats, tax maps surveys and other public records and data. Users of this data should consult the information sources listed above for verification of the information.

Property Gateway is a leading-edge Internet tool built to provide free and fee-based online access to Oakland County's land and property information including tax parcel reports and maps. Reports and maps can be purchased via a credit card transaction; recurring users request a business account. Visit Property Gateway, HERE.

This shapefile contains tax parcel polygons for Eaton County, Michigan, USA. Because tax parcel information changes daily, this shapefile contains only geometry, the parcel identifier and a URL link to the current information for each parcel. Parcel geometries are not survey-grade and should not be used to make important decisions like where to build a structure or install a fence. In their current form, they are only useful in spatial terms for getting an inexact idea of where a parcel is located. If you need to know exactly where a property line falls, please consult a certified land surveyor. Parcel geometries will be updated either annually or bi-annually. New splits and combinations are typically not visible in the parcel geometry until changes become official via Board of Review in the following April.

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

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

This map application shows tax parcel boudaries for Eaton County, Michigan. The ownership details are updated weekly and the parcel geometries are updated on an annual basis in late spring.The tax parcel boundaries depicted herein are a working representation derived from recorded property descriptions. Eaton County endeavors to maintain and publish accurate parcel boundary information using current methods and technology; however, these data are derivative in nature and may contain errors or omissions.Accordingly, these parcel boundaries are provided for reference purposes only and should not be relied upon as the sole basis for making financial, legal, or other significant decisions. Users are strongly advised to consult the original recorded documents and/or appropriate professionals for verification prior to relying on this information.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE. A spatial representation of parcel history. This polygon feature class is created and maintained through the use of a customized tool for parcel maintenance management. As parcel splits and combinations create child parcels, the parent parcels are saved out to the parcel history feature class. Retired tax parcels have been maintained since 1998. Right of way and alley vacations are also maintained in this feature class. Vacations have been maintained since Spring, 2005. The key attributes include parcel identification number (KeyPIN) and the creation date (RevisionDate).

The Digital Geologic-GIS Map of Natural Bridges National Monument, Utah is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (nabr_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (nabr_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (nabr_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (nabr_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (nabr_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (nabr_geology_metadata_faq.pdf). Please read the nabr_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Michigan Technological University. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (nabr_geology_metadata.txt or nabr_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

The Digital Geologic-GIS Map of Isle Royale National Park and Vicinity, Michigan is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (isro_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (isro_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (isro_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (isro_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (isro_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (isro_geology_metadata_faq.pdf). Please read the isro_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (isro_geology_metadata.txt or isro_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THETERMS OF USE.A spatial representation of land use. The polygons contained in this feature class were derived from the Oakland County Tax Parcel feature class. Each parcel was categorized by its land use. When a parcel has multiple land uses, the dominant land use is shown. Assessing records and orthophotography were the main sources used to attribute each tax parcel with land use information. The data was collected in 2011. Key attributes are the land use and key pin (Sidwell number). Land Use stores the Land Use description for each parcel. The Key Pin is the unique Parcel Identification Number (Pin) used to link the parcel to the parcel attributes which are stored and maintained in Oakland County Land Records.The 2011 version of land use was created using the 2010 version as a primary source. It was assumed that if the Parcel Identification Number and the Use Code were equal in both years, then the land use did not change. Thus, only the parcels where a change occured had to be assigned a land use. To ensure the quality of the land use data, however, several types of use codes were manually checked again for this update to enusre the assigned use is still accurate. Also, reference data such as the Adult Care, Public Beach, and Recreation Land feature classes the were used to locate misrepresented parcels.The development process consists of three basic steps. First, parcels with use codes that are assumed to relate to a single land use are categorized as such. Second, parcels with a use code that is assumed to relate to more than one land use are manually classified using orthophotography and ownership as a reference. Lastly, tax parcels, right-of-way, and hydrography are unioned to create a single land use dataset.Assumptions:In 2005, Oakland County Equalization and many of the local assessors have changed from using the use codes described below to property class codes. These codes were interpreted to simliar use codes for the purpose of this data. One major change is that tax exempt property is no longer recorded using the "ME, Miscellaneous Exempt" use code, but are instead usually classifed as "RV, Residential Vacant." The "Taxable" field was referenced to locate tax exempt property such as schools, churches, and governemnt-owned property during this land use update.Any parcel classified as vacant may be an accessory use to an adjacent, commonly owned, improved parcel. In this event, the vacant parcel is reclassified as the use of the adjacent, commonly owned, improved parcel. It should be noted, however, that parcels with use codes of RV, SV, and LV, that represent a single family vacant use, are exempt from this assumption.Parcels with an Equalization use code of RV, SV, or LV may include uses to be reclassified as Vacant or Recreation & Conservation (due to subdivision open space). These parcels are not manually checked. Queries are conducted to search for those parcels that are subdivision open space. The following strings are queried from the Owner1 and Owner2 fields: "*own*" (unknown, homeowner), "ass*" (association, ass'n, etc), and "park."The Equalization use code BI, Business Improved includes uses that are reclassified as Commercial/Office. Uses may also fall into Public/Institutional, however, all BI parcels are not manually checked for reclassification.The Equalization use code MM, Miscellaneous Business includes uses that are reclassified as Recreation and Conservation, Multiple Family, Commercial/Office, or Mobile Home Park.The Equalization use code ME, Miscellaneous Exempt includes uses that are reclassified as Recreation & Conservation, Public/Institutional, Transportation, Utility & Communication, Industrial (municipal landfills), or any Single Family classification.The Equalization use code KI, Condominium Improved includes uses that are reclassified as Multiple Family, Single Family, or Commercial/Office. Any parcel with an Equalization use code of FI, Farm Improved or FV, Farm Vacant is considered to be an active agricultural use.Any parcel with an Equalization use code of II, Industrial Improved is considered to be an industrial use.Any parcel with an Equalization use code of FC, Farm Conservation is considered to be a recreational/conservation use.Any parcel with an Equalization use code of AI, Apartment Improved is considered to be a multiple family residential use.Any parcel with an Equalization use code of UI, Utility Improved is considered to be a transportation, utility, or communication related use.Parcels with an Equalization use code of DI, Developmental Improved are reclassified as Single Family or Vacant.Any parcel with an Equalization use code of DV for Developmental Vacant may be reclassified as Vacant, Recreation & Conservation, (golf courses) or Industrial (mining or extractive).Polygons in the ROW region of the parcel coverage will be classified as Recreation and Conservation, and Commercial/Office, Vacant, Road ROW, and Railroad ROW.Because of inconsistencies in Use Code data, unique uses, and the goal of creating an accurate coverage that is not limited by its metadata, there may be exceptions from these assumptions.Exceptions:There are nine isolated cases where the land use would be tremendously overstated if the whole parcel was shown in a single use. In these cases, the polygon was split to show the use of the rest of the parcel vacant. These parcels are listed below: 01-29-451-001 01-35-300-014 04-08-200-002 04-24-100-004 07-13-301-006 14-04-376-002 18-19-476-015 21-10-200-001 21-10-200-002

In 2009, Data Driven Detroit partnered with Living Cities, the Detroit Office of Foreclosure Prevention and Response and Community Legal Resources (Michigan Community Resources) to conduct a survey of 1-4 unit residential structures and vacant lots in the City of Detroit. Surveyors went out in the field in August and September of 2009, and following this, data were entered into a database and cleaned. The survey collected information on property type, condition, vacancy, danger to the surrounding community, fire damage, and improvements on vacant lots.For more information on the DRPS, including aggregations and maps of the original data, please visit www.detroitparcelsurvey.org.Upon request, field description metadata is also available for this dataset.

The Digital Bedrock Geologic-GIS Map of Keweenaw National Historical Park and Vicinity, Michigan is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (kewe_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (kewe_geology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (kewe_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (kewe_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (kewe_geology_metadata_faq.pdf). Please read the kewe_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (kewe_geology_metadata.txt or kewe_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

The Office of the Assessor compiles property sales data to perform an annual property sales study to adjust calculated costs of property values based on local market conditions. This dataset includes property sales data obtained for annual sales studies from 2018 to the present. While only Valid Arm's Length transactions that occurred in the two years prior to when a given sales study is finalized are included in each study, this dataset includes all sales transactions obtained to perform the sales studies, whether or not the sales transactions met inclusion criteria for a study. More information about the Sales Study is available from the Office of the Assessor.Values in categorical fields such as 'Sales Instrument' are recorded based on State of Michigan CAMA standards at the time the value was recorded. Some variation in field value codes occurs over time as a related CAMA standard is updated. CAMA standards are available from the State of Michigan Department of Treasury State Tax Commission.Click here for the Analytics Hub visualization of Property Sales.

The Digital Surficial Geologic-GIS Map of Pictured Rocks National Lakeshore and Vicinity, Michigan is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (piro_surficial_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (piro_surficial_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (piro_surficial_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (piro_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (piro_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (piro_surficial_geology_metadata_faq.pdf). Please read the piro_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Western Michigan University. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (piro_surficial_geology_metadata.txt or piro_surficial_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE. The DevelopmentAuthority polygon feature class identifies certain types of entities that encourage development/redevelopment in designated areas. This feature class currently represents Downtown Development Authorities (DDA), Tax Increment Finance Authorities (TIFA), and Local Development Finance Authorities (LDFA); however, it will also depict Corridor Improvement Authorities (CIA) and Brownfield Redevelopment Authorities (BRA) in the future. These five types of authorities have the ability to capture tax increment financing (TIF). The features were digitized using legal descriptions, parcel lists, and maps that were provided to the State of Michigan Office of the Great Seal and/or Oakland County Equalization by the authority. The key attributes are Name (official name of the authority), Type (the type of development authority), and DevelopmentPlan (yes/no indicating if the feature represents an area that is part of a development plan and can caputre tax increment financing).Tax Increment Financing is a tool used to promote redevelopment and community improvement projects by channeling funding toward projects in targeted areas. TIF is captured from the increase of property values from a base year. Millage rates from taxing jurisdictions are applied to the increased value. The resulting tax revenue is directed to the authority, rather than the appropriate jurisdiction. Beginning in 1994, taxing jurisdictions have the option to "opt out" of having its taxes captured by the authority. Also since 1994, school taxes may no longer be captured unless they are necessary to make payments on existing eligible obligations. For more information about TIF, see Michigan Department of Treasury's Tax Increment Financing FAQ web page at http://www.michigan.gov/treasury/0,1607,7-121-3218---F,00.html. The State of Michigan has adopted enabling legislation to allow TIF through five types of authorities. Each type of authority has a focus relating to development/redevelopment: Downtown Development Authority (PA 197 of 1975) Correct and prevent deterioration in business districtsEncourage historic preservationPromote economic growth of the districts Tax Increment Finance Authority (PA 450 of 1980)Prevent urban deteriorationEncourage economic development and activityEncourage neighborhood revitalization and historic preservationClosed to new applicants since 1987Allows the development of virtually any type of land use Local Development Finance Authority (PA 281 of 1986)Encourage local developmentPromote conditions of employmentPromote economic growthLimited to business activities involving:ManufacturingAgricultural processingHigh-technology activitiesEnergy productionBusiness incubators Brownfield Redevelopment Authority (PA 381 of 1996)Promote revitalization, redevelopment, and reuse of certain propertyFocus on tax reverted, blighted, or functionally obsolete propertyMDEQ must approve brownfield redevelopment areas Corridor Improvement Authority (PA 281 of 2005)Correct and prevent deterioration in business districtsEncourage historic preservationPromote economic growth of the districtsMust be adjacent to a road classified as an arterial or collectorThese quasi-public entities are created by resolution through a community's governing body. CIA and LDFA boundaries may cross municipal boundaries. In the case of these multi-jurisdictional authorities, both communities must pass resolutions establishing authority. There is currently only one Joint LDFA (Cities of Southfield and Troy) and there are no CIAs in Oakland County. When the community establishes the authority, it must also define the geographic boundaries in which it will operate. DDAs and CIAs are authorized to levy and collect taxes through a special assessment on all properties within the authority boundary. After the authority and its boundaries are established, the authority creates a tax increment financing and development plan. The plan estimates the amount of tax increment financing that will be captured and lists specific projects on which it will be spent. It also defines the development area where the tax increment financing and projects will occur. The development area must be completely within the authority boundary; however, it may be coincident with the authority boundary. An authority may contain multiple development areas, each with its own development and tax increment financing plan. BRAs normally designate development areas as a one or two parcels for a specific development project, while the other types of authorities define development areas as a larger area. Also, LDFAs are only allowed to capture TIF from parcels in a permitted use, such as manufacturing. There may be both eliglible and inelgible parcels within a development area; however, the inelgible parcels do not participate in TIF capture. The base year used to calculate the amount of tax increment financing is set when the development plan is adopted. If the development plan is expanded at a later date, the base year could be reset for the entire development area or the capture could be calculated using multiple base years. The source for the base year was the tax billing code used by Oakland County Equalization. When no tax billing code was available (for communities that don't use the county's assessing system), the community was contacted to obtain the base year. When two separate authorities overlap, each authority can establish overlapping development areas. The authority that first created the development area has first claim on tax increment financing capture. Authority boundaries are represented using multiple features when the development area is not coincident with the authority boundary. One feature represents the development area and a second feature represents the remainder of the authority district that is not part of the development area. Multiple features are also used to represent authorities that have multiple development areas or development areas that have multiple base years. Brownfield Redevelopment Authorities are unique in that the authority boundaries are generally defined as the entire municipality. For this reason, the non-development areas of BRA's have been excluded from this data. The following list shows communities in Oakland County that have established a BRA: City of Auburn Hills City of Birmingham City of Farmington City of Farmington Hills City of Ferndale City of Hazel Park Charter Township of Highland Village of Holly City of Madison Heights Village of Milford County of Oakland City of Oak Park City of Pontiac City of Rochester City of Rochester Hills Charter Twp of Royal Oak City of Royal Oak City of Southfield City of Troy Charter Township of Waterford Source documents for the boundary of each feature were obtained from the State of Michigan Office of the Great Seal, Oakland County Equalization, and the Oakland County Treasurer's office. These could be in the form of a legal description, parcel list, and/or map. For several boundaries, multiple sources were available and conflicted with each other. When this occurred, hierarchy was given to the legal description, then a parcel list, over the map, and the conflict is noted in the Comments field. However, if a parcel was shown in a parcel list, but not described in the authority based on the legal description, then it was still shown in the authority.It should also be noted that legal descriptions were not digitized using exact coordinate geometry. Instead, features were created by referencing the legal description to snap vertices to parcels, right-of-way, section corners, subdivisions, and lots. Features digitized from a legal description or map included road and railroad rights-of-way as it was described or shown in the document.For vague legal descriptions and parcel lists, right-of-way was addressed uniquely for each authority. Some source documents had statements that all or half of the surrounding right-of-way is to be included in the boundary, but some did not address right-of-way at all. In these cases, right-of-way was addressed distinctly for each authority based on the type of authority and the source documents with the method used recorded in the Comments field. The data will be updated on an "as needed" basis when authorities amend their development plans or new authorities are established. Oakland County Equalization and the Oakland County Treasurer's Office will notify and forward the source documents of necessary revisions to Oakland County Planning and Economic Development Services who is the custodian of the feature class. Communities will be contacted annually to verify that the districts have not changed without the knowledge of county departments. In particular, county departments may not be aware of BRA development projects when no TIF is captured. Lastly, because the tax parcel feature class is revised periodically and it is important for the features to be coincident with the tax parcel feature class, the development authority feature class will also be updated annually to correct conflicts due to parcel shifting.

This dataset provides a land cover map focused on peatland ecosystems in the upper peninsula of Michigan. The map was produced at 12.5-m resolution using a multi-sensor fusion (optical and L-band SAR) approach with imagery from Landsat-5 TM and ALOS PALSAR collected between 2007 and 2011. A random forest classifier trained with polygons delineated from field data and aerial photography was used to determine pixel classes. Accuracy assessment based on field-sampled sites show high overall map accuracy (92%).

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public open space and voluntarily provided, private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastral Theme (http://www.fgdc.gov/ngda-reports/NGDA_Datasets.html). PAD-US is an ongoing project with several published versions of a spatial database of areas dedicated to the preservation of biological diversity, and other natural, recreational or cultural uses, managed for these purposes through legal or other effective means. The geodatabase maps and describes public open space and other protected areas. Most areas are public lands owned in fee; however, long-term easements, leases, and agreements or administrative designations documented in agency management plans may be included. The PAD-US database strives to be a complete “best available” inventory of protected areas (lands and waters) including data provided by managing agencies and organizations. The dataset is built in collaboration with several partners and data providers (http://gapanalysis.usgs.gov/padus/stewards/). See Supplemental Information Section of this metadata record for more information on partnerships and links to major partner organizations. As this dataset is a compilation of many data sets; data completeness, accuracy, and scale may vary. Federal and state data are generally complete, while local government and private protected area coverage is about 50% complete, and depends on data management capacity in the state. For completeness estimates by state: http://www.protectedlands.net/partners. As the federal and state data are reasonably complete; focus is shifting to completing the inventory of local gov and voluntarily provided, private protected areas. The PAD-US geodatabase contains over twenty-five attributes and four feature classes to support data management, queries, web mapping services and analyses: Marine Protected Areas (MPA), Fee, Easements and Combined. The data contained in the MPA Feature class are provided directly by the National Oceanic and Atmospheric Administration (NOAA) Marine Protected Areas Center (MPA, http://marineprotectedareas.noaa.gov ) tracking the National Marine Protected Areas System. The Easements feature class contains data provided directly from the National Conservation Easement Database (NCED, http://conservationeasement.us ) The MPA and Easement feature classes contain some attributes unique to the sole source databases tracking them (e.g. Easement Holder Name from NCED, Protection Level from NOAA MPA Inventory). The "Combined" feature class integrates all fee, easement and MPA features as the best available national inventory of protected areas in the standard PAD-US framework. In addition to geographic boundaries, PAD-US describes the protection mechanism category (e.g. fee, easement, designation, other), owner and managing agency, designation type, unit name, area, public access and state name in a suite of standardized fields. An informative set of references (i.e. Aggregator Source, GIS Source, GIS Source Date) and "local" or source data fields provide a transparent link between standardized PAD-US fields and information from authoritative data sources. The areas in PAD-US are also assigned conservation measures that assess management intent to permanently protect biological diversity: the nationally relevant "GAP Status Code" and global "IUCN Category" standard. A wealth of attributes facilitates a wide variety of data analyses and creates a context for data to be used at local, regional, state, national and international scales. More information about specific updates and changes to this PAD-US version can be found in the Data Quality Information section of this metadata record as well as on the PAD-US website, http://gapanalysis.usgs.gov/padus/data/history/.) Due to the completeness and complexity of these data, it is highly recommended to review the Supplemental Information Section of the metadata record as well as the Data Use Constraints, to better understand data partnerships as well as see tips and ideas of appropriate uses of the data and how to parse out the data that you are looking for. For more information regarding the PAD-US dataset please visit, http://gapanalysis.usgs.gov/padus/. To find more data resources as well as view example analysis performed using PAD-US data visit, http://gapanalysis.usgs.gov/padus/resources/. The PAD-US dataset and data standard are compiled and maintained by the USGS Gap Analysis Program, http://gapanalysis.usgs.gov/ . For more information about data standards and how the data are aggregated please review the “Standards and Methods Manual for PAD-US,” http://gapanalysis.usgs.gov/padus/data/standards/ .

These data were automated to provide an accurate high-resolution historical shoreline of Lake Michigan suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution...