<?xml version='1.0' encoding='UTF-8'?>
<metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Jenny L Hanson</origin>
        <origin>Stephanie R Sattler</origin>
        <origin>John W Lund</origin>
        <pubdate>20240912</pubdate>
        <title>LAS dataset of lidar and multibeam sonar data collected at Lake Superior at Minnesota Point, Duluth, MN, July 2020</title>
        <geoform>vector digital data</geoform>
        <onlink>https://doi.org/10.5066/P9JH0O1X</onlink>
        <lworkcit>
          <citeinfo>
            <origin>Daniel M Wagner</origin>
            <origin>John W Lund</origin>
            <origin>Kelly M Sanks</origin>
            <pubdate>20200710</pubdate>
            <title>Beach topography and near-shore bathymetry of Lake Superior at Minnesota Point, Duluth, MN, August 2019</title>
            <geoform>raster digital data</geoform>
            <pubinfo>
              <pubplace>https://www.sciencebase.gov</pubplace>
              <publish>U.S. Geological Survey</publish>
            </pubinfo>
            <onlink>https://doi.org/10.5066/p9gxt1x1</onlink>
          </citeinfo>
        </lworkcit>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset is a LAS dataset containing light detection and ranging (lidar) data and sonar data representing the beach and near-shore topography of Lake Superior at Minnesota Point, Duluth, Minnesota. The LAS dataset was used to create a digital elevation model (DEM) of the approximately 2.27 square kilometer surveyed area. Lidar data were collected July 23, 2020 using a boat mounted Velodyne unit.  Multibeam sonar data were collected July 20th and 23rd, 2020 using a Norbit integrated wide band multibeam system compact (iWBMSc) sonar unit. Methodology similar to Wagner, D.M., Lund, J.W., and Sanks, K.M., 2020 was used.</abstract>
      <purpose>Data were collected in cooperation with the U.S. Army Corps of Engineers (USACE), Detroit District, to define beach topography and near-shore bathymetry after placing dredge spoils to mitigate beach erosion. This post-placement survey was completed to evaluate movement of placed material and overall changes to the barrier island and surrounding nearshore area approximately 1-year after nourishment placement. The LAS dataset is provided because it was used to generate the elevation surface of the surveyed area, and can be used to generate additional DEMs with different resolutions.</purpose>
      <supplinf>Due to time constraints, surveys were conducted under windy conditions causing a high heave error. These conditions affected the data (heave) and are noticeable in the higher resolution datasets.

LAS is an industry-standard binary format for storing large point clouds, and mostly used for generating elevation surfaces.

