<?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>69414</catalog-item-id>
      <title>2019 - 2020 USGS Lidar: NY FEMA Region 2 Central</title>
      <short-name>ny2019_fema_r2_m9770_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>2019</creation-date>
      <publication-date>2022-03-17</publication-date>
      <abstract>Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.

Geographic Extent: 
Block 1: Niagara, Putnam and Westchester Counties covering approximately 1,367 square miles.
Block 2: Lewis, Oneida, Herkimer, Fulton, and Montgomery Counties covering approximately 2,396 square miles.
Block 3: Monroe, Ontario, Steuben, Onondaga, Cortland, Chenango, and Madison Counties covering approximately 2,806 square miles.
Block 4: Albany, Greene, Hamilton and Schenectady Counties covering approximately 3,167 square miles. 
Block 5: Broome, Chemung, Chenango, Cortland, Delaware, Ontario, Otsego, Schuyler, Steuben, Sullivan, Tioga, Yates Counties covering approximately 6,198 square miles. 


Dataset Description: NY_FEMAR2_Central_2018_D19 Lidar Project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83 (2011), Albers Equal Area, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles as tiled bare earth DEMs; all tiled to the same 1000 m x 1000 m schema. 

Ground Conditions: Lidar was collected in early 2019 through mid 2020, while no snow was on the ground and rivers were at or below normal levels. 

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>To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images, Breaklines and Raster DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 1 meter cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
      <supplemental-information>USGS Contract No. G16PC00016 CONTRACTOR: Dewberry SUBCONTRACTOR: Axis Geospatial and Airborne Imaging. Lidar data were acquired and calibrated by Axis Geospatial and Airborne Imaging. All follow-on processing was completed by the prime contractor.
      
   The following are the USGS lidar fields in JSON:
              {
                

    "ldrinfo" : {
              

    "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.3",

    "ldrsens" : "VQ-1560i",

    "ldrmaxnr" : "7",

    "ldrnps" : "0.47",

    "ldrdens" : "4.5",

    "ldranps" : "0.47",

    "ldradens" : "4.5",

    "ldrfltht" : "1828",

    "ldrfltsp" : "130",

    "ldrscana" : "58.52",

    "ldrscanr" : "1000",

    "ldrpulsr" : "206",

    "ldrpulsd" : "3",

    "ldrpulsw" : "0.9",

    "ldrwavel" : "1064",

    "ldrmpia" : "1",

    "ldrbmdiv" : "0.25",

    "ldrswatw" : "1985",

    "ldrswato" : "40",

    "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B"
  },

    "ldrinfo" : {
              

    "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.3",

    "ldrsens" : "VQ-1560i",

    "ldrmaxnr" : "7",

    "ldrnps" : "0.62",

    "ldrdens" : "2.63",

    "ldranps" : "0.62",

    "ldradens" : "2.63",

    "ldrfltht" : "1001",

    "ldrfltsp" : "150",

    "ldrscana" : "58.52",

    "ldrscanr" : "1000",

    "ldrpulsr" : "250",

    "ldrpulsd" : "3",

    "ldrpulsw" : "0.9",

    "ldrwavel" : "1064",

    "ldrmpia" : "1",

    "ldrbmdiv" : "0.25",

    "ldrswatw" : "1902",

    "ldrswato" : "20",

    "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B"
  },

    "ldrinfo" : {
              

    "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.3",

    "ldrsens" : "LMS-Q1560",

    "ldrmaxnr" : "7",

    "ldrnps" : "0.66",

    "ldrdens" : "2.31",

    "ldranps" : "0.66",

    "ldradens" : "2.31",

    "ldrfltht" : "2134",

    "ldrfltsp" : "170",

    "ldrscana" : "58.52",

    "ldrscanr" : "800",

    "ldrpulsr" : "178",

    "ldrpulsd" : "3",

    "ldrpulsw" : "0.9",

    "ldrwavel" : "1064",

    "ldrmpia" : "1",

    "ldrbmdiv" : "0.25",

    "ldrswatw" : "2285",

    "ldrswato" : "20",

    "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B"
  },

    "ldrinfo" : {
              

    "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.3",

    "ldrsens" : "VQ-1560i",

    "ldrmaxnr" : "7",

    "ldrnps" : "0.60",

    "ldrdens" : "2.80",

    "ldranps" : "0.60",

    "ldradens" : "2.80",

    "ldrfltht" : "2000",

    "ldrfltsp" : "140",

    "ldrscana" : "60",

    "ldrscanr" : "172",

    "ldrpulsr" : "467",

    "ldrpulsd" : "3",

    "ldrpulsw" : "0.9",

    "ldrwavel" : "1064",

    "ldrmpia" : "1",

    "ldrbmdiv" : "0.25",

    "ldrswatw" : "2241",

    "ldrswato" : "30",

    "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B"
  },

    "ldrinfo" : {
              

    "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.3",

    "ldrsens" : "LMS-Q1560",

    "ldrmaxnr" : "7",

    "ldrnps" : "0.60",

    "ldrdens" : "2.80",

    "ldranps" : "0.60",

    "ldradens" : "2.80",

    "ldrfltht" : "2000",

    "ldrfltsp" : "160",

    "ldrscana" : "60",

    "ldrscanr" : "191",

    "ldrpulsr" : "533.3",

    "ldrpulsd" : "3",

    "ldrpulsw" : "0.9",

    "ldrwavel" : "1064",

    "ldrmpia" : "1",

    "ldrbmdiv" : "0.25",

    "ldrswatw" : "2241",

    "ldrswato" : "30",

    "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B"
  },

    "ldraccur" : {
              

    "ldrchacc" : "0",

    "rawnva" : "0",

    "rawnvan" : "0"
  },

    "lasinfo" : {
              

    "lasver" : "1.4",

    "lasprf" : "6",

    "laswheld" : "Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.",

    "lasolap" : "Swath "overage" points are assigned per the producer's discretion. Dewberry did not classify overage points.",

    "lasintr" : "16",

    "lasclass" : {
              

    "clascode" : "1",

    "clasitem" : "Processed, but Unclassified"
  },

    "lasclass" : {
              

    "clascode" : "2",

    "clasitem" : "Bare Earth Ground"
  },

    "lasclass" : {
              

    "clascode" : "7",

    "clasitem" : "Low Noise"
  },

    "lasclass" : {
              

    "clascode" : "9",

    "clasitem" : "Water"
  },

    "lasclass" : {
              

    "clascode" : "17",

    "clasitem" : "Bridge Decks"
  },

    "lasclass" : {
              

    "clascode" : "18",

    "clasitem" : "High Noise"
  },

    "lasclass" : {
              

    "clascode" : "20",

    "clasitem" : "Ignored Ground"
  },

    "lasclass" : {
              

    "clascode" : "22",

    "clasitem" : "Temporal"
  }
  }}</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 version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="1fbf5df2-ab7c-43fc-9bb2-8eb3f8891f7b">EARTH SCIENCE &gt; OCEANS &gt; COASTAL PROCESSES &gt; COASTAL 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="854d0bb3-dcc3-48eb-a65a-2d26a8b87394">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; NEW YORK</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>Dewberry, USGS</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1222762" 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="1222761" 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="1222791" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2021</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="1222763" 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="1222764" 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="1222765">
         <geographic-areas>
            <geographic-area cc-id="1222792">
               <west-bound>-77.71</west-bound>
               <east-bound>-74.34</east-bound>
               <north-bound>43.05</north-bound>
               <south-bound>41.4</south-bound>
               <description>Block 5 - Broome, Chemung, Chenango, Cortland, Delaware, Ontario, Otsego, Schuyler, Steuben, Sullivan, Tioga, Yates Counties covering approximately 6,198 square miles.</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1222793">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2019-04-13</start-date-time>
               <end-date-time>2020-09-24</end-date-time>
               <description>Dates of collection for Block 5</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1222794">
         <geographic-areas>
            <geographic-area cc-id="1222795">
               <west-bound>-74.89</west-bound>
               <east-bound>-73.75</east-bound>
               <north-bound>44.11</north-bound>
               <south-bound>42.09</south-bound>
               <description>Block 4 - Albany, Greene, Hamilton and Schenectady Counties covering approximately 3,167 square miles.</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1222796">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2019-04-25</start-date-time>
               <end-date-time>2020-09-25</end-date-time>
               <description>Dates of collection for Block 4</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1222797">
         <geographic-areas>
            <geographic-area cc-id="1222798">
               <west-bound>-78.01</west-bound>
               <east-bound>-75.31</east-bound>
               <north-bound>43.25</north-bound>
               <south-bound>42.23</south-bound>
               <description>Block 3 - Monroe, Ontario, Steuben, Onondaga, Cortland, Chenango, and Madison Counties covering approximately 2,806 square miles.</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1222799">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2019-04-16</start-date-time>
               <end-date-time>2019-05-19</end-date-time>
               <description>Dates of collection for Block 3</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1222800">
         <geographic-areas>
            <geographic-area cc-id="1222801">
               <west-bound>-75.9</west-bound>
               <east-bound>-74.06</east-bound>
               <north-bound>44.23</north-bound>
               <south-bound>42.91</south-bound>
               <description>Block 2 - Lewis, Oneida, Herkimer, Fulton, and Montgomery Counties covering approximately 2,396 square miles.</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1222802">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2019-05-18</start-date-time>
               <end-date-time>2019-09-24</end-date-time>
               <description>Dates of collection for Block 2</description>
            </time-frame>
         </time-frames>
      </extent>
      <extent cc-id="1222803">
         <geographic-areas>
            <geographic-area cc-id="1222804">
               <west-bound>-79.1</west-bound>
               <east-bound>-73.46</east-bound>
               <north-bound>43.38</north-bound>
               <south-bound>40.84</south-bound>
               <description>Block 1 - Niagara, Putnam, and Westchester Counties covering approximately 1,367 square miles.</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1222805">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2019-01-04</start-date-time>
               <end-date-time>2019-04-25</end-date-time>
               <description>Dates of collection for Block 1</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="1222768">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9770/details/9770</download-url>
         <distributor cc-id="1222761">
            <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="1222769">
         <download-url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/NY_FEMAR2_Central_2018_D19/</download-url>
         <distributor cc-id="1222791">
            <from-date>2021</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, horizontal projection/datum of NAD83 (2011), Albers Equal Area, meters and vertical datum of NAVD88 (GEOID12B), meters.</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="1222813">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/NY_FEMAR2_Central_2018_D19/NY_FEMAR2_Central_4_2018/reports/Topographic_Lidar_Project_Report_NY_FEMA_WUID%23226169.pdf</url>
         <name>Lidar Report - Block 4</name>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Block 4 lidar report.</description>
      </url>
      <url cc-id="1222759">
         <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="1222808">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/NY_FEMAR2_Central_2018_D19/</url>
         <name>USGS Additional Info</name>
         <url-type>Online Resource</url-type>
         <description>This link is to the reports, breaklines, metadata, and shapefiles.</description>
      </url>
      <url cc-id="1222811">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/NY_FEMAR2_Central_2018_D19/NY_FEMAR2_Central_2_2018/reports/Topographic_Lidar_Project_Report_NY_FEMA_Block-02.pdf</url>
         <name>Lidar Report - Block 2</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Block 2 lidar report.</description>
      </url>
      <url cc-id="1222812">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/NY_FEMAR2_Central_2018_D19/NY_FEMAR2_Central_3_2018/reports/NY_FEMA_WUID214093_Report.pdf</url>
         <name>Lidar Report - Block 3</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Block 3 lidar report.</description>
      </url>
      <url cc-id="1222814">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/NY_FEMAR2_Central_2018_D19/NY_FEMAR2_Central_5_2018/reports/Topographic_Lidar_Project_Report_NY_FEMA_229498.pdf</url>
         <name>Lidar Report - Block 5</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Block 5 lidar report.</description>
      </url>
      <url cc-id="1222810">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/NY_FEMAR2_Central_2018_D19/NY_FEMAR2_Central_B1_2018/reports/Topographic_Lidar_Project_Report_NY_FEMA_Block-01.pdf</url>
         <name>Lidar Report - Block 1</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Block 1 lidar report.</description>
      </url>
      <url cc-id="1222809">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/NY_FEMAR2_Central_2018_D19/USGS_NY_FEMAR2_Central_2018_D19_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 which provides information about the project, the vertical accuracy results, the point classifications and the sensors used.</description>
      </url>
      <url cc-id="1222816">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_2_2018/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="1222817">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_3_2018/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="1222818">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_4_2018/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="1222819">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_5_2018/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="1222815">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_B1_2018/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="1222820">
         <url>https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_B1_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_2_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_3_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_4_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_5_2018/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>Riegl RiProcess and Leica HxMap; LP360; Microstation; Terrascan; ArcGIS 10.6; Windows 8; .las 5.48 TB</description>
   </technical-environment>
   <data-quality>
      <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) = 5.94 cm at 95% Confidence Level (3.03 cm RMSE)
