Set of all the USGS 24k Quadrangle maps that intersect Eaton County, Michigan.The quadrangles included are Aurelius, Bellevue, Charlotte, Chester, Dimondale, Duck Lake, Eagle, Eaton Rapids, Hoytville, Lansing North, Lansing South, Nashville, Needmore, Olivet, Onondaga, Portland South, Saubee Lake, Springport, Wacousta, and Woodbury. They are all the 2019 versions of the maps except Needmore, which is 2017. These maps were acquired by download from the National Map Viewer.https://www.usgs.gov/core-science-systems/ngp/tnm-delivery/ on 1/9/2020.

By using this data, you agree to the SEMCOG Copyright License Agreement. 1-foot elevation contour lines for Livingston County, Michigan, stored in file geodatabase format. Created from LiDAR data collected in 2017-2018.

By using this data, you agree to the SEMCOG Copyright License Agreement.

This document explains one process for downloading LiDAR and DEM data for Southeast Michigan form the United States Geological Survey (USGS). This data was flown in 2017 and 2018, and is identical to the data that SEMCOG distributes. Full metadata for the LiDAR and DEM data is available for download at a link included within the document.

The 1:24,000-scale (24K) U.S. Geological Survey (USGS) quadrangle boundary data set contains the following information. (1) The approximate boundaries of the various 24K USGS quadrangles. (2) The names and indexing codes associated with each 24K quadrangle.Topo Quads MetadataMore Metadata

These data were created as part of the National Oceanic and Atmospheric Administration Office for Coastal Management's efforts to create an online mapping viewer called the NOAA Lake Level Viewer. It depicts potential lake level rise and fall and its associated impacts on the nation's coastal areas. The purpose of the mapping viewer is to provide coastal managers and scientists with a preliminary look at lake level change, coastal flooding impacts, and exposed lakeshore. The viewer is a screening-level tool that uses nationally consistent data sets and analyses. Data and maps provided can be used at several scales to help gauge trends and prioritize actions for different scenarios. The NOAA Lake Level Viewer may be accessed at: https://coast.noaa.gov/llv. This metadata record describes the Lake Michigan digital elevation model (DEM), which is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Lake Level Viewer described above. This DEM includes the best available lidar, US Army Corps of Engineer dredge surveys, and National Park Service multibeam data known to exist at the time of DEM creation that met project specifications. This DEM includes data for Allegan, Antrim, Benzie, Berrien, Charlevoix, Delta, Emmet, Grand Traverse, Leelanau, Mackinac, Manistee, Mason, Menominee, Muskegon, Oceana, Ottawa, Schoolcraft, and Van Buren counties in Michigan; Lake, La Porte, and Porter Counties in Indiana, Cook and Lake Counties in Illinois, and Brown, Door, Kenosha, Kewaunee, Manitowoc, Marinette, Milwaukee, Oconto, Ozaukee, Racine, and Sheboygan Counties in Wisconsin. The DEM was produced from the following lidar data sets: 1. 2016 NOAA Topobathy Lidar: Upper Lake Michigan Islands 2. 2015 FEMA Marinette County 3. 2013 Indiana Statewide Lidar Collection: Lake, La Porte, Tippecanoe, Newton, Jasper and Porter County Buy-Up 4. 2013 Muskegon County, Michigan Lidar Co-Op 5. 2013 USACE NCMP Topobathy Lidar: Lake Michigan North (MI) 6. 2012 USACE NCMP Topobathy Lidar: Lake Michigan (MI,WI) 7. 2012 USACE NCMP Topobathy Lidar: Lake Michigan (IL,IN,MI,WI) 8. 2010 Brown County Lidar 9. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (IN) 10. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (WI) 11. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (IL) 12. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (MI) 13. 2007 USACE NCMP Topobathy BE Lidar: Lake Michigan (MI) and Lake Erie (PA) 14. 2007 ARRA Lidar: Lake County (IL) 15. 2006 USACE NCMP Topobathy Lidar: Lake Michigan (IN), Lake Erie (OH,PA), Lake Huron (MI) The DEM was produced from the following sonar data sets: 16. 2015 USACE Detroit District, Port Washington Harbor, WI 17. 2015 USACE Detroit District, South Haven Harbor, MI 18. 2015 USACE Detroit District, Washington Island (Detroit Harbor), WI 19. 2015 USACE Detroit District, Washington Island (Jackson Harbor), WI 20. 2015 USACE Detroit District, Grand Haven Harbor, MI 21. 2015 USACE Detroit District, Pentwater Harbor, MI 22. 2015 USACE Detroit District, Pensaukee Harbor, WI 23. 2015 USACE Detroit District, St. Joseph Harbor, MI 24. 2015 USACE Detroit District, Manistee Harbor, MI 25. 2015 USACE Detroit District, Green Bay Harbor, WI 26. 2015 USACE Detroit District, Saugatuck Harbor, MI 27. 2015 USACE Detroit District, Oconto Harbor, WI 28. 2015 USACE Detroit District, White Lake Harbor, MI 29. 2015 USACE Detroit District, Manistique Harbor, MI 30. 2014 USACE Detroit District, Milwaukee Harbor, WI 31. 2014 USACE Detroit District, Frankfort Harbor, MI 32. 2014 USACE Detroit District, St. Joseph Harbor, MI 33. 2014 USACE Detroit District, Holland Harbor, MI 34. 2014 USACE Chicago District, Burns Waterway Harbor, IN 35. 2014 USACE Chicago District, Burns Small Boat Harbor, IN 36. 2014 USACE Chicago District, Michigan City, IN 37. 2014 USACE Chicago District, Waukegan Harbor, IL 38. 2014 USACE Chicago District, Calumet River, IL 39. 2014 USACE Detroit District, Menominee Harbor, MI/WI The DEM was produced from the following NPS multibeam sonar data sets: 40. 2011, National Park Service, Sleeping Bear Dunes National Lakeshore Multibeam Sonar 41. 2012, National Park Service, Sleeping Bear Dunes National Lakeshore Multibeam Sonar The DEM is referenced vertically to the North American Vertical Datum of 1988 (NAVD88) with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is approximately 3 meters.