Lidar patch test values were estimated but a patch test was not formally conducted. The uncertainty of the lidar is unknown. Post data release, we found discernible errors in the positioning. Please use the data with caution.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <mdattim>
          <sngdate>
            <caldate>20200720</caldate>
          </sngdate>
          <sngdate>
            <caldate>20200723</caldate>
          </sngdate>
        </mdattim>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-92.04170</westbc>
        <eastbc>-92.00720</eastbc>
        <northbc>46.72940</northbc>
        <southbc>46.71050</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>elevation</themekey>
        <themekey>inlandWaters</themekey>
      </theme>
      <theme>
        <themekt>Data Categories for Marine Planning</themekt>
        <themekey>Bathymetry and Elevation</themekey>
      </theme>
      <theme>
        <themekt>USGS Thesaurus</themekt>
        <themekey>limnology</themekey>
        <themekey>lidar</themekey>
        <themekey>digital elevation models</themekey>
        <themekey>bathymetry</themekey>
      </theme>
      <theme>
        <themekt>USGS Metadata Identifier</themekt>
        <themekey>USGS:606776fad34edc0435c09d71</themekey>
      </theme>
      <place>
        <placekt>Common geographic areas</placekt>
        <placekey>Southwestern Lake Superior</placekey>
        <placekey>Great Lakes</placekey>
        <placekey>Duluth</placekey>
        <placekey>Lake Superior</placekey>
        <placekey>Superior</placekey>
      </place>
    </keywords>
    <accconst>None. Please see 'Distribution Info' for details.</accconst>
    <useconst>None.  Users are advised to read the dataset's metadata thoroughly to understand appropriate use and data limitations.</useconst>
    <ptcontac>
      <cntinfo>
        <cntperp>
          <cntper>Jenny L Hanson</cntper>
          <cntorg>U.S. Geological Survey, MIDCONTINENT REGION</cntorg>
        </cntperp>
        <cntpos>Biologist</cntpos>
        <cntaddr>
          <addrtype>mailing address</addrtype>
          <address>2630 Fanta Reed Road</address>
          <city>La Crosse</city>
          <state>WI</state>
          <postal>54603</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>608-781-6372</cntvoice>
        <cntfax>608-783-6066</cntfax>
        <cntemail>jhanson@usgs.gov</cntemail>
      </cntinfo>
    </ptcontac>
    <datacred>Funding for the project was provided by the Great Lakes Restoration Initiative (GLRI) in cooperation with the USACE, Detroit District. The Mounds View, MN office of the USGS Upper Midwest Water Science Center (UMID) teamed up with the La Crosse, WI USGS Upper Midwest Environmental Sciences Center (UMESC) to collect the lidar and multibeam data, using the UMESC's Velodyne puck and Norbit iWBMSc mounted on UMID's boat.</datacred>
    <native>Environment as of Metadata Creation: Microsoft Windows 10 Enterprise; Xylem's Hypack 2020; GeoCue's LP360 version 2020.1.80.0; Esri ArcGIS for Desktop version 10.7.1; Waypoint Inertial Explorer version 8.90</native>
    <crossref>
      <citeinfo>
        <origin>Daniel M Wagner</origin>
        <origin>John W Lund</origin>
        <origin>Kelly M Sanks</origin>
        <pubdate>20200720</pubdate>
        <title>Beach topography and near-shore bathymetry of Lake Superior at Minnesota Point, Duluth, MN, August 2019</title>
        <geoform>dataset</geoform>
        <pubinfo>
          <pubplace>https://www.sciencebase.gov</pubplace>
          <publish>U.S. Geological Survey</publish>
        </pubinfo>
        <onlink>https://doi.org/10.5066/p9gxt1x1</onlink>
      </citeinfo>
    </crossref>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>Prior to the bathymetric survey, a boresight calibration procedure was performed to determine the alignment offsets between reference frame of the sonar and that of the inertial measurement unit (IMU) that is part of the positioning system. The offsets determined from the boresight calibration procedure were applied to the bathymetric data during data collection. Patch tests were conducted on the Norbit iWBMSc multibeam sonar to determine latency and angular differences (yaw, pitch, and roll) between the sonar head and the IMU that is incorporated with the NovAtel positioning system. The patch test involves surveying over various bathymetric features in the same and opposite directions at different speeds, from which the angular offsets can be identified, quantified, and corrected. The following corrections were determined from the patch test: yaw = -1.67 degrees; pitch = -2.33degrees; roll = -0.4 degrees; and latency = 0 milliseconds. These corrections were applied to the multibeam sonar data during post-processing in Hypack 2020 software. Multibeam settings included a 140-degree swath that was further reduced to 65 beam angle limits in Hypack post-processing. During the bathymetric survey, data quality was assessed continuously by the sonar operator. Data-quality flags and alarms from the sonar and positioning systems were noted and investigated. To account for spatial and temporal changes in sound velocity, profiles were collected every 1-2 hours using a Sound Velocity Profiler unit and applied to the multibeam sonar data during post-processing in Hypack 2020 software.  Total propagated uncertainty (TPU) in the multibeam survey was estimated and accounted for in the final dataset using the Combined Uncertainty and Bathymetric Estimator (CUBE) method in Hypack 2020 software (Calder and Mayer, 2003). The CUBE method uses the uncertainties of the various components of error, such as position, sound speed, and loading conditions to compute TPU and adjust the final soundings accordingly. 