Vegetated Vertical Accuracy (VVA) = 17.25 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. The raw point cloud is of quality and data passes Non-Vegetated Vertical Accuracy specifications.</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="1222821">
            <citation-title>USGS AWS Entwine Point Tile</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/NY_FEMAR2_Central_B1_2018/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile file for NY_FEMAR2_Central_B1_2018</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1222825">
            <citation-title>USGS AWS Entwine Point Tile</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/NY_FEMAR2_Central_5_2018/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile file for NY_FEMAR2_Central_5_2018</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1222822">
            <citation-title>USGS AWS Entwine Point Tile</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/NY_FEMAR2_Central_2_2018/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile file for NY_FEMAR2_Central_2_2018</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1222823">
            <citation-title>USGS AWS Entwine Point Tile</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/NY_FEMAR2_Central_3_2018/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile file for NY_FEMAR2_Central_3_2018</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1222824">
            <citation-title>USGS AWS Entwine Point Tile</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/NY_FEMAR2_Central_4_2018/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile file for NY_FEMAR2_Central_4_2018</citation-url-name>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1222753">
            <sequence-number>1</sequence-number>
            <description>The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used proprietary  and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.3, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening. Please see the individual block lidar reports (links are in the URL section of this metadata record) for more detailed processing information.</description>
            <process-date-time>2021-01-01T00:00:00</process-date-time>
            <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="1222754">
            <sequence-number>2</sequence-number>
            <description>LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.7 meters was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. 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. The withheld bit was set on the withheld points previously identified in TerraScan before the ground classification routine was performed. The LAS files contain synthetic points.  These points were generated by the Riegl processsing software to fill Multiple Time Around (MTA) zones, which are a physical phenomenon that exists in any time of flight lidar system which has multiple pulses in air and wishes to record all of them seamlessly without range gate limitations. The MTA zones only exist in narrow bands of ranges and typically are dependent on flight planning parameters and project area topography. Dewberry proprietary software was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Dewberry proprietary software 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.  Please refer to the individual block lidar reports (links to these reports are provided in the URL section of this metadata record) for more detailed processing information.</description>
            <process-date-time>2021-01-01T00:00:00</process-date-time>
            <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="1222755">
            <sequence-number>3</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 no changes were made to the vertical of NAVD88 (GEOID12B), meters,</description>
            <process-date-time>2021-01-01T00:00:00</process-date-time>
            <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="1222826">
            <sequence-number>4</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/NY_FEMAR2_Central_B1_2018/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_2_2018/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_3_2018/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_4_2018/ept.json
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_FEMAR2_Central_5_2018/ept.json</description>
            <process-date-time>2023-03-08T00:00:00</process-date-time>
            <process-contact>
               <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>
            </process-contact>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <related-items>
      <related-item>
         <catalog-item-id>75270</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2019 - 2020 USGS Lidar DEM: NY FEMA Region 2 Central</title>
         <relationship-type>Cross Reference</relationship-type>
      </related-item>
   </related-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:69414</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2023-03-09T19:24:20</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2023-10-17T16:12:37</metadata-record-last-modified>
      <record-published>2023-03-09</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-03-09</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2024-03-09</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
