<?xml version='1.0' encoding='UTF-8'?>
<metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Stephanie Sattler</origin>
        <origin>Jayme Strange</origin>
        <origin>Jenny Hanson</origin>
        <origin>Jason Rohweder</origin>
        <pubdate>20260511</pubdate>
        <title>Upper Mississippi River System Lidar Breaklines</title>
        <geoform>Vector Digital Data Set (Polygon)</geoform>
        <onlink>https://doi.org/10.5066/P96D56BC</onlink>
      </citeinfo>
    </citation>
    <descript>
      <abstract>Lidar data is remotely sensed high-resolution elevation data collected by an airborne collection platform. Using a combination of laser range-finding, GPS positioning and inertial measurement technologies; Lidar instruments are able to make highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures and vegetation. Breaklines are used in surface models to represent a linear feature. These breaklines were used with lidar for hydro-flattening aquatic features.</abstract>
      <purpose>Polygons of the Upper Mississippi River System defined as aquatic areas that do not connect to the main channel of the Mississippi River. Breaklines create a flattened water body and provide a single elevation for every bank vertex defining the water body's perimeter. Minz represents the minimum elevation of the lidar points within two pixels adjacent to the aquatic polygon. Using the Minz value, the polygons may be used to flatten aquatic areas of digital elevation models that were produced with lidar.</purpose>
      <supplinf>These polygons only consist of aquatic areas that are backchannel or off-shore aquatic from the main-channel. These areas were given single minimum elevation values to provide a more aesthetically pleasing DEM during the Tier 2 process, which is where these breaklines originate from. The main channel, side channels and tributaries (not included in this dataset) were flattened by using the method of hydro-enforcement by giving a range of decreasing elevation values as the streams and rivers flowed downstream.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <mdattim>
          <sngdate>
            <caldate>200411</caldate>
          </sngdate>
          <sngdate>
            <caldate>201112</caldate>
          </sngdate>
        </mdattim>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-93.2268</westbc>
        <eastbc>-87.5830</eastbc>
        <northbc>44.9490</northbc>
        <southbc>36.9016</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>aquatic</themekey>
        <themekey>backwaters</themekey>
        <themekey>lakes</themekey>
        <themekey>ponds</themekey>
        <themekey>breaklines</themekey>
        <themekey>lidar</themekey>
        <themekey>digital elevation model</themekey>
        <themekey>minimum elevation</themekey>
        <themekey>elevation</themekey>
        <themekey>hydroflatten</themekey>
      </theme>
      <theme>
        <themekt>USGS Thesaurus</themekt>
        <themekey>geospatial datasets</themekey>
        <themekey>lidar</themekey>
      </theme>
      <theme>
        <themekt>USGS Metadata Identifier</themekt>
        <themekey>USGS:69f263ceb66b017286afb8bd</themekey>
      </theme>
      <place>
        <placekt>Large Rivers</placekt>
        <placekey>Mississippi River</placekey>
        <placekey>Illinois River</placekey>
      </place>
      <place>
        <placekt>State Location</placekt>
        <placekey>Minnesota</placekey>
        <placekey>Wisconsin</placekey>
        <placekey>Iowa</placekey>
        <placekey>Illinois</placekey>
        <placekey>Missouri</placekey>
      </place>
    </keywords>
    <accconst>There are no data access constraints.</accconst>
    <useconst>There are no data use constraints.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Upper Midwest Environmental Sciences Center</cntorg>
          <cntper>UMESC Data Coordinator</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>2630 Fanta Reed Rd</address>
          <city>La Crosse</city>
          <state>WI</state>
          <postal>54603</postal>
        </cntaddr>
        <cntvoice>608-783-6451</cntvoice>
        <cntfax>608-793-6066</cntfax>
        <cntemail>gs-b_umesc_data_management@usgs.gov</cntemail>
      </cntinfo>
    </ptcontac>
    <datacred>These data are a product of the U.S. Army Corps of Engineers’ Upper Mississippi River Restoration (UMRR) Program, Long Term Resource Monitoring (LTRM) element, as distributed by the U.S. Geological Survey, Upper Midwest Environmental Sciences Center, La Crosse, Wisconsin.</datacred>
    <native>Environment as of Metadata Creation: Microsoft [Unknown] Version 6.2 (Build 9200) ; Esri ArcGIS 10.5 (Build 6491) Service Pack N/A (Build N/A)</native>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>Attribute accuracy was compared to digital elevation model to ensure accuracy. The attributes were also checked for any extraneous values.</attraccr>
    </attracc>
    <logic>No formal logical accuracy tests were conducted.</logic>
    <complete>Data set is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details.</complete>
    <posacc>
      <horizpa>
        <horizpar>A formal accuracy assessment of the horizontal positional information in the data set has not been conducted.</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>A formal accuracy assessment of the vertical positional information in the data set has either not been conducted, or is not applicable. Vertical accuracy reports were created for the lidar that developed the breaklines elevation value.</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>UMRR LTRM</origin>
            <pubdate>20151029</pubdate>
            <title>UMRR's LTRM Lidar Tier 2</title>
            <geoform>Raster Digital Data Set</geoform>
            <pubinfo>
              <pubplace>La Crosse, WI</pubplace>
              <publish>UMESC</publish>
            </pubinfo>
            <onlink>https://www.umesc.usgs.gov/rivers/upper_mississippi/reach_1/pool_2/p2_gis_data.html#dem</onlink>
          </citeinfo>
        </srccite>
        <typesrc>Digital and/or Hardcopy Resources</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20110317</begdate>
              <enddate>20111211</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>Source Input 1</srccitea>
        <srccontr>Source information used in support of the development of the data set.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>UMRR LTRM</origin>
            <pubdate>2011</pubdate>
            <title>UMRR LTRM 2010 Land Cover/Use</title>
            <geoform>Vector Digital Data Set</geoform>
            <pubinfo>
              <pubplace>La Crosse,  WI</pubplace>
              <publish>UMESC</publish>
            </pubinfo>
            <onlink>https://www.umesc.usgs.gov/rivers/upper_mississippi/reach_1/pool_2/p2_gis_data.html#dem</onlink>
          </citeinfo>
        </srccite>
        <typesrc>Digital and/or Hardcopy Resources</typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>2010</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>Source Input 2</srccitea>
        <srccontr>Source information used in support of the development of the data set.</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Lidar boundaries, terrestrial and aquatic, were developed using the 2010 LTRM  land cover use polygons and/or manually editing.Each polygon feature was given a code value to distinguish whether the polygon was terrestrial (code 1), the main channel (code 2), off-shore aquatic (code 5), or a tributary (code 7).</procdesc>
        <procdate>201612</procdate>
      </procstep>
      <procstep>
        <procdesc>Using select by attributes in ArcGIS, the off-shore aquatic polygons (code 5) were selected. Any polygon features that were less than the one meter minimum mapping unit and any linear polygon feature less than five meters in width were deleted from the dataset.</procdesc>
        <procdate>201612</procdate>
      </procstep>
      <procstep>
        <procdesc>Selected off-shore aquatic polygons were given a minimum elevation value. This was done using  the QCoherent's LP360 Point Cloud Tasks Conflation tool. The following parameters were used:
1. Use a shapefile containing only off-shore aquatic polygons 2. Source Points: only ground points 3. Conflation Method: Summarize Z, create 2D feature and populate the attribute table with the selected vertical statistics, Minimum Z within 2.00 map units 4. Specify the Output File 5. Apply the settings and run point cloud task</procdesc>
        <procdate>201612</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>G-polygon</sdtstype>
        <ptvctcnt>214</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.6096</absres>
            <ordres>0.6096</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>
  </spref>
  <eainfo>
    <overview>
      <eaover>Polygons of the Upper Mississippi River System defined as aquatic areas that do not connect to the main channel of the Mississippi River. Breaklines create a flattened water body and provide a single elevation for every bank vertex defining the water body's perimeter. Minz represents the minimum elevation of the lidar points within two pixels adjacent to the aquatic polygon. Using the Minz value, the polygons may be used to flatten aquatic areas of digital elevation models that were produced with lidar. 

The zip file of the dataset contains metadata specific to each pool shapefile.</eaover>
      <eadetcit>https://doi.org/10.5066/P96D56BC
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</cntorg>
          <cntper>GS ScienceBase</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing address</addrtype>
          <address>Denver Federal Center, Building 810, 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 U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, 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.</distliab>
    <stdorder>
      <digform>
        <digtinfo>
          <formname>Vector Digital Data Set (Polygon)</formname>
        </digtinfo>
        <digtopt>
          <onlinopt>
            <computer>
              <networka>
                <networkr>https://doi.org/10.5066/P96D56BC</networkr>
              </networka>
            </computer>
          </onlinopt>
        </digtopt>
      </digform>
      <fees>None. No fees are applicable for obtaining the data set.</fees>
    </stdorder>
  </distinfo>
  <metainfo>
    <metd>20260511</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Upper Midwest Environmental Sciences Center</cntorg>
          <cntper>UMESC Data Coordinator</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>2630 Fanta Reed Rd</address>
          <city>La Crosse</city>
          <state>WI</state>
          <postal>54603</postal>
        </cntaddr>
        <cntvoice>608-783-6451</cntvoice>
        <cntfax>608-793-6066</cntfax>
        <cntemail>gs-b_umesc_data_management@usgs.gov</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
  </metainfo>
</metadata>