This location is part of the Arizona Mineral Industry Location System (AzMILS), an inventory of mineral occurences, prospects and mine locations in Arizona. Yavapai580B is located in T16N R2E Sec 28 NE in the Hickey Mountain - 7.5 Min quad. This collection consists of various reports, maps, records and related materials acquired by the Arizona Department of Mines and Mineral Resources regarding mining properties in Arizona. Information was obtained by various means, including the property owners, exploration companies, consultants, verbal interviews, field visits, newspapers and publications. Some sections may be redacted for copyright. Please see the access statement.

This digital data release presents contour data from multiple subsurface geologic horizons as presented in previously published summaries of the regional subsurface configuration of the Michigan and Illinois Basins. The original maps that served as the source of the digital data within this geodatabase are from the Geological Society of America’s Decade of North American Geology project series, “The Geology of North America” volume D-2, chapter 13 “The Michigan Basin” and chapter 14 “Illinois Basin Region”. Contour maps in the original published chapters were generated from geophysical well logs (generally gamma-ray) and adapted from previously published contour maps. The published contour maps illustrated the distribution sedimentary strata within the Illinois and Michigan Basin in the context of the broad 1st order supercycles of L.L. Sloss including the Sauk, Tippecanoe, Kaskaskia, Absaroka, Zuni, and Tejas supersequences. Because these maps represent time-transgressive surfaces, contours frequently delineate the composite of multiple named sedimentary formations at once. Structure contour maps on the top of the Precambrian basement surface in both the Michigan and Illinois basins illustrate the general structural geometry which undergirds the sedimentary cover. Isopach maps of the Sauk 2 and 3, Tippecanoe 1 and 2, Kaskaskia 1 and 2, Absaroka, and Zuni sequences illustrate the broad distribution of sedimentary units in the Michigan Basin, as do isopach maps of the Sauk, Upper Sauk, Tippecanoe 1 and 2, Lower Kaskaskia 1, Upper Kaskaskia 1-Lower Kaskaskia 2, Kaskaskia 2, and Absaroka supersequences in the Illinois Basins. Isopach contours and structure contours were formatted and attributed as GIS data sets for use in digital form as part of U.S. Geological Survey’s ongoing effort to inventory, catalog, and release subsurface geologic data in geospatial form. This effort is part of a broad directive to develop 2D and 3D geologic information at detailed, national, and continental scales. This data approximates, but does not strictly follow the USGS National Cooperative Geologic Mapping Program's GeMS data structure schema for geologic maps. Structure contour lines and isopach contours for each supersequence are stored within separate “IsoValueLine” feature classes. These are distributed within a geographic information system geodatabase and are also saved as shapefiles. Contour data is provided in both feet and meters to maintain consistency with the original publication and for ease of use. Nonspatial tables define the data sources used, define terms used in the dataset, and describe the geologic units referenced herein. A tabular data dictionary describes the entity and attribute information for all attributes of the geospatial data and accompanying nonspatial tables.

