Facebook
TwitterOnline 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.
Facebook
TwitterProperty 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.
Facebook
TwitterOakland 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.
Facebook
TwitterThis 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
Facebook
TwitterCounty town, range, section, quarter/quarter, quarter polygons, town, range, section, government lot polygons, or private claim polygons.More Metadata
Facebook
TwitterDownload In State Plane Projection Here. This is our working version of the Lake County boundary. Although technically the county's eastern border extends eastward into Lake Michigan to the state line where Illinois meets Michigan, we routinely use the Lake Michigan shoreline as our eastern boundary for mapping purposes. The north, west and south boundaries are based on a compilation of survey data which aligns well, but not perfectly, with the border as mapped by neighboring counties and the State of Wisconsin, which forms the northern boundary of the county. Update Frequency: This dataset is updated on a weekly basis.
Facebook
TwitterBY 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.
Facebook
TwitterThe 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).
Facebook
TwitterThe 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).
Facebook
TwitterSurvey sections and private claims for Michigan's Upper and Lower PeninsulasMore Metadata
Facebook
TwitterAttribution-ShareAlike 4.0 (CC BY-SA 4.0)https://creativecommons.org/licenses/by-sa/4.0/
License information was derived automatically
This dataset contains parcel level information on property and land use for parcels within the Arena District, including structure and/or lot condition and use. This dataset was created by University of Michigan students during a land survey in April 2017. Data was obtained for the Building and Conditions section of Little Caesar's Arena District Needs Assessment.Click here for metadata (descriptions of the fields).
Facebook
TwitterBY 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).
Facebook
TwitterThese data provide an accurate high-resolution shoreline compiled from imagery of BEAVER ISLAN AND GARDEN ISLAND, MICHIGAN . This vector shoreline data is based on an office interpretation of imagery that may be suitable as a geographic information system (GIS) data layer. This metadata describes information for both the line and point shapefiles. The NGS attribution scheme 'Coastal Cartograp...
Facebook
TwitterThe 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/ .
Facebook
TwitterThis 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%).
Facebook
TwitterThe first basin-wide map of large stands of invasive Phragmites australis (common reed) in the coastal zone was created through a collaboration between the U.S. Geological Survey and Michigan Tech Research Institute (Bourgeau-Chavez et al 2013). This data set represents a revised version of that map and was created using multi-temporal PALSAR data and Landsat images from 2016-2017. In addition to Phragmites distribution, the data sets shows several land cover types including urban, agriculture, forest, shrub, emergent wetland, forested wetland, and some based on the dominant plant species (e.g., Schoenoplectus, Typha). The classified map was validated using over 400 field visits.This map covers the coastal regions of Michgan along the southern portion Lake Huron including Saginaw Bay, Lake St. Clair, Lake Erie, and northeastern Ohio.
Facebook
TwitterThese data provide an accurate high-resolution shoreline compiled from imagery of PORT OF CALCITE AND ROGERS CITY HARBOR, MI . This vector shoreline data is based on an office interpretation of imagery that may be suitable as a geographic information system (GIS) data layer. This metadata describes information for both the line and point shapefiles. The NGS attribution scheme 'Coastal Cartogr...
Facebook
TwitterThis dataset combines the work of several different projects to create a seamless data set for the contiguous United States. Data from four regional Gap Analysis Projects and the LANDFIRE project were combined to make this dataset. In the northwestern United States (Idaho, Oregon, Montana, Washington and Wyoming) data in this map came from the Northwest Gap Analysis Project. In the southwestern United States (Colorado, Arizona, Nevada, New Mexico, and Utah) data used in this map came from the Southwest Gap Analysis Project. The data for Alabama, Florida, Georgia, Kentucky, North Carolina, South Carolina, Mississippi, Tennessee, and Virginia came from the Southeast Gap Analysis Project and the California data was generated by the updated California Gap land cover project. The Hawaii Gap Analysis project provided the data for Hawaii. In areas of the county (central U.S., Northeast, Alaska) that have not yet been covered by a regional Gap Analysis Project, data from the Landfire project was used. Similarities in the methods used by these projects made possible the combining of the data they derived into one seamless coverage. They all used multi-season satellite imagery (Landsat ETM+) from 1999-2001 in conjunction with digital elevation model (DEM) derived datasets (e.g. elevation, landform) to model natural and semi-natural vegetation. Vegetation classes were drawn from NatureServe's Ecological System Classification (Comer et al. 2003) or classes developed by the Hawaii Gap project. Additionally, all of the projects included land use classes that were employed to describe areas where natural vegetation has been altered. In many areas of the country these classes were derived from the National Land Cover Dataset (NLCD). For the majority of classes and, in most areas of the country, a decision tree classifier was used to discriminate ecological system types. In some areas of the country, more manual techniques were used to discriminate small patch systems and systems not distinguishable through topography. The data contains multiple levels of thematic detail. At the most detailed level natural vegetation is represented by NatureServe's Ecological System classification (or in Hawaii the Hawaii GAP classification). These most detailed classifications have been crosswalked to the five highest levels of the National Vegetation Classification (NVC), Class, Subclass, Formation, Division and Macrogroup. This crosswalk allows users to display and analyze the data at different levels of thematic resolution. Developed areas, or areas dominated by introduced species, timber harvest, or water are represented by other classes, collectively refered to as land use classes; these land use classes occur at each of the thematic levels. Raster data in both ArcGIS Grid and ERDAS Imagine format is available for download at http://gis1.usgs.gov/csas/gap/viewer/land_cover/Map.aspx Six layer files are included in the download packages to assist the user in displaying the data at each of the Thematic levels in ArcGIS. In adition to the raster datasets the data is available in Web Mapping Services (WMS) format for each of the six NVC classification levels (Class, Subclass, Formation, Division, Macrogroup, Ecological System) at the following links. http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Class_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Subclass_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Formation_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Division_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Macrogroup_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_Ecological_Systems_Landuse/MapServer
Facebook
TwitterThese 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...
Facebook
TwitterBY 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.
Facebook
TwitterOnline 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.