Lidar patch test values were estimated in post-processing, but a patch test was not formally conducted during acquisition. The uncertainty of the lidar is unknown. Please use the data with caution.</attraccr>
    </attracc>
    <logic>Positions and elevations of the point data from which the DEM and contours were derived fall within expected ranges and plot in the correct locations on available aerial imagery.</logic>
    <complete>A survey area was provided by the USACE (Detroit district), to show the area required along the Minnesota Point. The beach face was surveyed from approximately 2 kilometers (km; 1.24 miles [mi]) along the southern section of Park Point Beach to the breakwall at the Superior, Wisconsin entry to Superior Bay. Along this distance, the bathymetry of Lake Superior was surveyed from approximately 0.5 m (1.64 ft) to a depth of 12.2 m (40 ft) offshore, which corresponds approximately to the northeastern end of the breakwall.</complete>
    <posacc>
      <horizpa>
        <horizpar>During the survey, position and elevation data were collected using a NovAtel MarineSPAN Global Navigation Satellite System/Inertial Navigation System (GNSS/INS). The accuracy of the positioning data was improved in post-processing using the daily static occupations of a nearby National Geodetic Survey (NGS) Continuously Operating Reference Station (CORS). The data files from the daily static occupations were processed in WayPoint Inertial Explorer using the precise point kinematic method to help correct the 3D positioning location. The final navigation solution (called a smoothed best estimate of trajectory, or SBET, solution) was applied to the LiDAR and multibeam sonar data during post-processing. The estimated position accuracy for the solutions were calculated for the estimated standard deviation of less than 0.06 m (0.20 ft) in the X, or "easting", direction and less than 0.08 m (0.26 ft) in the Y, or "northing direction for July 20, 2020. The estimated standard deviation of less than 0.07 (0.23 ft) in the X, or "easting", direction and less than 0.09 m (0.30 ft) in the Y, or "northing direction for July 23, 2020.</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>During the survey, position and elevation data were collected using a NovAtel MarineSPAN Global Navigation Satellite System/Inertial Navigation System (GNSS/INS). The accuracy of the positioning data was improved in post-processing using the daily static occupations of a nearby National Geodetic Survey (NGS) Continuously Operating Reference Station (CORS). The data files from the daily static occupations were processed in WayPoint Inertial Explorer using the precise point kinematic method to help correct the 3D positioning location. The final navigation solution (called a smoothed best estimate of trajectory, or SBET, solution) was applied to the lidar and multibeam sonar data during post-processing. The estimated standard deviation of the Z ("down", or vertical) direction was less than 0.16 m (0.52 ft) for both July 20 and July 23, 2020. To correct vertical soundings to the International Great Lakes Datum conversion 1985 (IGLD 85), the Hypack geodesy settings were predefined to add a height above chart datum, by calculating the hydraulic corrector, or conversion between the dynamic height and the IGLD 85 height. Combined with the National Oceanic and Atmospheric Administration (NOAA) tide station 9099064 (located at the Duluth entry to the harbor on the northwest end of Minnesota Point, https://tidesandcurrents.noaa.gov/stationhome.html?id=9099064), the water surface elevation was vertically referenced for the multibeam sonar data.</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <procstep>
        <procdesc>Bathymetric data were collected using a Norbit iWBMSc sonar unit. A planned survey using a grid with survey lines spaced 100 feet apart was used for data collection. Generally, each subsequent pass was closer than the planned survey lines while moving progressively toward or away from shore until the lakebed was surveyed to a depth of at least 40 feet, which corresponded approximately to the northeast end of the breakwall at the Superior, Wisconsin entry to Superior Bay.</procdesc>
        <procdate>20200720</procdate>
      </procstep>
      <procstep>
        <procdesc>Lidar data were collected using a Velodyne VLP-16 unit mounted to the port side of the survey vessel. The Velodyne VLP-16 was coupled to a NovAtel positioning system for position and motion corrections. Data were collected simultaneously with multibeam data angled 90 degrees to the shoreline.</procdesc>
        <procdate>20200723</procdate>
      </procstep>
      <procstep>
        <procdesc>Data collected with the NovAtel's positioning system during the lidar and multibeam sonar surveys were post-processed using version 8.90 of  Waypoint Inertial Explorer software. The horizontal and vertical accuracy of the differential global navigation satellite systems (GNSS) solution was improved in post-processing by correcting the navigation solution based on the average solution of the daily occupations of nearby National Geodetic Survey (NGS) Continuously Operating Reference Stations (CORS). The post-processed navigation solution, known as a smoothed best estimate of trajectory (SBET) solution, was exported to a file for use in post-processing of lidar and multibeam sonar data.</procdesc>
        <procdate>20200723</procdate>
      </procstep>
      <procstep>
        <procdesc>Raw data collected with the Norbit iWBMSc sonar were edited using Hysweep's MBMAX64 module of Hypack 2020 software. The SBET solution from the NovAtel Inertial Explorer position system and boresight calibration file were applied to the multibeam data in Hypack 2020 MBMAX64.</procdesc>
        <procdate>20200927</procdate>
      </procstep>
      <procstep>
        <procdesc>The water-surface elevation from the National Oceanic and Atmospheric Administration (NOAA) Duluth, Minnesota, tide station (9099064) was applied to the multibeam sonar data as the vertical reference. Sound velocity profiles collected using the Sound Velocity Profiler unit were imported into Hysweep's MBMAX64 to correct soundings for spatial and temporal changes in sound velocity by interpolating between profiles based on geographic position and time of day.  Soundings from beams greater than 65 degrees from nadir were removed, and further screened using the 4 standard deviation and over/under filters to remove remaining erroneous soundings. TPU in the multibeam survey was accounted for in the final dataset using the CUBE method in Hypack 2020 software (Calder and Mayer, 2003). Filtered multibeam sonar data were exported from Hypack in LAS format.</procdesc>
        <procdate>20200927</procdate>
      </procstep>
      <procstep>
        <procdesc>Lidar data were classified using LP360 software. High and low noise were classified into the ignored ground class. Vegetation was classified into the medium-vegetation class. The data were examined in three dimensions; any remaining noise that was missed were reclassified. The LAS were exported to a Universal Transverse Mercator (UTM) projection of the National American Datum (NAD) of 1983 Zone 15 North with just the ground class remaining. The exported file was clipped to a boundary file (manually delineated) during the export. The LAS were exported to a 1-meter elevation (DEM) surface in order to conduct a quality control/quality assurance check for erroneous soundings.</procdesc>
        <procdate>20201005</procdate>
      </procstep>
      <procstep>
        <procdesc>The multibeam LAS datasets were imported to LP360 for further manual classification of noise.  A "clean" LAS dataset that did not contain any low or high noise was then exported, projected, and clipped to a boundary file (manually delineated).</procdesc>
        <procdate>20201005</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Point</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>Point</sdtstype>
        <ptvctcnt>284126101</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>Universal Transverse Mercator</gridsysn>
          <utm>
            <utmzone>15</utmzone>
            <transmer>
              <sfctrmer>0.9996</sfctrmer>
              <longcm>-93.0</longcm>
              <latprjo>0.0</latprjo>
              <feast>500000.0</feast>
              <fnorth>0.0</fnorth>
            </transmer>
          </utm>
        </gridsys>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.01</absres>
            <ordres>0.01</ordres>
          </coordrep>
          <plandu>meters</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>North_American_Datum_1983</horizdn>
        <ellips>GRS_1980</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altdatum>International Great Lakes Datum of 1985</altdatum>
        <altres>0.001</altres>
        <altunits>meters</altunits>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>SurveyArea.shp Attribute Table</enttypl>
        <enttypd>Table containing attribute information associated with the data set.</enttypd>
        <enttypds>Producer Defined</enttypds>
      </enttyp>
      <attr>
        <attrlabl>FID</attrlabl>
        <attrdef>Internal feature number.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Sequential unique whole numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Shape</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Area</attrlabl>
        <attrdef>Measure of surface area representing the survey polygon</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>2343101.42822</rdommin>
            <rdommax>2343101.42822</rdommax>
            <attrunit>squared meters</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Hectares</attrlabl>
        <attrdef>Measure of area, in hectares</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>234.310142822</rdommin>
            <rdommax>234.310142822</rdommax>
            <attrunit>hectares</attrunit>
          </rdom>
        </attrdomv>
      </attr>
    </detailed>
    <detailed>
      <enttyp>
        <enttypl>LIDAR_202007230.las</enttypl>
        <enttypd>LAS file of points from LiDAR survey</enttypd>
        <enttypds>Producer defined</enttypds>
      </enttyp>
      <attr>
        <attrlabl>Point Record</attrlabl>
        <attrdef>Point number of a point in LIDAR_20200723.las</attrdef>
        <attrdefs>Esri defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>1</rdommin>
            <rdommax>3,208,533</rdommax>
            <attrunit>integer</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>X coordinate</attrlabl>
        <attrdef>easting coordinate of point in LIDAR_20190810.las</attrdef>
        <attrdefs>Esri defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>573248.74</rdommin>
            <rdommax>575829.32</rdommax>
            <attrunit>meters UTM zone 15N</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Y coordinate</attrlabl>
        <attrdef>northing coordinate of point in LIDAR_20190810.las</attrdef>
        <attrdefs>Esri defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>5173473.13</rdommin>
            <rdommax>5174883.32</rdommax>
            <attrunit>meters UTM zone 15N</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Z coordinate</attrlabl>
        <attrdef>elevation of point in LIDAR_2020723.las</attrdef>
        <attrdefs>Esri defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>180.45</rdommin>
            <rdommax>248.03</rdommax>
            <attrunit>meters relative to IGLD85</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Return No.</attrlabl>
        <attrdef>Return number associated with the point.  A laser pulse can return to the LiDAR as one or more returns, depending on the number of reflective surfaces it encounters as it travels toward the ground.  The first returned pulse is the most significant and is associated with the highest feature in the landscape; if the highest feature is the ground, only one return is detected.</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>1</rdommin>
            <rdommax>1</rdommax>
            <attrunit>A value of 1 indicates first return</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Intensity</attrlabl>
        <attrdef>Intensity is a measure of the return strength of the laser pulse (from the LiDAR unit) reflected from a surface.  It is based, in part, on the reflectivity of the surface.  Intensity is normalized to a scale of 0-255.</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>0</rdommin>
            <rdommax>255</rdommax>
            <attrunit>integer</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Class code</attrlabl>
        <attrdef>Classification code for a point in LIDAR_20200723.las</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>2</rdommin>
            <rdommax>2</rdommax>
            <attrunit>Code 2 indicates ground points</attrunit>
          </rdom>
        </attrdomv>
      </attr>
    </detailed>
    <detailed>
      <enttyp>
        <enttypl>multibeam.las</enttypl>
        <enttypd>LAS file of points from multibeam sonar survey</enttypd>
        <enttypds>Producer defined</enttypds>
      </enttyp>
      <attr>
        <attrlabl>Point Record</attrlabl>
        <attrdef>Number of points in multibeam.las</attrdef>
        <attrdefs>Esri defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>1</rdommin>
            <rdommax>8089799</rdommax>
            <attrunit>integer</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>X coordinate</attrlabl>
        <attrdef>easting coordinate of point in multibeam.las</attrdef>
        <attrdefs>Esri defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>573275.78</rdommin>
            <rdommax>575853.03</rdommax>
            <attrunit>meters UTM zone 15N</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Y coordinate</attrlabl>
        <attrdef>northing coordinate of point in multibeam.las</attrdef>
        <attrdefs>Esri defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>5173481.01</rdommin>
            <rdommax>5175541.26</rdommax>
            <attrunit>meters UTM zone 15N</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Z coordinate</attrlabl>
        <attrdef>elevation of point in multibeam.las</attrdef>
        <attrdefs>Esri defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>168.1</rdommin>
            <rdommax>183.76</rdommax>
            <attrunit>meters relative to IGLD85</attrunit>
          </rdom>
        </attrdomv>
      </attr>
    </detailed>
    <overview>
      <eaover>The entity and attribute information provided here describes the tabular data associated with the data set. Please review the detailed descriptions that are provided (the individual attribute descriptions) for information on the values that appear as fields/table entries of the data set.</eaover>
      <eadetcit>The entity and attribute information were generated by the individual and/or agency identified as the originator of the data set. Please review the rest of the metadata record for additional details and information.</eadetcit>
    </overview>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>U.S. Geological Survey - ScienceBase</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>Mail Stop 302</address>
          <city>Denver</city>
          <state>CO</state>
          <postal>80225</postal>
          <country>United States</country>
        </cntaddr>
        <cntvoice>1-888-275-8747</cntvoice>
        <cntemail>sciencebase@usgs.gov</cntemail>
      </cntinfo>
    </distrib>
    <distliab>Although these data have been processed successfully on a computer system at the USGS, no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.</distliab>
    <stdorder>
      <digform>
        <digtinfo>
          <formname>Vector Digital Data Sets</formname>
        </digtinfo>
        <digtopt>
          <onlinopt>
            <computer>
              <networka>
                <networkr>https://doi.org/10.5066/P9JH0O1X</networkr>
              </networka>
            </computer>
          </onlinopt>
        </digtopt>
      </digform>
      <fees>None. No fees are applicable for obtaining the dataset.</fees>
    </stdorder>
  </distinfo>
  <metainfo>
    <metd>20240912</metd>
    <metc>
      <cntinfo>
        <cntperp>
          <cntper>Jenny L Hanson</cntper>
          <cntorg>U.S. Geological Survey, MIDCONTINENT REGION</cntorg>
        </cntperp>
        <cntpos>Biologist</cntpos>
        <cntaddr>
          <addrtype>mailing address</addrtype>
          <address>2630 Fanta Reed Road</address>
          <city>La Crosse</city>
          <state>WI</state>
          <postal>54603</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>608-781-6372</cntvoice>
        <cntfax>608-783-6066</cntfax>
        <cntemail>jhanson@usgs.gov</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
  </metainfo>
</metadata>
