<?xml version="1.0" encoding="UTF-8"?>
<inport-metadata xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 version="1.11"
                 source="https://www.fisheries.noaa.gov">
   <item-identification>
      <catalog-item-id>70095</catalog-item-id>
      <title>2020 - 2021 USGS Lidar: Ohio Statewide - Phase 2</title>
      <short-name>oh2020_phase2_m9845_metadata</short-name>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49401</parent-catalog-item-id>
      <parent-title>Lidar - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <creation-date>2020</creation-date>
      <publication-date>2022-05-20</publication-date>
      <abstract>Product: Processed, classified lidar point cloud data tiles in LAS 1.4 format.
Geographic Extent: Approximately 12,101 square miles in southern Ohio
Dataset Description: The OH Statewide Phase 2 2020 B20 lidar project called for the planning, acquisition, processing, and production of derivative products of QL1 lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications were based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2021 revision A. The data was developed based on a horizontal reference system of NAD83 (2011) State Plane Ohio North (FIPS 3401) (EPSG 6549) and South (FIPS 3402) (EPSG 6551) and a vertical reference system of NAVD88 (GEOID18) US Survey Feet. Lidar data was delivered as processed LAS 1.4 files formatted to 1,250-feet by 1,250-feet tiles. Lidar was collected 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  ground control points that were used to calibrate the lidar to known ground locations established throughout the entire project area. Additional independent accuracy checkpoints (NVA and VVA points), were collected throughout the entire project area and used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.

Block 1 (Work Unit 197533)
Counties included: Fairfield, Gallia, Morgan
Formatted to 19,553 tiles, covering approximately 1096 square miles.
Lidar was collected from Dec 11, 2020 through April 11, 2021. 
Woolpert established 73 ground control points and an additional 89 independent accuracy checkpoints (50 NVA points and 39 VVA points)

Block 2 (Work Unit 224682)
Counties included: Athens, Hocking, Meigs, Perry, Pickaway, Ross, Vinton, Washington
Formatted to 28,701 tiles, covering approximately 1609 square miles.
Lidar was collected from March 7 through April 13, 2021. 
Woolpert established 20 ground control points and an additional 48 independent accuracy checkpoints (27 NVA points and 21 VVA points)

Block 3 (Work Unit 224906)
Counties included: Athens, Belmont, Monroe, Muskingum, Noble, Washington
Formatted to 27,537 tiles, covering approximately 1544 square miles.
Lidar was collected from Jan 23 through March 29, 2021. 
Woolpert established 18 ground control points and an additional 47 independent accuracy checkpoints (23 NVA points and 24 VVA points)

Block 4 (Work Unit 224909)
Counties included: Licking, Muskingum, Perry
Formatted to 27,476 tiles, covering approximately 1540 square miles.
Lidar was collected from March 10 through April 3, 2021. 
Woolpert established 26 ground control points and an additional 46 independent accuracy checkpoints (27 NVA points and 19 VVA points)

Block 5 (Work Unit 224912)
Counties included: Guernsey, Belmont
Formatted to 19,255 tiles, covering approximately 1080 square miles.
Lidar was collected from March 21 through April 22, 2021. 
Woolpert established 12 ground control points and an additional 42 independent accuracy checkpoints (24 NVA points and 18 VVA points)

Block 6 (Work Unit 224915)
Counties included: Coshocton, Holmes, Knox, Tuscarawas
Formatted to 26,822 tiles, covering approximately 1503 square miles.
Lidar was collected from Nov 19, 2020 through April 5, 2021. 
Woolpert established 17 ground control points and an additional 49 independent accuracy checkpoints (26 NVA points and 23 VVA points)

Block 7 (Work Unit 224919)
Counties included: Carroll, Harrison, Jefferson, Tuscarawas
Formatted to 24,656 tiles, covering approximately 1382 square miles.
Lidar was collected from Nov 24, 2020 through April 19, 2021. 
Woolpert established 14 ground control points and an additional 48 independent accuracy checkpoints (25 NVA points and 23 VVA points)

