<?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>20180830</pubdate>
        <title>OH Clinton Delaware 2018 B18 - Delaware County; Classified Point Cloud</title>
        <geoform>Lidar point cloud</geoform>
      </citeinfo>
    </citation>
    <descript>
      <abstract>Product: Processed, classified lidar point cloud data tiles in LAS 1.4 format.
        Geographic Extent: Approximately 926 square miles across Clinton and Delaware Counties, Ohio.
        Dataset Description: The OH Clinton Delaware 2018 B18 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 (HARN) State Plane Ohio North Zone, US Survey Feet, and a vertical datum of NAVD88 (GEOID12B), US Survey Feet. Lidar data was delivered as processed LAS 1.4 files formatted to 570 individual 5,000-foot x 5,000-foot tiles.
        Ground Conditions: Lidar was collected by Woolpert in a total of 3 missions from March 6, 2018 through April 27, 2018, 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 9 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 60 independent accuracy checkpoints (35 NVA points and 25 VVA points), were collected and used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
        Note: Due to flooding around the Delaware Lake area, 25 tiles were withheld from this dataset. The following tiles will be re-produced after the area is re-flown in Fall 2018, when leaf-off conditions are present: N1805250, N1805255, N1805260, N1805265, N1805270, N1805275, N1805280, N1810250, N1810255, N1810260, N1810265, N1810270, N1810275, N1810280, N1815250, N1815255, N1815260, N1815265, N1815270, N1815275, N1815280, N1820265, N1820270, N1820275, N1825270.</abstract>
      <purpose>Data was collected as part of this task order to be used for the following: terrain mapping, conservation planning and design, support of easement/land stewardship programs, support of special emphasis programs, support of soil projects, fill gaps in existing lidar, water resource management.</purpose>
      <supplinf>USGS Contract No. G16PC0022, Task Order No. 140G0218F0168. Contractor: Woolpert.</supplinf>
      <lidar>
        <ldrinfo>
          <ldrspec>USGS NGP Base Specifications v1.3</ldrspec>
          <ldrsens>Leica ALS80</ldrsens>
          <ldrmaxnr>Unlimited</ldrmaxnr>
          <ldrnps>0.7</ldrnps>
          <ldrdens>2</ldrdens>
          <ldranps>0.7</ldranps>
          <ldradens>2</ldradens>
          <ldrfltht>2377</ldrfltht>
          <ldrfltsp>150</ldrfltsp>
          <ldrscana>40</ldrscana>
          <ldrscanr>35.5</ldrscanr>
          <ldrpulsr>346</ldrpulsr>
          <ldrpulsd>5</ldrpulsd>
          <ldrpulsw>2.5</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.20</ldrbmdiv>
          <ldrswatw>1731</ldrswatw>
          <ldrswato>25.5</ldrswato>
          <ldrgeoid>GEOID12B</ldrgeoid>
        </ldrinfo>
        <ldraccur>
          <ldrchacc>0</ldrchacc>
          <rawnva>0.070</rawnva>
          <rawnvan>35</rawnvan>
          <clsnva>0.072</clsnva>
          <clsnvan>35</clsnvan>
          <clsvva>0.122</clsvva>
          <clsvvan>25</clsvvan>
        </ldraccur>
        <lasinfo>
          <lasver>1.4</lasver>
          <lasprf>6</lasprf>
          <laswheld>Geometrically unreliable points were identified using a combination of automated and manual techniques and subsequently classified as high or low noise and given the standard Withheld bit.</laswheld>
          <lasolap>Swath "overage" points were identified in these files using the standard LAS overlap bit.</lasolap>
          <lasintr>16</lasintr>
          <lasclass>
            <clascode>1</clascode>
            <clasitem>Processed but not classified</clasitem>
          </lasclass>
          <lasclass>
            <clascode>2</clascode>
            <clasitem>Bare earth ground</clasitem>
          </lasclass>
          <lasclass>
            <clascode>7</clascode>
            <clasitem>Noise</clasitem>
          </lasclass>
          <lasclass>
            <clascode>9</clascode>
            <clasitem>Water</clasitem>
          </lasclass>
          <lasclass>
            <clascode>17</clascode>
            <clasitem>Bridge Decks</clasitem>
          </lasclass>
          <lasclass>
            <clascode>18</clascode>
            <clasitem>High Noise</clasitem>
          </lasclass>
          <lasclass>
            <clascode>20</clascode>
            <clasitem>Ignored ground</clasitem>
          </lasclass>
        </lasinfo>
      </lidar>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20180306</begdate>
          <enddate>20180427</enddate>
        </rngdates>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-83.2670859803</westbc>
        <eastbc>-82.7277328715</eastbc>
        <northbc>40.4477677932</northbc>
        <southbc>40.1186897571</southbc>
      </bounding>
      <lboundng>
        <leftbc>1755000.0</leftbc>
        <rightbc>1905000.0</rightbc>
        <topbc>285000.0</topbc>
        <bottombc>165000.0</bottombc>
      </lboundng>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Lidar</themekey>
        <themekey>LAS Point Cloud</themekey>
        <themekey>Classified LAS</themekey>
        <themekey>Elevation Data</themekey>
        <themekey>Remote Sensing</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>United States</placekey>
        <placekey>Ohio</placekey>
        <placekey>Delaware County</placekey>
      </place>
    </keywords>
    <accconst>No restrictions apply to this 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 Version 1607 (Build 14393.2189); ArcMap 10.4; ArcCatalog 10.4; TerraModeler ver. 18; Geocue 2017.2.20.0, POSPac Software v. 5.3, IPAS Pro v.1.35, Novatel Inertial Explorer v8.60.6129, TerraMatch v.18.03, Leica Cloud Pro v1.2.3, TerraScan v.18.18</native>
  </idinfo>
  <dataqual>
    <logic>Data covers the entire area specified for this project.</logic>
    <complete>These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist.</complete>
    <posacc>
      <vertacc>
        <vertaccr>The project specifications require that only Non-Vegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. The required accuracy (ACCz) is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm in non-vegetated land cover classes. The NVA was tested with 35 checkpoints located in bare earth and urban (non-vegetated) areas. These check points were not used in the calibration or post processing of the lidar point cloud data. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. See survey report for additional survey methodologies. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control points. AccuracyZ has been tested to meet 19.6 cm or better Non-Vegetated Vertical Accuracy at 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standard for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</vertaccr>
        <qvertpa>
          <vertaccv>0.070</vertaccv>
          <vertacce>Tested 0.070 meters NVA at a 95% confidence level using RMSE(z) 0.036 ft x 1.9600 as defined by the National Standard for Spatial Data Accuracy (NSSDA). The NVA of the raw lidar point cloud swath files was calculated against TINs derived from the final calibrated and controlled swath data using 35 independent checkpoints located in non-vegetated land cover categories.</vertacce>
        </qvertpa>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Woolpert</origin>
            <pubdate>20180830</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>20180306</begdate>
              <enddate>20180427</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>OH Clinton Delaware 2018 B18 - 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>20180830</pubdate>
            <title>Survey Control Acquisition</title>
            <geoform>Vector digital data and tabular digital data</geoform>
            <pubinfo>
              <pubplace>Dayton, OH</pubplace>
              <publish>Woolpert</publish>
            </pubinfo>
          </citeinfo>
        </srccite>
        <typesrc>Digital data</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20180329</begdate>
              <enddate>20180330</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>OH Clinton Delaware 2018 B18 - Surveyed Control Points</srccitea>
        <srccontr>This dataset includes ground control and QA/QC checkpoints collected as part of this task order. These points were used in the calibration and accuracy testing of the lidar point cloud and DEM data.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Woolpert</origin>
            <pubdate>20180830</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>20180830</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>OH Clinton Delaware 2018 B18 - Breaklines</srccitea>
        <srccontr>This dataset includes hydro breaklines collected as part of this task order.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Woolpert</origin>
            <pubdate>20180830</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>20180830</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>OH Clinton Delaware 2018 B18 - 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>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>USGS</origin>
            <pubdate>20180830</pubdate>
            <title>Tile index</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>20180830</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>OH Clinton Delaware 2018 B18 - Tile Index</srccitea>
        <srccontr>The tile index was created in shapefile format. The tiles have a size of 5,000-feet x 5,000-feet. The file naming convention is as follows: nxxxyyy (Ohio North Zone); Please note that xxx and yyy represent the easting and northing coordinates (respectively) in state plane feet. This index was used to create the tiled deliverables for this project.</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Lidar Point Cloud Classification: The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" lidar returns. This process determined Processed, but Unclassified (Class 1), Bare Earth Ground (Class 2), Low Noise (Class 7), Water (Class 9), Ignored Ground (Class 20), Bridge Decks (Class 17) and High Noise (Class 18). The bare-earth (Class 2 Ground) lidar points underwent a manual QA/QC step to verify the quality of the DEM as well as a peer-based QC review. This included a review of the DEM surface to remove artifacts and ensure topographic quality. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through a semi-automated process. All ground (Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (Class 9) using TerraScan/LP360 macro functionality. A buffer of 1.14 feet was also used around each hydro-flattened feature to classify these ground (Class 2) points to Ignored Ground (Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Woolpert proprietary software and LP360 was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.</procdesc>
        <srcused>OH Clinton Delaware 2018 B18 - Lidar Point Cloud Data</srcused>
        <srcused>OH Clinton Delaware 2018 B18- Surveyed Control Points</srcused>
        <srcused>OH Clinton Delaware 2018 B18 - Data Extent</srcused>
        <srcused>OH Clinton Delaware 2018 B18 - Tile Index</srcused>
        <procdate>20180830</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Point</direct>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>State Plane Coordinate System 1983</gridsysn>
          <spcs>
            <spcszone>3401</spcszone>
            <lambertc>
              <stdparll>40.43333333333333</stdparll>
              <stdparll>41.7</stdparll>
              <longcm>-82.5</longcm>
              <latprjo>39.66666666666666</latprjo>
              <feast>1968500.0</feast>
              <fnorth>0.0</fnorth>
            </lambertc>
          </spcs>
        </gridsys>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.01</absres>
            <ordres>0.01</ordres>
          </coordrep>
          <plandu>survey feet</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>North American Datum of 1983 (HARN)</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>feet</altunits>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <metainfo>
    <metd>20180830</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>