A spatial representation of ten-foot topographic contour lines. This line feature class was derived from a County-wide raster that was created from the terrain dataset based on the DTM deliverables (masspoints, soft breaklines, etc.) from the 2008 LIDAR project. The key attribute is Contour.

This layer is a component of Enterprise surface topography map service.

Layered GeoPDF 7.5 Minute Quadrangle Map. Layers of geospatial data include orthoimagery, roads, grids, geographic names, elevation contours, hydrography, and other selected map features.

These files contain rasterized topobathy lidar elevations generated from data collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system. CZMIL integrates a lidar sensor with simultaneous topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities. Native lidar data is no...

The State of Michigan (DTMB) contracted with Sanborn to provide LiDAR mapping services for 6 counties in the State of Michigan. These counties include Cass, Genesee, Kalamazoo, Lapeer, Shiawassee, and St, Joseph. This metadata record describes the three counties of Cass, Kalamazoo, and St. Joseph and the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV i...

This metadata record describes the lidar-based digital elevation model (DEM) for the 2017 Michigan LiDAR project covering approximately 512 square miles, covering Oceana County.

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

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

Lake Michigan Michigan City Surface Temperature Contour Map (2022-present) cdm_data_type=Other infoUrl=https://coastwatch.glerl.noaa.gov/ institution=CoastWatch Great Lakes Node sourceUrl=(local files) subsetVariables=fileType

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

Layered GeoPDF 7.5 Minute Quadrangle Map. Layers of geospatial data include orthoimagery, roads, grids, geographic names, elevation contours, hydrography, and other selected map features.

Lake Michigan Central Region Surface Temperature Contour Map (2022-present) cdm_data_type=Other infoUrl=https://coastwatch.glerl.noaa.gov/ institution=CoastWatch Great Lakes Node sourceUrl=(local files) subsetVariables=fileType

Bathymetry of Lake Michigan has been compiled as a component of a NOAA project to rescue Great Lakes lake floor geological and geophysical data and make it more accessible to the public. The project is a cooperative effort between investigators at the NOAA National Geophysical Data Center's Marine Geology & Geophysics Division (NGDC/MGG) and the NOAA Great Lakes Environmental Research Laboratory (GLERL). was compiled utilizing the entire historic sounding data base. This bathymetry resolves physiography of the lake floor to an extent that known features are revealed more accurately and features never before seen are revealed for the first time. Bathymetry has been compiled using the entire array of good-quality historical hydrographic soundings collected in support of nautical charting over a 120-year period by the NOAA National Ocean Service and its predecessor agency for Great Lakes surveying, the Army Corps of Engineers. More than 600,000 bathymetric soundings were employed, of which approximately 60 per cent were already in digital form, 25 per cent were digitized in conjunction with this effort, and the remaining 15 per cent were available only on paper survey sheets. Bathymetry was compiled at a scale of 1:250,000, with a contour interval of 5 meters. Density of tracklines is generally about 2000m for the open lake and ranges from 200m to 600m for nearshore areas. Soundings collected since 1903 were already reduced to the Lake Michigan mean low water datum; these were used for bathymetric contouring without further calibration or adjustments. Soundings collected prior to 1903 were reduced to the mean low water datum. In preparation for bathymetric contouring, digital soundings were converted to metric units and plotted in color; separate colors were assigned to the various depth ranges. From the paper sheets, contours in metric units were generated directly on overlays; these contours were then reduced to the compilation scale of 1:250,000 and incorporated into the map. Compilation sheets were then scanned and vectorized; and the resulting digital vector bathymetric contour data were used to generate the imagery shown on the large color plate. Images were constructed using the publicly-available software Generic Mapping Tools (GMT).

The lake contours were digitized by a number of different sources, but largely through the GIS group at the Institute for Fisheries Research. Lakes are associated with a New Key, a unique identifier that is a combination of a country code with a unique lake code (Breck, 2004; Humphrys and Green, 1962). Each contour has a maximum and minimum depth. The minimum depth is the value of the contour line and the max value is either the value of the next deepest contour or the deepest point within the contour if there is no next deepest contour.