Block 8 (Work Unit 224925)
Counties included: Carroll, Columbiana, Holmes, Mahoning, Stark, Tuscarawas, Wayne
Formatted to 42,505 tiles, covering approximately 1503 square miles.
Lidar was collected from May 19, 2020 through April 19, 2021. 
Woolpert established 45 ground control points and an additional 77 independent accuracy checkpoints (52 NVA points and 25 VVA points)

This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.
</abstract>
      <purpose>The 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.</purpose>
      <supplemental-information>USGS Contract No. G16PC00022, Task Order No. 140G0220F0194. Contractor: Woolpert.
   The following are the USGS lidar fields in JSON:
              {
                

    "ldrinfo" : {
              

    "ldrspec" : "USGS NGP Base Specifications v2021 rev A",

    "ldrsens" : "Leica Terrain Mapper",

    "ldrmaxnr" : "15",

    "ldrnps" : "0.35",

    "ldrdens" : "8",

    "ldranps" : "0.35",

    "ldradens" : "8",

    "ldrfltht" : "1372",

    "ldrfltsp" : "160",

    "ldrscana" : "40",

    "ldrscanr" : "150",

    "ldrpulsr" : "1600",

    "ldrpulsd" : "5",

    "ldrpulsw" : "2.5",

    "ldrwavel" : "1064",

    "ldrmpia" : "1",

    "ldrbmdiv" : "0.25",

    "ldrswatw" : "1456",

    "ldrswato" : "25",

    "ldrgeoid" : "GEOID18"
  },

    "ldraccur" : {
              

    "ldrchacc" : "0",

    "rawnva" : "0",

    "rawnvan" : "0",

    "clsnva" : "0",

    "clsnvan" : "0",

    "clsvva" : "0",

    "clsvvan" : "0"
  },

    "lasinfo" : {
              

    "lasver" : "1.4",

    "lasprf" : "6",

    "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.",

    "lasolap" : "Swath "overage" points were identified in these files using the standard LAS overlap bit.",

    "lasintr" : "16",

    "lasclass" : {
              

    "clascode" : "1",

    "clasitem" : "Processed but not classified"
  },

    "lasclass" : {
              

    "clascode" : "2",

    "clasitem" : "Bare earth ground"
  },

    "lasclass" : {
              

    "clascode" : "7",

    "clasitem" : "Noise"
  },

    "lasclass" : {
              

    "clascode" : "9",

    "clasitem" : "Water"
  },

    "lasclass" : {
              

    "clascode" : "17",

    "clasitem" : "Bridge decks"
  },

    "lasclass" : {
              

    "clascode" : "18",

    "clasitem" : "High noise"
  },

    "lasclass" : {
              

    "clascode" : "20",

    "clasitem" : "Ignored ground"
  }
  }}</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="74ed1690-968e-444c-8a31-7b8344a2aad3">EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="753f915c-70d4-49e1-9bd5-83e75f461e30">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="c23966c4-9e16-484c-a1ef-efcd2354d71c">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; OHIO</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="90761f8d-6abe-499c-b711-acec394daa59">VERTICAL LOCATION &gt; LAND SURFACE</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Instrument</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Instrument Keywords</thesaurus>
         <keyword identifier="7166c458-f935-4bd9-a322-d92830cf0c33">LIDAR &gt; Light Detection and Ranging</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Platform</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Platform Keywords</thesaurus>
         <keyword identifier="8b7834c1-2c66-414e-a655-2298e7dcc479">Airplane &gt; Airplane</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office for Coastal Management</organization>
      <city>Charleston</city>
      <state-province>SC</state-province>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <data-set-type>Elevation</data-set-type>
      <maintenance-frequency>None Planned</maintenance-frequency>
      <data-presentation-form>Model (digital)</data-presentation-form>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Woolpert, USGS</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1255621" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2023</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1255620" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2023</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1255675" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2022</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>U.S. Geological Survey</contact-name>
         <contact-address>12201 Sunrise Valley Drive </contact-address>
         <contact-address-city>Reston</contact-address-city>
         <contact-address-state>VA</contact-address-state>
         <contact-address-zip>20191</contact-address-zip>
         <contact-address-country>USA</contact-address-country>
         <contact-url>https://usgs.gov</contact-url>
         <contact-url-name>USGS Home</contact-url-name>
         <contact-url-description>Home page for USGS</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1255622" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2023</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1255623" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2023</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
   </support-roles>
   <extents>
      <currentness-reference>Ground Condition</currentness-reference>
      <extent cc-id="1255680">
         <geographic-areas>
            <geographic-area cc-id="1255681">
               <west-bound>-82.77</west-bound>
               <east-bound>-81.68</east-bound>
               <north-bound>39.75</north-bound>
               <south-bound>38.87</south-bound>
               <description>Block 2 (Work Unit 224682) - Includes Athens, Hocking, Meigs, Perry, Pickaway, Ross, Vinton, Washington counties</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1255682">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2021-03-07</start-date-time>
               <end-date-time>2021-04-13</end-date-time>
               <description>Dates of collection for Block 2</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1255676">
         <geographic-areas>
            <geographic-area cc-id="1255677">
               <west-bound>-82.87</west-bound>
               <east-bound>-81.57</east-bound>
               <north-bound>39.97</north-bound>
               <south-bound>38.83</south-bound>
               <description>Block 1 (Work Unit 197533) - Includes Fairfield, Gallia, and Morgan counties</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1255678">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2020-12-11</start-date-time>
               <end-date-time>2021-04-11</end-date-time>
               <description>Dates of collection for Block 1</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1255683">
         <geographic-areas>
            <geographic-area cc-id="1255684">
               <west-bound>-81.85</west-bound>
               <east-bound>-80.78</east-bound>
               <north-bound>39.91</north-bound>
               <south-bound>39.26</south-bound>
               <description>Block 3 (Work Unit 224906) - Includes Athens, Belmont, Monroe, Muskingum, Noble, and Washington counties</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1255685">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2021-01-23</start-date-time>
               <end-date-time>2021-03-29</end-date-time>
               <description>Dates of collection for Block 3</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1255686">
         <geographic-areas>
            <geographic-area cc-id="1255687">
               <west-bound>-82.81</west-bound>
               <east-bound>-81.72</east-bound>
               <north-bound>40.28</north-bound>
               <south-bound>39.73</south-bound>
               <description>Block 4 (Work Unit 224909) - Includes Licking, Muskingum, and Perry counties</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1255688">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2021-03-10</start-date-time>
               <end-date-time>2021-04-03</end-date-time>
               <description>Dates of collection for Block 4</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1255689">
         <geographic-areas>
            <geographic-area cc-id="1255690">
               <west-bound>-81.74</west-bound>
               <east-bound>-80.7</east-bound>
               <north-bound>40.23</north-bound>
               <south-bound>39.82</south-bound>
               <description>Block 5  (Work Unit 224912) - Includes Belmont and Guernsey counties</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1255691">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2021-03-21</start-date-time>
               <end-date-time>2021-04-22</end-date-time>
               <description>Dates of collection for Block 5</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1255692">
         <geographic-areas>
            <geographic-area cc-id="1255693">
               <west-bound>-82.78</west-bound>
               <east-bound>-81.55</east-bound>
               <north-bound>40.6</north-bound>
               <south-bound>40.12</south-bound>
               <description>Block 6 (Work Unit 224915) - Includes Coshocton, Holmes, Knox, Tuscarawas counties</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1255694">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2020-11-19</start-date-time>
               <end-date-time>2021-04-05</end-date-time>
               <description>Dates of collection for Block 6</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1255695">
         <geographic-areas>
            <geographic-area cc-id="1255696">
               <west-bound>-81.56</west-bound>
               <east-bound>-80.59</east-bound>
               <north-bound>40.6</north-bound>
               <south-bound>40.15</south-bound>
               <description>Block 7 (Work Unit 224919) - Includes Carroll, Harrison, Jefferson, Tuscarawas counties</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1255697">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2020-11-24</start-date-time>
               <end-date-time>2021-04-19</end-date-time>
               <description>Dates of collection for Block 7</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1255698">
         <geographic-areas>
            <geographic-area cc-id="1255699">
               <west-bound>-82.21</west-bound>
               <east-bound>-80.51</east-bound>
               <north-bound>41.13</north-bound>
               <south-bound>40.57</south-bound>
               <description>Block 8 (Work Unit 224925) - Includes Carroll, Columbiana, Holmes, Mahoning, Stark, Tuscarawas, and Wayne counties</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1255700">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2020-05-19</start-date-time>
               <end-date-time>2021-04-19</end-date-time>
               <description>Dates of collection for Block 8</description>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <grid>No</grid>
            <vector>Yes</vector>
            <text-table>No</text-table>
            <tin>No</tin>
            <stereo-model>No</stereo-model>
            <video>No</video>
         </representations-used>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Projected</crs-type>
               <epsg-code>EPSG:3857</epsg-code>
               <epsg-name>WGS 84 / Pseudo-Mercator</epsg-name>
               <datum-name>World Geodetic System 1984</datum-name>
               <ellipsoid>WGS 84</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257223563</flattening-ratio>
               <base-crs-name>WGS 84</base-crs-name>
               <projection-name>Popular Visualisation Pseudo-Mercator</projection-name>
               <conversion-method>Popular Visualisation Pseudo Mercator</conversion-method>
               <parameters>
                  <parameter>
                     <parameter-name>Latitude of natural origin</parameter-name>
                     <parameter-value>0° 0' 0" N</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Longitude of natural origin</parameter-name>
                     <parameter-value>0° 0' 0" E</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>False easting</parameter-name>
                     <parameter-value>0</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
                  <parameter>
                     <parameter-name>False northing</parameter-name>
                     <parameter-value>0</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
               </parameters>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Easting</name>
                     <abbreviation>X</abbreviation>
                     <units>metre</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Northing</name>
                     <abbreviation>Y</abbreviation>
                     <units>metre</units>
                     <orientation>north</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Vertical</crs-type>
               <epsg-code>EPSG:5703</epsg-code>
               <epsg-name>NAVD88 height</epsg-name>
               <datum-name>North American Vertical Datum 1988</datum-name>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Gravity-related height</name>
                     <abbreviation>H</abbreviation>
                     <units>metre</units>
                     <orientation>up</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <security-class>Unclassified</security-class>
      <data-access-procedure>Data is available online for bulk and custom downloads.</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <data-use-constraints>Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="1255627">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9845/details/9845</download-url>
         <distributor cc-id="1255620">
            <from-date>2023</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options.</description>
         <!--Note: file-type is deprecated-->
         <file-type>Zip</file-type>
         <compression>Zip</compression>
      </distribution>
      <distribution cc-id="1255628">
         <download-url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/OH_Statewide_Phase2_2020_B20/</download-url>
         <distributor cc-id="1255675">
            <from-date>2022</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>U.S. Geological Survey</contact-name>
         </distributor>
         <file-name>Bulk Download</file-name>
         <description>Bulk download of data files in LAZ format, Ohio State Plane North or South NAD83(2011), US survey feet coordinates and NAVD88 (Geoid18) heights in feet .</description>
         <!--Note: file-type is deprecated-->
         <file-type>LAZ</file-type>
         <distribution-format>LAS/LAZ - LASer</distribution-format>
         <compression>Zip</compression>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="1255618">
         <url>https://coast.noaa.gov/dataviewer/</url>
         <name>NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>HTML</file-resource-format>
         <description>The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.</description>
      </url>
      <url cc-id="1255704">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/</url>
         <name>USGS Additional Info</name>
         <url-type>Online Resource</url-type>
         <description>Link to the reports, breaklines, metadata, and spatial metadata.</description>
      </url>
      <url cc-id="1255705">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/OH_Statewide_Phase2_1_2020/reports/OH_Statewide_Phase_2_197536_WU_197533.pdf</url>
         <name>Lidar Report - Block 1 (Work Unit 197533)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Woolpert lidar report for Block 1 (Work Unit 197533).</description>
      </url>
      <url cc-id="1255706">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/OH_Statewide_Phase2_2_2020/reports/OH_Statewide_Phase_2_197536_WU_224682.pdf</url>
         <name>Lidar Report - Block 2 (Work Unit 224682)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Woolpert lidar report for Block 2 (Work Unit 224682).</description>
      </url>
      <url cc-id="1255707">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/OH_Statewide_Phase2_3_2020/reports/OH_Statewide_Phase_2_197536_WU_224906.pdf</url>
         <name>Lidar Report - Block 3 (Work Unit 224906)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Woolpert lidar report for Block 3 (Work Unit 224906).</description>
      </url>
      <url cc-id="1255708">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/OH_Statewide_Phase2_4_2020/reports/OH_Statewide_Phase_2_197536_WU224909.pdf</url>
         <name>Lidar Report - Block 4 (Work Unit 224909)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Woolpert lidar report for Block 4 (Work Unit 224909).</description>
      </url>
      <url cc-id="1255709">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/OH_Statewide_Phase2_5_2020/reports/OH_Statewide_Phase_2_197536_WU_224912.pdf</url>
         <name>Lidar Report - Block 5 (Work Unit 224912)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Woolpert lidar report for Block 5 (Work Unit 224912).</description>
      </url>
      <url cc-id="1255710">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/OH_Statewide_Phase2_6_2020/reports/OH_Statewide_Phase_2_197536_WU_224915.pdf</url>
         <name>Lidar Report - Block 6 (Work Unit 224915)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Woolpert lidar report for Block 6 (Work Unit 224915).</description>
      </url>
      <url cc-id="1255711">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/OH_Statewide_Phase2_7_2020/reports/OH_Statewide_Phase_2_197536_WU_224919.pdf</url>
         <name>Lidar Report - Block 7 (Work Unit 224919)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Woolpert lidar report for Block 7 (Work Unit 224919).</description>
      </url>
      <url cc-id="1255712">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/OH_Statewide_Phase2_8_2020/reports/OH_Statewide_Phase_2_197536_WU_224925.pdf</url>
         <name>Lidar Report - Block 8 (Work Unit 224925)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Woolpert lidar report for Block 8 (Work Unit 224925).</description>
      </url>
      <url cc-id="1255703">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase2_2020_B20/USGS_OH_Statewide_Phase2_2020_B20_Project_Report.pdf</url>
         <name>USGS Project Report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the USGS Project Report that provides information about the project, vertical accuracy results, and the point classes and sensors used.</description>
      </url>
      <url cc-id="1255713">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_1_2020/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - Block 1</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1255714">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_2_2020/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - Block 2</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1255715">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_3_2020/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - Block 3</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1255716">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_4_2020/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - Block 4</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1255717">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_5_2020/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - Block 5</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1255718">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_6_2020/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - Block 6</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1255719">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_7_2020/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - Block 7</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1255720">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_8_2020/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - Block 8</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1255721">
         <url>https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_1_2020/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_2_2020/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_3_2020/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_4_2020/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_5_2020/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_6_2020/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_7_2020/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_8_2020/ept.json%22]</url>
         <name>USGS 3D View</name>
         <url-type>Online Resource</url-type>
         <description>Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer.</description>
      </url>
   </urls>
   <technical-environment>
      <description>Microsoft Windows 10 Version 1803 (Build 17134.1304); ArcMap 10.7; ArcCatalog 10.7; TerraScan ver. 20; TerraModeler ver. 20; LP360 v2019.1.30.4.</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>Block 1
