<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE metadata SYSTEM "http://thor-f5.er.usgs.gov/ngtoc/metadata/fgdc-std-001-1998.dtd">
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Woolpert</origin>
        <pubdate>20191115</pubdate>
      	<title>OK Panhandle 2018 D18 - Oklahoma City UTM 14 AOI; Hydro Breaklines</title>
        <geoform>Vector digital data</geoform>
      </citeinfo>
    </citation>
  	<descript>
  		<abstract>Product: Lake and stream hydro breakline data in as polygon and polyline feature classes in an Esri file geodatabase; bridge breaklines as point features in Esri shapefile format.
  			Geographic Extent: Approximately 7,176 square miles of QL2 lidar data across four areas of interest throughout Oklahoma; approximately 952 square miles over the Oklahoma City UTM 14 AOI.
      	Dataset Description: The OK Panhandle 2018 D18 lidar project called for the planning, acquisition, processing, and production of derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.71 meters. Project specifications were based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The data was developed based on a horizontal datum/projection of NAD83 (2011) UTM Zone 14, meters (EPSG 6343), and a vertical datum of NAVD88 (GEOID12B) meters. Breaklines are reviewed against lidar intensity imagery to verify completeness of capture. The compilation procedure included use of lidar intensity, bare earth surface model, point cloud data, and open source imagery in an effort to manually compile hydrologic features in a 2-D environment. Following the compilation phase, a separate process was used to adjust the breakline data to best match the water level at the time of the lidar collection. Any ponds and/or lakes were adjusted to be at or just below the bank and to be at a constant elevation. Any streams were adjusted to be at or just below the bank and to be monotonic. Manual QAQC and peer-based QC review was performed on all delineated data to ensure horizontal placement quality and on all adjusted data to ensure vertical placement quality. Bridge breaklines were also compiled in efforts to generate an accurate DEM product.
      	Ground Conditions: Lidar was collected from January 30, 2019 through March 7, 2019 while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Woolpert established 85 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 316 independent accuracy checkpoints (186 NVA points and 130 VVA points), were collected and used to assess the vertical accuracy of the data. Accuracy testing was performed on a per-UTM zone basis. For the OK Panhandle + OK City UTM z14 AOIs, a total of 51 control points, 125 NVA points, and 80 VVA points were established. These checkpoints were not used to calibrate or post process the data.</abstract>
    	<purpose>This project will support the 3DEP mission, the Natural Resources Conservation Service (NRCS) high resolution elevation enterprise program and the Federal Emergency Management Agency (FEMA) Risk Mapping, Assessment and Planning (MAP) program.</purpose>
      <supplinf>
      	USGS Contract No. G16PC00022; Task Order No. 140G0218F0438; Contractor: Woolpert. Sub-Contractor: SurvTech.
        Breakline File Type = GDB
        Breakline Elevation Units = Meters
        Downhill Treatment Applied = Monotonic
        Type of Hydro Treatment Required = Hydro-flattened
      </supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
        	<begdate>20190130</begdate>
        	<enddate>20190307</enddate>
        </rngdates>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
    	<progress>Complete</progress>
      <update>None planned</update>
    </status>
  	<spdom>
  		<bounding>
  			<westbc>-97.6733327116</westbc>
  			<eastbc>-97.1395108663</eastbc>
  			<northbc>35.7250862571</northbc>
  			<southbc>35.0866077816</southbc>
  		</bounding>
  		<lboundng>
  			<leftbc>619990.013441</leftbc>
  			<rightbc>669304.587431</rightbc>
  			<topbc>3954693.72171</topbc>
  			<bottombc>3883874.27189</bottombc>
  		</lboundng>
  	</spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Model</themekey>
        <themekey>Breaklines</themekey>
        <themekey>Elevation Data</themekey>
        <themekey>Lidar</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>United States</placekey>
      	<placekey>Oklahoma</placekey>
      	<placekey>Cleveland County</placekey>
      	<placekey>Oklahoma County</placekey>
      </place>
    </keywords>
    <accconst>No restrictions apply to these data.</accconst>
    <useconst>None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.
      The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and within the limitations of the data for which it was requested and prepared, in general, and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data. It is not appropriate to use the related graphics as data. Woolpert gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from a Woolpert server, and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully upon Woolpert's computer system, no warranty, expressed or implied, is made regarding the utility of the data on another system, or for general or scientific purposes; nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data.</useconst>
    <native>Microsoft Windows 10; Esri ArcCatalog v10.4; Esri ArcMap 10.4; IPAS Pro v.1.35; LP360 v2018.1.57.4; Leica CloudPro 1.2.4; Novatel Inertial Explorer v8.60.6129; POSPac Software v. 5.3; TerraMatch v18; TerraModeler v18; TerraScan v18.</native>
  </idinfo>
  <dataqual>
    <logic>Data covers the entire area specified for this project. Breaklines were collected in all inland ponds and lakes ~2 acres or greater. These features were flat and level water bodies at a single elevation for each vertex along the bank. The entire water surface edge is at or below the immediate surrounding terrain. Breaklines were collected for all streams and rivers ~100' nominal width or wider. These features are flat and level bank to bank, gradient will follow the surrounding terrain and the water surface will be at or below the surrounding terrain. Streams/river channels will break at culvert locations however not at elevated bridge locations.</logic>
    <complete>All files are inspected to ensure that they conform to the specified file naming conventions, all files load in their correct geographic position, all files conform to the project specifications for file standard and content.</complete>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Woolpert</origin>
            <pubdate>20191115</pubdate>
            <title>Lidar Acquisition</title>
            <geoform>Lidar point cloud</geoform>
            <pubinfo>
            	<pubplace>Dayton, OH</pubplace>
            	<publish>Woolpert</publish>
            </pubinfo>
          </citeinfo>
        </srccite>
        <typesrc>Digital data</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
            	<begdate>20190130</begdate>
            	<enddate>20190307</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>OK Panhandle 2018 D18 - Lidar Point Cloud Data</srccitea>
        <srccontr>This dataset includes airborne lidar data point cloud data acquired as part of this task order. This data was used to create the required derivative lidar products.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Woolpert</origin>
            <pubdate>20191115</pubdate>
            <title>Hydro Breaklines</title>
            <geoform>Vector digital data</geoform>
            <pubinfo>
              <pubplace>Dayton, OH</pubplace>
              <publish>Woolpert</publish>
            </pubinfo>
          </citeinfo>
        </srccite>
        <typesrc>Digital data</typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>20191115</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>OK Panhandle 2018 D18 - Breaklines</srccitea>
        <srccontr>This dataset includes hydro breaklines collected as part of this task order.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Woolpert</origin>
            <pubdate>20191115</pubdate>
            <title>Data extent</title>
            <geoform>Vector digital data</geoform>
            <pubinfo>
              <pubplace>Dayton, OH</pubplace>
              <publish>Woolpert</publish>
            </pubinfo>
          </citeinfo>
        </srccite>
        <typesrc>Digital data</typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>20191115</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>OK Panhandle 2018 D18 - Data Extent</srccitea>
        <srccontr>The data extent was created in shapefile format. The shapefile was buffered by 100-meters. It was used in acquisition planning and to clip the final deliverable data.</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Hydro Breaklines: Class 2 (ground) lidar points was used to create a bare-earth surface model. The compilation procedure included use of lidar intensity, bare-earth surface model, point cloud data, and open source imagery in an effort to compile hydrologic features in a 2-D environment. Elevation values were assigned to all inland ponds and lakes, inland pond and lake islands, and inland stream and river islands, using TerraModeler/LP360 functionality. All ground (Class 2) lidar data inside of the collected inland breaklines were then classified to water (Class 9) using TerraScan macro functionality. A buffer of 0.7 meters was also used around each hydro-flattened feature. These points were moved from ground (Class 2) to Ignored Ground (Class 20). Breaklines are reviewed against lidar intensity imagery and surface models to verify completeness of capture. The horizontal placement of breaklines is compared to terrain features and the breakline elevations are compared to lidar elevations to ensure all breaklines match the lidar within acceptable tolerances. Some deviation is expected between breakline and lidar elevations due to monotonicity, connectivity, and flattening rules that are enforced on the breaklines. Once completeness, horizontal placement, and vertical variance is reviewed, all breaklines are reviewed for topological consistency and data integrity using a combination of Esri Data Reviewer tools. The final lake and stream hydrologic breakline products were delivered as polygon and polyline features in an Esri file geodatabase. Bridge breaklines were delivered as point features in Esri shapefile format. This hydro breakline dataset was used in the processing of the DEM deliverable.</procdesc>
        <srcused>OK Panhandle 2018 D18 - Lidar Point Cloud Data</srcused>
        <srcused>OK Panhandle 2018 D18 - Data Extent</srcused>
        <procdate>20191115</procdate>
        <srcprod>OK Panhandle 2018 D18 - Breaklines</srcprod>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>Universal Transverse Mercator</gridsysn>
        	<utm>
        		<utmzone>14</utmzone>
        		<transmer>
        			<sfctrmer>0.9996</sfctrmer>
        			<longcm>-99.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 of 1983 (2011)</horizdn>
        <ellips>Geodetic Reference System 1980</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altdatum>North American Vertical Datum of 1988</altdatum>
        <altres>0.01</altres>
        <altunits>meters</altunits>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <metainfo>
    <metd>20191115</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Woolpert</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>4454 Idea Center Blvd</address>
          <city>Dayton</city>
          <state>OH</state>
          <postal>45430</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>(937)461-5660</cntvoice>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
  </metainfo>
</metadata>