The data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 0.101 ft (3.1 cm) RMSEx / RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 0.250 ft (7.62 cm) at a 95% confidence level.

Blocks 2 - 8
The data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 14.8 cm RMSEx / RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 36.3 cm at a 95% confidence level.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.

USGS Determined Vertical Accuracy:

Non-Vegetated Vertical Accuracy (NVA) = 7.56 cm at 95% Confidence Level or 3.86 cm RMSE

Vegetated Vertical Accuracy (VVA) = 15.33 cm at 95th Percentile</vertical-positional-accuracy>
      <completeness-report>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.</completeness-report>
      <conceptual-consistency>Data covers the entire area specified for this project.</conceptual-consistency>
   </data-quality>
   <data-management>
      <resources-identified>Yes</resources-identified>
      <resources-budget-percentage>Unknown</resources-budget-percentage>
      <data-access-directive-compliant>Yes</data-access-directive-compliant>
      <archive-location>NCEI-CO</archive-location>
      <data-protection-plan>Data is backed up to tape and to cloud storage.</data-protection-plan>
   </data-management>
   <lineage>
      <lineage-statement>The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tile (EPT) files hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.</lineage-statement>
      <lineage-sources>
         <lineage-source cc-id="1255824">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_2_2020/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile for OH_Statewide_Phase2_2_2020</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1255825">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_1_2020/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile for OH_Statewide_Phase2_1_2020</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1255826">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_3_2020/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile for OH_Statewide_Phase2_3_2020</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1255827">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_4_2020/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile for OH_Statewide_Phase2_4_2020</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1255828">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_5_2020/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile for OH_Statewide_Phase2_5_2020</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1255829">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_6_2020/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile for OH_Statewide_Phase2_6_2020</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1255830">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_7_2020/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile for OH_Statewide_Phase2_7_2020</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1255831">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_8_2020/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile for OH_Statewide_Phase2_8_2020</citation-url-name>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1255613">
            <sequence-number>1</sequence-number>
            <description>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), Bridge Decks (Class 17), High Noise (Class 18), and Ignored Ground (Class 20). 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 0.7 meters 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. 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. 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.</description>
            <process-date-time>2022-05-20T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1255832">
            <sequence-number>2</sequence-number>
            <description>Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and the vertical units were converted to meters (NAVD88 Geoid18).</description>
            <process-contact>
               <contact-type>Organization</contact-type>
               <contact-name>U.S. Geological Survey</contact-name>
               <contact-address>12201 Sunrise Valley Drive </contact-address>
               <contact-address-city>Reston</contact-address-city>
               <contact-address-state>VA</contact-address-state>
               <contact-address-zip>20191</contact-address-zip>
               <contact-address-country>USA</contact-address-country>
               <contact-url>https://usgs.gov</contact-url>
               <contact-url-name>USGS Home</contact-url-name>
               <contact-url-description>Home page for USGS</contact-url-description>
               <contact-url-function>Online Resource</contact-url-function>
            </process-contact>
         </lineage-process-step>
         <lineage-process-step cc-id="1255833">
            <sequence-number>3</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container.

These are the AWS URLs being accessed:

https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_1_2020/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_2_2020/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_3_2020/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_4_2020/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_5_2020/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_6_2020/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_7_2020/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase2_8_2020/ept.json</description>
            <process-date-time>2023-06-06T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Organization</contact-type>
               <contact-name>Office for Coastal Management</contact-name>
               <contact-noaa-acronym>OCM</contact-noaa-acronym>
               <contact-ror>https://ror.org/05v14bq57</contact-ror>
               <contact-address>2234 South Hobson Avenue</contact-address>
               <contact-address-city>Charleston</contact-address-city>
               <contact-address-state>SC</contact-address-state>
               <contact-address-zip>29405-2413</contact-address-zip>
               <contact-url>https://www.coast.noaa.gov/</contact-url>
            </process-contact>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <related-items>
      <related-item>
         <catalog-item-id>80073</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2020 - 2021 USGS Lidar DEM: Ohio Statewide - Phase 2</title>
         <relationship-type>Cross Reference</relationship-type>
      </related-item>
   </related-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:70095</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2023-06-05T20:45:38</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2026-03-04T19:17:17</metadata-record-last-modified>
      <record-published>2023-06-07</record-published>
      <owner-organization>OCM Partners</owner-organization>
      <owner-organization-acronym>OCMP</owner-organization-acronym>
      <owner-organization-address/>
      <owner-organization-address-city/>
      <owner-organization-address-state/>
      <owner-organization-address-zip/>
      <owner-organization-address-country/>
      <owner-organization-phone/>
      <owner-organization-url/>
      <owner-organization-business-hours/>
      <owner-organization-group-id>1002</owner-organization-group-id>
      <publication-status>Public</publication-status>
      <limited-metadata-available>No</limited-metadata-available>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2023-06-07</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2024-06-07</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
